Last updated: November 12, 2026. Short answer: for most Xiaomi, Redmi and POCO owners on HyperOS 3 or 4, Magisk 31.1 is still the easiest root. If you want better root hiding without a custom kernel on a recent phone (Xiaomi 13 to 17, Redmi Note 13 to 15), use KernelSU Next 3.4.2. Choose SukiSU Ultra if you want kernel patch modules (KPM) and a custom kernel, plain KernelSU 3.3.1 if you prefer the upstream project, and APatch for older or non-GKI phones without kernel source. Remember that APatch patches boot.img, not init_boot.img. All of them need an unlocked bootloader and the boot image from the exact build your phone runs.
Latest versions (November 2026)
| Root | Latest version | Released | Download |
|---|---|---|---|
| Magisk | 31.1 | Oct 25, 2026 | GitHub · our Magisk guide |
| KernelSU | 3.3.1 | Oct 12, 2026 | GitHub |
| KernelSU Next | 3.4.2 | Oct 13, 2026 | GitHub |
| SukiSU Ultra | 4.3.0-r2 | Nov 5, 2026 | GitHub |
| APatch | 11282 | Oct 15, 2026 | GitHub |
| ZygiskNext (Zygisk for KernelSU/APatch) | 1.5.3 | Nov 7, 2026 | GitHub |
Download root apps only from their GitHub releases. Re-uploads on YouTube, Telegram or “one-click root” sites are a common way to spread malware.
Comparison
| Magisk | KernelSU | KernelSU Next | SukiSU Ultra | APatch | |
|---|---|---|---|---|---|
| How it roots | Patches the ramdisk | Kernel module (LKM) | Kernel module (LKM) | Kernel module or built-in | Patches the kernel image |
| File to patch on Xiaomi | init_boot (boot on older phones) | init_boot (boot on older) | init_boot (boot on older) | init_boot / boot / vendor_boot | boot.img only |
| Custom kernel needed? | No | No on kernel 5.10+ (GKI); yes on older | No on 5.10+; yes on older | No for root; yes for KPM | No (kernel 3.18–6.12) |
| Modules | Magisk modules (largest choice) | KSU modules; most Magisk modules after a metamodule | Same, plus backup and risky-module check | Same, plus KPM | APM (Magisk-like) plus KPM |
| Zygisk / LSPosed | Built in | Needs ZygiskNext | Needs ZygiskNext | Needs ZygiskNext | Needs ZygiskNext |
| Root hiding | DenyList + modules | Per-app profiles | Built-in SUSFS without custom kernel, spoofed manager | SUSFS (custom kernel), mount hiding | Kernel level; SELinux hide buggy on some kernels |
| Difficulty | Easiest | Easy | Easy | Easy (root) / hard (KPM) | Medium (SuperKey) |
Which one for your Xiaomi?
- First root, or you rely on many Magisk modules: Magisk 31.1. Note that 31.1 removed root pop-ups (grant root in advance in the Superuser tab) and the “hide Magisk app” option.
- Xiaomi 13, 14, 15, 17, Redmi Note 13–15, POCO F5–F8, X6–X8 and you want banking apps to work more often: KernelSU Next. It loads SUSFS root hiding itself on stock kernels. Owners report it working on a Xiaomi 17 Pro where Magisk and official KernelSU failed. Hiding is never guaranteed: Google Wallet contactless and some banks still detect it.
- You want the upstream project with no extras: KernelSU 3.3.1.
- You build or flash custom kernels and want KPM: SukiSU Ultra. On a stock Xiaomi kernel it gives root and modules, but KPM needs a kernel built with KPM support.
- Older Xiaomi/Redmi phones on kernel 4.14–5.4 (Mi 11, Redmi Note 10/11, Helio phones) without a custom kernel: APatch, or Magisk. KernelSU variants need a custom kernel there.
Check your kernel first: Settings → About phone → All specs → Kernel version, or adb shell uname -r. A version like 6.12.23-android16 means GKI (KernelSU works without a custom kernel; the android16-6.12 part is your KMI). Typical values: Xiaomi 12 series 5.10, Xiaomi 13 series 5.15, Xiaomi 14 series 6.1, Xiaomi 15 series 6.6, Xiaomi 17 series 6.12. The HyperOS 4 update doesn’t change the kernel generation: a Xiaomi 17 Ultra on HyperOS 4 still reports android16-6.12.
Where to get the boot image
All methods need the image from the Fastboot ROM of your exact build (same version and region, e.g. OS3.0.303.0.WOJMIXM):
- Download the Fastboot ROM (
.tgz) from your phone’s page in our firmware hub. - Extract it with 7-Zip. The images are in the
imagesfolder:init_boot.img(phones launched with Android 13 or later) andboot.img. - Keep an unpatched copy on your PC: it’s your way back if the phone bootloops.
The bootloader must be unlocked: how to unlock a Xiaomi bootloader on HyperOS. You need ADB and Fastboot on the PC.
How to install KernelSU / KernelSU Next / SukiSU (LKM)
- Install the manager APK from GitHub (for example
KernelSU_Next_v3.4.2_33355-release.apk). If it says Not installed, your kernel is supported. Unsupported means you need a custom kernel. - Copy
init_boot.img(orboot.imgon phones without init_boot) to the phone. - In the manager tap Install → Select a file, choose the image and confirm the detected KMI (e.g.
android16-6.12). The patched file is saved in Download. - Copy it to the PC and flash it:
adb reboot bootloaderfastboot flash init_boot kernelsu_patched_xxxxx.imgfastboot reboot - Open the manager: it should show Working (LKM). Before installing modules that change system files, install a metamodule such as meta-overlayfs; without it those modules don’t mount. Add ZygiskNext if you need Zygisk or LSPosed.
How to install APatch
- Extract
boot.img(not init_boot) from the Fastboot ROM of your build. - Install the APatch APK, tap the patch button → Select a boot image to patch, choose
boot.imgand set a SuperKey: 8–63 letters and numbers, strong and private. The SuperKey grants more than root, so anyone who knows it controls the phone. - Flash the result:
fastboot flash boot apatch_xxxxx.img, thenfastboot reboot. - Open APatch, enter the SuperKey and install AndroidPatch and KernelPatch when the app asks. Use APM for modules, plus ZygiskNext if needed.
APatch 11282 adds support for the newest HyperOS 4 kernels, but its own notes call it an early release, warn that upgrading is risky, and ask you to uninstall embedded KPMs first. If you don’t have a brand-new HyperOS 4 kernel, you don’t need it.
Updating HyperOS on a rooted phone
An update replaces the patched image, so root is gone afterwards. The safest order on Xiaomi:
- Before an incremental OTA, restore the stock image (manager → Uninstall → Restore stock image), or use the full Recovery ROM of the new build. Install the update and boot normally without root once.
- Download the Fastboot ROM of the new build, extract its
init_boot.imgorboot.img, patch it again and flash it.
Avoid the “Install to inactive slot (after OTA)” shortcut on HyperOS: owners report bootloops with it on a Xiaomi 15 (HyperOS 4 beta, KernelSU) and a Xiaomi 15 Pro (HyperOS 3, SukiSU). If it happens, flash the stock image of the new build from Fastboot, boot once, then flash the patched one. For the big jump to HyperOS 4, read how to install HyperOS 4 manually first.
Problems and fixes
| Problem | Fix |
|---|---|
| Bootloop after flashing | Flash the stock image from the same ROM: fastboot flash init_boot init_boot.img (or boot). Your data stays. Usually the image was from another build or region. |
| Bootloop after installing a module | KernelSU: boot into Safe Mode (from Recovery on HyperOS, or press Volume Down three times right after the first boot logo) to disable modules, then remove the module. Leftover modules in /data/adb/modules have caused bootloops on Xiaomi 17. |
| Manager says “Unsupported” | Your kernel is older than 5.10 GKI. Use APatch or Magisk, or a custom kernel. |
| APatch: “init_boot doesn’t patch” | APatch only patches boot.img. Use boot.img even on phones that have init_boot. |
| Magisk modules don’t change anything on KernelSU | Install a metamodule (meta-overlayfs or magic mount) first. |
| Banking apps or Google Wallet detect root | Try KernelSU Next with SUSFS, or Magisk’s DenyList with integrity modules. There’s no permanent fix: detection changes all the time, and Wallet contactless often needs strong integrity that rooted phones lose. |
Don’t mix root methods. Before switching (for example from Magisk to KernelSU Next), uninstall the old one and flash the stock image first.
FAQ
Is KernelSU better than Magisk on Xiaomi?
Not in general. Magisk is easier and has more modules. KernelSU Next is better at hiding root on recent GKI phones, which matters for banking apps. Both are actively maintained.
Does APatch use init_boot.img?
No. APatch always patches boot.img, because it modifies the kernel, not the ramdisk.
Do I need a custom kernel for KernelSU on my Xiaomi?
Not if your kernel is 5.10 or newer with a GKI version string (Xiaomi 12 series and newer, most 2022+ Redmi and POCO). Older kernels need a custom kernel, or use APatch/Magisk.
Does root work on HyperOS 4?
Yes. Owners report Magisk, KernelSU Next and SukiSU working on HyperOS 4 phones such as the Xiaomi 17 series. Re-patch the boot image after every update and avoid the inactive-slot OTA shortcut.
Can I root without unlocking the bootloader?
No. All these methods flash a modified boot image, which a locked bootloader refuses.
Xiaomi firmware & news on Telegram
New firmware, HyperOS 4 rollout updates, guides and Xiaomi news, all in one channel.