yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
what do you call it when someone questions someone elses motives, when the person theyre questioning already questions themselves (on all fronts), on a daily basis? Im sure the germans have a word for it, my friends just tell me im "spannering" stuff

i did point out what i was doing was secret squirrel business and not mainstream magisk tinkering like you

i was actually generally interested to see what would happen if i left Wallet unchecked, im going to run with it, leave it unchecked and see where it takes me, probably a trainwreck and future posts with an overabundance of explanation points when the sky falls, and i start looking around for someone else to blame for my predicament, which is my SOP...
[Magisk] ihavenolifee:
Final edit - I did a reinstall of the GPay Fix module and editted fingerprint to S21. It was still on the not meeting requirements but later today AKA now, the phone is now meeting requirements. Interesting DP, no idea if I could have just waited till then, or if the steps I did changed anything. Also did wipe cache of Play Services and also Wallet but those didn't change anything until the time passed as well.
[Magisk] 73sydney:
i was with you until you mentioned that flipping GPay Fix module

i dont have the energy to find a shaking fist meme pic right now, but please imagine one :)
[Magisk] ihavenolifee:
Just testing things and reporting DPs, any issues with that module that I'm OOTL for?
[Magisk] 73sydney:
Perhaps youre using the app and not a browser and cant see my signature or havent noticed, but ive been trying to stop people from using my module for a while now....

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

theres a link to the explanation why in the opening section
[Magisk] ihavenolifee:
Yea on mobile so no signatures show up. Will give that a read thanks and sorry haha
[Magisk] tangcla:
So, I noticed on Friday that my Google Wallet was telling me it did not meet security requirements - but it still seemed to work.

This morning I tried to use it, and it failed - on the EFTPOS terminal it said that card was unsupported. I switched to another card and it worked.

Is there a limited number of tap and pay tokens that has now run out?

Phone hasn't changed so as others have said above, could be server related changes.
[Magisk] CSX321:
Around me there are some terminals that only accept VISA for tap-to-pay, even if they accept other cards for swiping. It's a dumb contractual thing. It could be that something like that happened.
[Magisk] tangcla:
No, these places I've been to before, they definitely accept Amex.
[Magisk] bigknowz:
Not working again, tried Shamiko and same result. Thoughts appreciated.
[Magisk] pndwal:
What device? ROM? Android version? SafetyNet / Play Integrity solution? YASNAC result?

Shamiko won't help... Play Integrity is your issue... PW
[Magisk] bigknowz:
Pixel 6 pro running A13 September Verizon. Using USNF.
[Magisk] zgfg:
Play Integrity API Checker updated to v1.0:

Play Integrity API Checker - Apps on Google Play

Get info about your Device Integrity through the Play Intergrity API

play.google.com

Thanks @1nikolas
[Magisk] m0han:
IIRC, I'd updated to 0.5 yesterday or so. Stable now. 👍
[Magisk] zgfg:
I updated yesterday one device - it was v0.4->v0.5

Updated the other device few minutes later, it was already v1.0

Then updated first device again, to V1.0😁
[Magisk] brambles1234:
I have tried using Google Pay today and it comes up that I don't meet requirements. I'm guessing there's been an update. Is there a solution yet? I've updated Xprivacy Lua and changed fingerprint through termux. Any other help greatly received.
[Magisk] zgfg:
There is a GPay thread. You need to use "USNF v2.3.1-mod" module (not Lua) and for that you need to have Zygisk, therefore Magisk v25 (not Magisk v23 and Riru - if you are still on Riru)

Please search for the XDA GPay thread and find more info there
[Magisk] brambles1234:
For anyone looking for a fix for your system doesn't meet requirements' after September 22nd Update. There is no fix at present.
[Magisk] zgfg:
Oops (I overlooked, thought you are in Magisk thread) - this is the GPay thread

Look for "USNF v2.3.1-mod" (as I mentioned in the previous answer - must have that MOD in the name), from Displax (from him, not from the OP poster in the USNF thread). Might be here but also in the USNF thread

It's been month and more when that MOD version of the module was posted, and the whole story about Wallet, Play Integrity API discussion started here and in that USNF thread - info can be found by reading the posts
[Magisk] brambles1234:
Below 👇
[Magisk] brambles1234:
Whenever I come to XDA and ask a question I'm normally receive a really unhelpful reply, along the lines of "if you search you will find your answer" This is can be very annoying, especially after I have spent an hour looking and I still can't find the answer? Hence the reason I ask a question.

The reason I say this is because I have got Google wallet working and I will share what I did.

Samsung Galaxy S21 rooted Beyond Rom

1. Uninstalled Google wallet

2. Deleted both cache and data from play store

3. Updated Xprivacy Lua

4. Reinstalled UNSF

5. Changed fingerprint using su / props

6. Restarted phone

It is pertinent to say here that I fail all api integrity checks using the app on playstore. However Google wallet contactless payment works better than before.

I will keep this updated if I have as any issues.
[Magisk] CSX321:
Tap-to-pay is still working for me as of an hour ago. No pending app updates showing.

Pixel 6 with A13 September update

Magisk 25201 (slightly outdated, I know)

3 Modules: "Systemless Hosts", "Universal SafetyNet Fix" v2.3.1 mod version, "OnePlus Oxygen OS 11 - Two-Button Navigation (Standard Height)"
[Magisk] zgfg:
Fine that it works, and nice that you described your process

Feel free to help/answer to the others writing them complete instructions (or searching yourself to give them links to exact this or that post)👍
[Magisk] m0han:
just for info: latest gpay works fine with the latest magisk delta and riru. modules as in screenshot.
[Magisk] 73sydney:
Please understand that someone asking the same question over and over (and often expecting to be spoonfed) can be taxing.

And yes the search system can sometimes take a bit of learning to fully utilize properly....but really, heres the key.....if its a recent issue, then the issue is very likely not just affecting you, and so the solution will often be found in the last 5-10 pages of a thread. People get really tired of people who rock up create a new post at the end of the thread, when the answer is maybe 3 pages back, and they seem to think thats too much effort. Standard Operating Procedure on any thread should be to read the last 5-10 pages before creating a new post. That would earn the average person who thinks theyre catching a tough break because theyve touched a nerve that been tugged at by 50 people before them a lot of respect....consider trying the last 5-10 pages of a thread method in future, it will often not only giver you the solution, but the context, which can be just as important, and often you may be able to provide some input or insight no one else has, which everyone can benefit from. Also if people just rock up and expect an answer in 5 minutes everytime (theres plenty do it, some people might have been registered for 3, sometimes many more, years and never post until they need something, happens all the time), then they dont learn anything, and they also dont contribute....

As for your steps above:

3. Updated Xprivacy Lua <-thats not required and is a personal choice, and has no real bearing ion the issue)

Usually one would do:

1. Install USNF Mod (the Mod is important as already stated)

2. Integrity Test

3. Test contactless menu in Wallet

If contactless fails:

4. Delete both cache and data from play store and reboot

5. Test contactless menu in Wallet

Note

Step 4 has been known to take days to return a positive contactless setup, in some cases

Note #2:

5. Changed fingerprint using su / props <- this should be largely unnecessary except in the case of chinese ROM's or other edge cases as far as i remember
[Magisk] brambles1234:
Did you get magisk delta from telegram?
[Magisk] zgfg:
I dunno for Delta Telegram but simple google searches "XDA Magisk Delta" and "GitHub Magisk Delta" provide by no mistake the links (top choices) to the corresponding discussion here about Magisk Delta and to the GitHub project with instructions, download links, etc
[Magisk] pndwal:
... And with @Displax USNF_mod it is not needed even for ROMs not passing CTS Profile match (China region, Beta, Developer, many custom ROMS) in most cases. (There may rare be exceptions where this modded module doesn't work.)

Technical:

This mod actually adjusts the fingerprint prop to achieve the mismatch needed along with device prop mismatch to trigger bypassing of hardware based attestation enforcement in Play Integrity (different from the actual Evaluation type fallback triggered by the exception caused when trying to use key attestation with an injected 'fake' keystore provider registered)...

All these mods, official and unofficial, target the gms attestation process (one process within Google Play Services) only. The prop changes are not globally applied, so issues with OEM specific functions (eg Galaxy Store, special camera functions etc) caused by model prop changes and issues with Play Store (eg. YouTube not updating as expected) etc caused by fingerprint prop changes are successfully avoided...

Issues with unmatched security patch prop dates are also avoided with this solution...

The @Displax mod also kills a second bird (or rabbit 😜 ), ie. allowing ROMs not passing CTS Profile match to pass as mentioned above, simply because the fingerprint prop used for HA bypass trigger must also be properly certified for CTS...

--> This makes this USNF build a true 'Universal' fix, encompassing both old S/N API and new PI API, as well as the whole range of certified stock and uncertified China region, Beta, Developer and custom ROMS...

👀 PW
[Magisk] m0han:
Don't remember when/where I got it first from, but as of now I keep getting in-app updates.
[Magisk] Nekromantik:
Pixel 6 Pro September Update stock ROM so A13

i was on latest stable Magisk with kdragon USNF and DenyList UnMount and got the your device does not meet security message this morning. Tried the Integrity test and it failed all 3 on version 1. So installed USNF mod and then it passed first 2 but not strict. Did cache and data wipe of Google Play and rebooting but contactless menu still says does not meet requirements but I not tried to actually use it.

Should I pass all 3 in the integrity test?
[Magisk] shadowstep:
No. You cannot pass the strong integrity check. Conditions for MEETS_STRONG_INTEGRITY to be true are:

Hardware attestation is working

Bootloader is locked

Google Play is certified

ROM must be production build
[Magisk] Nekromantik:
Ah ok thanks
[Magisk] cescman:
I am using a pixel 6 pro rooted with magisk and usnf 2.3.1 installed. Play store and wallet and play service all in deny list. Google pay has been working fine for months until yesterday when I got a pop up message that my device doesn't meet requirement for contactless payment. YASNAC showed basic integrity and CTS match both pass and evaluation type basic.

I tried clearing play store data and cache and rebooted as described in a post above but it doesn't work. Any one has the same problem or any solution?
[Magisk] zgfg:
First, instead of the 'official' USNF 2.3.1 use the "2.3.1-mod" from Displax (mentioned in every 'second' post)

Second, there is no use of putting Playstore to DenyList - it relies on Google Play Services and that's managed by USNF 2.3.1-mod
[Magisk] Goooober:
Like many people Google Wallet is now broken for me. I've been using it without issue on my Poco F3 running Crdroid for a few months now using the latest Magisk, Zygisk and the SafetyNet Mod Fix by Displax but it not longer seems to work.

I've tried the usual clearing storage for Play Services, Play Store, Wallett App without success, I can't even add a card to the Wallet app now.

My YASNAC still passes but Google Play Integrity API Checker now fails on MEETS_DEVICE_INTEGRITY when it used to pass.

:(
[Magisk] Nekromantik:
@Goooober see post above yours

you need to use the UNSF MOD instead of official
[Magisk] Goooober:
As I said in my most I am already using the UNSF mod by Displax. I assume that's the one you're referring to unless there is another one?
[Magisk] cbarai:
I've been on the Canary build and I've rebooted my device a couple of times in the last day, no issues and GPay seems to be working from the first transaction Friday evening to last one on Saturday evening. Over the same time period I updated one build of Magisk and moved from build 118 ecf3d303 to build 119 8893cbd6 today. I've made payments since the update & reboot which were a couple of hours after the update & reboot. There has since been another update and build 120 has been released in the last couple of hours, I've not yet updated.

I'm going to stick to this setup for a while and see how things go. Hopefully the stable will be released soon and that should have the fix applied, SafetyNet is mentioned in the changelog notes on github.
[Magisk] Itachisasuke:
Yeah the changlelog notes so something to the effect of "Prevent SafetyNet from removing itself from MagiskHide"
[Magisk] DanRyb:
Which Google Play Services are you on? Did you downgrade to the 14.7 version?
[Magisk] mogantivenkatesh:
Hiii. I am using SAMSUNG GALAXY J7 PRO. I enabled OEM UNLOCK, installed TWRP RECOVERY and installed MAGISK MANAGER. The SAAFETYNET STATUS in MAGISK is TRUE for BOTH options. I installed GOOGLE PAY. I hide the ROOT access using MAGISK HIDE in MAGISK MANAGER. The GOOGLE PAY app is working fine and enterd my card details. But When i Click use CARDLESS PAYMENT it is asking details and after entering it takes some time and says THIS PHONE CANNOT BE USED TO PAY IN STORES. THIS MAY BE BECAUSE IT IS ROOTED OR ALTERED IN SOME THER WAY.

PLEASE HELP.
[Magisk] b3rsus:
Have downgraded Google Play Services to 14.7.x version. But it updates by itself. How to prevent GPS from updating (with saving of it's common features)?

P. S. Disabling "auto updates" in GP doesn't work)
[Magisk] caluz78:
I use an app called "service disabler" and seems to work...

https://play.google.com/store/apps/details?id=com.kunkunsoft.rootservicedisabler
[Magisk] b3rsus:
I do not need to disable or freeze the service. I need to disable its auto updates.
[Magisk] caluz78:
With this app you can. I only disable the service that update GPS, not GPS all.
[Magisk] StirringDesert:
Which one is it, please?
[Magisk] caluz78:
SystemUpdateService and UpdateShedulerService
[Magisk] b3rsus:
Interesting. I didn't think about it, I will try. Thanx :)
[Magisk] caluz78:
Let me know.. for me now is one week without update..
[Magisk] b3rsus:
Unfortunately in my case that doesn't work. GPS still updates by itself =(
[Magisk] pedritopl:
IMHO It's much better to install the latest Canary Magisk build instead of doing all those kind of dangerous workarounds and downgrades. With the latest Canary build Google Pay just works out of the box. No workarounds, no downgrading, no clearing app data, etc.
[Magisk] b3rsus:
I've tried 18.2

On my device (Taimen, stock 9.0 05.02.19) there are several bugs making impossible to use this Canary build.
[Magisk] prgopala:
Unfortunately this is not right. It may work for some days or payments but then it fails. I am currently on canary builds and google pay does not work. It did work for a day or so but has failed since then.
[Magisk] mattman83:
Not working for me - clean install as of yesterday only had 118 canary on it, just installed pay again and magisk hide everything Google and still can't add card.

Imo right now everything is just pot luck. There's no working long term fix until topjohnwu has a chance to look at what Google is doing now and if there's a workaround. With Q dropping as well though I'm sure there's a lot on his plate right now.

At the moment I've just accepted I have no gpay for now. Went back to stock ROM for pay for a few days but just can't accept some of the issues I have with stock miui (maybe minor to most, it just bugs me), would rather not have gpay lol.

M.
[Magisk] Itachisasuke:
Same boat man only except on a Pixel 2 XL. Gotta toss [MENTION=4470081]topjohnwu[/MENTION] some PayPal donates and tag them with GPay Fix. Beer money is a great motivator lol.
[Magisk] Didgeridoohan:
I actually find that to be a bad idea. A donation is just a gift as a token of appreciation. If you suddenly make it into a "motivator", you're just putting pressure on the guy, at the extreme end resulting in no more development at all.

If you want to donate, please do. But don't tag it with any kind of "please do this/fix that" messages. Just say "thanks for your great work". That's motivation enough...
[Magisk] Nekromantik:
not sure then

mine was same as yours until I changed to UNSF MOD
[Magisk] Goooober:
I've always been using the MOD version and everything was working just fine so i've no idea what I can do really as I cant bear the though of going back to stock MIUI.
[Magisk] SimpleStevie:
Same phone, same rom, same issues
[Magisk] tom510:
Me too. Also running latest version crDroid 8.9, last android security update 5/9/22
[Magisk] 73sydney:
Just an aside, did you have a recent google play services update...i got one a few days (official, from the play store update, not a self inflicted beta mess from apkmirror like some nut bars on here do - hint: never do that) ago that when it installed itself wreaked havoc by seemingly clearing either database or data upon install which severed my Watch 4 connection (the most egregious thing as its a total ballache to reset that backup from scratch thanks to Samsungs (non) backup) and killed Wallet. I had to uninstall the update, which reverted Wallet to Pay, which gave the usual Pay is updating so you cant open it nonsense, meaning wait 20 minutes, open it, set it back up and migrate to wallet shamozzle, at the end of which i was delighted to see contactless still working happily...only plus side of the events...
[Magisk] OverlordBubbles:
Why did I choose yesterday of all days to decide to install a rom on my Poco f3, Crdroid 8.9

I've just come from miui wanted a change, had custom ROMs on my previous devices and now just reading about these problems.
[Magisk] SimpleStevie:
Maybe it's a Poco F3 or CrDroid issue then? None of the fixes that are mentioned here work for me
[Magisk] Nekromantik:
Yes I had play services update but I already had Wallet instead of Pay even before the update few days ago
[Magisk] pndwal:
Nekromantik, SimpleStevie, OverlordBubbles, tom510, Goooober​

So everyone has this issue using @Displax USNF-mod module on Poco f3 w/ Crdroid 8.9?... Interesting...

Did issue occur with an update, or just started occuring?

If no update its likely Google has strengthened prerequisites for deviceIntegrity on server end... Could be something peculiar to Crdriod Rom too... Eg. is selinux enforcing?... Some strange prop settings/manipulations?...

Could ask Poco f3 Crdroid maintainer about possible incompatibility... An integrated mod may be causing issues when running Magisk USNF mod...

Strangely this seems to be removed from tree:

https://github.com/crdroidandroid/a...mmit/c24af39a3e66cf11bcff09fa150651dd60cfef16

Also, seems 12.1 branch ROMs are built with A13 fingerprints now:

- PixelPropsUtils: Update fingerprints to September 2022 release

- PixelPropsUtils: Update fingerprints to Android 13 August 2022 release

... not sure of effect of this...

... Perhaps these don't mix well with Magisk module or these:

- PixelPropsUtils: Limit SafetyNet workarounds to unstable GMS process

- PixelPropsUtils: Only spoof GMS to Raven

- Introduce PixelPropsUtils for safety net spoof

... or other commits... ???

Could post info. here for @Displax / @kdrag0n:

https://github.com/kdrag0n/safetynet-fix/pull/207

🙃 PW
[Magisk] batboy00:
Hello. Same problem since 22/09. Xiaomi Redmi Note 10 5G with magisk v23 and Props Config modification since july. Suddenly, Google Wallet does not meet security requirements and device integrity does not pass anymore.
[Magisk] pndwal:
Stock MIUI?... Guess you had official USNF + some mismatched (earlier) fingerprint prop configured in MHPC...

Does deviceIntegrity pass again for you if you disable MHPC and replace official USNF with @Displax's modded USNF?... PW
[Magisk] Goooober:
The issue just started spontaneously, no updates or anything. In the Play Store it still says the devices is certified despite Wallet not meeting security requirements.
[Magisk] batboy00:
Yes, stock MIUI. And official USNF until July. And then I had to use a prop with a lower Android version, hence the use of MHPC. If I am not mistaken the modded USNF works for latest Magisk and I have the v23 (not really willing for the moment to upgrade to brake something). But if no other solution will be found I will also try this solution.
[Magisk] zgfg:
There was (two months or so ago) USNF 2.3.1-mod (with that "mod" in the name!), by Displax (hence again, not the 'official'), targeting exactly the Wallet / new Play integrity API

With that, you should better test (first) without MHCP

And USNF, for it's full potential, requires Zygisk (hence the new Magisk)
[Magisk] pndwal:
Ah... Explains why you kept MHPC globally spoofed earlier fingerprint... So guess you have official Riru USNF... And G Play Services com.google.android.gms.unstable and (assuming A11+) com.google.android.gms processes in hidelist...

If you don't want to move to Zygisk builds, you could test targeted spoofed old fingerprint solution using @huskydg's Riru/Zygisk - Play Integrity Fix:

https://github.com/HuskyDG/safetynet-integrity-fix...

(@huskydg, I see you made this improvement:

Only inject safetynet process

but readme.md still says "by injecting into com.google.android.gms and com.google.android.gms.unstable" 😜...)

Please say (if you try this) if deviceIntegrity passes again for you by disabling MHPC and replacing official USNF with @huskydg's modded USNF... 👍 PW
[Magisk] pndwal:
Yup, - I noticed month's ago that Google seems to have only partially implemented PI API... Eg. G Pay/Wallet still seemed to be using S/N API for basic setup (incl. online purchases) but PI for Contactless setup of cards... the in-app contactless Security requirements dialog erroneously said "device meets security requirements" but card setup would fail in practice with a correct error message... Also, while Play Store began restricting app availability (eg Netflix) if PI deviceIntegrity failed, it's Play Protect dialogue in Settings, About, still said "Device is certified"... (Of course clearing app data can affect results also.)

Back to the issue; It seems evident that integrating signal spoofing in ROMs is complicated and fraught, and can involve many separate commits (some examples above), and further, these will need to be made to play well with additional magisk/root modules/solutions that attempt to do similar things...

For me personally, I much prefer ROMs that are clean of such mods (ie. don't attempt to fix S/N & PI issues natively)... Using official LOS (will never manipulate expected signals due to policy) for example allows users to apply all such mods using Magisk and be far more aware of what changes are actually being applied as well as decreasing the potential for conflicts... At least introduced conflicts can be reversed by users instead of requiring dev intervention...

Many have wondered why official LOS won't spoof signals but there is something to be said for this policy... In instances like this it has clear added advantages... Unless Devs can always get these manipulations (often requiring ability to juggle commits, a fantastic memory and much luck with outguessing Google mechanisms and changes) right... 🙃 PW
[Magisk] m0han:
There is a safetynetfix-2.3.2-riru-mod.zip on telegram. Wonder if that contains the 'improvement'.