yashsingh1/xdaforums huggingface dataset:
[Magisk] itsmir:
Well - this is weird. Tried spoofing with Pixel 4XL A11, cleared pay services, store & wallet data and wallet reports "Your Phone meets security checks" - woohoo!.

It allowed me to add 2 credit cards but failed to add a bank card with the error "This phone can't be set up for contactless payments". Will pop out later and buy a beer to see if the credit cards I added actually work!
[Magisk] Phil21185:
To those who've successfully spoofed:

Is the new Wallet app working for you or did you have to sideload and older version of GPay or something?
[Magisk] alagga:
New Version is working
[Magisk] trabando:
Thanks guys.. Works with spoofing android 10.
[Magisk] itsmir:
Quick question, will setting sys.oem_unlock_allowed to 0 have any adverse effects on my mi9t (A11, Magisk 23 b/l unlocked)??

Want to test it to see if it fixes problem with adding a bank card to Wallet but google gave me a couple of horror stories of bricking devices when doing this.
[Magisk] Evo400:
I have Xiaomi 11T pro with MIUI Android 12. I changed the font to some random font from MIUU store. It's a bit different changing the fonts on Xiaomi as it only has one font as standard. But obviously that triggered a warning within Gpay app and stopped working. Went back to stock font and Gpay worked again
[Magisk] gwenmillett:
I can't use the props command, why why why. I have the module installed
[Magisk] DerGriechisch:
That's exactly what happened to me too

Everything certified and safetynet passed but still Google wallet knows I'm rooted
[Magisk] 1nikolas:
Your bank might have a similar system but most banks now just move to GPay
[Magisk] nodio:
Here worked with a10 device fingerprint with same vendor/model

reseted data from play services and playstore, and done, the magic happens,

thanks all fellows for the attention

My device : Poco X3 NFC A11 MIUI 12.5

Fingerprint A10, same device
[Magisk] aricooperdavis:
Did you reboot after installing the module? What emulator are you using? Does it work over adb shell? We can't debug with that little information!
[Magisk] infyrno676767:
Enable the magiskhide props config module first and make sure you reboot after. Use termux.
[Magisk] Jamezsss:
You can just spoof, clear data from the wallet app and you are done. No custom or older versions needed.
[Magisk] infyrno676767:
I chose the Samsung galaxy s20 on android 8 and that only supports gpay instead of wallet. Installed from the play store and it works perfect.
[Magisk] infyrno676767:
Choose the galaxy s20 and android 8. Reboot, wipe necessary data, install gpay from play store, follow setup process, reboot, and finish setting up your card with your bank. Should work like a charm.
[Magisk] Cailloux92:
Install tsu package as user and use tsu instead of su to gain root access

It will keep all usefull path and props will works
[Magisk] 1nikolas:
Maybe try reinstalling GPay and rebooting
[Magisk] gwenmillett:
Anyone managed to get it working on poco f3? Please help, using magisk hide props cts fails, it only passes with universal safetynet fix. Can't use contactless anymore
[Magisk] silentdc:
My S22 Ultra S908E, Magisk 25.2 + USNF 2.3.1 + Shamiko 0.51 = Google Pay not working. But after I changed to Google Pixel 6 Pro fingerprint with MHPC module, I can use Google Pay again.

So this is a temporary fix for now. Hopefully USNF will update to fix Google Pay still detecting rooted devices even SafetyNet and Playstore already showed Pass and Device is certified.
[Magisk] taldershof:
I noticed even after removing Magisk I still didn't pass. Maybe it's having the bootloader unlocked? I'm on a Pixel 6 Pro, but locking the bootloader would be a major pain if you need to do something..
[Magisk] Evo400:
Just noticed also Google news feed not working.. Annoying as fook. The days are coming where androids becoming as restricted as iPhones
[Magisk] gwenmillett:
Does your safetynet pass? Mine didn't when I tried pixel 5 fingerprint. I have a poco f3
[Magisk] Gleniu:
@nodio managed to do it. Please note, that you still need USNF, as well as changed fingerprint in MagiskHidePropsConf.
[Magisk] ezdiy:
Apparently only "close" fingerprints are likely to work. Eg POCO F3 shipped with A11, so try using POCO F3 A11 fingerprint.
[Magisk] samy233:
Try to spoof your phone (fingerprint) with an modele witch have Android 10.
[Magisk] BootloopedMillennials:
So if Android 11 and before fingerprints are working, it means they are now checking and requiring SafetyNet's hardware attestation for devices running Android 12+ (id by fingerprint)?
[Magisk] Nova_Max:
I'm on Moto Z3 play (Android 9), spoofing the same fingerprint didn't work. Any recommendations?
[Magisk] gwenmillett:
My phone model never shipped with a10
[Magisk] samy233:
You can try an another model with A10 , some Xiaomi user used Samsung model.
[Magisk] gwenmillett:
Which fingerprint and rom did they use? Can you link the comment
[Magisk] 1nikolas:
I have a question. How does changing the fingerprint on a Stock ROM would help it pass the Integrity API?
[Magisk] Gleniu:
Sorry, my bad. It was POCO X3.
[Magisk] BootloopedMillennials:
I should add it's still working for me with a A12 FP set in MagiskHide Props Config. For now at least.
[Magisk] brambles1234:
I have been reading this thread with interest. I have all the files and modules installed and I pass safety net. However Google Pay isn't working for me.

Samsung S20 ultra

USNF

MAGISK (latest)

LSPOSED

XPRIVACY LUA

SHAMIKO

MAGISCHIDE PROPS

ZYGISK

From what I have read I need to spoof my phone fingerprints with another using android 10.

My question is how do I spoof my phones fingerprint with another phone?
[Magisk] BootloopedMillennials:
See this post from earlier

https://xdaforums.com/t/discussion-...cussion-thread.3906703/page-131#post-87183361
[Magisk] nodio:
dont need to do anything else then just use fingerprint spoof, and safetynet fix, latest one 2.1

my config was X3 NFC with miui 12.5 A11, spoofed to the same device with A10

keep de same config in magisk, lsposed, xprivacy, hideapps, etc

RESET Playstore data and playservices data, reboot then it works fine, without recstritions
[Magisk] nodio:
Which android do you use? try to use magiskhideprops module with android 1 version before actual that you use, example, if you have samsung s22 with a11, fingerprint to a10 same device
[Magisk] ezdiy:
More or less. Some people have reported that it's not always the case. It seems to depend on particular device - some have a lot of leeway in what CTS spoof you can use, others much less so. The intution stays the same, though - you're google and want to roll it out without affecting old devices as possible. Chances are they're using some fuzzy/machine learning model based on telemetry reported by vendor certification and SafetyNet over the years - that model still provides a lot of leeway, so as to not affect outdated devices. But the screws are tightening.

Crystal ball: Within a year, USNF will stop working, exactly as topjohnwu said it would.
[Magisk] nodio:
Use this mod on magisk to hide the fingerprint of the device
[Magisk] BootloopedMillennials:
I think you meant to quote the user I quoted. I already have it working fine.
[Magisk] BootloopedMillennials:
If topjohnwu said that, it's true (and not speculation) given his position.
[Magisk] brambles1234:
Thank you for this. It is now working for me
[Magisk] itsmir:
Nope, had this issue on my Mi 9t A11, I spoofed pixel 4xl A11 & it is mostly fixed. CC's work in Wallet but can't add bank cards.
[Magisk] ezdiy:
It's part speculation on my part. What topjohnwu said specifically is that Google *will* eventually transition into demanding HW attestation, and the whole whackamole becomes pointless. Thus the removal of magiskhide and outsourcing the cat and mouse to the community who might be inclined to care for it for a little longer.

It certainly seems all of this is coming to pass. On my device that *has* a working HARDWARE_BACKED attest (mtkclient tether-booted root), the moment I enable USNF in there, GPay stops working. I tried to spoof CTS profiles of other phones (Pixel 4 and Nexus 5, I think) to no avail. This phone ever shipped only with A10, with no other versions available. It doesn't even have NFC.
[Magisk] Lada333:
Pixel 4a, running crDroid, A12. Spoofing to P4a A11, cleared data of wallet, play store and services. Had to set up cards again, and wallet no longer says phone doesn't meet security requirements. I've tried s20 and P4a A10 previously, they did not work for me. Have not tried to pay with it yet, gonna update on that when I do.

Update: contactless payment works flawlessly.
[Magisk] Snuuuuupy:
4a spoofed to 4a Android 10

had to uninstall pixelify module :(

was able to add card again (previously was denied to add another card)

usually if you can add another card you can do payments, if you can't add another card you can't do payments

haven't tried tapping yet, but will give it a try next time I go out.

I guess pixel devices need to spoof props now.
[Magisk] aricooperdavis:
Works for the POCO M4 Pro using the fingerprint for the POCO F2 Pro Europe (10) that ships with MHPC (y)
[Magisk] Phil21185:
Spoofed props to an A11 S21.

Actual device is A12 S21FE. Wallet has allowed me to add a card but interestingly Netflix is still not in the store. I notice that the device certification section is missing from Play Store though...

Anyway, thanks to those in the community who helped with this.
[Magisk] jacobyo7:
OnePlus 7T android 11, did not updated anything, stopped working 2 days ago. Now I can't add my card it say my phone can't be used for contactless payments. I was still using magisk v23 with magisk hide, but today I updated to v25.2, installed USNF, configured deny list, and my safety net is PASS everywhere, even rootbeer fresh can't detect root, but it's still not working in Google Wallet. Am I doing something wrong ? I already cleared cash and data from google play store, framework and wallet multiple time, reboot the phone, I tried everything I could thing of. Thanks in advance
[Magisk] 73sydney:
try reading the last few pages before spamming us with every screenshot you could find, you would have discovered what the issue is and how to workaround it :)

please always try reading the last few pages of a thread to see if anyone else has reported a similar issue, instead of blasting it like youre the only person experiencing something :) Sometimes its not all about you :)

Heres a huge hint, the rest you can pick up by reading the last 2 pages:

https://xdaforums.com/t/module-magiskhide-props-config-safetynet-prop-edits-and-more-v6-1-2.3789228/
[Magisk] ezdiy:
Google provides new API to attest device integrity, somebody posted an app for it already. We should probably prod YASNAC (which is now widely recognized as "root checker"), so that people stop this "i get safetynet pass, wtf".
[Magisk] itsmir:
Tried again spoofing to A10 version of my rom, this time with WiFi off. After reboot cleared data from play store, play services & wallet. Cleared all caches. Enabled WiFi & once Google updated everthing Wallet works with all cards. So yes, spoofing does work on the Mi 9t eea.
[Magisk] stalker780:
Same for me. Samsung S8 Android8. Spoofed to Samsung S20 Android 10.

GWallet now does not show any notice about root, but cannot add bank card.

I get "Could not finish card setup for tap and pay. Contact your bank... bla-bla-bla"
[Magisk] Lada333:
I now see Netflix in play store. Have you cleared data for play store and services as well, or just wallet?
[Magisk] Phil21185:
Think I just did cache for store actually. Hang on.

Ok, didn't touch anything and went to check store. Netflix shows up. Certification section is still gone though.
[Magisk] alagga:
In the S20FE group some people mentioned that newest Magisk fixed the uncertified playstore.
[Magisk] wfred:
Used the props module on my 7T and changed the fingerprint to a 7T with A10. Cleared store & pay cache & data.

Looks like everything passes now.

Thanks
[Magisk] 73sydney:
Not true as far as i can see, it may stop the popup when you open Wallet, but checking the Contactless Menu shows the same error

No change i can see, i reinstalled Wallet as well

Didnt clear Play Store or Services as i have Watch 4 and that would break my Watch connection and id have to reset....major ballache
[Magisk] [-]awkeye:
Good eye there!

I wished I didn't flush all my data when my Google Pay stopped working few days ago. Could have at least tested out that theory a simple prop change will solve your issues currently.

That said, for folks who are using a Pixel 2 XL running a stock rooted Android 11, change your build prop one version behind (in my case Android 10) and it should allow you to re-add cards (assuming you accidentally cleared all previous data).

Unsure if it will let me tap though. I'll update my post once I have a chance to use Google Pay.

UPDATE: It kept giving me tap decline errors at certain vendor's, even after various reboots. In the past couple of hours since this edit, I was able to successfully use Google Pay again. Will update in the next few days if needed.
[Magisk] s4lah:
These steps worked for me.

Change fingerprint to pixel device (pixel 5 to be precise)

Reboot

Add play store to magisk hide list (all processes)

Clear data of play store

Reboot

Open app and should be able to use.
[Magisk] intellq:
What I did to reestablish Google Pay on my Oneplus 5:

- Latest Magisk with SNF 2.3.1 and MagiskHide Props Config (install them and reboot);

- adb shell (or terminal) / su / props / changed fingerprint to Oneplus5 Android 9 (Android 10 = no go);

- Uninstalled Google Pay;

- Deleted all data in Google Play Store and Google Play Services;

- Reboot;

- Reinstalled Google Pay;

- Now wallet is working, add card is working, even Netflix is once again showing in Play Store.

(before that Safety Net passed all tests, "Device Certified" in Play Store, but no netflix nor the ability to use gpay)

ps: don't know if is mandatory, but all google pay/play related stuff AND all nfc services are blacklisted in Magisk
[Magisk] FloofyPeachy:
Boom baby!

Using a Google Pixel 4a with 5G, spoofing my prop to a Google Pixel 4a with Android 10 installed has seemed to do the trick and Google Pay works now.

Definitely temporary, but at least it works now.
[Magisk] jacobyo7:
I am very sorry, I read the past 3 pages before posting but was not able to find my solution, english is not my 1st language. I removed my screenshot sorry again

thanks I found the app on page 130. So basicly YASNAC is useless now ?

Thanks I did exactly the same, I have the 7T as well and it work now. Do you know if having a fingerprint from android 10 on amdroid 11 can affect the device in any negative way ? Thank you
[Magisk] helgi1507:
Just to inform you all, I don't know what's going on all around Google Wallet these days, but today I reflashed new custom ROM and install Lygisk 25.2 (fresh version after 25.1). So then, I installed SafetyNetFix and MagiskHideProps to configure correct CTS profile as always.

But... I was shocked, because none of new (A12) and old(A11!) fingerprints do not pass YASNAC CTS check as it was before.

To my surprise, default fingerprint is passed YASNAC and Google Wallet and even New Api Check Integrity of Play Store.

I don't know this is a bug or what, but I often needed to change my CTS profile before todays morning.

I even deleted MagiskHideProps module and it works.
[Magisk] alagga:
It fixed the playstore being uncertified, NOT the wallet uncertified. The only fix for that is the CTS spoofing.
[Magisk] Lada333:
Did you re-flash the same ROM you were using before? Or a different one? If so, can you provide the name of the old and the new ROMs you're using? Both A12?
[Magisk] 73sydney:
Never had a problem with Play Store being certified :)
[Magisk] helgi1507:
I used LineageOS 19.1 all this days.

But wanted more customization and install - CrDroid 8.7 (based on the LineageOS)

Both A12
[Magisk] stalker780:
Worked today. Looks like my bank have some sort of limited attempts to connect a card during a day.

Also I had to clear data for Play Store, Play Store Services, GWallet and my bank app.
[Magisk] NateDG01:
Can confirm this working on a Pixel 3 XL

Also used the Android 9 fingerprint for said device.

Thanks a million! Never realized how much I used tap to pay until it randomly stopped working last week.

🤘
[Magisk] stereo007:
where can i find that? Is this a module or directly from google? Do you have a link?
[Magisk] aricooperdavis:
https://xdaforums.com/t/discussion-...cussion-thread.3906703/page-130#post-87182459
[Magisk] 1nikolas:
Please be aware that this app is not 100% accurate. The api has 2 more readings you can get (which are pretty important) but Google gives them to you only if you upload the app on Play Store. So I made a better app and uploaded it to Play Store. Now I'm just waiting for Google to verify my identity and it will be up. (Oh and by the way the app is 100% open source, I'll link everything once it's up)
[Magisk] debork:
Restored GPay on Oneplus 7 Pro (11.0.8.1.GM21AA):

Update Magisk v23 to latest Magisk v25.2

Install Universal SafetyNet Fix v2.3.1

Install Shamiko v0.5.1

Clear GPay + Google Play Services data

Add GPay + Google Play Services to Denylist, disable Magisk Denylist enforcement

Reboot
[Magisk] Fr33L4nc3r:
I'm struggling since a few days to get back Pay / Wallet to work again on my Oneplus Nord, glad I finally found the best place to find information :)

Using Magisk 25.2 + USNF 2.3.1 + Shamiko 0.5.1 + MHPropsConfig 6.1.2-v137

Props is set to Oneplus5 Android9 as explained in one earlier message

I put Pay + Play Services + Play Store + Services Framework + Nfc Service in DenyList (NOT enforced)

Data of above apps / services are cleared.

Device is Play Store certified.

YASNAC says pass (basic)

AppList Detector doesn't find anything

RootBeer Sample doesn't find anything

Momo mentions some suspicious traces (TEE broken, due to unlocked bootloader ?)

Yet it does not work in Google Pay or Wallet.

Play Integrity API Checker says the same thing.

I'm kinda running out of ideas, any advice ?
[Magisk] edwardecl:
I got my "Google Wallet" to kinda work on my Samsung Note 4 (910C) with LineageOS...

What I had to do was change my device fingerprint + the second option with the PropsConfig module to a Samsung Note 4 (910F)...

Using the latest version of Magisk (not sure if latest version is needed)

I did not need to clear any caches, just add Wallet to the Magisk deny list, plus use the USNF module.

My phone was previously verified with google play using one of the pixel fingerprints, possibly why I didn't need to clear the caches.

With the pixel fingerprint wallet would run, i could even get to the add a card part, but it would crap out of completing an existing card, so I assume that would not work when trying to use NFC. But as soon as I changed the ID to the closest thing to my actual hardware Google Pay fully works, I did use it in a shop successfully.

But I have had it lose the ability when swapping the battery, to get it to work again i changed the device fingerprint to something else, rebooted, run the wallet app, changed the id back to the 910F, reboot and it works again.

Bit of a pain, but whatever, better than nothing.

I'm going to assume Google is matching the device ID against the actual hardware in the phone or something.
[Magisk] plepew:
Thank you for that very specific outlined process (for Oneplus). I have OP6T McLaren and use everything you mentioned (had it already), but the one thing which was throwing me off...using A10 fingerprint profile which was not working at all.

Maybe I was doing something wrong, but using A9 profile worked...

Any chance anyone has the A10 profile working for a 6T? Does it really make a difference between the 2 profiles? If it does and someone can share for just knowledge, I would appreciate it.

Cheers! ✌️
[Magisk] 73sydney:
read the last 2-3 pages.....sheesh

when will people stop photo bombing the thread like theyre the only perosn with an issue, without first reading the last 2-3 pages of a thread....and figuring out other people have the issue.

second time someone has waded in spewing pics of their crisis in the last 24 hours

its not all about you, youre not special...everyone has issues at the moment

read the last 2-3 pages before you post next time, please
[Magisk] wfred:
Not that I can tell. All of my apps still work, but I don't have any that require A12.

The only thing I noticed is the date on the security patch is 05/22, but 1+ is slow to update that so maybe it didn't change.

BTW I added wallet to the magisk deny list.

Used Google pay at the grocery store today without any problem
[Magisk] wfred:
Does an OTA update reset the fingerprint to the actual device?
[Magisk] 73sydney:
A few quick tests - i normally run my S20+ 5g with stock ROM but my own magisk module spoofing the 2 manufacturer props to Google, so i can use Samsung Health and my Watch 4, that module was disabled for these tests. Deny List Unmount module loade :

i created a printslist file for MPHC with the following fingerprints for my S20+ 5G for A10 & 11:

Samsung Galaxy S20+ 5G SM-G986B (11):Samsung:SM-G986B=samsung/y2sxxx/y2s:11/RP1A.200720.012/G986BXXSCDUJ5:user/release-keys_2021-11-01

Samsung Galaxy S20+ 5G SM-G986B (10):Samsung:SM-G986B=samsung/y2sxxx/y2s:11/QP1A.190711.020/G986BXXU5BTJ3:user/release-keys_2020-10-01

neither would pass integrity/CTS

I changed the fingerprint to a Pixel 5a A12 and integrity/CTS passed, but contactless was still borked. I uninstalled Wallet, reinstalled, no change. I removed my card, readded it...tells me its ready to use contactless. Contactless still borked in menu. Contactless still borked. Cleared Play Store data...certified upon reopening. Contactless still borked

I changed the fingerprint to a Pixel 4a A10 and integrity/CTS passed, but contactless was still borked. I uninstalled Wallet, reinstalled, no change. I removed my card, readded it...tells me its ready to use contactless. Contactless still borked in menu. Cleared Play Store data...certified upon reopening. Contactless still borked

Did the most ballaching thing imagineable (because it will sever my watch connection, meaning ill have to spend an hour resetting up my fricking Watch 4 again) and cleared Play Services.....

Wierdly when you clear data on Play Service. Play Store & Wallet and reboot, wallet changes back to Google Pay and says you cant access it as its updating...so you have to uninstall it. When you reinstall it, it initially runs as Google Pay again...then switches to Wallet

Setting up Wallet leads you through adding a screen lock, when theres already one in effect (ffs)...the card added, and finally contactless works....but will it last

Suspect that it would have worked if id cleared Play Services and fricked my Watch up when i had the fingerprint set to Pixel 5a A12....this is probably what i will try before i reset my Watch up again...later, i need sleep :)

This is fun....not

Time to get TJW on the blower (phone for non Aussies) @pndwal :)

I very much want to stab someone at Google badly for this nonsense. Its my device, and my money thanks, ill decided how i use both thanks.....in years of running GPay rooted how many people have caused a security issue at Google or their bank: 0

ffs, leave us in peace.....
[Magisk] soadfan:
I couldn't agree more.

Back in the days (with the old phone) when I was using SuperSU and couldn't hide the root, my bank soft authenticator wouldn't work because of the root. I've asked them "Why?" They said this device is potentially compromised because you have absolute access to the OS. Then I asked them, ok, but how is this any different than running Windows with an admin account without any antivirus enabled, for example?

I didn't receive any replies, despite numerous "Kind reminders" after that.