I installed the DP3 build a month ago or so along with Magisk so I could use Android Pay. Android Pay was working fine for a couple weeks and then about a week ago, between breakfast and lunch, Android Pay stopped working. I did a SafetyNet check with Magisk and it failed. Today I tried reflashing DP3 (without a full wipe) and installed Magisk (via TWRP) and SafetyNet is still failing. Short of reflashing DP3 with a full wipe, what else can I try to get SafetyNet check to pass?
greenmaze said:
I installed the DP3 build a month ago or so along with Magisk so I could use Android Pay. Android Pay was working fine for a couple weeks and then about a week ago, between breakfast and lunch, Android Pay stopped working. I did a SafetyNet check with Magisk and it failed. Today I tried reflashing DP3 (without a full wipe) and installed Magisk (via TWRP) and SafetyNet is still failing. Short of reflashing DP3 with a full wipe, what else can I try to get SafetyNet check to pass?
Click to expand...
Click to collapse
Although Android Pay may work on DP3 Google make it clear that it fails CTS which means it will always fail Safety Test. So Android Pay is not guaranteed.
https://developer.android.com/preview/release-notes
Android P beta devices*aren't*Compatibility Test Suite (CTS)approved, but they have passed preliminary testing and provide the same set of APIs for developers. Apps that depend on CTS-approved builds might not work normally on supported devices.
Sent from my Pixel 2 XL using Tapatalk
If I had this issue, I would flash a custom kernel. I'm currently on the latest Sultan's and haven't had any issues with safetynet whatsoever.
I had this issue briefly. Clear data for Google Play Services and Google Play Store, then reboot. It cleared it right up for me.
DuckRuckus said:
If I had this issue, I would flash a custom kernel. I'm currently on the latest Sultan's and haven't had any issues with safetynet whatsoever.
Click to expand...
Click to collapse
I installed this Kernel after a complete wipe and resintall of DP3 and still no luck.
lightningdude said:
I had this issue briefly. Clear data for Google Play Services and Google Play Store, then reboot. It cleared it right up for me.
Click to expand...
Click to collapse
I tried this. I even reinstalled DP3 with a full wipe and still no luck.
Try toggle magisk hide and exit app. Usually a reboot fixes it also.
So I downloaded the stable release and flashed that through TWRP, along with magisk. Everything went fine. But now I can't unlock my phone with my fingerprint, it always says "PIN required for more security".
I've removed all my fingerprints and re-added them, still the same thing.
Any ideas?
Edit: there was some conflicting magisk modules. I disabled everything and then rebooted and it works again.
Now I need to figure out which one is the problem.
alot of modules will need to be updated i found.
After I reboot my Google Pixel it loads into Android for a few seconds then goes to the Google logo and loads into Android again (Sometimes happening more than once before staying in Android). Is there any way I can fix this without flashing back to stock?
I have a few mods including Viper4Android, YouTube Vanced, EdXposed, Lucky Patcher, and Magisk hide props config. Could any of these be causing the problem?
Any help would be appreciated :laugh:
EDIT: I flashed back to stock and re-rooted and now I am not having this problem.
Hi,
I bought an X3 pro with a global rom, but as I really need a call recorder I have installed the xiaomi 12.5.1 rom. I'm really not an expert on phones but somehow I managed to do it. Also for whatever reasons I had the magisk manager installed as well which I have never really wanted to use.
I was pretty happy with the phone when on one day (ironically a day after I have just checked if my phone is rooted) my phone said I can't use NFC payments anymore. So I have decided to try some magic and fix the problem myself. Again, I'm not an expert but as far as I understood I have a problem with safety-net which I have managed to solve by installing magisk and setting up modules as I have seen on youtube.
Now my phone passes the safety-net check and my phone in the play app says its certified but I still can't pay with NFC and some of the banking apps are not working anymore which is pretty bad for me.
So the question I have in escence: how can I really restore my phone to the factory default 12.5.1 eu rom? I mean I dont need TWRP or anything unlocked, I'd just like to be a regular joe without superuser rights.
Thanks a lot for your help.
ps: not sure if that matters, but if I hit the update button or I'd like to perform a factory reset on my phone then it boots into TWRP.
Uninstall Magisk or Use Magiskhide also your Banking app hide it on the Magiskhide and playstore,
Just MiFlash stock ROM.
Thanks for responding. I have tried hiding Magisk, but that didnt help me with my banking apps. Then I have uninstalled it which made things even worse cause some other programs started to complain. As the phone was not rooted anymore (I guess) I thought it can't be anything except the unlocked bootloader so I had the genius idea to type something like 'adb oem lock' which immediately bricked my phone saying 'the system is destroyed'.
I was very lucky that I remembered that xiaomi unlocker tool which opened the bootloader and that magically still worked and my phone booted to TWRP. From there I just installed an EU ROM and now everything works perfectly fine.
So overall I spent about 20h with unlocking, intalling a new ROM, rooting etc and then another 10 with reinstalling the original ROM plus reinstalling my apps again! Kudos to me going back to square one
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.