If you have ever rooted your Android device, you probably know how frustrating it is when banking apps or security checks detect root access. Traditional root frameworks rely on bind mounts or OverlayFS to apply system modifications. Unfortunately, these methods leave clear entries in system files like /proc/mounts, making it easy for apps to flag your device.
That is where ZeroMount comes in. Developed by Enginex0, ZeroMount changes how modules load by handling file redirection directly inside the Android kernel without polluting your mount table. In this blog post, we will cover everything you need to know about ZeroMount. You will learn what it is, its key features, system requirements, how to download and install it, how to use its WebUI, troubleshooting tips, and answers to common questions.
Table of Contents
What is ZeroMount?
ZeroMount is an advanced mount orchestration engine designed for rooted Android devices. Unlike standard module managers that create visible mount entries, ZeroMount operates at the Virtual File System (VFS) layer inside the Linux kernel.
When an app asks Android to read a file, ZeroMount intercepts the request at the kernel level using the getname()function. It redirects the file path to your module file before the filesystem even registers the request. Because this process happens inside the kernel VFS layer, no mount entries are created in /proc/mounts or /proc/self/mountinfo. Security detection tools see a completely stock system.
If your device kernel does not support the VFS driver, ZeroMount does not stop working. It automatically falls back to OverlayFS or MagicMount while applying SUSFS stealth layers to hide remaining traces.
Features of ZeroMount
ZeroMount comes packed with features designed for stealth, flexibility, and system stability:
- Kernel-Level VFS Redirection: Intercepts path lookups directly at the kernel level so module files load natively at stock paths without mount entries.
- Three-Tier Strategy Fallback: Automatically cascades from VFS to OverlayFS, and finally to MagicMount if kernel capabilities are missing. You can also override the strategy per module.
- Directory and Context Injection: Ensures modified files appear in standard directory listings (ls and readdir) while carrying proper SELinux security context labels to prevent permission denials.
- SUSFS Integration: Includes built-in support for path hiding, kernel stat (kstat) spoofing, mount hiding, maps hiding, and Android kernel log (AVC) spoofing.
- Property and Build Spoofing: Spoofs build properties like ro.debuggable, boot state, serial numbers, and custom ROM flags using an integrated resetprop tool.
- Process Camouflage: Masks the running ZeroMount process as a benign system thread ([kworker/0:2]) in system process lists.
- Hot Loading and Unloading: Add or remove module VFS rules on the fly through the WebUI without needing to reboot your phone.
- App and Module Exclusions: Exclude specific apps (by UID) from seeing redirected files, or blacklist specific modules from running.
- Multi-Stage Bootloop Guard: Actively monitors boot progress, Zygote stability, and SystemUI health during startup. If a crash loop occurs, it automatically disables itself and reboots safely.
- Built-in WebUI: Offers a full dashboard with dark, light, and AMOLED themes to manage modules, toggles, app exclusions, and settings easily.
- Extra Utilities: Includes custom emoji font injection, optional CPU performance tuning, and root shell access over ADB.
Requirements
Before installing ZeroMount on your phone, make sure your setup meets the following requirements:
- Unlocked Bootloader: Your Android device must have an unlocked bootloader.
- Supported Android Version: Tested and verified on Android 12 through Android 15.
- Supported Root Manager: Works with KernelSU (fully tested with metamodule support), APatch, or Magisk.
- Patched Kernel (Recommended for VFS Mode): To use true mountless redirection, your device needs a custom kernel patched with the ZeroMount driver and SUSFS patches. You can build one or find pre-compiled builds via the Super-Builders Repository. Note that if you use a stock kernel, ZeroMount will still work using OverlayFS or MagicMount fallback modes.
Download
You can obtain the latest official release directly from the developer’s source code repository.
- Visit the official Enginex0 ZeroMount GitHub Repository to check project releases, view source code, or read updates.
- Download the latest zeromount.zip module file from the repository releases section.
How to Install
Installing ZeroMount is straightforward if you follow these steps:
- Flash a Compatible Kernel: Flash a custom kernel that includes ZeroMount and SUSFS patches onto your device.
- Download the Zip: Get the latest release zip of ZeroMount on your phone.
- Flash via Root Manager: Open KernelSU, APatch, or Magisk manager, navigate to the modules section, choose install from storage, and flash the zeromount.zip file.
- Reboot Your Device: Once the installation finishes, reboot your phone to allow the boot pipeline to detect kernel capabilities and configure VFS rules.
- Open the WebUI: After booting up, open your root manager app, find ZeroMount in your module list, and tap the settings icon to open the WebUI.
How to Use ZeroMount
Once ZeroMount is installed, managing your system tweaks becomes simple through its WebUI interface:
- Dashboard: Open the WebUI dashboard to review engine status, view active VFS rules, see detected kernel capabilities, and inspect real-time logs.
- Module Management: Navigate to the Module Manager tab to view installed modules from /data/adb/modules/. You can hot-load or hot-unload modules at runtime without rebooting.
- App Exclusions: Use the App Exclusions tab to search for installed applications and exclude specific apps by UID. Excluded apps will only see untouched stock system files.
- SUSFS Panel: Open the SUSFS tab to toggle path hiding, mount hiding, process map hiding, or kernel build property spoofing according to your preference.
- Settings and Backup: Adjust mount strategy overrides, set bootloop guard sensitivity, or export your configuration backup for easy recovery later.
Credits
ZeroMount is made possible thanks to open-source contributions and inspiration from the Android custom development community:
- Enginex0: Creator and lead developer of ZeroMount, resetprop-rs, and Super-Builders.
- NoMount Project: Inspired the concept of kernel-level VFS path redirection.
- BRENE: Contributed SUSFS automation mechanisms.
- Hybrid Mount Org: Inspired the metamodule architecture concepts.
Troubleshooting
If you encounter issues while using ZeroMount, keep these solutions in mind:
- Device Enters a Bootloop: Hold down both volume keys during startup to activate Volume-Key Safe Mode. Alternatively, ZeroMount’s built-in Bootloop Guard will automatically detect startup crashes, disable the engine, and reboot your device into a working state.
- Recovery Lockout Mode: After a bootloop guard trigger, ZeroMount remains disabled for safety. You must manually re-enable it through the WebUI or command terminal once you fix the conflicting module.
- Mountless VFS Not Active: If the dashboard shows OverlayFS or MagicMount instead of VFS, your installed kernel lacks the required ZeroMount VFS driver patches. Flash a custom kernel compiled with ZeroMount patches to enable full mountless redirection.
- Apps Still Detecting Root: Ensure that SUSFS stealth toggles are enabled in the WebUI and check that app exclusions or property spoofing settings match your target security checks.
FAQs
No. While ZeroMount shares the goal of kernel-level VFS redirection without mount table pollution, it is built from scratch with a completely new architecture. It uses a custom Rust userspace binary, a custom kernel driver, SUSFS integration, a WebUI, and a multi-phase boot pipeline.
Yes, but with limitations. If your kernel does not have the ZeroMount VFS driver, ZeroMount automatically uses OverlayFS or MagicMount as a fallback. However, true mountless redirection requires a kernel compiled with ZeroMount and SUSFS patches.
ZeroMount allows you to inject or remove VFS redirection rules dynamically at runtime. This means you can activate or deactivate module files without needing a full system reboot.
No. ZeroMount features built-in conflict resolution. When multiple modules target the same file path, ZeroMount manages the hierarchy (last-installed takes priority) to ensure system stability.
Conclusion
ZeroMount represents a major leap forward in custom Android module management. By redirecting file paths directly within the kernel VFS layer, it eliminates visible mount entries while keeping your favorite modules fully functional. Combined with SUSFS stealth tools, hot-loading capabilities, and automated bootloop protection, it provides one of the cleanest and safest ways to customize rooted Android devices.
Give ZeroMount a try if you want an invisible root experience. Please leave a comment below if you have any questions, feedback, or experiences to share with the community!
