yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
Updates to GPay SQLite Fix Module:

14/01/2022

Big news, the module is finally on a repo...the Alt(ernate) Repo.

If you've been living under a rock for the last few months, you may not be aware that the official Magisk Repo has been removed from the Official(and other) Magisk Manager apps.

In its place, you have the choice of now using Fox Magisk Module Manager which also has access to the Alt-Repo

I made the necessary changes to my modules to submit them earlier in the week, and they were accepted late yesterday.

Going forwards, it will be easier for people, the few of you who still use this module especially, to see any changes that may take place.

(I live for the day when its dead and buried)

The often required SQLite3 Universal Binaries for use with the GPay SQLite fix module, is of course also now on the Alt Repo. (I also have a couple of other modules on there that are unrelated.)

I have updated the repos and releases links in the OP (linked below) for those who dont use the Fox Magisk Module Manager to reflect their new locations

https://xdaforums.com/t/working-mag...s-of-gms-17-1-22-on-pie.3929950/post-79643248
[Magisk] seemebreakthis:
Just wanted to report back quickly.

Was using Google Pay no problem, with @73sydney 's SQLite fix. Updated to the latest canary Magisk, and did some setting up before GPay is once again usable. Note: chances are not all the things below are necessary, but I am not going to make changes as long as it works. So pick and choose from the steps below as you see fit.

1. Enable Zygisk

2. Enforce Denylist, and add Google Pay, and Google Play Store (not sure if needed actually), to the Deny List. (I am a bit surprised I do not even need to enable Google Play services in the Denylist)

3. Install the magisk module "Universal SafetyNet Fix v.2.2.1" https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1 . Note this is specifically made for the latest Magisk build with MagiskHide stripped and Zygisk added.

4. Reboot, and test to see if you can pass SafetyNet. Since Magisk Manager doesn't have the safetynet check feature anymore, just download an app from playstore to do it. I use "SafetyNet Test".

5. If "passed", then "clear all data" for google pay, and google play services.

6. Reboot again, and you should be good to go.

Note that all along I have the SQLite Fix module installed, and I assume it is still needed as a prerequisite (although @73sydney hinted on not needing this module anymore from his earlier comments...?)

Anyway, happy to still be able to use GPay even with latest canary build.
[Magisk] BenDamnFinegold:
@73sydney let this be my only contribution: you wrote 14/01/21 when you meant 22.

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

I'm struggling to pass Safetynet on my Pixel 2XL running LineageOs 18.1... the play store says my device is not certified.

maybe I should finally upgrade my phone, though its screen is not cracked even after numerous drops.
[Magisk] 73sydney:
Hehe good catch, fixed

I barely function as a human, i have no concept of time at the best of times :)
[Magisk] BenDamnFinegold:
That worked for me on Pixel 2XL running Lineage OS 18.1 January 20 update.

I did not need the SQL Fux script.

Simply installing magisk canary, enabling zygisk, enforce denylist and adding pay, play, service and every banking app known to mankind, installing USNF v2.2.1 Zygisk. Reboot.

Did not pass safety net when checking via 'safetynet test' app.

Installing magisk hide props config and launching termux: 1, f, 7, 17, y, reboot

Safety net passes and Gpay works.
[Magisk] 73sydney:
Updates to GPay SQLite Fix Module:

v2.7 - 1/2/2022 (DD/MM/YYYY)

Update to ZackPtg5's MMT-Ex extended magisk module format 2.0

changed from old VKSEL key selection method to newer chooseport method, and added 5 second delay, over default 3 second one

Update for magisk 24 plugin schema

included update json link (for those who dont use Fox Module Manager to keep those folks up to date too)

included changelog link

For existing users upgrading to this version, choose NO to clear data prompt during install to avoid card loss,

you will then still get to update and enjoy the update.json benefits

As always the prerequisites, pre-installation checks, troubleshooting steps, and downloads are in the modules OP here:

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

In just a few weeks the first version to appear on a repo has racked up just shy of 1,200 downloads...
[Magisk] Cargonausorus:
Thanks for the update. The 2.6 module did not fix the Gpay issue for me. Where do you find your module for Android 9.0 version .zip with Magisk 23.0 stable?
[Magisk] 73sydney:
There is no "Android 9.0" version, there has never been a version for any specific version of Android

There is one version, and currently its 2.7

If it doesnt fix your GPay issue, i suggest you read the OP for the module and check the steps for troubleshooting, theyre there for that reason. It could be that you didnt read it before installing the module....there are pre-requisites and a pre-installation checklist to get the best possible chance of it working for you out of the box....and if you fail theres troubleshooting ideas...

The module is NOT a 1 click solution, people in general need to stop treating it like such and read the manual....its arguably the MOST documented (as in jokes about how it has broken the single post character limit on a few occasions) module there is....i even mention checking the troubleshooting guide in my above post.

People need to check there before posting.

Over 97% (pulled from the air but pretty accurate nonetheless) of ALL GPay module issues are solved by clearing the data for the relevant apps - again its in the troubleshooting guide.
[Magisk] 73sydney:
To all...

When theres a tonne of helpful information, added over years, this really should be a...

Personally i only post here to keep folks updated about the status of the module, not to spoonfeed people. If you have a legitimate issue with the module and have tried all the suggestions the OP and availed yourself of the Search box and set to search this thread, then by all means, please raise an issue on the modules github

Eagle eye viewers will also note (via my signature) that ive retired from taking any active part in XDA outside of keeping the module, which was started here, updated here, as a courtesy for having pinched and cobbled together the work of others, notably BostonDan who came up with the methods, into a module.

I repost links to the modules OP everytime i update, thusly...

As always the prerequisites, pre-installation checks, troubleshooting steps, and downloads are in the modules OP here:

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

Please read the manual, or use search...
[Magisk] Cargonausorus:
Good evening, it's good with the module and the manipulation of the data well erased Gpay works perfectly. I thought that as the contactless payment logo was crossed out it was not good. In the end I paid tonight and it worked!! Thanks again !!!
[Magisk] nevernat_theoriginal:
Page on GitHub is missing.....
[Magisk] 73sydney:
See note coming below.....
[Magisk] 73sydney:
Announcement On GPay SQLite Fix Module:

Due to a group of low individuals, lets call them Androidacy.com, who i found like to scrape both the original Magisk Repo and the newer Magisk Alt-Repo and then insert ads into the Readme.md files and the pre-download pages on their website to try and monetize the work of magisk module creators, most who have created and updated modules for years for free to support the community, i decided to remove my modules from the Magisk Alt-Repo, as well as make people aware what these lowlives were doing.

The GPay SQLite Module especially i felt deserved better than those vultures trying to get page clicks and views, as i only packaged the method created by @BostonDan into a module, i didnt invent the method. I was not prepared to just surrender the original method and work, let alone my own to these fools.

As they were no strangers to scraping repos, merely rolling back to my own repo would accomplish much, as my first contact with them was to ask them to kindly not list my module and my explanation why, they chose to ban me from their main method of contact on Telegram, while being really dismissive asserting they were not "monetizing modules", they "were monetizing their website."

I beg to differ, as this is an example of how they are "monetizing" their "website" - inserting ads at the end of Readme.md files,, and on pages before presenting modules for download that theyve scraped from the repos...this is an example:

For the moment, until i think of a better way to distribute the modules(s) that cant be abused by opportunists, the module releases will only be posted here on any new release. As the number of posts is fairly low, people should hopefully be able to find a link towards the end of the thread. Hopefully ill find a better way...

For the moment the required files will be attached to the modules original post here:

https://xdaforums.com/t/working-mag...s-of-gms-17-1-22-on-pie.3929950/post-79643248
[Magisk] Fishawy:
There used to be a way on the old XDA where a moderator can pin/sticky a certain post in a thread right after the OP's. You can check that, and if so then yours will be #2.

Thanks for the continuous efforts.
[Magisk] 73sydney:
Announcement On GPay SQLite Fix Module:

Late yesterday the offending party's spokesperson posted that they had made changes to how modules would be handled and specifically that authors could request removal from their repo, which is a stark contrast from their moderators "you have no claims" and immediate ban from all forms of communication.

You can read their full statement here:

https://xdaforums.com/t/androidacy-...-your-modules-your-work.4397385/post-86383595

As such, my modules, including the GPay one will be returning to their original repo, while i see how things pan out, and all going well may return to the Magisk Alt Repo in the near future.

I would like to thank those who supported those of us (i was merely one, the others were voicing their concerns on Fox MM's github issues pages) who objected to the monetization angle and handling of this issue, including Fox2Code (author of Fox Module manager - who was negotiating in the background while i just poured petrol and lit it) and the moderators and submission team from the Magisk Alt Repo

Ideally it shouldnt have gotten to the point of me blasting my repo away and having to post so vehemently against them publicly, but well they did block my attempts to try and resolve this any other way.

The repo links are back in the modules original post here.

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

Both modules have had a version bump reflecting the change of the updateJson links (for Magisk 24.X+ users) pointing back at my repo, theres no new functionality added.

I have also, considering my objection to people trying to monetize other peoples work, made the originators and contributors to the module more prominent (previously these credits were shown during the install) on the README at the repo. I have also made it quite clear where i stand on people forking/copying the modules with a view to trying to monetize it.
[Magisk] 73sydney:
A quick search of the linked ROM, and especially this post where youve had a direct reply, says its a suspected known issue.

Nothing in my module or in general troubleshooting for it is going to fix errors like:

02-07 14:25:13.693 5925 17504 E CardEmulation: This device does not support card emulation

Thats a device issue im sorry to say.

Posts in the linked ROM thread suggest it may be being worked on as its common on another device

Sorry i cant help on this one
[Magisk] AlexALXua:
Ok thanks for reply, well, just wanted to be sure i'm not missing something. Have a good day!
[Magisk] Mass59:
To thread
[Magisk] QuietMountains:
both the sql editor and the terminal app have root access, set that attest value to "0" and typed in those commands and it's telling me it's not permitted
[Magisk] BostonDan:
You do not appear to be running a root shell. Type 'su' <enter> before those commands. Even though it has root access, you still need to enter root in the terminal shell.

Cheers,

B.D.
[Magisk] QuietMountains:
Thanks for catching that. Used it but unfortunately it didn't change anything :(. Gpay still won't let me add my card. Appreciate the help though
[Magisk] BostonDan:
What version of magisk? 24.1?

Do you have gpay in your "sent list" in magisk?

Cheers,

B.D.
[Magisk] QuietMountains:
I have 24.3 for Magisk. Google Play Store says my device is certified. GPay launches but it won't let me add my card. Whenever I try to open the wallet from the notifcation bar, Google Play Services launches for a second then crashes, even after clearing data and having USNF.

Weirdest part is it was working at one point a few weeks ago but I cannot point out what I changed to make it stop working...
[Magisk] BenDamnFinegold:
I have it working on my Pixel 2XL Lineage OS 19.1, Magisk 25.1 with Denylist, Zygisk, UNSF v2.3.1 und MagiskHidePropsConf-v6.1.2
[Magisk] vladone97:
Now that Google Pay became Google Wallet, I can't add new csrds to the app. The cards already saved ones work fine, but when I try to add a new card, after I enter the CVC, it says "Contacting the bank", and then "The phone cannot be configured for contactless payments". Contactless payments actually work fine, it just gives me this error when I try to add a card. How do I fix this?

Update: now contactless payments don't work either.
[Magisk] pndwal:
Some discussion in this thread, and I linked my fixes for similar (not identical) issues here:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87179213 🙃 PW
[Magisk] vladone97:
Didn't work. I also tried deleting Google Wallet, clearing the Google Play Services data, reapplying chmod and reinstalling Google Wallet. That didn't work either. I guess Google Wallet has better security than Google Pay
[Magisk] alagga:
Same problem for me. We really need a fix 🥲
[Magisk] nevernat_theoriginal:
Same problem for me.
[Magisk] 73sydney:
Okay, for those having issues, i can confirm now too that something screwy is going on here....

Okay, i just went to check the Wallet app and got the popup message about device not meeting security requirements...random

So i removed the Wallet app, rebooted, installed it and readded to Deny List (for reference i am not using Shamiko, im using Deny List Unmount under Magisk current stable)

Tested app...all cards were present...no issues...Contactless Menu option showed fine

Waited about 20 minutes, tested Wallet again...popup message again

Main screen still shows Contactless available

Contactless Menu shows negative status

Going into my ANZ cards settings however shows contactless fine - i.e. i have a "deactivate contactless option present"

Perhaps interestingly, the screenshots are tagged under the app name Google Play Services...that was updated itself 3 days ago at least on my device

Please note, as i have a Watch 4, i havent done the usual "treatment" thats in my Google Pay magisk module post and i normally prescribe of clearing Google Play Services/Store/ Pay(Wallet), as clearing Google Play Services when you have a Watch 4 means having to reset the watch and setup from scratch again which is a total ballache of a process when you have so much tweaked and hacked on it, and i dont believe it would make any difference in this case.

I tend to think it might be a bug in the Wallet code at this stage, as while its flagged contactless as being broken in one place, in 2 others its still rumoured to be okay...i cant confirm as its 2:15AM here and all the shops are shut :)

Not that i didnt believe you peeps before, i just believe you a lil bit more now :)
[Magisk] rodken:
I'm still waiting for the 'random weirdness' to swing my way.

-- Will keep the current installed modules in place until further notice.

-- Real world testing has revealed that 'all is right in the world of mobile payment service'.

-- Still have the 'green light' for Play Protect certification.

-- Periodically, checking TB Checker for Safetynet Attestation.

-- Successfully uploaded my COVID Vaccination info to Wallet [just to see how far I can ride this wave]

-- Waiting on the switch for the API to add Driver's Licenses [wishful thinking].

N.B.: If there is any consolation, these findings are derived from a OnePlus 8 running OOS11 Stock ROM.
[Magisk] Paulo_1307_:
It's not just the Google pay/wallet. Check your Google play store, it should now be uncertified in a different way.

Now it does not shows if you're certified or not in the settings. But in reality you lost certification. Try searching for Netflix, it's just gone.

About 5 other people that were having issues with Gpay reported the same thing in a telegram group
[Magisk] setmaster:
Nope, not correct. I am also having problems with Google Pay -> Wallet update and not beeing certificated, but I can find, install and use netflix via playstore and DRM Info shows Widivine L1.

I have a OnePlus Pro 8 running Android 12 and XxX No Limits Mod.
[Magisk] BootloopedMillennials:
What version play store and play services? I still have Netflix showing but my Playstore hasn't updated to the latest yet (based on what is showing as the latest on APKMirror). My Play Services is 22.26.15.
[Magisk] Gleniu:
Same for me. Play store shows device certified, but Netflix is gone from search result.
[Magisk] 73sydney:
fwiw my Play Store is still certified AND i can still find and install Netflix

Play Services: 22.26.15.
[Magisk] nevernat_theoriginal:
For me:

Play store 31.4.10-21 shows device certified, If I look for Netflix in the Play Store I find it safely, but Wallet still says that my phone does not meet the security requirements.
[Magisk] rodken:
Updating to v.31.5.16-21 might or might not resolve the latter issue.
[Magisk] Phil21185:
Whoops, I made a fresh thread about this before finding this one.

Yeah I got a notification about an hour ago that my device was no longer secure enough for Gpay. After clearing caches, data and uninstalling, I saw that it's now Google Wallet.

I can't add cards now and Netflix is gone for me too. Device is certified. 31.4.10-21 and saying it's up to date (UK).
[Magisk] Treacletin:
Same. Tried clearing data and reinstalling a lower version of Google Pay. I'm not on Magisk 25, because the Ambassador custom ROM kernel that I use hasn't been updated yet. I'm on an S10 and rooting is much easier with a kernel. You just can't update Magisk until a new kernel comes out! Maybe that will sort the issue out. Hopefully someone figures out the fix.
[Magisk] vladone97:
I have Magisk 25.2 and it doesn't work.
[Magisk] Wickii:
Same here.

Oneplus 8 pro OOS 11

Magisk 25.2

xXx NoLimits 12.4

Shamiko

Universal SafetyNet Fix
[Magisk] miss:
some. pixel 6 , ota july, magisk 25.1 stable
[Magisk] roles75:
Same here.

Samsung Note9 with NOBLE ROM 2.x / [ROM][N960F/DS/N][ALEXNDR]

Magisk 25.2

Shamiko v0.5.1

Universal SafetyNet Fix v2.2.1
[Magisk] pndwal:
Re. new Play Integrity detection in GPay/Wallet, Playstore (and more soon), please read back in this thread, and see my post linked here:

https://xdaforums.com/t/...agisk-discussion-thread.3906703/post-87191597

🤠 PW
[Magisk] Treacletin:
Installing magiskhidepropsconfig and changing the fingerprint to Pixel 4a worked for me.
[Magisk] 73sydney:
Credit to @Displax

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-87198517
[Magisk] BostonDan:
One thing I did find (and this may just be me due to device configurations), is that Kali Linux trips root detections, even if play store shows device certified.

Just a PSA for people.

Cheers,

B.D.
[Magisk] Haas8:
I was trying to get this too work too on Lineage OS with Pie on a Lenovo P2.

Finally got it too work with the "USNF modded script" and "Gpay SQLlite Fix" and "Shamiko". I did the sqllite fix at last and followed the instruction by adding cards and then rebooting. After that no errors any more and pay seems to work. Still have to test in the shops tho.
[Magisk] 73sydney:
Nooooooooooo!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! lol

Can i ask if you tried with just the USNF and Shamiko, but without the GPay SQL Fix module?
[Magisk] Haas8:
Yes, like I said I did the sql fix last. There was also talk that I should have waited, but I have no patience.... Is there an issue in doing it this way?
[Magisk] 73sydney:
An issue in doing it that way?

No, and its not like im triggered and feeling super stabby about it, but ideally it shouldnt be necessary for 99.9% of people, there are weird edge cases where for unknown reasons it may be the only thing that works....

Just last night someone asked me to elaborate on why i try and dissuade people from using it (in my signature and elsewhere), so if youre bored you can go read that *very brief and concise post here

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/page-98#post-87231671

* Yes, everyone else who has read it already, i am the Worst
[Magisk] Haas8:
It maybe just worked without it but as I had read I should have waited 3 days, but yeaaaaaaaaaaah I failed on that part.

But anyway huge thanks too you and other devs who made this possible, it such awesome that I have an old phone running perfectly fine on Andriod Pie!
[Magisk] Fishawy:
Just when I thought I was out, they pull me back in! :D
[Magisk] ivanzipfer:
It does help me too. Working fine Pixel 5a
[Magisk] pndwal:
Very old initial solution... (fingerprint prop mismatch is a trigger for bypassing hardware verdict type enforcement in new Play Integrity API.)

@Displax's modded USNF fork (w/ deviceIntegrity fix for PI) is a much better available solution now... PW
[Magisk] 73sydney:
I think theres been a communication breakdown here, i wasnt reporting a problem

I dont have any issues, thats what i was trying to get across to the person who posted about using my automate script

I was just respondiong to him with my config to show i wasnt doing anything special :)
[Magisk] mike2587:
I have some questions/issues

1) using manual method with termux terminal (with root access) I got sqlite3 missing message (I installed the sqlite3 magisk module and rebooted)

2) with that method do I need to hide gpay and playservices in magisk manager?

3) with that method do I need to reapply it after every reboot? And that's why there are tasker or automate tasks?

4) can someone confirm the final working procedure? Just to be sure
[Magisk] eelsid:
This happened to me too. I deleted the card from Google pay altogether and tried again a couple days later and it worked. I'm thinking it was locked out by the bank from too many failures and the lock timed out on it's own.
[Magisk] vandyman:
I will give it a couple days and try again.

.
[Magisk] Leeum:
Since doing that i have had no problems adding and using my cards. I followed the instructions from post #58
[Magisk] MonztA2:
Anyone updated to the recent Google Pay 2.89.248785339? Hesitating to update.
[Magisk] Alpetrus:
Google Pay updated to 2.89.248785339 and everything works fine on my phone (I've made several payments).
[Magisk] pr0adam:
Thank you so much for this fix as well as the tasker file to automate it. Worked easily
[Magisk] shaDNfro:
Since I applied these changes my whatsapp does not get any push notifications... Any possible relation?
[Magisk] joeynshelby:
Also updated. No issues. Made payments as well.
[Magisk] Tr4sHCr4fT:
yes sometimes the device associated is not removed from the bank backend. Revolut kept telling me the card was "already added". worked again after a day.
[Magisk] rexx0520:
This works like a charm!

small problem here. Wear OS App is consuming RAM (1.5GB) after doing this...
[Magisk] Tr4sHCr4fT:
2.89 seems to also have fixed the "can't add card" without "altered/modified" issue