Guide summary
Root, modules, and device safety
Root/system workflows can break boot flow or require recovery. Keep user-facing docs calm, practical, and honest about limits.
Keep a known recovery path before replacing boot media or installing modules.
Confirm device, firmware, boot/shutdown path, file format, and module method.
Use previews and safe test paths before device-level changes.
Collect exact evidence when something fails so fixes can be reviewed.
| Not universal | Samsung/QMG behavior, root methods, firmware builds, and boot media paths vary. Avoid universal claims. |
|---|---|
| Module safety | Magisk/KSU module paths should include uninstall and rollback guidance. |
| Firmware context | Device Lab/Firmware Check style information should inform guidance, not override user responsibility. |
| Store packs | Approved packs may still need device-specific checks before use. |
| Disclaimer | Link the public disclaimer wherever root/system guidance appears. |
Workflow
Use this sequence
A practical flow that maps the public docs back to app behavior and support evidence.
Model, build, Android/One UI, resolution, and root method.
Prepare restore/uninstall route.
Run Package Doctor and preview output.
Avoid stacking unknown changes.
Share confirmed compatibility notes.
Related CRYA docs
Continue with the next useful page
The docs should move users between package work, safety, billing, store review, and support without exposing private admin systems.