Compare

Magisk vs KernelSU

Magisk and KernelSU both give you root and run Magisk-style modules, but they work at different layers. Magisk patches the boot ramdisk and runs in userspace. KernelSU grants root from inside the kernel, and on most phones it loads as a kernel module next to your stock kernel.

Last updated 14 sourcesHow we check pages

Short answer

Use Magisk if your phone isn't a GKI device, if you want Zygisk without extra modules, or if you follow guides and modules written for Magisk. Use KernelSU on a GKI phone (kernel 5.10 or newer) if you want root limited per app, modules hidden from other apps by default, and a way to turn root off without flashing. Switching between them is safe if you go back to a stock image in between, as shown below.

At a glance

MagiskKernelSU
Latest releasev31.1 stable (October 25, 2026); v30.7 (Feb 23, 2026) is the last for Android 6.0v3.3.1 (Oct 12, 2026)
Where root livesUserspace: magiskinit in the patched ramdisk, plus the Magisk daemonKernel: root is granted from kernel space
Device supportAndroid 6.0 and newer on v30.7; Android 7.0 and newer from v31.1. Works on most devices, GKI or not.Official builds support GKI devices only; non-GKI support was dropped in v1.0. LKM builds exist for arm64, x86_64 and, since v3.3.1, riscv64. v3.3.0 added Android 17 (android17-6.18) kernels.
Image you patchinit_boot, boot, vendor_boot or recovery (or the Samsung AP file), in the Magisk appLKM mode, recommended for phones: the stock init_boot (Android 13 launch devices) or boot. GKI mode: replace the kernel in boot; recommended for emulators and needed on Samsung Knox devices.
Granting rootSuperuser tab. v30.7 asks with a pop-up; from v31.1 you grant access ahead of time in the Superuser tab.Superuser tab, with an optional App Profile per app
RemovalUninstall Magisk → Complete Uninstall, or Restore Images before an OTAUninstall permanently, Uninstall temporarily (until reboot) or Restore stock image

Magisk and KernelSU feature by feature

FeatureMagiskKernelSU
Works without a GKI kernelYesNoOfficial builds: GKI 5.10+ only
Keeps your stock kernelYesYesLKM mode; GKI mode replaces it
32-bit ARM and x86 phonesYesNoarm64, x86_64, riscv64
Modules mount with nothing extra installedYesNoInstall a metamodule first
Install modules from recoveryYesNo
Zygisk built inYesNoReZygisk, NeoZygisk or Zygisk Next
Limit what root can do per app (UID, capabilities, SELinux)NoGrant or deny onlyYesApp Profile
Modules hidden from other apps by defaultPartlyDenyList, opt-in per appYes“Umount modules by default”
Turn root off without flashingNoYesUninstall temporarily (LKM)
Keep root through an A/B OTAYesInstall to Inactive SlotYesInstall to inactive slot (After OTA)
Samsung phonesYesPatches the AP filePartlyGKI mode only on Knox devices
Magisk v31.1 and KernelSU v3.3.1, from each project's documentation and the KernelSU manager's own strings. Checked October 26, 2026.

How they differ in practice

Kernel compatibility decides most cases. Magisk doesn't care which kernel you run, because it only patches the ramdisk. KernelSU's FAQ says official support is “only for GKI Linux Kernels 5.10+”, and its LKM module must match the kernel's KMI (for example 5.10-android12-9; the sub-level number doesn't matter). Phones that launched with Android 12 or later on kernel 5.10+ usually qualify. Older phones usually don't, even after Android upgrades, because the kernel version doesn't change with the Android version.

Root control is finer in KernelSU. An App Profile can run an app's su with a different UID, a reduced set of Linux capabilities or a custom SELinux context, and KernelSU enforces this in the kernel. Magisk grants or denies root per app (see Magisk's su for its command-line options, including --drop-cap).

Magisk does more out of the box. It mounts modules itself and includes Zygisk. On KernelSU you assemble the same setup from a metamodule plus a Zygisk module. That is more flexible, but it is two extra pieces to install and keep updated.

Module compatibility

KernelSU's documentation lists what is shared: the zip module format, /data/adb/modules, post-fs-data.sh, service.sh, system.prop, sepolicy.rule, and scripts running in BusyBox standalone mode. It also lists the differences module authors need to handle:

  • KernelSU modules cannot be installed from recovery.
  • KernelSU doesn't support .replace files. Use the REPLACE variable instead. To delete a file, use the REMOVE variable or a mknod <file> c 0 0 character device.
  • BusyBox is at a different path (/data/adb/ksu/bin/busybox vs /data/adb/magisk/busybox).
  • KernelSU adds extra script stages (post-mount, boot-completed) and sets KSU=true so scripts can tell which they're running on.

KernelSU v3.0 (November 30, 2025) introduced metamodules and removed the built-in overlayfs mount, and its release notes say all modules must be reinstalled after upgrading to 3.0. Modules that depend on Zygisk also need a Zygisk implementation. Browse the site's module guides for what each popular module needs.

Switching from Magisk to KernelSU

The safe rule: always go back to a stock image before installing the other tool. Patching an image that the other tool already patched can leave both installed, which is the conflict both projects warn about. The bootloader stays unlocked, so none of this wipes your data.

  1. Check that KernelSU supports your kernel

    2 minutes

    Install the KernelSU manager APK from the official releases and open it. “Not installed” on the home screen means your kernel is supported. “Unsupported” (“KernelSU only supports GKI kernels now”) means you would need a custom kernel or a fork, so stay on Magisk. You can also run adb shell uname -r: you need 5.10 or newer with an -android12- or later tag.

  2. Write down your modules and back up

    10 minutes

    Note every module you use and download its latest zip. Magisk's complete uninstall deletes /data/adb/modules, and KernelSU's v3.0 release notes say modules must be reinstalled anyway. Back up anything you can't lose. The switch doesn't need a data wipe, but a mistake in the next steps can leave you needing one.

  3. Get the stock image for your exact build

    10 minutes

    Extract the stock init_boot.img (most phones that launched with Android 13 or later) or boot.img from the firmware that matches your build number, the same way you did for Magisk. See getting the boot image. Always patch a stock image with KernelSU, never one Magisk already patched.

  4. Remove Magisk completely

    3 minutes

    In the Magisk app, tap Uninstall Magisk → Complete Uninstall. Magisk's uninstaller restores the stock boot image (from its backup, or from the copy saved inside the patched ramdisk), removes modules and Magisk files under /data/adb, uninstalls the app and reboots. To be sure nothing is left, also flash the stock image you extracted:

    Flash the stock image back
    $adb reboot bootloader # Android 13+ launch devices $fastboot flash init_boot init_boot.img # Everything else $fastboot flash boot boot.img $fastboot reboot
  5. Patch the stock image in the KernelSU manager

    3 minutes

    In the KernelSU manager, tap Install → Select a file and patch, pick the stock image and let it patch. This is LKM mode, which KernelSU recommends for phones. Copy the patched image to your computer and flash it to the same partition with fastboot flash init_boot or fastboot flash boot. If the phone supports fastboot boot, KernelSU's guide also allows booting the image once first and then using Direct install.

  6. Install a metamodule, then your modules

    10 minutes

    The manager should now show Working. Install a metamodule such as meta-overlayfs first. Without one, KernelSU doesn't mount module files. Then add a Zygisk module if you need Zygisk (see ReZygisk vs Zygisk Next), then your other modules. Grant root to apps from the Superuser tab.

If the phone doesn't boot after flashing the KernelSU image, flash the stock image from step 3 again with fastboot and you are back to an unrooted phone. The bootloop guide covers the details.

Going back from KernelSU to Magisk

  1. In the KernelSU manager, open Settings → Uninstall → Uninstall permanently. The manager describes this as removing “Root and all modules”. (Restore stock image is meant for OTA updates; the manager itself points you to the permanent option for uninstalling.)
  2. Reboot to the bootloader and flash the stock init_boot.img or boot.img for your build, to be certain no KernelSU patch remains.
  3. Uninstall the KernelSU manager and any Zygisk module apps, then install Magisk as usual: install guide. Patch the stock image in the Magisk app.
  4. Reinstall your modules from the Magisk app. Remove metamodules and Zygisk modules made for KernelSU: Magisk mounts modules and runs Zygisk itself.

KernelSU Next and SukiSU Ultra

Two active forks of KernelSU are common search topics. Both are licensed GPL-2.0 for the kernel part and GPL-3.0 or later for the rest.

KernelSU NextSukiSU Ultra
Latest releasev3.4.2 (Oct 13, 2026)v4.2.1-r2 (Oct 24, 2026)
Kernels4.4 to 6.18; prebuilt images and LKM for GKI 2.0, driver built into the kernel for 4.19 to 5.4, 3.18 and newer experimentalGKI 2.0 (5.10 and newer); non-GKI 4.14 and newer with a manual kernel build
Notable extrasMetamodule-based modules, built-in SUSFS loading on GKI 2.0, module and profile backupKPM kernel modules (based on KernelPatch) and a built-in SUSFS manager

The switching steps above apply to the forks too: return to a stock image, then install the fork's own manager and image. KernelSU, KernelSU Next and SukiSU Ultra are separate projects, so don't mix one's manager with another's kernel.

Common questions

Can I keep Magisk and add KernelSU?

Not with modules. KernelSU's FAQ says its module system conflicts with Magisk's magic mount, and enabling any KernelSU module can stop Magisk from working entirely. It says using only KernelSU's su works alongside Magisk, but there is little reason to run two root tools. Pick one.

Do Magisk modules work on KernelSU?

Most simple ones do, once a metamodule is installed. Modules that use .replace files, the Magisk BusyBox path, Zygisk, or recovery installation need changes or an extra module. Modules check KSU=true to tell where they are running.

Is KernelSU harder for apps to detect than Magisk?

There is no published measurement either way, and detection methods change constantly. What is documented: KernelSU removes module changes for apps without root by default, and v3.2.5 added an SELinux hide feature. Magisk relies on the DenyList, which you turn on per app. Neither changes Play Integrity's DEVICE verdict, which needs a locked bootloader on Android 13 and later. See banking apps and root.

My phone says “Unsupported” in KernelSU. What now?

Your kernel isn't a supported GKI kernel. KernelSU dropped official non-GKI support in v1.0 (the last version with it was v0.9.5). Your options are Magisk, a fork such as KernelSU Next (kernels from 4.4), building a kernel with KernelSU yourself, or APatch on ARM64 with kernel 3.18 to 6.12.

How do OTA updates work with each?

Both follow the same pattern on A/B phones. Magisk: Uninstall → Restore Images (don't reboot), install the update, then Install → Install to Inactive Slot. KernelSU: Restore stock image (the manager says it is “usually used before OTA”), install the update, then Install to inactive slot (After OTA), which forces the next boot into the updated slot. See keeping root through updates.

Does KernelSU have Zygisk?

Not built in. Install ReZygisk or NeoZygisk (open source) or Zygisk Next (closed source) as a module. Zygisk modules, such as Vector, the continuation of LSPosed, need one of these before they load on KernelSU.

Can I unroot KernelSU temporarily for one app?

Yes, in LKM mode. Settings → Uninstall → Uninstall temporarily turns KernelSU off until the next reboot without flashing anything. Magisk has no equivalent: you would restore images and reflash.

Sources

This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.

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