SafetyNet not passing on Magisk v12 OnePlus3T on 7.1.1 - OnePlus 3T Questions & Answers

My oxygenOS version is 4.1.6, I installed Magisk with MagiskSU(topjohnwu) today but SafetyNet won't pass. I have MagiskHide enabled.
Any idea why?

Google updated SafetyNet so you're gonna have to use magisk core mode for now to pass safetynet

You can also switch to Magisk 13 which is currently passing for me without issues. I am no longer using any Magisk Modules as having those enabled was causing it to fail.

Or you can switch v13 beta to pass safetynet which is not stable yet

CJ-Wylde said:
You can also switch to Magisk 13 which is currently passing for me without issues. I am no longer using any Magisk Modules as having those enabled was causing it to fail.
Click to expand...
Click to collapse
Same

chazarss said:
Or you can switch v13 beta to pass safetynet which is not stable yet
Click to expand...
Click to collapse
Do I flash the beta directly or must I uninstall Magisk before and then install the beta?
Also, where can I find this beta?

Here is the link
Fredol7 said:
Do I flash the beta directly or must I uninstall Magisk before and then install the beta?
Also, where can I find this beta?
Click to expand...
Click to collapse
You can dirty flash the magisk v13 without uninstall the previous one but don't forget to update magisk manager app to v5.0.2 or the magisk v13 won't work
Here is the link
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

Fredol7 said:
My oxygenOS version is 4.1.6, I installed Magisk with MagiskSU(topjohnwu) today but SafetyNet won't pass. I have MagiskHide enabled.
Any idea why?
Click to expand...
Click to collapse
Enable Magisk core module in only in the magisk settings to pass the safety net check. this is a temporary fix.

The following module works for me: https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Using Magisk v12, with other modules working (not just core mode) and it passes Safetynet.
The Safetynet fix does change the device fingerprint, so I think it will screw up (prevent) OTA updates. But you can simply disable the module when an update rolls out.

redpoint73 said:
The following module works for me: https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Using Magisk v12, with other modules working (not just core mode) and it passes Safetynet.
The Safetynet fix does change the device fingerprint, so I think it will screw up (prevent) OTA updates. But you can simply disable the module when an update rolls out.
Click to expand...
Click to collapse
The actual fix doesn't need the fingerprint change. There's a modified version here that have those prop changing lines commented out.

Related

Any Xposed v87 Systemless that doesn't require Magisk?

In short I have a rooted OnePlus 3 with OOS 3.2.7, the latest OOS is 3.2.8 but has the November security patch which as I'm sure you known blocks xposed v86 which I need.. I also need to pass SafetyNet so I can't use OOS 3.2.8 without the updated Xposed v87 yet workout it being systemless I can't pass SN with it and even then I'm assuming suhide along with Root Switch still works at disabling root and hides Xposed
Anyway you see my predicament as I can't use Magisk v9 with Systemless xposed etc as I still can pass SafetyNet
Any help would be appreciated
v86.2 is the last systemless xposed that doesn't require Magisk. Every version after requires Magisk. You're still stuck though I believe. Magisk v9 + Phh SU is the only way to pass SafetyNet on the November patch. Once you flash xposed SafetyNet fails.
suhide doesn't work anymore since the November patch so you can forget about using that. It just bootloops.
Tikerz said:
v86.2 is the last systemless xposed that doesn't require Magisk. Every version after requires Magisk. You're still stuck though I believe. Magisk v9 + Phh SU is the only way to pass SafetyNet on the November patch. Once you flash xposed SafetyNet fails.
suhide doesn't work anymore since the November patch so you can forget about using that. It just bootloops.
Click to expand...
Click to collapse
Nope suhide works perfect even with xposed enabled on iOS 3.2.7
The magisk+phh option even though it fails SN will it still play Pokemon go?
steve51184 said:
Nope suhide works perfect even with xposed enabled on iOS 3.2.7
The magisk+phh option even though it fails SN will it still play Pokemon go?
Click to expand...
Click to collapse
That's because 3.2.7 is not on the November patch. Magisk v9 and Phh SU will pass SN. I've been using it on ROMs with November security patch. Just had to give up Xposed which sucks.
Sent from my Pixel using Tapatalk
Tikerz said:
That's because 3.2.7 is not on the November patch. Magisk v9 and Phh SU will pass SN. I've been using it on ROMs with November security patch. Just had to give up Xposed which sucks.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
See I don't get why anyone would give up xposed over the features in 3.2.8 which are in short nothing..

Magisk 11.0 upgrade from 10.2 destroyed my Nexus 5x CTS profile match

Just upgraded from 10.2 to 11.0 on a nexus 5x using magisk manager. CTS profile match triggered now I'm screwed. How to go back or how to fix?
Just uninstall magisk, wipe your system, and reinstall your ROM. You shouldn't have to wipe user data.
mickrussom said:
Just upgraded from 10.2 to 11.0 on a nexus 5x using magisk manager. CTS profile match triggered now I'm screwed. How to go back or how to fix?
Click to expand...
Click to collapse
Did you enable magisk hide again?
It broke cts on my tablet too so going to try a few things before I do what I said in the above post.
Edit: I could not get CTS back with the new Magisk so something is broken with Magisk hide.
I had the same problem on my OnePlus 2.
I had to clear Magisk Application data, then reboot, and reactivate Magisk Hide to get it back. No need to reboot when activating Magisk Hide.
Chiyo-chan said:
I had the same problem on my OnePlus 2.
I had to clear Magisk Application data, then reboot, and reactivate Magisk Hide to get it back. No need to reboot when activating Magisk Hide.
Click to expand...
Click to collapse
Yeah I tried that but sadly if I have to reboot for other reasons it breaks Magisk Hide unless I toggle and even that only fixes it half the time.
For me, magisk hide is still working after reboot.
I have the same problem when i reboot magisk hide break
There's currently a bug with Hide initialization that will be addressed. After a reboot toggle Hide off and on and you'll be fine.
Yeah I got it to work but hopefully the bug is fixed quickly is rather not go back to pre-10.2 days.
I had the same problem.. but before reinstalling everything I turned magisk hose off rebooted turned it on again and rebooted and it worked fine since.
Sent from my HTC6545LVW using Tapatalk
Now Magisk hide works but it's losing root again.
Link_of_Hyrule said:
Now Magisk hide works but it's losing root again.
Click to expand...
Click to collapse
Try disabling Busybox in the Manager. Other users that are loosing root on v11.1 are reporting that this helped. Sounds like a bug somewhere...
Magisk 11.1 and Magisk Manager 4.0 fixed my CTS profile issue. I was having CTS profile issues with 11.0 but after updating to 11.1, the issue disappeared. I can now play Pokemon Go on a rooted phone with limited Xposed support (using Root Switch to disable Xposed); Xposed module like Snorlax is working.
I believe topjohnwu did acknowledge that it's due to some bug in MagiskHide.
xstahsie said:
Magisk 11.1 and Magisk Manager 4.0 fixed my CTS profile issue. I was having CTS profile issues with 11.0 but after updating to 11.1, the issue disappeared. I can now play Pokemon Go on a rooted phone with limited Xposed support (using Root Switch to disable Xposed); Xposed module like Snorlax is working.
I believe topjohnwu did acknowledge that it's due to some bug in MagiskHide.
Click to expand...
Click to collapse
Which Xposed are u using
I mean standard or the systemless
I flashed the official Xposed and NOT the unofficial from topjohnwu. Being that I have a Nexus 6P w/ 6.0.1 , I flashed xposed-87-sdk23-arm64.zip. I don't think the unofficial xposed works w/ Root Switch.
Official Xposed link: https://forum.xda-developers.com/showthread.php?t=3034811
Yeah the 11.1 fixed the cts issues but still lose root occasionally. It's not as stable as the old version was hopefully the bugs get fixed.

Safetynet checks failing with Magisk 20.4

hi, i just flashed my xiaomi mix phone with Magisk 20.4. everything is new but the safetynet checks are failing.
i have previously tried on riru and edxposed. the checks say YES but i still cannot load pokemon go. i think those fixes are fake and not working, Google seems to be able to detect it still.
Can anyone help?
thanks.
jasonjiangyu said:
hi, i just flashed my xiaomi mix phone with Magisk 20.4. everything is new but the safetynet checks are failing.
i have previously tried on riru and edxposed. the checks say YES but i still cannot load pokemon go. i think those fixes are fake and not working, Google seems to be able to detect it still.
Can anyone help?
thanks.
Click to expand...
Click to collapse
Having the exact same issue with my Mix 3. Just flashed a few moments ago. Been looking at the other threads and it seems that no fix works as of now. Hoping that it isn't permanent as Google is cracking down on unlocked bootloaders.
Try to hide what you want via magisk hide.
Sorry, but that is not helpful. Same thing here. Device passed SafetyNet on 20.3. After upgrade to 20.4 it fails. What can I do to figure out what changed?
please refer here to set it up in your phone.
Be notice: If you don't use edxposed, just skip it. If you do, please remember to install canary version of edxposed in Edxposed manager !
Kris
Kris Chen said:
please refer here to set it up in your phone.
Be notice: If you don't use edxposed, just skip it. If you do, please remember to install canary version of edxposed in Edxposed manager !
Kris
Click to expand...
Click to collapse
Thank you! You were right, this was not caused by the Magisk upgrade, but by EdXposed. After upgrading to Canary version SafetyNet passes again.
I'd also like to add (in case someone stumbles across this thread looking for answers) that Magisk v20.4+ has MagiskHide disabled by default. On a fresh install you will have to enable it before Hide will be able to do it's thing.

Question Safetynet failed after installing pixel experience+ (agust security patch)

Installed pixel experience using orangefox recovery. Don't know much about rooting. How to install magisk (without root) and pass the safetynet test?
Abhii1 said:
Installed pixel experience using orangefox recovery. Don't know much about rooting. How to install magisk (without root) and pass the safetynet test?
Click to expand...
Click to collapse
follow this tutorial:
[2023 FIX] Fix Magisk CTS Profile False Error - Bypass Safetynet
Magisk CTS Profile False Error is now popping up on almost everyone's device since Google made some changes in March. To Bypass Safetynet...
droidholic.com
aarestu said:
follow this tutorial:
[2023 FIX] Fix Magisk CTS Profile False Error - Bypass Safetynet
Magisk CTS Profile False Error is now popping up on almost everyone's device since Google made some changes in March. To Bypass Safetynet...
droidholic.com
Click to expand...
Click to collapse
Thanks but i don't know how to install magisk
Abhii1 said:
Thanks but i don't know how to install magisk
Click to expand...
Click to collapse
Or you can install try other os.. wait until it fix..
I use ArrowOS for daily use, everything seems stable so far.. including safetynet.. no need root for safetynet secure on ArrowOS
You can install Magisk with adb sideload.
In Magisk you can currently install Magisk hide props config. With that you can change the device fingerprint to an official one. Also use the hide option to prevent Google play from acting up.
I do not know how to pass the cts test yet. There is another mode that can help (Universal SafetyNet fix).
But I have not managed to get it pass the test.
If you find out, let me know.
I have exported some files for the fingerprint from miui
I hope that can help. It is for global Rom.

Questions regarding updating Magisk

Hi everyone!
It's been about a year and a half since I first installed Magisk on my phone with TWRP and considering that I now noticed I'm getting SafenityNet API error, I wanted to update my Magisk to the latest version and install the Universal SafetyNet module as well to fix this issue.
I just have some questions regarding this:
I'm running Magisk Manager 7.5.1 & Magisk 20.4 repacked and with Magisk Hide, how can I update from Magisk 20.4 to Magisk 23? My phone shows 22.1 as the latest.
Before updating do I need to restore Magisk Manager to the original package and app names?
Will updating Magisk affect my already installed Modules or will they stay in effect?
I'm using a Xiaomi with Android 9 Pie and MIUI Global 11.0.5.0
Thanks in advance.
reldinado said:
Hi everyone!
It's been about a year and a half since I first installed Magisk on my phone with TWRP and considering that I now noticed I'm getting SafenityNet API error, I wanted to update my Magisk to the latest version and install the Universal SafetyNet module as well to fix this issue.
I just have some questions regarding this:
I'm running Magisk Manager 7.5.1 & Magisk 20.4 repacked and with Magisk Hide, how can I update from Magisk 20.4 to Magisk 23? My phone shows 22.1 as the latest.
Before updating do I need to restore Magisk Manager to the original package and app names?
Will updating Magisk affect my already installed Modules or will they stay in effect?
I'm using a Xiaomi with Android 9 Pie and MIUI Global 11.0.5.0
Thanks in advance.
Click to expand...
Click to collapse
Maybe let Magisk Manager take you to v22.1, then you'll be one step away from v23.0 and hopefully at some point it becomes available. If upgrading to v22.1 succeeds you'll end up with one app that is Magisk SU and the manager all in one. I mention this in case you're wondering why Magisk Manager disappeared.
I don't understand what you mean about restoring Magisk Manager "to the original package and app names" but your modules should still work after upgrading. Worst case would be a module that didn't keep up with Magisk and isn't supported anymore.
reldinado said:
Before updating do I need to restore Magisk Manager to the original package and app names?
Click to expand...
Click to collapse
Yes, you do. See the v22.0 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
Didgeridoohan said:
Yes, you do. See the v22.0 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
Click to expand...
Click to collapse
Ahh, the question makes sense now. I've never needed to conceal Magisk.
Didgeridoohan said:
Yes, you do. See the v22.0 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
Click to expand...
Click to collapse
Thanks to both of you for the clarifications.
I will unhide/restore the manager and will install 22 before going onward to 23.

Categories

Resources