AnyRealm — NUKI kernel images with NURFS unified rootfs, plus SUSFS + ZeroMount
One tree, one kernel image, one user space. Desktop and mobile editions. One CI pipeline.
Warning
Super-Builders is in active development. Kernel builds are provided as-is.
Flashing a custom kernel carries inherent risk. You are solely responsible for any outcome — including bootloops, data loss, or bricked devices. Review the patches, understand your device's kernel version, and make sure you know what you're doing before flashing. If in doubt, fork this repo and build the kernel yourself.
No warranty. No liability. Your device, your risk.
Super-Builders is the kernel build pipeline for ZeroMount. It takes a kernel tree, applies the SUSFS + ZeroMount VFS patches, and compiles it across every supported target and KSU variant via GitHub Actions CI.
AnyRealm is the project. NUKI and NURFS are the architecture it is built on:
- NUKI — Native Unified Kernel Image: one kernel, compiled whole from one tree. No separated vendor module set, no KMI to match at boot.
- NURFS — Native Unified Root File System: one user space, integrated natively. No chroot, proot, container, or libc translator.
- bionic and glibc both run, because the kernel is the kernel.
execvedoes not check which libc an ELF interpreter names.
The same architecture ships as two editions:
| Edition | Produces | Tree | Arch |
|---|---|---|---|
| desktop | bootable install ISO for a PC — DarkMatter's rootfs with the Kali NetHunter Pro user space merged in | kernel-zenith, 6.12 |
x86_64 |
| mobile | flashable kernel for the Moto G Stylus 5G 2023 | AR-NUKI-genevn, 5.10.240 |
arm64 |
The desktop edition is the ASUS Vivobook Go 14/15 build; its ISO is the deliverable. Both editions are one kernel and one rootfs — the difference is the arch and the packaging, not the model.
The GKI track below is a separate, genuinely different thing: Google's core-kernel-plus-vendor-modules contract, matched through a frozen KMI. It is supported here for devices that need it, and KERNEL-ANDROID-MAPPING.md explains how the two differ and why the version numbers confuse people. GKI is the reference, not the default.
The kernels built here provide the infrastructure layer — the hiding primitives, VFS hooks, and control interfaces that the ZeroMount userspace module relies on for mountless module loading, root detection evasion, and SUSFS automation.
Super-Builders builds the engine. ZeroMount drives it.
- Path hiding — files and directories vanish from
readdirand path lookups for unprivileged apps - Kstat spoofing — file metadata (inode, device, timestamps, size) returns stock values to
stat/fstat/lstat - Maps hiding —
/proc/PID/maps,/proc/PID/mem, pagemap, andmap_filesentries blanked for flagged inodes - Mount ID spoofing — non-SU processes see fake mount IDs across
mountinfo,fdinfo,statfs - Mount hiding — KSU mount entries filtered from
/proc/PID/mountinfofor non-root processes - Uname spoofing —
uname -r/uname -vreturn stock-looking kernel version strings - Cmdline & bootconfig spoofing —
/proc/cmdlineand/proc/bootconfigshow clean boot state - AVC log suppression — SELinux audit denial messages suppressed from dmesg/logcat
- Kallsyms hiding — SUSFS and ZeroMount kernel symbols hidden from
/proc/kallsyms
- VFS path redirection — intercepts
getname()to redirect file lookups at the VFS layer, zero mount table entries - Directory entry injection — module files appear in
ls/readdirlike stock system files - d_path spoofing —
/proc/PID/fdsymlinks andd_path()return virtual paths - Mmap metadata spoofing —
/proc/PID/mapsdev/ino replaced with stock values for redirected files - SELinux xattr injection — redirected files carry correct SELinux contexts (
system_file,vendor_file, etc.) - statfs spoofing — system partitions report
EROFS_SUPER_MAGICas expected - Write protection — injected files are read-only through virtual paths, preventing source corruption
- Bloom filter — 4096-bit 3-hash pre-check rejects non-matching paths in a few CPU cycles
- ioctl control —
/dev/zeromountmiscdevice with 11 commands for userspace rule management
- Kstat redirect — single supercall maps virtual-path stat to real-path metadata
- Unicode filter — blocks filesystem path attacks using invisible/confusable unicode characters
- AS_FLAGS collision guards —
BUILD_BUG_ONprevents inode flag bit conflicts between SUSFS and ZeroMount
- Inline fast-path — root/system processes skip hiding logic entirely (zero overhead)
- Two-level readdir guard — parent directory flags enable early skip when no hidden children exist
- RCU-protected data structures — all hash tables use Read-Copy-Update for lock-free concurrent reads
- Zygote SID null guard — prevents false-positive process classification during early boot
- UID range fix — all Android app UIDs (10000–19999) correctly recognized
- Memory barriers —
WRITE_ONCE/READ_ONCEon hot-path hook flags for cross-CPU safety - strncpy null-termination — buffer overread prevention across 5+ SUSFS entry points
- EACCES removal — hidden paths return
ENOENT(indistinguishable from nonexistent) instead of leaking SUSFS presence
| Android | Kernel | Sublevels | Variants | Patches | Build |
|---|---|---|---|---|---|
| Android 12 | 5.10 | 107 → 270 | SukiSU, ReSukiSU, KSU-Next, WKSU | ✅ | ✅ All green |
| Android 13 | 5.10 | 107 → 246 | SukiSU, ReSukiSU, KSU-Next, WKSU | ✅ | 🔄 In progress |
| Android 13 | 5.15 | 41 → 194 | SukiSU, ReSukiSU, KSU-Next, WKSU | ✅ | 🔄 In progress |
| Android 14 | 5.15 | 131 → 194 | SukiSU, ReSukiSU, KSU-Next, WKSU | ✅ | 🔄 In progress |
| Android 14 | 6.1 | 25 → 157 | SukiSU, ReSukiSU, KSU-Next, WKSU | ✅ | 🔄 In progress |
| Android 15 | 6.6 | 30 → 118 | SukiSU, ReSukiSU, KSU-Next, WKSU | ✅ | 🔄 In progress |
| Android 16 | 6.12 | 23 → 58 | SukiSU, ReSukiSU, KSU-Next, WKSU | ✅ | 🔄 In progress |
Patch directories. Only
android12-5.10/exists today. The other rows have workflows that resolveandroid<NN>-<ver>and now fail fast instead of substituting a different Android KMI (which is what an oldercasefallback did — an Android 14 + 5.10 device silently got the Android 12 patch set). Creatingandroid13-5.10/is the correct shape should that target be added: the same kernel, a different KMI.
| What | Kernel | Sublevels | Variants | Patches | Build |
|---|---|---|---|---|---|
Google GKI branch android12-5.4 |
5.4.302 | 302 | SukiSU, ReSukiSU | ✅ | ✅ All green |
5.4 is ambiguous, and both readings are correct depending on whose tree you mean. There is no single answer to "is 5.4 GKI?", so don't look for one:
- A vendor's own 5.4 tree (Moto, Samsung, most 5.4 devices in the wild) is pre-GKI and monolithic — vendor and core built as one image, no KMI, no module contract. This is what most people mean by "5.4", and it's why the row was previously labelled Pre-GKI.
- Google's
android12-5.4branch (5.4.302) is GKI 1.0: it carries anandroid/abi_gki_aarch64KMI symbol list. This repo builds this one — the GKI buildersrepo initGoogle's manifest, never a vendor tree.
KernelSU-Next and WKSU are unsupported on either for an unrelated reason: they
need TWA_RESUME, which does not exist before 5.7.
Read
KERNEL-ANDROID-MAPPING.mdbefore changing anything here. The Android release and the kernel version are independent:android12-5.10andandroid13-5.10are both 5.10.270 but different KMIs, not synonyms. The trailing number in GKI shorthand such as5.10-9isKMI_GENERATIONfrombuild.config.common, not a sub-level —5.10-9isandroid12-5.10(GKI 1.0) and there is no5.10-11.
android16-6.12 in the Vivobook profile records where the kernel tree came
from (kernel-zenith is based on Google's android16-6.12), not the OS in the
ISO. The ISO runs DarkMatter Exo 4.7, which is Android-x86 7.1.1. That
kernel is built monolithic for x86_64 with KMI_GENERATION=0 and no GKI module
split, so none of the arm64 KMI machinery above applies to it — the merge of
the Kali user space into DarkMatter's rootfs happens at the filesystem level,
under one kernel, not through a KMI contract.
| Target | Status | Notes |
|---|---|---|
| non-GKI 4.19 | 🔲 Planned | — |
| non-GKI 4.14 | 🔲 Planned | — |
| MKSU workflow | 🔲 Planned | No SUSFS branch exists upstream yet |
| RKSU workflow | 🔲 Planned | No SUSFS integration upstream yet |
| Target | Status | Notes |
|---|---|---|
| USB ADB filter (65_ patches) | ⏸️ Deferred | Patches archived — may revisit later |
Each kernel version directory contains the same three-layer patch system:
android12-5.10/
├── SukiSU-Ultra/patches/
│ ├── 50_enhanced_susfs-android12-5.10.patch # SUSFS hiding infrastructure (~3900 lines)
│ ├── 60_zeromount-android12-5.10.patch # ZeroMount VFS driver (~2200 lines)
│ └── 70_ksu_safety-sukisu-5.10.patch # KSU variant-specific safety fixes
├── KernelSU-Next/patches/
│ ├── 50_enhanced_susfs-android12-5.10.patch # same 50_ — variant-independent
│ ├── 60_zeromount-android12-5.10.patch # same 60_ — variant-independent
│ └── 70_ksu_safety-kernelsu-next-5.10.patch # different 70_ — variant-specific
├── build-helpers/ # sublevel compat scripts
└── defconfig.fragment # kernel config flags
50_ (Enhanced SUSFS) — The core hiding infrastructure. Hooks readdir, namei, stat, proc, namespace, and more. Shared across all KSU variants — same patch, different forks.
60_ (ZeroMount VFS) — The mountless file injection driver. Intercepts getname(), injects directory entries, spoofs d_path, xattrs, and statfs. Also variant-independent.
70_ (KSU Safety) — Small variant-specific patches for each KSU fork. Fixes null-termination, UID ranges, zygote guards, and supercall wiring in the fork's own kernel/ directory.
build-helpers/ — Scripts that handle sublevel-specific compatibility issues across kernel versions. Different sublevels have different API surfaces — these scripts detect and adapt at build time.
defconfig.fragment — Kernel config flags enabling SUSFS, ZeroMount, ZRAM, BBR, and other features.
Application order: 50_ → 70_ → 60_ → build-helpers
| Variant | Fork | 5.4 Support |
|---|---|---|
| SukiSU Ultra | SukiSU-Ultra | ✅ |
| ReSukiSU | ReSukiSU | ✅ |
| KernelSU-Next | KernelSU-Next | 🔲 Planned |
| WKSU | WildKSU | 🔲 Planned |
All four variants share the same 50_ and 60_ kernel patches. The 70_ patch is generated per-variant to address safety issues specific to each fork's codebase.
- Find your kernel version — check
Settings → About Phone → Kernel versionor rununame -r - Download the matching build from Releases for your Android version, kernel sublevel, and preferred KSU variant
- Flash the kernel using your preferred method (fastboot, custom recovery, etc.)
- Install ZeroMount — the userspace module that activates the kernel features
- Reboot and open the ZeroMount WebUI from your KSU manager
Caution
Flashing the wrong kernel version will bootloop your device. Match your exact Android version and kernel sublevel. If you're unsure, don't flash — ask in the Telegram group first.
Every build runs through GitHub Actions CI. Fork this repo and trigger the workflow for your target:
# Dispatch a specific kernel build
gh workflow run kernel-a12-5.10.yml --ref main \
-f ksu_variant=SukiSU \
-f add_susfs=true \
-f add_zeromount=true
# Or use kernel-custom.yml for single-sublevel builds
gh workflow run kernel-custom.yml --ref main \
-f kernel_target="android12-5.10.107 (2022-11)" \
-f ksu_variant=AllThe CI pipeline handles kernel source checkout, patch application, build-helper execution, compilation, and artifact packaging automatically.
$ super-builders --connect
██████╗ ██████╗ ███╗ ██╗███╗ ██╗███████╗ ██████╗████████╗
██╔════╝██╔═══██╗████╗ ██║████╗ ██║██╔════╝██╔════╝╚══██╔══╝
██║ ██║ ██║██╔██╗ ██║██╔██╗ ██║█████╗ ██║ ██║
██║ ██║ ██║██║╚██╗██║██║╚██╗██║██╔══╝ ██║ ██║
╚██████╗╚██████╔╝██║ ╚████║██║ ╚████║███████╗╚██████╗ ██║
╚═════╝ ╚═════╝ ╚═╝ ╚═══╝╚═╝ ╚═══╝╚══════╝ ╚═════╝ ╚═╝
[✓] SIGNAL ──→ t.me/superpowers9
[✓] UPLINK ──→ kernel builds · bug triage · feature drops
[✓] STATUS ──→ OPEN — all operators welcome- ZeroMount — the userspace module that drives these kernels
- SUSFS by simonpunk — the hiding framework these patches are built on
- SukiSU Ultra — SukiSU fork with builtin SUSFS
- ReSukiSU — ReSukiSU fork
- KernelSU-Next — next-gen KernelSU fork
- WildKSU — WildKSU fork
- KernelSU by tiann — the original kernel root framework
- NoMount — the project that inspired the VFS approach
This project is licensed under the GNU General Public License v3.0.
⚡ The kernel infrastructure behind 👻 GHOST mode.