Working: Magisk with Google Pay as of gms 17.1.22 on Pie

Search This thread

hammondegs

Senior Member
Oct 9, 2016
59
12
18
Melbourne
How to work with/in Macrodroid ?

May you explain it more?
Remove the xml markup and configure your macro like attached images.
You can use whatever trigger you like but I am testing when the relevant apps are updated.
 

Attachments

  • Screenshot_20190517-182113.png
    Screenshot_20190517-182113.png
    185 KB · Views: 1,211
  • Screenshot_20190517-182418.png
    Screenshot_20190517-182418.png
    227.3 KB · Views: 1,213

marshedpotato

Senior Member
Jul 15, 2014
87
41
0
South East UK
Working for me too. Thanks for the well written easy to follow instructions.

I wish I had a better understanding of what I am doing here and any potential side effects, so if anyone discover anything please share it here. But for now I am happy enough that it is working and I have a backup from before.
 

bnwg

Senior Member
Sep 2, 2010
425
62
48
Here is the description and XML for import to Tasker:
(I use the TitaniumBackup's sqlite3 binary as suggested by @ Karpfenhai, you could edit it if you use other sqlite3)

GPay (326)
A1: Run Shell [ Command:chmod 777 /data/data/com.google.android.gms/databases/dg.db
/data/data/com.keramidas.TitaniumBackup/files/sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
chmod 444 /data/data/com.google.android.gms/databases/dg.db Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In:%DebugMsg Store Result In: ]

Just wondering...whether we need to chmod 777 instead of chmod 660 as the orginal dg.db having permission of 660
 

jcmm11

Recognized Contributor
Feb 10, 2012
3,572
3,585
263
Just wondering...whether we need to chmod 777 instead of chmod 660 as the orginal dg.db having permission of 660
660 (and 440) are more correct. 7 (or any odd number up to 7) gives execute permission, which a db file definitely doesn't need.
 
  • Like
Reactions: Tr4sHCr4fT

lssong99

Senior Member
Jul 15, 2005
349
196
63
Just wondering...whether we need to chmod 777 instead of chmod 660 as the orginal dg.db having permission of 660

The 777 is just a quick and dirty way to ensure the sqlite3 binary can access dg.db for maximum compatibility. Anyway it will be chmod to 444 in just a fraction of second. Of course if on your system 660 works then it's okay to use 660.
 

Autistic

New member
May 18, 2019
1
1
0
Hello i have problem, I could have add a credit card to my android pay.
But when Im trying to pay at shop, nothing happens like I wouldnt turn on nfc.
Anyone had same issue?
 
  • Like
Reactions: cineq

Bidalos

Senior Member
Apr 22, 2012
110
38
48
Hello i have problem, I could have add a credit card to my android pay.
But when Im trying to pay at shop, nothing happens like I wouldnt turn on nfc.
Anyone had same issue?

It's called Google Pay now. Make sure to update it, even better uninstall and install it again.
Then In NFC optiond chose HCE Wallet (in secure element position), not Sim Wallet.
 

GryphonBR

Senior Member
May 6, 2011
206
65
0
you guys are able to setup your cards for contactless payment in google pay after setting the file permissions to 440? I can not add any of my Master or Visacards. I get an error message everytime. Only PayPal works.
I just added a MasterCard after following the full method and changing permissions to 440. As an extra piece of info, the card I added had never been present on my GPay account since this bank was only recently added to the list of participating banks.
 

sliding_billy

Senior Member
Apr 23, 2012
1,735
603
143
North Texas
Has anyone installed the latest gpay update ?

Yes, my cards are still intact. Need to try paying to see if it still works.

All the atest database values still say 0 so I'm sure it'll work.

Edit: still works, paid earlier.

I used my Pixel 3XL and my wife's Pixel 3 (both updated to the new GPay yesterday) today at separate stores. No issues with either one. I'm guessing that if there is a failure coming, it will happen with a new GMS version and not GPay.
 

braveheartleo

Member
Jun 18, 2018
41
23
0
Many thanks @BostonDan for this. I was able to track down why my system fails at CTSprofile check, and at the same time make Google Pay work again. ?

Regarding chmod-ing dg.db to prevent overwriting the changed attestation values brought about by future gms updates, perhaps a more permanent solution to this would be to
Code:
chattr +i dg.db
. This makes the file immutable (+i) or non modifiable, even to root. To reverse the change,
Code:
chattr -i dg.db
should do.

EDIT: corrected the switches.
 
Last edited:
  • Like
Reactions: joeynshelby

joeynshelby

Senior Member
Feb 21, 2011
68
15
0
Many thanks @BostonDan for this. I was able to track down why my system fails at CTSprofile check, and at the same time make Google Pay work again. ?

Regarding chmod-ing dg.db to prevent overwriting the changed attestation values brought about by future gms updates, perhaps a more permanent solution to this would be to . This makes the file immutable (-i) or non modifiable, even to root. To reverse the change, should do.

Verified that this does work. However, chattr +i made the file non modifiable and chattr -i allowed modifications. After issuing the chattr +i command in terminal emulator to the dg.db file, it prevented me from making any modifications whatsoever in SQLite editor and also when attempting to chmod777 and use the run shell script in Tasker that was mentioned earlier in the thread. Thanks for this information and thanks to @BostonDan.
 
  • Like
Reactions: braveheartleo

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    @pndwal , all

    Updates to Gpay SQLite Fix Module

    14/03/2021


    Back and able to test again, and able to confirm the experience of some others, who have reported not needing the module recently to have Google Pay working. No one is quite sure why this is, or how long it will last. No one will be more happy than i if we can retire the module. For those wanting to try the minimal non-module method, ive added the steps i took below:
    1. Open Magisk Manager and enable MagiskHide (Settings -> toggle MagiskHide on)
    2. Toggle Airplane mode on
    3. 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)
    4. Reboot
    5. Toggle Airplane mode off
    6. Check Google Play Store is certified (Google Play -> Settings, scroll to bottom)
    7. Open Magisk Manager - check Safetynet passes (If not try steps under Pre Installation Checks)
    8. Add card and test
    If this fails for you, please continue on below for further steps in Pre Installation Checks (in OP: here) to try passing safetynet (adding fingerprints), or to try the module....
    2
    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?
    2
    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.

    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://forum.xda-developers.com/t/...s-of-gms-17-1-22-on-pie.3929950/post-84654929

    I recommend people try this before trying the module these days
  • 241
    Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and then reapply, but this still needs to be confirmed

    Without further ado, here is my process:

    1) download a SQL database editor. I used

    https://play.google.com/store/apps/details?id=com.tomminosoftware.sqliteeditor&hl=en_US

    2) download a terminal emulator program. I used terminus but any terminal emulator should work.

    3) make sure Google pay is forced close, if it is open.

    4) open SQL editor. Navigate to /data/data/com.google.android.gms/databases

    5) open dg.db

    6) change any value that lists "attest" in the name (first column) to 0 in the third column. Mine was showing a value of 10 in the third column for each of these values. (Column c for sqlite database editor I used)

    7) open the terminal emulator.

    8) get root access (su)

    9) cd /data/data/com.google.android.gms/databases

    10) type: chmod 440 dg.db
    This makes dg.db read only (for owner and group, and no access for world.)

    11) reboot

    I have Magisk 19.1 with GMS and Google Pay hidden. Also, I am using a custom kernel but others have reported using a stock kernel with this working.

    I suspect when gms is updated, one will have to go back to steps 10 and 11 and chmod 660 dg.db to allow new keys to be written to the database, and then go back and redo all these steps to reset the attestation values back to 0.

    If there is still an error, verify in sqlite database editor that all attest release keys values in dg.db are 0 when dg.db is read only (owner and group).

    Again, YMMV but this worked for me, so I give it back to the community now.

    Edit: people should know this by now, but GMS updates have not required any reapplication of this process.

    Edit2: After much time, it was determined that all one has to do is apply the chmod 440 to dg.db before launching google pay for the first time after clearing gms data. No need to change any keys in the dg.db file. If it does not work, you may have to clear gms (Google play services) before applying chmod.

    Cheers,
    B.D.
    112
    Magisk Method Gpay SQLite Fix.....

    This post best viewed in a browser - theres lots of formatting which is lost (and the hide tags dont work) when viewed via XDA App/Labs - (thanks to @pndwal for making me aware of this)

    Stats as of 18/8/2020 - 23,000+ downloads....um thats a lot..only once did i wish id charged $0.50 per download

    General Notice:

    14/03/2021


    Back and able to test again, and able to confirm the experience of some others, who have reported not needing the module recently to have Google Pay working. No one is quite sure why this is, or how long it will last. No one will be more happy than i if we can retire the module. For those wanting to try the minimal non-module method, ive added the steps i took below:
    1. Open Magisk Manager and enable MagiskHide (Settings -> toggle MagiskHide on)
    2. Toggle Airplane mode on
    3. 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)
    4. Reboot
    5. Toggle Airplane mode off
    6. Check Google Play Store is certified (Google Play -> Settings, scroll to bottom)
    7. Open Magisk Manager - check Safetynet passes (If not try steps under Pre Installation Checks)
    8. Add card and test
    If this fails for you, please continue on below for further steps in Pre Installation Checks to try passing safetynet (adding fingerprints), or to try the module....

    9/3/2021

    Good news, switched over to a bank which does not only Google Pay, buy Samsung Pay (which is handy as i have had an Active 2 fior a while now and Samsugn Pay is relatively easy to get working on a rooted phone), so i'll soon be back using my own module and be able to better test issues if and when they crop up.

    29/12/2020

    I have had to change cards/banks (due to the previous ones ATM eating my card, and not being able to get money out to eat/pay rent/buy food etc without the card - and my only option to travel into a head office ATM in the centre of COVID every time i need to get money out, no thanks) to my previous bank which doesnt do Google Pay (which is why i moved to the other bank). So for the forseeable future i will NOT be able to test Google Pay payments.

    19/08/2020

    Major update to the installation process, mainly adding a pre-installation checklist....hopefully doing some basic tests (CTS pass/fail and basic/hardware attestation) before trying to install the module. Its high time things were done this way and may head off a lot less posts, with repeating information. So as opposed to people just trying the module and finding out afterwards that they werent passing CTS etc, now people will be encouraged to pass CTS/attestation first, and given the info (hopefully correct and understandable) to troubleshoot/resolve that, before trying my module.

    At time of writing there are two hacks to bypass googles crackdown on rooted devices and make CTS pass (primarily bypassed by setting a valid fingerprint (usually most useful on custom ROMS)), and the other hardware backed attestation, which can be forced to basic. Both workarounds may become invalid at any time by google.

    There are no updates to the module itself at this time, all changes are only for new installs, so if you have the module installed and working, then you are unaffected


    Changelog:

    GPay SQLite Fix:

    v2.4 9/3/2021


    Changes to service.sh:
    • Fixed broken/mangled pipes that left the log file blank - dont ask me why
    If you need logging (only useful if youre having an issue and want to troubleshoot) you can choose to install the new zip, or extract the service.sh from the zip and overwrite the one in /data/adb/modules/73sydney.gpay

    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.

    v2.2 - 28/03/2020

    All changes due to MMT-EX upgrade to v1.5
    • changes to /common/functions.sh
    • /common/addon/Volume-Key-Selector/main.sh changed and renamed to /common/addon/Volume-Key-Selector/install.sh
    Upgrade to this version is not necessary, changes only affect module install...


    SQLite3 Universal Binaries:

    v1.1 - 1/10/2020


    - Added

    mkdir -p $MODPATH/system/xbin

    In response to report from XDA user @djjohnnyblaze that the sqlite binary wasnt getting copied on his device under Android 11

    Recommended especially for those folks who have recently tried installing the Gpay SQLite Fix and find it reports it doesnt find the sqlite binary, that you thought was just installed by the SQLite3 Universal Binaries module!

    Current users can also check if theyre unaffected by checking the contents of the /cache/payfixfirstrun.log file, if the sqlite binary hasnt been found by the module, it will show up here as:

    SQLite3 binary not found, please install a SQLite3 binary, without this the fix *may* not work
    I provide an SQLite3 Universal Binary Magisk Module, and links to SQLite3 binaries for other architectures
    at https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176


    Requirements:

    Magisk:

    Magisk Manager (Canary version)
    is highly desirable, especially for more recent devices. To avoid possible stability issues on some devices, It is recommended, at least for now, that you run stable Magisk (unless on a very recent device where ONLY a Canary version will run, or a Canary version includes a fix for a specific issue that affects you), but use Magisk Manager (Canary version).

    If your magisk install process usually involves installing Magisk Manager, and then install Magisk via it, its suggested that once you install Magisk Manager (Canary version), that you change the Update Channel to Stable (unless on a very recent device, or a canary version includes a fix for a specific issue that affects you):

    From Magisk Manager (Canary version):
    1. Click the settings icon (gear in top right)
    2. Scroll to Manager section
    3. Tap Update Channel, and set to Stable

    An SQLite3 binary:
    • Ive just added an SQLite3 Universal Binaries module to my github and download links below. Also the previous module for arm-v7 chipset only one will remain for now as an option for arm-v7 only devices.
    • Other SQLite3 binary choices for other chipsets *may* be found on Magisk Repo
    • For arm64-v8a (aarch64) users, an SQLite binary is available from the Magisk Repo: SQLite for ARM aarch64 devices
    • For all/other architectures, theres also some provided here (untested by me): https://forum.xda-developers.com/general/general/binary-sqlite3-binary-android-pie-t3721530
    • Other compatible SQLite3 binaries tested and reported working are provided with termux and titanium backup - users of these apps do not require a separate SQLite3 binary....

    And quite (very) possibly one or both of the following...

    MagiskHide Props Config - MagiskHide Props Config allows most devices to take advantage of a hack to bypass googles crackdown on rooted devices. Excellent work by @Didgeridoohan.

    This can potentially "fix" CTS passing - sometimes in conjunction with the Universal SafetyNet Fix below
    • Fingerprint: by spoofing a certified device by adding a valid fingerprint in props (most useful for custom ROMs, or stock ROMs for uncertified devices - Chinese ROMs etc)
    MagiskHide Props Config is available from the official Magisk Repo. The Pre-Installation Checklist below will help you identify if you need to install and configure it.

    Universal SafetyNet Fix - Universal SafetyNet Fix by @kdrag0n is a "universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021. The only requirement is that you can pass basic attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels."

    In short its now the preferred method of enabling users with hardware attestation to pass basic attesation, which MagiskHide Props Config offered before recent Google changes

    Not currently on the repo, but available via github, via link in OP of linked thread.

    Please note: The Uninversal Safetynet Fix is now soemtimes integrated into ROM's, please check your ROM doesnt already include it before installing it.


    Pre Installation Checks (To proactively head off the common reasons the module will fail)

    Check For Identified Conflicting Magisk Modules: (tracked by @pndwal)
    • SafetyPatch
    • FDE.AI
    These modules should be removed prior to trying this module. Failure to remove = no support.


    Check For EdXposed: (Steps/tips courtesy of @kevinwu128, via @pndwal)

    Method:

    In EdXposed Installer

    1. Enable Black/White list in EdXp Settings
    2. Blacklist Google Play Services in Black/White list
    3. Reboot
    4. Check SafetyNet status in Magisk Manager

    In EdXposed Manager

    1. Enable App List Mode in Settings
    2. Blacklist Google Play Services in Application List
    3. Reboot
    4. Check SafetyNet status in Magisk Manager

    If the above fails search the thread with the keyword "edXposed" for further tips


    Check for ctsProfile (pass/fail) and/or evalType (basic/hardware) in Magisk Manager (Canary version):

    Its now recommended to use Magisk Manager (Canary version) for the updated attestation test, which apart from the usual basicIntegrity and ctsProfile tests, it now provides a test showing how the attestation is generated/processed, evalType is either BASIC or Hardware

    Please note that Google could change this at any time and force all devices to use hardware attestation, though its unlikely that they care about your Galaxy S4 that youre stubbornly hanging onto.......

    Method:

    To check open Magisk Manager and tap Check SafetyNet mid way down the opening screen

    Based on the results, choose which path below to follow:

    • Result: ctsProfile of fail and evalType of Basic

      Solution: Install a FingerPrint via MagiskHide Props Config (thanks be to @Didgeridoohan)

      These are the simplified steps, for more info on fingerprints and patch levels read the doc or visit the MagiskHide Props Config thread

      Method To Install A Fingerprint:
      1. Install MagiskHide Props Config (from magisk repo)
      2. Check that MagiskHide is enabled in Magisk Manager:
        • Click the settings icon (gear in top right)
        • Scroll to Magisk section
        • Toggle MagiskHide on
      3. Reboot
      4. Open a terminal and type su (grant permissions when prompted)
      5. Type props
      6. Type 1
      7. Type f
      8. Type the number that matches your devices manufacturer
      9. Type the number that matches your devices model
      10. Type the number that matches your android version
      11. Type y
      12. Type e to exit
    • Test SafetyNet again via Magisk Manager, if all passes continue to Clear Play Store & Play Store Services Data & Check Play Store Certification below

      See here for more info: https://github.com/Magisk-Modules-R...ices-fingerprint-to-pass-the-ctsprofile-check

    • Result: ctsProfile of fail and evalType of Hardware
      • Install Universal SafetyNet Fix (thanks be to @kdrag0n), reboot and test SafetyNet again via Magisk Manager, if all passes continue to Clear Play Store & Play Store Services Data & Check Play Store Certification below, otherwise consider installing a fingerprint via MagiskHide Props Config (thanks be to @Didgeridoohan)
      • Method To Install A Fingerprint:
        1. Install MagiskHide Props Config and reboot
        2. Open a terminal and type su (grant permissions when prompted)
        3. Type props
        4. Type 1
        5. Type f
        6. Type the number that matches your devices manufacturer
        7. Type the number that matches your devices model
        8. Type the number that matches your android version
        9. Type y
        10. Type e to exit

        See here for more info:

        Spoofing fingerprints: https://github.com/Magisk-Modules-R...ices-fingerprint-to-pass-the-ctsprofile-check

      • Test SafetyNet again via Magisk Manager, if all passes continue to GPay SQLite Fix install below

        If the above fails, please post in the MagiskHide Props Config thread for best chance of success, please be aware that the ability to even attempt to trick the system as MagiskHide Props Config currently does may be shutdown by Google at any time


    Clear Play Store & Play Store Services Data & Check Play Store Certification
    • Toggle Airplane Mode on
    • Clear data and cache of:
      • Google Play
      • Google Play Services
    • Usually this will be achieved by (exact steps and terminology may change per device or ROM):
      • Opening Settings
      • Going to Apps, choosing Show All Apps
      • Enabling Show System Apps via a menu option
      • Locating the app, tapping it and then finding Storage/Cache
      • Tapping Clear Data
    • Reboot (Best) and/or Toggle Airplane Mode off
    • Open Google Play Store, go to Settings and check Certification at bottom

    Assuming you pass CTS and evalType tests, and Google Play Store Certification above, its time for the module installation.....


    Module Installation:

    The module has its best possible chance of succeeding if done on a clean flash of your ROM

    1. Install an SQLite binary (see Downloads below)
    2. 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.
    3. Install Gpay SQLite Fix magisk module via magisk manager (see Downloads below)
    4. At end of GPay SQLite Fix magisk module install, exit magisk manager
    5. Add card to Google Pay
    6. Reboot for gpay.sh service script to do its thing

    It *should* be that simple.


    Upgrade process (version v1.6 and above):

    - Uninstall previous version
    - Reboot
    - Install latest

    Upgrade process (versions below 1.6:

    Because the new version no longer uses chattr, for anyone using a verison older than v1.6, you will want to issue the following commands via a terminal to put /data/data/com.google.android.gms/databases/dg.db in its original state before installing the latest version:

    Code:
    su
    chattr -i /data/data/com.google.android.gms/databases/dg.db

    - Uninstall previous version
    - Reboot
    - Install latest


    Uninstall:

    1) Remove via Magisk Manager - all changes except packages hidden via MagiskHide and clearing the cache of Google Pay are reverted
    2) Reboot


    Known Issues:

    Loyalty Cards/Passes: You risk the possibility of loss of loyalty or other cards in the Passes section of Google Pay if you choose to flash the module and clear the cache & storage of Google Pay. Any version from v2.0+ will warn users and allow users to skip the clearing of Google Pay cache and app storage. This will also come with a warning that it *may* make the module fail to do its job.


    Downloads (hosted on my github):


    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....

    Gpay Fixes Downloads:


    repo: https://github.com/stylemessiah/GPay-SQLite-Fix
    release: https://github.com/stylemessiah/GPay-SQLite-Fix/releases/latest

    SQLite3 Binary Downloads:

    Newer & Universal (hopefully):

    SQLite3 Universal Binaries v1.1 (installs to /system/xbin if exists, otherwise /system/bin) here:
    repo: https://github.com/stylemessiah/SQLite3-Universal-Binaries
    release: https://github.com/stylemessiah/SQLite3-Universal-Binaries/releases/latest

    Older and only for arm-v7:

    SQLite3 v4.1 static binary (for arm-v7 devices ONLY and NOT using termux) (installs to /system/xbin if exists, otherwise /system/bin) here:
    repo: https://github.com/stylemessiah/SQLite3-v4.1-arm-v7
    release: https://github.com/stylemessiah/SQLite3-v4.1-arm-v7/releases/latest[/QUOTE]
    52
    [/COLOR]Thanks @BostonDan for this great method! My GPay just works now!

    [Edited to add @Karpfenhai's suggest to use TitaniumBackup's sqlite3 binary]

    Anyway for those sqlite impaired (this means 99.9999% of world population), here is my steps:

    If you have Titanium backup, please start from 3, if not, please start from 1

    1. Install Magisk module "SQLite for ARM aarch64 device" by ianmacd from Magisk Manager
    2. Reboot to enable this module
    3. Install your favorite terminal emulator (I use Termux)
    4. Enter Termux, then type "su" (Magisk might ask you for permission of root access, permit it.)
    5. Enter following command line by line: (This is Magisk module version. Titanium backup version is down below)

    am force-stop /data/data/com.google.android.apps.walletnfcrel
    chmod 777 /data/data/com.google.android.gms/databases/dg.db
    sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
    chmod 444 /data/data/com.google.android.gms/databases/dg.db

    6. Reboot
    7. Profit!

    For using with TitaniumBackup's sqlite3 binary, you could modify the sqlite3 path as
    /data/data/com.keramidas.TitaniumBackup/files/sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"

    Actually I put all those commands in a Tasker task so I could run it during each reboot (with "Monitor Start" Event). Tasker xml as attached.

    Also, if your system come with sqlite3 binary (Actually I use the one from Termux) you don't need even to install the Magisk sqlite3 module.

    I am not responsible for what you have done with your phone, but hey, just let me know if you guys have any issue and I am glad to help!
    16
    Magisk Method Gpay SQLite Fix.....

    v2.2 28/03/2020

    All changes due to MMT-EX upgrade to v1.5

    • changes to /common/functions.sh
    • /common/addon/Volume-Key-Selector/main.sh changed and renamed to /common/addon/Volume-Key-Selector/install.sh
    Upgrade to this version is not necessary, changes only affect module install...

    As always, the module can be found here, or in my sig below
    15
    OMG, after thousands of tries GPay is finally working!

    1. Google Pay, Google Play services, and Google Service Framework hidden in Magisk Hide
    2. Clear Data and Cache for Google Pay app.
    3. /data/data/com.google.android.gms/databases/dg.db permissions set to 440
    4. Run and configure Google Pay.
    5. Voila!

    Hope it's gonna to work for you guys!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone