yashsingh1/xdaforums huggingface dataset:
[Magisk] un4free:
Yes it used to have that option but sadly it disappeared a while ago, now their app isn't even on the Play store anymore.

I've tried card emulator pro and reading one of my NFC card (and creating and using a magisk module from the app) but it didn't seem to work :(

On a related note, can anyone help me updating magisk 23 to 25 please? I've made another post on the OnePlus 7t section but so far no reply that helped me upgrade.

I've already rooted my op 7t with magisk and it's now on v23. In the app I can update to v25. My question is: I've read a lot (maybe too much because now I'm confused) and everywhere they suggested to use a boot.img from stock ROM, patch it with magisk etc.

In my case (ie rooted already, magisk already there, but old version) do I have to do that?

Thank you for your help
[Magisk] pndwal:
Answered this here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87191527

😛 PW
[Magisk] pndwal:
Re. new Play Integrity detection in GPay/Wallet, Playstore (and more soon):

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

🤠 PW
[Magisk] Fr33L4nc3r:
Hey, thanks for taking the time to reply and "help"

Funny that you blatantly assumed I didn't read the thread at all, when if you actually read my post I mention the test app provided by 1nikolas that uses the new Google API stuff, which is located page 130

As for photo bombing, please excuse me from providing details instead of a simple "Hey guys, I have an issue, can you help me with your crystal ball ?"

Wishing you a better day than you seemed to have ;)
[Magisk] simika:
I worked for me on Poco M3 Pro ! i selected from menu:

1 - edit device fingerprint

----

F - pick a certified fingerprint

-----

26 - samsung

-------------

14 - samsung galaxy A40

-----------------------------------

i just went to grocery shop to try it and it works ( Google wallet .. just updated )​

BUT one thing .. i had to open the app to pay ! while before with Google Pay i just needed to unlock the screen!

is there some settings ? or that's how WALLET works?
[Magisk] gwenmillett:
ok so my wallet now works after using magisk hide props confix and universal safetynet fix with shamiko on poco f3 but the wallet app still says my phone is rooted in its contactless setup. Wierd it still works
[Magisk] 73sydney:
Reboots were done, thats implied because im a sane person who does them after clearing data.....reboots did not help...... :)
[Magisk] TraderJack:
I got it working on my 3 XL as well (running 12). However the wallet quick tile now shows my wallet is unavailable. Do you have this issue too?
[Magisk] 73sydney:
No, you did exactly what i commented on....thinking your crisis deserved higher attention than everyone who had already read about it and replied for 2 days without photo bombing

And i had a fine day, thanks :)
[Magisk] plepew:
@pndwal

Thank you so much for the clear & detailed explanation in both posts (here & the other thread, where you shared this post).

As I was reading through many the previous posts over the last week, I got more confused on what is happening on the immediate situation with GPay/Wallet & the longterm goals & changes Google has planned.

I was successful in using Props for the Fingerprint workaround yesterday, despite still not clearly understanding what is going on, until now.

Cheers!! ✌️

** The following comment is not directed @pndwal at all!! **

There are some that make comments to read, read, read...which is what ppl should do in general...but not everyone is as knowledgeable, savvy, or experienced in doing any of these workarounds & stuff.

I found some of the posts in recent pages to be disrespectful, condescending & agressive toward ppl that are simply trying to understand & looking for help. These forums are to share, inform, assist and help ppl when they need it the most!! It should always be positive. If you are angry towards what Google is doing, take it up with them, not the members of any level in XDA community.

✌️
[Magisk] 73sydney:
@pndwal

For shizz and giggles, i changed the fingerprint (from Pixel 4a A10) to PIxel 6 (A12) and simply rebooted.

YASNAC - CTS Pass

Play Integrity - Passed

Contactless still enabled

So i can haz Google Pixel A12, but not Samsung A12?

Waiting for a little while before i reset the watch to make sure it sticks :)
[Magisk] pndwal:
Ok... May have misconstrued what "may have worked" w/ pixel 5a print...

Either way I don't believe in-app Contactless setup 'device doesn't meet security requirements' issue is related to fingerprint unless old SafetyNet attestation is failing... The issue predated fingerprint affecting Play Integrity verdict also...

Clearing Play Services and Gpay app data fixed security requirement issue for me, but I opened GPay before rebooting. (Guess I must have been insane at the time by your reckoning).... I made payments for several days, but Activity list remained empty even after several reboots...

What repeating procedure of Clearing Play Services and Gpay app data but rebooting before opening cleanly installed GPay fixed was the Activity list issue... And my sanity... Thanks to @rodken kindly testing... PW
[Magisk] 73sydney:
Its a weird one alright...maybe we're experiencing a grey area margin with SafetyNet phasing out and Play Integrity phasing in...i just know like most, i didnt need this right now :)

As for the data wiping, you know me i go hard core, airplane mode it (yes, im a secret American) and then reboot, and airplane toggled back off before i open an app again - sorry i didnt make it clear in my earlier post that id done this and the reboots :)

Im starring to think this is all just an exercise to show shareholders a swollen chart full of Pixel users, because with Pixel fingerprints being a safe bet, theres plenty more about this week :)
[Magisk] NateDG01:
I don't have the actual wallet app, in fact I don't even have the actual pay app installed. I'm using the native "GPay" that's built into the stock rom.

So my quick tile from the pull down just says "GPay" and shows a little graphic of my linked card. But it's highlighted as active like my others (internet, Bluetooth etc)

Hope this helps.
[Magisk] TraderJack:
Yeah, thanks. After not showing up after multiple reboots, I just went to bed and now this morning it is working again.
[Magisk] dumdidum123:
When GPay changed to Wallet, paying worked one last time and then i got a notification overnight, that i am no longer able to pay with it.

I got a little out of practice with modding etc., since all worked fine for the last 2-3 years with just blocking access to that db-File somewhere (from what i remember).

What I did today: Update Magisk to 25.2 (+reboot), activate Zygisk (+reboot), block Google Wallet and Google Play Services with Zygisk, install Universal SafetyNet Fix, delete data of the Google Wallet app and end the app. Reboot and check with YASNAC for Basic integrety check and CTS profile match (both passed).

Open Google Wallet. No warning anymore, so i got myself a coke and all worked fine.

Let's hope it sticks this way. Maybe that helps someone.
[Magisk] helgi1507:
I think update to Magisk 25.2 did the trick in my case too, because at 25.2 didn't install MHPC module as I usual did and all works as you described above.
[Magisk] TraderJack:
I've posted a summary of the current state of things here:

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

Hopefully it helps some people get up to speed and sparks some additional information from people who I'm sure know more than I do.
[Magisk] TraderJack:
This is interesting. What devices do you both have?

Most of us are finding that the failure of GPay working now is due to the new Play Integrity API and this has nothing to do if your YASNAC/SafetyNet checks pass. Would you please download this app:

https://xdaforums.com/t/discussion-...cussion-thread.3906703/page-130#post-87182459

It checks for the new API pass/fail.

If your devices are failing that check it means that GPay/Wallet are not yet using the PI-API on your device and instead still just using SafetyNet and Basic Attestation. If that is the case it is interesting why they stopped working suddenly and then work again after resetting up everything.

I'm not sure that Magisk 25.2 has anything in it that 25.1 does not that would cause this behavior.

I also wonder if Google's servers are still wishy-washy during this roll out to different devices and are sometimes trying to enforce the new API on certain devices and sometimes not.
[Magisk] 73sydney:
I got full half day after the first reports starting coming in the other day

Silly me, thinking i was immune :)

Wouldnt be surprised if its flaky servers/staggered implementation
[Magisk] dumdidum123:
I am using a OnePlus 5. Your app shows "MEETS_DEVICE_INTEGRITY"

Hope this helps?
[Magisk] 1nikolas:
Just wait for the new app it will give more info
[Magisk] TraderJack:
Not my app, its @1nikolas .

What OS Version are you on? And have you set a specific fingerprint with PropsConfig (or even have installed)?
[Magisk] intellq:
Out of nowhere, GPay is again saying my phone doesn't meet requeriments (Oneplus 5 @ A10, fingerprinted to A9)

Some infos:

- Play Store is still showing Netflix;

- 1nikolas app says "MEETS_DEVICE_INTEGRITY";

- Can't add new cards at GPay;

- Don't know if GPay stopped accepting payments with NFC despite that message, going to test later.
[Magisk] pndwal:
I'm guessing running Android 10 or earlier..

No... It'll be using SafetyNet attestation for in-app 'Contactless setup' info but Play integrity verdict for actual cards / card setup just like those with cards failing...

Difference is the PI verdict is generally passing on devices w/ Android 10 or earlier fingerprint props... Seems mainly those on Android 11+ need to select different print prop to pass.... PW
[Magisk] pndwal:
As long as both PI and S/N are passing in test apps, I'd try clearing Google Play Services and Google Pay/Wallet data and reboot before opening Pay/Wallet (if you open first you may get things working but Activity list may fail to update / remain empty after purchases) and setting up cards again... Wallet will probably become GPay again before updating after some minutes to Wallet again.

This may fix in-app security issue for you; has for me/others... Let us know. 👍 PW
[Magisk] Lada333:
I have yet to upgrade to 8.7 - I'm still on 8.6.

Did you reset device fingerprint to default before flashing the new ROM?
[Magisk] dumdidum123:
Still on Android 9 (yeah, big shame on me). Never touched anything about Fingerprints or PropsConfig.
[Magisk] wfred:
Bumping this because 1+ just came out with an OTA update for the 7T.

Does anyone know if the fingerprint spoof survives an update?
[Magisk] pedritopl:
If Magisk survives then the module survives and the spoofing survives.

I just updated my 7T this way and the fingerprint is still the same (A10).

Other thing is whether this has any adverse results for the device - I don't know that.
[Magisk] rodken:
Oh me - On my, maybe I'm immune due to the fact that I've been able to use Wallet in the 'real world' without any degradation since the update first rolled out.

-- I also took the liberty of adding my COVID Vaccination info to Wallet on stock OP8 OOS 11.
[Magisk] helgi1507:
I format all device in recovery before installing, so, yes.
[Magisk] helgi1507:
My earlier post

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87187883
[Magisk] TraderJack:
How much of this do you know for sure, and how much are you theorizing?

I assume these statements are based on the fact that when failing PI, everything still looks good all the way through the end of add card process when it suddenly give you the device rooted message?

That could be the case. Or it could be that they have changed the app so now they only care about the contactless setup and PI is doing all the work?

The architecture of PI seems to make it very well suited for the app servers to make decisions based only on certain tasks. This means, if designed well (and one would hope Google is designing their apps around this better than others) they app may install and function perfectly fine until you try a specific task which they require PI for.

This is better than an app simply crashing on boot because it detects root, etc.

The way it stands now, even if you fail PI you can still use wallet/Gpay...just not for contactless.

Also, it would seem with this architecture a particular bank/institution could even be proxying the decision based on your PI status so one could seemingly allow you to add a card with MEETS_BASIC where another might require MEETS_STRICT.

I'm not saying you are wrong, but I think it is still a guessing game at this point. We need a lot more data and controlled testing barring some deeper insight into the actual code.
[Magisk] TraderJack:
So to confirm: you are running a custom 12L ROM on your Samsung S10 using the default fingerprint (MHPC not even installed) and you are getting a pass with the Play Integrity API checker and GPay/Wallet add cards/contactless is working?

Also, what is Lygisk? I'm unfamiliar with that fork.
[Magisk] zgfg:
But new devices have originally been released with A11 (or A12).

Hence, it's not possible to spoof A10 on those devices just by 'downgrading' the Android version

Then we come to the 'suggestions' to spoof fingerprints from a 'close device' (where A10 or earlier stock ROM was available) - but that just opens a Pandora box with who knows what kind of problems, because the same fingerprints are also used by system apps and services to drive various components:

- go to MHPC thread and find people who experimented with the same and lost fingerprint or the whole touch

- on another phone it could be camera or who knows what

- not to mention that spoofed CTS fingerprints may screw OTA and therefore brick the system
[Magisk] helgi1507:
Yes, you're right.

Lygisk is a fork of Magisk (just rebuilds with some patches) which can survive after OTA updates.

GitHub - programminghoch10/Lygisk: Your Lie in Android

Your Lie in Android. Contribute to programminghoch10/Lygisk development by creating an account on GitHub.

github.com
[Magisk] TraderJack:
Interesting. According to why I see on the Telegram Channel, it is built using the latest Magisk so it is 25.1/2 and uses the Zygisk deny and not the old Magisk hide mechanism.

I can only surmise that the particular fingerprint for your device is still in the databases as only being valid for basic attestation despite it being a 12 OS. Again, I would expect that sooner or later (most likely sooner) you will being to see an issue. Once that happens though I'm not sure how safe any of us will be using different fingerprints. I see no reason for instance that the Pixel 3 XL 9 fingerprint works when the 12 doesn't, as that device should support HA even on 9.
[Magisk] Lada333:
Fwiw, I just dirty flashed v8.7 and it looks like contactless still works for me. I have yet to actually try it out though, I'm going off by Wallet telling me that my device is set up for contactless payments.

EDIT: Yup, still working as expected.
[Magisk] zgfg:
Do you have an info about the availability of your app on Google Play - so far I could not find yet

Could you provide more details, something like in YASNAC, to see the relevant data when eg failing

Also, I pass on Xiaomi Mi 9T although it runs MIUI 12.5/A11 (it's also in the fingerprint), hence I believe it doesn't use TEE but kind of Basic attestation and gets tricked by USNF functionality built into the Xiaomi.eu ROM - would like to see what's really going on there 😁
[Magisk] 1nikolas:
I was waiting for Google to verify my identity now they just need to approve it (should take less than 24 hours). Keep in mind that I've never fully tested it. I can't test it until it's up on Play Store 🥲
[Magisk] zgfg:
"Is this the verdict for my Does not meet device integrity", or I should look for something else in logcat:

07-25 19:26:40.410 W/IntegrityServic(27680): type=1400 audit(0.0:208304): avc: denied { write } for name="tasks" dev="cgroup" ino=21 scontext=u:r:untrusted_app:s0:c232,c256,c512,c768 tcontext=u:object_r:cgroup:s0 tclass=file permissive=0 app=gr.nikolasspyr.integritytest
[Magisk] 1nikolas:
The old app can't get you more info so looking at logcat won't help. Just wait till the new app is out
[Magisk] Displax:
Modification of Universal SafetyNet Fix with Play Integrity API bypass

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-87198517
[Magisk] zgfg:
Thanks👍

Xiaomi 11 Lite 5G NE, MIUI 12.5/A11 (as released with - ie original A11 device)

Previously, with USNF V2.3.1 I was passing SafetyNet with Basic type attestation, now with your v2.3.2 mod I can also pass Play Integrity with MEETS_DEVICE_INTEGRITY
[Magisk] shadowstep:
Works for me as well, on OnePlus 9R running stock OOS 11. (y)
[Magisk] jons99:
working well on pixel 5 latest google update thanks
[Magisk] Griffinx:
This is working fine for me in the shops on Pixel 6 even though the Wallet app is still saying that my phone doesn't meet the security requirements.
[Magisk] Dredead:
Edit: sorry, it had already been posted 🙂
[Magisk] V0latyle:
Wallet and GPay are both happy on my Pixel 5 with USNF 2.3.2. Make sure you clear data for both.
[Magisk] Griffinx:
Thanks, what other Magisk modules do you have installed?
[Magisk] V0latyle:
MHPC 6.1.2, Systemless Hosts module.

System is bone stock.
[Magisk] CSX321:
It used to be that clearing data for Pay wiped out your loyalty cards, but I think that's no longer the case, right? No real downside now to doing it?
[Magisk] V0latyle:
I don't have any loyalty cards, I wouldn't know. I only use it for my credit/debit cards.
[Magisk] letm:
After 4 days to try, Ok for me. I tested it today 2 times with success.

My phone >> Redmi 9T-M2010J19SY-RKQ1.201004.002/V12.5.8.0.RJQEUXM under android 11

my modules run under magisk stable V 25.2 (25200)

busybox for android ndk 1.34.1

denylist Unmount V0.4

Gpay sqlite ver V2.8

Magiskhide propos config V6.12-V137

SQLite universal binaries V1.4

Universal Safetynet fic V2.3.1

Zygisk LSPosed V1.83

If you use lucky patcher, you need to hide it >> tools box >> xposed >> check all and apply

Hide Zygisk LSPosed V1.83 if you use it >> Parameters >> Create the shortcut

uninstall G(oogle) Pay, install wallet via google play.

In magisk 25 : Hide in exclusion list >> wallet, google play, play services.

Now go to "Magiskhide props config" in terminal to reset it to default >>type su >>type props >> option "r" to reset and reboot.

after restarted go to "Magiskhide props config" >>type su >>type props >> option 1 (fingerprint) >> option f >> option 7 google >> option 26 pixel 5 >> choose 11 or 12 (depend of your version) >> type yes >> after dont reboot type N (no) and no terminal exit.

//I you have a Redmi 9T under android 10 use pixel 4.. (not tested) Don't test redmi 9T fingerprints They don't work.//

Active airplaine mode and Clear cache and data for wallet, google play, play services. Reboot.

After reboot de-active airplaine mode, wait 5 minutes and launch wallet. Link a payment card to try it and it should be ok, like the attached screenshot.

Note : Before use wallet, you can test that wallet passed all security with the apk @1nikolas >> https://xdaforums.com/t/discussion-...cussion-thread.3906703/page-130#post-87182459
[Magisk] zgfg:
Just few comments:

With USNF v2.3.2 (posted here few days ago - specifically for Wallet and Play Integrity), you should be able to pass without MHPC (since you have the rooted but stock ROM)

Even if you put Google Play Services to DenyList, USNF will remove it (open the list again and check)

Also, Google Play app should be checking through Google Play Services hence Google Play app should not need to be added to DenyList
[Magisk] zgfg:
Did Google approve? You will be the first to provide Play Integrity checker (based on this new API)👍
[Magisk] 1nikolas:
Well, Google is much slower than I expected. Sigh..

At leasted updates are verified within hours, just the initial verification takes very long
[Magisk] pndwal:
With the @Displax modded USNF even uncertified ROMs should pass without MHPC if the old fingerprint isn't a per-device issue... PW
[Magisk] zgfg:
Please read the post I was commenting to see why I wrote that

My point was to suggest to that user (with rooted stock ROM) to use Display USNF mod instead of MHCP
[Magisk] Displax:
To be more precise - only for "com.google.android.gms.unstable" (safetynet process), so even GMS itself (other it dependencies) do not seen modified fingerprint. So there should be no unexpected conflicts.

safetynet-fix/zygisk/module/jni/module.cpp at master · kdrag0n/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com
[Magisk] pndwal:
... So you really meant "you should be able to pass without MHPC (since your ROMs fingerprint prop is replaced for gms (specifically SafetyNet process) purposes).

But as I said, @Displax USNF with fingerprint spoofing as a MHPC configured fingerprint replacement is not limited to stock ROMs...

Of course official USNF does not currently adjust fingerprint props, hence the need for USNF or similar solution. PW
[Magisk] letm:
Thancks a lot : the mod of USNF by Displax work perfectly (y)

Simple and effective and I was able to deactivate :

denylist Unmount V0.4

Gpay sqlite ver V2.8

Magiskhide propos config V6.12-V137

SQLite universal binaries V1.4

Universal Safetynet fic V2.3.1
[Magisk] 73sydney:
I really wish people would let my GPay SQLite module die :)

Even putting "You prolly dont need it these days" in my sig etc isnt enough....
[Magisk] Griffinx:
I added a new payment card to the Wallet and it stopped complaining about security requirements!!
[Magisk] pershoot:
Hi.

I used USNF 2.3.2 from Displax and this took place:

1. Took about 24-48 hours for the security warning in 'Wallet' to come off.

2. Tried to pay today, check mark ok on phone, but the connected card was declined at the vendor (the card was fine; used it directly thereafter in the machine to pay).

Bramble (latest update), latest Magisk + Zygisk.

Letting you know.
[Magisk] V0latyle:
I think embedded GPay overrides Wallet on my Pixel 5, but tap to pay works for me.
[Magisk] pershoot:
I have now changed to USNF 2.3.1-MOD (Displax)

Tap to Pay: Success!
[Magisk] Photopuppet:
@Displax Thank you for your help, this worked great!
[Magisk] 1nikolas:
The app is finally public! (thanks Google for taking a week to approve this 🤦)

I made it beta testing since I haven't tested it on much devices. If you find any problem, please open an issue here and I'll take a look at them once I return from vacation.

Play Integrity API Checker - Apps on Google Play

Get info about your Device Integrity through the Play Intergrity API

play.google.com

Source code:

GitHub - 1nikolas/play-integrity-checker-app: Get info about your Device Integrity through the Play Intergrity API

Get info about your Device Integrity through the Play Intergrity API - 1nikolas/play-integrity-checker-app

github.com

GitHub - 1nikolas/play-integrity-checker-server: Node-js server for the Play Inegrity API Checker app

Node-js server for the Play Inegrity API Checker app - 1nikolas/play-integrity-checker-server

github.com

If you are curious, the possible outcomes I've seen are:

3 ticks (unrooted samsung)

tick/tick/x (unrooted redmi note 4 with unlocked bootloader)

x/tick/x (my rooted a11 op7t)
[Magisk] zgfg:
Thanks👍

Xiaomi Mi 11 Lite 5G NE, stock A11, rooted (ofc, Bootloader unlocked), USNF 2.3.1-mod

IMO, as expected, cannot pass MEETS_STRONG_INTEGRITY since USNF spoofs to Basic attestation to pass CTS - Hardware Backed would require TEE that cannot be spoofed)
[Magisk] lukasikcz:
Hi, i installed the newest version, all working (banka, netflix, gplay, ... ) but gpay still not. Stock version of android. Anyone help?
[Magisk] shoey63:
Lucky me with Rog phone 3😋
[Magisk] pndwal:
Assume it's unlocked/rooted...

What do you see in Momo? (Does your device have broken keymaster implementation?)... PW