If you've been tinkering with Android for a while, you've probably heard the saying that Rooting your mobile phone is synonymous with total freedomMore control, more customization, and access to features you don't even see out of the box. The problem arises when you happily go to open your banking app, your favorite online game, or a work tool… and suddenly you get a message saying your device is rooted and it blocks access (just like apps like Netflix).
In recent years Google has tightened the screws with SafetyNet and Play IntegrityAnd many developers have incorporated increasingly aggressive systems to detect root access, unlocked bootloaders, or any system modifications. Even so, with the right tools (Magisk, Shamiko, bypass modules, pre-rooted ROMs, and a few other tricks) it's possible to minimize detections and continue using banking apps and games without giving up root access.
Why do banking and gaming apps detect root access?
When you root you get superuser permissions over virtually the entire systemThis allows you to modify files, processes, and settings that are normally protected. That's great for the power user, but for a banking app, a game with anti-cheat, or a corporate tool, it's a potential nightmare.
For this reason, many applications include what is known as integrity controls and unsafe environment detectionThey look for clues such as the presence of the `su` binary, changes to the boot image, frameworks like Xposed or Magisk, files in suspicious locations, and even altered system properties. If they find something unusual, they usually block login, crash, or display an "unsupported device" message.
Google provides its own layer of control through SafetyNet and, more recently, Play IntegrityThese services check if the system matches the expected configuration for that model: locked bootloader, system partition without critical modifications, Google Play certifications, etc. When the verification fails, Google Play may prevent you from downloading certain apps (for example, Netflix) or prevent paid services and apps with strict DRM from functioning properly.
All of this means that many users who have rooted their smartphones find that Key apps for daily life stop workingThese include banking clients, Google Pay and other mobile payment services, digital wallets, enterprise MDM tools, corporate VPNs, and games like Pokémon Go. This explains the surge of interest in hiding root access, temporarily disabling it, or disguising modifications to continue using these apps.
Magisk and the "systemless" root: the basis for hiding modifications
In the current Android ecosystem, Magisk has become the de facto standard for rootingIts main advantage over classic methods based on SuperSU or direct modifications to /system is that it applies a systemless root, meaning it doesn't permanently touch the system partition. Instead, it acts on the boot image, making it easier to revert changes and pass certain checks.
In addition to granting superuser privileges, Magisk includes a module manager that allows expanding the system's functions and load modifications relatively cleanly. For years it also incorporated MagiskHideThis feature is designed to hide root access and other telltale signs from specific apps. Newer versions rely more on Zygisk and external modules (such as Shamiko or SafetyNet/Play Integrity bypass), but the underlying principle remains the same: to allow certain apps to perceive a clean system.
Another great advantage of Magisk is that, by not directly affecting the system partition, In many cases, it allows you to install OTA updates. It's less risky than other methods. It's not foolproof and depends heavily on the manufacturer and the ROM, but it's usually more manageable: after updating, you can patch the boot image again and regain root access without having to format the phone.
However, for all of this to work correctly, it is key starting from the cleanest possible stateIf you're coming from a classic root with SuperSU that has modified /system, or you still have old frameworks like Xposed installed, it's advisable to completely unroot, restore the ROM, or at least remove remnants before switching to Magisk.
Basic installation: bootloader unlocking and Magisk
To reach the point where you can hide root access from banking apps or games, you first need to have the device properly rooted with MagiskThe most common workflow on most Android phones involves a few general steps (which may vary depending on the brand and model):
Firstly, it is usually necessary unlock bootloaderThis involves enabling developer options, allowing OEM unlocking, and using manufacturer tools or fastboot commands to unlock the bootloader. Be aware that this step can erase all your data and, on some devices, leave a permanent mark that certain apps might detect.
Once the bootloader is unlocked, it's time to install MagiskIn many cases, this is done by patching the original boot image with the Magisk app and then flashing the patched boot image using fastboot or manufacturer-specific tools. In others, a custom recovery (such as TWRP) is used to directly flash the Magisk ZIP file.
If you're already on a ROM like Gamma OS or another custom ROM that facilitates rooting, you can save yourself part of the process, but the idea is the same: obtain a stable root based on Magisk that you can manage from their application. From there, you can start thinking about Zygisk, Shamiko, SafetyNet or Play Integrity bypass modules, and deny lists for games and banks.
Configure Zygisk, Shamiko, and bypass modules
In the current situation, with SafetyNet and Play Integrity becoming increasingly demanding, many guides recommend combining Magisk, Zygisk and external modules This helps to better conceal root access from certain sensitive applications. This is especially useful with banking apps that are constantly updated to detect new hiding techniques.
The usual thing to do is to start with Activate Zygisk from Magisk settingsZygisk integrates modules directly into Android's Zygote process, allowing for deeper code injection and the ability to "trick" apps at runtime. Once activated, the device restarts for the changes to take effect.
After that, it is usually installed Shamiko moduleShamiko is very popular for hiding root access from apps that perform aggressive checks. It works in conjunction with Zygisk and usually requires a configured denial list (denylist or SuList, depending on the Magisk version or forks like Magisk Delta) where you add the apps you want to hide root access from (or alternatives like...). SuHide).
In addition to Shamiko, in many cases a SafetyNet or Play Integrity bypass moduleThis modifies certain device or ROM properties to pass Google's integrity tests. In some Magisk forks, these modules come integrated or pre-installed, while in the official version, they must be loaded manually from the module repository or external sources.
In more advanced configurations, some users add modules such as MagiskHide Props Config or Advanced Reset Sensitive Propswhich allow you to adjust system properties (such as ROM fingerprint, device model, etc.) to make it appear as a completely stock device to Google services and some applications.
Hide Magisk itself and use the deny list
One step that many overlook is that some apps, especially banking apps, They do not limit themselves to searching for the binary.Instead, they detect the presence of the Magisk app itself or forks like Magisk Delta. If they find the root manager installed, they assume the device is modified and block access even if you've hidden the binary.
To prevent this, Magisk includes a feature to hide or rename the applicationIn Magisk's settings, there's usually an option like "Hide Magisk application" that lets you change the name, icon, and package identifier. This way, the app stops being called Magisk and starts behaving like any other application with a more discreet name (similar to techniques for... hide apps).
In forks like Magisk DeltaThis approach is combined with more advanced management of the hiding list. Many users comment that, for example, for an app like CaixaBank Sign to work, it's crucial to properly hide the Delta app, restart the phone, and ensure that the SuList or denial list is configured correctlyInterestingly, there are cases where the banking app works even without being explicitly marked in the SuList, as long as the rest of the environment is well camouflaged.
A practical recommendation is not to uninstall the Normal Magisk until the fork (like Delta) is fully operationalSome users install Delta over the original Magisk, configure it, apply patches, and only when everything is working do they get rid of the original app to avoid conflicts and leave only the manager, which has already been hidden under another name.
In any case, after hiding Magisk or Magisk Delta and configuring the deny list, it is advisable clear data and cache of sensitive applications (banking, payments, games) from Settings → Applications to start them as if they were on a new device and repeat their integrity checks from scratch.
Check SafetyNet / Play Integrity and adjust the settings
Once you have Magisk, Zygisk, Shamiko, and the deny list up and running, it's time to verify that the device passes the integrity testsFrom the main screen of Magisk (or some forks) there is usually a button to run the SafetyNet or Play Integrity check and show whether the result is positive or negative.
If everything is set up correctly, you will see that The verification is approved, following good guidelines for Maintain SafetyNetThis doesn't guarantee that all applications worldwide will work, but it greatly increases the likelihood that banks, payment services, and games will adopt the environment.
When the test fails, there are several things to check: the version of Magisk or the fork you useCheck which modules you have installed and if any are outdated, make sure you don't have obsolete frameworks like Xposed still active or particularly intrusive modules (for example, some system-level ad blockers).
It's a good idea, especially if you come from a highly modified environment. having previously performed a complete unrooting with tools like SuperSUFlashing a clean ROM, or at least removing remnants of other rooting methods, is essential. The closer your system is to a stock image with only Magisk on top, the easier it will be to pass SafetyNet or Play Integrity using specific modules.
After each major change (installation or removal of modules, adjustment of properties, etc.), it is recommended reboot the device and run the integrity test again. Only then will you know which specific combination of settings works on your model and ROM.
RootCloak, Hide My Root and other classic tools
Although Magisk dominates the market today, there are still those who turn to classic tools to hide rootEspecially on older devices where modern versions of Magisk and Zygisk don't work well. Among them, RootCloak and Hide My Root stand out, each with its own approach.
RootCloak For a long time, he was one of the xposed modules The most well-known methods for hiding root access. Their approach is not based on modifying the boot image, but on intercept the calls made by applications to detect root. and return "clean" responses. To use it, you had to have Xposed installed, download the module, activate it in the Xposed app, and restart.
RootCloak allowed users to select target applications, similar to Magisk's hiding list. However, its biggest problem at present is compatibility: It only supports up to approximately Android MarshmallowIt is not prepared for the latest system versions or for modern SafetyNet/Play Integrity mechanisms, and the developer himself made it clear that it did not work with services like Android Pay.
For its part, Hide My Root It's an app designed for users looking for something simpler. It could be installed from Google Play (when it was available) and its main function was hide or temporarily uninstall the binary suWhen executed, it requested superuser permissions and offered options to hide, uninstall, or even remove the root management app (e.g., SuperSU), with the possibility of reinstalling it afterwards.
This solution has the advantage of simplicity, but also clear limitations: if the app uses deeper integrity checksOr, if your root method doesn't involve a binary, the classic Hide My Root might not be very helpful. Furthermore, while your root is uninstalled, you lose root access until you restore it.
Temporarily disable or remove root access
There are times when, no matter how much you tinker with Magisk, modules, and hiding lists, Some applications are still determined to detect modificationsIn these cases, it may be more practical to temporarily disable or even remove root access to use them without complicating things so much.
One of the most convenient ways is to use Pre-rooted custom ROMs such as the long-standing CyanogenMod, LineageOS, or some MIUI variants. These ROMs usually integrate root access into the system settings themselves, so you can enable or disable it with a simple toggle.
In ROMs based on CyanogenMod or LineageOS, for example, you just need to go to Settings → About phone and enable developer options Tap the build number several times. Then, in "Developer options", you'll find a setting called something like "Administrative access" or "Root access", which lets you choose between several modes: disabled, ADB only, apps and ADB, etc.
If you select "Disabled"The system acts as if root access had never been used, and applications should no longer be able to request or detect superuser privileges. When you want to use rooted tools again, simply reactivate access from that same option without needing to flash anything extra.
This method is quite clean because It doesn't hide root access, it simply disables it.However, it's only available on ROMs that integrate this functionality; if you're using a stock ROM without these options, you'll have to resort to Magisk or consider a more thorough unrooting if nothing else works.
Complete derooting: when nothing works anymore
There comes a point, especially with very strict banking or corporate appsIn this case, hiding techniques are no longer sufficient. If you absolutely need these apps to work and aren't willing to take any risks, the most effective solution is to completely unroot the device.
If you rooted your device using SuperSU, you'll find an option in its settings tab to “Complete unrooting”This function attempts to revert all changes made to the system, remove the su binary, and restore the original files. Read the instructions carefully because, in some cases, it will ask if you want to keep the modified recovery or not.
Alternatively Re-flash the official ROM or a clean system image without rootThis can be done using a custom recovery or the manufacturer's tools on your computer (Odin for Samsung, fastboot for many others, proprietary utilities for Chinese brands, etc.). This usually ensures that integrity checks, both from Google and banks, will stop detecting deep modifications.
Once you've returned to a completely stock state, you can always decide later whether to root it again. The difference is that, with the experience you've gained, you'll be able to... Choose a modern Magisk-based method from the start and plan your hiding settings (Zygisk, Shamiko, etc.) before installing all your sensitive apps.
Living with sensitive apps: banking, payments, games, and more
In practice, what you want is that Ensure your critical apps function properly on a daily basis Even if you maintain root access for all other uses. This almost always includes banks, payment services, some games with anti-cheat protection, and tools your company may require to access internal resources.
The most logical approach is to make a list of priority applicationsFor example, your bank's primary client, signature or confirmation apps (like CaixaBank Sign), Google Pay or other wallets, online games that use anti-cheat systems, and enterprise applications with MDM. With that list in hand, you log into Magisk or your fork and make sure they are all added to the deny list or SuList.
Next, it is recommended that hide the Magisk app itselfMake sure you pass the SafetyNet/Play Integrity test and that you don't have any conspicuous modules loaded while using those apps (for example, cheat modules in games, Xposed with aggressive hooks, etc.). The cleaner the environment appears, the less likely the alarm will be triggered.
In the specific case of banking apps like CaixaBank SignThere are reports from users who have managed to get them working on rooted devices simply by ensuring that the Magisk Delta app is properly hidden, the device has been restarted after the changes, and the app is (or isn't, depending on the case) correctly managed by SuList. The key is to try different combinations while always maintaining the basic structure: Zygisk + hiding module + integrity bypass.
It's important to remember that the developers of these applications frequently update their detection systems, so something that works today might stop working after an update. That's why it's useful. Follow the community for your device and Magisk to see which modules and configurations are working best at any given time.
Data management, backups and recovery
A fairly common consequence of all these experiments is that, at some point, you need to delete data or reinstall apps that store important local information: banking settings, sessions, downloaded files, etc. Before you start messing with root, hiding, and ROMs, it's a good idea to stop for a second and think about backups.
The wisest course of action is to use reliable backup toolsFrom built-in Android features and each manufacturer's cloud solutions, to apps or desktop programs that allow exporting application data, contacts, call history, and other critical elements.
If you've already deleted something by accident, you can still try. recover data with scanning software From a computer. These types of programs usually scan the phone's internal memory for deleted files that haven't been overwritten yet. They don't always work, but in some cases they can recover settings or files associated with your apps.
In any case, every time you go to uninstall modules, change root method, or flash a ROMIt's a good idea to assume that something might go wrong and that you could have to restore your phone from scratch. Making a backup beforehand will save you a lot of trouble if, in the process of trying to hide the root access, you end up losing access to your data.
Ultimately, living with a rooted phone and apps that don't play well with root access is a matter of balance and patienceBetween Magisk, Zygisk, Shamiko, bypass modules, classic tools like RootCloak or Hide My Root, and the option to disable or remove root when there is no other way out, you have a range of possibilities to adapt the system to your needs without completely giving up the security and compatibility that the most sensitive applications demand.
