Hybrid Mount is a KernelSU and APatch meta-module that scans installed modules at boot and routes their files through OverlayFS, Magic Mount, its own VFS backend, or an ignore rule.
One Plan, Multiple Mount Backends
Choose a global backend, then override it for individual modules or specific paths without modifying their source directories.
OverlayFS
Provides tmpfs or ext4 staging. KernelSU uses its official ioctl for ext4 sysfs hiding, while APatch can use the packaged compatibility LKM.
Magic Mount
Handles files, directories, symbolic links, .replace markers, and whiteout behavior as a conventional systemless mount backend.
Hybrid VFS
Sends injection rules to the project's own hybridmount kernel subsystem. It is not a real mount and does not interoperate with NoMount.
Rule Priority and Configuration
Routing priority is path rule, then module default, then global default. The persistent configuration is stored at /data/adb/hybrid-mount/config.toml, upgrades preserve it, and changes take effect after reboot.
A single file cannot be assigned to multiple backends. File-type conflicts, incompatible .replace rules, or an unavailable strict VFS provider cause planning to fail instead of applying an ambiguous mount set.
Installation
- Read the upstream usage notice and keep a known-good boot image or module-disable method available.
- Download the release ZIP from the page controls and install it with KernelSU or APatch.
- On the first installation, use the volume keys to choose the default backend; volume up selects OverlayFS and volume down selects Magic Mount.
- Reboot, open the WebUI, and verify the mount plan before adding per-module or per-path rules.
- After configuration changes, reboot again and inspect the module status or run the included VFS diagnostic when that backend is selected.