I have followed the instructions here to update my OnePlus6 from OOS 09.09 to OOS 10. It all worked fine and I lost no data, although it has a few quirks. Minor bugs that I expect will get fixed in a coming release. The problem is that my phone no longer passes the SafetyNet tests, and so I can no longer use my phone for Google Pay. Is anyone else having that problem?
To be very clear, when on the 9.09 release with TWRP and Magisk my phone passed the SafetyNet tests and GooglePay work just fine. Now, both the Basic Integrity and CTS Profile Match tests fail.
I am on oneplus 6 android 10 openbeta 1
With unlock bootloader and encrypted.
Magisk installed.
This mod work on my phone
Yes. Passed both CTS and BasicIntegrity
Yep, here too. Everything passes, and i can pay with Google Pay.
ButtonBoy said:
I have followed the instructions here to update my OnePlus6 from OOS 09.09 to OOS 10. It all worked fine and I lost no data, although it has a few quirks. Minor bugs that I expect will get fixed in a coming release. The problem is that my phone no longer passes the SafetyNet tests, and so I can no longer use my phone for Google Pay. Is anyone else having that problem?
To be very clear, when on the 9.09 release with TWRP and Magisk my phone passed the SafetyNet tests and GooglePay work just fine. Now, both the Basic Integrity and CTS Profile Match tests fail.
Click to expand...
Click to collapse
Are you using edxposed? Google made some updates and is detecting edxposed, disable it and see if safety net passes.
ptmaniac said:
Are you using edxposed? Google made some updates and is detecting edxposed, disable it and see if safety net passes.
Click to expand...
Click to collapse
No. I did have AdAway & FDroid installed, though. I removed both of those, and still no joy.
ptmaniac said:
Are you using edxposed? Google made some updates and is detecting edxposed, disable it and see if safety net passes.
Click to expand...
Click to collapse
Turn on 'App List' in experimental settings and add all Google apps to the blacklist. Especially Play Services, Play Store and Framework as they are the culprits that detect EdXposed. Leave out any other Google apps that you have Xposed mods for such as Gmail and Play Store Dark Themes.
Both Sim Cards are not being detected.
When I open SIM settings it shows, "com.android.phone keeps stopping".
I am using oxygen OS 10.3.0
with xXx No limits 9.5.
Other than that, I have magisk 20.2, edxposed 4.5.3, riru core 19.6, edxposed yahfa v4491.
The same issue also came the previous month when I was using oxygen OS 10.0.2 with xXx No limit 9.4.
I have noticed that it happens when the phone is switched off an then turned ON.
I have tried many things and searched everywhere but didn't find a solution other than full data wipe.
please help!!!
harshparmar said:
Both Sim Cards are not being detected.
When I open SIM settings it shows, "com.android.phone keeps stopping".
I am using oxygen OS 10.3.0
with xXx No limits 9.5.
Other than that, I have magisk 20.2, edxposed 4.5.3, riru core 19.6, edxposed yahfa v4491.
The same issue also came the previous month when I was using oxygen OS 10.0.2 with xXx No limit 9.4.
I have noticed that it happens when the phone is switched off an then turned ON.
I have tried many things and searched everywhere but didn't find a solution other than full data wipe.
please help!!!
Click to expand...
Click to collapse
I cleared cache in twrp and mine starting working again
Ultraman666 said:
I cleared cache in twrp and mine starting working again
Click to expand...
Click to collapse
I also wiped dalvik cache but same error exists...
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
6nchris said:
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
Click to expand...
Click to collapse
but I am not using call recorder module...
I am using cloudflare dns and xXx no limit module only
I think xxx hast it inclueded? Try deactivating magisk modules?
harshparmar said:
Both Sim Cards are not being detected.
When I open SIM settings it shows, "com.android.phone keeps stopping".
I am using oxygen OS 10.3.0
with xXx No limits 9.5.
Other than that, I have magisk 20.2, edxposed 4.5.3, riru core 19.6, edxposed yahfa v4491.
The same issue also came the previous month when I was using oxygen OS 10.0.2 with xXx No limit 9.4.
I have noticed that it happens when the phone is switched off an then turned ON.
I have tried many things and searched everywhere but didn't find a solution other than full data wipe.
please help!!!
Click to expand...
Click to collapse
This happened to me and after disabling all Magisk modules and rebooting I got it to recognize the SIM card again. I did dirty flash the ROM during this process with modules activated, but it didn't fix the issue until I deactivated all modules and rebooted. I think it was an issue with xXx, but when I installed xXx after detecting the SIM again I didn't have any issues.....
6nchris said:
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
Click to expand...
Click to collapse
god damn me that was it...it was driving me nuts. thank you!!
6nchris said:
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
Click to expand...
Click to collapse
That worked for me, thanks!
The OnePlus helpdesk was making a ticket to send the phone to recovery
I'm using a OnePlus 5. I also had the same problem after an OS update. The OnePlus Native Call Recording Magisk module was indeed the culprit!
Usually, I uninstall Magisk before an OS update. I got lazy and skipped this time. Oh, yeah, now I remember... Random time-wasting stuff like this happens half the time if I skip Magisk uninstall! Lesson learned.
I was able to use the Call Recording module again by uninstalling and then reinstalling Magisk.
HI,
Not sure if anybody can help me, but i recently tried to install edXposed and now my BasicIntegrity and CTS profile both fail safetynet. I uninstalled/removed riru - core and edXposed from magisk.
would a factory reset fix this?
actually i some how fixed it by clearing Google Play services cache and clearing Google Play Store Storage
Pls close thread
I had the same issue after installing /uninstalling edxposed. Cleared both and safetynet is back.
Sent from my HTC 10 using XDA Labs
I didn't think this would actually help but I had the same problem with my OnePlus Nord and it did.
Hello, admittedly I am new to the rooting scene and don't always know what to do. My main issue is Snapchat. It was working fine, then I had some problems with the notifications, so I uninstalled it. When I went to reinstall it and sign in, I got the error message. Now I can't sign back in on my OP7P no matter what I do. I've tried unrooting (although I don't know if I did it correctly) and that didn't work. I'm wondering if I Unroot and Lock the bootloader would that fix some of the issues? I was failing safetynet, so that could also be the issue, but I haven't found how to get safetynet not to fail.
TLDR- Snapchat login issue, Will Unrooting+Locking bootloader fix this? If so, how can I go about doing those things. Also, I would like to keep the root if I could, how can I start passing safetynet? I litterally have nothing installed besides Magisk and TWRP.
So the latest 31.0810.1226.77-1.1.138-2203 update has introduced Android 12..and killed Safetynet bypass. The kdragon Safetynet fix 2.2.1 no longer works and the device doesn't pass basic attestation either. Is there a workaround that doesn't involve unrooting it or are we ****ed for the time being? Goddamn Magisk had to deprecate their Magiskhide and safetynet bypass features. /rant
Just re-flash magisk should be enough. Else re-flash safetynet-fix-v2.2.1.zip after magisk.
course if you havent got TWRP installed you would have to re-flash the boot.img to get magisk working again.
I usually do that after every firmware update, reflashing the patched boot.img, and I already had the latest kdrag0n safetynet fix (2.2.1 as of now). This time after restarting on android 12, safety net failed and the Google pay app reported that my device is no longer certified. Guess I'll try again. Wait..is there finally now a TWRP for ROG 5? I miss using it from my old 1+3.
Edit - didn't work.
There is no TWRP for A12.
You will have to make a new patched boot image for A12. Go to Magisk and patch boot.img taken from Payload.bin (Payload dunper required) and flash it. That will get you root back.
Then you can use the universal safety net fix zip inside magisk.
BakaValen said:
Then you can use the universal safety net fix zip inside magisk.
Click to expand...
Click to collapse
Getting root on 12 is not the problem. The kdrag0n safetynet fix stopped working after upgrading to 12. I have the latest Zygisk version 2.2.1 that was updated last December.
I am on A12 latest. Rooted with safetynet passed using the fix. You must be doing something wrong.
Explain your process
Did the same process I've followed for every system update - patch boot.img with the payload dumper and patch script as described in this forum before applying the update, and flash it afterwards. The safetynet fix that had already been installed and working under 11 stopped, and removing and reapplying it does nothing.
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
BakaValen said:
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
Click to expand...
Click to collapse
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
KaiserSnorezay said:
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
Click to expand...
Click to collapse
Are you running Shamiko withLSPosed/Xprivacy + blocking tracking for Goog Play Services and the relevant apps? Safetynetfix 2.2.1 alone is no longer a full solution whether you're on A11 or A12 and regardless of your Magisk version...
If you mean adding play services to the deny list, then yes. Got rid of xprivacylua as it didn't help. Used it to block reading identifiers and tracking for play services and other components, to no avail. Right now even the basic integrity test is failing.
Update - Installed Shamiko, disabled the 'enforce denylist' in Magisk so that it takes over the job and rebooted..and nothing different.
Passed here just fine... all you need is a clean magisk install, then...
hide the magisk app itself.
enable zygisk, reboot.
flash zygisk version of usf https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
optionally: flash shamiko, reboot, then select play store and play service in deny list without enabling it.
check again in YASNAC, should pass now.
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
KaiserSnorezay said:
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
Click to expand...
Click to collapse
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Strephon Alkhalikoi said:
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Click to expand...
Click to collapse
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
I noticed that if I add Google play services (all components) to the Magisk deny list, it doesn't persist after reboot. Could that be it? Is it unable to modify the system partition? I'm using Shamiko, with Magisk enforce deny list option disabled.
Andrologic said:
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
Click to expand...
Click to collapse
It may be a glitch, as GPay is currently not complaining about root when I pull up one of my stored cards. Regardless, I don't have Shamiko installed, but will look into it so long as it doesn't require Xposed or any of its derivatives.
EDIT: Confirmed to be a glitch. Not more than five minutes prior to this edit I used GPay without trouble.
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
KaiserSnorezay said:
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
Click to expand...
Click to collapse
Same boat here. I got safetynet fix passed literally right after I disabled LSPosed. I glimpsed through the issues in LSPosed Github repo but they don't seem to be working on this.
I dont have any issues with safetynet.