Zygisk NoHello is a Zygisk module that reduces root and Zygisk visibility for selected applications and can unmount matching filesystem entries through configurable rules.
Targeted Root-Hiding Controls
Coordinates Zygisk process selection, root-manager unmount settings, and optional mount rules for advanced cases.
Process Selection
Uses blacklist behavior by default and can switch to a whitelist model through a marker file.
Mount Rule System
Matches mount roots, points, filesystem types, or sources and unmounts selected entries from target processes.
Release and Debug Builds
Upstream recommends the smaller release package for normal use and reserves debug builds for reproducible bug reports.
Root-Framework Setup
| Environment | Required Setup |
|---|---|
| KernelSU / KernelSU Next | Install Zygisk Next or ReZygisk, enable unmount for each target app in the manager, disable the manager's separate “Umount modules” option when present, and turn off Enforce DenyList in the Zygisk provider. |
| APatch | Install Zygisk Next or ReZygisk, enable target-app unmount in APatch, and disable Enforce DenyList in the Zygisk provider. |
| Magisk | Use Magisk 28+ when practical, disable Enforce DenyList, then use built-in Zygisk or an independent provider and add target apps to the denylist unless the selected fork uses a whitelist. |
Do not enable two Zygisk implementations simultaneously. Conflicting denylist enforcement can prevent NoHello from receiving the process state it expects.
Blacklist and Whitelist Modes
The default blacklist workflow applies NoHello to apps selected through the relevant denylist or unmount controls. Creating an empty file at /data/adb/nohello/whitelist switches the logic to whitelist mode.
Whitelist mode changes which processes are evaluated and should be enabled only with a clear package-selection plan. Test application launches, background services, and device temperature after changing modes.
Mount Rule System
Rules are stored in /data/adb/nohello/umount. Each line can match the mount's root, mount point, filesystem fs, or source. The first, second, and fourth fields accept documented wildcard patterns; filesystem type is an exact match.
Rules are independent and case-sensitive. Quote paths containing spaces and escape literal wildcard or brace characters. Begin with the narrowest rule possible to avoid removing a mount required by the target app.