Database Develop

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.

GPay Fix EU ROM

Anyone experiencing GPay issues on EU ROM, I got this working by updating the certificate.
Fingerprint payments - Widevine L1 - Update Certificate
Not tested in store yet, will report back when I get a chance
Before updating cert GPay check had cross on last point re phone security

This is the only thing that stopped me from unlocking the bootloader and flashing the EU Rom. I don't want any problems with GPay in the future so will stick with the Chinese Rom for now.

and this doesn't work for me. I'm going a bit crazy, I use Gpay religiously.
Any ideas?

Just flash back the latest Chinese stock ROM until a fix is found.

I am on the eu rom, with latest magisk, the modified trwp for thos device, and the latest Edxpos3d Canary build installed as well. Initially had an issue with with Pokemon Go not working and Gpay stopped working after I realized that Cts profile in Magisk wasn't passing anymore. I also use Workspace for work and it wouldn't work as well. My Chase and Barclays app worked fine though. I reinstalled the EU Rom again through Twrp and Gpay and Pokemon go worked again with location spoofer as well using Smali Patcher. But today at these store after trying to used Gpay I kept on receiving an error stating thaty device was modified. I tried Rehiding Magisk, installing random Safety Modules to pass safety and it still wouldn't pass. I just installed the MagiskHide Props module from Magisk and I changed my fingerprint to prop to the Pixel 4xls, restarted the phone, and now my Pokemon Go and Gpay work again as well as Passing the Cts Profile in Magisk. I also Forced Basic key attestation in the MagiskHide props module using terminal. The command in terminal for this module is used by executing "su" (without quotes) for root access in terminal and then running command "props" without quotes

offiiciallialngl said:
I am on the eu rom, with latest magisk, the modified trwp for thos device, and the latest Edxpos3d Canary build installed as well. Initially had an issue with with Pokemon Go not working and Gpay stopped working after I realized that Cts profile in Magisk wasn't passing anymore. I also use Workspace for work and it wouldn't work as well. My Chase and Barclays app worked fine though. I reinstalled the EU Rom again through Twrp and Gpay and Pokemon go worked again with location spoofer as well using Smali Patcher. But today at these store after trying to used Gpay I kept on receiving an error stating thaty device was modified. I tried Rehiding Magisk, installing random Safety Modules to pass safety and it still wouldn't pass. I just installed the MagiskHide Props module from Magisk and I changed my fingerprint to prop to the Pixel 4xls, restarted the phone, and now my Pokemon Go and Gpay work again as well as Passing the Cts Profile in Magisk. I also Forced Basic key attestation in the MagiskHide props module using terminal. The command in terminal for this module is used by executing "su" (without quotes) for root access in terminal and then running command "props" without quotes
Click to expand...
Click to collapse
interesting - changing the build.prop passes CTS? If so then it can be fixed with next EU rom release

offiiciallialngl said:
I am on the eu rom, with latest magisk, the modified trwp for thos device, and the latest Edxpos3d Canary build installed as well. Initially had an issue with with Pokemon Go not working and Gpay stopped working after I realized that Cts profile in Magisk wasn't passing anymore. I also use Workspace for work and it wouldn't work as well. My Chase and Barclays app worked fine though. I reinstalled the EU Rom again through Twrp and Gpay and Pokemon go worked again with location spoofer as well using Smali Patcher. But today at these store after trying to used Gpay I kept on receiving an error stating thaty device was modified. I tried Rehiding Magisk, installing random Safety Modules to pass safety and it still wouldn't pass. I just installed the MagiskHide Props module from Magisk and I changed my fingerprint to prop to the Pixel 4xls, restarted the phone, and now my Pokemon Go and Gpay work again as well as Passing the Cts Profile in Magisk. I also Forced Basic key attestation in the MagiskHide props module using terminal. The command in terminal for this module is used by executing "su" (without quotes) for root access in terminal and then running command "props" without quotes
Click to expand...
Click to collapse
Have you commented on the bug list for the 10 ultra in the Xiaomi.EU forum to let them know how you fixed yours? It is them who can get it added to the next fixes

Hello, thanks a looot for sharing your solution!
I've a little problem with this part: "and I changed my fingerprint to prop to the Pixel 4xls"
I don't find whereor how change this setting!
Please could you let me know how?
Thanks you so much!
Inviato dal mio M2007J1SC utilizzando Tapatalk

I haven't posted how I fixed this on the Xiaomi EU forum.
The curious thing is that I bootlooped my phone two days ago by installing the Viper Module from Magisk and again I couldn't pass the Cts profile in Magisk. My safetynet failed. Pokemon Go would keep on asking me to login and Gpay wouldn't work.
I fixed this again by using MagiskHide Module but this time using the latest Magisk Canary build. The normal Magisk 20.4 works fine as well.
The fix is to root your phone using Magisk, install Magisk via Twrp, install the Magisk Manager Apk. Once in Magisk Manager install the HideMagisk Module.
Also have a terminal app installed. Once you have gotten to this step in terminal run command "su" without quotes.
After execute command "props"
Follow the instructions that the terminal gives to you but only updating Force Basic Key Attestation and change the Fingerprint prop value. Both values can be set to the Pixel 4xls. This only seems to break Google Chrome for me. I can only fix the chrome issue by uninstalling the MagiskHide Prop.
Installing Edexposed after all of this breaks everything again so don't attempt to install Edxposed. It breaks SafetyNet.

Any news about a Google Pay fix? Thanks a lot
Inviato dal mio M2007J1SC utilizzando Tapatalk

So is Gpay working on EU rom?
Do you have to root your phone to install the EU rom?
The issue is with the rom or the root?
Thanks

Tried today at 5 Guys, the phone scanned about 30cm from the card reader.
No issues.

I've finally fixed Gpay or it seems working now...
Thanks a lot to this thread and the authors!!!
So after installing Magisk and MagiskHide (i've activated it and also selected every Google app in my phone, also if unecessary), I've used a terminal app, like Termux, then I've typed:
Su
Props
In this menu I've changed the fingerprint profile with Google Pixel 4x (worked for me), then I've enabled "Force the basic key attestation", rebooted the smartphone and WOW!
Cts profile fixed!!!
Thanks a lot!!!!
NOTE: I think the most important part after Magisk and MagiskHide was enable "Force Basic key attestation", so perhaps is unuseful change also the fingerprint profile... How I can re-set the original profile in Mi 10 Ultra?

Same fixed I posted on another thread and this one for this forum. Glad it worked for you as well. So it confirms that changing the prop values fixes this issue

I'm running 20.9.3and this doesn't work for me. I'm going a bit crazy, I use Gpay religiously.
Security Screen on gpay
Error I get
All my certs are up to date
Any ideas?
Click to expand...
Click to collapse
Exact same issue here. Any solution would be great SafetyNet passed, Widevine L1 but still

It seems to be an issue with the (for now latest weekly) 20.9.24 eu rom. This didn't seem to happen with the first weekly (20.9.3) and the latest stable rom (xiaomi.eu_multi_MI10Ultra_V12.0.10.0.QJJCNXM_v12-10) also doesn't seem to have safetynet or L1 problems. Thus no need to root the device with either of those roms to solve the issue. Imo, rooting to solve the issue is creating another issue which needs constant attention and thus a bigger problem (security risk) than the one it is supposed to be a sollution for.

In my opinion some ppl like to take risk while modifying their device. I root my phones for the purpose of breaking it and fixing in while it being my daily driver.
Just like why unlock the bootloader on your device if you are already compromising the security of your device for trying to install the eu rom.

Appelsap said:
It seems to be an issue with the (for now latest weekly) 20.9.24 eu rom. This didn't seem to happen with the first weekly (20.9.3) and the latest stable rom (xiaomi.eu_multi_MI10Ultra_V12.0.10.0.QJJCNXM_v12-10) also doesn't seem to have safetynet or L1 problems. Thus no need to root the device with either of those roms to solve the issue. Imo, rooting to solve the issue is creating another issue which needs constant attention and thus a bigger problem (security risk) than the one it is supposed to be a sollution for.
Click to expand...
Click to collapse
Are you sure that V12.0.10.0 has no problems? As I have 20.9.3 and it's broken for me.

Odd, it was fine with that beta for me earlier, just did a check and the 12.0.10.0 now fails the CTS - although I haven't had any problems with it. Widevine is still L1 though.
Verstuurd vanaf mijn M2007J1SC met Tapatalk

For me this worked fine. I had no Problems. I just flashed the eu rom and it worked fine out of the box.

Question [Solved] Root and Gpay?

Hi guys
I recently decided to root my Exynos S21U, all fine to far but I'm fighting to get Google Pay to work properly - so far without success.
Has anybody here got a rooted S21U with working Gpay and could kindly share what you did to make it work?
Thanks,
Axel

U dont need root to have google pay.
Download apk from here and install it on your device:
https://apkpure.com/google-pay/com.google.android.apps.walletnfcrel

Beso said:
U dont need root to have google pay.
Download apk from here and install it on your device:
https://apkpure.com/google-pay/com.google.android.apps.walletnfcrel
Click to expand...
Click to collapse
I don't think he's rooting to get Google Pay.
He wants a rooted phone, but is dealing with the side effect that it renders GPay un-usable.
Correct me if I'm wrong @s3axel
BTW @s3axel , have you tried Magisk Hide?

Yes, my device is rooted and I want to get Gpay to work
What I tried so far, all without success (of course all With Magisk Hide enabled for at least Gpay, Google Play Services and Google Framework)
- Magisk Stable
- Magisk Canary
- Props Magisk module
- Safetynet Fix 1.1.1
Funny enough everything is working fine in my other phone (Mi11U) with Magisk Stable and Magisk Hide enabled, nothing else...
Thus I was curious for reports from people who use their S21U rooted and with Gpay to learn what I need to do.....

s3axel said:
Yes, my device is rooted and I want to get Gpay to work
What I tried so far, all without success (of course all With Magisk Hide enabled for at least Gpay, Google Play Services and Google Framework)
- Magisk Stable
- Magisk Canary
- Props Magisk module
- Safetynet Fix 1.1.1
Funny enough everything is working fine in my other phone (Mi11U) with Magisk Stable and Magisk Hide enabled, nothing else...
Thus I was curious for reports from people who use their S21U rooted and with Gpay to learn what I need to do.....
Click to expand...
Click to collapse
It's possible to make it work (I'm on S21 Ultra 5G, latest Magisk canary, AUC8).
Follow these instructions to the letter and you'll get going ;-)
Working: Magisk with Google Pay as of gms 17.1.22 on Pie
Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and...
forum.xda-developers.com
By the way, once you succeed in make it work, I suggest you update the thread title with something like [SOLVED] or [WORKING], so other newcomers can benefit from it

rodrigofd said:
It's possible to make it work (I'm on S21 Ultra 5G, latest Magisk canary, AUC8).
Follow these instructions to the letter and you'll get going ;-)
Working: Magisk with Google Pay as of gms 17.1.22 on Pie
Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and...
forum.xda-developers.com
By the way, once you succeed in make it work, I suggest you update the thread title with something like [SOLVED] or [WORKING], so other newcomers can benefit from it
Click to expand...
Click to collapse
Thanks, this worked fine once I found the correct Magisk module
Just for reference flashing this module did its magic and kept the fingerprint in 3rd party apps working...

Safetynet fail

Hello,
today my phone suddenly wrote to me that it is no longer possible to use google pay.
Phone Pixel 5. Stock firmware.
Google pay reports that the device is certified.
I use magical canary 23001. I have the safetynet fix module installed.
Google pay does not work. And magisk reports an error when verifying the safetynet.

matata86 said:
Hello,
today my phone suddenly wrote to me that it is no longer possible to use google pay.
Phone Pixel 5. Stock firmware.
Google pay reports that the device is certified.
I use magical canary 23001. I have the safetynet fix module installed.
Google pay does not work. And magisk reports an error when verifying the safetynet.
Click to expand...
Click to collapse
Android 11?
Why using Canary?
Magisk v23 works perfectly.

Try this Safetynet Test App and see what it says.

Looking for some tips - Unable to get these two Belgium apps working with Magisk

Hi,
I live in Belgium and it's been years that I'm using Cyanogen, then now Lineage. Recently, I made a bargain and bought 2 Google Pixel 4a, one for me and one for my girlfriend.
I installed Lineage on both of them, and I have to say that it's the best Android experience I had so far. We both love our device. It's small, powerful enough, camera pictures are amazing.
However, we are unable to get any banking apps working. We would like to use 2 applications:
1. Payconiq: https://play.google.com/store/apps/details?id=mobi.inthepocket.bcmc.bancontact&hl=en&gl=US
2. Keytrade: https://play.google.com/store/apps/details?id=be.keytradebank.phone&hl=en&gl=US
I succeeded to get Payconiq working on my phone, using Magisk 23 and Magisk hide. So far so good.
Since this morning, Magisk has been updated to 24.1, Magisk hide is gone and I have to use Magisk Zygisk... And Payconiq doesn't work anymore.
Regarding the second app "Keytrade", it never worked, with any version of Magisk. I don't know what they did in their app, but it seems that they were able to find a way to detect if a phone has a custom rom pretty nicely.
Maybe this is something that the author of Magisk should be aware of? Maybe I'm doing something wrong?
Do you have any piece of advice for me? I don't want to be forced to re-install the official rom, I still want to use Lineage and have those apps working.
Thanks!
Edit 1: After installing Universal Safetynet fix (https://github.com/kdrag0n/safetynet-fix), payconiq works, but not Keytrade.

Easiest way is to use a good browser like Brave to login to the bank's website bypassing the app.
I consider banking apps to be trash apps and never load them. The more needless apps you load, the greater the security risk.
Apps I sometimes use but don't like their behavior I package block when not in use and/or firewall block.
Rather than fight it, bypass it...

blackhawk said:
I consider banking apps to be trash apps and never load them.
Click to expand...
Click to collapse
Not helpful, because thanks to EU rules many banks simply and mandatorily require their app as the second authentication factor - especially when you don't want to use their "real" banking app and use the oldfashioned web interface instead.

Ramihyn said:
Not helpful, because thanks to EU rules many banks simply and mandatorily require their app as the second authentication factor - especially when you don't want to use their "real" banking app and use the oldfashioned web interface instead.
Click to expand...
Click to collapse
That sucks... so much for easy fixes

The Transporter said:
Hi,
I live in Belgium and it's been years that I'm using Cyanogen, then now Lineage. Recently, I made a bargain and bought 2 Google Pixel 4a, one for me and one for my girlfriend.
I installed Lineage on both of them, and I have to say that it's the best Android experience I had so far. We both love our device. It's small, powerful enough, camera pictures are amazing.
However, we are unable to get any banking apps working. We would like to use 2 applications:
1. Payconiq: https://play.google.com/store/apps/details?id=mobi.inthepocket.bcmc.bancontact&hl=en&gl=US
2. Keytrade: https://play.google.com/store/apps/details?id=be.keytradebank.phone&hl=en&gl=US
I succeeded to get Payconiq working on my phone, using Magisk 23 and Magisk hide. So far so good.
Since this morning, Magisk has been updated to 24.1, Magisk hide is gone and I have to use Magisk Zygisk... And Payconiq doesn't work anymore.
Regarding the second app "Keytrade", it never worked, with any version of Magisk. I don't know what they did in their app, but it seems that they were able to find a way to detect if a phone has a custom rom pretty nicely.
Maybe this is something that the author of Magisk should be aware of? Maybe I'm doing something wrong?
Do you have any piece of advice for me? I don't want to be forced to re-install the official rom, I still want to use Lineage and have those apps working.
Thanks!
Click to expand...
Click to collapse
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com

Austinredstoner said:
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Click to expand...
Click to collapse
Safetyfix passes on the phone... I don't know how the Keytrade app is doing to detect root on the phone.

blackhawk said:
That sucks... so much for easy fixes
Click to expand...
Click to collapse
So true Unfortunately, that seems the way to go in Europe considering banking. If you want it online instead of running to the bank clerk all the time, you're stuck with at least some authentication app. Things get only worse when there's no classical webinterface at all and you're bound to use a complete banking app instead (there are some neobanks doing so already).
The Transporter said:
I don't know how the Keytrade app is doing to detect root on the phone.
Click to expand...
Click to collapse
They simply recognize Magisk app in some way. I've read in some other threads here that a probable solution is to use the app called "Ice Box" to hide the Magisk app by freezing it. Might be worth a try for you.

Another way if you have zygisk enabled. Go to config denylist select play store play services gms you need to hit menu system apps first. And you apps you wish to hide. Then search magisk alpha telegram channel. Download shamiko module. Reboot your phone with enforce denylist selected. After reboot turn the enforce denylist toggle off and flash the shamiko module and reboot. If your app still does not work and you are using lsposed zygisk. You can download hide my applist Xposed module and further hide your app.
Pm me if you want to links to all as they are not supposed to be posted on xda

Have you managed to fix this?
I'm in the same boat.
My bank app 'keytrade bank' keeps detecting that I've rooted my device. This is what I tried
- I installed Magisk
- Installed module Shamiko
- Installed SafetyNet Fix v2.2.1
- Enabled Zygisk
- Configured DenyList
- Hide Magisk app

Awaces said:
Have you managed to fix this?
I'm in the same boat.
My bank app 'keytrade bank' keeps detecting that I've rooted my device. This is what I tried
- I installed Magisk
- Installed module Shamiko
- Installed SafetyNet Fix v2.2.1
- Enabled Zygisk
- Configured DenyList
- Hide Magisk app
Click to expand...
Click to collapse
You have to disable Enforce DenyList in Magisk.