TL;DR: The OnePlus 15 16.0.9.400 KernelSU SUSFS combination is not yet a safe, universal flash. Tested OxygenOS firmware uses kernel 6.12.52, while the latest public WildKernels package targets 6.12.23. Do not flash that older package. Wait for an image verified for your exact model, region and firmware.
By the PrivacyPortal team
Last updated September 2026. This guide is current as of 25 September 2026.
A OnePlus 15 running OxygenOS 16.0.9.400 can support KernelSU and SUSFS in principle. However, the available public package does not match the kernel found on tested CPH2749/OP611FL1 hardware. The phone used 6.12.52-android16-5, while WildKernels v2.2.0-r4 listed a 6.12.23 build. A ColorOS user also reported a bootloop after flashing that earlier package. The safe answer is to wait for a build that names your firmware and device variant.
Back up every important file before changing anything. Unlocking the bootloader wipes the phone. A bad image can also cause a bootloop or, in rare cases, leave the device needing a full recovery. Root may affect warranty support, over-the-air updates, banking apps and Play Integrity results.
OnePlus 15 16.0.9.400 KernelSU SUSFS compatibility status
The current status is platform-compatible but not package-verified. KernelSU can work with the Android 16 and Linux 6.12 platform. SUSFS can also work when it is compiled into a compatible kernel. Neither fact makes an older OnePlus 15 image safe to flash on 16.0.9.400.
A kernel version difference does not prove that every build will fail. Android’s Generic Kernel Image design can preserve interfaces across some updates. Yet a flash package may also contain device-specific kernel code, ramdisk changes and assumptions about partitions. Those details can turn a small-looking version gap into a boot failure.
Physical testing on CPH2749/OP611FL1 with OxygenOS 16.0.9.400 found kernel 6.12.52-android16-5 on 25 September 2026.
Image caption: The Software information and kernel version screens identify the exact firmware that a root image must match.
What the available builds actually cover
| Item | Observed status | What it means |
|---|---|---|
| Tested OnePlus 15 | CPH2749/OP611FL1, OxygenOS 16.0.9.400 | Uses 6.12.52-android16-5 |
| WildKernels v2.2.0-r4 | Lists OnePlus 15 with Android 16 kernel 6.12.23 | Not an exact match for the tested firmware |
| ColorOS report | Earlier 6.12.23 package reportedly bootlooped on 16.0.9.400 | Confirms that blind flashing carries a real risk |
| Exact KernelSU and SUSFS image | Not publicly verified across every 16.0.9.400 variant | Wait for model-specific testing and recovery notes |
WildKernels v2.2.0-r4 still identifies its OnePlus 15 Android 16 build with Linux kernel 6.12.23.
Why the kernel number matters
KernelSU places root control in the kernel. That makes the exact kernel far more important than it is for a normal Android app. A build may boot only when its configuration, drivers and Kernel Module Interface match the phone.
The tested 6.12.52-android16-5 string includes three useful clues. It identifies the Linux branch, the patch level and the Android kernel generation. You should compare the complete string. Do not match only “6.12” or “Android 16”.
Model and region matter too. OxygenOS and ColorOS packages with the same visible release number may not contain identical boot components. CPH2749, OP611FL1 and another regional identifier must not be treated as interchangeable without maintainer confirmation.
The practical rule is simple: a OnePlus 15 16.0.9.400 KernelSU SUSFS image should name the exact model, firmware and expected kernel. It should also include a checksum and tested recovery path.
KernelSU, SUSFS and the control module are separate layers
KernelSU’s official installation guide explains its kernel-based design. KernelSU provides root access and manages modules. It does not automatically include every SUSFS feature.
SUSFS, or SUS File System, changes kernel-level filesystem behaviour. The kernel must be compiled or patched with SUSFS support. A companion module may expose settings and apply hide rules. That module cannot add missing kernel support by itself.
If a module interface says “SusFS not supported”, stop there. Reinstalling the same module will not fix an incompatible kernel. Some builds integrate both the kernel patch and their preferred control layer, so follow that build’s documentation rather than mixing packages.
SUSFS is not a Magisk module in the usual sense. Installing its userspace files under Magisk does not create the required kernel feature. KernelSU Next and SukiSU Ultra are common SUSFS-capable routes, but support still depends on the exact build.
Risks to understand before unlocking
Android’s official bootloader documentation states that unlocking triggers a factory data reset. Copy photos, messages, authenticator recovery codes and app data elsewhere first. Check that the backup can be opened before proceeding.
- Boot failure: An incompatible kernel or boot image can leave the phone looping at the logo.
- Update failure: Modified boot components can block or complicate OxygenOS over-the-air updates.
- App checks: Banking, work and media apps may detect an unlocked or modified device.
- Play Integrity: Results can change after an app, firmware or server-side update.
- Security: Root gives approved processes deep access. A malicious root module can read or alter sensitive data.
- Warranty and support: Policies vary by seller and region. Restore requirements may apply.
No KernelSU, SUSFS or module setup can be promised to pass a specific bank’s checks. Test the apps you rely on. Keep another way to reach money, travel tickets and two-factor codes.
Image caption: A bootloader warning is a security state notice, not a harmless cosmetic message.
How to check and install a verified OnePlus 15 build
Use this workflow only after a maintainer publishes an image that explicitly supports your exact OnePlus 15 variant and firmware.
- Back up the phone. Save personal files and account recovery details to a separate device or encrypted drive.
- Record the identity. Note the model, region, full OxygenOS or ColorOS build number and active slot.
- Read the running kernel. Enable USB debugging, connect Android Debug Bridge and run adb shell uname -r.
- Check the package. Confirm that its release notes name 16.0.9.400, your model and the expected kernel.
- Verify the download. Compare its SHA-256 checksum with the maintainer’s published value.
- Prepare stock recovery files. Keep matching stock boot, init_boot and other files specified by the maintainer.
- Unlock when ready. Use the supported OnePlus bootloader process and accept that it wipes all user data.
- Follow the package instructions exactly. Flash only the documented partition; do not guess between boot and init_boot.
- Boot and verify. Check the kernel string, KernelSU manager state, mobile data, Wi-Fi, cameras and calls.
- Add SUSFS cautiously. Install only the control module specified by the kernel maintainer, then reboot and test.
Prerequisites and files
You need current Android platform tools, a sound USB cable and enough charge for recovery work. The computer must detect the phone in both Android Debug Bridge and fastboot modes. Install the correct driver on Windows before unlocking.
You also need an untouched firmware package matching the phone’s current region and build. Do not rely on a random boot image labelled only “OnePlus 15”. Keep a copy outside the phone because internal storage is erased during unlocking.
Check the appended “Modules, apps & files to try” section when one is supplied. Use a listed file only if its notes explicitly cover your exact build. At present, the older 6.12.23 package is not a safe substitute for the tested 6.12.52 firmware.
If you are new to Android modification, read our guide to de-Googling an Android phone before deciding whether root is necessary. Many privacy gains do not require kernel changes.
Verification after the first boot
A successful home screen is only the first check. Open the KernelSU manager and confirm that the installed kernel is recognised. Then run adb shell uname -r again. The result should match the release notes.
Test calls, SMS, Wi-Fi, Bluetooth, cameras, fingerprint unlock and charging. Reboot at least twice. A setup that works once but fails on the next slot or restart is not stable.
Check Play Integrity only as a diagnostic. Google documents the changing verdict model in its Play Integrity overview. A passing result today does not guarantee future results or access to any named app.
If the device bootloops, stop repeated experiments. Use the maintainer’s recovery procedure or restore matching stock images. Never relock the bootloader while modified or mismatched images remain installed.
A reported ColorOS 16.0.9.400 test of the earlier OnePlus 15 6.12.23 package ended in a bootloop.
How to configure SUSFS without creating new faults
Only configure SUSFS after the phone is stable and the manager confirms kernel support. Change one setting at a time. Reboot and test after each change so a fault has a clear cause.
Common KernelSU Next guidance disables SUSFS logging, removes “KSU” from a spoofed kernel string and enables spoofing on boot. Some interfaces call the final apply action “make it sus”. Names can change between releases, so use the instructions shipped with your build.
In Custom SUSFS Settings, community users often leave defaults in place and disable “hide ReVanced”. Do not copy a large hide list from another ROM. Paths differ across OxygenOS, ColorOS and custom ROMs.
The usual custom path file is /data/adb/susfs4ksu/sus_path.txt. Adding a LineageOS overlay idmap path has caused a horizontal display fault in reported setups. That path has no clear place in a stock OnePlus configuration.
Image caption: Change SUSFS options one at a time so any boot or display fault can be traced and reversed.
Modules and combinations to avoid
More hiding modules do not always produce better results. Overlapping tools can modify the same mounts, properties or process state. The outcome may be instability or a more unusual device profile.
- Do not add Shamiko merely because a Magisk guide recommends it. SUSFS is normally the hiding layer in a KernelSU setup.
- Do not install Integrity Box by default. Reported releases have added custom-ROM paths aggressively and have conflicted with SUSFS configurations.
- Do not combine KernelSU forks or managers unless the kernel maintainer requires it.
- Do not import another user’s sus_path.txt without checking every path.
- Do not assume a failed app needs another concealment module. The app may use remote attestation or its own checks.
The best baseline has the fewest moving parts: one verified kernel, its matching manager and the documented SUSFS control layer.
What to do while an exact build is unavailable
Remain on the stock kernel if the OnePlus 15 is your main phone. This keeps the expected boot chain and makes official updates simpler. It is also the best choice when access to work or banking apps matters more than root.
Experienced users can monitor release notes for all four match points: model identifier, region, 16.0.9.400 and 6.12.52-android16-5. A maintainer should state whether the image was tested on real hardware. Build success alone is not device testing.
You may build a kernel yourself if you already understand Android kernel compilation, boot image formats and recovery. That is not a beginner workaround. You must use the matching source, configuration and toolchain, then preserve the required device components.
A request for OnePlus 15 16.0.9.400 KernelSU SUSFS support is safest when it includes the complete kernel string and device identifier. Do not share serial numbers, IMEI values or account data in public support channels.
Frequently asked questions
Does KernelSU support the OnePlus 15 on Android 16?
KernelSU supports the relevant Android 16 and Linux 6.12 architecture in principle. Support for the platform is not proof that a particular flash image supports your phone. The image must match the OnePlus 15 variant, firmware, kernel and partition layout.
Can I flash the WildKernels 6.12.23 package on 16.0.9.400?
It is not recommended. A tested OxygenOS 16.0.9.400 phone uses 6.12.52-android16-5, and a ColorOS user reported a bootloop with the earlier 6.12.23 package. Wait for explicit maintainer confirmation or an updated build.
Does SUSFS work without KernelSU?
SUSFS needs compatible kernel changes. Its common control module is designed for KernelSU-based setups. Installing only the module cannot add SUSFS to an unpatched kernel, and SUSFS should not be treated as a normal Magisk hiding module.
Will KernelSU and SUSFS make every banking app work?
No. Apps can inspect boot state, root traces, device properties and remote integrity verdicts. Their checks can change without notice. No guide can promise that OnePlus 15 16.0.9.400 KernelSU SUSFS will pass a specific bank’s detection.
Can I install an OTA update after rooting?
Possibly, but do not assume it is safe. An update can replace boot components and change the kernel version. Restore the required stock state, follow the kernel maintainer’s update process and wait for a compatible root build before flashing again.
Can I relock the bootloader after installing KernelSU?
Do not relock while modified images are installed. Verified Boot may reject them and leave the phone unable to start. Relock only after restoring the complete matching stock firmware and confirming that every required partition is genuine.
Bottom line
The OnePlus 15 16.0.9.400 KernelSU SUSFS stack is technically plausible, but no public image is verified for every current variant. The tested firmware’s 6.12.52 kernel does not match the public 6.12.23 package. That mismatch, plus the reported bootloop, makes waiting the sound choice.
Back up first, keep stock recovery files and never flash by phone name alone. When a release explicitly matches your model, region, firmware and kernel, verify its checksum and follow its named partition instructions. Until then, stock 16.0.9.400 is safer than an unverified kernel.
PrivacyPortal sells ready-to-use, de-Googled GrapheneOS Pixels — hardened, kept updated, and shipped with our encrypted Graphite messenger. Browse privacy phones →
