Google Pay, Android 11 - Google Pixel 3 XL Questions & Answers

I had Google pay working with Android 10 no problems. I just recently upgraded to Android 11 and Google Pay continues to indicate that Phone Doesn't meet security requirements and doesn't allow me to use Google Pay.
I have
Magisk 21004 Installed
Magisk Manager (310) (11) installed
Both are Canary builds.
I have hidden through Magisk :
Google Pay
Google Play Services
Google Play Store
Google Services Framework ( both under google services framework is checked but the check for Framework will uncheck when I leave MagiskHide)
My Banking App
I have the Magisk Module:
Gpay SQLite Fix
Sqlite for Arm
are both installed.
SafetyNet Checks pass no problems in Magisk.
Has anyone been successful in getting Gpay to work while rooted on Android 11?

Follow this guide: https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

Related

Google pay not working - Passed safety net and tried magisk hide

Hi all,
I'm running on aosp extended with magisk 17.1. I tried registering on google pay app and its not possible says the app is not secure.
1. Magisk hide is done with google pay app
2.Magisk is updated to 17.1
3.Magisk itself is hidden from detecting
Please let me know if anyone got a workaround for the same.
Thanks
Try magiskhide props config module in magisk manager downloads.

Google Maps not compatible all PIE ROM's

Latest pie ROMs won't work with Google Maps latest version. Play store won't show it and if Google search it states incompatible device in play store.
Hopefully be sorted when official PIE is out.
Same problem here D:
Some magisk modules may be helpful. Such as ARcore enabler which will change device fingerprinter to Pixel.

Google Play with MiUi.eu and magisk

[GOOGLE PAY]Hello everyone i im miui.eu 11 and have flash magisk, i try magisk hide props module and magisk hide in app , Netflix wotks but Google pay dont work, any mode tô use Google pay with nfc ?
Try this:
https://forum.xda-developers.com/Mi-9/how-to/gpay-how-to-gpay-to-rooted-xiaomi-mi9-t3972227
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
If you read both of it thoroughly it should work.

Some very wierd cookies goint on with EFS

So I rooted my OnePlus 7T, to fix some issues I had with OOS...and it was great. I absolutely loved FDEAI, iOS emojis, swift installer, AdAway and I could go on.
But one stupid day, I installed a magisk module, that corrupted my EFS. I was really scared, since even tho I had a backup, I had trouble restroning it permanently. It got erased on every reboot.
This problem presists, I haven't found a fix. But I have a hypotesis, on what could be it's cause. I have uninstalled the module already, so that wasn't it. Only today, two weeks after the incident, I realized, that my SELinux policy was Premissive. I didn't change it intentionally, so it must have been the module that did it.
Here's where I ask for help tho : 1. How do I change SELinux to Enforcing again? I only could find tutorials on how to set it to permissive. 2. Could this be the cause of the issue? 3. If it can't be this, what do I do? I'm running OxygenOS 11, so I can't just flash a fastboot rom, nor use MSM to reset. (Both are A10 only) and I don't think downgrading with mods installed would be anything of a good idea. There's also no TWRP support as you know.
This is a true nightmare, I really hope that I'll get to fix this soon. Thanks for you'alls help in advance. Here's some technical info : Device : OnePlus 7T, HD1903 OS : OxygenOS 11.0.1.1, HD65BA Kernel : 4.14.190-prefs+ Magisk : Installed from Boot image, version 23 Current Modules Installed : iOS 14.5 Emoji for FB and Messenger 1.4 Swift Installer Module v5 Systemless Hosts v1.0 Apps with root acces : AdAway Buoy Servicely Swift Installer Vanced Manager
Disabled Packages : Android Accesibility Suite Android Auto Bookmark Provider BugReportLite Calendar Chrome com.oem.logkitservice com.qti.qualcomm.datastatusnotification com.qualcomm.embms com.qualcomm.qti.lta com.qti.qms.service.connectionsecurity Common Log Tool Default Print Service Device Personalization Services Digital Wellbeing Drive Duo Games Google Google Assistant (both packages) Google Pay Google Play Movies Google Play Music Text-To Speech Engine Insight Provider Market Feedback Agent Maps Messages Nfc OnePlus Link OnePlus Logkit Photos Qualcomm Voice Assistant Qualcomm Mobile Security Shot On OnePlus System Tracing Zen Mode
I listed theese packages, because they also might cause issues, I'm not sure.
Msm tool to go back to stock oos10
Then update to oos11 via oxygen updater app

How To Guide Rooted, passing SafetyNet, Play Integrity, and GPay/Wallet contactless on A13 stable

I installed Android 13 yesterday and had some trouble getting GPay/Wallet contactless payments working. Here's what eventually worked for me:
Magisk 25.2 (Github, XDA)
Hide Magisk app
Enable Zygisk
Enforce DenyList
Add the usual suspects to DenyList (Google Play Store, Google Services Framework, Google Play Protect Service, Wallet/GPay app)
Install @Displax Universal SafetyNet Fix Mod as a Magisk module (kdrag0n's unmodded original did not work for me)
Clear storage/cache from GPay/Wallet, Play Store, and Play Services
Reboot
And that's it. No messing around with hiding props configs or anything like that.
I used a couple of apps to check my Safetynet/Play Integrity status: YASNAC (Github, Play Store) and Integrity Checker by @1nikolas (Play Store). On YASNAC, you need to pass Basic integrity and CTS profile match. On Integrity Checker, you need MEETS_DEVICE_INTEGRITY (which I didn't have with the standard Universal Safetynet Fix; I needed Displax's mod) and MEETS_BASIC_INTEGRITY. I don't have MEETS_STRONG_INTEGRITY; it's my understanding that you can't get that with root/unlocked bootloader at the moment. However, it appears you can get contactless payments working without it.
I hope having all this information together helps others, as I had a bit of trouble hunting it down.
Bringing from the kernel thread so we keep the off-topic to a minimum there.
triggerhappy_ said:
Reinstalling SafetyNet Fix 2.3.1 in Magisk Modules seems to be working fine.
Spoiler: YASNAC CTS profile check
View attachment 5687621
But still I haven't DEVICE_INTEGRITY in Play Integrity API checker. upd. after cleaning cache, now it doesn't have even BASIC.
Spoiler: API checker
View attachment 5687635
The app is probably corrupted, others are just doing fine. Anyway.
Spoiler: SafetyNet checker
View attachment 5687649
Click to expand...
Click to collapse
The newer Mod version of 2.3.1 Universal Safety Net fix referenced in the OP fixed the device integrity for me just now. I uninstalled the original fix (didn't reboot yet), then installed the new fix, rebooted, and I got device integrity passed.
direwolf1 said:
Add the usual suspects to DenyList (Google Play Store, Google Services Framework, Google Play Protect Service, Wallet/GPay app)
Click to expand...
Click to collapse
You don`t need to add all this stuff to DenyList when using USNF.
Weird that some don't work and others do *typical of Google though I guess lmao*. I've been using mine fine since the moment I first flashed it without any of above hassle. The Wallet might be bank related but integrity I dunno what would be the difference
This worked for me. I followed the same procedure in the exact order and experienced the same thing all the way through. Thanks very much for taking the time to make this post, I was absolutely dreading this and you made it easy for me!
Displax said:
You don`t need to add all this stuff to DenyList when using USNF.
Click to expand...
Click to collapse
Thanks! Appreciate the tip and the great work on the mod!
You can also install Shamiko for banking apps that need to be hidden. Mark but disable the deny list.
For those that have done this, is all DRM related stuff working with Widevine L1, etc (Netflix, Hulu, Peacock, etc)...
I can confirm for Hulu, works perfectly well with Displax's mod of USNF 2.3.1 and Shamiko.
Is it weird I'm still passing Integrity and Safetynet after the Android 13 update with the original kdrag0n module? Or is this one of those slow rollout things that will eventually affect me?
Thanks for this! Did the exact steps as the OP and everything works perfectly!
HereticBG said:
Is it weird I'm still passing Integrity and Safetynet after the Android 13 update with the original kdrag0n module? Or is this one of those slow rollout things that will eventually affect me?
Click to expand...
Click to collapse
Until I used the SafetyNet v1.31 MOD version, I only passed basic integrity in the Integrity Checker app. After I installed the MOD version, I then passed Device Integrity as well.
direwolf1 said:
I installed Android 13 yesterday and had some trouble getting GPay/Wallet contactless payments working. Here's what eventually worked for me:
Magisk 25.2 (Github, XDA)
Hide Magisk app
Enable Zygisk
Enforce DenyList
Add the usual suspects to DenyList (Google Play Store, Google Services Framework, Google Play Protect Service, Wallet/GPay app)
Install @Displax Universal SafetyNet Fix Mod as a Magisk module (kdrag0n's unmodded original did not work for me)
Clear storage/cache from GPay/Wallet, Play Store, and Play Services
Reboot
And that's it. No messing around with hiding props configs or anything like that.
I used a couple of apps to check my Safetynet/Play Integrity status: YASNAC (Github, Play Store) and Integrity Checker by @1nikolas (Play Store). On YASNAC, you need to pass Basic integrity and CTS profile match. On Integrity Checker, you need MEETS_DEVICE_INTEGRITY (which I didn't have with the standard Universal Safetynet Fix; I needed Displax's mod) and MEETS_BASIC_INTEGRITY. I don't have MEETS_STRONG_INTEGRITY; it's my understanding that you can't get that with root/unlocked bootloader at the moment. However, it appears you can get contactless payments working without it.
I hope having all this information together helps others, as I had a bit of trouble hunting it down.
Click to expand...
Click to collapse
Thanks so much for your detailed instructions.
Could you please be so kind as to check whether Xprivacylua works with your settings?
Looking forward to your comments
bush911 said:
Thanks so much for your detailed instructions.
Could you please be so kind as to check whether Xprivacylua works with your settings?
Looking forward to your comments
Click to expand...
Click to collapse
I don't use Xposed, so unfortunately I can't test that for you.
roirraW edor ehT said:
Until I used the SafetyNet v1.31 MOD version, I only passed basic integrity in the Integrity Checker app. After I installed the MOD version, I then passed Device Integrity as well.
Click to expand...
Click to collapse
That's what's weird, I pass both Basic and Device Integrity without the new MOD version, just using the old kdrag0n module. I guess it'll just hit me eventually lol
bush911 said:
Thanks so much for your detailed instructions.
Could you please be so kind as to check whether Xprivacylua works with your settings?
Looking forward to your comments
Click to expand...
Click to collapse
try to use shamiko if you use lspoed
LLStarks said:
You can also install Shamiko for banking apps that need to be hidden. Mark but disable the deny list.
Click to expand...
Click to collapse
also a blank whitelist file in /data/adb/shamiko will hide all rooted things from the system you can chack rooted status with MOMO app
Druboo666 said:
try to use shamiko if you use lspoed
Click to expand...
Click to collapse
Thank you for the input, I use Xpivacy mainly for hooking location as well other items, but shamiko is for hiding root?
bush911 said:
Thank you for the input, I use Xpivacy mainly for hooking location as well other items, but shamiko is for hiding root?
Click to expand...
Click to collapse
shamiko should hide both lspoed and root.not sure give it a try
It worked perfect on Pixel 6 with Android 12 thanks!

Categories

Resources