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.
Related
HI, is anyone else having an issue with an Droid pay? I'm running nought on a2017u . When I unlock the phone and open the android pay app to pay it doesn't work. I'm shown my credit cards but I'm never prompted to enter my pin or fingerprint. Is there something else to do? I'm not rooted and bootholder is locked.
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.
I finally installed 10.3.0, rooted, and am using the SafetyPatch module to bypass Safetynet on my OnePlus 6t T-Mobile phone converted to International.
Now my Google account show shows my device as Huawei P20 Pro. How do I change this?
redcodefsu said:
I finally installed 10.3.0, rooted, and am using the SafetyPatch module to bypass Safetynet on my OnePlus 6t T-Mobile phone converted to International.
Now my Google account show shows my device as Huawei P20 Pro. How do I change this?
Click to expand...
Click to collapse
Under some circumstances it is necessary to change the "fingerprint" of your device to appear as if it is another device in order to pass CTS.
... Oddly I too had problems with Safety net when first flashing over to 10.3, I got lost in translation somewhere because after re-flashing it a few times with both the local upgrade method and TWRP now it passes Safety-net by default, no extra Magisk module necessary.
I am rooted without TWRP, last time I tried going through TWRP but it flashed on both partitions and I lost My OS.
Hey,
I had the PixelElxperience custom rom installed until I heard about the new android 11 oxygenos beta. So I installed the new beta. Only problem there is I don't pass the safetynet anymore. I locked the bootloader which lets me pass google pays safety as I can add paypal. But my banking app doesn't let me log in.
Use magiskhide...
I second MagiskHide with the additional option of setting your props config to OnePlus 6T on Android 10.
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