KernelSU
About 325 wordsAbout 1 min
2025-12-23
Suitable for original KernelSU and all its forks.
Install using LKM method
If you installed KernelSU using LKM method, please refer to steps and methods of Magisk to switch to FolkPatch.
Install using GKI method
If you installed KernelSU using GKI method, please refer to following steps:
- Patch using unmodified
boot.img. - Flash image in Fastboot mode.
Put phone into Fastboot mode:
adb reboot bootloaderFlash patched
boot.img:fastboot flash boot PATH/TO/patched_boot.imgReboot phone:
fastboot reboot
Clean Up KernelSU Residuals
After switching to FolkPatch, KernelSU may leave residual files in the /data/adb directory. These residual files can affect authorization even if the su path has been switched, which is a sign of incomplete uninstallation.
Check for Residual Files
Use a Root file manager (such as MT Manager) to navigate to the /data/adb directory and check for the following files or folders:
/data/adb
ksud# KernelSU daemon binary
susfs4ksu# KernelSU SusFS directory
Cleanup Steps
- Confirm KernelSU is uninstalled: Make sure the KernelSU manager app is completely uninstalled
- Delete residual files: Use a file manager to delete the residual files and folders listed above
- Reboot the device
- Check su path: Open FolkPatch → check if the Root path on the home page is
/system/bin/su - Manually reset if needed: Go to Settings → General → Reset su Path and change the path to
su
Dangers of Residual Files
Even if FolkPatch's su path shows /system/bin/su, the presence of ksud or susfs4ksu residuals in /data/adb can still cause authorization failures. This is because FolkPatch detects these files and considers them as conflicting Root solutions in the environment, which affects the normal authorization process.
Make sure to thoroughly clean up these residual files after switching.
For more detailed troubleshooting steps, please refer to Superuser FAQ.
Copyright
Copyright Ownership:FolkPatch Team
License under:Attribution 4.0 International (CC-BY-4.0)