KernelSU vs APatch
KernelSU and APatch both grant root from the kernel rather than from userspace like Magisk. APatch's UI and module code were derived from KernelSU, so they feel alike, but they get into the kernel in different ways and suit different kernels.
Last updated 13 sourcesHow we check pages
Short answer
Your kernel decides. On a GKI phone (kernel 5.10 or newer), use KernelSU in LKM mode: it keeps the stock kernel, limits root per app, and is the only one of the two that supports kernels newer than 6.12. On an older, non-GKI ARM64 phone (kernel 3.18 to 5.4), use APatch, which only needs the stock boot.img. If you want KPM kernel modules, use APatch or the SukiSU Ultra fork. If neither fits, Magisk works on almost any kernel.
Which one fits your kernel?
uname -r show?- 5.10 or newer with an
-android12-or later tag (GKI)Is the version newer than 6.12?- Yes (for example 6.18)KernelSU. v3.3.0 added
android17-6.18; APatch stops at 6.12 - NoDo you need KPM kernel modules?
- NoKernelSU in LKM mode
- YesAPatch, or the SukiSU Ultra fork of KernelSU
- No
- Yes (for example 6.18)
- Older or non-GKI (3.18 to 5.4)ARM64 with
CONFIG_KALLSYMS=y?- YesAPatch, patching only the stock
boot.img - NoMagisk, or KernelSU built into a custom kernel
- Yes
adb shell uname -r.At a glance
| KernelSU | APatch | |
|---|---|---|
| Latest release | v3.3.1 (Oct 12, 2026) | Build 11282 (Oct 15, 2026) |
| Target devices | Officially GKI 2.0 devices (kernel 5.10 and newer); older kernels from 4.14 with a manual kernel build. LKM builds for arm64, x86_64 and riscv64. | ARM64 devices with Android kernel 3.18 to 6.12 and CONFIG_KALLSYMS=y |
| How it gets in | LKM mode loads a kernel module without replacing the kernel and patches init_boot on Android 13 launch devices (recommended for phones). GKI mode replaces the kernel in boot; needed on Samsung Knox devices. | Inserts KernelPatch into the existing kernel in boot.img (never init_boot) |
| Modules | Magisk-like modules, mounted only once a metamodule is installed (since v3.0) | APM (Magisk-like, metamodule since build 11219) and KPM (kernel code with inline and syscall-table hooks) |
| Access control | Superuser list with per-app App Profiles enforced in the kernel | Superuser list, plus a SuperKey that APatch warns has higher privileges than root |
| Zygisk | Via a module: ReZygisk, NeoZygisk or Zygisk Next | Via a module: ReZygisk, NeoZygisk or Zygisk Next |
| License | GPL-2.0-only for the kernel part, GPL-3.0-or-later for the rest | GPL-3.0 |
KernelSU and APatch feature by feature
| Feature | KernelSU | APatch |
|---|---|---|
| GKI kernels 5.10 to 6.12 | Yes | Yes |
| Kernels newer than 6.12 | Yesandroid17-6.18 since v3.3.0 | No |
| Non-GKI kernels with no custom build | No4.14+ only with a manual kernel build | Yes3.18 and newer |
| x86_64 devices and emulators | Yes | NoARM64 only |
| Leaves the kernel image unmodified | YesLKM mode | NoKernelPatch is inserted into it |
| Samsung Knox devices | PartlyGKI mode only | NoPlanned |
| Kernel modules (KPM) | NoSukiSU Ultra fork adds them | Yes |
| Limit root per app (UID, capabilities, SELinux) | YesApp Profile | PartlyGrant or deny per app |
| Hide module changes from chosen apps | YesOn by default | Yes“Exclude modifications” |
| Turn root off until reboot, no flashing | YesUninstall temporarily | Not applicableNot documented |
| Install to inactive slot after an OTA | Yes | Yes |
| Root without a secret key | Yes | NoSuperKey |
Kernel compatibility in detail
KernelSU ships prebuilt LKM modules per KMI, the part of the kernel version such as 5.10-android12-9 or 6.1-android14-11. Its install guide notes that the sub-level (the third number) isn't part of the KMI, and that the Android version and kernel version are independent. Android has required GKI on devices shipping kernel 5.10 or newer since Android 12, so most phones that launched with Android 12 or later qualify. The manager's home screen tells you: “Not installed” means supported, “Unsupported” means you need a custom kernel.
APatch doesn't depend on GKI. It patches whatever ARM64 kernel is in your boot.img, as long as the version is between 3.18 and 6.12 and the kernel was built with CONFIG_KALLSYMS=y. With CONFIG_KALLSYMS_ALL=n the README lists only “initial support”. Its guide says kernel 6.6 has only been tried on Xiaomi and OnePlus devices, and build 11282's notes list known issues with selinux_hide and KPM compatibility on some kernels.
Security model
KernelSU decides in the kernel which apps get root, and an App Profile can narrow what an app's su can do: a different UID and groups, fewer Linux capabilities, or a custom SELinux context. KernelSU's documentation stresses that this “is enforced in the kernel and doesn't rely on the voluntary behavior of root apps”.
APatch adds a second path: KernelPatch's SuperCall grants kernel privileges to any caller that presents the SuperKey. The README warns that a weak or leaked key can let someone take control of the device, and patching requires 8 to 63 letters and numbers with weak keys rejected. Choose a long random key and keep it out of clipboards and screenshots. See the SuperKey explained.
Switching between KernelSU and APatch
They usually live in different partitions, which is the trap. On most phones that launched with Android 13 or later, KernelSU's LKM mode patches init_boot, while APatch always patches boot. Flashing APatch without removing KernelSU leaves both active. APatch's guide also says not to patch a boot.img that another manager already patched.
KernelSU to APatch:
- Check APatch's requirements while you still have root:
adb shell su -c 'zcat /proc/config.gz | grep -w CONFIG_KALLSYMS'should printCONFIG_KALLSYMS=y. - In the KernelSU manager, use Settings → Uninstall → Uninstall permanently, which removes root and all modules.
- Flash the stock
init_boot.img(if your firmware has one) and stockboot.imgwith fastboot. If you used KernelSU's GKI mode, the stockboot.imgalso puts your original kernel back. - Patch the stock
boot.imgin APatch with a strong SuperKey, flash it withfastboot flash boot, then install a metamodule and your modules.
APatch to KernelSU: use APatch's Uninstall KPatch mode (UnPatch) or flash the stock boot.img, boot once to confirm root is gone, then patch the stock init_boot.img (or boot.img on older phones) in the KernelSU manager with Select a file and patch. Reinstall modules after a metamodule. KPMs don't carry over; on KernelSU only the SukiSU Ultra fork loads them.
Moving to or from Magisk instead? See Magisk and KernelSU or Magisk and APatch. If a phone won't boot after any of this, flash the stock images again; the bootloop guide has more.
Common questions
Is APatch better than KernelSU?
Neither is better everywhere. On a GKI phone KernelSU is the more conservative choice: it doesn't modify the kernel image in LKM mode, it limits root per app, and it supports kernels newer than 6.12. APatch wins on older non-GKI ARM64 kernels and when you want KPM kernel modules.
Does KernelSU need kernel source code?
Only for kernels it doesn't support officially. APatch's FAQ says KernelSU needs your kernel source. That only applies to kernels KernelSU doesn't support officially: GKI 2.0 kernels (5.10 and newer) use KernelSU's prebuilt LKM modules or GKI images and need no source. Older kernels (4.14 and newer) still need a manual kernel build, per KernelSU's README.
Do either of them include Zygisk?
No. Both need a Zygisk module: ReZygisk, NeoZygisk or Zygisk Next. APatch's FAQ adds that its developers won't handle Zygisk bug reports; report those to the module's author. The Zygisk comparison explains the options.
Why don't my modules work after installing?
Both now hand module mounting to a metamodule: KernelSU since v3.0 and APatch since build 11219. Without a metamodule installed, module files aren't mounted. Install one first, then reinstall your other modules.
Which passes Play Integrity better?
Neither changes the outcome. On Android 13 and later the DEVICE and STRONG verdicts need a locked bootloader with hardware attestation, so both get BASIC at most without spoofing modules. See the Play Integrity guide.
Can I install the KernelSU manager and APatch together?
Installing both apps is harmless, but only one root implementation should be patched into the phone. Remove one completely, back to stock images, before installing the other.
No match. Try another word from the error message.
Sources
This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.
- KernelSU README: compatibility and license (tiann/KernelSU)
- KernelSU installation: LKM and GKI modes (KernelSU documentation)
- KernelSU FAQ (KernelSU documentation)
- KernelSU App Profile (KernelSU documentation)
- KernelSU metamodules (KernelSU documentation)
- KernelSU releases, including v3.3.0 and v3.3.1 (tiann)
- KernelSU manager strings (tiann/KernelSU)
- APatch README: requirements and license (bmax121/APatch)
- APatch installation guide (apatch.dev)
- APatch FAQ (apatch.dev)
- APatch releases (bmax121)
- APatch manager strings at build 11282 (bmax121/APatch)
- Generic Kernel Image requirements (Android Open Source Project)
Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.
Report a problem with this page