TL;DR: SukiSU Ultra is a free, community-maintained kernel-level root solution for Android, forked from KernelSU. Its headline features are built-in KPM (Kernel Patch Module) support and an integrated SUSFS root-hiding manager. You install it by flashing a SukiSU-patched kernel or boot image, then manage superuser access through its own app — while accepting the usual bootloader, warranty and detection risks.
By the PrivacyPortal team · Last updated June 2026
If you have landed here asking "what is SukiSU Ultra?", here is the short version before the detail. SukiSU Ultra (package name com.sukisu.ultra) is one of the most capable members of the KernelSU family — a way to gain root, the highest level of control over your own Android device, from inside the Linux kernel rather than from the boot ramdisk like Magisk. It is maintained by the SukiSU-Ultra organisation (work originally led by the developer known as ShirkNeko) and tracks the KernelSU-Next lineage. What sets it apart is kernel-space modules (KPM) and strong, built-in root hiding (SUSFS). It is powerful and popular, but it is still third-party software that can brick a phone if you rush it.
What is SukiSU Ultra, in plain terms?
SukiSU Ultra is a root manager: software that grants and controls "superuser" permissions so apps can change parts of Android that are normally locked. Unlike Magisk, which patches the boot ramdisk and runs in userspace, SukiSU Ultra is kernel-based — the root logic lives inside the kernel itself and is served by a small daemon called ksud. In practice that means root is harder for apps to spot, and it can reach places userspace root cannot.
Because it is a fork of KernelSU, it keeps that project's Magisk-style module system, so many existing modules work. On top of that it adds two things stock KernelSU does not ship: Kernel Patch Modules (KPM) and a built-in SUSFS manager for hiding root-related files and mounts. It targets modern GKI 2.0 devices (Generic Kernel Image, kernel 5.10 and newer) and, via community backports, a long list of older non-GKI kernels.
Image: The SukiSU Ultra manager app showing a "Working" status with the kernel version and KPM enabled.
Where SukiSU Ultra came from
KernelSU, created by developer weishu, popularised kernel-level root for GKI devices. The community then produced forks that pushed hiding and features further — KernelSU-Next (KSUN), RKSU and SukiSU Ultra among them. SukiSU's distinctive move was backporting APatch's KernelPatch engine to add KPM, giving it kernel-space code injection that mainline KernelSU lacks. You can trace the lineage on the official KernelSU project on GitHub and the SukiSU Ultra project on GitHub.
SukiSU Ultra vs KernelSU: the real differences
Both are kernel-based and share the same core architecture, so a fair "sukisu ultra vs kernelsu" comparison comes down to features, hiding and convenience rather than how root itself works. The table below summarises what actually differs in day-to-day use.
| Feature | SukiSU Ultra | KernelSU | KernelSU-Next | Magisk |
|---|---|---|---|---|
| Root location | Kernel | Kernel | Kernel | Userspace (boot ramdisk) |
| KPM (kernel modules) | Yes, built-in | No | No | No |
| SUSFS root hiding | Built-in manager | Add-on module | Add-on module | Via modules |
| Magisk-style modules | Yes | Yes | Yes | Yes |
| Kernel requirement | GKI 2.0 or patched/custom kernel | GKI 2.0 (5.10+) | GKI 2.0 (5.10+) | Any; no custom kernel |
| Reinstall after OTA | Usually re-patch/re-flash | One-tap LKM | One-tap LKM | Re-patch boot |
The trade-off: SukiSU Ultra gives you more hiding and kernel-level power out of the box, whereas official KernelSU is simpler and has the cleaner "install after an update" story.
As of June 2026, the SukiSU Ultra manager app is on the 4.1.x series, with v4.1.3 the latest stable release.
What KPM, SUSFS and WebUI actually do
KPM (Kernel Patch Modules)
KPM lets you load modules that run inside the kernel, using inline hooks and syscall-table hooks borrowed from the APatch/KernelPatch project. This is more powerful than ordinary Magisk-style modules because it can change kernel behaviour directly — useful for advanced hiding and low-level tweaks. It is also riskier: a bad KPM can cause a bootloop, so add them one at a time and test between each.
SUSFS (built-in root hiding)
SUSFS hides root-related mounts, files and properties from apps that probe for them. SukiSU Ultra ships its own SUSFS manager, so — unlike most other root managers — you do not need a separate SUSFS module to change its settings. Everything is configured from inside the app, which is one less moving part to break.
WebUI and Magisk-module compatibility
The manager includes a WebUI, so modules can present a settings page you open from within the app, and it keeps KernelSU's compatibility with many Magisk-style modules. In practice the integrity stack people pair with it is ReZygisk (a Zygisk implementation), Tricky Store and a Play Integrity Fix module — all listed in the files section below.
Image: SukiSU Ultra's module list with ReZygisk and Tricky Store installed for integrity hiding.
Before you flash: prerequisites and real risks
Rooting with SukiSU Ultra means unlocking your bootloader and replacing part of your boot image or kernel. Treat this seriously and read the risks first.
- Back up everything first. Photos, app data, 2FA seeds and password vaults. Unlocking the bootloader erases all data on the device.
- Bricking is possible. Flashing the wrong image for your exact build can leave the phone unbootable. Keep your stock firmware to recover.
- Warranty and OTA updates. Unlocking may void your warranty, and system updates usually need re-patching afterwards.
- Banking and Play Integrity. Root can trip Google's Play Integrity checks and break banking, wallet and some streaming apps. No method, SukiSU Ultra included, can promise to defeat a specific bank's detection.
- Security. Root removes guardrails; only grant superuser to apps you genuinely trust.
If that list gives you pause, that is healthy. If you want the privacy benefits without flashing anything, every PrivacyPortal de-Googled phone arrives ready to use. For the unlock stage itself, see our guide on how to unlock your bootloader safely.
How to install SukiSU Ultra, step by step
This is the common path for a GKI 2.0 device. Exact partitions and images differ per phone, so confirm yours before flashing. Everything you download is listed in the "Modules, apps & files to try" section at the end.
You will need: a device with an unlockable bootloader; the exact stock boot or init_boot image matching your current build; a PC with Android platform-tools (adb and fastboot); a USB cable; the SukiSU Ultra manager app; and, for non-GKI phones, an AnyKernel3_SukiSU kernel zip.
- Back up and charge. Make a full, tested backup and charge to at least 50%.
- Enable developer options. Turn on OEM unlocking and USB debugging in Settings.
- Unlock the bootloader. Boot to fastboot and run fastboot flashing unlock (or fastboot oem unlock). This wipes the device; set it up minimally afterwards.
- Install the manager app. Open the SukiSU Ultra app; it will report "Not installed" until a patched kernel is flashed.
- Get your boot image. GKI devices launched on Android 13+ patch init_boot; older devices patch boot. Extract the image that matches your exact firmware build.
- Create the patched image. Either use the app's boot-image patching (you will set a patch password), or — for non-GKI phones or stronger hiding — use a SukiSU-patched kernel / AnyKernel3_SukiSU zip built with SUSFS for your model.
- Flash it. In fastboot, test first with fastboot boot patched.img; if it boots cleanly, make it permanent with fastboot flash init_boot patched_init_boot.img (or boot).
- Reboot and verify. Open the app — the status should read "Working" with your kernel version and, where supported, "KPM: enabled".
- Confirm root persists. Grant superuser to a trusted root app, reboot once more and check root still works.
- Optional — add hiding. Install ReZygisk, Tricky Store and a Play Integrity Fix module, then configure them for passing Play Integrity.
Image: A laptop terminal running fastboot to flash a patched init_boot image to a connected phone.
SukiSU Ultra v3.1.7 introduced a crash on LKM (non-GKI) kernels that the earlier v3.1.6 did not have.
Common pitfalls and known bugs
Drawn from real community experience, these are the snags that most often catch people out:
- Wrong image = bootloop. The boot or init_boot image must match your build number exactly. Keep stock firmware to restore.
- Termux "process completed (code 126)". A known SukiSU Ultra bug after granting Termux root; reinstalling Termux helps, but the error often returns after a reboot. KSU-Next + SUSFS does not show this.
- Version regressions. Not every release suits every device — some LKM-kernel users had to stay on an older build when a newer one crashed. Update deliberately, not blindly.
- IntegrityBox bootloops. Some integrity modules can bootloop on certain configurations; add hiding modules one at a time so you can isolate the culprit.
- OTA updates. Unlike KernelSU's one-tap reinstall, SukiSU Ultra usually needs you to re-patch or re-flash after a system update, so do not take an OTA right before you need a working phone.
Does SukiSU Ultra pass Play Integrity and banking apps?
Often, but never guaranteed. SukiSU Ultra has a strong reputation for hiding root out of the box, and many users report that, paired with SUSFS, Tricky Store and a Play Integrity Fix, it passes basic and even device integrity on phones such as the OnePlus 13. That is genuinely better than many setups manage.
Even with strong integrity configured, community testers report that apps such as Google Wallet and Revolut can still detect root on some SukiSU Ultra setups.
So treat hiding as a moving target, not a switch. Banks change detection frequently, and we will never claim SukiSU Ultra defeats a specific bank's checks. If a banking or wallet app is critical to you, test it before relying on root, and keep a clean device or profile as a fallback.
Frequently asked questions
Is SukiSU Ultra safe to use?
It is widely used and open-source, but rooting always carries risk. The main dangers are bricking from flashing the wrong image, a voided warranty, broken updates and tripping app security checks. Back up first and only grant root to apps you trust.
What is the difference between SukiSU Ultra and KernelSU?
Both are kernel-based root. SukiSU Ultra adds built-in KPM (kernel modules) and a built-in SUSFS hiding manager, and it tends to hide root better by default. KernelSU is simpler and has a cleaner one-tap reinstall after updates.
Do I need a custom kernel for SukiSU Ultra?
On GKI 2.0 devices you can patch your boot or init_boot image with the app. On non-GKI or older devices you need a SukiSU-patched custom kernel, usually flashed as an AnyKernel3_SukiSU zip built for your specific model.
Do I still need a separate SUSFS module?
No. SukiSU Ultra includes its own SUSFS manager, so you configure hiding from within the app. Standalone SUSFS modules are only for root managers that lack built-in support.
Will my banking app work after rooting?
Maybe. SukiSU Ultra hides root well, but no root method can promise to pass a particular bank's detection, and apps like Google Wallet and Revolut still fail for some users. Always test before depending on it.
Can I switch to another KernelSU fork without losing modules?
Often yes. Community migrations (for example to a ReSukiSU build) keep modules by granting the new manager superuser, doing a direct LKM install/repair and rebooting before removing the old app. Back up first in case something goes wrong.
SukiSU Ultra, explained simply, is the feature-rich, hiding-focused branch of the KernelSU family — ideal if you want kernel-level power and strong stealth and are comfortable flashing. Grab the manager app, the AnyKernel3_SukiSU kernel and the ReZygisk/Tricky Store integrity stack from the "Modules, apps & files to try" section below, back up first, and take it one careful step at a time.
