yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Well it can... 😬

Its use should definitely be limited in traditional Magisk as hiding more than a few apps / processes makes the system unstable due to restrictions on the hide daemon's passive reaction speed (to app processes). Also Webview and more are broken by indiscriminate hiding of Chrome and other Google apps / processes... Nb

- www.twitter.com/topjohnwu/status/1039528958289760256

Also, John did much debugging w/ early MagiakHide just to make it useable (see 'More on timing issues here also' link and John's general rule from here:

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

Nb. The hiding elements retained by denyist may well have changed, ie hijacking app_process (Zygote) rather than simply monitoring these passively may now be used / possible with Zygisk and be faster / not face this restriction any longer. However I haven't checked code for this nor am I aware of comments by John about changes to the mechanism used here. Someone may know more...

Just to qualify this, those using stock or custom ROMs that spoof certified (use a certified fingerprint matched to security patch date) won't need MHPC, but many custom ROM users, eg all official LineageOS (except where fingerprint / patch dates match before any update that bumps up security level) users, as well as those with uncertified stock ROMs (China region etc) will need to spoof certified by using a working fingerprint. 👀 PW
[Magisk] pndwal:
Yup, @kdrag0n's Zygisk solutions remove these from denylist as USNF hides these itself so as to better target Play Services only... explanation in USNF GitHub...

Your failing S/N has a different explanation...

Nb. to pass with MagiskHide we need SafetyNet process, com.google.android.gms.unstable in hidelist where Magisk is in /sbin. For Android 11+ etc (assuming Magisk is not in /sbin), main process, com.google.android.gms needs adding also. However, MagiskHide adds these automatically when toggling ON...

Nb. 2 Only these processes need to be / should be hidden to pass Safety net... 🙃 PW
[Magisk] steve.rand:
Has anyone lost the Google Pay cards from the power menu? I updated Magisk when prompted (I don't know why, everything worked fine) and then of course my cards were all not able to be used for contactless payment.

I've enabled zygote, hidden gms and banking etc, added safetynet and props hide, cleared cache and data from play, pay, services, ran the latest gpay and added my cards successfully.

Everything appears good, Play Store says certified etc but for the life of me the option to enable cards on the power menu is gone and i'm not sure if i've done something whacky. Any ideas or suggestions greatly welcome!

Pixel 2 XL on last build/security patch running Magisk version whatever came out yesterday.

Thanks!
[Magisk] steve.rand:
I could delete the post but in case someone else finds it useful... My cards are back on the power menu after leaving it for a few hours.

Clearing the Pay data didn't do anything at the time but now it looks like all my cards have gone bar the primary one I actually removed and added during the gpay sqlite module installation. I've added the second card and afterpay with no issues.

Not sure what the winning combo is, after spending about 2 hours removing and rebooting things multiple times. Thanks @73sydney for the module maintenance!
[Magisk] DocMAX:
While we need to delete Google Services Data sometimes, to make Pay work, is there a way to backup all credit cards and restore them? (titanium backup?)
[Magisk] nightmare1942:
Hi guys and gals,

after reading many infos here I got everything to work for me.

I needed these settings for the following apps:

Google Pay (GPay)

Pokemon Go

comdirect photoTAN app

What I did was the following:

Updated to magisk 24.1

Needed a deinstall and reinstall

modules already installed were Busybox, MagiskHide Props Config, Smali Patcher

Installed Universal SafetyNet Fix for Zygisk by kdrag0n

Enabled Zygisk

Rebooted

Enforced DenyList

Added the three apps above to the DenyList (just left everything checked by default, didn't enable anything else)

Deleted all data (not only cache) from the apps above, Google Play Services and Google Play Store

Reconfigured all three apps and it seems to work fine (haven't yet testet GPay in RL, but looks good)

I hope this will help to understand what needs to be done at least.

I have a Galaxy S9+ with CustomROM on Android 12.
[Magisk] 73sydney:
No,

Plus that would be insanely insecure...
[Magisk] jumo0n:
I did the same and I can confirm that everything works just fine. Difference is that I alao used props to spoof the fingerprint of my phone.
[Magisk] borisSweden:
Is it still Gapps depending to pass Safety Net? Is there still no Gapps faker? Whatabout using old Android Pay apk, does it have a exploit?
[Magisk] 73sydney:
In order of questions the answers are:

Yes (core services are needed to pass SafetyNet), No (and never will be), and No
[Magisk] renanrdrigues:
Nice !!! worked for me on lineage 18.1 - S7 Edge
[Magisk] Gogikz:
Hi boys and girls,

I can't set Up a google pay.Safety chek pass as well but stil can't set up my card.Magisk v.24.3 on redmi note 9 pro.The problem came after software update
[Magisk] Gogikz:
Can somebody help to solv this problem
[Magisk] 73sydney:
1) Theres a section of my modules post here: https://xdaforums.com/t/working-mag...s-of-gms-17-1-22-on-pie.3929950/post-79643248

titled "Clear Play Store & Play Store Services Data & Check Play Store Certification"

which suggests:

Clear Play Store & Play Store Services Data & Check Play Store Certification

Toggle Airplane Mode on

Clear data and cache of:

Google Play

Google Play Services

Google Pay (note: may/will remove any cards previously entered)

Usually this will be achieved by (exact steps and terminology may change per device or ROM):

Opening Settings

Going to Apps, choosing Show All Apps

Enabling Show System Apps via a menu option

Locating the app, tapping it and then finding Storage/Cache

Tapping Clear Data

Reboot

Toggle Airplane Mode off

Open Google Play Store, wait 5 minutes, go to Settings and check Certification at bottom, it may take some time for "Certified" to appear, but as long as its not "Not Certified", and just showing version info, you are good to go

an awful lot, in fact most, GPay issues are resolved merely by doing what this section says...

2) Disable DNSCrypt-Proxy temporarily (and reboot) - i dunno what if any blocklist youre using, but theres a chance that a blocklist entry may be interfering.

Beyond this, i have no idea, you mention a software update...so you may wish to check with other sin your devices threads to see if anyone else is having issues
[Magisk] Gogikz:
Thanks I had try this but I miss one step.After I read your post and did everyting step by stem my problem is solved.Thanks a lot
[Magisk] varunpilankar:
I'm using rooted android 10 with Safetynet Pass & Play Store -Certified, but I'm still not able to activate tap to pay on Paytm app.

It's gives me a error - "This functionality is not available due to security concerns with your device."

How can I fix it?
[Magisk] 73sydney:
Things to try?

1) Make sure you do not have a visible TWRP folder on internal memory - if you do and have a backup in there, rename the folder until you need it, or alternately move it off device

2) Make sure you are using the most up to date Magisk your device supports, and set MagiskHide or Zygisk (dependent on Magisk version) and relevant apps set to hide (do not hide all apps like an insane person). Consider installing Shamiko if using current Magisk 24.x with Zygisk

All details here: https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/

3) Make sure you do not have any of the known apps/modules that are known to cause issues, this include "tweak" apps/scripts like FDE.AI or (badly configured) EdXposed (on older Magisk) - which are noted here: https://xdaforums.com/t/working-mag...s-of-gms-17-1-22-on-pie.3929950/post-79643248

4) If you have any magisk modules installed, try toggling them off and retrying (you;d be surprised what will give up root, something as benign as a font module will betray you)

5) And despite having a SafetyNet pass and certification in Google Play, and perhaps after 4) above, i would still give the standard troubleshooting steps of clearing data as in the three posts above this one ↑ a go....

6) Consider running RootBeer to see what may be triggering root detection, if at all

As always, i prolly try these things in this order for a possible "quick fix":

1, 5 and 6 - 5 has solved an awful lot of issues by itself...

And sometimes it will just resolve itself after a few days...GPay is sometimes a weird beast....
[Magisk] borisSweden:
Does this count for the new Google Pay Flutter edition? Maybe I wasn't very specific. I pass Safety Net using LOS+Magisk24.3+USNF+MagiskHidepProps+Fingerprints+DenyList but does Gpay demand Gapps to be present?
[Magisk] QuietMountains:
The GPay app technically can launch but when asked to set up contactless Google Play Service launches then crashes. I've cleared Play services data several times now

Magisk is version 24.3. I have Zygisk enabled with the deny list enabled. The GPay SQlite fix module, MagiskHide Props Config, and Universal SafetyNet Fix. Google Play Store says my device is verified as well as YASNAC

Tried out that working solution and that didn't change anything. What am I doing wrong?
[Magisk] borisSweden:
Is it possible to emulate Android Pie variables just to make Google Pay and Android Pay to work without Gapps? Let say Android 11 with all the Magisk fixes but the Pay app is in a container for Android 9 where the fixes work without Gapps?
[Magisk] 73sydney:
Very short answer: No
[Magisk] 73sydney:
Cant say ive ever had GPay just crash when trying to set up a card, it will usually give an error if anything

Do you only Deny Google Pay, NOT every Google app/service as some people mistakenly do thinking it will "solve everything"...it can break stuff

Have you tried the most common fix:

Clear Play Store & Play Store Services Data & Check Play Store Certification

Toggle Airplane Mode on

Clear data and cache of:

Google Play

Google Play Services

Google Pay (note: may/will remove any cards previously entered)

Usually this will be achieved by (exact steps and terminology may change per device or ROM):

Opening Settings

Going to Apps, choosing Show All Apps

Enabling Show System Apps via a menu option

Locating the app, tapping it and then finding Storage/Cache

Tapping Clear Data

Reboot

Toggle Airplane Mode off

Open Google Play Store, wait 5 minutes, go to Settings and check Certification at bottom, it may take some time for "Certified" to appear, but as long as its not "Not Certified", and just showing version info, you are good to go

You might also consider trying Shamiko, link here with the Deny List NOT enforced (Shamiko requires this) and only enable Deny List for Google Pay, as far as Pay stuff goes
[Magisk] borisSweden:
Even if I install v1.0 for both apps, it doesn't work. Is it the OS fault for this? Or should we just emulate IDK, Garmin and Fitbit pay in the phone?
[Magisk] fkofilee:
Anybody finding that there GPay isnt working any more? Pixel 6 Pro here...

I am unable to keep Google Play Services added to the Denylist. But Google Pay and Google Store do stay.
[Magisk] 73sydney:
Play Services is by design not able to be added if using KDragons Universal SafetyNet Module i think from memory (not sure if Magisk does this now by default either), this is by design

Modules i use:

Universal SafetyNet

Shamiko (turn off Enforce Deny List when using this)

Google Pay is the only Google app in my Deny List - (i dont even have Play Store on the Deny List)

Google Pay works fine, you have other issues.

Why do you say it doesnt work, what happens? error messages?

Do you pass SafetyNet? ...dont forget to hide the magisk app. If you do, then try the steps in my last post, 3 posts above here....aka the *almost* universal fix for GPay issues.....

All things new Magisk and passing SafetyNet, including downloads of modules mentioned are here:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/
[Magisk] fkofilee:
@73sydney - Thanks for this - Managed to get it sorted, but I may need to default my phone again with the May firmware release.

I have a few bugs which are linked to the backup the device is pulling from Google1. Items like my lockscreen not always appearing correctly etc

GPay is another one of those, but thanks for the suggestion anyway :)
[Magisk] 73sydney:
Well thats a new one, ive never even heard of that happening ...(Ive never used google backup and restore)

Hope you get it sorted out
[Magisk] Fishawy:
FYI, I had a problem - all of a sudden yesterday - with Google Pay on my OnePlus 9 Pro. Tried everything I could, even installing older versions of the apk, no luck for 3 hours. Google Pay kept showing something like "Checking for updates, this may take a few minutes".

Finally, turns out it's the latest version of Google Play Services (I was naive enough to opt in the beta testing program).

If you come across something like that, what worked for me was uninstalling Google Play Services updates, opting out of beta program, then re-applying the usual Google Pay process, and I was good to go.
[Magisk] 73sydney:
didnt even know there WAS a beta program for core google services...i wouldnt have been signing up for that :)

thanks for the heads up and sharing the info for the benefit of others!

fwiw its been a long while since a specific version of Google Pay itself caused any dramas...
[Magisk] rodken:
I too, was naive enough to opt in the beta testing program - and have since dropped it like it was hot.
[Magisk] Fishawy:
The last 2 versions of Google Pay gave us prolonged hard times (months) in trying to add and auto-top-up the Myki public transport card in Melbourne, until they finally resolved it. Of course that's not a global scale problem, but yeah the APKs have been problematic for some.
[Magisk] 73sydney:
no such problem with Opal in Sydney :)
[Magisk] Fishawy:
Lived there for years and can confirm the statement, however you can't add Opal to GPay unlike Myki. :D

Either way, minor things really when any form of tap-to-pay works fine.
[Magisk] pndwal:
Just tapped on Opal terminal w/ GPay this morning! - don't need to (probably can't as you say) add Opal to GPay but.

I do have the card I associated with GPay added in Opal Travel app, so see trips both in 'Opal activity' and 'Contactless payment activity'... PW
[Magisk] Fishawy:
Yes, that's exactly what I used to do in Sydney. Having Myki on Google Pay is probably the alternative for not being able to tap-and-pay in Melbourne (or I could be wrong).

Glad we have an electronic option regardless.
[Magisk] 73sydney:
Just what we need, you cashed up and moving about Sydney :p

Ive never been able to even top up from within the app (i use firefox and the webpage:) )...i just assumed it had some way to detect root i wasnt aware of

If i hit top up it just cycles right back to the main screen....

Also cant add to billing information

So guessing its a root issue, i have it in deny list and HMA as well...
[Magisk] Fishawy:
You can do it - and auto top-up too - from the app. Just click the gear icon on the card, then configure it. I didn't have to manually top-up in years.

Or maybe a fresh start, remove and reinstall, then Opal in Deny List and that's it, worked like a charm.

Which reminds me, I have $20 stuck in there with no use since I moved 🤦🏻‍♂️😄
[Magisk] 73sydney:
I know how to do all that stuff, but doesnt work for me, cycles back to the menu you launch the option from :(

Only app on my phone i have issues with...
[Magisk] Fishawy:
Wish I was still there, we would've met for coffee and figured this out. I've learned that when it comes to stuff like this, 2 minds are always better than one.

Maybe @pndwal can do that coffee thing if both of you are up for it 😄
[Magisk] 73sydney:
Its not pebkac......

I catlogged it just now

and theres several weird errors....

my personal favourite is the line where it says zygote is sending signal 9 (which is SIGKILL = vewwy bad) to the process whenever the top up activity fires...

theres no obvious "root detected" status in the entire log.

and im not sure @pndwal wants to chance being seen with me...he knows why :)
[Magisk] Fishawy:
FYI, Google Wallet is soon to - maybe - replace Google Pay here in Australia (and possibly worldwide).

Google is relaunching Google Wallet alongside Google Pay, worldwide - Ausdroid

First, there was Google Wallet, then there was Android Pay, then there was Google Pay, and now there is Google Wallet? At first glance, this could look like Google’s merry-go-round of product naming, but we think it actually makes sense. Right off the bat, we’re not going to defend Google’s...

ausdroid.net
[Magisk] pndwal:
Pasting this from Magisk General Discussion. (Now fixed. Details following.):

I've actually had the same / similar issue for last 3 days; Contactless failed, removed and set up cards again etc. (Redmi Note 8T)

I haven't had any SafetyNet failure however...

Haven't been able to put my finger on the exact issue; above card image I have

- Wasn't sure if it meant card removed, but I called bank and was told cards were set up and fine for GPay on their end...

Since GPay itself is working / not complaining about root, it seems something is simply breaking Contactless function or NFC detection or hardware..

Does this match your experience?

Haven't had much time to dig further into issue... Suspect it's an issue with late Canary, but haven't tested... PW
[Magisk] pndwal:
Still not sure what caused this glitch (likely SafetyNet failure during Magisk setup).

Anyway, I found in Google Pay, Contactless setup

the Last item said 'Your phone does not meet the security requirements'.

Clearing Google Pay data wouldn't fix.

I am scared to clear data for the several components that appear in applist w/ 'security' as keyword... So next I cleared Google Play Services and Google Play Store data, but now Google Pay wouldn't even open, just this (unending):

Strangely, clearing Google Pay data again had no effect either...

Next, I simply uninstalled Google Pay completely, then reinstalled it from Play Store, and now get 'Your phone meets he security requirements' as shown above. Also:

so seems I'm good to go again! 😛

I don't know if version changed, but I assume I had latest version before as I auto-update... Some things are a mystery, but Uninstalling and reinstalling did the trick for me where clearing data wouldn't...

For others facing this, clearly you'll need to fix any SafetyNet issues first...

Hope this might alay some anguish. 😜 PW
[Magisk] 73sydney:
Thats slightly bonkers, wouldnt think it would be a database issue as a data clear would handle that, maybe some backend Google Pay thingy? The only issue i ever had with Google Pay was one of those rare error codes where you have to contact Google Pay and they reset it from their end..24-48 hour turnaround. In my case it was an issue where the originating bank (my bank) spammed their backend with false data when i was adding my card after a ROM flash

In any event, youve maintained your track record of solving issue sin this thread before i get to them. Your sacrifice is noted...

Ponkles
[Magisk] pndwal:
Just got back from Bunnings and Macca's (treat for my son, not me 😜...), and GPay's working fine... Went to check the purchases in Activity, and this:

... WHY??? 😳 PW

It's a human sign

When things go wrong...

But it's no sacrifice

No sacrifice

It's no sacrifice at all
[Magisk] 73sydney:
Im not sure if there isnt a delay before it shows up there?

Last time i went to Bunnings (Alexandria) my activity looked like this (big spender):

Went to Woolies this arvo, and the detail for that is even betterer, shows the location:

And yes, some of that $59 was Oreo Double Stuffed Cinnamon Bun bikkies,

closest thing to the old Nabisco Coffee Scroll bikkies from the late 80's/90's

- people have tried petitioning to have them reborn, but no...
[Magisk] pndwal:
Maybe... Still nout but... Wait; I'll restart... PW

Edit: Still no dice...

One should always spend more at bunnies than woollies... with ones Sammy...
[Magisk] 73sydney:
Bummer....Google Services are sometimes a mystery unto themselves

Not much you can do with a single room you dont own, hence Bunnings bills always low. Im not Scomo building chicken coops :)
[Magisk] pndwal:
Re:

Solved:

Did this, and can confirm it did the trick 👍 ... I think the reboot made the difference; without it

never completes (and after circumventing this by uninstalling / reinstalling previously, Activity wouldn't update despite payments working fine).

Many thanks! PW
[Magisk] pndwal:
Didn't do Aeroplane (are you American 😛) mode thing (seldom do), just the wipes and reboot suggested as stated...

Did work!; by 'did this', I mean I did exactly what rodken prescribed (no need nor mention of full uninstalling G Pay again!) 'and it did the trick' for me. 👍

By 'I think the reboot made the difference', I mean my original fix, while allowing Contactless payment to work, was flawed...

If I had also rebooted after wiping G Pay app data, I believe I would have both fixed Contactless Payment setup (security requirement) issue, 'Google Pay is currently updating' would have completed and I should have avoided broken Activity list...

In short, if you get

and see 'Your phone does not meet the security requirements' in Contactless setup, clearing Google Pay app data won't fix it.

Fix by

1) Clearing Google Play Services and Google Play Store data.*

(but now

won't complete...)

*Clearing Play Store data may (likely) not be required.

2) Clear Google Pay app data and reboot. (I'm not 100% sure full uninstall / reinstall of G Pay app, which I did, is not necessary here, but I now suspect it isn't).

Now 'Google Pay is currently updating' should complete and you should get

and, after payments

👍

...If you're still getting

for Oreo Double Stuffed Cinnamon Bun bikkies in some vain attempt to scroll back to the 80's & 90's, you really need to re-evaluate your whole approach, get 'with it' (suggest biting ends off TimTams and sucking rum / brandy into them at least) and maybe chuck out that Royal Doulton tea set and the Queen Anne furniture... And why the hankering for American Kraft/Heinz Nabisco Coffee anyway? ... No wonder your spellings all up the shoot! 😁 PW
[Magisk] 73sydney:
The airplane mode thing in what i call the "standard" Google Pay Fix, was always to me to avoid Google Play Store reconnecting before the reboot

Im a secret American
[Magisk] rodken:
Especially, with the beta version of Google Play Services.
[Magisk] tangcla:
I'm in the same predicament as you were - I cleared Google Pay data, rebooted, and when I started it again, it asked me for the Google account and then I'm back to the 'updating' screen. How long should it take to update?

EDIT: Jumped the gun, tried again after 5 mins and we're good!
[Magisk] Ryoncz:
Thank you, this help me a lot. ❤️
[Magisk] castaway1:
thank you

pndwal a lot.works!​
[Magisk] varunpilankar:
I tried this but still no luck..

Any other way around?
[Magisk] simika:
yes, this worked for me :-) thank you
[Magisk] J.PG:
It seems that Magisk v25.1 fixed Google Pay by itself, at least on my Redmi Note 11 Pro (sweet) with Android 11 (crDroid 7.16).
[Magisk] umibuzu:
I had some difficulties with this " not set up " NFC sign. But eventually, after erasing ALL data of pay+service(carreful not the " for AR"+play) , uninstalling pay, running an SD MAID, and reinstall again, I fixed it.
[Magisk] rpmccormick:
Did anyone ever figure out how to use GPay with no screen lock? I was hoping to find a Magisk module to allow this, but no luck so far.

I am not required to keep a pad lock on my wallet, I don't want one on my phone.

Add up all the seconds you have spent unlocking your phone over a decade, and you will find it wastes a lot of your life! I have never lost my phone nor my wallet in my 45 years of life, therefore I refuse to lock my phone.
[Magisk] 73sydney:
Its a requirement of all payment apps...

There is no workaround

End of discussion