Google Updates SafetyNet, Temporary Fix Available for Magisk, Official Update Coming

XDA

By Doug Lynch

Published Jul 17, 2017

As we all know, the SafetyNet bypassing is a cat and mouse game between Google and the community. It was only last month when Google had previously updated SafetyNet in order to prevent our bypass attempts with applications such as Magisk. XDA Recognized Contributor and Developer topjohnwu was able to quickly put in a fix in their Magisk beta channel, which led to a stable update for the application toward the start of last week.

Google struck back with a new update to SafetyNet over the weekend that was brought to our attention thanks to XDA Member collinjames. This back and forth game between Google and the community will not likely stop until Google restructures the way it performs these checks. topjohnwu wrote about this previously and said that since Magisk is running as root while SafetyNet checks are not, the community will continue to have an advantage here.

This has led many to speculate that Google will indeed switch to a much more difficult method sometime in the future. Whatever the case may be, the latest update breaks Magisk's current bypass methods because it has been updated to check for a number of properties that Magisk uses. Then last night, XDA Senior Member Tobi@s explained what had changed on Google's end and did some investigating as to why these properties even exist.

You can read more about this explanation here in our Magisk forum. So for a temporary fix, you will either need to use a terminal emulator application on your smartphone, or execute the following commands via ADB...

```
su
```
```
resetprop --delete init.svc.magisk_pfs
```
```
resetprop --delete init.svc.magisk_pfsd
```

resetprop --delete init.svc.magisk_service

```
resetprop --delete persist.magisk.hide
```

Alternatively, if you are using Magisk's core mode feature, then you'll also need to execute this command as well. . .

```
resetprop --delete ro.magisk.disable
```

These commands will need to be executed each time you reboot your smartphone or tablet, or you could add all of these to a .sh file inside /magisk/.core/service.d/ so that Magisk will run them on each boot cycle. Tobi@s says they're not aware exactly how this interferes with Magisk's behavior, so do this at your own risk. Thankfully though, topjohnwu says they're aware of the issue and that an official fix is coming in the future.