Revision history for MagiskHideMore
Additions:
Some apps detect Busybox and see this as a sign of your device being compromised (rooted). Magisk should be able to hide any Busybox installed as a Magisk module. [[https://forum.xda-developers.com/member.php?u=4544860 | osm0sis]] has a great Busybox module available in the Magisk repo (install from the Magisk app, under "Downloads").
Deletions:
Deletions:
If you can't get MagiskHide to work, try enabling the Core Only Mode in Magisk Manager settings. Only ""MagiskSU"" and MagiskHide will be activated, and no modules will load. This is a good way for finding out if it's a module causing your issues without actually uninstalling the module.
Additions:
Some apps trigger if they find "sensitive props". Also, on some devices SafetyNet triggers if certain props are not set to the expected values. A few props are set to "safe" values by MagiskHide by default. These prop are known to trigger some apps that look for root and "tampered" devices. Currently these are (apart from props for the bootloader state):
Deletions:
Deletions:
Please don't hesitate to [[https://www.paypal.me/didgeridoohan | support the work involved]] in keeping this guide alive.@@
----
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.@@
----
Please don't hesitate to [[https://www.paypal.me/didgeridoohan | support the work involved]] in keeping this guide alive.@@
----
Additions:
The props can be changed with a [[https://github.com/topjohnwu/Magisk/blob/master/docs/modules.md | Magisk module]] or 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) and the resetprop tool.
If you for some reason need to reset the prop values that MagiskHide changes //(see "Sensitive props" above)//, you can do this with the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]]. It can also be done by using a [[https://topjohnwu.github.io/Magisk/guides.html#boot-scripts | boot script]] that runs the resetprop tool to change back to the desired prop value. Add the following to a file you place in /data/adb/service.d (and don't forget to set the proper permissions for the script to execute):
If you for some reason need to reset the prop values that MagiskHide changes //(see "Sensitive props" above)//, you can do this with the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]]. It can also be done by using a [[https://topjohnwu.github.io/Magisk/guides.html#boot-scripts | boot script]] that runs the resetprop tool to change back to the desired prop value. Add the following to a file you place in /data/adb/service.d (and don't forget to set the proper permissions for the script to execute):
Deletions:
If you for some reason need to reset the prop values that MagiskHide changes //(see "Sensitive props" above)//, you can do this with the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]]. It can also be done by using a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]] that runs the resetprop tool to change back to the desired prop value. Add the following to a file you place in /data/adb/service.d (and don't forget to set the proper permissions for the script to execute):
Additions:
The props can be changed with a [[https://github.com/topjohnwu/Magisk/blob/master/docs/modules.md | Magisk module]] or 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) and the resetprop tool.
If you for some reason need to reset the prop values that MagiskHide changes //(see "Sensitive props" above)//, you can do this with the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]]. It can also be done by using a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]] that runs the resetprop tool to change back to the desired prop value. Add the following to a file you place in /data/adb/service.d (and don't forget to set the proper permissions for the script to execute):
If you for some reason need to reset the prop values that MagiskHide changes //(see "Sensitive props" above)//, you can do this with the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]]. It can also be done by using a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]] that runs the resetprop tool to change back to the desired prop value. Add the following to a file you place in /data/adb/service.d (and don't forget to set the proper permissions for the script to execute):
Deletions:
If you for some reason need to reset the prop values that MagiskHide changes //(see "Sensitive props" above)//, you can do this with the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]]. It can also be done by using a boot script that runs the resetprop tool to change back to the desired prop value. Add the following to a file you place in /data/adb/service.d (and don't forget to set the proper permissions for the script to execute):
Additions:
If you can't get MagiskHide to work, try enabling the Core Only Mode in Magisk Manager settings. Only ""MagiskSU"" and MagiskHide will be activated, and no modules will load. This is a good way for finding out if it's a module causing your issues without actually uninstalling the module.
Deletions:
Additions:
If you for some reason need to reset the prop values that MagiskHide changes //(see "Sensitive props" above)//, you can do this with the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]]. It can also be done by using a boot script that runs the resetprop tool to change back to the desired prop value. Add the following to a file you place in /data/adb/service.d (and don't forget to set the proper permissions for the script to execute):
Deletions:
Additions:
If you for some reason need to reset the prop values that MagiskHide changes //(see "Sensitive props" above)//, you can do this with the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]]. It can also be done by using a boot script that runs the resetprop tool to change back to the desired prop value. Add the following to a file you place in /sbin/.core/img/.core/service.d (and don't forget to set the proper permissions for the script to execute):
Deletions:
Additions:
There are apps that detect known apps that require root and refuse to work properly or even start if that is the case. Usual suspects include (but aren't limited to) busybox apps, Xposed installer, root hiding apps, etc.
Deletions:
Additions:
This can be worked around by uninstalling or possibly freezing ([[https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup | Titanium Backup]] can do this, among others) the offending root app when you need to use an app detecting root apps and reinstalling/unfreezing it afterwards. Cumbersome, but it might work. There are also some Xposed modules that can hide apps from other apps, but having Xposed installed might cause other issues with tampering detection...
Deletions:
Additions:
If you for some reason need to reset the prop values that MagiskHide changes //(see "Sensitive props" above)//, you can do this with the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-simple-t3765199 | MagiskHide Props Config]]. It can also be done by using a boot script that runs the resetprop tool to change back to the desired prop value. Add the following to a file you place in /sbin/.core/img/.core/service.d (and don't forget to set the proper permissions for the script to execute):
Deletions:
Additions:
This can be worked around by uninstalling or possibly freezing ([[https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup | Titanium Backup]] can do this, among others) the offending root app when you need to use these apps and reinstalling/unfreezing it afterwards. Cumbersome, but it might work. There are also some Xposed modules that can hide apps from other apps, but having Xposed installed might cause other issues with tampering detection...
Deletions:
Additions:
This can be worked around by uninstalling or possibly freezing ([[https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup | Titanium Backup]] can do this) the offending root app when you need to use these apps and reinstalling/unfreezing it afterwards. Cumbersome, but it might work. There are also some Xposed modules that can hide apps from other apps, but having Xposed installed might cause other issues with tampering detection...
Deletions:
Additions:
%%getprop ro.debuggable%%
