[App] [SafetyNet Passer] Pass SafetyNet after 2017-07-17 on Magisk V13

[Funk Wizard]

Hello XDA,

As we are all aware that once again Google broke SafetyNet Passing as they have extended their property scanning | Original Article here

The temporary fix was originally mentioned on this thread by @[email protected]

However you had to do the terminal commands after every reboot, thus Me and a few friends took this idea and created an app that does the same for you in the background and thus an easy temporary fix.

All you have to do is to install the apk as usual, grant it supersu permission and click to fix :laugh:

GitHub: https://github.com/Agusyc/SafetyNetPasser | Credits @Agusyc15

Download APK

Made a Quick Video Here

Tested Working on Oneplus 5 & Pixel XL | Magisk V13.2

Development Credits: @Agusyc15 & @unknownblkman
Magisk Credits as always @topjohnwu
Original Fix & ADB Commands: @[email protected]

PS: This is a temporary fix, I am sure @topjohnwu is aware of this situation and an official fix should be out soon :fingers-crossed:

Never Settle :highfive:

 

[Funk Wizard]

Reserved

 

[Interceptor777]

You can use the module I attached, it works and does it systemlessly.

I didn't make it but I forgot who did lol

 

[Bewildered Wolf]

You can use the module I attached, it works and does it systemlessly.

I didn't make it but I forgot who did lol

What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?

 

[Interceptor777]

What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?

Resurrection Remix with Spectrum kernel app, running lightning kernel LOS version which supports it.

The symbol on the quick settings is a quick profile switcher for spectrum, this is what it looks like on balanced profile.

Also, theme is also called spectrum on the play store.

 

[hachamacha]

Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.

 

[Funk Wizard]

GitHub along with the Updated apk now uploaded on the OP | Credits @Agusyc15

 

[Funk Wizard]

Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.

Please try the new apk uploaded on the OP :fingers-crossed:

 

[hachamacha]

Please try the new apk uploaded on the OP :fingers-crossed:

Just tried it and it works fine as did your first. Thanks!

 

[Pho3nX]

@Funk Wizard you can also purpose the recovery flash solution (by noahajac) available from Github : here

Personaly i prefer flash the fix by this way instead of install a apk/service for fix SafetyNet each boot

 

[ArkAngel06]

Magisk 13.2 has been released and fixes the SafetyNet test failing.

Magisk 13.2

I can confirm that it's working for me.

 

[Hackpb]

Magisk 13.3 already available, and everything is fixed

 

[Binary Assault]

Anyone having issues upgrading ?

I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.

Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.

Reinstalling Magisk 13.0 allows Magisk manager to run.

Root still works when upgrading to 13.3, but Magisk manager still force closes.

Any ideas?

 

[L22EEW]

13.3 fixed for me

 

[crumble6]

Anyone having issues upgrading ?

I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.

Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.

Reinstalling Magisk 13.0 allows Magisk manager to run.

Root still works when upgrading to 13.3, but Magisk manager still force closes.

Any ideas?

I'm having this issue too.

EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.

 

[ArkAngel06]

Anyone having issues upgrading ?

I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.

Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.

Reinstalling Magisk 13.0 allows Magisk manager to run.

Root still works when upgrading to 13.3, but Magisk manager still force closes.

Any ideas?

I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.

I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.

My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.

Latest Magisk Manager

Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.

 

[Binary Assault]

I'm having this issue too.

EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.

That didn't work for me unfortunately.

I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.

I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.

My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.

Latest Magisk Manager

Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.

This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.

Thanks guys!

 

[crumble6]

That didn't work for me unfortunately.

This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.

Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.

 

[Binary Assault]

Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.

Ya, I just discovered this. I actually noticed a few things,
My original issue was caused by a module I installed
It seems anything I flash via TWRP makes Magisk manager fail.
Most modules I installed in TWRP that fails, will properly install within Magisk manager.

For me, the culprit was doze for Google play services. Even installing it via Magisk manager froze Magisk manager.

Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.

 

[crumble6]

Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.

Just delete the module folder from /magisk and reboot. You will need root access for this but from what I've found, root access still works even though Magisk Manager is not responding.