Automated AnyKernel3 builds for dozens of OnePlus models — with SukiSU root and NoMount hookless VFS redirection baked in.
Based on WildKernels/OnePlus_KernelSU_SUSFS
Warning
A custom kernel can disable hardware key-attestation, so Google Wallet tap-to-pay, Play Integrity STRONG, and some banking apps may stop working. Unlocking the bootloader wipes your data. Back up your stock boot.img first. Flash at your own risk.
Every release contains two things. Flash the kernel first, then add NoMount Suite on top of it.
| 1️⃣ The kernel — built here | 2️⃣ NoMount Suite — the add-on | |
|---|---|---|
| What it is | AnyKernel3 ZIP (AK3_<device>_…zip) with SukiSU root and CONFIG_NOMOUNT=y compiled in |
00_NoMount-Module-vX.Y.Z.zip — the metamodule that switches NoMount on |
| Where it comes from | This repo's GitHub Actions — one ZIP per device | The separate NoMount Suite — attached to each release as an add-on (sorted to the top of the Assets list) |
| How you install it | Flash with Kernel Flasher or SukiSU Manager | SukiSU Manager → Modules → Install from storage |
| Get it now | ⬇️ Latest release | ⬇️ Latest release — it's at the top of the Assets list |
Important
The kernel on its own does nothing visible. NoMount is compiled in but stays dormant until the NoMount Suite module activates it. NoMount Suite is the part that carries your injection rules, the WebUI, and the spoofing — think of it like a Magisk/KSU module. You need both.
Most hiding solutions mount something — an overlayfs or bind mount — to swap files in. Every mount is a line in /proc/mounts and an st_dev mismatch a detector can read.
NoMount serves your modules with zero mounts. It's a hookless, per-inode VFS redirection living inside the kernel:
- 🚫 No overlay / bind mounts — there's nothing in the mount table to find.
- 🎯 Per-app, per-file — redirect only the files you choose, only for the UIDs you choose.
- 🧼 No mount-hiding cat-and-mouse — you can't be caught hiding a mount that never existed.
- 🖥️ WebUI-driven — injection rules, per-app hiding and health checks, all from your manager.
![]() |
![]() |
![]() |
![]() |
![]() |
| Status zero mounts, live counts |
Modules what is served, and how |
Rules per-module rule breakdown |
Check one diagnostic, plain verdicts |
Duck Detector 0 danger, 0 warning |
Tap a screenshot for the full-size view.
- SukiSU Ultra — kernel-level root.
- NoMount — hookless VFS redirection; modules are served with no mount at all.
- WireGuard — modern VPN built into the kernel.
- BBR & ECN — TCP / network optimizations.
- sched_ext — extensible scheduler framework (supported kernels).
One build fans out to dozens of OnePlus models across Android 13–16 and kernel 5.10–6.12. See the latest release for the full, per-device list — or browse:
configs/
Prerequisites: unlocked bootloader · a backed-up stock boot.img · Kernel Flasher installed.
- Download the latest release — grab both:
- the kernel ZIP matching your exact device / OS / kernel base, and
- the
00_NoMount-Module-vX.Y.Z.zipadd-on (top of the Assets list).
- Flash the kernel ZIP with Kernel Flasher (or SukiSU Manager).
- Install the SukiSU Manager APK — use the version shown as
SukiSU Versionin the release notes. - 🧩 Add NoMount Suite: SukiSU Manager → Modules → Install from storage → select
00_NoMount-Module-…zip.Already have a metamodule? Remove it and reboot first — only one metamodule can be active at a time.
- Reboot.
- Open SukiSU Manager → NoMount Suite → Open — the WebUI should show Active with your rules.
Tip
Safety net: if the phone fails to boot 3 times in a row, NoMount auto-disables itself so you can get back in and recover. Keep your stock boot.img handy either way.
- Update — re-flash the kernel ZIP and NoMount Suite together (keep them a matched set).
- After an OTA — the system update restores the stock kernel; just re-flash the release.
- Remove — delete NoMount Suite in SukiSU Manager and reboot, then flash a stock boot image (or take an OTA) to drop the custom kernel.
Do I really need the module? Yes. The kernel ships NoMount dormant; NoMount Suite activates it. No Suite → no hiding.
Where does the module come from? It's a separate add-on, maintained in the NoMount Suite and attached to each release as 00_NoMount-Module-vX.Y.Z.zip (named to sort to the top of the Assets).
Can I keep my current kernel and just flash the module? No — NoMount must be compiled into the kernel (CONFIG_NOMOUNT=y). Use the kernel from this release.
Will it pass Play Integrity / my bank? NoMount removes the mount signal. It cannot restore hardware key-attestation, which a custom kernel may break (STRONG / Wallet). Always test with your own apps.
Via GitHub Actions:
Actions → Build and Release OnePlus Kernels → Run workflow
Root option:
[{"type":"SUKISU","hash":"main"}]First run: enable Force toolchain sync before build (auto-on for releases) — required once to populate the toolchain cache.
- SukiSU Ultra · SukiSU Manager releases
- NoMount Suite — the hiding add-on
- Kernel Flasher
- Releases
Any and all donations are appreciated!
- PayPal: paypal.me/fatalcoder524
- DM on Telegram for UPI donations!
- NoMount Suite & all contributors — NoMount development 🙌 (built on maxsteeel/nomount)
- SukiSU Ultra — the root solution
- AnyKernel3 by osm0sis and contributors
- WildKernels/OnePlus_KernelSU_SUSFS — the excellent OnePlus build framework this is forked from
- OnePlusOSS — kernel source
- Community testers and contributors
GPL-2.0 — the same license as the Linux kernel this builds.
Kernel source comes from OnePlusOSS (GPL-2.0); the build framework is forked from WildKernels/OnePlus_KernelSU_SUSFS. The NoMount Suite add-on is a separate project — see NoMount Suite for its own license.




