[Magisk] 73sydney:
Also worth pointing out, apart from the feedback during module install, theres a log file (/cache/payfixfirstrun.log) that logs the failure/success of every command in the service.sh script (where all the real work happens)

The process should be:

1) Preinstall Checks - cant pass CTS/evalType or show Certified in Play Store - try the cache clear during airplane mode trick or MagiskHide Props Config. Don't proceed till this is fixed

2) Module Install

3) Test Payment

The recent OP rewrite was because the way things were going people were often trying to help people fix CTS/evalType problems after module install, and i thought it was more than time to get people into the process of checking CTS/evalType first, mostly for [MENTION=7550078]pndwal[/MENTION] sanity as im sure he was probably reposting the same advice over and over :)

Im only good at trying to fix the Module Install part, because im not Google :)

The best i and others can do is advise things that are already in the extensive original post of mine:

During Pre Install phase if failing CTS/ evalType:

check (and remove is recommended) youre not using Xposed

try clearing cache of google services, play store and reboot

That post was recently updated to try and reduce the amount of posts about the same issues (mostly people

NOT passing CTS/evalType), and reduce the wear and tear on [MENTION=7550078]pndwal[/MENTION] ....

Just for reference, because there seems to be some confusion about what my module actually does (hint: it doesnt cause, or even resolve every problem people report) - it does what the OP of the thread does, just in a scripted fashion:

install.sh

1) Check for sqlite binary in the following paths:

/data/data/com.termux/files/usr/bin/sqlite3

/data/data/com.keramidas.TitaniumBackup/files/sqlite3

/system/bin/sqlite3

/system/xbin/sqlite3

* Feedback if script fails to find sqlite binary

2) Attempts to magiskhide Google Play Services and Google Pay

* Feedback if script fails to magiskhide any element

3) Warning and option to clear cache of Google Pay (warning due to reports it removes loyalty cards)

* Feedback if script fails to clear cache of Google Pay

4) User is advised to add their card now, and then reboot

After reboot....

service.sh:

1) Waits for boot to complete

2) Checks /system/bin/chmod is accessible

3) Checks /data/data/com.google.android.gms/databases/dg.db is accessible

4) Checks sqlite binary is in a path as above - you wouldnt think it would be necessary, but id never bet against one person removing their binary after module install and before the reboot, so the check is there... :)

5) Stops Google Pay

6) Chmods 777 on /data/data/com.google.android.gms/databases/dg.db

7) Runs sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"

8) Chmods 440 on /data/data/com.google.android.gms/databases/dg.db

Thats all the module does, if part of that fails, its feedback is onscreen during install, or after via /cache/payfixfirstrun.log

The xposed tweaks or disabling and cache clearing tips are contributed by others like pndwal and he ends up doing a lot of troubleshooting here, which im always grateful for. And the more tricky stuff used to pass CTS/evalType is mainly handled by using MagiskHide Props Config, which is makign life easy for many people

I appreciate theres always going to be the odd case where theres a curveball and we'd all like to fix that, but i think its important that people have knowledge of what the module actually does.

Android 11 is very new (so new i upgarded to it, and then 2 hours later downgraded because it broke too many things for me personally), as is the Pixel 4.

I can say, and [MENTION=7550078]pndwal[/MENTION] can back me up here that a user in the thread, also using a Pixel 2 XL to make it worse, beat me to testing the module on Android 11 by a few hours, so it does work with Android 11.

Not sure why a Pixel 4 is being such a pain, but it should be solvable, hopefully, barring any new crackdown by Google.

When in doubt, go back and start afresh with as clear a slate (base) as possible is really my best tip here.

This module has always had its best chance/success on a clean flash, i personally have never used it any other way, so any other than a clean flash strategy is usually being solved by others who then submit tips....i.e. ive never had to do the clear cache/data trick....