yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
just a general tip, be aware that something as benign sounding as replacing fonts, using font modules, can give up root status. not directly related to current issue, but worth knowing...
[Magisk] 73sydney:
@rodken , all

i just got hit by the weirdness, see here

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

it doesnt discriminate after all:)
[Magisk] aricooperdavis:
Quite unexpectedly mine is now working again! All I did was disable "Enforce DenyList" and replace it with Shamiko, install LSPosed and the Core Patch module, and do the cache clearing and rebooting.

Now the Google Wallet app has the same UI as rodken, which is also interesting.

I have no faith whatsoever that what I did actually fixed the problem, and as such assume it'll break again directly.

Edit: I tried to add a card to Google Wallet and, surprise surprise, it wouldn't do it and now it says my phone doesn't meet requirements 🙃
[Magisk] _Raziel666:
I guess from the various cleaning of cache/data and reboots, my phone doesn't want to boot anymore. So beware, guys and gals!
[Magisk] 73sydney:
at this point someone needs to wake up @pndwal and get him to call his mate on the inside :)
[Magisk] rodken:
I took the liberty of trying to replicate your issue of adding a card - a lo and behold, I am still able to add said card - even after removing it from Wallet [go figure].
[Magisk] rodken:
Are you running a Custom ROM?
[Magisk] _Raziel666:
Yes I do. Any ideas? Sorry for the offtopic and thanks!
[Magisk] Lada333:
Try disabling magisk (modules)?
[Magisk] _Raziel666:
Theoretically, I've flashed my ROM so Magisk is not active.

Some Magisk-related TWRP functionality doesn't seem to work.

I thought about removing /adb folder, but I will look into it after I backup my internal storage...
[Magisk] ezdiy:
Untested, but might work: In MagiskHidePropsConf, select 'Nexus 5' as CTS profile to spoof. Or any phone that originally shipped with Android 6, but had NFC. The idea is that Google didn't nuke support for pre-2014 NFC phones just yet, but merely narrowed down their CTS checks, and now reject fingerprints that ought to have working HARDWARE_BACKED SafetyNet attestation.
[Magisk] rodken:
If your device truly refuses to boot anymore - dirty flash the Custom ROM?
[Magisk] _Raziel666:
It reaches a point where it shows the Google logo and stops. If I long press power button it shows the power menu. Really haven't seen this all these years with Android...
[Magisk] Gintskk:
Seeing as I am also affected by the Google Pay not working issue: I tried your suggestion.

Set device fingerprint to Nexus 5 via `props` but now even basic integrity and CTS profile fail (they were passing before). I assume this happens because of a mismatch to the actual model of my device.

Resetting to the original fingerprint fixed SafetyNet, but Google Pay still not working/Netflix still not appearing on Google Play Store.

Installed v: Google Play Services 22.24.13 (190400-455379205), Universal SafetyNet Fix 2.3.1
[Magisk] rodken:
Before or after dirty flashing?
[Magisk] ezdiy:
Yes, I've encountered this for a while that fake profiles don't work correctly quite often. Presumably, if Google started looking whether any given CTS profile should have TEE, they may also check which android version they should be running.

Somebody with an old Nexus / LG on Marshmellow should check whether GPay is fine for em (in which case its just matter of improving propsconfig module to fool DroidGuard reliably). These things genuinely should continue working even with BASIC attestation only, up to Android 9 (Nexus 6 era or about).
[Magisk] _Raziel666:
Both before and after.

The same behavior before and after.

For now I made a clean install and will keep an eye here for any developments.
[Magisk] Lada333:
Sorry, what? If you've just flashed the ROM, and don't have magisk, wouldn't you fail safetynet to begin with? Since bootloader is unlocked? Am I misremembering how this works?

Wdym by magisk related twrp functionality? What device are you using?
[Magisk] _Raziel666:
I don't know what you're talking about. My phone wasn't booting to the launcher screen, it didn't even ask me for a PIN.
[Magisk] helgi1507:
I used to run with custom props (Samsung S10e, Android 12) as always, but Gpay stopped work suddenly after update to the new google wallet.

So I've tried to change props and figure out, that it's working with old versions which is included in the latest props-config. I use Android 11 signature and Gpay finally allowed me to add credit cards.

Meanwhile, none of my custom Android 12 props works as before...
[Magisk] rodken:
My apologies - considering that dirty flash is usually but not limited to only wiping cache and dalvik then flashing the Custom ROM.

-- Not really a Bonafide remedy for fixing and/or repairing corrupted data/files.
[Magisk] ezdiy:
Interesting! It would make sense to first roll this out on A12 fingerprints, as old devices that can't do hw attest are super unlikely to run that.
[Magisk] Zotyoo:
Hello! I encountered the same problem as others here: GPay was renamed today, which in itself would not be a problem. Unfortunately, touch payment no longer works because the phone is not compatible. I was able to update the app on the smart watch (Samsung Watch 4), which worked, but after that the card had to be set up again on the phone. Google Play data deleted, Services also deleted, Wallet data deleted in airplane mode, then reboot, exit airplane, enter play store, wait, but it didn't ask me for any list or anything. The downside is that now there is no payment on the watch, and you can't set it up on the phone. This happened once before, but then the card data was not lost, so it was not necessary to enter it again. The payment did not work, but after a few hours it was restored by itself. Can this be expected now, or what can be expected? Phone Samsung S10 Magisk root (Android 10), v23 Magisk, Riru 26.1 .4, Universal Safety NetFix 2.1.3. All banking applications pass and are safe, safetynet passed, everything is green. Does anyone have any ideas? Thanks!
[Magisk] stalker780:
Same for me Samsung S8 Android 8 after update to Google Wallet.

Tried to restore latest backup of GPay, did not help, it does not work anymore.

What I have noticed in Magisk 25.2:

1. I check DenyList for all Google Play Services

2. Restart a phone

3. Check DenyList. It's ok. Close Magisk. Close, not hide.

4. Execute GWallet and get a notice I cannot use it

5. Check DenyList and Google Play Services are unchecked there

Looks like Google Play Sevices can unhide itself now :)

All of my local banking applications work and don't see root.
[Magisk] Gleniu:
I believe that this is expected if you are using Universal SafetyNet Fix, but can someone confirm?
[Magisk] alagga:
Yes that's right and expected behavior
[Magisk] stalker780:
Yes, I am using SafetyNext fix.

Hm... Sorry then. I did not notice this behavior before. Perhaps because it just worked, so I did not check so thoroughly.
[Magisk] Zotyoo:
On S8, a simple MagiskHide is also enough. Nothing else is needed. No tricks are needed on Android 9 either.
[Magisk] pndwal:
You are my mate on the inside... What you got? 🤪 PW
[Magisk] stroke55:
Same problem with my wife's Pixel 4a 5G on latest Android 12.1 with Magisk 25.2 and Universal SafetyNet Fix 2.3.1. SafetyNet passes, Playstore is certified and banking apps don't detect root. Tried also Shamiko without success.

Google Wallet on my Pixel 6 Pro is still working.
[Magisk] stalker780:
MagiskHide was in Magisk 23. I don't remember why, but it seems I had to update to 24 and 25 because of one of my local applications.

Anyway, everything works now except GWallet. Hope this will be fixed as this update affected lots of users.

Also my new S21+ is on it's way to me, so I will have to move to Android 12 in a few days :)
[Magisk] xdxita:
I think this behavior is from USNF.
[Magisk] stroke55:
Does Netflix show up in the Playstore?
[Magisk] BootloopedMillennials:
For those with a disappearing Netflix are you on Play Store version 31.4.11 or 31.5.16 or?

I'm on 31.4.10 and Netflix is still there. As well as the device certification section in play store settings. Some said this was gone too.
[Magisk] stalker780:
Nope. I have never used it. But search in GP does not show it.

GP 31.4.11
[Magisk] sam0056:
It certainly is a major headache been embarrassed a few times in shops lately when it didn't work.
[Magisk] 73sydney:
Fudge!

Today mine stopped working after a Google Pay update "Error you cannot pay in shops with gpay anymore".....was fine before that...well you know besides it wasnt working on Google Play Services 15, but did after i downgraded to 14 and it then mysteriously upgraded itself (after i turned off background data etc) back to 15....and worked....

Now its cactus with error as above

Google Pay version 2.84.23748778

Google Play Services 15.0.90

Magisk 18.1

WTF is going on here......please, end the madness someone....
[Magisk] D-m-x:
Yeah, I didn't think this would be such a huge issue in the beginning. The thing is you can't test it from home, just in stores. Really annoying.

Anyone have reliable information if it's fully working for completely Stock Phones? I'm getting the feeling it could be a GPay issue rather than a Magisk one.
[Magisk] caluz78:
I'm on Oneplus 5T latest OXYGEN OS Beta, with Magisk Stable 18.1.

The only way to make it work is to downgrade to Google Play Services 14.7.99.

Other versions (also beta) never worked for me.

The only way to test before trying in the stores, is removing and readding card in the app.

Now everything works with:

- OOS Beta 26

- Magisk Stable 18.1 (no apps hide, no magisk app hide)

- Google Play Services 14.7.99 (i wish never upgrades)

- Google Pay 2.84.237487748
[Magisk] Destroyer706:
I'm on Mi Mix 2 POSP rom. I updated to the beta of Google Play Services. Uninstalled Magisk 18.1, cleared data of Google pay, playstore, services and services framework.

Then I flashed Magisk 18.1 stable again and could add card.

Paid 3 times with gpay yesterday without any further problems.
[Magisk] tlf55:
You want to stop all these madness ? just one solution..

Update to Canary build (18.2.xxxxxxxx) , go to magisk hide, Hide Google Play service, Hide Google Pay, reboot. (if it's still not working just clear data should do the job too)

And voila, all of you are complaining about Google play service updating itself, it's NORMAL, it's Google way to keep your device "secure" and "updated"

If you don't want to update to canary build, just stay calm and wait for topjohnwu to update the stable or beta version to 18.2. All other workaround that says that you have to downgrade the play service won't work that long as google always update play service in the background by a way or an other.
[Magisk] pOOBAH1973:
Zero solution here. Magisk > 16.7 makes my phone (ZTE A2017G with stock Oreo) stuck in a reboot loop.
[Magisk] xocomaox:
I had downgraded to fix this a week ago... Worked okay even after it auto-updated. However, today it stopped working.

This is the best solution, in my opinion:

https://xdaforums.com/showpost.php?p=79114224&postcount=246

I did it today and am now on Magisk Canary 18.2 build with 15.0.90 Play Services and it's working great.
[Magisk] gozzaa:
Doesn't work for me. Tried rebooting and clearing data/cache of pay and service several times. Google pay still says iam rooted
[Magisk] lesharodin:
Me too, started today. I allready tryed everything, and gpay still says im rooted.

mi8, magisk canary, all up to date

UPD: Google Play service downgrade to 14.7.99 helps, I was able to add a card to pay, tomorow will check if it will work.
[Magisk] prot-:
Tried all these things never works for me
[Magisk] PuffDaddy_d:
Tried this and somehow broke Google play services. Can't open Google Pay app at all and play services is not listed as an admin app anymore either, plus I can't roll back updates or side load new ones.
[Magisk] KKenna:
If this helps anyone...

I've been struggling with this for a week. I can follow the instructions for downgrading GPS and everything works - for about three hours until, no matter what I do, GPS gets upgraded.

So...

I tried the upgrade the the beta of GPS. No luck for me as it wouldn't let me verify any cards. Tap on the link, and... Nothing!

So...

I downgrade the 14... of GPS, add and verify all my cards for in store. Then, immediately upgrade to the beta of GPS 16.0.86 and...

SUCCESS!

I just walked across the street and made a purchase!

**** you Google!
[Magisk] HamsterHam:
Mine was working fine after downgrading etc. Then play services updated itself and it was fine. Now all of a sudden it stopped again.

These workarounds are temporary solutions until it stops again. Might be a day or 2 of good use maybe even 3 but it'll stop again.

Only thing I haven't tried is that new beta.
[Magisk] ArkadashShefirr:
- update magisk to latest beta , hide it from google apps

- remove /data/data/com.google.android.gsm/ directory

So, google pay works now
[Magisk] sam0056:
New version 18.2 magisk is out and i was able to setup my card I guess it should work now.
[Magisk] D-m-x:
Nice. Anyone know if Gpay "remembers" a flagged card? I mean in the sense of do we have to remove and add the card? I didn't do anything in the meantime and would like to keep my transaction history.

Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
[Magisk] gozzaa:
Clearing the data manually actually worked for me. Google pay works now and everything up to date
[Magisk] BlenderFox:
I installed the oldest gapps I could find at the gapps github repo: github.com/opengapps/arm/releases?after=20190222 (can't post url tags since I don't have enough posts yet)

Installed this via TWRP, rebooted,

Had Google Pay on Magisk Hide, setup up (NOTE: it was _really_ slow for some reason), got the message from my bank (Monzo) saying my card had been setup.

Removed Gpay from Magisk Hide, switched to Gpay, force closed, and reopened the app, and then went to buy something (used an office vending machine with an NFC reader as a test). And it worked, and the transaction immediately showed up on my app.

App versions:

Magisk: v18.1 (18100) -- not canary/beta

Magisk Manager: v7.0.0 (185) -- not hidden

Google Play Services Version: 15.0.90 (100300-231259764) with background data disabled

DISCLAIMER:

This worked for me, it may or may not work for you.
[Magisk] joeyddr:
Pay broke on me again this morning, used it yesterday with latest canary and services 15.0.90... clearing services app data allowed me to add cards back and use it again... not sure what is going on.
[Magisk] stroke55:
My 4a 5G is on 31.4.10 - no Netflix altough Store is certified and SN check passes. Weird...

Edit: I mean it seems you can no longer rely on both certifications since the store seems to be limited regardless of the certifications as long as you cannot use Wallet/Pay due to root detection.
[Magisk] Nova_Max:
I can't confirm that older Android versions work better. I'm on Android 9 and Wallet isn't working.
[Magisk] Lada333:
Netflix doesn't appear in play store for me neither. I don't use it, so I'm unsure if it was there before or not. We can safely assume tho, that it's not google pay that's broken, but something closer to the system itself?
[Magisk] BootloopedMillennials:
Maybe like someone mentioned earlier, it has to do with checking for "Hardware-backed" Attestation. On devices that came with it enabled instead of Basic.

I'm fully expecting to lose Netflix in the store soon. I'm on the latest Play Services (not Beta though) but my Play Store hasn't updated to the latest (though it says it is on the latest).

Don't know.
[Magisk] 1nikolas:
Hello same here, Gpay/Wallet stopped working after the update (and a bit prior to this so this should be a Play Services thing). Also Netflix doesn't appear on me too (had never install it). If I open it through Google it says device not compatible. Is there any new option on the Play Console to block rooted phones?

EDIT: yes there is, have no idea if this is new

It's this api
[Magisk] Phil21185:
Jumping on.

Same behaviour, S21FE, A12, Magisk 25, Play Store 31.4.10-21, can't add cards, Netflix gone.

SN passes on Basic with USNF (2.2.1).

Device shows as certified in Play Store

All other security conscious apps work fine still.

Interestingly though, I added Play Store and Services to deny list when trying to fix this (when I still though it was something dumb I had done and not a widespread issue!), forgetting that it isn't required, but both stay on the list after reboot, despite what others have said regarding USNF...
[Magisk] ezdiy:
Can you try spoofing "close enough" CTS string for Android 11?
[Magisk] Brava27:
Notworkig anymore. Here like the rest of you guys.
[Magisk] nodio:
any light on the end of tunnel??? still hoping for the fix
[Magisk] trabando:
For me it's not only Google wallet that stopped working. Also company portal app from Microsoft is suddenly detecting root after updating blocking me from using my work email on outlook / Microsoft teams. Reverted back to a version from May to get it working again.
[Magisk] 1nikolas:
UPDATE 1/8/2022

This app is officially discontinued in favor of a new app I published on Play Store. Read more here:

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

====================

ORIGINAL MESSAGE:

I just made this simple app which tells you if your device passes the new Play Integrity API (which is presumably what Google Pay and Play Store use to detect root now). If you don't trust random apks from the internet feel free not to use this. I'll upload the source code at a later time since it's very junk now (probably on github).

You can use it to play around and see if you manage to get it to pass without having to mess with Google Pay. There are screenshots of the 2 possible outputs (pass screenshot is from an online emulator).

Also I didn't test it much since I don't have many devices that can pass. Hope it works fine 🤞

Hope this helps someone find a solution :)

EDIT:

Here is a quote from Google of what exactly "Does not meet device integrity" mean:
[Magisk] un4free:
Hopefully there will be a bypass.

Does anyone know a real alternative to google pay/wallet?
[Magisk] dimon222:
On device that doesn't have Google Wallet update pushed yet - app still gives "pass".
[Magisk] Pshemo__:
I'm lost now... Does it mean that it's still something else?
[Magisk] Phil21185:
I'll give this a try tonight. Thanks for the link!
[Magisk] Gintskk:
It worked! After I set my device's fingerprint to one with my device model from Android 10.

This is probably not a long-term solution, I expect Google to add a check for a matching Android version eventually

Google Play Services version 22.24.13 (190400-455379205)

Universal SafetyNet Fix v2.3.1

Device: SM-N986B/DS (c2s) on A12 stock OS with Magisk/unlocked bootloader.

I have also set sys.oem_unlock_allowed to 0 via MagiskHidePropsConfig for other sensitive apps

AFAIK no, there is not: @1nikolas app should test the strictest Google Play verification that is also used by Google Pay now.

I had the same situation as you do. From there I did the usual "clear play services data - clear play store data - uninstall google pay - reboot - install google pay - add google pay to magiskhide again" and now it works. I don't know what else differs in your setup, but this is what did the thing for me.
[Magisk] unxcepted:
That's interesting - but could you try to just leave the sys.oem_unlock_allowed, and revert to the old cts string? Maybe Google just started looking for unlocked OEM explicitly?
[Magisk] Gintskk:
sys.oem_unlock_allowed was set to 0 for me from the beginning, and it was 0 already when I had the original A12 CTS string. I think it makes sense that if you have the CTS string from an Android version that did not support hardware attestation yet, then it is not attempted at all.
[Magisk] setmaster:
I have uninstalled magisk via restoring Boot Image and have no more root, but still getting the message, that my OnePlus 8Pro does not meet device integrity (rooted).

What else can I do?
[Magisk] Gleniu:
I can confirm that. I changed my Redmi Note 10 Pro A11 fingerprint to Redmi Note 9 Pro A10. Cleared Play Store and Play Services data. Rebooted. 1nicolas app shows that I meet requirements. Contactless payments work. Netflix is back.

Thank you very much for your ideas. I believe that we need permanent and universal workaround, but for now I'm happy - even if just for 1 day or 1 week or 1 month :) Best regards to all the Google employees who follow this thread, just leave us alone, guys :D
[Magisk] alagga:
Short help for using the Magiskhideprosconf Module:

I only have to pick my device from this list, copy the complete line as ### and after installing the module run it as

props ###

In Terminal?
[Magisk] Gleniu:
You need to type 'su' in terminal, next type 'props' (of course without quotes). Then you will see the MagiskHidePropsConf menu. Number 1 is 'change device fingerprint', then you just need to find the correct fingerprint. This module has a large base of fingerprints. Basically, you only confirm your choices by inputting different numbers :)
[Magisk] Gintskk:
Note, you can also paste your own CTS string of choice after selecting menu option 1
[Magisk] helgi1507:
All is working with old props for now (except Android 12 and above)
[Magisk] alagga:
Can confirm CTS spoofing is working for me too (Samsung S20FE 5G with Android 12 rooted stock rom). Thanks everyone 🙂

Edit: Some people from another group confirmed that playstore is certified with newest Magisk Version (though wallet still only works with CTS spoofing).
[Magisk] Cailloux92:
Hello Guys,

Same here, was not able to pay since 24 hours.

Issue is solved by using a FingerPrint of an Android 10 device.

Thanks for the workaround, and let's wait for a fix !
[Magisk] decayed.cell:
Tested working on S20 5G A12 spoofed to S20 Ultra A10
[Magisk] glennza:
I've got a Samsung S9. I believe this is an Android 10 device. Should I just select S9 from the list or a different model?
[Magisk] floppy110112:
I installed MagiskHide Props config zip inside Magisk as suggested

Activated module, rebooted phone

In Termux app (see Play Store), got root by typing "su" without quotes

Opened props config editor typing "props" in termux

Navigated into menu, applied an android 10 fingerprint

Rebooted the phone again

Cleared Google Wallet data only

Now NFC payments via G Wallet app are working on Redmi 10, Magisk 25.2 and Android 12. Thank you for all the help.

I haven't touched this setting, I only changed the phone fingerprint without clearing play services cache and data and it worked.
[Magisk] helgi1507:
You could try select whatever you want except A12 fingerprints
[Magisk] simion_levi:
Thank you- Pixel 4 XL A12, spoofed to Pixel 4 XL A11 is working for me.
[Magisk] itsmir:
Mi 9T here(on A11 EEA global), spoofed to A10, cleared data etc, still not working :(
[Magisk] infyrno676767:
I use a Redmi Note 9 Pro and I changed the device footprint to a galaxy s20 after trying the note 8 pro and it not working. At least samsungs are still good for something! Google pay works and netflix is available to download again. Cleared data, not cache, on play store and google pay, uninstalled the update for google pay, am using gpay instead of wallet (old android version) and rebooted. Works flawlessly.
[Magisk] samy233:
Xiaomi 11T Pro (A12) , spoofed with Xiaomi mi 10T pro (A10) , cleared cash on Playstore and Gpay.

All works fine (Pstore Certified , Netflix is back , Gpay OK)

Thank's @LL
[Magisk] Ad4mo86:
Spoofed my Mi9T to Pixel XL4 A11, worked like a charm, hopefully a long-term solution comes for Zygisk hide soon
[Magisk] onesolo:
I'm using a module for unlimited google photos. If I spoofi another fingerprint, does photos unlimited backup will stop??
[Magisk] Evo400:
Oh my god!! That's what it was in my case. Pure coincidence. I changed the font, then Google did an update and bang. G PAY stopped working. I reverted the font, reboot and viola. Back working. Thanks man
[Magisk] Gleniu:
What device are you using and what font module exactly did you use? I'm asking, because I'm usinge Google Sans Prime module - I just love Google Sans font.