website/docs/guide/faq.md
KernelSU supports devices running Android with an unlocked bootloader. However, official support is only for GKI Linux Kernels 5.10+ (in practice, this means your device needs to have Android 12 out-of-the-box to be supported).
You can easily check the support for your device through the KernelSU manager, which is available here.
If the app shows Not installed, it means your device is officially supported by KernelSU.
If the app shows Unsupported, it means your device isn't officially supported at present. However, you can build kernel source code and integrate KernelSU to make it work, or use Unofficially supported devices.
Yes. KernelSU requires an unlocked bootloader.
Yes, most Magisk modules work on KernelSU. However, if your module needs to modify /system files, you need to install a metamodule (such as meta-overlayfs). Other module features work without a metamodule. Check Module guide for more info.
Yes, you can use LSPosed (or other modern Xposed derivative) with ZygiskNext.
KernelSU has no built-in Zygisk support, but you can use a module like ZygiskNext to support it.
KernelSU's module system conflicts with Magisk's magic mount. If any module is enabled in KernelSU, Magisk will stop working entirely.
However, if you only use the su of KernelSU, it will work well with Magisk. KernelSU modifies the kernel, while Magisk modifies the ramdisk, allowing both to work together.
No. Replacing Magisk isn't our goal. Magisk is already an excellent userspace root solution. KernelSU focuses on exposing kernel interfaces to users instead of supplanting Magisk.
It's possible. But you should download the kernel source, integrate KernelSU into the source tree, and compile the kernel yourself.
It's the device's kernel that affects KernelSU's compatibility, and it has nothing to do with the Android version. The only restriction is that devices launched with Android 12 must have a kernel version of 5.10+ (GKI devices). So:
It's possible. KernelSU is backported to kernel 4.14 now. For older kernels, you need to backport it manually, and PRs are always welcome!
Please check the Integrate for non-GKI devices guide.
The kernel version has nothing to do with the Android version. If you need to flash kernel, always use the kernel version; the Android version isn't as important.
GKI 1.0 is completely different from GKI 2.0, you must compile kernel by yourself.
/system RW?We don't recommend that you modify the system partition directly. Please check Module guide to modify it systemlessly. If you insist on doing this, check magisk_overlayfs.
Of course. But KernelSU doesn't have built-in hosts support, you can install a module like systemless-hosts to do it.
If your modules need to modify /system files, you need to install a metamodule to mount the system directory. Other module features (scripts, sepolicy, system.prop) work without a metamodule.
Solution: See the Metamodule Guide for installation instructions.
A metamodule is a special module that provides infrastructure for mounting regular modules. See the Metamodule Guide for a complete explanation.