NoHello by MhmRdd is a Zygisk module that hides root and Zygisk from the apps you choose. It unmounts root-related mounts before the app starts, and you can control which mounts count through its own rule file.
Requirements
- A Zygisk provider: Magisk's built-in Zygisk, Zygisk Next, or ReZygisk.
- The boot script disables the module if your version is too old. The minimums are Magisk 27005, Zygisk Next 497 and ReZygisk 361. It also disables itself if Zygisk Next and ReZygisk are both enabled.
- Install from your root manager app. The installer refuses to run from recovery, or on KernelSU if Magisk is also present.
- Use the release zip. The developer says debug builds are only for bug reports.
The latest release is 0.0.7, from May 2025.
Setup for your root manager
| Root manager | What to do |
|---|---|
| KernelSU and KernelSU Next | Install Zygisk Next or ReZygisk. Enable unmount for the target app in the manager. Disable the manager's "Umount modules" setting if it has one. Disable Enforce DenyList in Zygisk Next or ReZygisk. |
| APatch | Install Zygisk Next or ReZygisk. Enable unmount for the target app. Disable Enforce DenyList in Zygisk Next or ReZygisk. |
| Magisk | Optionally update to 28.0 or newer. Turn on Zygisk, or preferably install Zygisk Next or ReZygisk. Turn off Enforce DenyList everywhere. Add the target app to the deny list. |
Mount rules
Since 0.0.5, rules in /data/adb/nohello/umount decide which mounts get unmounted. Each rule uses these keywords with values in braces:
| Keyword | Matches | Wildcards |
|---|---|---|
root | Root of the mount in /proc/self/mountinfo | Yes |
point | Mount point path | Only at the start or end |
fs | Exact filesystem type, such as ext4 or erofs | No |
source | Source device or file | Yes |
For example, this matches all tmpfs mounts under /data/adb:
fs { "tmpfs" } point { "/data/adb/*" }Whitelist mode
The default is blacklist mode. Create an empty file at /data/adb/nohello/whitelist to switch to whitelist mode.
The README warns that whitelist mode with mount rules can cause severe overheating and slowdowns, because rules are checked every time a process starts. To check them once per boot instead, also create an empty file at /data/adb/nohello/umount_persist.
What else it does at boot
service.sh also uses resetprop to set bootloader and build properties to locked, stock-looking values, including ro.boot.verifiedbootstate, ro.boot.flash.locked, ro.debuggable and ro.build.tags. Uninstalling removes /data/adb/nohello, including your rules.