Switch from Magisk
About 186 wordsLess than 1 minute
Magisk and YukiSU use different boot chains and privilege implementations. There is no in-place conversion that preserves every state.
- Back up data, the module list and exact stock boot images
- Disable Magisk modules and verify a normal boot
- Use Magisk's own uninstall/restore flow, or restore the partition it changed using device documentation
- After the device boots cleanly and is within the Android 12+/ARM64 GKI 2.0 boundary, follow Get started
Do not copy a generic fastboot flash boot command without confirming the partition and slot.
For ImgPatch, input must be a restored stock boot containing the ARM64 kernel. boot-patch-v2 refuses automatic cleanup when it detects a Magisk Ramdisk instead of stacking both boot injection layouts. See Installation and image modes for the Ramdisk/ImgPatch boundary.
Magisk modules can depend on Magisk-specific installer commands or mounting behavior. YukiSU mounts files through built-in Kagami or an enabled external MetaModule. Reuse modules whose authors support KernelSU/YukiSU; do not copy the entire Magisk module directory into YukiSU.
Copyright
Copyright Ownership:Anatdx
License under:Attribution-NonCommercial-ShareAlike 4.0 International (CC-BY-NC-SA-4.0)