TL;DR: OnePlus 15 16.0.9.400 KernelSU SUSFS compatibility is not verified as of July 2026. WildKernels v2.2.0-r3 supports the OnePlus 15 on Android 16, but the same release bootlooped on ColorOS 16.0.9.400. OxygenOS users should keep the stock kernel and wait for an exact-build success report or corrected release.
By the PrivacyPortal team
Last updated July 2026
The current evidence does not support treating WildKernels KernelSU-Next and SUSFS as safe to install on a OnePlus 15 running OxygenOS 16.0.9.400. Compatibility is being tracked, but there is no confirmed OxygenOS success report for that exact build. A closely related ColorOS 16.0.9.400 report ended in a bootloop. Back up everything before unlocking or flashing: unlocking the bootloader wipes the phone, and an incompatible kernel can leave it unable to boot.
OnePlus 15 16.0.9.400 KernelSU SUSFS status
The practical status is experimental and unconfirmed. WildKernels v2.2.0-r3 includes a OnePlus 15 Android 16 kernel with KernelSU-Next and SUSFS support, but that description alone does not establish compatibility with every OxygenOS or ColorOS maintenance build.
Kernel compatibility depends on more than the Android version. The kernel source, device tree, vendor modules, boot image layout and security changes can differ between firmware releases. A kernel built for an earlier Android 16 release can therefore bootloop on 16.0.9.400 even when the device name and headline Android version match.
On 26 July 2026, WildKernels issue 263 was still collecting evidence for OnePlus 15 compatibility with software version 16.0.9.400.
The relevant public discussion is available in the WildKernels OnePlus 15 compatibility issue. The verified brief contains one exact-numbered ColorOS 16.0.9.400 bootloop report and no successful OxygenOS 16.0.9.400 installation.
Image caption: OnePlus 15 compatibility should be matched by device, region and complete OxygenOS build number rather than Android version alone.
What KernelSU and SUSFS actually do
KernelSU provides root access from the Android kernel rather than injecting Magisk into the normal boot process. KernelSU-Next is a community-developed fork with additional device and kernel support. Its source and current documentation are maintained in the official KernelSU-Next repository.
SUSFS, short for SUS File System, is a kernel patch designed to hide selected filesystem paths, mounts and other root-related traces from applications. The important distinction is that SUSFS is not merely an installable Android module. The running kernel must already contain compatible SUSFS patches.
The SUSFS-FOR-KERNELSU module supplies userspace controls and additional hiding behaviour. Installing that module over an unsupported stock kernel does not add the missing kernel implementation. Its WebUI will normally report SusFS not supported.
WildKernels v2.2.0-r3 contains an Android 16 build for the OnePlus 15, but it is not verified for OxygenOS 16.0.9.400.
This guide does not recommend combining SUSFS with Magisk. Use the root manager and supporting modules specified by the kernel maintainer. Mixing Magisk, KernelSU-Next and overlapping hiding modules can introduce mount conflicts, boot failures and misleading integrity results.
Compatibility decision table
| Evidence available | Risk assessment | Recommended action |
|---|---|---|
| Confirmed success on the exact OnePlus 15 region and OxygenOS 16.0.9.400 build | Lower, but flashing and root risks remain | Follow the maintainer’s documented method and retain exact stock recovery images |
| Release says OnePlus 15 and Android 16, without naming 16.0.9.400 | High | Do not assume compatibility; wait for exact-build evidence |
| Success reported on a different OxygenOS or ColorOS version | High | Treat it as a different firmware target |
| Bootloop reported on the same numbered ColorOS build | Very high | Keep the stock kernel and wait for maintainer investigation |
| No exact stock images or tested recovery route available | Unacceptable | Do not flash |
For OnePlus 15 16.0.9.400 KernelSU SUSFS, the current evidence places the device in the very high risk row. Experienced flashing does not compensate for a kernel and firmware mismatch.
Risks to understand before proceeding
- Data loss: unlocking the bootloader performs a factory reset. Back up photographs, messages, authenticator recovery codes, passkeys and application data first.
- Boot failure: an incompatible kernel may cause a bootloop, crash before Android starts or leave one A/B slot unusable.
- Recovery complications: boot, init_boot, vendor_boot, vbmeta, vbmeta_vendor and vbmeta_system images must come from the exact installed OTA, including its region and version.
- Security: an unlocked bootloader and root increase the consequences of malicious software or physical access. Kernel patches also expand the trusted code running at the highest privilege level.
- Updates: an over-the-air update may fail, replace the modified kernel or boot against incompatible modules. A new OTA needs a newly compatible build.
- Warranty and support: bootloader unlocking or unofficial software may affect repair and warranty handling depending on the seller, region and fault.
- Banking and media applications: Play Integrity, hardware-backed attestation and application-specific checks can detect modification. No root-hiding configuration is guaranteed to work with a particular bank, wallet, game or streaming service.
Readers new to these concepts should start with PrivacyPortal’s Android bootloader unlocking guide and its explanation of KernelSU compared with Magisk before modifying their own device.
How to install KernelSU and SUSFS safely when compatibility is confirmed
The following procedure is deliberately conditional. Do not install WildKernels v2.2.0-r3 on OxygenOS 16.0.9.400 based solely on its OnePlus 15 label. Begin only after the maintainer publishes a corrected build or a reproducible success report confirms the exact device, region and firmware.
Image caption: A safe flashing workspace includes the exact stock firmware images, verified platform tools and a tested USB connection.
- Back up the phone. Copy personal data to a separate device and confirm that the backup opens. Export authentication recovery codes. Bootloader unlocking will erase the OnePlus 15.
- Record the complete software identity. Note the model, sales region, OxygenOS version, active slot and full kernel version. Do not shorten 16.0.9.400 to “Android 16” when checking compatibility.
- Obtain exact stock recovery files. Keep the full OxygenOS 16.0.9.400 package for the same region and extract the required boot-chain images. Images from another region, ColorOS, an earlier OTA or a merely bootable release are not valid substitutes.
- Prepare current Android platform tools. Confirm that ADB and Fastboot recognise the phone reliably before changing anything. Use a stable cable and USB port, and avoid flashing from a computer prone to sleeping or disconnecting.
- Unlock through the supported OnePlus process. Enable OEM unlocking and USB debugging, then follow the current device and regional procedure. The commonly documented Fastboot unlock command may not be accepted on every regional model. Android’s official documentation confirms that bootloader unlocking erases user data.
- Download only the explicitly compatible package. Use the WildKernels package named for the OnePlus 15, Android 16 and OxygenOS 16.0.9.400 or a maintainer-confirmed equivalent. The relevant modules and applications are listed in the appended Modules, apps & files to try section. Check release notes and published hashes.
- Use the release’s documented flashing route. If the package supplies a raw image and explicitly supports temporary booting, test it with the documented Fastboot command before permanent installation. If it supplies a flashable archive, use only the recommended flasher. Horizon Kernel Flasher requires a working, already-rooted Android installation; it is not a substitute for bootloader recovery.
- Verify the first boot before adding modules. Confirm that Android starts, mobile data, Wi-Fi, cameras, fingerprint unlocking and charging work. Open KernelSU-Next Manager and verify that it recognises the installed kernel. Do not install several modules at once.
- Confirm kernel-level SUSFS support. Install the maintainer-specified SUSFS-FOR-KERNELSU userspace module only if the release requires it. Reboot and open its WebUI. Stop if it reports SusFS not supported; repeatedly reinstalling the module cannot patch the running kernel.
- Apply conservative SUSFS settings. Community-tested settings disable SUSFS logging, remove the visible KSU string through kernel-version spoofing, enable spoofing at boot and then apply make it sus. In Custom SUSFS Settings, keep defaults and disable hide revanced unless the maintainer documents another configuration.
- Verify one change at a time. Reboot, check KernelSU-Next and SUSFS status, then test ordinary device functions before testing sensitive applications. A favourable integrity result does not prove that every application will accept the device.
- Plan for the next OTA. Disable or remove incompatible modules and restore the required stock partitions before updating, following the kernel maintainer’s instructions. Do not reuse a 16.0.9.400 kernel after moving to a newer firmware unless that exact combination is supported.
Recovery plan for a bootloop
If the phone bootloops immediately after a kernel flash, stop retrying random images. First attempt the documented bootloader or recovery key combination. If Fastboot remains accessible, restore the exact stock images required by the installation method.
On an A/B device, determine which slot was modified before changing slots or flashing. Blindly mixing partitions between slots can turn a recoverable kernel failure into a broader boot-chain mismatch.
If the failure begins after installing a KernelSU module, use KernelSU safe mode where supported. Disable the newest module first, boot cleanly and re-enable modules individually. Module compatibility must cover the Android version, root manager version and kernel implementation.
Do not add the LineageOS overlay idmap path to /data/adb/susfs4ksu/sus_path.txt. Community reports associate that entry with a horizontal display fault. Integrity Box v6 has also been reported to conflict with recent SUSFS4KSU behaviour, so avoid combining them without release-specific confirmation.
Recovering an A/B Android phone requires partition images from the exact OTA installed on that device; a similar regional or versioned package is not interchangeable.
Image caption: Exact-version stock partitions provide the recovery path after an incompatible kernel or module prevents Android from starting.
How to judge a future compatibility report
A useful report for OnePlus 15 16.0.9.400 KernelSU SUSFS should identify the complete OxygenOS build, region, model, kernel package and installation method. “Works on Android 16” is insufficient.
- Look for a cold boot and at least one subsequent reboot, not merely a successful flash.
- Confirm that the report concerns OxygenOS rather than the similarly numbered ColorOS release.
- Check whether the user started from a stock kernel or another custom kernel.
- Confirm KernelSU-Next Manager status and the SUSFS WebUI result separately.
- Look for testing of radios, cameras, fingerprint unlocking, charging and sleep.
- Prefer maintainer confirmation or multiple reproducible reports over an isolated screenshot.
This evidence standard provides more useful assurance than integrity screenshots. Integrity verdicts can change server-side and do not demonstrate that the kernel is stable.
Frequently asked questions
Does WildKernels v2.2.0-r3 work on OnePlus 15 OxygenOS 16.0.9.400?
There is no verified OxygenOS 16.0.9.400 success report as of 26 July 2026. A user on the same numbered ColorOS release reported a bootloop. Treat v2.2.0-r3 as incompatible until better evidence or a corrected build becomes available.
Can I install the SUSFS module on the stock OnePlus kernel?
Not by itself. SUSFS requires compatible kernel-level patches. The userspace module controls those patches but cannot add them to an unsupported stock kernel. A SusFS not supported message means the required implementation is absent.
Will KernelSU and SUSFS make banking apps work?
They may hide some root-related signals, but they cannot guarantee acceptance by any bank or application. Apps can use Play Integrity, hardware-backed attestation and their own detection systems. Updates can change those checks without notice.
Can I recover by flashing boot images from another OxygenOS version?
No. Use images from the exact firmware version and region installed on the phone. Mixing boot-chain partitions from different OTAs can cause verification errors, lost hardware functionality or a more serious boot failure.
Should I use KernelSU-Next, standard KernelSU or SukiSU Ultra?
Use the implementation explicitly supported by the selected kernel. Root-manager forks are not interchangeable merely because they share KernelSU ancestry. For OxygenOS 16.0.9.400, no option removes the need for an exact compatible kernel.
Is it safe to accept an OxygenOS update after rooting?
Assume that an OTA can replace the kernel, fail verification or make installed modules incompatible. Restore the required stock state, follow the maintainer’s OTA procedure and wait for a kernel confirmed against the new firmware before restoring root.
Bottom line
The OnePlus 15 16.0.9.400 KernelSU SUSFS combination is not ready for routine installation. The responsible choice is to remain on the stock kernel, preserve exact-version recovery files and monitor the WildKernels compatibility issue. Flash only after exact OxygenOS evidence exists, and approach every future OTA as a new compatibility target.
PrivacyPortal sells ready-to-use, de-Googled GrapheneOS Pixels — hardened, kept updated, and shipped with our encrypted Graphite messenger. Browse privacy phones →
