Automated AnyKernel3 builds for dozens of OnePlus models, with BakaSU 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.
| The kernel, built here | NoMount Suite, the add-on | |
|---|---|---|
| What it is | AnyKernel3 ZIP (AK3_<device>_…zip) with BakaSU 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 BakaSU Manager | BakaSU 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.
Every kernel ZIP also carries susfs_guard_lkm.ko, built against that exact kernel and
inert unless something loads it. Flashing the kernel drops it into Download; installing
00_Loader-Module-vX.Y.zip (also in the Assets) picks it up and loads it at every boot.
Skip it and nothing changes. One module per kernel: by design it will not load on a build it was not compiled against.
Most hiding solutions mount something, an overlayfs or a 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 no mounts at all. It's a hookless, per-inode VFS redirection inside the kernel:
- Nothing in the mount table. No overlay, no bind mounts.
- Per-app, per-file. Redirect only the files you pick, only for the UIDs you pick.
- Nothing to catch. You can't be caught hiding a mount that never existed.
- Driven from the WebUI. Rules, per-app hiding and health checks, inside your manager.
 |
 |
 |
 |
 |
| Status | Hiding | Rules | Checks | Duck Detector |
Tap a screenshot to enlarge.
- BakaSU, kernel-level root.
- WireGuard, built into the kernel.
- BBR and ECN for TCP.
- sched_ext, the extensible scheduler framework, on kernels that carry it.
One build fans out to dozens of OnePlus models, Android 13 to 16, kernel 5.10 to 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 and 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 BakaSU Manager).
- Install the BakaSU Manager APK. Use the version shown as
BakaSU Versionin the release notes. - Add NoMount Suite: BakaSU 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 BakaSU Manager → NoMount Suite → Open. The WebUI should show Active with your rules.
Safety net: three boots in a row that never finish and NoMount disables itself, so the
fourth comes up without it. 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 BakaSU 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 and the 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), so use the kernel from this release.
Will it pass Play Integrity or my bank? NoMount removes the mount signal. It cannot restore hardware key-attestation, which a custom kernel may break (STRONG, Wallet). Test with your own apps.
Via GitHub Actions:
Actions → Build and Release OnePlus Kernels → Run workflow
Root option:
[{"type":"BAKASU","hash":"main"}]First run: enable Force toolchain sync before build (auto-on for releases). Required once to populate the toolchain cache.
- BakaSU · BakaSU Manager releases
- NoMount Suite — the hiding add-on
- Kernel Flasher
- Releases
Appreciated, never expected.
- PayPal: paypal.me/fatalcoder524
- DM on Telegram for UPI donations!
- NoMount Suite & all contributors — NoMount development 🙌 (built on maxsteeel/nomount)
- BakaSU — the root solution
- AnyKernel3 by osm0sis and contributors
- WildKernels/OnePlus_KernelSU_SUSFS — the excellent OnePlus build framework this is forked from
- inforcqb/susfs4ksu-lkm — SUSFS as a loadable module, which is what each kernel here carries
- OnePlusOSS — kernel source
- Community testers and contributors
GPL-2.0, the same license as the 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.