Revision history for MagiskHideHidingRoot


Revision [750]

Last edited on 2019-10-16 06:53:53 by didgeridoohan
Additions:
- Many apps look for the Magisk Manager as a sign of your device being rooted. For this you can use the feature to hide the Manager (repackage it with a random name), //see “Hiding the Magisk Manager” below//. If the app still detects Magisk, first make sure that the hiding of the Manager actually worked and that you haven't ended up with [[https://www.didgeridoohan.com/magisk/ManagerIssues | two managers installed]]. Unfortunately, the way that Android works, it is almost impossible for an app to completely hide from other apps and services without advanced hacks (like Xposed). If an app still can detect Magisk, even if you have it on the Hide list, the Manager is repackaged and everything else from this list of tips is ok, simply try to uninstall the Manager and see if this helps. If that works, you might be out of luck and the only way to fully use the app in question is to regularly uninstall and then reinstall the Magisk Manager... Fortunately, topjohnwu is currently working on a solution that will make it impossible to detect the Manager, but only on Android Pie and above.
Deletions:
- Many apps look for the Magisk Manager as a sign of your device being rooted. For this you can use the feature to hide the Manager (repackage it with a random name), //(see “Hiding the Magisk Manager” below)//. If the app still detects Magisk, first make sure that the hiding of the Manager actually worked and that you haven't ended up with [[https://www.didgeridoohan.com/magisk/ManagerIssues | two managers installed]]. Unfortunately, the way that Android works, it is almost impossible for an app to completely hide from other apps and services without advanced hacks (like Xposed). If an app still can detect Magisk, even if you have it on the Hide list, the Manager is repackaged and everything else from this list of tips is ok, simply try to uninstall the Manager and see if this helps.


Revision [749]

Edited on 2019-10-16 06:51:40 by didgeridoohan
Additions:
- Many apps look for the Magisk Manager as a sign of your device being rooted. For this you can use the feature to hide the Manager (repackage it with a random name), //(see “Hiding the Magisk Manager” below)//. If the app still detects Magisk, first make sure that the hiding of the Manager actually worked and that you haven't ended up with [[https://www.didgeridoohan.com/magisk/ManagerIssues | two managers installed]]. Unfortunately, the way that Android works, it is almost impossible for an app to completely hide from other apps and services without advanced hacks (like Xposed). If an app still can detect Magisk, even if you have it on the Hide list, the Manager is repackaged and everything else from this list of tips is ok, simply try to uninstall the Manager and see if this helps.
Deletions:
- It might be necessary to hide the Manager (repackage it with a random name), since many apps look for this as a sign of rooting //(see “Hiding the Magisk Manager” below)//. Also make sure that the hiding of the Manager actually worked and that you haven't ended up with [[https://www.didgeridoohan.com/magisk/ManagerIssues | two managers installed]].


Revision [747]

Edited on 2019-10-16 06:42:58 by didgeridoohan
Additions:
- There's always a possibility that the ROM you are using have some props that makes it possible for an app or service to decide if your device is "compromised" or not. An example is //persist.sys.root// which can be found on some ROMs (Lineage) and need to be set to 0. Changing props can be done directly in the prop files, by a [[https://topjohnwu.github.io/Magisk/guides.html#boot-scripts | Magisk boot script]] or with the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]].
Deletions:
- Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values (very rare, but has been reported). For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. It can also be done with a [[https://topjohnwu.github.io/Magisk/guides.html#boot-scripts | boot script]] (don't forget to set the proper permissions for the script to execute).


Revision [746]

Edited on 2019-10-16 06:39:10 by didgeridoohan
Additions:
- //From Magisk v19.4 this detection method is no longer possible, but I'll leave the tip in here for those who refuse to update (for whatever reason).// There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 440 /proc/net/unix%% This will prevent the apps that use this method to read the file. The command needs to be run at every boot, so as not to have to do it every time it is very convenient to put the command (without the "su -c" part since it isn't necessary to call su in the boot scripts) in a service.d boot script.
Deletions:
- There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 440 /proc/net/unix%% This will prevent the apps that use this method to read the file. The command needs to be run at every boot, so as not to have to do it every time it is very convenient to put the command (without the "su -c" part since it isn't necessary to call su in the boot scripts) in a service.d boot script.


Revision [738]

Edited on 2019-10-15 15:41:36 by didgeridoohan
Deletions:
@@{{image url="https://img.shields.io/badge/-PayPal-blue.svg" title="" alt="PayPal"}}
Please don't hesitate to [[https://www.paypal.me/didgeridoohan | support the work involved]] in keeping this guide alive.@@
----


Revision [714]

Edited on 2019-09-02 13:19:31 by didgeridoohan
Additions:
==""Passing SafetyNet""==
Deletions:
==""SafetyNet""==


Revision [701]

Edited on 2019-08-04 05:43:24 by didgeridoohan

No Differences

Revision [700]

Edited on 2019-08-02 05:20:39 by didgeridoohan
Additions:
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 [[https://www.didgeridoohan.com/magisk/MagiskHideHelp | 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.
Deletions:
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 [[https://www.didgeridoohan.com/magisk/MagiskHideHelp | 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.


Revision [699]

Edited on 2019-08-02 05:20:02 by didgeridoohan
Additions:
- If none of the above works, try disabling USB debugging, OEM Unlocking, developer options, etc //(see [[MagiskHideBasics | ”Magisk can not hide”]])//. There are also apps that need a little more TLC when trying to hide root from them. Take a look at //[[MagiskHideAppsList | App Resources]]// below. Also keep reading the rest of the guide...
Deletions:
- If none of the above works, try disabling USB debugging, OEM Unlocking, developer options, etc //(see [[MagiskHideBasics | ”Magisk can not hide”]])//. There are also apps that need a little more TLC when trying to hide root from them. Take a look at //App Resources// below. Also keep reading the rest of the guide...


Revision [698]

Edited on 2019-08-02 05:18:51 by didgeridoohan
Additions:
- If none of the above works, try disabling USB debugging, OEM Unlocking, developer options, etc //(see [[MagiskHideBasics | ”Magisk can not hide”]])//. There are also apps that need a little more TLC when trying to hide root from them. Take a look at //App Resources// below. Also keep reading the rest of the guide...
Deletions:
- If none of the above works, try disabling USB debugging, OEM Unlocking, developer options, etc //(see [[MagiskHideBasics | ”Magisk can not hide”]])//. Also keep reading below.


Revision [691]

Edited on 2019-07-30 07:57:29 by didgeridoohan
Additions:
- If you've previously had your device rooted with a different root solution it is possible that there are remnants of that triggering whatever app you're having trouble with. Uninstall any management app you might still have and run [[https://forum.xda-developers.com/member.php?u=4544860 | osm0sis']] [[http://forum.xda-developers.com/showpost.php?p=63615067 | unSU script]] to remove any traces. Magisk should reinstall itself, but if not you can just reinstall.
Deletions:
- If you've previously had your device rooted with a different root solution it is possible that there are remnants of that triggering whatever app you're having trouble with. Uninstall any management app you might still have and run ([[https://forum.xda-developers.com/member.php?u=4544860 | osm0sis']] [[http://forum.xda-developers.com/showpost.php?p=63615067 | unSU script]] to remove any traces. Magisk should reinstall itself, but if not you can just reinstall.


Revision [690]

Edited on 2019-07-28 05:23:46 by didgeridoohan
Additions:
==""SafetyNet""==
- Passing ""SafetyNet"", both CTS profile and basic integrity, is a good start. That way you know that MagiskHide is working and the apps that do use ""SafetyNet"" won't trigger that way. See [[MagiskHideSafetyNet | SafetyNet]] for more details on that.


Revision [689]

Edited on 2019-07-28 01:25:32 by didgeridoohan
Additions:
It might also pay to check out what others have been discussing about the app you are having trouble with. Take a look at the [[MagiskHideAppsList | 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 [[MagiskHideSafetyNet | 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...
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 [[MagiskHideHelp | "Asking for help/reporting bugs"]])//. Save the log and post it in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | General support thread]], with plenty of details about the issue. Just make sure you've tried everything first.
Deletions:
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 [[MagiskHideSafetyNet | 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, don't try all tips at once...
If you can't get it working, grabbing a logcat when the app detects root might show something //(see [[MagiskHideHelp | "Asking for help/reporting bugs"]])//. Save the log and post it in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | General support thread]], with plenty of details about the issue. Just make sure you've tried everything first.


Revision [673]

Edited on 2019-07-24 15:26:36 by didgeridoohan
Additions:
==Magisk Modules==
- Most Magisk modules can be hidden by MagiskHide, but that depends on exactly what the module does. If you can't figure out what is triggering an app, try disabling all modules (could be easiest to do by enabling Core Only Mode in the Manager settings). If the app no longer triggers you can enable your modules one by one until you find the culprit (but remember to disable Core Only Mode first).


Revision [665]

Edited on 2019-07-22 14:30:09 by didgeridoohan
Additions:
@@{{image url="https://img.shields.io/badge/-PayPal-blue.svg" title="" alt="PayPal"}}
Please don't hesitate to [[https://www.paypal.me/didgeridoohan | support the work involved]] in keeping this guide alive.@@
----
@@[[MagiskHide | -- To the top/main article --]]@@
Deletions:
@@[[MagiskHide | -- To the top/main article --]]@@


Revision [651]

Edited on 2019-07-22 02:23:25 by didgeridoohan
Additions:
===**Nothing works**===
If you can't get it working, grabbing a logcat when the app detects root might show something //(see [[MagiskHideHelp | "Asking for help/reporting bugs"]])//. Save the log and post it in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | General support thread]], with plenty of details about the issue. Just make sure you've tried everything first.
Deletions:
If you can't get it working, grabbing a logcat when the app detects root might show something //(see [[MagiskHideHelp | "Asking for help/reporting bugs"]])//. Save the log and post it in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | General support thread]], with plenty of details about the issue.


Revision [650]

Edited on 2019-07-22 02:20:46 by didgeridoohan
Additions:
==Update Android==
- Update your device to a newer Android version. It is not possible to fully prevent detection on devices with Android versions lower than 7.0.


Revision [649]

Edited on 2019-07-21 02:32:32 by didgeridoohan
Additions:
==Old root==
- If you've previously had your device rooted with a different root solution it is possible that there are remnants of that triggering whatever app you're having trouble with. Uninstall any management app you might still have and run ([[https://forum.xda-developers.com/member.php?u=4544860 | osm0sis']] [[http://forum.xda-developers.com/showpost.php?p=63615067 | unSU script]] to remove any traces. Magisk should reinstall itself, but if not you can just reinstall.


Revision [648]

Edited on 2019-07-20 13:44:12 by didgeridoohan
Additions:
- If none of the above works, try disabling USB debugging, OEM Unlocking, developer options, etc //(see [[MagiskHideBasics | ”Magisk can not hide”]])//. Also keep reading below.
Deletions:
- If none of the above works, try disabling USB debugging, developer options, etc //(see [[MagiskHideBasics | ”Magisk can not hide”]])//. Also keep reading below.


Revision [646]

Edited on 2019-07-17 14:33:30 by didgeridoohan
Additions:
===**OEM Unlocking**===
If you haven’t yet, try disabling OEM Unlocking to see if this helps you use your root detecting app.
**WARNING** 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.


Revision [645]

Edited on 2019-07-13 16:34:21 by didgeridoohan
Additions:
- There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 440 /proc/net/unix%% This will prevent the apps that use this method to read the file. The command needs to be run at every boot, so as not to have to do it every time it is very convenient to put the command (without the "su -c" part since it isn't necessary to call su in the boot scripts) in a service.d boot script.
Deletions:
- There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 440 /proc/net/unix%% This will prevent the apps that use this method to read the file. The command needs to be run at every boot, so as not to have to do it every time it is very convenient to put the command (without the "su -c" part since it isn't necessary to call su in the boot scripts) in a service.d boot script. More details on this detection method can be found here: https://github.com/Ingan121/UDSBypass/blob/master/README.md


Revision [641]

Edited on 2019-07-08 01:47:22 by didgeridoohan
Additions:
- It might be necessary to hide the Manager (repackage it with a random name), since many apps look for this as a sign of rooting //(see “Hiding the Magisk Manager” below)//. Also make sure that the hiding of the Manager actually worked and that you haven't ended up with [[https://www.didgeridoohan.com/magisk/ManagerIssues | two managers installed]].
- Make sure MagiskHide works, if you haven't already. Easiest is to make a ""SafetyNet"" test in the Manager. If at least basic integrity passes, MagiskHide works. If it doesn't work, the first thing to test is to toggle MagiskHide off and on again //(also see [[MagiskHideIssues | "Test MagiskHide"]])//.
Deletions:
- Start by making sure MagiskHide works, if you haven't already. Easiest is to make a ""SafetyNet"" test in the Manager. If at least basic integrity passes, MagiskHide works. If it doesn't work, the first thing to test is to toggle MagiskHide off and on again //(also see [[MagiskHideIssues | "Test MagiskHide"]])//.
- It might be necessary to hide the Manager, since many apps look for this as a sign of rooting //(see “Hiding the Magisk Manager” below)//. Also make sure that the hiding of the Manager actually worked and that you haven't ended up with [[https://www.didgeridoohan.com/magisk/ManagerIssues | two managers installed]].


Revision [640]

Edited on 2019-07-02 04:04:22 by didgeridoohan
Additions:
- MagiskHide does not work on apps installed to adoptable/external storage. Any apps you want to hide root from has to be installed to the internal storage.
- There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 440 /proc/net/unix%% This will prevent the apps that use this method to read the file. The command needs to be run at every boot, so as not to have to do it every time it is very convenient to put the command (without the "su -c" part since it isn't necessary to call su in the boot scripts) in a service.d boot script. More details on this detection method can be found here: https://github.com/Ingan121/UDSBypass/blob/master/README.md
Deletions:
- Currently, MagiskHide does not work on apps installed on adoptable/external storage. Any apps you want to hide root from has to be installed to the internal storage.
- There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 440 /proc/net/unix%% This will prevent the apps that use this method to read the file. The command needs to be run at every boot, so as not to have to do it every time it is very convenient to put the command in a service.d boot script. More details on this detection method can be found here: https://github.com/Ingan121/UDSBypass/blob/master/README.md


Revision [639]

Edited on 2019-06-29 10:35:13 by didgeridoohan
Additions:
- There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 440 /proc/net/unix%% This will prevent the apps that use this method to read the file. The command needs to be run at every boot, so as not to have to do it every time it is very convenient to put the command in a service.d boot script. More details on this detection method can be found here: https://github.com/Ingan121/UDSBypass/blob/master/README.md
Deletions:
- There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 440 /proc/net/unix%% This will prevent the apps that use this method to read the file. More details on this detection method can be found here: https://github.com/Ingan121/UDSBypass/blob/master/README.md


Revision [638]

Edited on 2019-06-29 01:29:14 by didgeridoohan
Additions:
- There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 440 /proc/net/unix%% This will prevent the apps that use this method to read the file. More details on this detection method can be found here: https://github.com/Ingan121/UDSBypass/blob/master/README.md
Deletions:
- There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 000 /proc/net/unix%% This will prevent the apps that use this method to read the file. More details on this detection method can be found here: https://github.com/Ingan121/UDSBypass/blob/master/README.md


Revision [637]

Edited on 2019-06-27 14:38:36 by didgeridoohan
Additions:
- It was discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device (see [[https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20 | here]] for an in-depth write-up) . This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. From Magisk v18.0 MagiskHide will fix the leak on any Android 7.0+ devices. Unfortunately, nothing can be done about this on earlier Android versions.
==UDS detection==
- There is a very simple but currently effective detection method that started surfacing recently. It's easily circumvented by simply running the following command in a terminal: %%su -c chmod 000 /proc/net/unix%% This will prevent the apps that use this method to read the file. More details on this detection method can be found here: https://github.com/Ingan121/UDSBypass/blob/master/README.md
Deletions:
- It was discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device (see [[https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20 | here]] for an in-depth write-up) . This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. From Magisk v18.0 MagiskHide will fix the leak on any Android 7.0+ devices. Unfortunately, nothing can be done about this on earlier Android versions..


Revision [636]

Edited on 2019-06-27 14:14:31 by didgeridoohan
Additions:
==Adoptable/external storage==
- Currently, MagiskHide does not work on apps installed on adoptable/external storage. Any apps you want to hide root from has to be installed to the internal storage.
Deletions:
==App name==
- Some apps have started to look for "Magisk" in app names. From Magisk Manager v6.1.0 this is circumvented by renaming the app to "Manager" whenever the app is repackaged with a random package name //(also see "Hiding the Magisk Manager" below)//. If you have updated to Manager v6.1.0+ and the app is still called "Magisk Manager", even though you have it repackaged, unhide the Manager and hide it again.


Revision [630]

Edited on 2019-06-13 01:37:37 by didgeridoohan
Additions:
- Also, if MagiskHide suddenly stops working after an update to Magisk or the Magisk Manager, try toggling MagiskHide off and on again in the Manager settings.


Revision [629]

Edited on 2019-05-30 13:16:53 by didgeridoohan
Additions:
- It might be necessary to hide the Manager, since many apps look for this as a sign of rooting //(see “Hiding the Magisk Manager” below)//. Also make sure that the hiding of the Manager actually worked and that you haven't ended up with [[https://www.didgeridoohan.com/magisk/ManagerIssues | two managers installed]].
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.
Deletions:
- It might be necessary to hide the Manager, since many apps look for this as a sign of rooting //(see “Hiding the Magisk Manager” below)//.
You can see if your Manager is hidden by going to “About” in the Manager and next to the version code there’ll be a random package name rather than com.topjohnwu.magisk. The “Hide Magisk Manager” option will also be changed to "Restore Magisk Manager" in the settings on a hidden Manager.


Revision [619]

Edited on 2019-05-27 03:35:48 by didgeridoohan
Additions:
- Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values (very rare, but has been reported). For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. It can also be done with a [[https://topjohnwu.github.io/Magisk/guides.html#boot-scripts | boot script]] (don't forget to set the proper permissions for the script to execute).
Deletions:
- Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values (very rare, but has been reported). For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. It can also be done with a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]] (don't forget to set the proper permissions for the script to execute).


Revision [611]

Edited on 2019-05-02 03:39:17 by didgeridoohan
Deletions:
==Logging/logd==
- Android logging has to be enabled //(see [[MagiskHideBasics | ”MagiskHide requirements”]])//. If you don't know if you have logging enabled or not, check the Magisk log. If it's empty you might have logging disabled.


Revision [603]

Edited on 2019-03-17 10:16:51 by didgeridoohan
Additions:
- If none of the above works, try disabling USB debugging, developer options, etc //(see [[MagiskHideBasics | ”Magisk can not hide”]])//. Also keep reading below.
Deletions:
- If none of the above works, try disabling USB debugging, developer options, etc //(see [[MagiskHideBasics | ”Magisk can not hide”]])//.


Revision [598]

Edited on 2019-02-24 03:44:32 by didgeridoohan
Additions:
- Make sure that the app in question is selected in the Hide list (Under Magisk Hide in the Manager). But, don't go crazy... Only add those apps that actually detect root. If you add too many unnecessary apps and processes you will very likely experience system instabilities //(also see [[MagiskIssues | "System instabilities"]])//
Deletions:
- Make sure that the app in question is selected in the Hide list (Under Magisk Hide in the Manager). But, don't go crazy... Only add those apps that actually detect root. If you add to many unnecessary apps and processes you will very likely experience system instabilities //(also see [[MagiskIssues | "System instabilities"]])//


Revision [588]

Edited on 2019-02-17 07:12:29 by didgeridoohan
Additions:
- Make sure that the app in question is selected in the Hide list (Under Magisk Hide in the Manager). But, don't go crazy... Only add those apps that actually detect root. If you add to many unnecessary apps and processes you will very likely experience system instabilities //(also see [[MagiskIssues | "System instabilities"]])//
Deletions:
- Make sure that the app in question is selected in the Hide list (Under Magisk Hide in the Manager).


Revision [587]

Edited on 2019-02-17 07:10:19 by didgeridoohan
Additions:
- Also make sure that your device conforms with the basics for MagiskHide to work and take a look at what Magisk can and cannot hide //(also see [[MagiskHideBasics | "Basics"]])//.
Deletions:
- Also make sure that your device conforms with the basics for MagiskHide to work //(also see [[MagiskHideBasics | "Basics"]])//.


Revision [582]

Edited on 2019-02-10 04:48:53 by didgeridoohan
Additions:
There's a corresponding section about hiding root from apps and ""SafetyNet"" in the [[https://topjohnwu.github.io/Magisk | official Magisk documentation]]. That is also very well worth a look.
Deletions:
There's a corresponding section about hiding root from apps and ""SafetyNet"" in the [[https://topjohnwu.github.io/Magisk/tutorials.html#best-practices-for-magiskhide | official Magisk documentation]]. That is also very well worth a look.


Revision [574]

Edited on 2019-02-08 00:24:04 by didgeridoohan
Additions:
===**Samsung Knox**===
If you have a Samsung device you have likely triggered [[https://en.wikipedia.org/wiki/Samsung_Knox | 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 [[https://www.didgeridoohan.com/magisk/MagiskHideHelp | 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.


Revision [561]

Edited on 2019-01-12 00:18:17 by didgeridoohan
Additions:
- It was discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device (see [[https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20 | here]] for an in-depth write-up) . This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. From Magisk v18.0 MagiskHide will fix the leak on any Android 7.0+ devices. Unfortunately, nothing can be done about this on earlier Android versions..
Deletions:
- It was recently discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device (see [[https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20 | here]] for an in-depth write-up) . This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. From Magisk v18.0 MagiskHide will fix the leak on any Android 7.0+ devices. Unfortunately, nothing can be done about this on earlier Android versions..


Revision [560]

Edited on 2019-01-06 13:34:10 by didgeridoohan
Additions:
@@[[MagiskHide | -- To the top/main article --]]@@
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the ""AdAway"" blacklist and apply the hosts file. **Keep in mind that you're disabling part of the apps security.** See [[https://forum.xda-developers.com/apps/magisk/how-to-bypass-lloyds-root-detection-t3837206 | this thread]] for an example.
Deletions:
@@[[MagiskHide | -- To the top/main article --]]@@
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the ""AdAway"" blacklist and apply the hosts file. **Keep in mind that you're disabling part of the apps security.**


Revision [537]

Edited on 2018-12-16 13:12:12 by didgeridoohan
Additions:
- Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values (very rare, but has been reported). For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. It can also be done with a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]] (don't forget to set the proper permissions for the script to execute).
Deletions:
- Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values (very rare, but has been reported). For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. It can also be done with a [[https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12 | boot script]] (don't forget to set the proper permissions for the script to execute).


Revision [535]

Edited on 2018-12-14 22:33:18 by didgeridoohan
Additions:
- It was recently discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device (see [[https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20 | here]] for an in-depth write-up) . This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. From Magisk v18.0 MagiskHide will fix the leak on any Android 7.0+ devices. Unfortunately, nothing can be done about this on earlier Android versions..
Deletions:
- It was recently discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device (see [[https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20 | here]] for an in-depth write-up) . This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. From Magisk v18.0 MagiskHide will fix the leak on any Android 7.0+ devices.


Revision [532]

Edited on 2018-12-11 03:30:48 by didgeridoohan
Additions:
- Make sure you're up to date with the latest Magisk version. Magisk and MagiskHide is constantly being improved upon and there might have been changes that impact the app you're trying to hide root from.
- It might also be worth to try the latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It might have been updated with an improved MagiskHide.
Deletions:
- It might also be a good idea to update, if you're not on the latest Magisk version. Magisk and MagiskHide is constantly being improved upon and there might have been changes that impact the app you're trying to hide root from.
- Lastly, try the latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It might have been updated with an improved MagiskHide.


Revision [531]

Edited on 2018-12-11 03:25:13 by didgeridoohan
Additions:
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 [[MagiskHideSafetyNet | 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, don't try all tips at once...
Deletions:
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 [[MagiskHideSafetyNet | the section about SafetyNet]])//.


Revision [530]

Edited on 2018-12-09 04:35:45 by didgeridoohan
Additions:
- Some apps have started to look for "Magisk" in app names. From Magisk Manager v6.1.0 this is circumvented by renaming the app to "Manager" whenever the app is repackaged with a random package name //(also see "Hiding the Magisk Manager" below)//. If you have updated to Manager v6.1.0+ and the app is still called "Magisk Manager", even though you have it repackaged, unhide the Manager and hide it again.
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 to simply "Manager" to circumvent apps and services detecting "Magisk" in the app name. 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 of the Manager if it is already hidden.
Deletions:
- Some apps have started to look for "Magisk" in app names. From Magisk v18.0 this is circumvented by renaming the app to "Manager" whenever the app is repackaged with a random package name //(also see "Hiding the Magisk Manager" below)//.
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. The app name is also changed to "Manager" to circumvent apps and services detecting "Magisk" in the app name.


Revision [528]

Edited on 2018-12-09 04:22:45 by didgeridoohan
Additions:
- It was recently discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device (see [[https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20 | here]] for an in-depth write-up) . This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. From Magisk v18.0 MagiskHide will fix the leak on any Android 7.0+ devices.
Deletions:
- It was recently discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device (see [[https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20 | here]] for an in-depth write-up) . This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. There's a quick fix though. After the discovery, topjohnwu created an app to detect if your device is affected and to fix it if that is the case. It can be found here: [[https://github.com/topjohnwu/ProcGate/releases/latest | ProcGate]]. In a future update of Magisk, MagiskHide might take care of fixing this bug for us, but until then there's the app.


Revision [527]

Edited on 2018-12-09 04:20:13 by didgeridoohan
Additions:
- Some apps have started to look for "Magisk" in app names. From Magisk v18.0 this is circumvented by renaming the app to "Manager" whenever the app is repackaged with a random package name //(also see "Hiding the Magisk Manager" below)//.
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. The app name is also changed to "Manager" to circumvent apps and services detecting "Magisk" in the app name.
Deletions:
- Some apps have started to look for "Magisk" in app names. If this is the case, hiding/repackaging the Magisk Manager doesn't do anything to hide the Manager. This is easy to test, just uninstall the Magisk Manager and try the app again. There are plans to fix this, but until then you might be able to use something like [[https://play.google.com/store/apps/details?id=com.gmail.heagoo.apkeditor | APK Editor]] to change the Magisk Manager app name. You can also just uninstall the Manager whenever you need to use the app detecting it. The latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge builds]] have a new function that will change the app name when you also hide the Manager. This function will of course be available in the next beta/stable releases.
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.


Revision [524]

Edited on 2018-12-09 04:16:11 by didgeridoohan
Additions:
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the ""AdAway"" blacklist and apply the hosts file. **Keep in mind that you're disabling part of the apps security.**
Deletions:
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the ""AdAway"" blacklist and apply the hosts file. **Keep in mind that you're disabling part of your banks security.**


Revision [509]

Edited on 2018-12-05 09:43:31 by didgeridoohan
Additions:
==Test ""MagiskHide""==
==The Basics==
==The Hide list==
==Hide the Manager==
==Clear data==
==Dependencies==
==Other root apps==
==Logging/logd==
==Update==
==Other stuff==
==App name==
- Some apps have started to look for "Magisk" in app names. If this is the case, hiding/repackaging the Magisk Manager doesn't do anything to hide the Manager. This is easy to test, just uninstall the Magisk Manager and try the app again. There are plans to fix this, but until then you might be able to use something like [[https://play.google.com/store/apps/details?id=com.gmail.heagoo.apkeditor | APK Editor]] to change the Magisk Manager app name. You can also just uninstall the Manager whenever you need to use the app detecting it. The latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge builds]] have a new function that will change the app name when you also hide the Manager. This function will of course be available in the next beta/stable releases.
==File on the internal storage==
==External connection==
==Prop values==
==Blacklist==
==procfs leaks==
==Canary build==
- Lastly, try the latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It might have been updated with an improved MagiskHide.
Deletions:
- Some apps have started to look for "Magisk" in app names. If this is the case, hiding/repackaging the Magisk Manager doesn't do anything to hide the Manager. This is easy to test, just uninstall the Magisk Manager and try the app again. There are plans to fix this, but until then you might be able to use something like [[https://play.google.com/store/apps/details?id=com.gmail.heagoo.apkeditor | APK Editor]] to change the Magisk Manager app name. You can also just uninstall the Manager whenever you need to use the app detecting it. There are plans to implement a feature like this in the Manager, but there's no ETA for when this might happen.
- Lastly, make sure you're on the latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]] installed. It might have been updated with an improved MagiskHide.


Revision [498]

Edited on 2018-11-25 03:56:00 by didgeridoohan
Additions:
- It was recently discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device (see [[https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20 | here]] for an in-depth write-up) . This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. There's a quick fix though. After the discovery, topjohnwu created an app to detect if your device is affected and to fix it if that is the case. It can be found here: [[https://github.com/topjohnwu/ProcGate/releases/latest | ProcGate]]. In a future update of Magisk, MagiskHide might take care of fixing this bug for us, but until then there's the app.
Deletions:
- It was recently discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device. This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. There's a quick fix though. After the discovery, topjohnwu created an app to detect if your device is affected and to fix it if that is the case. It can be found here: [[https://github.com/topjohnwu/ProcGate/releases/latest | ProcGate]]. In a future update of Magisk, MagiskHide might take care of fixing this bug for us, but until then there's the app.


Revision [497]

Edited on 2018-11-25 03:55:09 by didgeridoohan
Additions:
- It was recently discovered by topjohnwu that many OEMs ship their devices with a broken implementation of how /proc is handled and thus there are procfs leaks letting apps monitor information about other processes on your device. This will let those apps detect Magisk... Since Android 7.0 this is not supposed to be allowed, but manufacturers being manufacturers, and whatever. There's a quick fix though. After the discovery, topjohnwu created an app to detect if your device is affected and to fix it if that is the case. It can be found here: [[https://github.com/topjohnwu/ProcGate/releases/latest | ProcGate]]. In a future update of Magisk, MagiskHide might take care of fixing this bug for us, but until then there's the app.


Revision [469]

Edited on 2018-10-16 13:17:19 by didgeridoohan
Additions:
There's a corresponding section about hiding root from apps and ""SafetyNet"" in the [[https://topjohnwu.github.io/Magisk/tutorials.html#best-practices-for-magiskhide | official Magisk documentation]]. That is also very well worth a look.


Revision [458]

Edited on 2018-09-26 10:56:46 by didgeridoohan
Additions:
- Lastly, make sure you're on the latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]] installed. It might have been updated with an improved MagiskHide.


Revision [433]

Edited on 2018-09-04 02:09:17 by didgeridoohan
Additions:
- It might also be a good idea to update, if you're not on the latest Magisk version. Magisk and MagiskHide is constantly being improved upon and there might have been changes that impact the app you're trying to hide root from.
Deletions:
- It might also be a good idea to update, if you're not on the latest Magisk version (even the beta release). Since Magisk v16.4, MagiskHide has been improved so that subprocesses of the hidden app or service are also monitored.


Revision [427]

Edited on 2018-09-04 02:04:16 by didgeridoohan
Additions:
- Another variant of root detection is that the app looks through your internal storage and triggers if it finds any files or folders that may hint at you having a rooted device. Magisk zips, etc. One such folder is ""MagiskManager"". Magisk v17+ no longer uses the ""MagiskManager"" folder for downloading zips and storing logs. If you have the folder on your device, it's a remnant of an old Magisk installation and can be deleted.
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the ""AdAway"" blacklist and apply the hosts file. **Keep in mind that you're disabling part of your banks security.**
Deletions:
- Another variant of root detection is that the app looks through your internal storage and triggers if it finds any files or folders that may hint at you having a rooted device. Magisk zips, etc. One such folder is ""MagiskManager"". Magisk v17+ no longer uses the ""MagiskManager" folder for downloading zips and storing logs. If you have the folder on your device, it's a remnant of an old Magisk installation and can be deleted.
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the ""AdAway"" blacklist and apply the hosts file. **Keep in mind that you're disabling part of your banks security.**


Revision [426]

Edited on 2018-09-04 02:03:10 by didgeridoohan
Additions:
- Another variant of root detection is that the app looks through your internal storage and triggers if it finds any files or folders that may hint at you having a rooted device. Magisk zips, etc. One such folder is ""MagiskManager"". Magisk v17+ no longer uses the ""MagiskManager" folder for downloading zips and storing logs. If you have the folder on your device, it's a remnant of an old Magisk installation and can be deleted.
Deletions:
- Another variant of root detection is that the app looks through your internal storage and triggers if it finds any files or folders that may hint at you having a rooted device. Magisk zips, etc. One such folder is MagiskManager. Currently there is no other way around this than renaming the folder whenever you need to use an app looking for it (which unfortunately will cause the Manager to not work properly, but rename it back when you're done). Like the above app name detection method, there should be a future update that will work around this. As usual, no ETA.


Revision [425]

Edited on 2018-09-04 02:01:16 by didgeridoohan
Additions:
- Android logging has to be enabled //(see [[MagiskHideBasics | ”MagiskHide requirements”]])//. If you don't know if you have logging enabled or not, check the Magisk log. If it's empty you might have logging disabled.
Deletions:
- Android logging has to be enabled //(see [[MagiskHideBasics | ”MagiskHide requirements”]])//.


Revision [401]

Edited on 2018-08-27 16:53:51 by didgeridoohan
Additions:
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 [[MagiskHideSafetyNet | the section about SafetyNet]])//.
Deletions:
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 [[MagiskHideSafetyNet | the section about SafetyNet]])//.


Revision [400]

Edited on 2018-08-27 16:53:41 by didgeridoohan
Additions:
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 [[MagiskHideSafetyNet | the section about SafetyNet]])//.
- Start by making sure MagiskHide works, if you haven't already. Easiest is to make a ""SafetyNet"" test in the Manager. If at least basic integrity passes, MagiskHide works. If it doesn't work, the first thing to test is to toggle MagiskHide off and on again //(also see [[MagiskHideIssues | "Test MagiskHide"]])//.
Deletions:
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 [[MagiskHideSafetyNet | the section about SafetyNet]])//.
- Start by making sure MagiskHide works, if you haven't already. Easiest is to make a SafetyNet test in the Manager. If at least basic integrity passes, MagiskHide works. If it doesn't work, the first thing to test is to toggle MagiskHide off and on again //(also see [[MagiskHideIssues | "Test MagiskHide"]])//.


Revision [394]

Edited on 2018-08-18 12:28:17 by didgeridoohan
Additions:
- Another variant of root detection is that the app looks through your internal storage and triggers if it finds any files or folders that may hint at you having a rooted device. Magisk zips, etc. One such folder is MagiskManager. Currently there is no other way around this than renaming the folder whenever you need to use an app looking for it (which unfortunately will cause the Manager to not work properly, but rename it back when you're done). Like the above app name detection method, there should be a future update that will work around this. As usual, no ETA.


Revision [389]

Edited on 2018-08-14 07:38:29 by didgeridoohan
Additions:
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the ""AdAway"" blacklist and apply the hosts file. **Keep in mind that you're disabling part of your banks security.**
Deletions:
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the AdAway blacklist and apply the hosts file. **Keep in mind that you're disabling part of your banks security.**


Revision [382]

Edited on 2018-08-13 11:27:43 by didgeridoohan

No Differences

Revision [381]

Edited on 2018-08-13 07:06:34 by didgeridoohan
Additions:
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the AdAway blacklist and apply the hosts file. **Keep in mind that you're disabling part of your banks security.**
Deletions:
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the AdAway blacklist and apply the hosts file.


Revision [380]

Edited on 2018-08-13 07:01:47 by didgeridoohan
Additions:
- Some apps have started to look for "Magisk" in app names. If this is the case, hiding/repackaging the Magisk Manager doesn't do anything to hide the Manager. This is easy to test, just uninstall the Magisk Manager and try the app again. There are plans to fix this, but until then you might be able to use something like [[https://play.google.com/store/apps/details?id=com.gmail.heagoo.apkeditor | APK Editor]] to change the Magisk Manager app name. You can also just uninstall the Manager whenever you need to use the app detecting it. There are plans to implement a feature like this in the Manager, but there's no ETA for when this might happen.
- Some apps will connect to an external web service that performs the check for it. This might mean that adding the app to the Hide list or repackaging the Magisk Manager won't help. One solution to this issue is to simply block the connection to the web service. One way is to use Magisk's Systemless Hosts and [[https://forum.xda-developers.com/showthread.php?t=2190753 | AdAway's]] "Log DNS requests" feature to figure out what domain to block. You can then add this domain directly to the AdAway blacklist and apply the hosts file.
- It has been reported that some apps go to extremes and blacklist your device with the bank/service provider/etc. If that's the case you're likely going to have to reflash your device or otherwise change your device id to get around it. This is kind of uncommon though. Consider it a last resort.
Deletions:
- Some apps have started to look for "Magisk" in app names. If this is the case, hiding/repackaging the Magisk Manager doesn't do anything to hide the Manager. This is easy to test, just uninstall the Magisk Manager and try the app again. There are plans to fix this, but until then you might be able to use something like [[https://play.google.com/store/apps/details?id=com.gmail.heagoo.apkeditor | APK Editor]] to change the Manager app name. You can also just uninstall the Manager whenever you need to use the app detecting it.
- It has been reported that some apps go to extremes and blacklist your device with the bank/service provider/etc. If that's the case you're likely going to have to reflash your device or otherwise change your device id to get around it. This is highly uncommon though. Consider it a last resort.


Revision [376]

Edited on 2018-08-03 08:22:35 by didgeridoohan
Additions:
- It has been reported that some apps go to extremes and blacklist your device with the bank/service provider/etc. If that's the case you're likely going to have to reflash your device or otherwise change your device id to get around it. This is highly uncommon though. Consider it a last resort.
Deletions:
- Some apps go to extremes and blacklist your device with the bank/service provider/etc. If that's the case you're likely going to have to reflash your device or otherwise change your device id to get around it.


Revision [374]

Edited on 2018-08-02 15:57:23 by didgeridoohan
Additions:
- Some apps go to extremes and blacklist your device with the bank/service provider/etc. If that's the case you're likely going to have to reflash your device or otherwise change your device id to get around it.
Deletions:
- Some apps go to extremes and blacklist your device with the bank, service provider, etc. If that's the case you're likely going to have to reflash your device or otherwise change your device id to get around it.


Revision [373]

Edited on 2018-08-02 15:56:24 by didgeridoohan
Additions:
- Some apps go to extremes and blacklist your device with the bank, service provider, etc. If that's the case you're likely going to have to reflash your device or otherwise change your device id to get around it.


Revision [372]

Edited on 2018-08-01 04:36:03 by didgeridoohan
Additions:
- Some apps have started to look for "Magisk" in app names. If this is the case, hiding/repackaging the Magisk Manager doesn't do anything to hide the Manager. This is easy to test, just uninstall the Magisk Manager and try the app again. There are plans to fix this, but until then you might be able to use something like [[https://play.google.com/store/apps/details?id=com.gmail.heagoo.apkeditor | APK Editor]] to change the Manager app name. You can also just uninstall the Manager whenever you need to use the app detecting it.
Deletions:
- Some apps have started to look for "Magisk" in app names. If this is the case, hiding/repackaging the Magisk Manager doesn't do anything to hide the Manager. This is essay to test, just uninstall the Magisk Manager and try the app again. There are plans to fix this, but until then you might be able to use something like [[https://play.google.com/store/apps/details?id=com.gmail.heagoo.apkeditor | APK Editor]] to change the Manager app name. You can also just uninstall the Manager whenever you need to use the app detecting it.


Revision [371]

Edited on 2018-07-31 05:23:51 by didgeridoohan
Additions:
- Some apps have started to look for "Magisk" in app names. If this is the case, hiding/repackaging the Magisk Manager doesn't do anything to hide the Manager. This is essay to test, just uninstall the Magisk Manager and try the app again. There are plans to fix this, but until then you might be able to use something like [[https://play.google.com/store/apps/details?id=com.gmail.heagoo.apkeditor | APK Editor]] to change the Manager app name. You can also just uninstall the Manager whenever you need to use the app detecting it.


Revision [370]

Edited on 2018-07-29 12:07:44 by didgeridoohan
Additions:
- Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values (very rare, but has been reported). For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. It can also be done with a [[https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12 | boot script]] (don't forget to set the proper permissions for the script to execute).
Deletions:
- Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values. For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. It can also be done with a [[https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12 | boot script]] (don't forget to set the proper permissions for the script to execute).


Revision [346]

Edited on 2018-07-19 14:11:27 by didgeridoohan
Additions:
- Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values. For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. It can also be done with a [[https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12 | boot script]] (don't forget to set the proper permissions for the script to execute).
Deletions:
- Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values. For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-simple-t3765199 | MagiskHide Props Config]] can do this. It can also be done with a [[https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12 | boot script]] (don't forget to set the proper permissions for the script to execute).


Revision [344]

Edited on 2018-07-19 10:10:36 by didgeridoohan
Additions:
You can also unhide the Manager by uninstalling the repackaged Manager and manually install the apk. Get it from the ([[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | release thread]] or [[https://github.com/topjohnwu/MagiskManager/releases | GitHub]])
Deletions:
The Manager can also be unhidden by installing the app again. Simply download the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Manager apk]] and install.
This means that every time there’s an update to the Manager or Magisk, you will have to hide the Manager again.


Revision [334]

Edited on 2018-07-19 09:47:09 by didgeridoohan
Additions:
===**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... See [[ManagerIssues | "Can't hide the Magisk Manager"]] for more info.


Revision [302]

Edited on 2018-07-09 00:49:32 by didgeridoohan
Additions:
- Start by making sure MagiskHide works, if you haven't already. Easiest is to make a SafetyNet test in the Manager. If at least basic integrity passes, MagiskHide works. If it doesn't work, the first thing to test is to toggle MagiskHide off and on again //(also see [[MagiskHideIssues | "Test MagiskHide"]])//.
Deletions:
- Start by making sure MagiskHide works, if you haven't already. Easiest is to make a SafetyNet test in the Manager. If at least basic integrity passes, MagiskHide works //(also see [[MagiskHideIssues | "Test MagiskHide"]])//.


Revision [300]

Edited on 2018-07-06 15:49:10 by didgeridoohan
Additions:
- Start by making sure MagiskHide works, if you haven't already. Easiest is to make a SafetyNet test in the Manager. If at least basic integrity passes, MagiskHide works //(also see [[MagiskHideIssues | "Test MagiskHide"]])//.
- Also make sure that your device conforms with the basics for MagiskHide to work //(also see [[MagiskHideBasics | "Basics"]])//.
Deletions:
- Start by making sure MagiskHide works, if you haven't already. Easiest is to make a SafetyNet test in the Manager. If at least basic integrity passes, MagiskHide works //(also see [[MagiskHideIssues | "Test MagiskHide]])//.


Revision [299]

Edited on 2018-07-06 15:45:02 by didgeridoohan
Additions:
- It might also be a good idea to update, if you're not on the latest Magisk version (even the beta release). Since Magisk v16.4, MagiskHide has been improved so that subprocesses of the hidden app or service are also monitored.
Deletions:
- It might also be a good idea to update, if you're not on the latest Magisk version (even the beta release). Since Magisk v16.4, MagiskHide has been improved you also hide subprocesses of the hidden app or service.


Revision [298]

Edited on 2018-07-06 15:44:20 by didgeridoohan
Additions:
- Some apps also detects other root apps on your device and stop working if they detect these. You can test by uninstalling these apps //(also see [[MagiskHideMore | "Detecting apps requiring root"]])//.
Unfortunately, there are apps out there with their own ways of detecting root that may circumvent MagiskHide //(also see [[MagiskHideMore | “More hiding tips”]])//. Magisk is constantly being updated and improved upon though, so it can pay to try again with a new Magisk update.
If you can't get it working, grabbing a logcat when the app detects root might show something //(see [[MagiskHideHelp | "Asking for help/reporting bugs"]])//. Save the log and post it in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | General support thread]], with plenty of details about the issue.
Deletions:
- Some apps also detects other root apps on your device and stop working if they detect these //(also see [[MagiskHideMore | "Detecting apps requiring root"]])//.
There are apps out there with their own ways of detecting root that may circumvent MagiskHide //(also see [[MagiskHideMore | “More hiding tips”]])//.
If you can't get it working, grabbing a logcat when the app detects root might show something //(see [[MagiskHideHelp | "Asking for help/reporting bugs"]])//.


Revision [296]

Edited on 2018-06-08 05:18:35 by didgeridoohan
Additions:
- It might also be a good idea to update, if you're not on the latest Magisk version (even the beta release). Since Magisk v16.4, MagiskHide has been improved you also hide subprocesses of the hidden app or service.


Revision [264]

Edited on 2018-04-06 11:12:36 by didgeridoohan
Additions:
- Start by making sure MagiskHide works, if you haven't already. Easiest is to make a SafetyNet test in the Manager. If at least basic integrity passes, MagiskHide works //(also see [[MagiskHideIssues | "Test MagiskHide]])//.


Revision [263]

Edited on 2018-04-06 11:09:34 by didgeridoohan
Additions:
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 [[MagiskHideSafetyNet | the section about SafetyNet]])//.
Deletions:
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.


Revision [258]

Edited on 2018-04-02 14:09:26 by didgeridoohan
Additions:
If you can't get it working, grabbing a logcat when the app detects root might show something //(see [[MagiskHideHelp | "Asking for help/reporting bugs"]])//.


Revision [257]

Edited on 2018-04-02 12:28:27 by didgeridoohan
Additions:
- Make sure that the app in question is selected in the Hide list (Under Magisk Hide in the Manager).
- It might be necessary to hide the Manager, since many apps look for this as a sign of rooting //(see “Hiding the Magisk Manager” below)//.
- Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values. For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-simple-t3765199 | MagiskHide Props Config]] can do this. It can also be done with a [[https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12 | boot script]] (don't forget to set the proper permissions for the script to execute).
- The app may also rely on other apps/services that detect root //(also see [[MagiskHideMore | "Dependencies"]])//.
- Some apps also detects other root apps on your device and stop working if they detect these //(also see [[MagiskHideMore | "Detecting apps requiring root"]])//.
Deletions:
- First, make sure that the app in question is selected in the Hide list (Under Magisk Hide in the Manager).
- If it still detects root, also hide the Manager //(see “Hiding the Magisk Manager” below)//.
Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values. For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-simple-t3765199 | MagiskHide Props Config]] can do this. This can also be done with a [[https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12 | boot script]] (don't forget to set the proper permissions for the script to execute).
The app may also rely on other apps/services that detect root //(also see [[MagiskHideMore | "Dependencies"]])//.
Some apps also detects other root apps on your device and stop working if they detect these //(also see [[MagiskHideMore | "Detecting apps requiring root"]])//.


Revision [255]

Edited on 2018-04-01 05:20:17 by didgeridoohan
Additions:
Some apps also detects other root apps on your device and stop working if they detect these //(also see [[MagiskHideMore | "Detecting apps requiring root"]])//.
Deletions:
Some apps also detects other root apps on your device and stop working if they detect these //(also see [[MagiskHide#hn_Detecting_apps_requiring_root | "Detecting apps requiring root"]])//.


Revision [253]

Edited on 2018-04-01 05:17:46 by didgeridoohan
Additions:
The app may also rely on other apps/services that detect root //(also see [[MagiskHideMore | "Dependencies"]])//.
Some apps also detects other root apps on your device and stop working if they detect these //(also see [[MagiskHide#hn_Detecting_apps_requiring_root | "Detecting apps requiring root"]])//.
Deletions:
The app may also rely on other apps/services that detect root (also see [[MagiskHideMore | "Dependencies"]]).


Revision [252]

Edited on 2018-03-31 14:10:59 by didgeridoohan
Additions:
The app may also rely on other apps/services that detect root (also see [[MagiskHideMore | "Dependencies"]]).


Revision [232]

Edited on 2018-03-18 14:42:11 by didgeridoohan
Additions:
Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values. For this you'd need to edit the files somehow. The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-simple-t3765199 | MagiskHide Props Config]] can do this. This can also be done with a [[https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12 | boot script]] (don't forget to set the proper permissions for the script to execute).
Deletions:
Some apps also look for the values written in build.prop or default.prop rather than reading the loaded values. For this you'd need to edit the files somehow. This can be done with a [[https://github.com/topjohnwu/Magisk/blob/master/docs/modules.md | Magisk module]] or with a [[https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12 | boot script]] (don't forget to set the proper permissions for the script to execute).


Revision [231]

Edited on 2018-03-05 15:47:28 by didgeridoohan
Additions:
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.
You can see if your Manager is hidden by going to “About” in the Manager and next to the version code there’ll be a random package name rather than com.topjohnwu.magisk. The “Hide Magisk Manager” option will also be changed to "Restore Magisk Manager" in the settings on a hidden Manager.
Deletions:
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. You can see if your Manager is hidden by going to “About” in the Manager and next to the version code there’ll be a random package name rather than com.topjohnwu.magisk. The “Hide Magisk Manager” option will also be gone from settings on a hidden Manager.


Revision [230]

Edited on 2018-03-05 15:45:55 by didgeridoohan
Additions:
Go to the Manager settings and choose "Restore Magisk Manager".
The Manager can also be unhidden by installing the app again. Simply download the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Manager apk]] and install.
Deletions:
The Manager is unhidden when installing the app again. So, if you need to unhide the Mangager, simply download the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Manager apk]] and install.


Revision [226]

Edited on 2018-03-01 03:37:12 by didgeridoohan
Additions:
- Android logging has to be enabled //(see [[MagiskHideBasics | ”MagiskHide requirements”]])//.
Deletions:
- Android logging has to be enabled //(see [[MagiskHideBasics | ”MagiskHide requirements”]])//.


Revision [222]

Edited on 2018-03-01 03:29:07 by didgeridoohan
Additions:
- Android logging has to be enabled //(see [[MagiskHideBasics | ”MagiskHide requirements”]])//.


Revision [189]

The oldest known version of this page was created on 2018-02-05 15:40:39 by didgeridoohan
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki