I have the Verizon LG Velvet. It works fine but here is the issue.
Android 10 software version-G900VM10e-Google Pay works fine. SafetyNet check gives the phone a good pass on all:
SafetyNet Request-PASS
Response Signature-PASS
Validation-PASS
Basic Integrity-PASS
CTS Prifile Match-PASS
However, when the phone reaches Android 11 G900VM20F via updates, CTS Profile Match comes back with a FAIL. And Google Pay no longer works. I get the following message when trying to set up my cards in Google Pay:
{Couldn't finish setup to pay in stores-This phone can't be used to pay in stores.This may be because it is rooted or altered in some other way.}
This phone was never rooted and I only get this message when the phone reaches the 20f firmware update. I had to downgrade the phone back to Android 10 G900VM10e in order to continue using Google Pay. But the phone will update back up again to 11.
Does anyone know what may be the issue and how it can be fixed? Thanks
NVM....updates corrected it this time around
I can confirm that Google Pay does not work on Velvet 5G, Android 12, Software Version: G900VM30f.
Same CTS failure. Phone was never rooted.
What is the working version of the firmware that you are using?
abuchison said:
I can confirm that Google Pay does not work on Velvet 5G, Android 12, Software Version: G900VM30f.
Same CTS failure. Phone was never rooted.
What is the working version of the firmware that you are using?
Click to expand...
Click to collapse
It was a dead issue. The same issue returned shortly after I thought it cleared. I ended up getting a refund from the seller.
Related
I'm unable to use Android Pay - I'm not rooted, the boot loader is RELOCKED but when I try and add my card I get the dreaded "Google is unable to verify that your device or software running on it is Android compatible" error.
So, I was wondering, is it the fact that I did previous unlock my boot loader or something else stopping me.
BTW, Vendor: hw Country: eu, running C432B170.
Cheers.
No joy either
Same problem here. Imported mine and have done nothing but update to latest version of official roms (tried a couple of different ones today as well) and I get the same error. No rooting, purposely held off doing so so I could try Android Pay. SafetyNet Helper says the "CTS profile match" is false. My wild stab in the dark is that it is something to do it with it being identified as an international handset or handset from a non-Android pay supported country.
Had a web chat with an Android Pay helpdesk monkey and they had me reboot and reinstall a few times. They've also had me send some screenshots but I'm not holding out much hope for a useful reply.
captainkibble said:
CTS
Click to expand...
Click to collapse
CTS or CSC?
themissionimpossible said:
CTS or CSC?
Click to expand...
Click to collapse
CTS. Just double checked.
Maybe it's the same thing as CSC for Samsung phones.
In case, this might represent the target market for that phone, and that market might not yet be allowed to use Android Pay.
I'm using the single SIM version, NXT-L09, I managed to add my card but when I tried to pay for something in store I got the unable to verify.... message pop up on screen.
It also fails the CTS profile match in Safetynet helper
Android Pay worked for me today
I gave safetynet helper another try and this time it said my device passed. Re added my card to it and then used it on a London bus.
Using a Mate 8 NXT-L09C636B170
I too am able to use Android Pay. It started working for me last Thursday. While I had an open support ticket with the Android Pay help desk I periodically checked to see if it had started working. Eventually it did. I was able to add cards, SafetyNet Helper passed it's check and I was able to make payments. Result.
The same day, Android Pay help desk got back to me regarding my support ticket (there had been some backwards and forwards with logs, screenshots and the like). They concluded that Android Pay would not work because my phone was rooted. It isn't and has never has been. They had me send screenshots of multiple root checkers that displayed that the phone was not rooted *before* they came to this conclusion. I guess they just wanted the ticket closed and that was the most convenient excuse.
I've put it down to enough people reporting handsets not working that the Google added more phones to the "approved list" and help desks don't know what they are talking about.
My build number is NXT-L29C636B180
Hm.. Well this was interesting to read. Thanks for the updates saying that Android Pay does in fact (hopefully) work! I'm going to to get the L29 International dual SIM version soon so I was curious... I'll update when I get it and test it out
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
gnasher666 said:
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
Click to expand...
Click to collapse
Same here...
bh4714 said:
Same here...
Click to expand...
Click to collapse
I've downgraded to B170 and now have Android Pay working.
The high level process was:
All done via the help of SRK Tool http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
1) Unlock Boot Loader
2) Install Custom Recovery
3) Root Phone
4) Change to oeminfo and custom.bin eu (c432) - Even though I already was
5) Copy Full Update.app for C432B153 to dload folder
6) Flash stock recovery
7) Boot recovery and allow update to install
8) Factory Reset
9) Copy Update.app for C432B170 to dload folder
10) Boot recovery and allow update to install
I'm not sure how but following this process (although I've listed the steps from memory and not in front of my Laptop I did this on) I ended up with a Bootload LOCKED C432B170 and Android Pay works. I've not - nor will I update to and EMUI 4.1 version until they are released as OTA updates that my phone asks me to install
Android Pay was working fine on B103, I've upgraded to B321 via dload and now got pop up info that my device is incompatible with android pay. Any ideas?
Sent from Huawei Mate 8
Just one question
Hi,
Which recovery should I flash? the one for EMUI 4.1 or 4.0?
thanks
I believe Android Pay will not work with EMUI 4.1. I wish we were warned about this before we were allowed to flash to 320 or 321. No warning with the update links. Sucks!
Sent from my HUAWEI NXT-L29 using XDA-Developers mobile app
Hello Guys,
I Just wanted to know how I root my pixel 3 with android 12 just guide mn or is there already a thread than give me a link but plz for android 12
Rooting Android 12 works exactly the same as Android 11 on the Pixel 3.
Since there were no obvious guides, I just wrote one for the Pixel 3. Here you go.
Thanks for help
Can u tell me is there any twrp for android 12
Not that I know of, at least it doesn't work on my rooted P3 running Android 11
Hmm so how we install custom roms
rocketrazr1999 said:
Not that I know of, at least it doesn't work on my rooted P3 running Android 11
Click to expand...
Click to collapse
Update... Android 12 can be rooted using Magisk Canary
I was able to take an OTA update to Android 12 on my BL unlocked, rooted, custom kerneled Pixel 3! I started the update accidentally by hitting that pop up reminder and after a minute of thinking what to do (i did not want to lose my data!!!), I held down the power button to force it to reboot during the update. I have had this work to stop an OTA update and restore it perfectly to previous state. Anyway, it did NOT work this time, and it updated to A12 perfectly! No loss of data, no loss of custom kernel, but i did of course lose root. Also.... when i checked the update version in settings, it wanted to update AGAIN, from Oct 21 to Feb 22 (which is just an Emergency Dialer patch). My phone still shows Oct 21 security patch in settings, but shows the Feb 22 firmware (...016.C1), which suggests the patch was only a tiny fix to the 911 Dialer and did not affect anything else. So this time i let it update, which i started to think was stuck or looping after waiting about an hour, but finally i checked the progress and it was done, requesting a reboot! So i rebooted it and behold, its now running final security update to the Pixel 3, and all i need to do now is root with Magisk and install SafetyNet Fix. Which is the ONLY thing i can think of as to how it was able to do a factory OTA update while rooted and BL unlocked! The SafetyNet Fix patch may be so good that it bypasses the Google security measure that refuses to allow OTA updates on rooted, unlocked Pixel 3s. Yup, on a GOOGLE PIXEL! I used to have to unroot and install the factory kernel to do an OTA sideload on my old Essential in order to update and not lose data, but i was told that you could not update to new Android versions without losing your data on the P3, so Ii just figured my Sept 21 A11 firmware was the final update until a phone upgrade. Anyway, just wanted to pass on the good news that you CAN perform a factory OTA update from A11 to A12 on the Pixel 3 WHILE rooted and unlocked and with a custom kernel, but I of course have to recommend you do so on your own, and if anyone has an unused or non-daily driver P3 that want to confirm this good news, please do so and help convince the disbelievers ! The ONLY thing i would recommend is that you have the latest "Android 12" version of SafetyNet Fix installed with the switches on in Magisk, which is what i had. Its the only thing i can think of that would allow Google's Safety Net to bypass the security restrictions. OK then, hope a few of you give it a try to show im not a nutcase, lol.
Question kind of related to this... Was the P3 kernel updated in Android 12 to fix that race condition that causes freezes if using systemless hosts? With A11 I always had to make sure I installed a custom kernel before Magisk and enabling systemless hosts to keep my P3 from freezing.
Hello! I have an T-mobile version of LG v60. It is permanently unlocked and it has the V600TM20n update. I tried researching on internet about the LG V60 variant, and I couldn't find much information.
Can somebody tell me:
If it is possible to prevent the updates from applying during midnight?
If Android 11 version is still 'root-able'?
If not, is still possible to revert to an older version of Android without losing carrier unlocked status?
My main concern is that these updates will disable my ability to root the phone. Thanks.
Pioneer22 said:
Hello! I have an T-mobile version of LG v60. It is permanently unlocked and it has the V600TM20n update. I tried researching on internet about the LG V60 variant, and I couldn't find much information.
Can somebody tell me:
If it is possible to prevent the updates from applying during midnight?
If Android 11 version is still 'root-able'?
If not, is still possible to revert to an older version of Android without losing carrier unlocked status?
My main concern is that these updates will disable my ability to root the phone. Thanks.
Click to expand...
Click to collapse
Yes,youcan turn off auto updates in settings.Yes,A11 is still rootable.And,yes you should be able to downgrade and you won't lose carrier unlock.
surgemanx said:
Yes,youcan turn off auto updates in settings.Yes,A11 is still rootable.And,yes you should be able to downgrade and you won't lose carrier unlock.
Click to expand...
Click to collapse
Turning off auto updates and settings does nothing to actually prevent the phone from updating on its own.
Some of us tried preventing Android 10 to 11 but it didn't work. Is anything different for Android 11 to Android 12? If you did get it to stop can you detail what you did? It would be quite helpful.
If you are rooted and unlocked, your phone will not update. It will "error" out everytime.
You will continue to get the nag screens, but the phone won't update. That's been my phone's behavior.
[NG]Owner
Hi guys, so I bought my first Realme phone a couple of months ago and I noticed that the Google Pay app wasn't working. I checked the ali store where i bought it and surely it said "Global rom: This is the version with global firmware installed, with many languages, including portuguese language, spanish language, google store is normal, but please note that google pay payment does not work properly". For any reason, this ROM wont let me have Google Pay, so I wanted to know if any of you knows how to enable the Google Pay app? or should I install another ROM? Has any of you had a similar problem? Thanks
Perhaps shift from global to Europe firmware?
Im from South America, so I dont know if the European firmware would work. I'm having a little bit of trouble finding out how RUI 3.0 - Firmware - ROM work. Also, do you know how to do the shift from Global to European? Or at least a tutorial? Ive seen the site https://realmefirmware.com/realme-gt-neo2-5g-firmware/ which has the global firmware released today but I dont know if it's just installing the firmware and problem solved.
Bootloader unlocked = no google pay, it will only work with the original firmware channel, don't try locking your bootloader if you are not 100% sure of it, this will cause your phone to bootloop and you will end up with a bricked device that only realme support would be able to solve, the best solution would be to spoof your device fingerprint to pass the SafetyNet and everything will work just fine, you can contact me for help if you want.
Yes Im going to need a little bit of help with that, thanks
hen1_98 said:
Bootloader unlocked = no google pay, it will only work with the original firmware channel, don't try locking your bootloader if you are not 100% sure of it, this will cause your phone to bootloop and you will end up with a bricked device that only realme support would be able to solve, the best solution would be to spoof your device fingerprint to pass the SafetyNet and everything will work just fine, you can contact me for help if you want.
Click to expand...
Click to collapse
Hello hen1_98, so may I know how to spoof the fingerprint to pass SafetyNet?
drwpls said:
Hello hen1_98, so may I know how to spoof the fingerprint to pass SafetyNet?
Click to expand...
Click to collapse
With Magisk installed you can use the Universal SafetyNetFix by kdrag0n, easy fix
hello, I also flashed the phone, changed the region, rooted it (now it does not work). And closed the bootloader. works on the old bank, but the new (other) does not want to.
hen1_98 said:
With Magisk installed you can use the Universal SafetyNetFix by kdrag0n, easy fix
Click to expand...
Click to collapse
i did install it, but CTS profile still not pass.
I figure out that I need a valid fingerprint which associate to the device (The one which registered to google) to make CTS check pass.
So, I need the fingerprint when the device is in stock rom and haven't rooted.
Google Pay does not work.
-The phone fails Play Store certification.
-The phone fails CTS check
The phone is 100% stock and never rooted.
Software Version: G900VM30f (The latest available)
Anyone else ran into this issue? What was the last firmware version that worked with GPay?
No Velvet 5g owner uses GPay?