yashsingh1/xdaforums huggingface dataset:
[Magisk] IM0001:
My Pixel 2XL seems to be completely unable to turn on Contactless Payments no matter what I do short of Relocking the Bootloader (Which I may try just to see if I can get this crap to work again.)

Disregard the complete loss of my Google Cloud Backup for stupid reasons, I did a full wipe last night, flashed the full April Factory Image, and also flashed either the EX Kernel, or Stock with Bootlooder Block only, and GPay still didn't work. (Device is Rooted or Modified) (Wiped and reflashed between both, just to be sure. Then tried just plain stock with Magisk 19.1, still cannot turn on Contactless Payments no matter what I do. (Tried blocking all the correct things, renaming/deleting the data/data/*.gms folder, etc.) All the cards are still in my GPay so I am not re-adding them, and I was actually able to activate Contactless payments on my Essential Phone with nothing but EX Kernel and no Magisk installed.

So Is there some caching of the card in G-Pay that they need to be re-added after all this to get them to be allowed on a phone again? Is there anything I could be missing that I need to Wipe/Flash to get the phone to look stock to GPay short of actually going completely stock?
[Magisk] Flipz77:
It's installed as a normal Magisk module, then enabled and configured through a terminal app.

I'm running it with Magisk Canary on the Q beta.

The module is able to change my device fingerprint to stock Pie so it can pass all the checks.

I've never had to touch any folder but I still use Magisk Hide on Play Services and GPay just to be sure.

I hope it works for you as well
[Magisk] twotimer:
Sharing my experience. Some time in late March/early April (or was it around April update on my Pixel 2?) I had to do the trick with wiping the .../somthsmth.gms folder. After re-adding the cards/Paypal everything worked up until about late April, when Google has updated something. After that I could no longer pay contactless. Then the Magisk update arrived, after which I've wiped the ...gms folder again and re–added my cards/paypal (loosing the transaction history in GPay, which is unfortunate). After that, NFC payment with N26 card added to Gpay works OK.

I guess it's gonna be a never ending battle between the devs and Google after all.
[Magisk] warrencoakley:
So what do I need to do in terminal?
[Magisk] ChillerMarvin:
sadly this doesn't work for me. how long should i wait until i try to add paypal again?
[Magisk] JarlPenguin:
Is basicintegrity showing up as true?
[Magisk] ChillerMarvin:
yes, both basicIntegrity and ctsProfile are showing up as true. (magisk 19.1)
[Magisk] bravoxray23:
I have exactly the same problem! I'm using mi mix 2s with xiaomi.eu ROM. I've been monitoring this and xiaomi.eu forum waiting for someone who has the same problem to no avail until now. I hope there's a solution for this.
[Magisk] Paz9:
not relevant

i pass CTS and basicintegrity

there is something about gps and detecting root.

it works fine on 16.0.91 but on 17.x version of google play services nothing works.

---------- Post added at 03:33 PM ---------- Previous post was at 02:59 PM ----------

doesnt work with the new gplay service 17.x

---------- Post added at 03:36 PM ---------- Previous post was at 03:33 PM ----------

contact your banks?

ive attempted to add my card some 50 odd times and i reverted to stock and it still works.
[Magisk] coolzizi:
Hi,

Which apps i shouldnt update after downgrade gservices? Aparat from gservices of course ;)

Wysłane z mojego Pixel 3 przy użyciu Tapatalka
[Magisk] zencooler:
Google Play Store. But it is not enough as GMS is automatically updating itself. You should freeze Google Play Store or disable some services desribed few post before on this thread).
[Magisk] Brusington:
This worked like a charm. Thanks for this ?
[Magisk] loadie:
Sorry, tagged the wrong post..
[Magisk] dvhttn:
Another update. Since the above comments I've upgraded my S7 to a Pie ROM (the Blackdiamond NFE port - clean install obviously). Google Pay and Google services have updated a couple of times. Magisk is now - MM 7.1.2 (208) and Magisk 19.1 (19100). Re-set my cards in Google Pay via my bank (have to contact my bank every time - not that much of a pain) after the last MM upgrade. All other settings are as above for MM and used GP twice today.

Maybe I'm lucky still .....
[Magisk] IM0001:
Did everything I could think of short of re-locking my bootloader, but Google Pay still says my Phone is Rooted/Modified when I try to turn on Contactless Pay. With a full factory image flashed and a kernel that should have the bootloader unlock hidden, what else could it possibly be seeing that triggers it to appear modified? If it's blacklisted, how would I go about UnBlacklisting it if that's even possible at this point.

Essential Phone with Only the EX kernel was able to add a card just fine so I know the Kernel can be hidden without Magisk.
[Magisk] Alpetrus:
Flashing stock firmware and relocking bootloader did not solve the problem for me, too. I think the only solution is to send the phone back to the service in order to flash the signed firmware :(
[Magisk] IM0001:
So the question then is, where is Google keeping this?

A Flashed back to stock Image/Locked BL phone should be all that AP needs so where else is this "Blacklist" Being kept?
[Magisk] IM0001:
Going by what I found about this app Auditor it definitely looks like Google may have finally switched on the switch to use the Hardware Security in our Pixel 2+'s that could be used to check for any modifications whatsoever. Mine does Fail so I'd check with any device that doesn't work (and some that do even) and see if this is the case.

You can also get a modified version that doesn't need a 2nd device from here
[Magisk] Windroid-user:
Literally just applied for my first current account about an hour and a half ago.

Can you explain what you mean by "free physical card"

Just looked it up and seems to be a pretty interesting choice.

Could you tell me why you chose this branchless bank? I'm curious, you might want to pm me instead of replying here since it's kinda off topic

Btw for everyone else Gpay has been working for well... correct me if I'm wrong but has it cut off any old transactions? Makes it harder to tell but I can confidently say it will be or has been a month with GPay working flawlessly.

You may be like what I thought you just said you applied for a bank/current account? Well the answer is simple, it's not mine:cool:

Enjoy Gpay but I'm out once I get my card, that's if I have to fiddle with it extensively to get it to work.

But so far so good:fingers-crossed:
[Magisk] bravoxray23:
I've tried contacting the bank multiple times and they always said they don't see anything wrong with my account. :rolleyes: I've told them to make a request to their technical support to check on my specific device. Not only my account. Let's see what happens. In the meantime I'm wondering if there's any way to spoof my device so the bank sees another device instead of my phone.
[Magisk] elitewarrior:
Does Magisk do anything to hide an unlocked bootloader? Or does it only hide itself? I have an unlocked bootloader and a custom kernel, thats it, and my pay wont work. Ive already wiped it and it worked for 2 weeks but its broken again. I am pretty sure GPS isn't detecting root, it's detecting unlocked bootloader and if newer versions of Magisk don't do anything to mitigate that then everyone who he gets it working after some insane sequence of steps will eventually break. I would rather go full stock then have to consistently fiddle to get it working and I plan on doing it after playing around in Android Q beta 3. Don't wanna factory reset an extra time lmao.
[Magisk] cls2:
I'm also thinking to go back to full stock due to Gpay not working with unlocked bootloader. So far I haven't found a way to go full stock though (Huawei Mate 10 APL-L29). Do you have a way?
[Magisk] froader:
I'm afraid full stock with locked bootloader may be the only way I can get GPay working again on my Pixel 3 XL. That requires a wipe though, I'm not interested in dealing with if I don't need to. Hopefully, Magisk will have a fix soon. Difference of carrying a thin and thicker wallet. Sure nice to have GPay!
[Magisk] irony_delerium:
So, I know it's not detecting root, nor is it detecting unlocked bootloader - /init on my device masks it instead of the kernel, as I'm using the Huawei stock kernel on a custom ROM - but it would still fail. (SN passes consistently.)

At the moment, I've managed to hold on to GMS 14.7.99, no forced updates or anything yet. Pay has kept working for the past 2 months and probably will until the update is forced on me again, at which point I'll probably end up having to pull out a card to pay everywhere. (Obnoxious, because the phone is easier to grab usually.)

The one thing that comes to mind is that potentially Google changed GMS to use hardware attestation through TEE in v15+, and while the bootloader lock state can be hidden from userspace, it can't be hidden from TEE as easily, if at all.
[Magisk] Tr4sHCr4fT:
same for me...

i think a hard reset and back to stock is the only way
[Magisk] D-m-x:
Wow, if this is really the way they are handling things now, wtf is wrong with Google? Going back to Stock is fine but why are they hassling people even more by denying GPay even on those Setups.
[Magisk] highdiver_2000:
What is TEE?
[Magisk] ssceddie:
http://lmgtfy.com/?q=Android+tee
[Magisk] Itachisasuke:
The only way to prevent direct Hardware Attestation Checking would be a shunt of some kind either hardware or software similar to how you would intercept actions to a TPM chip on a PC.
[Magisk] ssceddie:
So we hold on, the easiest way is to keep the playservices at 14.7.99.
[Magisk] pittrich67:
That's works for me, thanks

Gesendet von meinem MIX 3 mit Tapatalk
[Magisk] Forever Alone:
The question is how do I downgrade Google play services? My GApps latest lol.
[Magisk] ssceddie:
Maybe could write a dev a script/flashable zip that delete previos gps and install 14.7.99....
[Magisk] pittrich67:
Disable "Google Pay" and "Find Device" in device administrator. Then you can uninstall the updates of the Play Services.

Gesendet von meinem MIX 3 mit Tapatalk
[Magisk] warrencoakley:
How have you stayed on 14.7.99? When I try it keeps updating back to 16.
[Magisk] irony_delerium:
Disabled the "Android Setup" app, turned off "Modify system settings" on Play Services, and turned off automatic updates in Play Store. (Also been careful about updating apps - I suspect that once setup is done, GMS updates automatically in response to a needed feature, or at least demands the update. As such, I've got at least 15 pending updates.)

I disabled setup more because it would continually pop up asking me to finish setting up my phone, which is probably an integration bug on my part.
[Magisk] zencooler:
It was discussed on this thread few times how to keep GMS not updated.

You can go back to previous posts to read about few methods.

The best one IMHO is to block cache folder (details in previous posts) and to freeze Google Play Store app. This both will definitely stop GMS autoupdating possibility.
[Magisk] bigmikey307:
I don't think it's a coincidence, Google pay not working on my OnePlus 6t too
[Magisk] elitewarrior:
I'm a pixel so it's as simple as flashing the original system image and relocking the bootloader, can't speak for other phones tho sorry

Whatever the case the end result is that they know its an unlocked bootloader and holding onto an old version is not a good long term solution as for sure it will be blocked eventually. Magisk won't help because its job is to hide it self not other things. People will have to choose Gpay or root and for me it's a simple choice of wanting Gpay. But let's see what happens as experienced devs look into it.
[Magisk] karnasw:
I also have unlocked bootloader. Tried every solution in this thread. None of them helped. I lost my most important function in phone.
[Magisk] IM0001:
The problem I have is the only reason I root now, is for Titanium Backup.

Too often do I either get screwed by the cloud backup option, or does it just not backup what I want overall that makes restoring a device a royal timesink pain in the ass. Titanium Backup gives a very helpful security in grabbing everything, and being able to restore the data for countless apps that loosing that ability is almost not worth it.

Is there any other app that can do near to what Titanium Backup does that doesn't require root?

*One other reason for a Unlocked Bootloader even without Root, is for those stupid rare but serious occurrences like the bootloop of death on the Nexus 5X/6P. With a locked bootloader you were SOL short of freezing your phone to get it to power up one last time to possibly back things up. But with it unlocked, you were able to borrow some more time by flashing a modded kernel that disabled the big cores that were dying in the phone allowing you to resume using it to guarantee everything was backed up.
[Magisk] drup88:
I just tried updating to magisk 19.1 stable and I can start adding cards again. Didn't change anything else. Going to test an actual purchase and report back. Anyone else tried?
[Magisk] PriMieon:
Stopped working for me.

Google pixel 3

-Play service 17.1.22

-AOSIP ROM May 7th 2019

-May 5th vendor.img

-Magisk 19.1

-Magisk app 7.1.2

-Magisk hide: EVERYTHING Google related (even system apps) and Pokemon GO

-cleared GPay cache, storage

-Deleted GPay, reinstalled it, hid it again in magisk and tried to set it up with mobile data

-latest busy box

-No custom Kernal

-deleted the Data/data/com.google.android.gms (hope I typed it correctly) directory

I've done all those things a few times. No good
[Magisk] warrencoakley:
It's the 17.1.22 thats causing the issue. You'll need to roll back.
[Magisk] irony_delerium:
Nope, it's absolutely not a good solution. It is, however, the only solution I've had that's worked so far.

I fully expect that it'll fail eventually - even if that failure simply is because newer apps start depending upon newer Play Services. In the meantime, until it's possible to figure out what the actual trigger for the failure is, it's mostly a matter of either digging through obfuscated Java, hoping Google reverts the changes, or waiting for someone else to find a workaround for it. There's various ways to keep GMS from updating, but so far there hasn't been much in the way of progress on keeping GPay happy.

One thing I did find digging through smali from decompiling GMS (16.0.89) is that the code path which sets fails_attestation seems to be related to SafetyNet, but I haven't gotten too much farther through it. (Trying to find code in classes named "abhq" just gets really hairy, really quickly.)
[Magisk] PriMieon:
Thanks. The 17.1.22 update had been out for a week or so but it just stopped yesterday. And I searched the forum and found no one who stated that 17.1.22 kills it at the moment. Thx
[Magisk] wabmorgan:
Anyone on the May 5th security update with Gpay working ?
[Magisk] zencooler:
It's definitely 17.x version issue. I've been playing many combinations of GPay and GMS and up to version 16.x all was warking fine (of course after all steps like hiding in Magisk etc.). When it is GMS 17.x it works for a short period of time then sets attestation state trigger and stops GPay. It could work for few days but finally will set this status as a failed.

So I agree that the only successfull way of keeping GPay working is to keep GMS on version 16.x. It's quite easy to do via freezing Google Play Store and block cache folder (details you can find in previous posts).

I am keeping ver. 16.0.86 and GPay works like a charm (every day I pay using many cards definied in GPay). On ver. 17.1.22 it was working maximum 2-4 days.
[Magisk] ChillerMarvin:
maybe it seems a bit obvious, but i was stupid enough to f*ck this up:

you need to delete the gms folder in the data folder in your data partition, not on your internal storage. use some app like root explorer to achieve this.

after that you need to hide all the google stuff in magisk hide, be sure to check "show system apps" in the upper right corner, then reboot and try to setup your cards, worked for me.

newest google play services, never disabled any updates or downgraded anything, magisk 19.1, pixel 2, sixrom pie
[Magisk] twotimer:
Got tired of jumping through the hoops and pulled the trigger, going back to unrooted Pixel 2 and re-locked bootloader. I wasn't using the whole root thingie for anything but ad blocking. It's a pity though that the adguard private dns causes soft reboots of the system ui on my pixel 2.

Off-topic:

One more thing I noticed – google devs still have a lot of work to do to make restoring from full backups stored on google drive work.

Native google device, same account, the same latest release of Android OS on both pre- and post-factory reset phone – and it still fails to restore my call log, wifi passwords for known networks, and a bunch of other stuff I had to re-install and tip in all the passwords in for 4 hours.

And there seems to be no option to manually force–restore specific items (like call log) from drive backup.
[Magisk] fmc000:
[OT] Have a look ath this as an alternate ad-block solution. [/OT]
[Magisk] warrencoakley:
Yes working fine
[Magisk] muzzas:
Not working for me. Pixel 2XL Q Beta3
[Magisk] doctorew:
Where can I find that beta?
[Magisk] coolzizi:
Anyone have tried relock bootloader in pixel 3? I'm wondering about this but worry that I'll brick my phone. Any sugestions? Greet

Wysłane z mojego Pixel 3 przy użyciu Tapatalka
[Magisk] jcmm11:
Unless you're running COMPLETELY stock - DON'T. Root, custom kernel, custom ROM, custom recovery - if you have any of these don't even think about locking the bootloader.
[Magisk] Ingan121:
If this issue is related to bootloader unlock status, can devices that don't need to unlock bootloader (e.g. Galaxy series before S10) bypass it?
[Magisk] IM0001:
Pretty much the only reason I am Rooted/Unlocked these days is due to Titanium Backup for restoring app data and content that Google still doesn't capture. Leaving the backup options up to the Dev of said app, even to Google themselves is still a cluster of crap. Sigh.
[Magisk] warrencoakley:
Check your GMS version. If it's on 17 that's the issue
[Magisk] muzzas:
My device is certified on the play store and my GMS version is 16.7.90
[Magisk] ckegg:
I'm on Pixel 2 XL with May 5th security updates, bootloader unlocked and rooted. The current and only workaround that works for me is to downgrade Google Play Services to 16.0.91:

Download Disable Service.apk

Download 16.0.91 Google Play Services

Open Play Store, and set Settings > Auto-update apps > Do not auto-update apps

Put phone in airplane mode preventing Google Play Services get updated back to the latest version

Security > Device admin apps > Disable "Google Pay" and "Find Device"

Disable and uninstall new version of Google Play Services from managing apps

Clear cache and data on Google Pay from managing apps (You may not need to do this)

Install 16.0.91 Google Play Services

Install Disable Service.apk and disable following to freeze Google Play Services being auto updated

System > Google Play Services > SystemUpdateService

System > Google Play Store > GmsCoreUpdateService

Magisk and Hide on

Google Pay

Google Play Services

Turn back on "Google Pay" and "Find Device" in Device admin apps

Turn off airplane mode

Finish up Google Pay (if your Google Pay turns off itself during setup, go check Google Play Services version it may get updated itself again, if so then start over on the guide)

At this point, if you open Play Store, your Google Play Service will get updated regardless. Do not open it until we have a new solution.

Most people can skip most of these steps and just downgrade Google Play Service and don't let it update itself

If you still have trouble with Google Pay, delete /data/data/com.google.android.gms , and reboot the phone before you do step #8
[Magisk] Superschmiddi:
[MENTION=3038600]ckegg[/MENTION]

I can open my Play Store, update my apps and Im still on 16.0.91.

Same device, same workaround
[Magisk] warrencoakley:
Yes me too. Once a week I enable play store, update the apps and then disable it again. GPay still working.
[Magisk] fightinfilipino:
has GMS Toolbox stopped working for anyone else?

when I press "Check" in the app now, nothing appears to happen. I've tried reinstalling the apk, too.
[Magisk] zencooler:
For me it works fine. I use it very often (generally every day) to check my GPay instead of be surprised in the shop ;)
[Magisk] dardack:
What do you mean by this? How do you enable disable?
[Magisk] warrencoakley:
Go into apps in settings, find Google play store and disable it.
[Magisk] dardack:
I feel stupid now. Thanks.
[Magisk] Paz9:
I have an idea on how to get this working if someone is willing to try?

I believe the GMS folder is still the culprit

More specifically a file, that gets patches on 17. So it never works

I'd need someone to go back to an older version prior 16091

Then update to 16091 and attempt to add a card in gpay (it needs to fail)

Then delete a folder in the gms directory (not the gms folder itself, but navigate in there and delete a singular folder) then restart, add a card and see if it works

If it doesn't, repeat until it does each time trying another folder

When it does work, start at the beginning (downgrade then upgrade until gpay fails adding a card) and instead of deleting the folder in the gms directory delete each file until we find the corresponding file, then maybe if we copy that file to sdcard, update GPS then place the file back with only read access it might work

I'd try it but I'm currently travelling and don't have the time
[Magisk] .me:
Perfectly fantastic!!! Thanks man!
[Magisk] xxxmoscoxxx:
Thanks, tried this workaround in my Mi9 running Xiaomi.EU

It worked i was able to add my cards again, but it updated Play Services in minutes after finished the procedure and after the button to uninstall the play services disappeared..

Probably i needed to limit the access to backgroung data etc etc... but i find this really annoying. So i reflashed the stock rom and i relocked the bootloader. I'll wait for a definitive solution (if it will be in future).

However thanks for useful post!!
[Magisk] PriMieon:
Currently on 17.1.22

GPay currently not working

Deleted Google pay cache and storage.

Did not delete com.google.android.gms

Installed 16.0.89

Then installed 16.0.91

Tried to add a card but it didn't fail. What to do now? How do I get it to fail?

Would love to help but I'm kinda stuck
[Magisk] Paz9:
go to a version below 16.0.91

then try to update to 16091 it should fail.