I got a problem. My Google Pay app doesn't work. I got magisk v18 with 2 modules: "universal safetynet fix v3-beta1 (magisk v17 fix)" and google face unlock. When I check the status it shows the two "ctsprofile" and "basicintegrity" as true both. In magisk hide, I selected "Google Pay" and "NFC service" apps, but also without their selection it isn't still recognized by a pos. Now, I'm really sure my payment card works, my bro one with a phone unrooted works fine.
How should I do for make pos recognize my LG H815 rooted Gpay?
Sorry my bad english
p.s. I haven't any xposed or similar installed.
On my OP6 with OOS 9.0.3, CTS returns false without any additional modules and Google Pay and other apps detect root and refuse to work. That happened with the update from 17.2 to 18.0
Unfortunately, I got no helping hint in the main support thread or in the other thread here reporting on failing banking apps.
Later... after downgrading to Magisk 17.2, MagiskHide is working again... an issue is open on Github on that.
Yeah but gpay still not working in my phone, also with magisk 17.2
theicecave said:
Yeah but gpay still not working in my phone, also with magisk 17.2
Click to expand...
Click to collapse
I'll try that when I'm next time in a shop here... but as Safetynet works, GPay should too...
akxak said:
I'll try that when I'm next time in a shop here... but as Safetynet works, GPay should too...
Click to expand...
Click to collapse
And that's the paradox. Lemme know.
Just was at a shop and paid successfully with Google Pay. 17.2 rocks.
Idk why mine is not recognized by pos. And for sure I can say that my NFC works, I use it with my headsets. It's a problem with my phone, it's rooted, and that's it. Gpay cannot be used with root, although it accepted my card payment card after I protected my ctsprofile etc. I lost hope
My OP6 is unlocked and rooted with Magisk. Back on 17.2 SafetyNet checks succeed again and I just could pay... with Magisk 18 though it failed.
What phone and how did you root?
akxak said:
My OP6 is unlocked and rooted with Magisk. Back on 17.2 SafetyNet checks succeed again and I just could pay... with Magisk 18 though it failed.
What phone and how did you root?
Click to expand...
Click to collapse
Which module do you use to protect safetynet, ctsprofile etc?
Just asking.. 'cause, as I told, also with magisk 17.2 it doesn't work.
No module, just plain Magisk and MagiskHide on Google Pay.
akxak said:
No module, just plain Magisk and MagiskHide on Google Pay.
Click to expand...
Click to collapse
No module? I need necessary to use "universal safetynet fix" to activating all 4 green checks on main page of magisk. Without it, last 2 (inside safetynet fix) are red: ctsprofile:false and basicintegrity:false.
And magisk hide with or not selecting gpay doesn't change anything.
However I'm considering the main problem is my rom, resurrection remix.
On OOS I have only two arrows...
ctsProfile and basicIntegrity
But I am on a stock rom
Yeah sorry my bad, I mean just these two.
I'm considering to flash my stock rom again. But it was Android 6. I should set nova launcher and lots of changes to modernize it : D
Also my bro used a stock one to let gpay work. Modded all ones seems not working.
I'm on Android 9 Pie... Nova is great, I use it myself.. with starting on the Oneplus, I stuck to the stock OS and had gold experiences... on the OP6 even mire as I can update it and keep it rooted from within the OS not needing TWRP anymore... allowing an easy upgrade process.
Just flashed up the stock rom of my H815. I installed magisk 17.2 (it's an android nougat). I activated MagiskHide only for Google Pay; now safety net says ctsProfile: false and basicIntegrity: true. I watched this thread and just at beginning of section Safetynet fix - changing device fingerprint seems to be my problem. But my phone hasn't fingerprint (rofl). So after installing modules MagiskHide Props Config and Busybox by osm0sis cts is still false. Watched this because seems the only well built guide about; this problem is splitted anywhere. No more ideas.
theicecave said:
Just flashed up the stock rom of my H815. I installed magisk 17.2 (it's an android nougat). I activated MagiskHide only for Google Pay; now safety net says ctsProfile: false and basicIntegrity: true. I watched this thread and just at beginning of section Safetynet fix - changing device fingerprint seems to be my problem. But my phone hasn't fingerprint (rofl). So after installing modules MagiskHide Props Config and Busybox by osm0sis cts is still false. Watched this because seems the only well built guide about; this problem is splitted anywhere. No more ideas.
Click to expand...
Click to collapse
If I understand you correctly, I think you've misunderstood... It's not about a fingerprint scanner, it's the device fingerprint property that needs to change. You'll have to run the props script and select a certified fingerprint from the list (the module is not a flash and forget module). But if you're on a stock ROM I would expect the CTS check to pass, so there might be something else going on. Anyway, try changing the device fingerprint and see if anything changes.
Didgeridoohan said:
If I understand you correctly, I think you've misunderstood... It's not about a fingerprint scanner, it's the device fingerprint property that needs to change. You'll have to run the props script and select a certified fingerprint from the list (the module is not a flash and forget module). But if you're on a stock ROM I would expect the CTS check to pass, so there might be something else going on. Anyway, try changing the device fingerprint and see if anything changes.
Click to expand...
Click to collapse
Idk how to do this and where is this list. He just attached a .zip on his thread.
Or maybe I do not understand english enough. Very probably.
theicecave said:
Idk how to do this and where is this list. He just attached a .zip on his thread.
Or maybe I do not understand english enough. Very probably.
Click to expand...
Click to collapse
If you're talking about the thread you linked, the "he" is me...
Take a look in the module documentation, most things should be covered there. But basically, what you need is a Terminal emulator where you just type 'props' and press enter. After that you can just follow the ui to do the rest.
Didgeridoohan said:
If you're talking about the thread you linked, the "he" is me...
Take a look in the module documentation, most things should be covered there. But basically, what you need is a Terminal emulator where you just type 'props' and press enter. After that you can just follow the ui to do the rest.
Click to expand...
Click to collapse
Solved following this. In effect, not so different on what were you talking about in your guide. At the moment both ctsprofile and basicintegrity are true, I just need to try Google Pay in a pos.
Related
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.
I know other folks had issues with earlier updates, but this is the first time I've seen this. I skipped the last few updates. Does the Magisk patch method no longer work for rooting the Pixel 4 XL? Or is there some way to fix this?
The "hardware off" module from Displax might help you.
Sent from my Google Pixel 4 XL using XDA Labs
It's hardware based so nothing you can do about it
Patching your boot image with Magisk still works. With the recent implementation of hardware attestation, apps can now recognize if your bootloader is unlocked and safetynet checks result in ctsProfile failing. Magisk Hide still works and you can still hide root from most apps but cannot hide that your bootloader is unlocked unless you use either the hardwareoff mod or the Magisk Props mod.
Lughnasadh said:
Patching your boot image with Magisk still works. With the recent implementation of hardware attestation, apps can now recognize if your bootloader is unlocked and safetynet checks result in ctsProfile failing. Magisk Hide still works and you can still hide root from most apps but cannot hide that your bootloader is unlocked unless you use either the hardwareoff mod or the Magisk Props mod.
Click to expand...
Click to collapse
I tried MagiskHide Props Config but that didn't work - unless I need to do more than just replace the fingerprint. Replacing the fingerprint did not fix the problem. It's likely the Pixel 4 XL uses hardware backed key attestation to check the bootloader state, which I think means MagiskHide Props Config won't solve the problem.
I did find and install the hardwareoff mod and that fixed the problem. Thanks everyone who mentioned that. It was not available for download in Magisk but I found it buried deep in a 4000+ post thread on XDA.
https://forum.xda-developers.com/ap...systemless-t3432382/post83028387#post83028387
fuarkgl3 said:
It's hardware based so nothing you can do about it
Click to expand...
Click to collapse
Eventually you will be right, once Google makes hardware backed key attestation permanent. But for now the hardwareoff mod works.
No work for me
Basic integrity and CTS profile remains false.
madmartian said:
I tried MagiskHide Props Config but that didn't work - unless I need to do more than just replace the fingerprint.
Click to expand...
Click to collapse
Just for clarification: you would also have had to use the "Force BASIC attestation" option. It basically does the same thing as the hardware off mod, so you're good to go already...
So I have the same problem basic integrity but the cts profile fails. Iam in the January update.
I've done anything to fix it but 0 for me. And the problem is that it just happened from nowhere it was everything ok I was passing the safety net and in a moment the gpay made me a warning about contactless payments and the problem started.
Escribis said:
So I have the same problem basic integrity but the cts profile fails. Iam in the January update.
I've done anything to fix it but 0 for me. And the problem is that it just happened from nowhere it was everything ok I was passing the safety net and in a moment the gpay made me a warning about contactless payments and the problem started.
Click to expand...
Click to collapse
Go over to the Magisk thread. It's discussed there in detail and there has been a Magisk Mod released to fix it..
Lughnasadh said:
Go over to the Magisk thread. It's discussed there in detail and there has been a Magisk Mod released to fix it..
Click to expand...
Click to collapse
Can you give me the link my friend?
Lughnasadh said:
Go over to the Magisk thread. It's discussed there in detail and there has been a Magisk Mod released to fix it..
Click to expand...
Click to collapse
Found it, thank you very much sir.
Can you share the link please?
I also woke up to Google Pay warning, an update, than lost Magisk. I've re-installed it but now failing safetynet. Been attempting to fix it for 2 hours now
mushtafa said:
Can you share the link please?
I also woke up to Google Pay warning, an update, than lost Magisk. I've re-installed it but now failing safetynet. Been attempting to fix it for 2 hours now
Click to expand...
Click to collapse
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Found the link. It works, just need to setup Google Pay again https://github.com/kdrag0n/safetynet-fix
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.
I feel like I am at a loss and i need help,like 2 days ago I reverted back to stock from a custom rom on my pixel 4 xl and google play store keeps saying device not certified, now I have come across this issue before in the past and fixed it with guides posted on the internet but this time they are not working. here is everything I have done:
-registered device as per guides on the internet, cleared play store data and even play services data and rebooted. waited a literal day. rebooted and cleared data of both then rebooted again
- i redownloaded the april image and flashed it to both slots and manually wiped user data in fastboot, tried registering again and waited atleast 10 minutes before trying anything else
- downloaded march image and did everything listed above
- downloaded the android 12 dev beta and did everything listed above.
- tried making safetynet pass with magisk and stuff in between there
- checked safetynet right off the bat on a fresh flash with zero modifications and it failed too.
- as i am posting this i am flashing a fresh download of the april image + platform tools on a different computer and different cable
if anyone has any suggestions please let me know.
Did you flash the Universal SafetyNet Fix module after rooting? If not, try that. Also make sure you enable Magisk Hide in the Manager settings, clear data & cache of Play Store and reboot. Sometimes it takes a while for it to show up as certified.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Lughnasadh said:
Did you flash the Universal SafetyNet Fix module after rooting? If not, try that. Also make sure you enable Magisk Hide in the Manager settings, clear data & cache of Play Store and reboot. Sometimes it takes a while for it to show up as certified.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
i will give that a shot in a little bit here and update
Lughnasadh said:
Did you flash the Universal SafetyNet Fix module after rooting? If not, try that. Also make sure you enable Magisk Hide in the Manager settings, clear data & cache of Play Store and reboot. Sometimes it takes a while for it to show up as certified.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much that did the trick. I in all honesty did not know that module existed so thank you so very much! <3
Buddyjohn said:
Thank you so much that did the trick. I in all honesty did not know that module existed so thank you so very much! <3
Click to expand...
Click to collapse
No problem. Glad you got it going
Lughnasadh said:
No problem. Glad you got it going
Click to expand...
Click to collapse
I know im kinda late.. But gosh, thank you so much
Hi everyone! I have a rooted Pixel 7, with Magisk working perfectly. The only issue i have is with Google Wallet, even SafetyNetFix and Zygisk hide list didn't work. Can anyone with a rooted A13 device pay contactless?
Yes, it works perfectly with GPay/GWallet.
You shouldn't need to do anything else after enabling Zygisk, installing SafetyNetFix, then test if it passes the tests.
Which it should. If it doesn't, use the 2.3.1_MOD2-fix, not 2.4.0.
Had issues with 2.4.0 being inconsistent.
Download 'YASNAC' from the store, and run the test.
Does everything work?
If no, install 2.3.1_MOD2.
If yes, make sure you kill playstore and then wipe storage and buffer.
Do the same for gpay/wallet.
Reboot, and it should work.
Nothing should be added to the Zygisk hide-list.
Hi,
I also had the same problem.
Then I deleted the latest safetynetfix and used the version: v2.3.1
It works fine with this.
dmbardal said:
Yes, it works perfectly with GPay/GWallet.
You shouldn't need to do anything else after enabling Zygisk, installing SafetyNetFix, then test if it passes the tests.
Which it should. If it doesn't, use the 2.3.1_MOD2-fix, not 2.4.0.
Had issues with 2.4.0 being inconsistent.
Download 'YASNAC' from the store, and run the test.
Does everything work?
If no, install 2.3.1_MOD2.
If yes, make sure you kill playstore and then wipe storage and buffer.
Do the same for gpay/wallet.
Reboot, and it should work.
Nothing should be added to the Zygisk hide list.
Click to expand...
Click to collapse
Google Wallet still no worky after installing v2.3.1. Where can i find 2.3.1_MOD2?
LeoPeink said:
It doesn
Google Wallet still no worky after installing v2.3.1. Where can i find 2.3.1_MOD2?
Click to expand...
Click to collapse
https://forum.xda-developers.com/attachments/safetynet-fix-v2-3-1-mod_2-1-zip.5795137/
Link to comment by Displax:
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Installed 2.3.1_mod2.
YASNAC gives me "pass" on Basic Integrity but "Fail" on CTS profile match.
Google Wallet still gives me the "your device does not meet security requirements to pay contactless".
Any further advice?
EDIT: Hide Props Configuration Module is configured to spoof the device as a Pixel 6.
EDIT 2: I will install the Feburary update on my rooted phone, I'll retry when it is up to date so i dont have to mess with fingerprints. Thank you who helped
seanho12345 said:
Did you reboot the phone after clearing it? I've been wiping it a few time but it still not seemed to work.
Click to expand...
Click to collapse
dmbardal said:
https://forum.xda-developers.com/attachments/safetynet-fix-v2-3-1-mod_2-1-zip.5795137/
Link to comment by Displax:
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
LeoPeink said:
Installed 2.3.1_mod2.
YASNAC gives me "pass" on Basic Integrity but "Fail" on CTS profile match.
Google Wallet still gives me the "your device does not meet security requirements to pay contactless".
Any further advice?
EDIT: Hide Props Configuration Module is configured to spoof the device as a Pixel 6.
EDIT 2: I will install the Feburary update on my rooted phone, I'll retry when it is up to date so i dont have to mess with fingerprints. Thank you who helped
Click to expand...
Click to collapse
not work with me
salamdiab said:
not work with me
Click to expand...
Click to collapse
Dont use props-modules.
Can you post your setup?
Like I've posted mine here
dmbardal said:
Dont use props-modules.
Can you post your setup?
Like I've posted mine here
Click to expand...
Click to collapse
Here's my current Magisk hidelist and module setup. I'm using Shamiko for hiding apps from root
I've had gpay working this entire time used it yesterday around 6PM EST. This morning went to the gas station and got the error the device doesn't meet the software requirements.
Just saw the update for Shimako and Safety net fix. Just ran it and cleared Gpay and Google Play. All looks good just need to test it out now.
canibuz said:
I've had gpay working this entire time used it yesterday around 6PM EST. This morning went to the gas station and got the error the device doesn't meet the software requirements.
Just saw the update for Shimako and Safety net fix. Just ran it and cleared Gpay and Google Play. All looks good just need to test it out now.
Click to expand...
Click to collapse
I'll try again later with Shimako.
To test Google Wallet, you can remove your credit card and add it back: if it does not give you the "unable to pay contactless on this device" you should be clear.
LeoPeink said:
I'll try again later with Shimako.
To test Google Wallet, you can remove your credit card and add it back: if it does not give you the "unable to pay contactless on this device" you should be clear.
Click to expand...
Click to collapse
Just tested it out and it failed.
Can confirm that the new 3.0 MOD from Displax works flawlessly. I just installed it and everything is working.
https://github.com/Displax/safetynet-fix/releases/download/v2.3.1-MOD_3.0/safetynet-fix-v2.3.1-MOD_3.0.zip
seanho12345 said:
Can confirm that the new 3.0 MOD from Displax works flawlessly. I just installed it and everything is working.
https://github.com/Displax/safetynet-fix/releases/download/v2.3.1-MOD_3.0/safetynet-fix-v2.3.1-MOD_3.0.zip
Click to expand...
Click to collapse
Ok it passes tests and lets me add a card to Google Wallet without warnings. I'll try to pay ASAP
If anyone else sees this thread, keep up to date here: https://github.com/Displax/safetynet-fix/releases
The latest version is v2.4.0-MOD_1.2 and works across all devices (not just Google Pixel) for passing safetynet / google pay etc...