yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
I'll have a look at it

Ahh, nice catch...there used to be 3 versions of the script, including one that just changed permissions on the database file and didnt run the SQLite commands....over time i took down the others and concentrated on one version

Looks like when i was cleaning up my drive the other day, im in the middle of my yearly clean up and format and clean install Windows thing, i must have consolidated the scripts and overwritten the one that has that variable set....and uploaded it to make sure it was the latest...oops

Fixed now...its (again) set at top of script, so the adventurous *could* still turn running the SQLite commands off

Looks like ive gotten away with it for a week or so as as pwndal noted for whatever reason he (and others) have been getting by without needing the fix recently. But im glad its fixed :)

Thanks for bringing this to my attention, big fan of your work, used your stuff many times over the years
[Magisk] osm0sis:
Ah good, I'm not crazy! 😛

My thought is that I just tripped some deeper bootloader check in GMS earlier on before I rooted and despite MagiskHide and Play Store wipe getting me passing and certified the only way to clean out the old check was the SQLite hack.

Now that it's working I've removed the module, set up GPay the rest of the way, got all my loyalty cards, etc. back and all is still working, so fingers crossed it'll stay that way. 🤞
[Magisk] 73sydney:
Just be aware that the uninstall script, in trying to be 100% reversible to the service script, resets the permissions on the database file so it can be edited again. So you *may* want to manually set the permissions to 440.

i.e. the module wasnt meant to be uninstalled after install

Also be very aware that flashing the module with loyalty cards present can lead to loyalty cards being purged (theres a warning during module install)
[Magisk] JeffXT:
Same! Can also confirm on Pixel 3 build 11.0.0 (RQ1A.201205.003.A1, Dec 2020, Verizon), Magisk v21. Although I'm cautiously optimistic, because I have a feeling we're on borrowed time until Google finally rolls out hardware backed attestation and it will be impossible to workaround.
[Magisk] 73sydney:
Youve just jinxed everyone..... :)
[Magisk] shaunoleary:
Hello,

Just wanted to say THANK YOU - this worked like a treat just tonight!

I have a Pixel 3 (blueline) running LineageOS 17.1. I did a wipe and clean install, and followed the steps in the OP.

To get SafetyNet to pass, I used the Force SafetyNet option in Props, and also reset a fingerprint (in Props). For some reason, Props sees my Pixel 3 as a Nexus 5 (odd, as my old phone was a Nexus 5 - and much loved, may it rest in peace :)). And lo and behold - SafetyNet passed!

Then I installed the GPay Fix module, and (with bated breath) tried to add my card to Google Pay. And it worked first try!

I have yet to test it by making a payment, hopefully do that tomorrow, but otherwise - this is the first and only solution I have tried that worked. Google Pay working for the first time in months.

Thanks again :cool:
[Magisk] angiotell:
Could you send me Gpay fix please?
[Magisk] State.of.mind:
It's a magisk module. You can find it here.

GitHub - stylemessiah/GPay-SQLite-Fix: A magisk module that ONCE allowed Google Pay to work on rooted phones

A magisk module that ONCE allowed Google Pay to work on rooted phones - GitHub - stylemessiah/GPay-SQLite-Fix: A magisk module that ONCE allowed Google Pay to work on rooted phones

github.com
[Magisk] 73sydney:
I need to do some updating of my modules documentation to encompass this new module for fixing hardware and hardware (masked as basic) attestation

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/

Im just working on figuring out how to word it and fit it into my current instructions for the GPay Sqlite Module

It can be used in conjunction with Magisk Hide Props Config, to pass basic attestation with "a valid combination of device and model names, build fingerprints, and security patch levels "

Note this modules innards is now starting be incorporated directly into some ROMs (already a few for my Pixel 2/XL) and may be incorporated in more as time goes on.

Hopefully will have the documentation updated on the weekend
[Magisk] osm0sis:
Had to do this again yesterday after wiping my device and booting up without MagiskHide enabled briefly (since that's the default now 🙄), so they're not being super lenient on everyone.

Had to FC+wipe Play Store and Google Play Services, then FC+wipe Google Pay and manually ran the sqlite3 command to get it working again. 🤷‍♂️

@73sydney please remember to update your module with the fix we discussed here: https://xdaforums.com/t/working-mag...-17-1-22-on-pie.3929950/page-55#post-84138189 (y)
[Magisk] 73sydney:
I did fix that the day you pointed it out

service.sh:

# set script to run SQL commands
runsql=1

I did not make a new release just for that fix, so you may need to download the zip again

Releases · stylemessiah/GPay-SQLite-Fix

A magisk module that ONCE allowed Google Pay to work on rooted phones - stylemessiah/GPay-SQLite-Fix

github.com
[Magisk] osm0sis:
Ah, yup, I was looking at the commits and release dates. (y)

Thanks!
[Magisk] 73sydney:
Sorry, i got lazy at GitHub and just removed and replaced the zip

My bad
[Magisk] stangn99:
Can someone help me out here (Pixel 3xl, Android 11)?

I've got Termux with SQLite3 binary copied in /files of Termux.

I installed them magisk module by @73sydney (thank you).

I get no errors during install.

I can setup my cards in Gpay, but I get a "/" through the wireless icon and it reads "Not set up".

Am I missing something? I used the manual method noted on the first post on Android 10 without issues.
[Magisk] osm0sis:
You need to wipe data on Play Services and Play Store first.
[Magisk] stangn99:
I've done this, but still fails with the following:

This is what i've done:

clear data on Play Services

clear data on Play Store

run Magisk module, press volume up, completes successfully

close Magisk and open GPay

Add card (adds just fine)

It says "not set up" above the card
[Magisk] osm0sis:
That was the problem I had, but force closing and clearing all of Play Services data was the key. I have Google Pay and default Play Services items in MagiskHide and ran the sqlite3 command manually instead of the module. Otherwise I followed the directions on @73sydney's Page 9 module post to make sure I had Play Store showing Certified and SafetyNet passing and everything first.
[Magisk] stangn99:
Finally got it working.

Did a full wipe

Rooted with Magisk Canary

Used MagiskHide Props Config module AND Unversal SafetyNet Fix (didn't work without it)

edited the dg.db file with SQL editor, chmod' to 440

Reboot.

Thanks for the help
[Magisk] lukjod:
Great, got it to work on dub5 samsung s20 ultra latest ui3.1 A11

Thx
[Magisk] 73sydney:
Updates to Gpay SQLite Fix Module

First up documentation ....

Added the advice to try Universal SafetyNet Fix by @kdrag0n if failing CTS with hardware, instead of the previous advice to force basic via MagiskHide Props Config. It still may be necessary to install a fingerprint via MagiskHide Props config in addition to this.

Adjusted the pre installation steps to reflect this change from using MagiskHide Props Config to force basic to using Universal SafetyNet Fix, hopefully it makes sense. Im sure @pndwal will let me know if it doesn't :)

Module update

v2.3 - 20/12/2020

Changes to service.sh:

setting variable runsql=1, as noted by @osm0sis it was missing and script expected it to be set

I had fixed this and just reuploaded the v2.2 zip file, lazy at the time i didnt increment the version or document it here or on github. Fixed now. As noted, this fix has been in effect since the 20th December last year. Apologies for my laziness in updating the thread/github
[Magisk] heathrow1:
Hi, thank you so much for your effort. Works great on my Xiaomi redmi note 9 pro.

I have a question regarding the installation of OTA updates:

When a new OTA update is available I have to restore images in magisk, apply the update, create a new patched boot.img in magisk and flash it to have root with magisk again.

After this is done, the play store certification is gone. I then have to delete data and cache of play store and play services and reboot.

Afterwards the play store certification is back but all cards in Google pay are gone and I have to add them again.

Is there any better way to apply OTA updates?

Best regards from Germany!
[Magisk] shaunoleary:
Hello all,

As we speak, my Pixel 3 (Blueline, running LineageOS 17.1) is still working perfectly with the GPay fix I applied; EFTPOS payments can be made no problem at all using my phone.

I have a likely stupid question, and apologise in advance, but would like to get the skinny on this before I proceed.

Is it safe to do an upgrade of LineageOS - either by downloading and "dirty" flashing through ADB, or by doing an OTA upgrade directly on the phone? I ask because it is currently difficult (if not impossible) to complete a NANDROID backup on my phone, as running recoveries such as TWRP are very tricky.

Or for that matter, if upgrading the GPay patches themselves (and/or the ROM) may mean screwing up my GPay install.

I'd hate to potentially lose my working GPay install, and have to start from scratch.

Thanks in advance, and once again I apologise if this is a dumb or annoying question.
[Magisk] 73sydney:
Updating via dirty update within the same ROM is almost always fine, least it has been for me when i used the module myself (not currently using as i changed banks and they dont do GPay) and dirty flashed. Though i often clean flashed ROMs as i didnt have any loyalty cards etc that might make some people worry about losing the points etc. and only was adding one card, stored in Google Pay

I assume OTA works if you have a method for maintaining/reinstalling magisk across the OTA update, and you dont have to wipe Google Pay Store data (this will remove cards), ive never done an OTA update of any ROM while using the module, so i can only go on what others report

I run a Pixel 2XL and yes, full nandroid backups are impossible these days via TWRP

Google Pay updates are fine to do, well so far, theres always a chance that they will nix the workaround, but it hasnt happened yet via Google Pay updates, and will probably happen via another package/method other than this
[Magisk] 73sydney:
Theres no way i know around having to clear Google Pay data IF it becomes not certified.

Thats why even in the module installer theres a warning that clearing the Google Pay data

may remove loyalty cards, and that if you fail to do this the module may not work.

As i just posted last post, ive never done an OTA update on a phone when ive used the module

If someone else has an idea, im open to hearing it too :)
[Magisk] shaunoleary:
Hey - just letting everyone know upgrading via ADB to latest LineageOS (17.1) worked fine on my Pixel 3. :) However, there were one or two little hurdles, so thought I'd just share my process/experience in the hope it helps others in the same boat.

What I did was:

Download the LineageOS update onto my PC (duh)

Boot phone into LineageOS Recovery (adb reboot recovery)

In Recovery, go to Advanced/enable ADB (PRO TIP: this is important, I was trying to figure out for ages why my device was unauthorised for ADB in recovery :unsure:)

On my PC: adb sideload lineage-xxxx.zip.

Reboot phone - phone goes into bootloop!! o_O

adb reboot recovery - again, on the PC. I don't recall at this point that I actually did anything in Recovery, I was going to try a clear cache or something, but this is not available in LineageOS recovery. I'll try another upgrade soon and report back what exactly I did - I'm really sorry I can be more specific right now.

Reboot again, and hold breath ...

Phone rebooted back to running LineageOS system, confirmed still had root with Magisk, and GPay is still happy!

I hope this helps someone!
[Magisk] banzighug:
Hi all,

Long time lurker first time registration! I have a Sony Xperia XZ2 Compact (Dual Sim) and have loaded LOS 17.1 successfully. Had the same issue as everyone else and GPay wasn't working.

1) Sideloaded Magisk

2) added all the modules

3) changed the fingerprint (I chose Pixel 4a, but they all seem to work)

4) Passed SafetyNet

etc

Got GPay working fine for the last day, and then this morning I got the dreaded "Not set up" messaging.

I decided to go ahead and try it in a store anyway and it worked!? I have no idea why or how. But I thought I'd share my experience so that maybe some people can try to replicate it?
[Magisk] Sh0X31:
Anyone with Pixel 5 who bypass
[Magisk] AndDiSa:
Hi all,

just as an information to who is running into a similar situation:

I had this module running for quite a while on my Pixel 3a. Yesterday I updated to the 2021-04 version ... suddenly GPay noticed "your device is no longer certified" ... :-(

So I made the database dg.db writeable again, flashed Magisk and the SafetyNet-Fix module, cleaned data for Play-Services and Play-Store ... and after that I was able to use GPay normally without applying any additional patch or module. I only had to re-register my cards.
[Magisk] 73sydney:
Just a heads up that im not even using my own module these days as its working without much fiddling - others have experienced the same thing for a few months

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

I recommend people try this before trying the module these days
[Magisk] xunholyx:
I'm using G Pay right now with Android 12 on my Pixel 5, and I'm failing SafteyNet lol
[Magisk] 73sydney:
Well since most normal folks are not using 12, and i havent tested on it...

All i can suggest is trying the previous pre module checklist instructions - Universal Safetynet Fix/Magiskhide Props Config - Fingerprints to try and pass safetynet, then try without the module...

Otherwise bleeding edger, youre on your own :)
[Magisk] xunholyx:
I think you misunderstood, I'm able to use Google Pay without modules and without passing Saftynet. I don't understand how I'm able to use it, but I am.
[Magisk] 73sydney:
ahh, okay...

i pray that the ban hammer does not come down upon thee anytime soonsih :)
[Magisk] 73sydney:
In other news, theres a new Google Pay app rolling out, in what looks to be a staged rollout

I was made aware by a user in the other GPay thread - post here: https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-84832123:

And though i was able to install it, it wouldnt let me run it, because i wasnt in one of the 3 countries its valid in: India, Singapore or USA

That user was worried about whether his cards, and most importantly loyalty cards would migrate or whether he would have to readd the cards for new app and possibly wipe data

I guess we will find out when someone in one of those 3 countries decides to be a guinea pig :)
[Magisk] osm0sis:
Pretty much all of GPay is handled by Google Play services now and the app is just a front end. Should be fine I think.
[Magisk] 73sydney:
Well thats my theory too, but theres a few nervous folks, im guessing theyre waiting for someone else to be a guinea pig

I tried, to try and short cut things, but it wont let me (geo blocked)
[Magisk] CSX321:
I was the one who asked, but I just decided to be the guinea pig. :D I updated to the new app and had no issues. I posted in the other thread with more details.
[Magisk] 73sydney:
thanked in other post :)
[Magisk] shaunoleary:
Hey all,

Just wanted to confirm this seems to be working on my Pixel 3 (blueline), running LineageOS 18.1 (Android 11) and Magisk 22104.

My steps to install (slightly modified from post on page 9; I've added step 1 to install Safetynet Fix, and step 3 regarding MagiskHide entries)):

Install Magisk module Safetynet Fix from here (currently running version 1.1.1 at time of writing).

Open Magisk Manager and enable MagiskHide (Settings -> toggle MagiskHide on).

Go to MagiskHide screen (tap shield on menubar at bottom of sceen, then tap MagiskHide at top of screen). Scroll to Google Play Services, and tap on it. turn on ALL the switches to hide all parts of Google Play Services.

Toggle Airplane mode on.

Clear data for Google Play Store and Google Play Service (Settings > All Apps (toggle Show System) the search for and clear data for these packages).

Reboot.

Toggle Airplane mode off.

Check Google Play Store is certified (Google Play -> Settings, scroll to bottom).

Open Magisk Manager - check Safetynet passes (If not try steps under Pre Installation Checks).

Add card and test.

I have yet to actually test this by making a payment, will do this tomorrow. Google Pay seems to be happy, and the power button menu brings up my card with the text "Hold to reader", so at this point all seems to be working. Will find out tomorrow when I take my wife out to lunch for her birthday :))) and see if I can pay for lunch using my phone.

EDIT: Just successfully paid with my phone in shop!
[Magisk] luce111:
I can confirm. SafetyNet Pass, Airplane mode on, clears Google Play Store and Google Play Services data. Reboot, exit Airplane mode and Google Pay works great. I'm on OnePlus 8T and LineageOS 18.1.
[Magisk] jaccydan:
I'm not sure how to find this setting:

Samsung s20 Ultra SM-G9880 Snapdragon. I am confirmed rooted in root checker. I have Magisk installed.

Getting that G-Pay message that "Can't set up payment card because phone is altered or rooted"

I have hidden G-Pay and all Google play services in Magisk.

I am using a re-flashed stock ROM, not a custom ROM, because I reversed a failed custom ROM attempt/bricked/bootloop situation. Phone is working fine except for this issue.

Any ideas how I can get G-Pay to work?

Thanks.
[Magisk] 73sydney:
For many people the requirement to fiddle with the database hasnt been needed in months, i dont even use my own module (which does the same thing) and havent for many months

I also do not have Google Pay hidden in MagiskHide....

Go back a page and try the basics: https://xdaforums.com/t/working-mag...s-of-gms-17-1-22-on-pie.3929950/post-84654929
[Magisk] jaccydan:
I now have this error message in G-Pay after I try adding payment card:

Going to try the methods set out in this feature below, because it seems to be down to whether Safety Net passes or not, and atm mine is failing:

How to Pass Magisk SafetyNet on Rooted Android 11

In this tutorial, we will show you how to pass the Magisk SafetyNet test on your rooted Android 11 device with Hardware attestation type.

www.droidwin.com
[Magisk] 73sydney:
Seen other people have this in the past, and had this myself a few weeks ago

It can happen randomly, especially if like me youre adding your card over and over as youre testing ROM's (which i do a lot)...i had to contact Google Pay and get them to fix it...48 hour turn around

This be the link i think: https://support.google.com/pay/answer/9080767?hl=en

Click Contact Us on the lower section of page

Gentle mention that if you had searched the thread it was already covered here: https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-80895607

Search is there for things like this :)

p.s. Did you also go back and check the basics link i referred to last post...wont solve you current problem, but you still need to check it out
[Magisk] jaccydan:
Ok thanks for the info @73sydney - most helpful. I will send the error to Google Support and see what they say.

I was under the impression that it's a phone issue?
[Magisk] jaccydan:
I am looking for expert advice from someone who has done this before..

I'm confused. I have Magisk on my phone. I simply wish to 'upgrade' to the latest Canary Build.

I saw this guide:

How to Update Magisk ZIP and Magisk App (without TWRP)

In this detailed tutorial, we will show you the steps to update the Magisk ZIP and Magisk Manager without using TWRP Recovery.

www.droidwin.com

It says Pre-Requisite is to download the latest Magisk Manager APK and Magisk Installer ZIP. Do I swap those out for the lastest downloaded Canary files? Or do I choose 'beta' in the 'Update Channel' in order to install (beta) Canary build?:

And where do I put the latest Magisk Manager APK and Magisk Installer ZIP on my phone? - (I normally stick my 'flash files' on my SD card).

Btw, I don't fancy uninstalling my current Magisk and re-flashing Canary ZIP within Odin.

(Just to let you guys know - my Hide Magisk Manager option is greyed out for some reason which isn't going to help with me trying to pass cts SafetyNet- Hardware attestation in order for G-Pay to work):

​

Thanks in advance..
[Magisk] 73sydney:
You would have more luck asking in the topic where this is more appropriate, which is Magisk General Support/Discussion

Ive never swapped channels, so cant help you on this one.

Also just be aware that theres no new Magisk builds being made on the official repos, canary or otherwise as the original developer has ceased developing Magisk since he left to join Google

Some of us have moved to the Alpha builds from vvb2060, which is possibly more recent, and has more cutting edge commits, and which is located here: https://github.com/vvb2060/magisk_files/tree/alpha the file at that location if you wish to go this route is app-release.apk

But your question is best handled in the General thread....

You might want to mention your brand/model of device as well...and whether your bootloader is unlocked etc...basic info
[Magisk] osm0sis:
Incorrect. He simply hasn't resumed development yet since joining Google. 😉
[Magisk] 73sydney:
Haha, the pedant in me would say that my statement is still technically correct sir :)
[Magisk] jaccydan:
@73sydney Have you got out the bed the wrong side? What's with all the attitude? i am leading on from my original post on this thread so it is organic - I don't think I'm on the wrong thread - this is G-Pay related and not going on about the weather!

I have already mentioned my setup if you'd actually care to look further up the thread. I will re-post it for you:

"Samsung s20 Ultra SM-G9880 Snapdragon. I am confirmed rooted in root checker. I have Magisk installed.."

My bootloader is therefore obviously unlocked.

I am not interested in Alpha builds from vvb2060 - i am only interested in what I am trying to do with Magisk which is still available. I am only looking for constructive answers to my question, not clever chastisement.

(If people can't help why do they feel the need to say anything?! - Haven't they got anything else to do with their time?) :rolleyes:

@73sydney Stop throwing out misinformation; trying to be clever; and taking the piss!
[Magisk] osm0sis:
Your word choice of "ceased" carried a certain finality to its connotation, so I'm sure you understand my want to reassure. 😛
[Magisk] 73sydney:
Please, lose your attitude, i didnt have any. Youre the only one who seems to have gotten out of the "wrong side of bed". I correctly pointed you to the Magisk main thread, because your question is exactly better dealt with there, and off topic here...

Your question is about changing Magisk channels, not Google Pay, hence off topic here

None of what i said was misinformation....

I do not appreciate personal attacks for doing the correct thing, thank you

The bolding of words is also completely unnecessary, and aggressive

Any further aggression will be reported
[Magisk] 73sydney:
Lol, im still waiting for the feature you sponsored of mine (to remain on installation tab after install) to appear :)