Hide root status from sensitive apps to preserve functionality and access restricted features
Hide root status from sensitive apps to preserve functionality and access restricted features
Vote (2 votes)
Program license Free
Developer ŘímanApps
Version 2.1.1
Works under Android
Vote
(2 votes)
Developer
ŘímanApps
Works under
Android
Program license
Free
Version
2.1.1
Pros
- Per-app control over where root should be hidden
- Designed to keep root enabled while masking common root indicators
- Hides several well-known detection targets (such as su, common superuser apps, root-run processes, and adb) for selected apps
Cons
- May not help with apps that perform native-level root detection
- Does not directly conceal custom ROM signals
- Does not allow use with Android Pay
RootCloak is an Android module designed to help rooted devices keep using apps that refuse to run when they detect root. Instead of removing root access, it focuses on hiding common root “signals” on a per-app basis so sensitive apps can keep functioning.
This is for people who already use the Xposed Framework on a rooted device and want selective root hiding for specific apps, such as finance/banking, enterprise, or audio and video apps that perform root checks.
What RootCloak does well
RootCloak’s biggest strength is its targeted approach. You choose which installed apps should have root hidden (with support for adding a custom entry), and RootCloak applies multiple tactics to reduce what those apps can “see.” In practice, that can mean masking items commonly used for detection, including the su binary, common superuser apps, processes associated with root, and even indicators like adb.
Because it aims to keep root intact while limiting what a chosen app can detect, RootCloak fits neatly into setups where you want root for some tasks but still need certain restrictive apps to open and behave normally.
How the hiding works (and why it matters)
Rather than tailoring behavior for each app individually, RootCloak relies on hooking core, SDK-level behavior (for example, calls related to executing commands, file access, and querying installed applications). That general strategy can make it feel consistent across many apps, and it avoids the “one-off fix” mindset that often breaks when an app changes its checks.
Limits you should expect
RootCloak is not a universal bypass. Apps that rely on native code for root detection can still spot a rooted environment, since Xposed-based hooking does not operate at the native layer, and certain native checks are outside RootCloak’s reach.
It also does not directly hide the presence of custom ROMs. If an app’s “root detection” is simplistic and overlaps with build-signing clues, you may still benefit, but it is not meant to comprehensively disguise a modified OS environment.
Finally, RootCloak explicitly does not enable Android Pay use.
Overall impression
RootCloak is a focused tool for Xposed users who want app-by-app root concealment without giving up root entirely. When an app’s detection relies on typical, higher-level indicators, RootCloak’s method-based hiding can be a practical fix. If the app checks root through native routines or is more aggressive about custom ROM detection, RootCloak’s design leaves less room to maneuver.
Pros
- Per-app control over where root should be hidden
- Designed to keep root enabled while masking common root indicators
- Hides several well-known detection targets (such as su, common superuser apps, root-run processes, and adb) for selected apps
Cons
- May not help with apps that perform native-level root detection
- Does not directly conceal custom ROM signals
- Does not allow use with Android Pay