KernelSU vs Magisk comes down to where root lives. Magisk patches the boot ramdisk and works on almost any phone with an unlocked bootloader, Samsung included. KernelSU runs inside the kernel and is officially supported only on GKI kernels 5.10 and newer, which in practice means phones that launched with Android 12 or later. APatch also works in the kernel but needs only your stock boot.img; it supports ARM64 phones with kernel versions 3.18 to 6.12. Below is a side-by-side comparison and a simple way to choose.

What Each Root Method Is

Magisk

Magisk, by John Wu (topjohnwu), is the long-standing “systemless” root tool. It patches the ramdisk in your boot, init_boot or vendor_boot image (or recovery, on phones without boot ramdisk). It has root management, modules, Zygisk and DenyList built in. The latest stable version is v31.1 (25 October 2026), and it needs Android 7.0 or newer.

KernelSU

KernelSU gives root from inside the kernel. Current releases install in LKM mode: a loadable kernel module is added to your stock kernel through a patched boot or init_boot image. Since v3.0, KernelSU no longer publishes ready-to-flash GKI boot images. The latest release is v3.3.1 (12 October 2026). It ships kernel modules for GKI versions from android12-5.10 up to android17-6.18.

APatch

APatch is built on KernelPatch. It patches the kernel inside your stock boot.img, so it does not need your phone maker’s kernel source. Its app and module system are based on KernelSU’s. Root access is protected by a SuperKey that you choose. The latest release is build 11282 (15 October 2026). Its notes call it an early release for the newest Xiaomi HyperOS (“Pengpai 4.0”) kernel and say users who are not on the newest kernel do not need to update.

KernelSU vs Magisk vs APatch: Comparison Table

Feature Magisk KernelSU APatch
Where root runs Patched boot ramdisk (userspace) Kernel (loadable module) Kernel (KernelPatch)
Latest release (Nov 2026) v31.1, 25 Oct 2026 v3.3.1, 12 Oct 2026 11282, 15 Oct 2026
Official device support Android 7.0 and newer GKI kernels 5.10+ (phones launched with Android 12+) ARM64 only, kernel 3.18 to 6.12
Image you patch boot, init_boot, vendor_boot or recovery init_boot (if the phone has it) or boot boot.img only
Modules Magisk modules, mounting built in Most Magisk modules; a metamodule is needed for /system changes APModules (Magisk-like) plus kernel modules (KPM)
Zygisk Built in Not built in (separate ZygiskNext module) Not built in (separate module)
Root control Grant per app in the Superuser tab App Profile: limits root per app (user ID, capabilities, SELinux) SuperKey plus per-app root list
Samsung Galaxy Official Samsung install guide Docs say LKM mode cannot work on Knox-enabled Samsung phones Support for Samsung phones with security protection is “planned”
Bootloop safe mode Automatic after two failed boots Press Volume Down more than three times after the first boot screen Press Volume Down repeatedly during boot

Requirements for All Three

  • An unlocked bootloader. Magisk, KernelSU and APatch all say this is required. Unlocking erases the phone, and Android’s own rules make the phone ask for confirmation first.
  • Your phone’s stock image from the official firmware for the build you are running. Keep a copy on your PC so you can flash it back.
  • A PC with adb and fastboot from Google’s SDK Platform-Tools. Our fastboot commands list explains the commands used below.

Some brands no longer allow unlocking. Reports since July 2025 say Samsung’s One UI 8 removed the OEM unlocking option on Galaxy phones, so none of these tools can be installed on those phones.

Which One Should You Choose?

  • Samsung Galaxy (still unlockable): Magisk. It is the only one of the three with an official Samsung guide. Knox is tripped either way.
  • Phone launched with Android 12 or later, and you want fine control over what each root app can do: KernelSU. Install its manager first; if it says Not installed, your kernel is supported. If it says Unsupported, you would have to build your own kernel.
  • Older ARM64 phone that KernelSU does not support: APatch, if the kernel is between 3.18 and 6.12 and has CONFIG_KALLSYMS enabled. Magisk is the simpler option on these phones.
  • You need many Zygisk modules or the widest module support: Magisk, because Zygisk is built in.

Do not mix them. KernelSU’s FAQ says that if any KernelSU module is enabled, Magisk stops working entirely.

How to Install Each One

All three follow the same pattern: patch a stock image in the app, then flash it with fastboot. Flashing overwrites that partition, so use the image from your own phone’s current build.

Magisk

  1. Install the APK from the Magisk GitHub releases page and check Ramdisk on the home screen.
  2. Tap Install > Patch firmware / image and select your boot or init_boot image (or the whole firmware zip).
  3. Copy the patched file to your PC and flash it, for example fastboot flash init_boot magisk_patched-[version]_[random].img.

KernelSU (LKM mode)

  1. Install the manager APK from the KernelSU GitHub releases page and check that it shows Not installed.
  2. Extract init_boot.img from your firmware if your phone has an init_boot partition (common on phones that launched with Android 13 or later). Otherwise extract boot.img.
  3. In the manager, tap the install icon at the top right and choose Select a file. Since v3.3.0 you can also choose Backup as stock image after patching.
  4. Flash the patched file to the same partition with fastboot flash init_boot or fastboot flash boot, then run fastboot reboot.
  5. If your modules change /system, install a metamodule such as meta-overlayfs first and reboot.

APatch

  1. Install the manager from the APatch GitHub releases page and extract boot.img from your firmware. APatch’s docs say not to patch init_boot or other images.
  2. Tap the patch button at the top right and choose Select a boot image to patch.
  3. Set a SuperKey of 8 to 63 characters with letters and numbers only, no special characters. Do not use a weak key such as 12345678.
  4. Tap Start, then flash the result with fastboot flash boot followed by the patched file name, and run fastboot reboot.

APatch warns that the SuperKey has more power than root itself. Anyone who knows it can take control of the phone, so keep it private.

Common Problems

Bootloop right after flashing

Flash your backed-up stock boot or init_boot image with fastboot. KernelSU and APatch both name this as the fix, and it also removes Magisk on non-Samsung phones. Our boot loop guide covers other causes.

Bootloop after installing a module

Use the safe mode listed in the table above. All modules are disabled, and you can then remove the bad one in the app.

KernelSU modules do nothing after a fresh install

Since KernelSU v3.0, modules that change /system are not mounted until you install a metamodule. Updating to 3.0 or later also meant reinstalling all modules.

APatch shows “OS error 2/5/22” when installing modules

APatch’s FAQ says to remove root access from the “Shell” app on the Superuser page.

Banking apps and Google Wallet stop working

This happens with all three. On Android 13 and higher, Google’s Play Integrity device check needs hardware-backed proof that the bootloader is locked, and Google Wallet does not support tap to pay on rooted phones.

Related Guides

FAQ

Is KernelSU better than Magisk?

Not for everyone. KernelSU gives finer control over each root app, and because the core does not mount modules itself, its developers say it is harder to detect. But it only officially supports GKI kernels. KernelSU’s own FAQ says replacing Magisk is not its goal.

Can I use KernelSU and Magisk together?

Only in a limited way. KernelSU’s FAQ says using just its su works alongside Magisk, but if any KernelSU module is enabled, Magisk stops working.

Which root method supports Android 17?

Magisk added Zygisk support for Android 17 in v31.0. KernelSU 3.3.x includes a module for the android17-6.18 kernel. APatch’s docs list kernel versions only up to 6.12. See our Android 17 guide for which phones run it.

Do Magisk modules work on KernelSU and APatch?

Most do, because the module format is nearly the same. Modules that need Zygisk require a separate Zygisk module on KernelSU and APatch. APatch modules cannot be installed from a custom recovery.

What is the APatch SuperKey?

It is the password that unlocks APatch’s kernel features. A program has to send the correct SuperKey to use them. It is set when you patch the boot image, so pick a strong one.

https://droid-developers.com/wp-content/uploads/2026/11/kernelsu-vs-magisk-vs-apatch-featured-1024x538.jpghttps://droid-developers.com/wp-content/uploads/2026/11/kernelsu-vs-magisk-vs-apatch-featured-150x150.jpgFahim MahmudAndroidRootKernelSU vs Magisk comes down to where root lives. Magisk patches the boot ramdisk and works on almost any phone with an unlocked bootloader, Samsung included. KernelSU runs inside the kernel and is officially supported only on GKI kernels 5.10 and newer, which in practice means phones that launched...Android Help,Troubleshooting  & Stock Rom