EDIT: TOPJOHNWU IS WORKING ON A FIX RIGHT NOW, WAIT FOR MAGISK 13 RELEASE OR ENABLE CORE ONLY MODE AS A TEMP FIX.
Posting this from my phone so sorry for any errors here.
Google seems to have updated safetynet within the last few hours, on 2 devices. That previously passed with magisk. There is an easy way to fix it, that I don't really want to post here as Google probably read the forums. Let's just say it's easy to fix, but you not using modules any more. Hoping for an update soon if that's possible and I can provide any logs or details to the dev if needed.
manor7777 said:
Posting this from my phone so sorry for any errors here.
Google seems to have updated safetynet within the last few hours, on 2 devices. That previously passed with magisk. There is an easy way to fix it, that I don't really want to post here as Google probably read the forums. Let's just say it's easy to fix, but you not using modules any more. Hoping for an update soon if that's possible and I can provide any logs or details to the dev if needed.
Click to expand...
Click to collapse
Yeah, it seems like Google has updated SafetyNet, now I can't pass the check
Sent from my Pixel using Tapatalk
Same here.
Using Galaxy s6, same here.
Thanks it works
Glad to know I'm not the only one. They will probably patch what I've done later on but at least I can still use my phone with root. Can back to stock as I'm on a OP3T but I don't want to lol
So i need to uninstall my youtube ad free module?
bam099 said:
Same here.
Click to expand...
Click to collapse
Yep... may not be related, but noticed random "unable to parse data" toast messages earlier today. Later caught google play downloading. Killed download, then ran safetynet check. Failed CTS profile mismatch. Again, any of those symptoms could be unrelated. Just reporting anomalies.
bummer
Nexus 6 running Pure Nexus 7.1.2 on Magisk v12.0
SafetyNet Failed: CTS profile mismatched
Yeah, looks like another swing from Google.
how can i pass safteynet i cant get to hide my root to log into snapchat
Same here it definitely updated. Haven't done anything with my phone in a while. Suddenly failing the check
I thought i was the only one
If you can live without modules, enable 'Magisk Core Only Mode' in Settings and you'll pass SafetyNet again.
Works but..
blk_jack said:
If you can live without modules, enable 'Magisk Core Only Mode' in Settings and you'll pass SafetyNet again.
Click to expand...
Click to collapse
I have a problem with Mario run, safetynet pass And magisk hide is enabled but Mario run always give me the 804-5100 error code
Btw, it seems not all modules trigger SafetyNet. My suggestion to people is to test each module one at a time and see which are affected.
To do this:
- Disable all modules
- Enable the first module
- Reboot
- Check if SafetyNet passes
- Disable the first module and enable the second
- Reboot
- Check if SafetyNet passes
- Repeat.......
angelus_kun said:
I have a problem with Mario run, safetynet pass And magisk hide is enabled but Mario run always give me the 804-5100 error code
Click to expand...
Click to collapse
Maybe try clearing data in the game. You might have tripped a flag and the game is remembering that your device has failed.
blk_jack said:
Maybe try clearing data in the game. You might have tripped a flag and the game is remembering that your device has failed.
Click to expand...
Click to collapse
Nope, i tried that before And dosen't work, irñts very strange because on my moto G4 with magisk hide And safetynet pass i was able to play without issues until now, And i don't know why because i have the same modules like before, And i have the same issue on my galaxy Tab A6 t280 with the same modules, safetynet pass etc :\
---------- Post added at 03:10 AM ---------- Previous post was at 02:42 AM ----------
andybfmv96 said:
Same here it definitely updated. Haven't done anything with my phone in a while. Suddenly failing the check
Click to expand...
Click to collapse
Mario run work again i solved the issue deleting all modules enable magisk core And systemless host (for adaway at least) magisk hide with Mario run selected, clear Mario run data And reboot oh Well :/ bye bye to ad away OGyoutube module
angelus_kun said:
Nope, i tried that before And dosen't work, irñts very strange because on my moto G4 with magisk hide And safetynet pass i was able to play without issues until now, And i don't know why because i have the same modules like before, And i have the same issue on my galaxy Tab A6 t280 with the same modules, safetynet pass etc :\
---------- Post added at 03:10 AM ---------- Previous post was at 02:42 AM ----------
Mario run work again i solved the issue deleting all modules enable magisk core And systemless host (for adaway at least) magisk hide with Mario run selected, clear Mario run data And reboot oh Well :/ bye bye to ad away OGyoutube module
Click to expand...
Click to collapse
Did you even read OP's post? Google updated a security patch and now most of us can't pass SafetyNet.
MiuKing said:
Did you even read OP's post? Google updated a security patch and now most of us can't pass SafetyNet.
Click to expand...
Click to collapse
Yes And the solution is don't use modules anymore that work for me And you And everyone Even if you pass safetynet you need to enable magisk core to use broken apps like Mario run
I can confirm that enabling "Core Only Mode" in Magisk Settings does pass SafetyNet.
(Sigh), now magisk modules break SafetyNet. Now what do we do?
Related
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.
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
Hey guys!
I recently flashed my Galaxy Note9 (SM-N960F, One UI 2.5) with TWRP and Magisk, all being the latest version. However my phone would just reboot randomly and I could barely find a pattern. I could only infer that the reboot is system level since most of the time I was launching a system-level app like Bixby, Torch, or just simply swipe down the notification panel. If related, 19:30 seems to be the time my phone would definitely reboot recently.
By ''partly goes back to a previous state' I mean some of my apps would be replaced to their factory version. Like I used YouTube Vanced, and after this one reboot it went back to its factory version. And Gboard was exiled of all its permissions once. My Edge Panel was reset after one boot. Some of the adb tweaks were reset.
I'm half sure this is a kernel problem, and the only modifications I did to my kernel were Magisk and Universal DM-Verity. I don't know if it's a DM-Verity problem.
I tried to disable my root permission for apps but it didn't help. Also Googled how to catch system logs but none of these worked.
If you're experiencing the same problem or have an idea of how to solve this issue please feel free to leave a comment!
Maspon said:
Hey guys!
I recently flashed my Galaxy Note9 (SM-N960F, One UI 2.5) with TWRP and Magisk, all being the latest version. However my phone would just reboot randomly and I could barely find a pattern. I could only infer that the reboot is system level since most of the time I was launching a system-level app like Bixby, Torch, or just simply swipe down the notification panel. If related, 19:30 seems to be the time my phone would definitely reboot recently.
By ''partly goes back to a previous state' I mean some of my apps would be replaced to their factory version. Like I used YouTube Vanced, and after this one reboot it went back to its factory version. And Gboard was exiled of all its permissions once. My Edge Panel was reset after one boot. Some of the adb tweaks were reset.
I'm half sure this is a kernel problem, and the only modifications I did to my kernel were Magisk and Universal DM-Verity. I don't know if it's a DM-Verity problem or I just disabled too many system apps (Galaxy Themes, Bixby Service, Galaxy Friends and stuff).
I tried to disable my root permission for apps but it didn't help. Also Googled how to catch system logs but none of these worked.
Whether you're experiencing the same problem or have an idea of how to solve this issue please feel free to leave a comment!
Click to expand...
Click to collapse
Happened to me as well few months ago.
I suspect it is related to safetynetfix or hideprop. I used safetynetfix for samsung, and update latest hideprop, now i never experienced the random reboot.
xfakexbloodx said:
Happened to me as well few months ago.
I suspect it is related to safetynetfix or hideprop. I used safetynetfix for samsung, and update latest hideprop, now i never experienced the random reboot.
Click to expand...
Click to collapse
Thanks for the reply! I just flashed Universal SafetyNet Fix. Now my phone is stuck in bootloop. It would just reboot infinitely. May I possibly get the SafetyNet Fix you're using?
Maspon said:
Thanks for the reply! I just flashed Universal SafetyNet Fix. Now my phone is stuck in bootloop. It would just reboot infinitely. May I possibly get the SafetyNet Fix you're using?
Click to expand...
Click to collapse
Based on this post
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
Try to read each page, some people say it works, some people say it doesn't. I've tried and updating my magiskhide prop and it works.
xfakexbloodx said:
Based on this post
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
Try to read each page, some people say it works, some people say it doesn't. I've tried and updating my magiskhide prop and it works.
Click to expand...
Click to collapse
Thanks a lot! My phone now boots normaly and it's a Success on SafetyNet. Hope no more random reboots afterwards.
I'm particularly curious what variant of DM-Verity did you use? I googled for DM-Verity for Samsung this morning and did get a Samsung-only patch. I'm not sure if DM-Verity patch could contribute to these reboots.
Maspon said:
Thanks a lot! My phone now boots normaly and it's a Success on SafetyNet. Hope no more random reboots afterwards.
I'm particularly curious what variant of DM-Verity did you use? I googled for DM-Verity for Samsung this morning and did get a Samsung-only patch. I'm not sure if DM-Verity patch could contribute to these reboots.
Click to expand...
Click to collapse
Sorry no idea about that. I'm using alexis rom though..
xfakexbloodx said:
Sorry no idea about that. I'm using alexis rom though..
Click to expand...
Click to collapse
Sadly my phone still rebooted this morning. I caught the last kernel message and I hope it will help
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...