yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] xflearx1:
Now it works for me after very long tries.

safetynet test with yasnac app worked but not wallet app.

I have oneplus 7 pro with the new lineageos 21.

I made this:

1. sideload magisk app in recovery mode (with pc)

2. when device rooted: (u can check that with root checker :D)

in magisk app: magisk app hide, zygisk is on, enabled Systemless hosts. put google play store, google play services and wallet on the deny-list.

Module installed in magisk app: Magiskhide 1.10 from huskyDG, Play Integrtyfix from chiteroman

3. reboot and go to settings-->apps; then cleared google wallet, play store, play services.
[General Questions and Answers] znbaboy:
i also have this issue with OnePlus 7 Pro after updating to Lineage 21. I cannot pass basic integrity. I had to switch to my other phone thats still on Lineage 20.
[General Questions and Answers] Danishblunt:
When i tried it on my Rog3 which has it embedded as well since A12, it didnt work. Maybe there is something different going on on the pixel phones?
[General Questions and Answers] V0latyle:
Maybe. Have you tried spoofing a signature with MHPC? Also, do you have the GPay app installed still?
[General Questions and Answers] maintanosgr:
I've tried on my realme 8 5G all the steps above but unfortunately still getting the message that my phone doesn't meet security requirements. Any ideas?
[General Questions and Answers] Danishblunt:
I think you misunderstood me.

It works just fine after spoofing. Before spoofing however i could launch embedded gpay without any error message but would fail at transaction.
[General Questions and Answers] V0latyle:
Quite possible, I misunderstand a lot at my age

Unfortunately for me, my wife thinks it's deliberate
[General Questions and Answers] tom1807:
Sorry, I don't get it. I should change the FP from my Google PIxel 6 to any other, like 6Pro or Pixel 5?

Cheers

Tom
[General Questions and Answers] deechte:
I'm very grateful for this guide, thank you so much! I'm not an ace at this, rooted my device long ago and simply kept updating.

The recent developments at Magisk got me so confused. I follow the Magisk - The Age of Zygisk thread, but there are so many things I don't understand and problems people have, that I was going to give up. I was still on Magisk v23 because of all of this. And then Google Wallet recently started complaining about root on my device.

So happy I found this thread with a simple step by step approach. After clearing data of the Wallet app, Play Store and Play Services I obviously had to re-add my banking card to it, and I was able to successfully do it. No warnings so far in the app, but I still have to make my first payment.
[General Questions and Answers] deechte:
I figured out you need to subsequently choose:

A) edit device fingerprint

B) pick a certified fingerprint

C) choose your specific brand, device and Android version

D) confirm with Yes

This does not really change anything to your actual fingerprint you use to unlock your device, but apparently it changes something needed to make it all work.
[General Questions and Answers] Pumpkin_PL:
Working like a charm :)

THX
[General Questions and Answers] PapaSmurf6768:
Confirmed here too, GPay was working with just Safetynet Fix up until some recent update, not sure what exactly broke it. Enabled Pixel 6 fingerprint through Props config module and was able to add my card in again.
[General Questions and Answers] Hack3rxt:
thanks for the explanation. I think this is missing in the first post. It has taken me 3 days and I did not understand the reason, now everything works fine for me.
[General Questions and Answers] Koehlix:
How exactly did you do that? Is there guide or something?

I managed to nable Pixel 6 fingerprint through Props config module, but nothing changed.

maybe you can do a step by step for me, so i can get what i missed?
[General Questions and Answers] Rayfen Windspear:
Mine stopped working a few days ago on my Pixel 2. Have already done these steps. Redid the ones that could be redone. Nothing has worked. Even cleared all data for Google Play Services. Still a no-go.

Thing is, it never stopped passing SafetyNet checks. Never stopped reading as "Certified" in Play Store settings... Can't figure it out. Only thing I can think is that when I first set it up, I was nearly driven mad trying all the things, then I just let it settle for a few days and it finally started working.

So I guess that's what I'm trying now. The waiting game. The same thing happened when setting up a Pixel 4a 5G for my wife. Did all the steps, didn't work immediately, but checked a few days later and it had picked it up... super annoying.
[General Questions and Answers] tom1807:
Thanks, so basically I did it right, didn't work me, still showed "doesn't meet requirements. But today, without further doing. It was fine.

Thanks to your post, I thought check again after it didn't worked yesterday. And yes, it shows today, "You are ready to pay..."

Cheers

Tom
[General Questions and Answers] saam_oc:
Only thing I did was the prop part and it worked. Finally. Adding a fingerprint solved the issue.
[General Questions and Answers] CZMiki:
Working, thx
[General Questions and Answers] pinkhyori:
For those who managed to get it to work. Did it work immediately after following the steps? And is your device in the big list of devices?

I have a device which isn't found in the list and picked another certified device's fingerprint. However it's not working and I'm wondering if that's the issue.
[General Questions and Answers] deechte:
My device is a Oneplus 7T Pro, which is in the list.

It did or didn't work right away, I'm not 100% sure. I didn't work right away BEFORE I removed data of Wallet, GPlay and GServices apps. After I deleted data of these three apps, I didn't have my banking card at hand, hence I couldn't add it right away. A few hours later I added it and it worked.
[General Questions and Answers] jkmaxfli:
Thanks a lot bro.

You saved me!
[General Questions and Answers] painterKDM:
My phone passed all the tests but would not work with Wallet. Tried fingerprint in props but my phone or variants of not listed. Followed Reddit suggestion of disabling/removing Props and flashing modded safetynet fix 2.32 modded by Displax over normal one. That solved my problem with my Oukitel F150 R2022
[General Questions and Answers] deechte:
Update: by now I've been able to pay multiple times without trouble.

Edit: bootloader is unlocked.
[General Questions and Answers] LoredoJC:
On my ZE620KL nothing worked, many tries, I waited a few days and it didn't work. Even changing the rom for an official Asus rom (without root) the app kept saying that the device is not safe. It only started to allow contactless payment after relocking the bootloader. I believe that in my case, gpay did not work by detecting the unlocked bootloader.

Edit

The device passed all tests, safenet, Google protect, basic, CTS (with root).

but it still only worked after relocking the bootloader
[General Questions and Answers] Clasimodo:
On Samsung I didn't even have to hide Magisk. Magiskhide Props Config did the job. I had Universal SafetyNet Fix already installed, but don't know if that is necessary for wallet to work. I paid in different places without a problem.
[General Questions and Answers] oksagi:
Pixel 6 with latest Magisk 25.2.

MagiskHide Props module.

Changed the fingerprint, cleared cache for Playstore, Play services and walled app.

I was able with these steps to pay via wallet yesterday.

Thanks for the workaround!
[General Questions and Answers] Rpgilligan85:
This worked for me, I also added google pay and google wallet to the deny list. Thanks for the instructions!
[General Questions and Answers] Kaiyum:
Redmi Note Pro 9 with Magisk 25.2 ,Gpay worked fine after this,tho there is no Joyeuse cert(even tho in the list ??) So just changed to other device and now is working <3
[General Questions and Answers] Rayfen Windspear:
Update on my Pixel 2. I changed the fingerprint to Pixel 6 and it let me add my card. Netflix updated as well. Looks like they are starting to deprecate some of the *really* older fingerprints.
[General Questions and Answers] mj084:
Here too on OnePlus 7T - worked some days before using MagiskHide Props Config - now I installed the module and setted a certified Fingerprint and I was able to add my credit card to Google Wallet :)
[General Questions and Answers] Rayfen Windspear:
Another update from me on Pixel 2. Changing the fingerprint from an Android 11 print to 12 caused my Camera app to update, totally breaking it on launch. Had to reverse my fingerprint back to Pixel 2 @ 11 to get my camera back up. I AM running LineageOS on 12 (12.1), but it looks like the Camera app is fingerprint dependent. Appears everything still works on the Pay side. Note that I haven't gotten around to making a payment yet, but the app no longer simply rejects me. I've yet to have it fail without it telling me to get lost from the app beforehand.

Looks like the GPay/Wallet/Play Store only check periodically and cache the results. Seems strange for something they would want to lock down pretty tight like Card payments... but whatever. Works for me at the moment.

I suspect I'll possibly have to mess with my fingerprint eventually again. If/when I do, I'll be sure to report back if it's the device they may have blacklisted, or if it was the Android 11 fingerprint. I'd suspect it's the device, not the OS though. It's certainly getting on the old side :cry:
[General Questions and Answers] Rayfen Windspear:
Fingerprint back to Pixel 2 at android 11 restored my camera, but after a day or so, killed gpay again 😒. Any other fingerprint makes my camera want to update and break. Going to try several to see what correlation there is between OS and device that causes success. Trying Pixel 3 @ 11 right now. Have to wait for caches to settle before gpay decides I'm kosher again though.
[General Questions and Answers] Rayfen Windspear:
Well, now I'm stuck with a choice between a working camera app, and having Pay work 😒. Updating my fingerprint to anything causes the camera app to update and throw an unsupported device error. Manually extracting and installing the camera app causes it to crash unable to load some shared library file.

Leaving the fingerprint on Pixel 2 @android 11 brings back the camera, but breaks Pay for the whole Wallet... Although it has let me add cards/methods without issue, and doesn't whine that I'm rooted when tapping on "not set up" like it does when you are rooted and have zero Pay mitigations.

So now I'm just waiting again to see if it will spring alive again after a bit, and then I'll tackle trying to get the right camera version installed without letting the stupid play store update it.
[General Questions and Answers] deechte:
If your camera app updates through play store, you could disable automatic updates. If it updates without play store, maybe installing AFWall+ and blocking internet access for it might work?
[General Questions and Answers] Rayfen Windspear:
I disabled auto update, then I walk away from it and and come back to find it had updated.

As to Pay update. I was changing my fingerprint all day yesterday playing with the camera, but I did a system update overnight, and Pay activated. It's been a while since I've opened recovery and wiped dalvik/cache. LineaogeOS recovery doesn't have that option. I wonder if changing fingerprint then clearing it would avoid having to wait.
[General Questions and Answers] Rayfen Windspear:
Now this o_O

Here we go again...
[General Questions and Answers] Danishblunt:
Well if thats the only issue, why not download a gcam mod for your pixel 2 instead?
[General Questions and Answers] ihavenolifee:
What do you do to clear google wallet data if it's embedded in a Pixel 6? Having issues with it currently.
[General Questions and Answers] V0latyle:
The reason for this is that Google has deprecated the SafetyNet certifications in favor of the new Play Integrity API, which uses 3 fields:

MEETS_DEVICE_INTEGRITY

The app is running on an Android device powered by Google Play services. The device passes system integrity checks and meets Android compatibility requirements. This is replacing SafetyNet's ctsProfile. This is what USNF fixes.

MEETS_BASIC_INTEGRITY

The app is running on a device that passes basic system integrity checks. The device may not meet Android compatibility requirements and may not be approved to run Google Play services. For example, the device may be running an unrecognized version of Android, may have an unlocked bootloader, or may not have been certified by the manufacturer. This is replacing SafetyNet's basicIntegrity, and means that Play Services has not detected root.

MEETS_STRONG_INTEGRITY

The app is running on an Android device powered by Google Play services and has a strong guarantee of system integrity such as a hardware-backed proof of boot integrity. The device passes system integrity checks and meets Android compatibility requirements.

This is replacing SafetyNet's Hardware Attestation, and uses the Android system's Trusted Execution Environment to guarantee process security. This will not pass with an unlocked bootloader, and cannot be spoofed as it specifically relies on hardware security; unlocking the bootloader "breaks" TEE.

The workaround for this is the modded USNF module by @Displax which spoofs an older fingerprint causing apps to fall back to the "old way" of using only the DEVICE and BASIC fields. I imagine at some point in the future, app developers (especially large ones like Google) will eventually remove this fallback in their apps, which will mean that anyone whose device does not pass Play Integrity will not be able to use the app. This will include everyone running versions of Android older than 8.0, when TEE was implemented.
[General Questions and Answers] pndwal:
Wow.. another thread 😬... Perhaps we could condense this in @Didgeridoohan's GPay thread?

Anyway, since you asked me to critique, it's there:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87274413

🤠 👍 PW
[General Questions and Answers] arwindr79:
Thanks for the instructions, finally managed to make a payment today. Sprint LG G8 crossflashed to A11, Magisk 25.2, google pay worked fine but broke after the update to wallet. Even though my exact model number wasn't on the fingerprint list, the G8 fingerprint which is listed seems to be working fine.
[General Questions and Answers] jono0080:
Worked a treat on s21 ultra followed step by step now have it working again
[General Questions and Answers] Trilis:
Oneplus 8t fingerprint unlock stopped working, anyone has a fix?
[General Questions and Answers] maxb31:
Hi, I changed the fingerprint for e pixel 3 on my mi 11 pro, and it worked!!!! thank you very much but can it change something that my phone is recognized as pixel 3 and not mi 11 pro?
[General Questions and Answers] agpol07:
Same for me.

Any solution on this?
[General Questions and Answers] BernatVM:
Pixel 3 android 12 profile not working for my Xiaomi Mi 9T running android 12 custom rom. CTS Failed in YASNAC app. Anyone got it working in a Xiamoi Mi 9T Pro /K20 Pro ??

EDIT: this worked for me
[General Questions and Answers] agpol07:
Uninstall prop module and install only this safetynet-fix

Release v2.3.1-MOD · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Release v2.3.1-MOD · Displax/safetynet-fix

github.com
[General Questions and Answers] mythos6910:
That worked for me. Oneplus 7pro.

Thanks.
[General Questions and Answers] tenow:
Installed pixel 4 android 12 fingerptint on pixel 4 android 13.

Had to clear all data in google play services then contactless returned
[General Questions and Answers] leAndroid91:
Hi guys I have a OnePlus Nord with pixyOS based on Android 12L.

I have done the tutorial as described also with deleting cache and data from wallet, play and play services.

In wallet I still get the security error message.

Any suggestions what I'm doing wrong?

Maybe I'm using the wrong fingerprint?

For the OnePlus Nord there is only Android 10 + 11 available. I took it.

Maybe that's the issue since mine is based on Android 12?
[General Questions and Answers] williamcll:
I have Zenfone 9 and I haven't tried using pros config yet since there's no fingerprint file out there. Should I try the modded safetynet fix instead?
[General Questions and Answers] Kal-El7:
@tenow - I was about to ask something related to this. Google Pixel 4 or 4a or 4a5G on Android 13 (thirteen)... could a person use the Android 12 fingerprint on either of these Pixel models running Android 13 (thirteen) OS and still have success using Tap-to-Pay Google Wallet on the latest version of Google Wallet.

Is this essentially what you are reporting?

Thanks!
[General Questions and Answers] Kal-El7:
@BernatVM - is that a SafetyNet modded patch/fix that doesn't require using Props Config?
[General Questions and Answers] tenow:
Correct. That's what I did. Not sure though if that was what actually helped or clearing data for google play apps
[General Questions and Answers] Kal-El7:
@tenow - this is perfect. Thank you so much for sharing this info. I was reluctant to updating, but now not so much. Now the only thing for me to do is to assess if Android 13 is worth upgrading to and go through all the hassle of redoing everything. I only do straight AOSP - no custom roms.

Thanks again for sharing.
[General Questions and Answers] BernatVM:
Correct, it worked for me just with this, no other setup
[General Questions and Answers] Kal-El7:
@BernatVM - Well I'll be. That's interesting, then. Thank you for responding.
[General Questions and Answers] Kal-El7:
Hey all, I have a question on the SafetyNet Fix/Patch that was recommended a few posts just above. This method has been verified by members in this thread to work absent the Magisk Props-Config module.

I have a Google Pixel phone that is listed on the certified Fingerprint list. Everything went through smoothly with the Magisk Props-Config module instructions and I was able to finally add my bank card, though I have not yet conducted a transaction. Assuming that my phone can succeed with contactless payment using either method, SafetyNet Fix or Props-Config, could anyone provide me pros-and-cons for choosing either method? I would like to settle on the path that is best for me.

Thanks so much!
[General Questions and Answers] MachtKoma:
I tried everything but it still dont work for me. Iam using an mi9t tried the modded safty net, after that it still didnt worked and then used Magisk Props-Config. But still it doesnt function
[General Questions and Answers] Clasimodo:
After the latest update of Google Wallet yesterday it stopped working with prop module (rooted device warning). Did this and it doesn't give a warning anymore. Didn't have the chance yet to pay with it.
[General Questions and Answers] deechte:
No problem here with yesterday's Wallet update. But I took the route from the OP, not yours.
[General Questions and Answers] Clasimodo:
That is what I did as well and what stopped working for me. I did not rename magisk though (and still didn't do so), so I don't know if this was the problem.
[General Questions and Answers] brambles1234:
After September's 2022 update I'm no longer able to use Google wallet. Does this 👆 apply to this new update.
[General Questions and Answers] deechte:
You quoted a post that says to uninstall the props module. That's different from what the OP explained.
[General Questions and Answers] Clasimodo:
I did this after the method of the opening post didn't work anymore. What I quoted solved this for me.

I first used the method of the OP, but that stopped working after yesterday's update. The quoted method solved my issue.
[General Questions and Answers] peelz_:
I had the same problem as @Clasimodo; it stopped working for me yesterday. I had MagiskHidePropsConf and safetynet-fix installed. After switching to the safetynet-fix fork by Displax and clearing all storage used by Google Play Services (i.e "Clear all data" button), I managed to get it working again.
[General Questions and Answers] rseiler:
On the subject of the v2.3.1-MOD fork from back in July, does anyone have a grasp on why its exists? I understand that it apparently (somehow) works around the current problem, but it's a little underdocumented.
[General Questions and Answers] peelz_:
I have my doubts that v2.3.1-MOD did anything to fix my issue. On my previous attempts, I only cleared the cache of Google Play Service and Google Wallet. When I switched to 2.3.1-MOD, I pressed "Clear all data" instead.

I'm not sure how Wallet detected the root in the first place, but maybe it cached the detection somewhere that wouldn't be purged by clearing the cache?
[General Questions and Answers] rseiler:
You'll find out, I think, when whatever it is that triggered it in the first place (some kind of Google Play Service action, perhaps) recurs, which it surely will at least try to do.

There's a fork of the fork, incidentally, here, and that one looks more maintained and even documented. Not sure of its efficacy yet.
[General Questions and Answers] peelz_:
Thanks for the link. I'll try that if it happens again.
[General Questions and Answers] drieg:
That was the only thing that eventually worked for me on my oneplus 8t, aftee trying about anything: denylist, universal safetynet fix v2.3.1, fingerprint change as depicted in this post, shamiko

Thanks a lot!!
[General Questions and Answers] Clasimodo:
I experimented a little. If I go back to the OP method I cannot add a payment card (rooted warning). I cleared data of Google Play. If I then remove the props module and then install the mod instead of the original safety fix I can add a payment card.
[General Questions and Answers] Clasimodo:
Thanks for that link. The size is different from the Displax one, but this gives molded by Displax too in the module.prop info. Must be related. This version works for me as well (can add payment card).
[General Questions and Answers] himan7991:
Tried this today and it let me add the card. Will update the reply when I try to pay. Thanks 💪🏻
[General Questions and Answers] leopseft:
Facing the same issue with a Realme 7 but I have just unlocked bootloader, its not rooted!! I haven't install twrp or magisk yet, so the device fingerprint is untouched, right?

So google somehow can detect unlocked bootloaders. (I get a warning during boot that the phone is unlocked and I have to press the power button once within 5 seconds, so the boot will continue.)

Does anyone have any idea??
[General Questions and Answers] Zoneee:
On a Realme GT 5G with Realme UI 3.0 (A12) RMX2202_11_C.21

Didn't work:

1. Original SafetyNetFix (enabled)

2. MagiskHide Props Config (enabled but not setup)

3. Renamed Magisk 25.2 with DenyList for:

- Google Play Store

- Google Wallet

4. Cleared Cache for Play Store, Play Services, Wallet and restarted phone

Works:

1. Use Safetynet with integrity API fix earlier from this thread

Releases · HuskyDG/safetynet-integrity-fix

A workarround to pass SafetyNet / Play Integrity API on rooted devices with unlocked bootloader - HuskyDG/safetynet-integrity-fix

github.com

Thanks @rseiler

Steps 3,4 remain the same. No need for step 2 (module is now uninstalled because it was never used)

TODO: Try an actual payment.

UPDATE: Payments working perfectly! Yay!
[General Questions and Answers] b0mb:
Hey Guys,

i´ve finally god Google Wallet with PayPal as service for contactless payment working ussing the followin Modules.

Shamiko, Safetynet Integrity Fix, Lsposed für Zygisk and Xprivacylua.

In Xprivacylua i´ve chosen all options for the following:

Goole Play

Google Play Services

Google Framework Services

Google Wallet

and TaDa..... finally i was able to get Google Wallet work