Magisk compared with KernelSU, APatch and Shizuku
Magisk, KernelSU and APatch all give you root and need an unlocked bootloader. Shizuku is not root at all: it gives supported apps ADB-level access on a locked phone. The right one depends on your kernel, your phone maker and what you want root for.
Last updated 18 sourcesHow we check pages
Short answer
Pick Magisk unless you have a reason not to. It works on old and new kernels, includes Zygisk, patches Samsung firmware, and nearly every module and guide is written for it. Pick KernelSU on a GKI phone if you want root from the kernel with per-app limits. Pick APatch on an ARM64 phone without GKI if you want kernel modules. Pick Shizuku if you can't or won't unlock the bootloader and the app you need supports it.
Not sure whether your phone can be rooted at all? Run the compatibility checker first.
Where each tool works
The biggest difference is the layer each tool lives in. Magisk replaces init in the boot ramdisk, so it starts before Android does and runs as a userspace daemon. KernelSU and APatch put the root logic inside the kernel. Shizuku doesn't modify the phone at all: it runs a server process as the ADB shell user.
Where each tool works
Top of the stack first. Lower layers start earlier in boot and see more of the system.
-
Apps and the ADB shellNormal app sandbox, or the
shelluser thatadbruns asShizuku server -
ZygoteForks every app processZygisk (built into Magisk)Zygisk modules on KernelSU and APatch
-
init and the boot ramdiskFirst userspace process, loaded from
init_boot,bootorvendor_bootMagisk (patched ramdisk) -
KernelGrants root from kernel spaceKernelSU (LKM or built in)APatch (KernelPatch)
-
BootloaderMust be unlocked for Magisk, KernelSU and APatch. Shizuku doesn't need it.
Zygisk sits in the Zygote layer for all three root tools, but only Magisk ships it. On KernelSU and APatch you add it as a module. The Zygisk guide explains what it does.
Feature comparison
What each one can do
| Feature | Magisk | KernelSU | APatch | Shizuku |
|---|---|---|---|---|
Full root (su) | Yes | Yes | Yes | NoADB-level API access |
| Works with a locked bootloader | No | No | No | Yes |
| Works on non-GKI kernels | Yes | PartlyOfficial builds: GKI 5.10+. Forks or own kernel build otherwise | YesARM64, kernel 3.18 to 6.12 | Not applicable |
| Magisk-style modules | Yes | PartlyMounted only with a metamodule | PartlyAPM; metamodule since build 11219 | No |
| Kernel modules (KPM) | No | NoThe SukiSU Ultra fork adds them | Yes | Not applicable |
| Zygisk built in | Yes | NoAdd ReZygisk, NeoZygisk or Zygisk Next | NoSame modules | Not applicable |
| Fine-grained per-app root limits | PartlyGrant or deny per app | YesApp Profile: UID, capabilities, SELinux | PartlyGrant per app | Not applicable |
| Keep root through an A/B OTA from the app | YesInstall to Inactive Slot | YesInstall to inactive slot (LKM) | YesInstall to inactive slot (After OTA) | Not applicable |
| Samsung phones | YesPatches the AP file | PartlyKnox devices need GKI mode | NoListed as planned | Yes |
| Play Integrity DEVICE verdict | NoBASIC at most without spoofing | NoSame | NoSame | YesPhone stays locked |
| Release in the last 3 months | Yesv31.1, Oct 25, 2026 | Yesv3.3.1, Oct 12, 2026 | Yes11282, Oct 15, 2026 | Nov13.6.0, May 25, 2025 |
| Magisk | KernelSU | APatch | Shizuku | |
|---|---|---|---|---|
| Latest release | v31.1 stable (October 25, 2026) | v3.3.1 (Oct 12, 2026) | Build 11282 (Oct 15, 2026) | v13.6.0 (May 25, 2025) |
| Android versions | 6.0 and newer on v30.7; 7.0 and newer from v31.1 | Depends on the kernel, not the Android version | Depends on the kernel | Wireless start needs Android 11+; older versions start from a computer |
| Architectures | ARM, ARM64, x86, x86_64 | ARM64, x86_64, riscv64 (LKM) | ARM64 only | Any |
| Image you flash | init_boot, boot, vendor_boot or recovery | LKM: init_boot (Android 13 launch devices) or boot. GKI mode: boot | boot only, never init_boot | Nothing |
| Hiding from apps | DenyList unmounts Magisk for chosen apps | “Umount modules” on by default for apps without root | “Exclude modifications” per app, plus a test-stage “Hide SELinux modification” setting | n/a |
Forks extend KernelSU further: KernelSU Next (v3.4.2, October 13, 2026) supports kernels from 4.4, and SukiSU Ultra (v4.2.1-r2, October 24, 2026) adds KPM kernel modules.
Which should you choose?
Which should I use?
- NoShizuku: ADB-level access for apps that support it. No root tool works on a locked phone.
- YesIs the kernel GKI, version 5.10 or newer? (
uname -rshows-android12-or later)- No or not sureDo you need kernel modules (KPM)?
- NoMagisk: works on old and new kernels alike
- YesAPatch, if the phone is ARM64 with kernel 3.18 to 6.12
- No
- YesDo you want built-in Zygisk and the most guides, or kernel-level per-app limits?
- Built-in Zygisk, most guidesMagisk
- Per-app limitsKernelSU in LKM mode, plus a metamodule
- Built-in Zygisk, most guides
- No or not sure
- Magisk if you want the widest device support, Zygisk without extra modules, or you follow guides written for Magisk. How to install it.
- KernelSU on a GKI phone (kernel 5.10 or newer) when you want App Profiles that limit what root can do per app, and you are happy to install a metamodule and a Zygisk module yourself.
- APatch when the kernel isn't GKI, there are no kernel sources to build KernelSU, and the phone is ARM64 with a kernel between 3.18 and 6.12. Its SuperKey must be kept private.
- Shizuku when the app you want supports it and ADB-level access is enough. It is the only option on a locked bootloader.
Comparisons
Magisk vs KernelSU
Userspace vs kernel root, GKI and LKM, metamodules, switching safely, and the KernelSU Next and SukiSU Ultra forks.
Magisk vs APatch
KernelPatch, ARM64 limits, the SuperKey, APM and KPM modules, and the init_boot trap when switching.
KernelSU vs APatch
The two kernel-based options: kernel compatibility, how each gets in, and security trade-offs.
Magisk vs Shizuku
What ADB-level access can and can't do, and when you need real root.
Common questions
Can I install Magisk and KernelSU (or APatch) at the same time?
No. KernelSU's FAQ says its module system conflicts with Magisk's, and that enabling any KernelSU module can stop Magisk from working. Zygisk Next's documentation also requires a single root implementation. Remove one completely before you install another. The switching steps show the safe order.
Which root is best for banking apps?
None of them changes the Play Integrity picture. On Android 13 and later the DEVICE and STRONG verdicts need a locked bootloader with hardware attestation, so any rooted phone gets BASIC at most, plus whatever spoofing modules manage at the moment. What differs is how easy each one is to hide from a single app: Magisk has the DenyList, KernelSU unmounts modules for apps by default. See banking apps and root and passing Play Integrity.
Is KernelSU better than Magisk?
Not in general. KernelSU's own FAQ says it focuses on exposing kernel interfaces “instead of supplanting Magisk”. It is a good fit on a GKI phone if you want per-app limits on what root can do. Magisk supports more devices, includes Zygisk, and has far more guides. The full comparison covers the details.
Is Shizuku a root app?
No. Shizuku runs a helper process with ADB privileges (or root, if the phone is already rooted) and lets apps written for it call system APIs through that process. It can't change system files or load modules. See Magisk vs Shizuku.
Which one works on Samsung?
The Magisk app patches Samsung's AP firmware file directly. KernelSU's guide says LKM mode can't work on Knox devices, so Samsung needs its GKI mode. APatch lists Samsung devices with security protection as planned. Note that Samsung removed bootloader unlocking in One UI 8, and US and Canada models can't be unlocked at all. See the Samsung guide.
How do I know if my phone has a GKI kernel?
Run adb shell uname -r. A GKI kernel version contains the Android release it was built for, for example 5.10.198-android12-9 or 6.1.75-android14-11. Android requires GKI on devices that ship with kernel 5.10 or newer from Android 12. The KernelSU manager also tells you: “Not installed” means supported, “Unsupported” means you would need a custom kernel.
Can any of them root a phone with a locked bootloader?
No. Magisk, KernelSU and APatch all flash a modified boot, init_boot or kernel image, and a locked bootloader refuses to boot it. Shizuku is the only one of the four that works locked, because it doesn't modify the phone.
Do the Magisk v31.1 changes affect which one to pick?
They might. v31.1, the current stable release, needs Android 7.0 or newer, removes the option to hide the Magisk app, and removes root pop-ups (you grant access ahead of time in the Superuser tab). v30.7 is the last release with app hiding and the last for Android 6.0. Read the release notes before you update.
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.
- Magisk releases (topjohnwu)
- Magisk documentation (topjohnwu)
- Magisk OTA upgrade guide (topjohnwu)
- KernelSU releases (tiann)
- What is KernelSU? (KernelSU documentation)
- KernelSU installation: LKM, GKI and inactive-slot install (KernelSU documentation)
- KernelSU FAQ (KernelSU documentation)
- APatch releases (bmax121)
- APatch README (bmax121/APatch)
- APatch installation guide (apatch.dev)
- APatch FAQ (apatch.dev)
- APatch manager strings at build 11282 (bmax121/APatch)
- KernelSU manager strings (tiann/KernelSU)
- Shizuku releases (RikkaApps)
- Shizuku README (RikkaApps)
- KernelSU Next releases
- SukiSU Ultra releases
- 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