yashsingh1/xdaforums huggingface dataset:
[Magisk] Arkan_:
Hi,

I tried to follow the method of 73sydney by installing via Magisk SQLite for ARM aarch64 devices, and then Google Pay SQLite Fix, but this one doesn't want to be installed.

What I did:

1. Installed SQLite via Magisk repo

2. Phone Reboot

3. Downloaded GPay-SQLite-Fix-master.zip

4. Went to Magisk Modules, selected GPay-SQLite-Fix-master.zip which was located in my Download Files of the phone.

Then, it shows a message saying that zip is not a magisk module.

My phone: Pixel 3a, Android 10 (december update), original ROM (Pixel Launcher)

Safetynet check pass succesfully.

What did I do wrong?
[Magisk] dr.terrible:
Hi mate, looks like you've downloaded the source code snapshot. The file you need is GPay.SQLite.Fix.v1.9.zip

Here is the direct link, file size is 8.33kb

https://github.com/stylemessiah/GPay-SQLite-Fix/releases/download/v1.9/GPay.SQLite.Fix.v1.9.zip

FYI it's on the releases page, release 1.9, in the expandable Assets section. Download button on the main project page just gives you the latest sources from the master branch -- that's why you have that '-master' part in the file name.
[Magisk] Arkan_:
Thanks a lot! I'm not that used to github, thank you for showing me the right link.

I was able to make Google Pay works, but I cannot put my credit card.

I figured that my Bank is not compatible with Google Pay, only with Paylib app which is a French NFC system pay. Of course Paylib app doesn't want to start as it sees that my phone is rooted even if Magisk is hidden for this app. Looks like I will have to find another way to be able to pay with my phone

Thank you anyway for your help and your quick answer!
[Magisk] 73sydney:
Ive just updated my original post with clear instructions on which file is the correct one to download.......

To download the working module zip, please click on the release link for any of the files below (this will take you to the latest release), and then download the first zip file on the following page, not the source.zip file nor the source.tar.gz below...

To look over the code and contents in the module, use the repo link and either browse the code and contents online or download the zip from that page. If you download the zip from the repo link it will not work as a flashable magisk module....
[Magisk] dr.terrible:
Glad I could help.

Does Google Pay say your device can't be used for NFC payments? Because after you apply the sqlite fix, I think you have to clear app data for Google Pay, although I'm not sure. Try it, maybe it'll help.
[Magisk] Arkan_:
It says I have to "Double-check my card details", because "something went wrong", even after I cleared app data and cache. NFC is activated in my phone settings.

I guess it's more on my bank side, which is not compatible with Google Pay as I saw in the website. Only with Apple Pay, Samsung Pay, and in my case, Paylib.

Thanks for helping anyway, I appreciate :)
[Magisk] fvc2000:
Everything was working with the instructions. But I don't know what happened, maybe January pixel 4 security update, that my card got deauthorized.

Like a brand new install, asking for set up for in-store payment.

Tried adding and I got back to "double-check your card details" when contacting bank

Tried 4 different cards from 3 different banks.. all were working till 3 days ago.

Tried uninstalling sql and fix and reinstalling. Tried the command on termux from https://xdaforums.com/showpost.php?p=80763371&postcount=11

Nothing works

Please help

---------- Post added at 08:39 PM ---------- Previous post was at 07:57 PM ----------

Nothing wrong with the method.

Just discovered with my bank support that they only allow to add a card to Google Pay through the bank app.

It automatically adds the credit card to Google Pay app.

It's a new process they started this year.

It's very strange... All my info was typed in a very different way.
[Magisk] Cedoresti:
where find the module GPay-SQLite-Fix-master.zip ? thank
[Magisk] pndwal:
You don't want this as explained last page post #827 [edited error].

You want GPay.SQLite.Fix.zip etc.

Check original post for this. Links right at the end:
[Magisk] Cedoresti:
NO! I WANT THIS module GPay-SQLite-Fix-master.zip.

---------- Post added at 08:58 PM ---------- Previous post was at 08:54 PM ----------

second question its, what its different: give root edxposed or not. edxposed work if have root or dont have root.
[Magisk] adriantc_ro:
Hello everybody,

I have a Xiaomi Mi 9T Pro with the latest Magisk and EdXposed installed. SafetyNet is all green, Magisk Hide all setup, Google Play Services blacklisted in EdXposed, but for some reason I cannot add my cards. I do have to say I am in a country unspported by Google Pay (Romania), but the cards are (they have UK BIN). I have also tried setting up the payments profile on an UK address and (thru VPN to UK) register the card. Still no luck.

I have also tried the exact sets of installing the SQLlite module, followed after restart by the GPay fix v1.9, but without succes.

The really weird thing is that the bank gets contacted (as I can see the authorization hold), but then I get the error.

Do you have any ideas on what else I could try?
[Magisk] Didgeridoohan:
You sure? That's just the downloaded GitHub repository for the module and you won't be able to install it without doing some extra work (unzip, move the files and directories to their proper location, re-zip). As you saw in the post you first quoted, that user wasn't able to install the downloaded zip...

The post [MENTION=7550078]pndwal[/MENTION] directed you to contains the actual module zip (that will be exactly the same as the one you're talking about here, apart from the fact that it will install).
[Magisk] franky_z:
Maybe delete data of Gpay, Playstore and Play Services and reboot. Also in Playstore settings at the bottom device must be certified.
[Magisk] adriantc_ro:
I forgot to mention I was certified in Play Store and still am. I have tried your suggestion and although it still does not work, the message changed. It now seems it can detect the root although everything seems green, everything is hidden correctly in Magisk and EdXposed.
[Magisk] 73sydney:
What youre doing is what happens when people do not read more than the last page of a thread, because if you went back just one page...

This: https://xdaforums.com/showpost.php?p=81474753&postcount=829

I just updated the info after the person youve been quoting tried to download the repo master.zip, which WILL NOT install a working module, i thought it was obvious when labelling the download links repo and release, but perhaps wasnt translating for everyone, hence my update to spell it out

My original post, with download links (you want the release ones) is here

fyi: Top tip for XDA forums, read the first and at least the last 5 pages of any thread...
[Magisk] franky_z:
One more suggestion would be using the magisk module "safetypatch".But since I updatet Magisk to newest, I had problems too. Maybe it has something to do with newest Magisk. Playstore message shows either nothing or device is not certified.
[Magisk] adriantc_ro:
Tried that too... it didn't work. However I do have one question: what SQLlite module do you use? (I have a Xiaomi Mi 9T Pro with Snapdragon 855 so arm-v7 isn’t good for me)
[Magisk] franky_z:
I have the same phone with EvolutionX and used the SQLite that you find in the magisk download section. This and the instructions here in the first post worked for me before https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
[Magisk] pndwal:
The very link I provided replete with directions to links at end of post and to [MENTION=4247022]dr.terrible[/MENTION]'s explaination... But he is insistent... ? PW.
[Magisk] billyx1:
You are right, if the advanced details of the document is expanded and the flow diagram is checked it looks like the transaction is only approved after an online verification.

BUT one-time-password, validation of a cryptogram, confirm match between token and card number can be done all offline and doesn't mean balance and account existence is checked online.

The document I had read before was https://developers.google.com/pay/transit/additional-information/offline-data-authentication which allows all this done offline with the security issues.

I don't know which of the protocols is usually used.
[Magisk] pndwal:
It is an interesting reference.

However, it is clearly addressing how GPay is able to duplicate functionality already authorised for standard contactless cards by the card network for very specific transactions and terminal types.

The intended purpose, as the title of the article infers, is using "Google Pay for Transit".

The protocol used for such Transit transactions is ODA (Offline Data Authentication - seems a stupid acronym as Online Data Authentication would also be 'ODA' - go figure). There is no suggestion it is allowed at general EFTPOS / payment terminals.

The necessity for ODA makes perfect sense when you consider that waiting for an online transaction to process before unlocking a turnstile would clearly be impractical, the delay being multiplied necessarily by the number of exiting or entering passengers in the queue. ODA allows entry in milliseconds and passengers to proceed quickly.

Of course, this is no less secure than doing the same thing with a card, and it must be authorised by the appropriate parties.

Also, the payment network decides whether to allow ODA specifically for Transit purposes.

There is nothing to imply that ODA is allowed for transactions other than for Transit (read public transport), so it's safe to state that the general requirement for transactions to process is that they are first authenticated / cleared ONLINE (ie. Online Data Authentication) irrespective of whether a card or mobile device is presented.

This was an interesting exception to the rule (diversion), but clearly poses NO security issues not already accepted for standard contactless card transactions, these issues being confined to terminals for Transit entry / exit points (and only involve the cost of a bus / train / tram or ferry fare). PW
[Magisk] Marcopoloy13:
Hey, thanks it really helped me.

Not just with GPay but also with all Google Apps, it all was so slow before.

I just bought a new Pixel 3a and all Google Apps were slow as hell and also GPay didn't worked, even though SafetyNet was green and Device was Certified. But I have to say, I was worried that it doesn't work becouse the prozzes in GPay taks like 20 - 30 Min. But I all goes well. =)
[Magisk] Marcopoloy13:
I was happy too early - after a day I got problems with all Google Apps and Google Play Service.

First the system got crazy slowly again - apps crashing and everything.

Then I could use some apps, it says "It can't be use with this Google Account"

Have therefor restored the Setting to 10, removed Google Play Service updates, clear App cash and data and now it seems to work everything for now - but of course GPay don't work because of this.

That's sad, I love to pay with my Phone, but for now I can't use it. I hope someday someone corms up whit a fix.
[Magisk] sadiku:
Just wondering which phone you use?
[Magisk] Marcopoloy13:
A new pixel 3a with the latest software

Android 10 (QQ1A.200105.002)

Stock system and kernel, just unlock and rooted with magisk 20.3

Thried divrend Google pay service versions.

The latest from apk mirror works with gpay, but the system is slow as hell, apps crashing, apps like Tasker or battery reborn keeps crashing and restarting, so does the notifications appear and diaper reagelly and all 5 second comes up a notification, that I have to update Google Play service, elsway I can't use Google apps, but can't update cuz I have allready the latest installed.

Then I removed the update and installed the latest from play store.

There gpay doesn't work, also some other apps like Google Wifi (it says, the app can't be used with my account.

Now I removed every update of Google Play service, restored the database changes, everything works kinda. Of course gpay doesn't.
[Magisk] AndDiSa:
[MENTION=3338024]Marcopoloy13[/MENTION] Sounds very strange to me, probably the best thing to do is setting up with a factory image from scratch. I am using Google Pay and Magisk on a Pixel 3a without any issues.
[Magisk] pndwal:
If everything is set up right, Playstore GPay should work fine (and show in Playstore). No one here mentions any need to risk sideloaded versions. These modded or older apks may be adding your device's abnormalities, and could even introduce security vulnerability (read malware) to your device.

Regarding why it's not working, didn't you say you already had these problems before before SQLite mod was applied? ("I just bought a new Pixel 3a and all Google Apps were slow as hell and also GPay didn't worked"). You may need to fix problems with GApps or other issues first. You should consider data backup, then clean ROM install incl. GApps.

Also, please see steps that were successful for me at post #764 (4th post page 77)

Including

-checking Google stuff in Magisk Hide.

-activating Magisk modules Busybox for Android NDK and SafetyPatch.

-Using GPay SQLite fix (Full Edition) module after reboot.

-Wiping data / cache in GPay.

Other considerations (Including requirements for those using XPosed): posts #816, 819.

Magisk SQLite Fix main post by [MENTION=9317193]73sydney[/MENTION] has also been updated frequently, so it would also pay to recheck his notes and Installation guide: https://xdaforums.com/showpost.php?p=79643248&postcount=176

Hope something helps! PW
[Magisk] Marcopoloy13:
Thanks for the answer. I tried now to to Flash the latest stock factory image by Google but run there in a problem.

I already wrote a post about it, maybe someone her can help me with it.

https://xdaforums.com/pixel-3a/how-to/flashing-factory-img-t3931197/page4
[Magisk] yurishouse:
Still works on my Galaxy S9+ G965F running Android Q

Thx for the guide again
[Magisk] Lernos:
I have Huawei P20 Lite and the latest stable version of Magisk. I have BusyBox NDK and SafetyPatch modules installed. It's confirmed that both my Magisk and TWRP can install external modules from .zip files. However, whenever I try to install the GPay SQLite Fix, it says "Unable to extract zip file! Installation failed!" PLEASE HELP, I've spent hours searching for the answer and can't seem to find any, it's driving me crazy.
[Magisk] wabmorgan:
January update

If this recently stopped working you might want to try the SafetyPatch module.

I installed the safety patch module and gpay returned to normal.
[Magisk] nnjimmy59:
I just installed SafetyPatch also and cleared cache in GPay and Google Framework and now it's telling me it's ready to use. Will try it tomorrow.
[Magisk] pndwal:
You're not trying to flash GPay-SQLite-Fix-master.zip or a later zip listed as 'source' are you? These won't work! You need to select a 'release' zip file (Nb. Slightly larger size, and no 'v' in source files). PW
[Magisk] Lernos:
Nah, I'm flashing GPay.SQLite.Fix.v1.9.zip. Also tried 1.8 and 1.7 just for good measure, same result.
[Magisk] pndwal:
Interesting. Is that full (recommended) fix?

Is size 8529 bytes?

Are you able so see /extract contents manually?

Are you flashing it from 'download' folder?

If yes, yes, yes, yes, I'm stumped! :( PW

Edit: Does error message go something like:

...unzip: invalid option -- j usage: unzip [-d DIR] [-lnopqv] ZIP [FILE...] [-x FILE...] ! Unable to extract zip file! ! Installation failed

Seems others are having similar problems (with busybox unzip -j switch compatibility), especially with 64 bit Q. Not sure it's your problem, but check the following:

https://github.com/topjohnwu/Magisk/issues/1858

https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901/page327 (&328)

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3605 post #36041

Seems reinstalling Magisk environment and busybox should fix at least for a while... PW
[Magisk] Lernos:
Unfortunately, it's yes to all of that. If by download folder you mean storage/emulated/0/Download, which I have, by the way, flashed other modules from, and it's the same folder Magisk downloads zips from the official repo. Is there really no hope for me? :( Also, couldn't this module be added to the official Magisk repo? Or does it violate the rules?

EDIT: Don't mind the file being located at my external SD at the moment, I just put it there to try flashing from TWRP. It was still a big fat nope.
[Magisk] pndwal:
[MENTION=9477225]Lernos[/MENTION]

Bit more info that may help. Check under 'Edit:' in my post above.

Also, most Magisk modules will not flash in TWRP, although some are designed for compatibility with both. PW
[Magisk] Lernos:
Hey, thanks a lot! So, for anyone wondering, that's what I did: I went to TWRP and flashed/installed Magisk-uninstaller-20200110.zip (you may wish to find one for your current version). This uninstalled Magisk from my phone. Then I wiped Cache&Dalvik (in my TWRP it's an option available right after flashing any zip) and rebooted to system. After the phone booted and I saw there was no Magisk, I immediately rebooted back into TWRP and flashed the newest stable version of Magisk, Magisk-v20.3.zip. Wiped Cache&Dalvik again and rebooted. Then I went to Magisk and added Busybox NDK, SafetyPatch, SQLite binary and other modules I use from the repo. I rebooted again to get them to install, and then I manually added the GPay SQLite Fix zip and it worked! Will test now if it actually fixes Google Pay for me, though. Thanks again :)

EDIT: Well, it seems to be working! Although I have to say, when I first rebooted after installing the GPay SQLite Fix, it brought me to a boot loop. However, here's another useful trick for all of you out there, maybe it'll work for you. It certainly helps me out with my Huawei P20 Lite and my wife's Honor 7x. So, Huawei devices have two recoveries - the regular recovery and the "erecovery". My TWRP is installed to erecovery. Whenever I am in a bootloop, I am usually still able to enter "erecovery" which loads TWRP. From there, I choose "Reboot" and pick "Recovery". It now brings me to the stock Recovery, where I pick "Reboot to system now" and the boot loop is over.
[Magisk] pndwal:
Glad it worked. Great result!

Just for clarity, did your original error message from Magisk Manager include "...unzip: invalid option -- j..."? (The one in image you posted didn't, but may have been from TWRP).

Also, please let us know if this reoccurs. [MENTION=8010004]guest4711[/MENTION] & [MENTION=5826679]gudenau[/MENTION] both indicated that unfortunately this may be a temporary fix (workaround) as "It seems like the BusyBox install regularly breaks itself. Can't figure out what the trigger is" on some devices. I'm not sure if this has been fully resolved.

Thanks for reporting back and for extra tips too! PW
[Magisk] Lernos:
No, the image I posted was in fact from Magisk, and that's the whole of it.
[Magisk] guest4711:
On the devices having the problem with busybox I put a script called service.sh into a module folder, e.g. /data/adb/modules/99busybox

The main contents of the script reads:

BB='/sbin/.magisk/busybox' ;
rm -rf ${BB} ;
mkdir ${BB} ;
cd ${BB} ;
cp /data/adb/magisk/busybox ./ ;
chmod +x ./busybox ;
./busybox --install ./ ;

I did not test whether it's needed anymore. But I have not had any problems with busybox after creating and activating the script.
[Magisk] sirucato:
Hello, I have a SM-G965FD (Galaxy S9+). Can I do this to use Google pay? Or I need to do something extra. Thanks

Installation:

Install an SQLite binary

Reboot if the SQLite you've just added is supplied by a magisk module (via magisk manager), so its active, as its required for GPay SQLite Fix install script.

Install Gpay SQLite Fix magisk module via magisk manager

At end of GPay SQLite Fix magisk module install, exit magisk manager

Add card to Google Pay

Reboot for gpay.sh service script to do its thing
[Magisk] 73sydney:
Not necessary to quote the entire original post :)

I dont have a Galaxy S9+ so how can i tell you with 100% surety it will work, each device let alone each model can have a different outcome due to factors i cant control...

Any issues i currently have brought to my attention are noted under the Known Issue section....

That being said i dont see why it wouldnt work, and with anything posted by others the best thing to do is try it and see, it cant harm your device in any way, if it doesnt work then post with any info you have and we'll try and help, but i cant preemptively tell you its going to work 100%...
[Magisk] sirucato:
Thanks for your reply [MENTION=9317193]73sydney[/MENTION]

I did not realize i quoted the entire post, sorry!

Ok, if it can not harm the device great, it was my concern as I did not understand the changes the fix do.

I have titanium backup so I will install the fix directly .

Thanks
[Magisk] 73sydney:
Cool, its normal when new here to quote a long post or two until someone intervenes..happens to all of us :)

Yes, with Titanium Backup you have one less step!

Let me know how you go
[Magisk] drup88:
Did anyone's loyalty card suddenly get removed when trying the above? I had about 40 loyalty card, all gone! [emoji174]
[Magisk] nnjimmy59:
Safety Patch causes bootloop. On a LG V30 vs996
[Magisk] pndwal:
SafetyPatch is the most simple fix (for safetynetcheck CTS on many custom ROMs and Chinese stock uncertified ROMs that fail this check) but it uses a Huawei fingerprint to pass.

Could be LG doesn't like this if you're sure this module is the problem.

Have you tried MagiskHideProps config (Magisk repo also) with fingerprint of your choice? (I'd try an LG model, or even your model if there is one, but if there is one for your specific device you should only be needing one of these modules if your custom ROM isn't handling CTS properly). PW
[Magisk] sirucato:
It was perfect. Sample. I install the fix, I restart and I could add the cards. Today I use it. Working great!

THANKS a lot. How is possible you do not have your own thread with this fix.

Thanks
[Magisk] nnjimmy59:
[MENTION=7550078]pndwal[/MENTION]

My phone passes Safety Net check, but cannot use GPay. I'll try the module you mentioned.

Thanks.
[Magisk] pndwal:
If you're already fully passing CTS and device shows Certified in Playstore settings, you shouldn't need these modules and it's doubtful they will help. Probably some other problem. PW
[Magisk] 73sydney:
Hi, Im sorry to hear that youve had problems. I have never used loyalty cards, and after 4,500 downloads, issues with loyalty cards have never been mentioned before that im aware (but its a long thread), but ive never received a PM or email about it

But the module does clear the cache and storage of Google Pay as part of its setup and perhaps? this removes the loyalty cards

As ive said, ive never used anything but my banks VISA card with GPay

Sadly as i said, ive never used loyalty cards, or received a report from anyone until now about loyalty cards, and i have none i could use to test.

What i will do:

Immediately:

Add a warning about the possibility of loss of loyalty or other cards in the Passes section of Google Pay if you choose to flash the module

As soon as possible (in the next few days):

Switch to the extended magisk module template from [MENTION=6037748]Zackptg5[/MENTION] (which i was going to do anyways for some other modules as well, just been time poor) which will allow me to use the volume key selector, which i will use to allow people to choose whether they want to clear the cache and storage of Google Pay during install. The clear cache and data command was there as some people had success without clearing the cache and data and some did not.

I know thats no comfort in your situation, but its the best i can do going forwards
[Magisk] pndwal:
Good call! Perhaps clearing cache only could remain default.

FWIW, one user reported problems using SQLite fix with loyalty cards: https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950/post80550819 PW