Switch from APatch
About 173 wordsLess than 1 minute
APatch follows the KernelPatch path, while YukiSU uses a KernelSU-derived LKM. They cannot be replaced in place.
- Back up APatch settings, module list and exact stock boot images
- Disable APatch/KPM modules and verify the device still boots
- Uninstall using APatch's own flow or restore the correct modified boot partition
- After a clean boot and confirmation that the device is within the Android 12+/ARM64 GKI 2.0 boundary, follow Get started
YukiSU uses SuperKey only to authenticate a manager UID, not as an app root password. Configure YukiSU authentication during migration instead of copying APatch key settings, kernel patches, or its manager. KPM modules cannot be installed as YukiSU modules.
APatch and YukiSU ImgPatch can both involve the kernel inside boot, but their capsules, loaders and recovery metadata are unrelated. Never treat a KernelPatch/KPM kernel as stock input to YukiSU ImgPatch. Restore through APatch first, then select YukiSU's Ramdisk or ImgPatch layout.
Copyright
Copyright Ownership:Anatdx
License under:Attribution-NonCommercial-ShareAlike 4.0 International (CC-BY-NC-SA-4.0)