hi I have always managed to pay contactless with Gpay with magisk, but after this update I found no way to pay since Gpay tells i'm unable to add my cards since my phone is rooted.
Is it happening to you as well?
any solution?
It's because the update is reporting a wrong version, if you check your version in About Device it'll say C.21 instead of C.20.
People on the SafetyNet Fix git made this list to get it to work: https://github.com/kdrag0n/safetynet-fix/issues/188#issuecomment-1147295375
Here's the newer SafetyNet Fix they use (v2.3.0): https://github.com/frnode/safetynet-fix/releases
Related
Hi,
I have the Z17 Lite (NX591J) and 1 week ago, Google Pay now gives me this message: "Google pay can't be used on this device. This may be because your device is rooted, has an unlocked bootloader or is running a custom ROM. As a result, Google can't confirm that your device meets Google Pay's security standards."
Before this, NFC and Google Pay had been working perfectly. I have not done anything to cause this and did not have any OTA update or anything from Nubia. It may have started from Google Pay version 1.55.190269934, but may have been the previous version.
I have installed "Root Checker Pro" just to check. It says "Not Rooted" and on Safety Net check, the only thing that fails is CTS profile match.
Everything was working well and I updated it to the 20180223 update from geekbuying still everything working well including NFC and Google Pay.
Yesterday, I updated to the 20180316 from geekbuying (which I think is exactly the same as 20180223) but it has not changed anything. I still get that error message from Google Pay.
What can I do?
Is anyone able to help me regarding CTS Profile match = false (mismatch)?
Geekbuying released an updated firmware v1.05. CTS profile is fixed and therefore Google Pay works again.
This thread can be closed.
Hi all!
I decided to go back from ArrowOS Pie to stock 8.1. I used this procedure and a POTTER_RETAIL_8.1.0_OPSS28.85-17-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip file from here. Everything is great, even Netflix is accessible via Google Play, but device from Google Play perspective is still uncertified. Safetynet check says there's CTS profile mismatch, therefore Google Pay won't work.
Is there any way to fix this without unlocking the bootloader again and applying Magisk? I heard that ROM files Motorola vendor uses for flashing their devices could help, was any version of it released or leaked for potter?
Thanks for any suggestions!
K
Hi folks,
LM-V350AWM here running flashed Pie (V350AWM20d). Haven't tried to root, flash modded boot.img, anything. For a few weeks after flashing Pie, Google Pay was working just fine. Now in the last week my device has lost its Play Protect certification (which prevents me from using Google Pay). Nothing has really changed software-wise.
On my old G6 we had root and TWRP so Magisk could just trick the SafetyNet check, but I can't think of any reason why the certification would be lost with neither. Possible interference with Blokada's "VPN?"
I and my friend with LG V40 have the same problem! If you can find the solution please post it here.
Same here.
Bumping, anyone figure out a fix?
Hello
I have OnePlus 6T international version.
I recently updated to OOS11, build A6013_41_210805 via Oxynogen Updater.
No root, just stock.
Google Pay shows all cards, Contactless Set Up menu shows "You're all set to pay with your phone".
But when I tried to pay, error pops that phone not configured for payments.
No issues with OOS 10.
Anybody with same experience?
How can I fix?
Thanks for any advice.
EDIT:
Disabling, wiping app, removing all cards and setting again and payment works.
Hello. I have some issue with gpay on oos13. In2023 11_f_64.
I have root with magisk26.1 hidden.
The safetynet passed with safetynet fix module.
the problem is Gpay work for some hours on my device then after hours i got a message saying my device dont match the security requirement and that i can not use gpay. When i clean all the data of the google play store and the google play service. I can use gpay again. But after some hours i got the same message. I think it may detect the unlocked bootloader. Do somebody face the same problem ? Any solutions ?
stell52 said:
Hello. I have some issue with gpay on oos13. In2023 11_f_64.
I have root with magisk26.1 hidden.
The safetynet passed with safetynet fix module.
the problem is Gpay work for some hours on my device then after hours 192.168.100.1 192.168.1.1 i got a message saying my device dont match the security requirement and that i can not use gpay. When i clean all the data of the google play store and the google play service. I can use gpay again. But after some hours i got the same message. I think it may detect the unlocked bootloader. Do somebody face the same problem ? Any solutions ?
Click to expand...
Click to collapse
Google Pay uses SafetyNet API to check for device integrity and security. If any modifications have been made to the system or if the bootloader is unlocked, it can trigger a SafetyNet failure, leading to GPay not working properly.
SAMI_AI202 said:
Google Pay uses SafetyNet API to check for device integrity and security. If any modifications have been made to the system or if the bootloader is unlocked, it can trigger a SafetyNet failure, leading to GPay not working properly.
Click to expand...
Click to collapse
Thanks you for your reply. I still always pass the safetynet test but gpay is not working