yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
And a noble want it is!

I'm assuming colaborators (especially contributors) are in loops not traversed by us mere mortals...

After 34 days with no word on such development, your reassurance is certainly appreciated, if nebulous...

Some further clarity may actually become imperative to dispell any perception that development has in fact ceased, at least on the part of many; we simply don't have (active) sources to check...

I do understand that there are likely (certainly) loyalties involved that necessarily have colaborators between a rock and a hard place in this matter, so I'm not expecting such clarification any time soon. - But while the speculation has been effectively subdued, it's clear the pessimism persists nowhere more than on XDA.

Meantime, Ours is not to reason why...

And sorry for prolonging the OT here. 😬 PW
[Magisk] jaccydan:
Fixed this Google Pay issue.

In Google Play Store > Settings my Play Protection Certification was showing 'Device Not Certified', and in Magisk SafetyNet Check it was showing 'cts SafetyNet- Hardware attestation FAILED' in red (see my last post above).

Solution:

1. Ensure you install the lastest Magisk Canary APK build (https://www.androidsage.com/2020/04...ld-to-root-android-11-and-magisk-manager-apk/) = app-debug.apk; then in Magisk go to Settings > App > click 'Update Channel' then choose Canary. Reboot device.

2. Enable MagiskHide in Magisk settings and ensure all Google Play Services are individually hidden. Also hide Google Pay app there too.

3. In Magisk install modules: 1. Busybox for Android NDK & 2. MagiskHide Props Config. Then Reboot.

see:

4. From Google Play install Termux app, and run it for your particular brand of phone as also shown in the above youtube video.

5. Then manually download and (manually install in Magisk) the following software: safetynet-fix-v1.1.1.zip from:

Release v1.1.1 · kdrag0n/safetynet-fix

Changes Removed security patch fixup to fix CTS profile mismatches on some devices Some devices will now need to use MagiskHide Props Config in addition to this module in order to pass CTS profil...

github.com

see:

Reboot Device.

Et Voila - SafetyNet will PASS and turn blue in Magisk.

Also Google Play Store will report in Settings > Play Protection Certification - 'Device Certified'

I have successfully now added my bank card to G-Pay and linked my TicWatch and added G-Pay to that also.

I have just tested it on a local shop pay terminal and it all worked no problem.

Hope this helps someone with the same Google Pay issue.

I am running a Samsung s20 Ultra SM-G9880 Snapdragon Hong Kong variant. This solution could work for other phone makes and models if you make the appropriate settings changes and download the appropriate software for your device following my above methods - but don't quote me on that.
[Magisk] pndwal:
Just a (few) head's-up(s) as we wouldn't want to mislead others (even though perhaps OT here as this was really a Magisk SafetyNet-passing issue):

Works fine on latest public (Stable/Beta) build also as at this point it is essentially identical to debug (Canary), aside from verbose logging.

Please don't list 3rd party links / sources for official Magisk here as these have often been hosted with malware included (even on PlayStore!), and can be a real hazard / security risk.

If you do a little searching official threads and site pages, especially OPs, you'll find all you need.

Eg, magisk-general-support-discussion thread OP links Announcement Thread for "All information". OP there links Magisk's official GitHub Page "For all up-to-date info and links"... And you already have the link to this from any Magisk App version you have installed; Home page, GitHub 'OctoCat' symbol.

There, under Downloads, we read:

"Github is the only source where you can get official Magisk information and downloads."

Directly under this are big official links to latest public stable/beta and debug canary (app-debug.apk) builds.

Of Google Play Services, only standard com.google.android.gms.unstable SafetyNet process should normally be hidden.

MHPC module / fingerprint spoofing (configured in terminal emulator UI) is generally only needed for custom ROMs without built-in spoofing, and non Google-certified stock ROMs (China region, etc).

As you say you're now on stock I doubt you need this unless Hong Kong variant is non G-certified, but having bootloader unlocked you can always use global / different region G-certified ROMs.

While USNF module may work on your Sammy device, it is probably not the best available solution for 'heavily skinned' OS's like One UI as it will most likely break biometric authentication or other functions, and destabilize system because customised Keystore has been replaced with AOSP one.

A newer (experimental) fix from the same dev (shims the keystore service instead of replacing it) is now working for Sammy users (confirmed to fix S20 issues) and others with:

- some 32-bit ARM devices

- Heavy OEM skins

- Samsung One UI

- MIUI (needed for some variants only)

- Broken biometric authentication in apps

- Unstable system (i.e. rebooting and/or crashing)

Link (read OP here):

https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635

Nb. Additional working module variations for several specific devices are found in the closed issues mentioned / linked from PR thread above.

Hope these clarifications help, and possibly improve matters. 🙂 PW
[Magisk] greendra8:
[/QUOTE]

worked on my POCO F3
[Magisk] 73sydney:
worked on my POCO F3

[/QUOTE]

Just out of interest...did you try NOT using it?, i dont even use it anymore
[Magisk] greendra8:
Just out of interest...did you try NOT using it?, i dont even use it anymore

[/QUOTE]

Yep. After rooting it wasn't working but this fixed it.
[Magisk] 73sydney:
Yep. After rooting it wasn't working but this fixed it.

[/QUOTE]

Cheers, its just that its now rare to find a device where its actually needed these days :)
[Magisk] shaunoleary:
This has been working like a charm on my Pixel 3 (running LineageOS 18.1) for ages.

Things are a bit worrying with MagiskHide potentially being given the chop though. I'd say sticking with Magisk v23 will be crucial, I'll be very reluctant to update Magisk at all from here on.
[Magisk] jaccydan:
Hi guys, after a while of running my s20 ultra Hong Kong variant with the Google Pay fix (see earlier posts) - I'm back with a new issue in that the Google Pay contactless and online payments are no longer working, thus SafetyNet attestation is now failing (see below)..

Here is the error in SafetyNet Test. See 'Can't access Google Play Services':

The error also (of course) occurs in the Magisk app.

Here is the screenshot of the Magisk SafetyNet test:

Crucially (I think), I have noticed that Google Play Services have disappeared from MagiskHide (see pic):

(Just for reference) Here are the modules I still have enabled in Magisk:

I did incidently have to update MagiskHide Props Config.

I was wondering if anyone has any ideas that I can try to get this SafetyNet passing again - thus then getting Google Pay to work again?

Thanks in advance.
[Magisk] pndwal:
Just toggling MagiskHide off, then on again should restore SafetyNet process (com.google.android.gsm.unstable) in Google Play Services to MagiskHide list.

Check Magisk discussion thread re. new Google server end detection / ctsProfile failure over last few days. PW
[Magisk] jaccydan:
Thanks @pndwal the Google Play Services came back. I have just posted to the Magisk thread. Much appreciated.
[Magisk] pndwal:
Woops, that was actually MagiskHide Props Config module thread, not Magisk General Discussion thread. 😉 Sorry I didn't give the link.

For you and others, here are links for early fixes and some notes on developments, but read last few pages. 🙂 :

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

Early fix

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

Other notes

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

👍 PW
[Magisk] 73sydney:
@pndwal

Efficient as always you are... i was just updating my modules post to say people *may* need to use the rotten module again, and to give a brief reason why (magisk changes/google fun) and point them to the last dozen or so (currently) pages of the Magisk General thread for fixes :)
[Magisk] matheusdanoite:
GPay now working again on my Xiaomi Mi 9 running crDroid

Thank you so much for the help!
[Magisk] zoisa:
Hi, i have a redmi note 8T and my problem is i get Google Pay work, i pass safetynet but in X days stop working and safetynet dont pass, the only i could do is do all again, any tip for this? Im tired do every time, meanwhile i use a old version google pay with 0 problems but i dont think it work for ever. Thx.
[Magisk] infinitely:
I'm running a SM-G970F (S10e) with BeyondRom 8.7 (android R) and ThundeRStormS kernel. I'm passing safetynet and I'm also play protect certified and I'm running the SQLite3 and GPay magisk modules.

But I still can't get mobile payment to work in my banking app (ING bank). Whenever I try to enable mobile payment the operation fails. It works on stock so I know it's not the app or some temporary issue with the bank. I've also hidden root from my banking app with MagiskHide. Anyone got any ideas?
[Magisk] 73sydney:
Have you tried clearing data on Google Pay and then readding the card? If you have done some of the steps after first adding the card, sometimes clearing Google Pay can make the difference. Its not an exact science though...

My personal setup from ROM flash is to:

Install Magisk

Enable Magisk Hide / Deny List (latest Magisk)

Test SafetyNet

Hide banking and other apps (I restore my backed up /data/adb/magisk.db file - includes all MagiskHidden / Deny List apps (latest Magisk), saves adding those by hand every time i flash a ROM. (Semi) Pro Tip)

Reboot

Hide Magisk App

Test Google Play Store for Certification

If not certified:​

Toggle Airplane mode on, clear data for Google Play Store, Google Play Services and Google Pay

Reboot

Toggle Airplane mode off

Check Google Play for Certification

Add card to Google Pay

i.e. I never add card at the beginning, ever.....

​
[Magisk] infinitely:
Thanks for your response. Actually google pay is not available in my country but rather the bank app itself has a feature to enable mobile payment. For the sake of testing I just wiped the data on the bank app and set it up anew but didn't help unfortunately.
[Magisk] 73sydney:
Sorry, i assumed that the bank app would somehow be tied to Google Play as it is with every bank account ive ever had that ive used Google Pay with :)

And youre in the Google Pay thread....

If you like you can try (if using the a version of Magisk with MagiskHide still (its changed recently to a Deny List - let me know if you are using the Deny List recent versions and i can try and help you edit what im about to suggest to try it with some mods):

Riru (download the file Riru-v.xxxx NOT Source): https://github.com/RikkaApps/Riru/releases/latest

and

my Riru-Momohider (mod which auto configures the config files) atatched to the post here: https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2320#post-85187739

Install Riru first via Magisk Manager, then reboot

Then install Riru-Momohider (Mod) and reboot

Test and see if it works

These modules are what i use to keep Samsung Pay from sniffing root on my Pixel, and also helps with my banks official app...

You can also try Riru-Unshare (https://github.com/vvb2060/riru-unshare/releases/latest) in place of Riru-Momohider, but not both at once....

These Riru addons are designed to try and isolate apps from detection above what MagiskHide can do

All mentioned modules are uninstallable/reversible as magisk modules
[Magisk] @chris@:
Hi guys,

I would like to share with you my successful SafetyNet fix experience. Here is how I did it (TWRP 3.5.2-9.0 + crDroid v7.8 + NikGapps-basic-arm64-11-20211018 + Magisk-23.0) :

- After the first installation and reboot, Update Magisk. If you try to download the proprietary code of Magisk : certificate refused.

- then Update Magisk Application then reboot.

- Enable development settings, thenFrom the modules section, download riru-v26.1... + BusyBox + MagiskHide Props Config and reboot.

- Go to Magisk Manager/Settings : Enable MagiskHide, also hide Magisk Manager. Add a shortcut to the home screen : ok.

- Check Safety Net Download of the owner code : Certificate granted !
[Magisk] 73sydney:
This process is device specific (always best to post which device youre using), though common for newer devices/magisk builds...and more related to general Magisk than here in the Google Pay thread....

Im glad at least it allows you to then use Google Pay
[Magisk] Thaliya:
Is the any way one the newest Canary Build? I cant find a way to downgrade to older Magisk with MagiskHide. Phone: OnePlus 8T 11.0.11.11
[Magisk] Flexy':
Worked like a charm on ASUS Rog Phone 5 with Magisk 23, thank you!

chmod 440 dg.db

before launching Google Pay + Magisk Hide ticking is all it took.

Reverted the permissions back to 660 after launching GPay and it still appears to be working 😵
[Magisk] 73sydney:
where exactly are you failing, do you

1) Pass SafetyNet? Have you checked with a safetynet testing app? like:

GitHub - RikkaW/YASNAC: Yet Another SafetyNet Attestation Checker

Yet Another SafetyNet Attestation Checker. Contribute to RikkaW/YASNAC development by creating an account on GitHub.

github.com

apk download:

Release v1.1.5 · RikkaW/YASNAC

What's Changed Add ID translation by @alinuxrc in #19 Fix Indonesian localization by @alinuxrc in #21 Show short app name only in the app drawer by @VladWinner in #20 Show the reason of isGooglePl...

github.com

Because nothing else after that matters unless you pass safetynet first
[Magisk] 73sydney:
Updates to GPay SQLite Fix Module:

Note: Existing users do need to upgrade, the changes only affect new installs...

v2.5 9/12/2021

Changes in:

module.prop

version bump, i had forgotten to do that since v2.2 :)

install.sh

New script code added (to @Didgeridoohan 's previously generously contributed lines) to detect and hide packages depending on whether user is using a version of magisk with either magiskhide or zygisk and deny list.

The code should only use magiskhide method for 2 magiskhide compatible variants of magisk (stable (topjohnwu) and custom (TheHitMan7)), and zygisk and deny list method for the other 2 magisk variants (canary (topjohnwu) and alpha (vvb2060))

Credits to @osm0sis for helping put my head straight on gms not needed to be hidden when using zygisk, with 4 variants its easy to get confused :)

Ive been meaning for a little while to add the ability for the script to automatically adjust for hiding based on magiskhide or zygisk and deny list. Sorry it took a little while to get to it, life got in the way. Ideally no one would still be using this, but for some it seems to make the difference, so i have made what i hope is the final build of it.

As im not directly responding to posts here on XDA any longer, please lodge any issues on my github directly, thanks.

Module download and github repo links for any issue reporting as always in the original post for the module here:

https://xdaforums.com/t/working-mag...s-of-gms-17-1-22-on-pie.3929950/post-79643248
[Magisk] bricked.:
Hey,

I just had fun doing this whole thing (after a system update) and documented each step:

How to root and enable Google Pay on a CustomROM (Lineage) (SafetyNet bypass)

How to root and enable Google Pay on a CustomROM (Lineage) (SafetyNet bypass) - lineage-root-and-enable-google-pay.txt

gist.github.com

I used lineage-18.1-20211208-nightly-jason-signed.zip on my Xiaomi Mi Note 3.

I hope it helps.
[Magisk] braveheartleo:
Thanks for the correction, got the two modes switched. ?
[Magisk] xxxvego:
Hello guys !

Can you download applications from the store after doing this? There is a problem for me, it still stands for "downloading". I tried to delete the Google Play Services and Store cache and data, installed other versions, the internet works, SafetyNet true, device is certified. Anyone have any ideas how can I fix this without factory reset?
[Magisk] joeynshelby:
No problems here. Play store is working as it should.
[Magisk] vandyman:
I can not get past the bank card verification.

It just faults and says "Something went wrong".
[Magisk] logikor:
doesn't work for me, unfortunately! Any other tipp what I can do to get it work.
[Magisk] rwanek:
Unfortunately for me it doesn't work, i used automate flow [MENTION=9317193]73sydney[/MENTION] posted here but cant add card due to "your phone may be rooted".

Maybe i missed some step?

Pixel 2 XL via Tapatalk
[Magisk] raphytaffy:
Just wanted to comment and say that this is an absolutely amazing fix and this is what keeps me coming back to the community. Cheers!
[Magisk] DavidRJ:
Huge thank you! Finally a method that works, tested on Android Pie, GMS version 17.1.91.

Since you don't want any donations, a shell script to automate the process is at least a small contribution I could do here :)

It automatically downloads the correct SQLite3 binary if not found and then follows your tutorial basically.

https://github.com/davidramiro/gpay-gms-patch
[Magisk] martyfender:
On question, will this script download an SQLite3 binary for x86?
[Magisk] jcmm11:
I checked the script, and verified the download. Yes it will download for any Android abi, including x86 and x86_64. SQLite version is 3.22 from January of 2018.

One caution - script mounts system as RW and installs to xbin, whether you have an xbin directory or not. If you just want to download the file yourself:

x86

https://raw.githubusercontent.com/davidramiro/gpay-gms-patch/master/bin/x86/sqlite3

x86-64

https://raw.githubusercontent.com/davidramiro/gpay-gms-patch/master/bin/x86_64/sqlite3

arm64-v8a

https://raw.githubusercontent.com/davidramiro/gpay-gms-patch/master/bin/arm64-v8a/sqlite3

armeabi-v7a

https://raw.githubusercontent.com/davidramiro/gpay-gms-patch/master/bin/armeabi-v7a/sqlite3

armeabi

https://raw.githubusercontent.com/davidramiro/gpay-gms-patch/master/bin/armeabi/sqlite3
[Magisk] DavidRJ:
I thought xbin was a fitting directory since it contains non-essential binaries (I actually thought it was a default directory, so you say it might not be present?) and sqlite can be called natively since it should be a PATH directory. Am I wrong there? I'm of course open for any suggestions, I understand mounting system as RW (even if I remount it RO afterwards) might not be an elegant way.
[Magisk] jcmm11:
A lot (most?) newer phones don't have an xbin directory. Since system is supposed to be read only I guess Google decided xbin wasn't needed. On top of that trying to add an xbin directory to /system/ via Magisk has proven problematic. Which leaves 2 options: check if xbin is present. If not stick it in bin. Or just stick it in bin to start with and forget about xbin. (Also means you need to check both locations if you're checking if it already exists)

The problem with mounting system RW is that it breaks OTA. Some people don't care about that - some do. The better way is to create a Magisk Mod and do it systemlessly. You can either create an official Magisk Module or just generate the required structure on the fly in the script. Either way you would need a reboot before it showed up in the PATH but you could explicitly call it using the full path before that.
[Magisk] DavidRJ:
Gotcha, thanks - I think I'll ditch /system entirely then, because I do not want to touch bin as much as I do not want to break OTA, wasn't aware of that. I will probably just put it in /data/local, as it doesn't have to be in a PATH directory for the sake of this script as it gets called with its absolute path anyways.
[Magisk] Tr4sHCr4fT:
Thanks for the binaries also, please keep them up!

---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------

option 3: throw it into /data/local, chmod it executable and just call it straight from there (/data/local/sqlite3...)
[Magisk] DavidRJ:
Yup, will do! Also, no worries, the binaries stay up, I won't delete the repository.
[Magisk] 73sydney:
Note: i am running magisk - latest canary build and pass every check before i fiddle with trying to add cards...

Only things ticked in magiskhide are:

com.google.adroid.gms.unstable (standard i beleive)

my banking app

Thats it

Nothing fancy here

Note: added the armv7 sqlite3 v4.1 binary magisk module im using to my earlier post....
[Magisk] Bidalos:
Hide Google Pay as well. You dont need Magisk Canary. Just install 19.2
[Magisk] 73sydney:
So far havent needed to hide anything other than what i listed earlier.

fwiw Google Pay is not ticked here and it works fine...i forgot to tick it before i added the card yesterday and it worked just fine, go figure

Didnt say anyone needed latest canary, just said i was :) :)
[Magisk] dwane3:
Sorry,where to put and how to run this script?
[Magisk] Bidalos:
Okay. Then I don't know your problem.
[Magisk] Conan179:
Hello@all.

i need help for my note 20 ultra 5g.

On A11 are the gpay fix working, on the 25.12 i update to a12 and now, i cant get it work.

saftynet check are pass.

the ne magisk hide are on and gpay both tikt.

i have many time, delet the module, reboot, install, with vol key, with out vol key.

i dont know what i make do.

Can any body help?
[Magisk] soCram:
This will not be sufficient anymore with Android 12. I had the same issues and even with fixing the SQLite DB it didn't work for me. You will need to use the three dots on the upper right, show system apps and type in gms. The Google Play Services will be required to be hidden too, otherwise, they will "refix" the security flag sometime in the future. It is necessary to clear the data of Play Services, Play Store and Google Pay.

But be aware that hiding Google Play Services might cuase some other issues. At least for me the hiding did not work after a reboot and needed to be redone after every reboot. Additionally, my Samsung Watch4 will not connect anymore and does require a reset after hiding the Play Services (just in case you're also using a watch).
[Magisk] Conan179:
In the meantime it works, I just had to wait 24 hours.
[Magisk] soCram:
Good to know. For the sake of completeness. Did you use Zygisk to deny Google Play Services? For me it's also working at the moment even without having it on the deny list.
[Magisk] Conan179:
no zygisk, deny list, and ruru modules.
[Magisk] 73sydney:
Updates to GPay SQLite Fix Module:

Note: Existing users do not need to upgrade, the changes only affect new installs...the module name change means if you did install it you will end up with 2 identical modules, with two different module folders. Again, only use the newer one on new installs...

v2.6 11/01/2022

Changes in:

module.prop

Change module ID to match repo for submission to Alt Magisk Repo for download using Fox Magisk Module Manager - i never bothered trying more than once to get it on the official repo, due to personalities, hopefully the Alt Repo team has less people with umm "personality defects". As im no longer posting on XDA, i thought i might as well submit it to the Alt Repo. Ideally most people wont need to use it, but it does seem to solve issues for some edge cases.

(Note: Thanks as ALWAYS to didgeridoohan who always wondered why it wasnt on there and helped in its evolution) - we have over 36,000 installs without it ever having been on the repo, mostly word of mouth, the occasional link in the GPay thread on XDA, or my (previous) signature on XDA

Special Note: thanks of course to @BostonDan, who developed the original fix (coming up to almost 3 years ago) i half assedly packaged into a magisk module, who just liked this post, i forgot to thank him before he did so :)