yashsingh1/xdaforums huggingface dataset:
[Magisk] ManovSteele:
I just installed the safetynet-fix-v1.2.0-MOD as a magisk module but doesn't look like it's worked on my Poco X3 running ArrowOS - fails on cts profile.

Edit: just tried the shim version and it's worked fine! Rebooted, cts pass, cleared data from Google Pay and it's like it was never blocked! Amazing work, thanks!
[Magisk] pndwal:
If you have restored full S/N pass, check that Google Pay is checked in MagiskHide list, then that Play Protect certification (in Play Store settings) says 'Device is certified'.

If not certified, clear PlayStore data to reset, check Device is certified, then clear Google Pay data again and it should be fixed! 😜 PW
[Magisk] conizius:
Got it workin with the old "hardware_off" module and XPrivacy.

Xiaomi 9T Pro with EvolutionX

Have XPrivacy running over LSPosed with following Play Services restrictions:

• Determine Activity

• Read identifiers

• Use analytics and

• Use tracking

"Universal SafetyNet Fix" variations with "MagiskHidePropsConf" didn't do the job for me.

After deletion of Google Play Services data GPay seems to work (had to add the cards again but it worked).
[Magisk] jonske:
so my phone is failing the safety net test, yet i am still able to use Gpay and Play store still reports device is still certified. is this normal?

Poco X3 NFC using PixelExperience ROM
[Magisk] pndwal:
It will probably fail with Device is not certified soon. If you want to test this, you can force immediate check / reset by clearing Play Store data. 😜

Nb. This assumes real Check SafetyNet failure, not SafetyNet API error / evalType = N/A. PW
[Magisk] 73sydney:
I decided for the moment i dont need drama or excitement, so im still rocking the previous alpha, my particular setup has a few moving parts where i dont need to throw it against the wall and see what sticks right now

Everything still works...
[Magisk] ibrahm24:
Sorry for noob question, is this caused by a new version of gapps / google framework? Can I avoid it if use an older gapps version and don't update it?
[Magisk] Foglito:
Used the shim file on my Note 20 Ultra 5G Exynos with Dr. Ketan R09 rom. Works like a charm. Thank you!
[Magisk] Inervo:
Thanks for the help :)

Google pay was Magiskhide, play protect certification okay. I found the issue : i had to clear Google Play Services data, not just Google Play data.
[Magisk] pndwal:
No and no. It's a server-end change. PW
[Magisk] jonske:
yeah im getting cts profile fail. what do i do to stop the inevitable happening :O
[Magisk] drmarble:
This fixes ctsProfile mismatch on moto one action.

Many thanks.
[Magisk] mido67:
Please follow exactly this tutorial...

[MODULE] Fix CTS Profile Match Fail - Play Integrity Fix

To Fix CTS Profile Match Fail issue and to fix "Play Integrity", use the Magisk Module mentioned in this article. This Magisk module will help to get...

droidholic.com

Works for mi8 with latest PE rom. :)
[Magisk] MariusWildfire:
yes! can confirm, its working on my op6t with latest PE rom :)
[Magisk] _Kuroi_:
Modded safetynet fix did not help on Zenfone 6
[Magisk] ReservedName:
I think the LSPosed route is causing some delay in email/messaging notifications I might have to try the modded kdragon usnf
[Magisk] Dorisnov:
I forgot to tell that with LSposed worked, but I wanted to make it work without having to use LSposed. TY.
[Magisk] zagi988:
Xperia XZ1 with PixelExperience has troubles.

Don't know what else except device fingerprint should I use from MagiskProps module, maybe something from Device simulation? Since this ROM reports to Google like it's a Pixel 5... Should I tell it to pretend to be Pixel or Xperia?

Tried the Universal Fix versions, doesn't work.
[Magisk] asripath:
maybe a bit offtopic

since we all are riled by current situation with safetynet

before jumping onto the lsposed workaround

take a few moments to go thru an interesting thread

https://xdaforums.com/t/something-about-lsposed.4236335/
[Magisk] Jon8RFC:
Displax's mod fix worked for me on pixel 5.

I also needed to clear data for play store and play services for the store to become "certified" again.

Gpay tap to pay from power button was fixed with this: https://github.com/stylemessiah/GPay-SQLite-Fix

Although, maybe I didn't need the Gpay fix and an additional reboot would've done it. I didn't wipe cards info when it prompted me, or whatever the "if you choose this, it might not still work", but it worked.
[Magisk] klemi71:
Besides the safety net issue: I want to wait to avoid changing Magisk every day. What version to install to receive updates? Stay on John's official v23 or switch to alpha. So far everything works with v23. Which will be the official future version? I know I'll have to see what happens concerning hide feature.

Best regards.
[Magisk] zgfg:
To summarize how to fix broken SafetyNet (assuming SN worked for you till day or two ago, and now got broken by Google changing things on their side)

In short (for details, search and read for details in the corresponding posts):

1) Method by @Displax is simpler, it uses well known USNF + mingling up to three props (for some, only ro.product.model would be enough).

However, that method does not re-fix broken SN for all who tried

2) Method originating from TeamFiles is more complicated, it requires installing and properly configuring riru, LSposed and XPrivacyLua, but all who dared to try (not just in this thread but also in USNF thread and elswehere - I've seen on Telegram, Xiaomi.eu forum, etc) were able to re-fix the broken SN

Hence, it makes sense to try (1), and if no success, dive to (2)

---

I'm too lazy and in hurry to waste time on finding back and quoting the right posts - but that's also on purpose : guides have alreadybeen quoted many times and everybody who dares to roor his phone should have mental capacities to search through the thread (if didn't nalready follow the story recolving for the last two days)

Besides, I don't have the broken SN (yet), and why should I do the homework for somebody else.

In fact, even if I put above the proper quotes/links, those who do not follow the conversation and who are lazy to search before asking, would also skip over/ignore this post
[Magisk] osm0sis:
ro.product.model was enough for my OP8T, but I didn't like how Google Play Services started referring to my device as "OnePlus BASIC" with the "hardware off" module, so I knocked together this module really quickly to just append _SN to the real model name. WFM. 🤘
[Magisk] thejohnize:
Doensn´t work on Poco F3 with CrDroid Build. Tried all fixes with the magisk modules..
[Magisk] howpathetic:
Sadly the LsExposed trick do not work for me :/ Mi Mix 2s - Pixel Experience.

None of those fixes work :( I hope someone will bring the ultimate solution to this problem.
[Magisk] Daddi8989:
Sorry for crossposting but I see that a lot of us are having issues with Google pay me included...

I just sorted out the safety net issue and now it's passing all the test, everything looks fine including Google pay where I'm able to register my credit card and the contactless logo says that's ready but when I try to pay all the payments get declined.

Did anyone fix this?
[Magisk] cater2:
Thank you very much for the notice.

From what you wrote I understand that I must install the second module

already installed

Note: I was using safetynet-fix-shim-MOD.zip module , but I started having problems with my galaxy m12 , so I installed safetynet-fix-v1.2.0-MOD .zip module
[Magisk] zagi988:
Can confirm that TeamFiles fix works on PixelExperience ROM.
[Magisk] Kape1234:
Didn't read everything here. Not sure if I need shim, but someone said it's for Samsung.

Result: everything is working!!!! You're my hero.

Samsung Galaxy S20+ Snapdragon.
[Magisk] Displax:
So, about such custom ROMs where simple method doesn't work (pixel experience, EVO etc).

They has prebuilded utils, which manipulate the props values. Need to fix inside there.

Simple-sample commit for PE.

SafetyNet fix · Displax/frameworks_base@77c2bc8

Contribute to Displax/frameworks_base development by creating an account on GitHub.

github.com

Someone who has contacts, please bring it to the developers.

I just don't have time to fight Gerrit.
[Magisk] pndwal:
Guessing PE ROM users could make / use a Magisk module to overlay com.google.android.apps.photos and com.google.android.gms package util files retrospectively?

Edit: Bad guess. 🙄 Seems this is not possible / practical / achieveable (retrospectively) as "creating the Application singleton during each app's initialization" is required, preferably through hooking. 😒

https://git.stag-os.org/StagOS/andr...mmit/dece290875c4bfbd366867730d077b1ade522eef PW
[Magisk] Jon8RFC:
I haven't attempted charging yet, but I needed this to make things work again:

Releases · stylemessiah/GPay-SQLite-Fix

A magisk module that ONCE allowed Google Pay to work on rooted phones - stylemessiah/GPay-SQLite-Fix

github.com

As for being declined, I had a random issue with that a few months ago. I'm pretty sure it was one of two things: 1) my card issuer(s) periodically delete virtual cards, or 2) that particular card issuer deletes a virtual card when the phone is detected as rooted and safetynet fails. Safetynet did fail at one point and I needed to redo things to get safetynet to pass again. Gpay never gave me any reason to think it wasn't working properly, either...

Re-verifying the CVC worked as expected and it never acted like anything was wrong, but whenever I charged by tapping, it was declined and my card issuer didn't see any declines on their end...it was odd. Completely deleting the card from gpay wallet (and having to setup a different default card before deleting it), then adding it back in all over again was my fix that time.

Also oddly, another card in my gpay wallet didn't have that problem of being declined by tapping to pay, and I didn't need to completely delete it to get it working. I just re-verified the CVC like I initially did for the card that was being declined.
[Magisk] shaunoleary:
I have a Pixel 3 running LineageOS 18.1.

I just ran into this little hiccup myself this afternoon, after doing a ROM update. Little did I know that nearly cost me having GPay access.

So this is what seems to be working for me - hoping it helps someone.

My phone: Google Pixel 3 (blueline).

ROM: LineageOS 18.1 (currently running 2021-08-31 update).

Magisk 23.0

Running the following Magisk modules:

GPay SQLite Fix v2.4

Riru V25.1.1

Riru - LSPosed V1.5.3 NOTE: I'm using Riru/LSPosed for running GravityBox, I don't know if it's impacting GPay. I do have XPrivacyLUA installed, and configured as per previous posts, but I still had SafetyNet fail after installing it, and GPay was complaining my phone didn't meet security requirements.

Universal SafetyNet Fix V1.2.0-MOD

I had to set up my card again in GPay, but that went through without a hitch. I haven't tried making a payment yet,but I'll try that tomorrow and see if I can make a payment.

Otherwise, it seems to be working. SafetyNet passes, and GPay is happy. I think what is doing the trick is the GPay SQLite Fix, and modded SafetyNet Fix.

Thanks to everyone above who posted their experiences etc. I can appreciate that Google ostensibly is concerned about security for GPay users. But if I bought my phone outright and paid for it, I should have the right to set it up and use it as I see fit - provided, of course, I'm not doing anything illegal, or anything that is placing anyone in harm's way.

Anywho, I hope this post helps to consolidate the process for anyone who may be trying to fix this on their phone. I'm a bit hesitant to do anymore ROM updates!!! :)
[Magisk] Mowca:
Has anyone fixed the problem with safetynet cts profile for Samsung s10e?
[Magisk] wtosta:
Yes, I did. The SafetyNet check passes with basic integrity. But the solution is not entirely satisfactory. I use Beyond ROM 8.6. I have installed Magisk 23.0 alongside with Safety-Net Fix 1.2 modded for Samsung SHIM. It is possible to register credit card with Google Pay, but when you try to enable NFC to use contactless payments, the Google Pay app says that The NFC is unconfigured, Although the NFC module is on, contactless payments won't work. At this point I stuck.
[Magisk] Yossarrian_07:
Same experience here. Updated ROM CrDroid. SafetyNet check failed. Gpay saw root. Installed SQLite for ARM aarch64 and GPay SQLite Fix v2.4 modules and added the cards again in Gpay with no issues. Paid in restaurant. But the SafetyNet check still fails in Magisk 23.
[Magisk] shaunoleary:
That's cool that it's working. Odd the Magisk doesn't pass SafetyNet for you though, it's passing here for me every time. Just tried a couple of times.

I've got a feeling though that our days of having GPay on rooted devices are coming to an end fairly soon though. I really hope I'm wrong, but time will tell.
[Magisk] Daddi8989:
Awesome, flashing that fix sorted out the issue straight away!

Thank you!
[Magisk] 73sydney:
Awesome, flashing that fix sorted out the issue straight away!

I dont get it, why are people suddenly having issues with Pay etc. literally no change here on my end at least (last Alpha), no "server end changes" as far as i can see here.

And i havent used my magisk module in like 8 months

All this due to maybe because i have an old Pixel 2XL....maybe they dont care about me :)
[Magisk] heathrow1:
Modded safetynet fix worked like a charm on Redmi Note 9 pro with stock miui. Thanks!
[Magisk] Dorisnov:
For me the LSposed method stopped working today.
[Magisk] pndwal:
Few Headsups:

1) There are reports that Danny's (@kdrag0n) new early release Universal SafetyNet Fix 2.0.0 (combines AOSP Keystore and shim Keystore solutions) is restoring ctsProfile for some. It just may work for all, but not enough reports as yet. Also, it requires a payment at this stage:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-85581909

https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-904209677

2) There are reports that simply using MagiskHide Props Config module to 'delete' ro.product.model prop fixes ctsProfile on custom ROMs where other methods have failed. Eg:

https://github.com/kdrag0n/safetynet-fix/issues/78#issuecomment-912885628

3) New MagiskHide Props Config module 6.0.0 just released with all the sensitive prop values that MagiskHide changed up to and including Magisk v23 set by default, "Force BASIC key attestation" re-enabled (for Googles latest changes), and various other fixes.

https://xdaforums.com/t/module-magi...p-edits-and-more-v6-0-0.3789228/post-85581939

I have to agree that this module's name does suddenly seem very apt, and as always, it proves elegant in its versatility. 😛👍

4) Another elegant solution that some may have relegated to a bygone era seems to be coming back in fashion to!

Those with Google Pay problems persisting after fixing ctsProfile are reporting in GPay threads, here and elsewhere, that GPay-SQLite-Fix + SQLite binary modules from stylemessiah (a connoisseur at least in digital fashion ... or perhaps just lucky, our @73sydney, - original solution from @BostonDan ) is fixing these for them once again. 😜 Eg:

https://github.com/kdrag0n/safetynet-fix/issues/78#issuecomment-912798412

WOT 😉 to read if interested:

https://xdaforums.com/t/working-mag...s-of-gms-17-1-22-on-pie.3929950/post-79643248

🤠 PW
[Magisk] pndwal:
Just out of curiosity because I don't have current ctsProfile failed result (@vvvb2060's Alpha Magisk on Xiaomi Redmi Note 8T and Xiaomi Mi Pad 4) and I understand several others also currently using Alpha fork have escaped this, has anyone using Alpha Magisk encountered it?... Thanks, PW
[Magisk] MaBo2020:
Hi :) Is currently a working Version for the European Model of A21s out ? (Sorry my English, iam German-Potato-Eater)
[Magisk] Ryano89:
I have an 8t on Havoc, is just flashing this.mod enough? Do you think it will mess anything up?
[Magisk] osm0sis:
Should be enough. Still working well here. Hasn't messed anything up on stock OOS that I've noticed, so Havoc will possibly be fine too.
[Magisk] Ryano89:
So no other fix needed to pass CTS, just your mod?
[Magisk] osm0sis:
Correct! Read and follow the info when it flashes: you just have to force close and clear data on Play Store, Pay and Play Services after flashing to reset it flagging you as unlocked.
[Magisk] pndwal:
What version did you have issues with?

No idea why current Magisk shouldn't work with Samsung Galaxy A21s! (My German is hopeless; we prefer spuds downunder.) PW
[Magisk] Ryano89:
Thank you sir
[Magisk] Ryano89:
Didn't work for me
[Magisk] osm0sis:
Must be because you're on custom ROM. MagiskHide Props Config should get you the rest of the way. Spoof OOS fingerprint. I seem to recall that's what I had to do on custom ROMs.
[Magisk] QkiZMR:
Question: which one i should use? Or both?
[Magisk] pndwal:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85575127

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85575593 PW
[Magisk] 73sydney:
Blast!, you meddler, youve just reminded me that i need to update the SQLite binaries package :P

Its test for the correct bin directory (to copy the binaries into) searches thusly

if [ ! -d /sbin/.magisk/mirror$xbindir ]; then

Updating now(ish)

As i havent used it in so long, and it had largely been unnecessary, i hadnt updated it

Will post again when its updated and i have a new build done
[Magisk] MaBo2020:
i havent any issues, i want only root my A21s :) For this i need SU, TWRP or MAGISK. But i think, there will no Chance, too root the Phone !
[Magisk] Didgeridoohan:
Have you checked the A21s forums? There's usually something about rooting in the Guides section of a device's forum...
[Magisk] pndwal:
So it's my fault... Well at least it'll get you out of bed!

My fault too?

Take your time mate... Wouldn't want to push you. 🙄 😉 PW
[Magisk] ipdev:
I finally gave vvb2060's Magisk alpha a spin last night.

Poco F2 Pro running stock (not rooted) MIUI v12.5.2.

Android 11 June security.

Patched the boot image with Magisk alpha and then booted it.

Setup and installed Magisk like I normally do.

Added com.google.android.gms.unstable to the hide list.

Installed the USNF module and rebooted.

CTS was still failing, so I tried osm0sis's module to adjust the model prop and rebooted.

Post 47,566 - Link

Still failed.

Then I remembered zgfg had mentioned a few times about having to hide a second google.

Post 47,449 - Link

I added com.google.android.gms to the hide list and CTS passed.

Cleared data for PlayStore and PlayServices and rebooted.

SafetyNet passes and Device shows certified in PlayStore.

Note:

This is the first time I had to add com.google.android.gms to the hide list.

Normally just com.google.android.gms.unstable was enough.

Cheers. :cowboy:

EDIT:

I was wrong. :oops:

Looking into it a bit more I noticed com.google.android.gms was added back into the default hide list.

Since the end of April 2020, it has been hidden by default. ?

Magisk - GitHub - commit - Link

So I have been hiding com.google.android.gms by default. 🙃
[Magisk] osm0sis:
Did you also try clearing app data after my module? That's really important because Play Services knows whether you've ever failed SafetyNet and needs to be wiped to reset it.
[Magisk] dron39:
Hi. I use your model along with kdragon patch (v.1.2.0) - everything works fine.

But you said that it is enough to use only your module (_SN) without any others. Is it correct?
[Magisk] osm0sis:
It may be enough on devices that don't have working HW attestation, like the OP8T (or any OnePlus device), running rooted stock.
[Magisk] pndwal:
Well there are a couple of guides there; I recall having been there before as this device does seem to be difficult as it doesn't play well with magisk.init and a modded Magisk apk has apparently been required till now...

Seems quite doable however following this:

https://xdaforums.com/t/root-modified-magisk-for-galaxy-a21s-r.4271537/post-84947089 PW
[Magisk] ipdev:
No.

Since I was still failing CTS, I did not check Play certification.

I only cleared PlayStore and PlayServices once I passed SafetyNet.

Cheers. :cowboy:
[Magisk] shadowstep:
Is it just me who's had trouble with the latest alpha build (f98c68a2)? My OnePlus 5 running OOS 9.0.11 Pie just straight up refuses to boot with the latest alpha. Reverting to the last alpha build (1eb83ad8-31) fixes the issue for me, so sticking with that for the moment.
[Magisk] 73sydney:
You rotten individual, you know full well its 3am here in Sydney :)

Its ALL YOUR fault, everything that happens...literally everything :p

Youre just lucky ive called someone i know "the worst person i know" today already :p

Nah, im switching the module over to use Zacks MM-Ext format as it eliminates that old function used to find out whether a ROM has a /system/xbin or /system/bin directory ...which has that obsolete reference to the old Magisk mirror path. Zacks module format handles the xbin/bin detection internally, meaning i can be lazy.

I had meant to go through and check my modules for that old mirror path after a new module im working on (slightly delayed to 14 day isolation after another patient of my GP's practice caused all the medical centres patients that day to go into mandatory iso, and oh, some brain scan fun) uses it directly.

So okay, the new, updated (fixed) SQLite3-Universal-Binaries module is done, tested and uploaded to my github.

GitHub - stylemessiah/SQLite3-Universal-Binaries: Universal (well almost, support from arm-v7+ ) SQLite3 binaries for Android

Universal (well almost, support from arm-v7+ ) SQLite3 binaries for Android - GitHub - stylemessiah/SQLite3-Universal-Binaries: Universal (well almost, support from arm-v7+ ) SQLite3 binaries for A...

github.com

There is also some actual error checking and log output to /sdcard/sqlite3install.log if anyone is having problems

That Google Pay SQLite Fix module of mine, i was just about to retire it, why wont you people let it die? :)
[Magisk] ipdev:
Checked on my 5T.

Clean flash of OOS 10.0.1, alpha f98c68a2 patched boot image boots and seems to work fine.

Clean flash of OOS 9.0.11, alpha f98c68a2 patched boot image failed to boot.

Cheers. :cowboy:
[Magisk] Cypherous2:
So, sadly none of the methods in this thread fixed my issue

I've run the gpay sqlite fix, i've run the universal mod

I can pass basic attestation and get a pass of evalType Basic

My device is listed as certified in the google play store, i have added googles services to to magiskhide

Google pay still says my device doesn't meet the security standards which makes me rather sad

Running an Xperia 1 III with android 11 with the july security updates

*edit*

After multiple reboots and nuking the play store cache multiple times it now appears to have finally worked, god i hate safetynet
[Magisk] Festum:
Thanks! It working perfectly on my Pixel 5 Android 11.
[Magisk] pndwal:
Thanks for that; so most likely a regression causing this in TJW commits I guess. Affecting at least OnePlus w/ OOS Pie... And others?

It may also show up in his next release, but probably too early to submit an official issue ticket yet, but could report in Alpha Telegram group... PW
[Magisk] shadowstep:
Thanks for testing! It's been so long something hasn't worked for Pie, haha. Time to go digging! (y)

Yeah, definitely seems like a regression. I reported it as a comment under the build in the 'Magisk alpha' channel, but can't seem to find the group. I'll try and look for it. Thanks!
[Magisk] pndwal:
But Play Services cached result can affect ctsProfile itself when it's data / cache are not cleared as SafetyNet API is part of play services. (Graphical description: https://developer.android.com/training/safetynet/attestation )

This has certainly been the case where both basicIntegrity and ctsProfile failed due to Xposed (recently EDXposed) issues; Check SafetyNet itself would only pass after at least Play Services cache was cleared, and PlayProtect issue was resolved after that.

I'm not sure about ctsProfile-only failing, but it stands to reason that cached SafetyNet result in Google Play Services may need clearing in this case to...

What occurs if you simply remove main Play Services process (com.google.android.gms) from MagiskHide list again now? PW