How to ask
About 392 wordsAbout 1 min
Include the device model, Android version, build fingerprint, complete uname -r, current slot, actual patched partition, target KMI, and the firmware source of the image. Record full manager/LKM versions, both manager-bundled and device-installed ksud versions, and the Hook type and working mode shown on Home (Ramdisk, ImgPatch, or Jailbreak/late-load). If an integrity mismatch makes the installed version read “Unknown,” record that exact state instead.
Give the shortest reproduction from a clean boot, expected and actual results, the last known-good state, and the single change made before failure. Save or share the manager bugreport and attach the complete installation output when relevant. For module issues, include the module ID/version, MetaModule state, YukiZygisk status, target process, module type, and ABI.
Include the logs and state for your issue:
| Problem | Also include |
|---|---|
| ImgPatch, image patch, or restore | Input provenance, target partition/slot, full patch output, and whether an original-image backup exists |
| Install to inactive slot after OTA | Whether OTA completed, slot before/after the operation, target image, and target KMI |
| Feature switch failed to save | Feature name, before/after state, and whether the manager reported rollback or requested a reboot |
ksud replacement warning | Bundled version, installed-side “Unknown/mismatch” state, warning time, and any root manager or sync action run beforehand |
| YukiZygisk/native module | Module type and ABI, target name/path, and whether status says not observed or injection failed |
Before filing:
- reproduce on the latest stable or identify the exact CI commit
- disable unrelated modules to minimize variables
- search GitHub Issues
- remove SuperKeys, personal paths, accounts, package lists, and unrelated private data
Describe the operation and the step that failed. Attach the first error and surrounding text logs; use screenshots to show the UI state. A manager bugreport can include properties, processes, packages, mounts, kernel data, and YukiZygisk diagnostics; review it before sharing.
Support: GitHub Issues · Telegram
Additional logs for module and runtime issues
| Area | Include |
|---|---|
| Mounting | Kagami/external MetaModule, actual backend, target namespace and unmount settings |
| Hot installation | Module request, current mode, full installer/script output, directory-switch state |
| Preinit | Kernel support, preparation status, failed-boot count, early logs, last full reboot |
| One-shot script | Source/version, redacted parameters, exit code, run history |
| YukiZygisk | Load policy, target/PID, injection outcome, exit evidence, isolation and daemon recovery state |
Copyright
Copyright Ownership:Anatdx
License under:Attribution-NonCommercial-ShareAlike 4.0 International (CC-BY-NC-SA-4.0)