Revision [806]

This is an old revision of MagiskHideHidingRoot made by didgeridoohan on 2020-03-31 16:32:54.


Hiding root from apps

First, it might pay to check out what others have been discussing about the app you are having trouble with. Take a look at the App resources for links to discussions and workarounds for a few select apps that are known to be troublesome when it comes to hiding root.

If you have apps that you need to hide root from, that detect that your device is rooted even if you can pass SafetyNet, here are a few tips (if you can't pass SafetyNet, see the section about SafetyNet). A good aproach would be to try one thing at a time and see if the app in question stops detecting root. No need to try all tips at once...

Unfortunately, there are apps out there with their own ways of detecting root that may circumvent MagiskHide (also see “More hiding tips”). Magisk is constantly being updated and improved upon though, so it can pay to try again with a new Magisk update.

Hiding the Magisk Manager

This is done by going to the Manager settings and choosing “Hide Magisk Manager”. When this is done, the Manager is repackaged with a random package name and can therefore not be detected by any apps or services looking for com.topjohnwu.magisk. Since v6.1.0 of the Manager, the app name is also changed, by default to "Manager" to circumvent apps and services detecting "Magisk" in the app name, but you can pick your own app name as well to make the app completely anonymous. If you have the app hidden, but it is still called "Magisk Manager", even though you are on app version v6.1.0+, try unhiding it and hiding it again. The name can't be changed when updating from an earlier version than that if it is already hidden.

You can see if your Manager is hidden on the main screen of the app. Under the information about the latest Manager release there will be a package name consisting of a random string. The “Hide Magisk Manager” option will also be changed to "Restore Magisk Manager" in the settings on a hidden Manager.

Unhiding the Magisk Manager

Go to the Manager settings and choose "Restore Magisk Manager".

You can also unhide the Manager by uninstalling the repackaged Manager and manually install the apk. Get it from the (release thread or GitHub)

Can't hide the Magisk Manager

If you're having issues trying to hide (repackage) the Magisk Manager, this is often caused by having the Manager installed as a system app, either by you or the ROM creator. This is a bad idea... But, there might be other reasons as well. See "Can't hide the Magisk Manager" for more info.

USB/ADB debugging

If you haven’t yet, try disabling USB/ADB debugging to see if this helps you use your root detecting app.

OEM Unlocking

If you haven’t yet, try disabling OEM Unlocking to see if this helps you use your root detecting app. Be careful with this option though. There is a chance that it can cause issues.

WARNING 1 On Samsung devices, toggling OEM Unlocking might be enough to lock the bootloader. This might mean you end up with a device that can't boot.
WARNING 2 On some devices (known: Huawei) both OEM Unlock and an unlocked bootloader is necessary for the fastboot flash command to work. This should not be the case on devices that use vanilla Android (Google), or stay close to vanilla Android. Please exercise caution.

Developer options

If you haven’t yet, try disabling Developer options to see if this helps you use your root detecting app.

Samsung Knox

If you have a Samsung device you have likely triggered Knox when rooting your device. This cannot be undone and it cannot be hidden, so if an app is using the Knox fuse to determine if you have been modding your device there is nothing that can be done.

I don't do Samsung, so I do not know how to determine if an app detects Knox or not, except that it might show up in a logcat. If the app works perfectly with Magisk and MagiskHide on a non-Samsung device, but doesn't on a Samsung it's very probable that it's Knox that is causing issues.

Nothing works

If you can't get it working even though you've tried everything, grabbing a logcat when the app detects root might show something (see "Asking for help/reporting bugs"). Save the log and post it in the General support thread, with plenty of details about the issue. Just make sure you've tried everything first.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki