Revision history for MagiskHideSafetyNet


Revision [769]

Last edited on 2019-11-17 08:03:03 by didgeridoohan
Additions:
You might also have to edit ro.bootimage.build.fingerprint and ro.vendor.build.fingerprint.


Revision [740]

Edited on 2019-10-15 15:41:52 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 [666]

Edited on 2019-07-22 14:30:38 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.@@
----


Revision [631]

Edited on 2019-06-13 13:12:43 by didgeridoohan
Additions:
If ""SafetyNet"" starts failing after an update to either Magisk, the Manager or both it's usually fixed by toggling MagiskHide off and on //(see ”Test ""MagiskHide"" above”)//. It might be necessary to reboot after toggling the setting off and on.
Deletions:
If ""SafetyNet"" starts failing after an update to either Magisk, the Manager or both it's usually fixed by toggling MagiskHide off and on //(see ”Test ""MagiskHide"" above”)//.


Revision [620]

Edited on 2019-05-27 03:36:20 by didgeridoohan
Additions:
Try changing your device's ro.build.fingerprint to a device's/ROM's that is known to pass ""SafetyNet"". The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. This 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) and the resetprop tool //(also see [[MagiskHideMore | "Sensitive props"]])//.
To change the device fingerprint with a [[https://topjohnwu.github.io/Magisk/guides.html#boot-scripts | boot script]], 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:
Try changing your device's ro.build.fingerprint to a device's/ROM's that is known to pass ""SafetyNet"". The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. This 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) and the resetprop tool //(also see [[MagiskHideMore | "Sensitive props"]])//.
To change the device fingerprint with a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]], 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):


Revision [612]

Edited on 2019-05-02 03:42:26 by didgeridoohan
Deletions:
===**Android logging**===
Android logging has to be enabled for MagiskHide to work //(see [[MagiskHideBasics | ”MagiskHide requirements”]])//.


Revision [549]

Edited on 2018-12-20 01:07:04 by didgeridoohan
Additions:
@@[[MagiskHide | -- To the top/main article --]]@@
Deletions:
[MagiskHide | -- To the top/main article --]]@@


Revision [548]

Edited on 2018-12-20 01:06:13 by didgeridoohan
Additions:
[MagiskHide | -- To the top/main article --]]@@
Make sure that you have a proper working internet connection and that there's nothing interfering (firewalls, etc).
Deletions:
@@[[MagiskHide | -- To the top/main article --]]@@


Revision [547]

Edited on 2018-12-20 01:04:38 by didgeridoohan
Additions:
This basically means that your device can't get a proper response from the Google servers, for whatever reason. It says nothing about wether your device actually passes ""SafetyNet"" or not...
If you get an invalid response result when checking ""SafetyNet"" it might mean that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest version of the ""SafetyNet"" API. Your best bet is always to use the Magisk Manager to check the ""SafetyNet"" result.
Deletions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest version of the ""SafetyNet"" API. Your best bet is always to use the Magisk Manager to check the ""SafetyNet"" result.


Revision [539]

Edited on 2018-12-16 15:33:42 by didgeridoohan
Additions:
To change the device fingerprint with a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]], 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:
To change the device fingerprint with a boot script, 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):


Revision [536]

Edited on 2018-12-16 13:10:52 by didgeridoohan
Additions:
Try changing your device's ro.build.fingerprint to a device's/ROM's that is known to pass ""SafetyNet"". The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] can do this. This 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) and the resetprop tool //(also see [[MagiskHideMore | "Sensitive props"]])//.
Deletions:
Try changing your device's ro.build.fingerprint to a device's/ROM's that is known to pass ""SafetyNet"". The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | 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) and the resetprop tool //(also see [[MagiskHideMore | "Sensitive props"]])//.


Revision [517]

Edited on 2018-12-09 04:09:45 by didgeridoohan
Additions:
To change the device fingerprint with a boot script, 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:
To change the device fingerprint with a boot script, 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):


Revision [508]

Edited on 2018-12-03 01:27:40 by didgeridoohan
Additions:
There are devices/ROM’s that just won’t be able to pass ""SafetyNet"". This might have to do with how the ROM is built, and if so there is nothing the user can do to change it.
But, fortunately, most of the time it is much simpler than that.
All custom ROMs are incompatible with ""SafetyNet"" out of the box (unless the ROM creator uses the described method below and uses a certified device fingerprint instead of the on that matches the ROM). This has to do with how Google certifies devices, CTS certification (Compatiblity Test Suite). If a device hasn’t passed the Google certification process, or if the ROM alters how the device is perceived by Google, it won’t be able to fully pass ""SafetyNet"" (CTS profile mismatch). You might be able to get basic integrity to report as true //(see Checking if Basic integrity passes above)// and this would mean that MagiskHide is working as it should and it's most likely a simple CTS certification issue.
Deletions:
There are devices/ROM’s that just won’t be able to pass ""SafetyNet"" fully. This has to do with how Google certifies devices, CTS certification (Compatiblity Test Suite). If a device hasn’t passed the Google certification process, or if the ROM alters how the device is perceived by Google, it won’t be able to fully pass ""SafetyNet"" (CTS profile mismatch). You might be able to get basic integrity to report as true //(see Checking if Basic integrity passes above)// and this means that MagiskHide is working as it should and it's most likely a CTS certification issue.


Revision [495]

Edited on 2018-11-18 12:17:06 by didgeridoohan
Additions:
If everything works out, ""SafetyNet"" should pass with no further input from the user, as long as your device fulfills the [[https://didgeridoohan.com/magisk/MagiskHideBasics | basic requirements]]. Nothing needs to be added to the Hide list. You'll see in the Magisk Manager if it works by checking the ""SafetyNet"" status. If ""SafetyNet"" doesn't pass after enabling Hide, try rebooting //(also see [[https://www.didgeridoohan.com/magisk/MagiskHideMore | “MagiskHide isn’t working”]])//.
Deletions:
If everything works out, ""SafetyNet"" should pass with no further input from the user, as long as your device fulfill the [[https://didgeridoohan.com/magisk/MagiskHideBasics | basic requirements]]. Nothing needs to be added to the Hide list. You'll see in the Magisk Manager if it works by checking the ""SafetyNet"" status. If ""SafetyNet"" doesn't pass after enabling Hide, try rebooting //(also see [[https://www.didgeridoohan.com/magisk/MagiskHideMore | “MagiskHide isn’t working”]])//.


Revision [494]

Edited on 2018-11-18 12:16:54 by didgeridoohan
Additions:
If everything works out, ""SafetyNet"" should pass with no further input from the user, as long as your device fulfill the [[https://didgeridoohan.com/magisk/MagiskHideBasics | basic requirements]]. Nothing needs to be added to the Hide list. You'll see in the Magisk Manager if it works by checking the ""SafetyNet"" status. If ""SafetyNet"" doesn't pass after enabling Hide, try rebooting //(also see [[https://www.didgeridoohan.com/magisk/MagiskHideMore | “MagiskHide isn’t working”]])//.
Deletions:
If everything works out, ""SafetyNet"" should pass with no further input from the user. Nothing needs to be added to the Hide list. You'll see in the Magisk Manager if it works by checking the ""SafetyNet"" status. If ""SafetyNet"" doesn't pass after enabling Hide, try rebooting //(also see [[https://www.didgeridoohan.com/magisk/MagiskHideMore | “MagiskHide isn’t working”]])//.


Revision [493]

Edited on 2018-11-18 12:15:22 by didgeridoohan
Additions:
First thing to do is to toggle MagiskHide off and on again. Sometimes MagiskHide stops working temporarily after an update of Magisk or the Manager. If ""SafetyNet"" still doesn't pass, make sure MagiskHide is actually working by using a root checker or a root app. Start by making sure the app can detect that your device is rooted. After that, add the app to the Hide list and see if it no longer can detect root. If that is the case, MagiskHide is working on your device. If you can't get it to work, see [[MagiskHideIssues | "MagiskHide Issues"]].
If ""SafetyNet"" starts failing after an update to either Magisk, the Manager or both it's usually fixed by toggling MagiskHide off and on //(see ”Test ""MagiskHide"" above”)//.
Deletions:
First thing to do is to toggle MagiskHide off and on again. Sometimes MagiskHide stops working temporarily after an update of Magisk or the Manager. If SafetyNet still doesn't pass, make sure MagiskHide is actually working by using a root checker or a root app. Start by making sure the app can detect that your device is rooted. After that, add the app to the Hide list and see if it no longer can detect root. If that is the case, MagiskHide is working on your device. If you can't get it to work, see [[MagiskHideIssues | "MagiskHide Issues"]].
If SafetyNet starts failing after an update to either Magisk, the Manager or both it's usually fixed by toggling MagiskHide off and on //(see ”Test ""MagiskHide"" above”)//.


Revision [492]

Edited on 2018-11-17 03:58:44 by didgeridoohan
Additions:
===**Permissive SELinux**===
MagiskHide can usually mask a permissive SELinux and let you pass ""SafetyNet"" anyway. But, it has been reported that this is not successful on all devices. If you have SELinux set to permissive, try changing it to enforcing and check ""SafetyNet"" again.
Changing ROM or completely wiping your device and starting out clean might also be a good idea.


Revision [479]

Edited on 2018-11-11 12:49:38 by didgeridoohan
Additions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest version of the ""SafetyNet"" API. Your best bet is always to use the Magisk Manager to check the ""SafetyNet"" result.
Deletions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest version of the ""SafetyNet"" API. Your best bet is always to use the Magisk Manager to check the SafetyNet result.


Revision [478]

Edited on 2018-11-11 12:49:18 by didgeridoohan
Additions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest version of the ""SafetyNet"" API. Your best bet is always to use the Magisk Manager to check the SafetyNet result.
This response might also mean that Google's servers are down at the moment.
Deletions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest version of the ""SafetyNet"" API. [[https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample | SafetyNet Helper Sample]] is a good app for checking ""SafetyNet"". It might also mean that Google's servers are down at the moment.


Revision [477]

Edited on 2018-11-11 12:43:10 by didgeridoohan
Additions:
If the device fingerprint is from an Android build after March 16 2018 you'll also have to match that build's Android Security Patch date (ro.build.version.security_patch). This is automatically done by [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]], but otherwise you can go about it the same way as described above.


Revision [476]

Edited on 2018-11-11 12:37:57 by didgeridoohan
Additions:
You can match your ROM's ro.build.fingerprint (and possibly other props, like ro.build.version.security_patch) with an official ROM for your device, or any other device that is certified, to make it pass ""SafetyNet"" fully //(see "Matching official prop values to pass ""SafetyNet""" and "Spoofing device fingerprint" below)//.
If you use an unofficial/developers ROM you might have to match an official/stable ROM's details (usually ro.build.fingerprint and possibly ro.build.version.security_patch) to pass ""SafetyNet"" //(also see "Spoofing device fingerprint" below)//.
Deletions:
You can match your ROM's ro.build.fingerprint (and possibly other props) with an official ROM for your device, or any other device that is certified, to make it pass ""SafetyNet"" fully //(see "Matching official prop values to pass ""SafetyNet""" and "Spoofing device fingerprint" below)//.
If you use an unofficial/developers ROM you might have to match an official/stable ROM's details (usually ro.build.fingerprint and possibly ro.build.description) to pass ""SafetyNet"" //(also see "Spoofing device fingerprint" below)//.


Revision [470]

Edited on 2018-10-16 13:17:45 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 [461]

Edited on 2018-10-02 04:26:54 by didgeridoohan
Deletions:
Some users have reported having to add the Play store to the MagiskHide list.


Revision [429]

Edited on 2018-09-04 02:05:53 by didgeridoohan
Additions:
Several (but not all) of the things mentioned above can be hidden by Magisk. See what Magisk can and cannot hide under //[[https://didgeridoohan.com/magisk/MagiskHideBasics | Basics]]//.
Deletions:
Many (but not all) of the things mentioned above can be hidden by Magisk. See what Magisk can and cannot hide under //[[https://didgeridoohan.com/magisk/MagiskHideBasics | Basics]]//.


Revision [428]

Edited on 2018-09-04 02:05:34 by didgeridoohan
Deletions:
===**Cannot check ""SafetyNet""**===
Don't be alarmed if you get a message when trying to check ""SafetyNet"" in the Magisk Manager, stating that it's not possible on a repackaged Manager. It's perfectly normal and is just a side effect of hiding the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager"]])//. Nothing is wrong...
If you need to check ""SafetyNet"", but want to keep the Manager hidden, use another app. But, make sure it's been updated to use Google's latest API, or you will simply get an invalid response. [[https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample | SafetyNet Helper Sample]] is a good working app for checking SafetyNet.


Revision [404]

Edited on 2018-08-29 11:23:14 by didgeridoohan
Additions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest version of the ""SafetyNet"" API. [[https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample | SafetyNet Helper Sample]] is a good app for checking ""SafetyNet"". It might also mean that Google's servers are down at the moment.
Deletions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest versin of ""SafetyNet"". [[https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample | SafetyNet Helper Sample]] is a good app for checking ""SafetyNet"". It might also mean that Google's servers are down at the moment.


Revision [403]

Edited on 2018-08-28 14:57:13 by didgeridoohan
Additions:
Start by clearing data for Play Services and the Play Store. There have been reports of this making ""SafetyNet"" passing. It's also a good idea to read through the rest of the guide. For example [[MagiskHideMore | More hiding tips]], [[MagiskHideIssues | MagiskHide Issues]], [[MagiskOther | Other things to try]], [[MagiskHelp | Asking for help/reporting bugs]] and other parts.
Deletions:
Start by clearing data for Play Services and the Play Store. There have been reports of this making SafetyNet passing. It's also a good idea to read through the rest of the guide. For example [[MagiskHideMore | More hiding tips]], [[MagiskHideIssues | MagiskHide Issues]], [[MagiskOther | Other things to try]], [[MagiskHelp | Asking for help/reporting bugs]] and other parts.


Revision [402]

Edited on 2018-08-28 04:27:15 by didgeridoohan
Additions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest versin of ""SafetyNet"". [[https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample | SafetyNet Helper Sample]] is a good app for checking ""SafetyNet"". It might also mean that Google's servers are down at the moment.
Deletions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest versin of ""SafetyNet"". [[https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample | SafetyNet Helper Sample]] is a good app for checking SafetyNet. It might also mean that Google's servers are down at the moment.


Revision [399]

Edited on 2018-08-27 16:17:46 by didgeridoohan
Additions:
This error is usually caused by the Manager not having internet access or the snet.apk not downloading properly. Try clearing data for the Manager and make sure that you have a working internet connection when starting the ""SafetyNet"" check. The Manager need to download the necessary files to be able to do the check and internet access is required to get a response from Google's servers.
Deletions:
This error is usually caused by the Manager not having internet access. Try clearing data for the Manager and make sure that you have a working internet connection when starting the ""SafetyNet"" check. The Manager need to download the necessary files to be able to do the check and internet access is required to get a response from Google's servers.


Revision [393]

Edited on 2018-08-17 06:18:55 by didgeridoohan
Additions:
There are two parts to the ""SafetyNet"" check, CTS Profile and Basic Integrity.
Deletions:
There are two parts to the SafetyNet check, CTS Profile and Basic Integrity.


Revision [392]

Edited on 2018-08-17 06:18:39 by didgeridoohan
Additions:
===**What triggers ""SafetyNet""?**===
There are two parts to the SafetyNet check, CTS Profile and Basic Integrity.
Examples of when ctsProfileMatch will report as false (failed):
- Uncertified device (the manufacturer haven't applied for Google certification)
- Unlocked bootloader
- Custom ROM
- Signs of system integrity compromise (rooting, etc)
- Signs of other attacks (Xposed, etc)
Examples of when basicIntegrity will report as false (failed):
- Signs of system integrity compromise (rooting, etc)
- Signs of other attacks (Xposed, etc)
Many (but not all) of the things mentioned above can be hidden by Magisk. See what Magisk can and cannot hide under //[[https://didgeridoohan.com/magisk/MagiskHideBasics | Basics]]//.


Revision [391]

Edited on 2018-08-16 02:55:22 by didgeridoohan
Additions:
If you need to check ""SafetyNet"", but want to keep the Manager hidden, use another app. But, make sure it's been updated to use Google's latest API, or you will simply get an invalid response. [[https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample | SafetyNet Helper Sample]] is a good working app for checking SafetyNet.
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest versin of ""SafetyNet"". [[https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample | SafetyNet Helper Sample]] is a good app for checking SafetyNet. It might also mean that Google's servers are down at the moment.
Deletions:
If you need to check ""SafetyNet"", but want to keep the Manager hidden, use another app. But, make sure it's been updated to use Google's latest API, or you will simply get an invalid response. Unfortunately, most ""SafetyNet"" checker apps in the Play Store are currently using the old API and cannot be used to check ""SafetyNet"". If you know of one that does, feel free to contact me through a [[https://forum.xda-developers.com/private.php?do=newpm&u=4667597 | PM]] over at [[http://www.xda-developers.com | XDA Developers]].
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest versin of ""SafetyNet"". It might also mean that Google's servers are down at the moment.


Revision [385]

Edited on 2018-08-14 02:41:55 by didgeridoohan
Additions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check ""SafetyNet"" hasn't been updated to work with the latest versin of ""SafetyNet"". It might also mean that Google's servers are down at the moment.
Deletions:
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check SafetyNet hasn't been updated to work with the latest versin of ""SafetyNet"". It might also mean that Google's servers are down at the moment.


Revision [384]

Edited on 2018-08-14 02:41:18 by didgeridoohan
Additions:
If you need to check ""SafetyNet"", but want to keep the Manager hidden, use another app. But, make sure it's been updated to use Google's latest API, or you will simply get an invalid response. Unfortunately, most ""SafetyNet"" checker apps in the Play Store are currently using the old API and cannot be used to check ""SafetyNet"". If you know of one that does, feel free to contact me through a [[https://forum.xda-developers.com/private.php?do=newpm&u=4667597 | PM]] over at [[http://www.xda-developers.com | XDA Developers]].
If you get an invalid response result when checking ""SafetyNet"" it likely means that the app you're using to check SafetyNet hasn't been updated to work with the latest versin of ""SafetyNet"". It might also mean that Google's servers are down at the moment.
Deletions:
If you need to check ""SafetyNet"", but want to keep the Manager hidden, use another app, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. Do not use [[https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest | SafetyNet Test]] by Free Android Tools. That app is broken and will give a false failure.
If you get an invalid response result when checking ""SafetyNet"" it might mean that Google's servers are down at the moment, or that the app you're using have not been updated to work with the latest version of ""SafetyNet"".


Revision [383]

Edited on 2018-08-14 02:17:26 by didgeridoohan
Additions:
If you get an invalid response result when checking ""SafetyNet"" it might mean that Google's servers are down at the moment, or that the app you're using have not been updated to work with the latest version of ""SafetyNet"".
Deletions:
If you get an invalid response result when checking ""SafetyNet"" it might mean that Google's servers are down at the moment.


Revision [375]

Edited on 2018-08-03 02:45:22 by didgeridoohan
Additions:
If you need to check ""SafetyNet"", but want to keep the Manager hidden, use another app, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. Do not use [[https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest | SafetyNet Test]] by Free Android Tools. That app is broken and will give a false failure.
Deletions:
If you need to check ""SafetyNet"", use another app, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. Do not use [[https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest | SafetyNet Test]] by Free Android Tools. That app is broken and will give a false failure.


Revision [347]

Edited on 2018-07-19 14:11:55 by didgeridoohan
Additions:
Try changing your device's ro.build.fingerprint to a device's/ROM's that is known to pass ""SafetyNet"". The Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | 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) and the resetprop tool //(also see [[MagiskHideMore | "Sensitive props"]])//.
Deletions:
Try changing your device's ro.build.fingerprint to a device's/ROM's that is known to pass ""SafetyNet"". 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) and the resetprop tool //(also see [[MagiskHideMore | "Sensitive props"]])//.


Revision [343]

Edited on 2018-07-19 10:02:44 by didgeridoohan
Additions:
Start by clearing data for Play Services and the Play Store. There have been reports of this making SafetyNet passing. It's also a good idea to read through the rest of the guide. For example [[MagiskHideMore | More hiding tips]], [[MagiskHideIssues | MagiskHide Issues]], [[MagiskOther | Other things to try]], [[MagiskHelp | Asking for help/reporting bugs]] and other parts.
Deletions:
Start reading through the rest of the guide. For example [[MagiskHideMore | More hiding tips]], [[MagiskHideIssues | MagiskHide Issues]], [[MagiskOther | Other things to try]], [[MagiskHelp | Asking for help/reporting bugs]] and other parts.


Revision [338]

Edited on 2018-07-19 09:54:18 by didgeridoohan
Additions:
If you get an invalid response result when checking ""SafetyNet"" it might mean that Google's servers are down at the moment.
Deletions:
If you get an invalid response result when checking ""SafetyNet"", check if you've repackaged (hidden) the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager"]])//. This is probably caused by a feature in the Play Services that checks for maliciously repackaged APK's. It's purely cosmetical and only means you can't check ""SafetyNet"" directly in the Manager. Use a different app to check ""SafetyNet"", like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. **From Magisk Manager v5.7.0 the ""SafetyNet"" check is disabled to reflect this.**
It is also possible that Google's servers are down at the moment.


Revision [337]

Edited on 2018-07-19 09:53:15 by didgeridoohan
Additions:
It is also possible that Google's servers are down at the moment.


Revision [311]

Edited on 2018-07-19 09:02:22 by didgeridoohan
Additions:
First thing to do is to toggle MagiskHide off and on again. Sometimes MagiskHide stops working temporarily after an update of Magisk or the Manager. If SafetyNet still doesn't pass, make sure MagiskHide is actually working by using a root checker or a root app. Start by making sure the app can detect that your device is rooted. After that, add the app to the Hide list and see if it no longer can detect root. If that is the case, MagiskHide is working on your device. If you can't get it to work, see [[MagiskHideIssues | "MagiskHide Issues"]].
Deletions:
First thing to do is to toggle MagiskHide off and on again. Sometimes MagiskHide stops working temporarily after an update of Magisk or the Manager. If SafetyNet still doesn't pass, make sure MagiskHide is actually working by using a root checker or a root app. Start by making sure the app can detect that your device is rooted. After that, add the app to the Hide list and see if it no longer can detect root. If that is the case, MagiskHide is working on your device. If you can't get it to work, see "[[MagiskHideIssues | "MagiskHide Issues"]].


Revision [308]

Edited on 2018-07-19 08:58:16 by didgeridoohan
Additions:
===**""SafetyNet"" fails after an update**===
If SafetyNet starts failing after an update to either Magisk, the Manager or both it's usually fixed by toggling MagiskHide off and on //(see ”Test ""MagiskHide"" above”)//.


Revision [307]

Edited on 2018-07-16 07:45:46 by didgeridoohan
Additions:
If you need to check ""SafetyNet"", use another app, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. Do not use [[https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest | SafetyNet Test]] by Free Android Tools. That app is broken and will give a false failure.
First thing to do is to toggle MagiskHide off and on again. Sometimes MagiskHide stops working temporarily after an update of Magisk or the Manager. If SafetyNet still doesn't pass, make sure MagiskHide is actually working by using a root checker or a root app. Start by making sure the app can detect that your device is rooted. After that, add the app to the Hide list and see if it no longer can detect root. If that is the case, MagiskHide is working on your device. If you can't get it to work, see "[[MagiskHideIssues | "MagiskHide Issues"]].
Deletions:
If you need to check ""SafetyNet"", use another app, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. Do not use SafetyNet Test by Free Android Tools. That app is broken and will give a false failure.
First thing to do is to make sure MagiskHide is actually working by using a root checker or a root app. Start by making sure the app can detect that your device is rooted. After that, add the app to the Hide list and see if it no longer can detect root. If that is the case, MagiskHide is working on your device. If you can't get it to work, see "[[MagiskHideIssues | "MagiskHide Issues"]].


Revision [303]

Edited on 2018-07-10 02:48:42 by didgeridoohan
Additions:
If you need to check ""SafetyNet"", use another app, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. Do not use SafetyNet Test by Free Android Tools. That app is broken and will give a false failure.
Deletions:
If you need to check ""SafetyNet"", use another app, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]].


Revision [295]

Edited on 2018-06-02 02:47:14 by didgeridoohan
Additions:
There are two parts to a ""SafetyNet"" check, CTS compatibility and Basic integrity. The CTS check is a server side checkup up that's difficult to spoof, while Basic integrity is done on the device side and is a lower level of security. Some apps only use the Basic integrity part of the ""SafetyNet"" API and thus can be used even if ""SafetyNet"" doesn't fully pass.
You can check ""SafetyNet"" directly in the Magisk Manager, to see if you at least pass Basic integrity. If you can't pass ""SafetyNet"", but Basic integrity shows as true, that basically means Google doesn't trust your device for some reason //(also see """SafetyNet"" incompatible devices and ROMs" below)//. You should be able to fix this by matching prop values with a ROM that passes ""SafetyNet"" //(see "Matching official prop values to pass ""SafetyNet""" and "Spoofing device fingerprint" below)//.
There are devices/ROM’s that just won’t be able to pass ""SafetyNet"" fully. This has to do with how Google certifies devices, CTS certification (Compatiblity Test Suite). If a device hasn’t passed the Google certification process, or if the ROM alters how the device is perceived by Google, it won’t be able to fully pass ""SafetyNet"" (CTS profile mismatch). You might be able to get basic integrity to report as true //(see Checking if Basic integrity passes above)// and this means that MagiskHide is working as it should and it's most likely a CTS certification issue.
You can match your ROM's ro.build.fingerprint (and possibly other props) with an official ROM for your device, or any other device that is certified, to make it pass ""SafetyNet"" fully //(see "Matching official prop values to pass ""SafetyNet""" and "Spoofing device fingerprint" below)//.
If you use an unofficial/developers ROM you might have to match an official/stable ROM's details (usually ro.build.fingerprint and possibly ro.build.description) to pass ""SafetyNet"" //(also see "Spoofing device fingerprint" below)//.
Try changing your device's ro.build.fingerprint to a device's/ROM's that is known to pass ""SafetyNet"". 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) and the resetprop tool //(also see [[MagiskHideMore | "Sensitive props"]])//.
If you get an invalid response result when checking ""SafetyNet"", check if you've repackaged (hidden) the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager"]])//. This is probably caused by a feature in the Play Services that checks for maliciously repackaged APK's. It's purely cosmetical and only means you can't check ""SafetyNet"" directly in the Manager. Use a different app to check ""SafetyNet"", like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. **From Magisk Manager v5.7.0 the ""SafetyNet"" check is disabled to reflect this.**
If the ""SafetyNet"" status check never finishes (make sure to wait a while), it might mean that your Google Play Services aren’t working properly or have crashed. Try force closing Play Services, clearing data and/or rebooting the device.
This error is usually caused by the Manager not having internet access. Try clearing data for the Manager and make sure that you have a working internet connection when starting the ""SafetyNet"" check. The Manager need to download the necessary files to be able to do the check and internet access is required to get a response from Google's servers.
The solution is to make sure your device passes ""SafetyNet"" and then clear data for the Play store and reboot. If you have multiple users on your device, you might have to clear data for all users. Next time you open up the Play store, "Device certification" should show "certified" and the apps should be able to install/show up again. You might have to wait a bit before the apps show up. Some users have reported having to wait mere minutes, others several hours up to a whole day.
Deletions:
There are two parts to a SafetyNet check, CTS compatibility and Basic integrity. The CTS check is a server side checkup up that's difficult to spoof, while Basic integrity is done on the device side and is a lower level of security. Some apps only use the Basic integrity part of the SafetyNet API and thus can be used even if SafetyNet doesn't fully pass.
You can check ""SafetyNet"" directly in the Magisk Manager, to see if you at least pass Basic integrity. If you can't pass ""SafetyNet"", but Basic integrity shows as true, that basically means Google doesn't trust your device for some reason //(also see """SafetyNet"" incompatible devices and ROMs" below)//. You should be able to fix this by matching prop values with a ROM that passes SafetyNet //(see "Matching official prop values to pass SafetyNet" and "Spoofing device fingerprint" below)//.
There are devices/ROM’s that just won’t be able to pass SafetyNet fully. This has to do with how Google certifies devices, CTS certification (Compatiblity Test Suite). If a device hasn’t passed the Google certification process, or if the ROM alters how the device is perceived by Google, it won’t be able to fully pass SafetyNet (CTS profile mismatch). You might be able to get basic integrity to report as true //(see Checking if Basic integrity passes above)// and this means that MagiskHide is working as it should and it's most likely a CTS certification issue.
You can match your ROM's ro.build.fingerprint (and possibly other props) with an official ROM for your device, or any other device that is certified, to make it pass SafetyNet fully //(see "Matching official prop values to pass SafetyNet" and "Spoofing device fingerprint" below)//.
If you use an unofficial/developers ROM you might have to match an official/stable ROM's details (usually ro.build.fingerprint and possibly ro.build.description) to pass SafetyNet //(also see "Spoofing device fingerprint" below)//.
Try changing your device's ro.build.fingerprint to a device's/ROM's that is known to pass SafetyNet. 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) and the resetprop tool //(also see [[MagiskHideMore | "Sensitive props"]])//.
If you get an invalid response result when checking SafetyNet, check if you've repackaged (hidden) the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager"]])//. This is probably caused by a feature in the Play Services that checks for maliciously repackaged APK's. It's purely cosmetical and only means you can't check SafetyNet directly in the Manager. Use a different app to check SafetyNet, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. **From Magisk Manager v5.7.0 the SafetyNet check is disabled to reflect this.**
If the SafetyNet status check never finishes (make sure to wait a while), it might mean that your Google Play Services aren’t working properly or have crashed. Try force closing Play Services, clearing data and/or rebooting the device.
This error is usually caused by the Manager not having internet access. Try clearing data for the Manager and make sure that you have a working internet connection when starting the SafetyNet check. The Manager need to download the necessary files to be able to do the check and internet access is required to get a response from Google's servers.
The solution is to make sure your device passes SafetyNet and then clear data for the Play store and reboot. If you have multiple users on your device, you might have to clear data for all users. Next time you open up the Play store, "Device certification" should show "certified" and the apps should be able to install/show up again. You might have to wait a bit before the apps show up. Some users have reported having to wait mere minutes, others several hours up to a whole day.


Revision [294]

Edited on 2018-06-02 02:45:32 by didgeridoohan
Additions:
If everything works out, ""SafetyNet"" should pass with no further input from the user. Nothing needs to be added to the Hide list. You'll see in the Magisk Manager if it works by checking the ""SafetyNet"" status. If ""SafetyNet"" doesn't pass after enabling Hide, try rebooting //(also see [[https://www.didgeridoohan.com/magisk/MagiskHideMore | “MagiskHide isn’t working”]])//.
Google continuously updates ""SafetyNet"". Currently, no versions prior to Magisk v13.3 will pass ""SafetyNet"" without major workarounds.
If you need to check ""SafetyNet"", use another app, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]].
You can check ""SafetyNet"" directly in the Magisk Manager, to see if you at least pass Basic integrity. If you can't pass ""SafetyNet"", but Basic integrity shows as true, that basically means Google doesn't trust your device for some reason //(also see """SafetyNet"" incompatible devices and ROMs" below)//. You should be able to fix this by matching prop values with a ROM that passes SafetyNet //(see "Matching official prop values to pass SafetyNet" and "Spoofing device fingerprint" below)//.
Deletions:
If everything works out, SafetyNet should pass with no further input from the user. Nothing needs to be added to the Hide list. You'll see in the Magisk Manager if it works by checking the SafetyNet status. If SafetyNet doesn't pass after enabling Hide, try rebooting //(also see [[https://www.didgeridoohan.com/magisk/MagiskHideMore | “MagiskHide isn’t working”]])//.
Google continuously updates SafetyNet. Currently, no versions prior to Magisk v13.3 will pass SafetyNet without major workarounds.
If you need to check SafetyNet, use another app, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]].
You can check SafetyNet directly in the Magisk Manager, to see if you at least pass Basic integrity. If you can't pass SafetyNet, but Basic integrity shows as true, that basically means Google doesn't trust your device for some reason //(also see "SafetyNet incompatible devices and ROMs" below)//. You should be able to fix this by matching prop values with a ROM that passes SafetyNet //(see "Matching official prop values to pass SafetyNet" and "Spoofing device fingerprint" below)//.


Revision [293]

Edited on 2018-06-02 02:44:13 by didgeridoohan
Additions:
Don't be alarmed if you get a message when trying to check ""SafetyNet"" in the Magisk Manager, stating that it's not possible on a repackaged Manager. It's perfectly normal and is just a side effect of hiding the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager"]])//. Nothing is wrong...
Deletions:
Don't be alarmed if you get a message when trying to check ""SafetyNet"" in the Magisk Manager, stating that it's not possible on a repackaged Manager. It's perfectly normal and is just a side effect of hiding the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager")//. Nothing is wrong...


Revision [292]

Edited on 2018-06-02 02:43:34 by didgeridoohan
Additions:
Don't be alarmed if you get a message when trying to check ""SafetyNet"" in the Magisk Manager, stating that it's not possible on a repackaged Manager. It's perfectly normal and is just a side effect of hiding the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager")//. Nothing is wrong...
Deletions:
Don't be alarmed if you get a message when trying to check SafetyNet in the Magisk Manager, starting that it's not possible on a repackaged Manager. It's perfectly normal and is just a side effect of hiding the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager")//. Nothing is wrong...


Revision [291]

Edited on 2018-06-02 02:39:06 by didgeridoohan
Additions:
===**Cannot check ""SafetyNet""**===
Don't be alarmed if you get a message when trying to check SafetyNet in the Magisk Manager, starting that it's not possible on a repackaged Manager. It's perfectly normal and is just a side effect of hiding the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager")//. Nothing is wrong...
If you need to check SafetyNet, use another app, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]].


Revision [290]

Edited on 2018-05-01 15:40:08 by didgeridoohan
Additions:
If you get an invalid response result when checking SafetyNet, check if you've repackaged (hidden) the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager"]])//. This is probably caused by a feature in the Play Services that checks for maliciously repackaged APK's. It's purely cosmetical and only means you can't check SafetyNet directly in the Manager. Use a different app to check SafetyNet, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. **From Magisk Manager v5.7.0 the SafetyNet check is disabled to reflect this.**
Deletions:
If you get an invalid response result when checking SafetyNet, check if you've repackaged (hidden) the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager"]])//. This is probably caused by a feature in the Play Services that checks for maliciously repackaged APK's. It's purely cosmetical and only means you can't check SafetyNet directly in the Manager. Use a different app to check SafetyNet, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. **In Magisk Manager v5.7.0 the SafetyNet check is disabled to reflect this.**


Revision [284]

Edited on 2018-04-29 11:44:52 by didgeridoohan
Additions:
If you get an invalid response result when checking SafetyNet, check if you've repackaged (hidden) the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager"]])//. This is probably caused by a feature in the Play Services that checks for maliciously repackaged APK's. It's purely cosmetical and only means you can't check SafetyNet directly in the Manager. Use a different app to check SafetyNet, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]]. **In Magisk Manager v5.7.0 the SafetyNet check is disabled to reflect this.**
Deletions:
If you get an invalid response result when checking SafetyNet, check if you've repackaged (hidden) the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager"]])//. This is probably caused by a feature in the Play Services that checks for maliciously repackaged APK's. It's purely cosmetical and only means you can't check SafetyNet directly in the Manager. Use a different app to check SafetyNet, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]].


Revision [280]

Edited on 2018-04-28 14:12:25 by didgeridoohan
Additions:
If you get an invalid response result when checking SafetyNet, check if you've repackaged (hidden) the Magisk Manager //(see [[MagiskHideHidingRoot | "Hiding the Magisk Manager"]])//. This is probably caused by a feature in the Play Services that checks for maliciously repackaged APK's. It's purely cosmetical and only means you can't check SafetyNet directly in the Manager. Use a different app to check SafetyNet, like [[https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground | SafetyNet Playground]].
Another thing to try is to force close Play Services, clearing it's data and/or rebooting the device.
Deletions:
If you get an invalid response result when checking SafetyNet. Try force closing Play Services, clearing data and/or rebooting the device.


Revision [270]

Edited on 2018-04-08 14:39:05 by didgeridoohan
Additions:
First thing to do is to make sure MagiskHide is actually working by using a root checker or a root app. Start by making sure the app can detect that your device is rooted. After that, add the app to the Hide list and see if it no longer can detect root. If that is the case, MagiskHide is working on your device. If you can't get it to work, see "[[MagiskHideIssues | "MagiskHide Issues"]].
Deletions:
First thing to do is to make sure MagiskHide is actually working by using a root checker or a root app. Start by making sure the app can detect that your device is rooted. After that, add the app to the Hide list and see if it no longer can detect root. If that is the case, MagiskHide is working on your device.


Revision [269]

Edited on 2018-04-08 14:37:32 by didgeridoohan
Additions:
If everything works out, SafetyNet should pass with no further input from the user. Nothing needs to be added to the Hide list. You'll see in the Magisk Manager if it works by checking the SafetyNet status. If SafetyNet doesn't pass after enabling Hide, try rebooting //(also see [[https://www.didgeridoohan.com/magisk/MagiskHideMore | “MagiskHide isn’t working”]])//.
Deletions:
If everything works out, SafetyNet should pass with no further input from the user. Nothing needs to be added to the Hide list. You'll see in the Magisk Manager if it works by checking the SafetyNet status. If SafetyNet doesn't pass after enabling Hide, try rebooting //(also see [[https://www.didgeridoohan.com/magisk/MagiskHideMore | “MagiskHide isn’t working”]] and the sections about SafetyNet below)//.


Revision [268]

Edited on 2018-04-08 14:35:25 by didgeridoohan
Additions:
You can check SafetyNet directly in the Magisk Manager, to see if you at least pass Basic integrity. If you can't pass SafetyNet, but Basic integrity shows as true, that basically means Google doesn't trust your device for some reason //(also see "SafetyNet incompatible devices and ROMs" below)//. You should be able to fix this by matching prop values with a ROM that passes SafetyNet //(see "Matching official prop values to pass SafetyNet" and "Spoofing device fingerprint" below)//.
Deletions:
You can chekc SafetyNet directly in the Magisk Manager, to see if you at least pass Basic integrity. If you can't pass SafetyNet, but Basic integrity shows as true, that basically means Google doesn't trust your device for some reason //(also see "SafetyNet incompatible devices and ROMs" below)//. You should be able to fix this by matching prop values with a ROM that passes SafetyNet //(see "Matching official prop values to pass SafetyNet" and "Spoofing device fingerprint" below)//.


Revision [267]

Edited on 2018-04-08 14:35:08 by didgeridoohan
Additions:
You can chekc SafetyNet directly in the Magisk Manager, to see if you at least pass Basic integrity. If you can't pass SafetyNet, but Basic integrity shows as true, that basically means Google doesn't trust your device for some reason //(also see "SafetyNet incompatible devices and ROMs" below)//. You should be able to fix this by matching prop values with a ROM that passes SafetyNet //(see "Matching official prop values to pass SafetyNet" and "Spoofing device fingerprint" below)//.
There are devices/ROM’s that just won’t be able to pass SafetyNet fully. This has to do with how Google certifies devices, CTS certification (Compatiblity Test Suite). If a device hasn’t passed the Google certification process, or if the ROM alters how the device is perceived by Google, it won’t be able to fully pass SafetyNet (CTS profile mismatch). You might be able to get basic integrity to report as true //(see Checking if Basic integrity passes above)// and this means that MagiskHide is working as it should and it's most likely a CTS certification issue.
Deletions:
There are devices/ROM’s that just won’t be able to pass SafetyNet fully. This has to do with how Google certifies devices, CTS certification (Compatiblity Test Suite). If a device hasn’t passed the Google certification process, or if the ROM alters how the device is perceived by Google, it won’t be able to fully pass SafetyNet (CTS profile mismatch). You might be able to get basic integrity to report as true (see Checking if Basic integrity passes below) and this means that MagiskHide is working as it should and it's most likely a CTS certification issue.
If you can't get it to work, the best place to ask would be in your device's/ROM's forum.
You can chekc SafetyNet directly in the Magisk Manager, to see if you at least pass Basic integrity. If you can't pass SafetyNet, but Basic integrity shows as true, that basically means Google doesn't trust your device for some reason //(also see "SafetyNet incompatible devices and ROMs" above)//. You should be able to fix this by matching prop values with a ROM that passes SafetyNet //(see "Matching official prop values to pass SafetyNet" below)//.


Revision [266]

Edited on 2018-04-08 14:33:36 by didgeridoohan
Additions:
You can match your ROM's ro.build.fingerprint (and possibly other props) with an official ROM for your device, or any other device that is certified, to make it pass SafetyNet fully //(see "Matching official prop values to pass SafetyNet" and "Spoofing device fingerprint" below)//.
If you use an unofficial/developers ROM you might have to match an official/stable ROM's details (usually ro.build.fingerprint and possibly ro.build.description) to pass SafetyNet //(also see "Spoofing device fingerprint" below)//.
Deletions:
It's possible that you can match your ROM's ro.build.fingerprint (and possibly other props) with an official ROM for your device to make it pass SafetyNet fully //(see "Matching official prop values to pass SafetyNet" below)//.
If you use an unofficial/developers ROM you might have to match an official/stable ROM's details (usually ro.build.fingerprint and possibly ro.build.description) to pass SafetyNet. Check your device's forum for details //(also see [[MagiskHideMore | "Sensitive props"]])//.


Revision [233]

Edited on 2018-03-18 14:45:23 by didgeridoohan
Additions:
Try changing your device's ro.build.fingerprint to a device's/ROM's that is known to pass SafetyNet. 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) and the resetprop tool //(also see [[MagiskHideMore | "Sensitive props"]])//.
Deletions:
Try changing your device's ro.build.fingerprint to a device's/ROM's that is known to pass SafetyNet. 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) and the resetprop tool //(also see [[MagiskHideMore | "Sensitive props"]])//.


Revision [228]

Edited on 2018-03-04 10:41:21 by didgeridoohan
Additions:
To change the device fingerprint with a boot script, 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):
%%
#!/system/bin/sh
resetprop ro.build.fingerprint <fingerprint value>
%%


Revision [225]

Edited on 2018-03-01 03:36:45 by didgeridoohan
Additions:
If everything works out, SafetyNet should pass with no further input from the user. Nothing needs to be added to the Hide list. You'll see in the Magisk Manager if it works by checking the SafetyNet status. If SafetyNet doesn't pass after enabling Hide, try rebooting //(also see [[https://www.didgeridoohan.com/magisk/MagiskHideMore | “MagiskHide isn’t working”]] and the sections about SafetyNet below)//.
===**Android logging**===
Android logging has to be enabled for MagiskHide to work //(see [[MagiskHideBasics | ”MagiskHide requirements”]])//.
Deletions:
If everything works out, SafetyNet should pass with no further input from the user. Nothing needs to be added to the Hide list. You'll see in the Magisk Manager if it works by checking the SafetyNet status. If SafetyNet doesn't pass after enabling Hide, try rebooting (also see “Hide isn’t working” and the sections about SafetyNet below).


Revision [190]

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