yashsingh1/xdaforums huggingface dataset:
[Magisk] phly95:
I did, and it did not help. Adding Discover to Magisk hide did add a Google Pay option to the app, but even so, adding it via Google Pay or the Discover app resulted in an error. I also had the errors before I even installed the Discover app.
[Magisk] SauravD:
Facing issues in my Gpay.

I unlocked my Redmi Note 5(Vince) and installed PaintByAndroid Xiaomi.EU Custom Rom with MiUi 12

.Installed Magisk 23 and followed this link

https://xdaforums.com/t/certified-play-store-and-pass-safetynet.3816925/

To set the certificate and pass the SafetyNet tests.

My phone has passed SAfetyNet tests and I have enabled MagiskHide for GooglePlay Service and Gpay.

I am able to launch and log into my Gpay , however when I try to do transactions, it shows to activate account and I get the following message, when I click Activate

Couldn't Register

Make sure +91 XXXXXXX is linked to your bank account and its SIM is in your device. YOu could also try to turn airplane mode on and off,

or remove and reinsert your SIM.

When I click on Retry , nothing happens.

I can see my Bank Accounts as greyed out and it asks to activate.

Tried resolving my issue using the below links

There's a working solution here:

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

And a Magisk Module for it here:

https://xdaforums.com/ap...7-1-22-pie-t3929950/post79643248#post79643248.

Anyone facing same issue? I called gPay support but to no avail. Is there any workaround?
[Magisk] 73sydney:
Im the one to blame for the module, which is just a packaged easy to install version of the original method, so i can answer from that side of things, and give some other general tips

First up, as noted in the module thread, for some months now, many folks, including me, no longer need to use the module. thats right, i dont even use my own module these days...google changed something on their end which meant it was no longer necessary to use or perform the changes in the original thread. We dont know how long this will last

Maybe you missed the opening statement in my thread, in bold:

General Notice:

14/03/2021

You may not need to use this module - read below!

Your issue looks like its related to your bank and its app, detecting root or custom ROM

First simple thing to try:

Try enabling MagiskHide for your banks app....thats where it looks the issue stems from

2nd simple thing to try (you van do this in conjunction with above):

In Magisk Manager > Settings > Hide The Magisk App

You can stick with the default name "Manager" from memory, or call it anything you like, other than Magisk Manager

Reboot and test again

Second thing to try:

Do you use a custom recovery? TWRP? Some bank apps will test for a TWRP folder to determine if youre running a custom ROM. If you have one, as logn as youre not storing a backup in it, you can safely delete the TWRP folder (of course, and disclaimer: if you are storing a backup in there, copy the TWRP folder (including backup) off device before removing the TWRP folder for testing))

Other possible issues: Xposed...i personally dont get why people want to make everything even harder by running that crap, but thats me....
[Magisk] SauravD:
No Worries there.

I have enabled the magiskhide for the banking apps, and its working fine.

Also you mean to say the steps followed to pass the SafetyNet test api, should I undo that? in that case will the device certfication and other checks will pass? Sorry if this is misleading, but I want to be sure.

LAstly I will definitely remove the TWRP folder and try again.
[Magisk] Lord Sithek:
Maybe because it allows to make many other things easier... but that's just me 🙃

(BTW, Im using Google Pay successfully with LSPosed :))
[Magisk] 73sydney:
No, if youre passing Safety net, leave it the way it is. Sorry if that confused you.
[Magisk] 73sydney:
We dont need another thread of conspiracy theories about Johns new employment

Poor bastard is already copping way too much flack and pressure

The man is entitled to earn a living anyway he likes, just like everyone here, and people are too quick to forget he has devoted years of his personal time to XDA and Magisk

Be thankful
[Magisk] plepew:
Jesus...buddy...what conspiracy am I spreading ???

I was just making a joke of all this in regards to the article saying "he's on the other side"...that's all!

So telling me to be thankful is a bit out of place...I'm not the one spreading **** about him out there!! As John tweeted, he'll take care of it privately and yeah, whoever did what they did is pretty disgusting.

I've been a supporter of Magisk & John's work before that.

So if you're a taking a shot at me, it's not appreciated.
[Magisk] 73sydney:
Pointing out there was an existing thread where it was far more on topic than here. We dont need forks of conspiracy theories,. please and thank you, it has the ability to confuse and misinform, that is all.
[Magisk] tekhtime:
Anyone from the UK know if Starling/Monzo or any other banking apps are working?
[Magisk] tyler19820201:
I am from UK but not using these apps. At the moment Santander and GooglePay does not work for me. Natwest Barclays Halifax & Lloyds are working. I have xprivacy lua and get applications thicked on there.
[Magisk] 73sydney:
Things have changed a lot for me recently, i could no longer get my bank apps and Google/Samsung Pay to pass

I tried all the Lsposed/EdXsposed stuff....nope

Im now using Riru + Riru-Momohider with the 4 config switches (blank files under config folder as per the page linked)

Which can be manually added (after rebooting to install Riru-Momohider), thusly:

Install Magisk (im using vvb2060s Alpha from here (app-release.apk)), enable Magiskhide.....reboot

Install Riru (core module)....reboot

Install Riru-Momohider....reboot

MagiskHide bank apps (i dont have Google Pay hidden my end, ymmv)

Hide (Rename) Magisk App

Open root terminal and execute the following:

touch /data/adb/modules/riru_momohider/config/isolated

touch /data/adb/modules/riru_momohider/config/setns

touch /data/adb/modules/riru_momohider/config/app_zygote_magic

touch /data/adb/modules/riru_momohider/config/initrc

Then reboot and try bank apps (after clearing their data if necessary)

You can also always test with Magisk Detector

Note: as i always says, for people who think they can be clever and skip the reboots, youre only going to have a world of pain, and get nowhere. As usual also make sure you have no TWRP or custom recovery folders present on your device.

Im looking at modifying the Riru-Momohider module to add these config options at install time...

Both my bank apps and Samsung Pay and Google Pay work. But it very much depends on the ROM and the banking apps and what theyre searching for. Even some ROMs will betray you with their build.props. I can only get this working on 2 ROMs for my Pixel 2 XL....
[Magisk] tyler19820201:
I have got a very similar problem.

Since few days ago there is some problem with Google pay. I can add the card but NFC payment can not set it up!

I was trying to reinstall Goggle Pay and readding the card.

Also was realised that SafetyNet Pass was failed. However fixed that issue ( at least at the moment) with installing safetynet-fix-v1.1.1 magisk module.

I am using latest Magisk Canary + EdXposed + XprivacyLua.

On Xprivacylua only Santander UK app has been thicked at get applications nothing to do with Google Pay.

I am confused now shall i set manually Google Pay in xprivacylua and/or EdXposed hide (black) also??

I think if i set magisk hide for EdxPosed then become unneccesary to do that... However i was trying not to hide Google services on edxposed hide (black) and then safetynet was failed again...

So now my bank card succesfully added to GP and does not pop up "your device might be rooted' staff also SafetyNet is passed but why NFC can not setup? It says my phone does not meet with contactless requirements... But NFC is ON GP is set as primary payment method also screen lock PIN is on.

Now i am having four google related item marked on Xposed Hide ( black):

Google Pay

Google Play Services for AR

Google Play services

Google Services Framework
[Magisk] 73sydney:
Just for reference, not even Google Pay is hidden in MagiskHide on my end. I havent had to hide that in months (even long after i stopped using my own GPay magisk module).

I also updated my post to add which Magisk im using (vvb20260's Alpha), and MagiskHiding Bank apps, because that wasnt clear...

You prolly know more about Lsposed/EdXposed than me, i only used it for the first time (since i sued the original Xposed eons ago) last week. A lot of faffing about, for no real help with my situation.

One query: Does your Google Play Store says certified?

Try: Airplane mode on, wipe data for Google Play Store & Google Play services, Reboot, Airplane mode off, wait 5 minutes and check Google Play Store status again
[Magisk] tyler19820201:
What do you mean exactly google play certified? i have not see this option to check.

The funny thing is that i was trying to pay in tesco with the phone and the payment went through....However my device still has not got NFC set up...
[Magisk] 73sydney:
Google Play -> Settings -> About

Last line
[Magisk] tyler19820201:
No it is not certified... Probably because on xposed has been hide...No clue.
[Magisk] 73sydney:
Airplane mode on

Wipe data for Google Play Store & Google Play Services,

Reboot

Airplane mode off

Wait 5 minutes

Check Google Play Store status again
[Magisk] tyler19820201:
Ok. Thanks. Will try it.

By the way i did 3-4 payments now in row on different stores and all went well with no issue. It is just frustrating the pop up message my device is not meeting with NFC payment requirements. But apart of that is working fine.
[Magisk] tyler19820201:
I was busy yesterday and did not do this Airplane mode & wipe data & reboot stuff but i just checked today and my playstore is certified now...

I have google related services marked on three places: 1 Magisk Hide 2. EdXposed and 3.XprivacyLua.

Google Pay also works however my device is still not suitable for NFC payment...:cool:;)
[Magisk] PuppyWuppy:
I'm rooted using Magisk and I have kdrag0n's SafetyNet fix.

Every few weeks, my GPay app would tell me that my device had stopped meeting the requirements for in-store payments, and when I checked safetynet in the Magisk Manager app, it would somehow be failing with hardware attestation. However, rebooting usually caused SafetyNet to go back to basic attestation and passing. However, I'd have to clear the storage for Google Play Services, uninstall GPay, and reboot, and then re-install GPay, and I'd be able to set up my NFC payments again.

However, when this happened again recently a couple of days ago, and I did the whole clear data/uninstall/reboot/reinstall flow, this time, when I try to re-enable NFC payments in GPay, it gets to the point where I enter the CVV, and then accept the issuer's terms, and then it says "Contacting your bank" with a spinner for a second or two, and then I get an error message saying "Your card couldn't be added. Please contact your card issuer for more info. You can also try adding a different card.". This happens for all 4 of my different cards from different issuers, so it seems like it's an issue on the google pay side and not the bank's side. I contacted the google pay chat support, and they told me to contact my bank also.

Has anyone seen this issue before or have any idea how to fix it?

[Update]

I rebooted yet once again, and seem to have been able to add a couple of my cards now. I think I tried enough with my primary card though that I got locked out somehow, so will wait for that to resolve itself and try again.
[Magisk] tyler19820201:
There is nothing to do with banks or google pay support. I have just realized if i completly remove edxposed and xprivacylua and magisk manager .apks and delete all the related folders on sdcard has fixed this issue for me.
[Magisk] dr4go:
Which folders did you delete on your sdcard?
[Magisk] tyler19820201:
twrp folder
[Magisk] richardmace:
My experience of issues. I'm on a OnePlus 6, Oxygen 10.3.11. Rooted, TWRP, Magisk 23.0 with Universal Safetynet fix v 1.1.1. Google Pay was working fine until recently. My cards reverted to 'unathorised' a couple of days ago. I suspect this was due to the update of Google Pay to Version 2.130.370156226. If I uninstall Google Pay and regress to Version 2.97.265766933 all my cards are restored to 'authorised'. I've deleted my TWRP directory. Cannot get Version 2.130.370156226 to work. Open to suggestions. Using Version 2.97.265766933 for now.
[Magisk] tyler19820201:
Okay. So update to latest canary. install riru and riru xposed modules. install enhanced storage isolation module. install riru unshare module. install xprivacylua. on xprivacy thick get applications only for gpay.

If does not work, alternativelly uninstall magisk manager apk. Not magisk itself!! Delete any magisk or twrp related folders or rename them.
[Magisk] richardmace:
Thanks for that but all the stuff in your first paragraph means nothing to me. As for second paragraph, I don't have Magisk manager APK installed. I have deleted all Magisk and TWRP related stuff previously.
[Magisk] 73sydney:
Im still amazed that people who use xposed (of any type) get surprised when they have issues...

Heres what i currently use:

Magisk (Alpha or Canary will do) with MagiskHide on

Riru

Riru-Momohider (my own mod) here: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85187739 - automatic version of the recommended config here

I dont not have, and havent had for 6 months or more, MagiskHide even enabled for Google Pay...

The above also allows me to use my personal banking apps and Samsung Pay, ymmv with your banking apps, and as always, some ROMs will give up root to detectors, so it cant all be hung on Magisk..

If you must use Xposed, use Lsposed, been mentioned about a dozen times in the Magisk General thread in the last week....
[Magisk] 73sydney:
Im still amazed that people who use xposed (of any type) get surprised when they have issues...

Heres what i currently use:

* Magisk (Alpha or Canary will do) with MagiskHide on

* Riru

* Riru-Momohider (my own mod) here: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85187739 - automatic version of the recommended config here

* Magisk App renamed

I dont not have, and havent had for 6 months or more, MagiskHide even enabled for Google Pay...

The above also allows me to use my personal banking apps and Samsung Pay, ymmv with your banking apps, and as always, some ROMs will give up root to detectors, so it cant all be hung on Magisk..

If you must use Xposed, use Lsposed, been mentioned about a dozen times in the Magisk General thread in the last week....
[Magisk] richardmace:
Magisk 'Alpha or Canary' means nothing to me, I have Magisk 23.0 which I installed as a *.zip file via TWRP, the rest of the stuff you posted is even more meaningless to me. I'm not being funny or obstructive but my knowledge in this area is very lacking. Also, there is much conflicting information.
[Magisk] tyler19820201:
Well if u have lack of knowledge of magisk it is not the best place to learn. First of all update your magisk to alpha or canary. remove magisk from your phone fully!! install magiskcanary.apk. Then flash the magisk .zip from twrp. reboot and voila! you will get canary update channel. Then follow 73sydney instructions.
[Magisk] richardmace:
What's the difference between Alpha/Canary and the 'offficial' V23 Magisk? Are they 'forks'?
[Magisk] tyler19820201:
canary is like "beta" or "nightly" or "dev" version
[Magisk] richardmace:
Ok, I'll look into it, thanks.
[Magisk] richardmace:
Interestingly, I've run 'diff' over your canary.apk and the one here https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk they are different. Comments please? Just a bit worried about integrity of what I'm installing.
[Magisk] richardmace:
Ok, I've bi

Ok, I've installed Canary, Riru and Riru-Momohider. MagiskHide is on. Magisk app renamed. Anything else I should do? Thanks again.
[Magisk] richardmace:
Sorry about my sh*t formatting, I'm new to this!
[Magisk] richardmace:
Failed.
[Magisk] 73sydney:
Have you checked youre passing SafetyNet? This is a biggie

Main window of Magisk app, Check SafetyNet

If you dont pass that, post back

Have you Magiskhidden any banking apps

Second icon in Magisk app taskbar (shield) > MagiskHide

Tick any apps relating to banking, you can try ticking Google Pay, though i havent had to in 6 months, your mileage may vary

It may be necessary, if making the above changes, to clear the data for Google Pay, but just be aware this can, and probably will, remove ALL cards, including any loyalty ones that you have already entered. As you get more comfortable with this you will figure out which steps you need to take in order for it to work, till then its trial and error.

Case in point (though rare):

In *rare* circumstances, ive had one account that did this, you *may* need to add the card via the banks app before adding to Google Pay. As mentioned i had one bank, the previous one, where you had to add the card to the apps digital wallet first, upon completion it would then ask if you wanted to add to Google Pay....but as mentioned ive only seen that once..

Also if i failed to do it in that order, i could NOT add the card to Samsung Pay on the same device.
[Magisk] richardmace:
Safetynet passed. All Banking and Google apps hidden by MagiskHide. I've deleted Google pay cache. As stated in earlier post, if I uninstall the latest version of Google Pay and revert to an earlier version, all is well, it's only when the latest version is installed I have problems.
[Magisk] Fishawy:
OP8Pro, stock, rooted, SafetyNet passes, MagiskHide for all Google apps, device is certified on Google Play, card is added on my bank app, followed your detailed guide in the famous post below (with modules and all), and I even downgraded GPay and Play Services.

Card is only added on GPay, but now I'm getting the [OR-TAPSH-08] error when I try to setup the contactless pay.

Any more suggestions?

https://xdaforums.com/t/working-mag...s-17-1-22-on-pie.3929950/page-9#post-79643248
[Magisk] richardmace:
Update, I have removed Magisk (via the app) and confirmed no files remaining. Removed all twrp files. Rebooted and then installed the latest Google Pay version. Message "Google Pay cannot be used.... Failed safety standards....." Looks like detecting bootloader unlocked?
[Magisk] richardmace:
Phone unrooted, no Magisk or twrp files. See picture.
[Magisk] 73sydney:
Yeah, i havent used my own module in 6+ months...theres a big section up the top about how not it may not be necessary and its not my first choice in recommendations as its been unnecessary for many people for 6+ months...to the point where im thinking of removing the link from my sig

Ive had the [OR-TAPSH-08] issue once, and just once ever, a few weeks ago, and seen it a few times in the thread, the solution for myself and others was to contact Google Pay, in my experience and others, it was a back end issue that took up to 48 hours for Google Pay to clear. It seems to stem from trying to add a card too many times and it failing, or in my case, my bank screwing up my account leading to them spamming my Google Pay account with spurious data. I have since left that bank :) That bank required me to add the card to its digital wallet in its app first, before adding it to GooglePay at the end. Only bank ive used where that was the method...

Google Pay support link - chat at bottom

Fix problems with tap to pay transactions - Google Wallet Help

If you can’t complete a contactless payment, use these steps to help you solve the problem. Step 1: Update your app & Play Services Make sure that your Google Wallet app is up to date. Learn

support.google.com

Other people have claimed to have resolved the [OR-TAPSH-08] error without Google intervention, via updating google Pay and other claimed methods...

Note: MagiskHiding ALL google apps in unnecessary...i dont even have Pay MagiskHidden
[Magisk] 73sydney:
Which device/ROM
[Magisk] richardmace:
OnePlus 6 with stock ROM. With TWRP (Magisk uninstalled to try to fix Gpay problem).
[Magisk] 73sydney:
I seem to remember people with OnePlus devices having issues going back 2 years...i'll see if theres anything to be gleaned from a search, though it sounds like it might be unlocked bootloader

Wouldnt you know it, it goes all the way back to BostonDans Oneplus drama that started the thread , and the method thats included in the magisk module i have

Essentially the OP, 1st post ever says he did the database fix BEFORE ever opening Google Pay for the first time...my module does wipe the data of google Pay as an install step (optionally) but even im not sure if that resets the database file fully..i should look at that one of these days

Also reading through the thread it seems OnePlus is especially prone it seems to Google Pay version updates screwing the functionality up...doesnt doesnt like fun times, i couldnt live like that :)

What did you OnePlussers do to Google?, steal their lunch money :)
[Magisk] Stillhard:
I bet they bullied them while in the first grade
[Magisk] richardmace:
All was fine for two weeks after I rooted. I paid successfully using my 'default' G.Pay (credit) card. Then, coincidentally, some days later, I just went into the G.Pay app. The account had a line through the 'proximity' symbol thingy on my default card. And 'card not authorised'. I have two other cards (debit) that seem to be ok, although I haven't tried to use them. Incidentally, the card is fine on my other OnePlus 6 (unrooted) phone.
[Magisk] kangurosmz:
I had recently the same problem. I've followed 73sydney instructions, but now success. SafetyNet passed in Basic mode,but Gpay still showed error of rooted phone. Today I found the solution on another forum. Stop Gpay process. Than go to /data/data folder and rename com.google.android.gms to com.google.android.gms.backup Restart your phone and open Gpay. If app shows error with Google account, remove the Gpay and reinstall. It should work after this procedure :)
[Magisk] 73sydney:
Thats no different than the suggestions already given to clear data for Google Play Services, which is also what my module does during its setup...
[Magisk] kangurosmz:
Nope. Clear data didn't help in my case. Just wanted to share with solution that helped me. I was strangling with Gpay few days. Now it's working fine.
[Magisk] Fishawy:
You were right. Google support resolved it from their end.

Thank you.
[Magisk] richardmace:
I'll try that. Thanks.
[Magisk] richardmace:
I regressed to earlier G.Pay (Version 2.97.265766933), left it a few days and today, card accepted without issue! All well. Still rooted, still twrp.
[Magisk] 73sydney:
Perhaps a good reminder, this isnt an exact science :)
[Magisk] ivivaitylin:
Woke up this morning to a notification from GPay saying that it was detecting root. Thing is, I haven't done anything to my phone in at least a few weeks, so I have no idea what caused the sudden fail. All other apps which normally throw up safetynet errors such as banking apps, alongside a couple of safetynet checking apps are all still passing me.

I'm running GPay 2.130.370156226, so I might try rolling back to .97 per the above comment, though it's weird that it suddenly happened out of the blue. The app didn't update recently on my phone. Happy to provide more details/will accept more advice if people have it!
[Magisk] richardmace:
That's exactly what happened to me and the start of my problems. No problems since I rolled back
[Magisk] ivivaitylin:
Thanks, why did you go to .97 specifically? Just looking on apkpure and the oldest version they have there is .105 which is from last February so wondering if there was something specific about that version that was important.
[Magisk] richardmace:
Hi, if you press uninstall in apps, it just gives you the option to uninstall updates. That takes you back to the .97 version.