I have a US unlocked HTC 10. I'm S-Off, but the bootloader is locked and I'm not rooted. Using totally stock software. Android Pay had been working fine up until a few weeks ago, but now it stopped working and my Play Store settings says my phone is "Uncertified" under "Device certification".
There were a few updates a few weeks ago. I'm wondering if one of them caused the device to be Uncertified when it is s-off? Or maybe it was a recent update to Android Pay or Play Services?
Can anyone verify that just having s-off breaks Android Pay?
Yea might be because of that s-off flag.... Google is stupid so many times
Sent from my HTC 10 using XDA Labs
xanadu1979 said:
I have a US unlocked HTC 10. I'm S-Off, but the bootloader is locked and I'm not rooted. Using totally stock software. Android Pay had been working fine up until a few weeks ago, but now it stopped working and my Play Store settings says my phone is "Uncertified" under "Device certification".
There were a few updates a few weeks ago. I'm wondering if one of them caused the device to be Uncertified when it is s-off? Or maybe it was a recent update to Android Pay or Play Services?
Can anyone verify that just having s-off breaks Android Pay?
Click to expand...
Click to collapse
This might not help you in your case, but I'm s-off with locked bootloader and fully stock other than rooted with Magisk, and I pass safetynet.
DeeZZ_NuuZZ said:
Yea might be because of that s-off flag.... Google is stupid so many times
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Not so sure about that. S-On/Off is an HTC lock, not Google.
pomponazzo said:
Not so sure about that. S-On/Off is an HTC lock, not Google.
Click to expand...
Click to collapse
Yes but Google has access to everything, so they can check whether you've modified it or not, but there are also some posts on the web that complete stock phones even non HTC can't use Android pay because of play store shows uncertified device. Don't blame HTC or so for that. It's Google ****
Sent from my HTC 10 using XDA Labs
I used Android Pay successfully yesterday. S-OFF, locked, ResurrectionRemix, Magisk.
tabp0le said:
I used Android Pay successfully yesterday. S-OFF, locked, ResurrectionRemix, Magisk.
Click to expand...
Click to collapse
Was this at a NFC payment terminal?
I'm on the latest Lineage 14.1 5/04 nightly and I pass Safety Net with the use of Magisk. I'm able to use Android Pay within the Uber app, but NFC terminal payments at stores don't work for me on thing but the stock HTC Sense software.
Edit: I forgot to mention I'm S-On and bootloader's unlocked.
tabp0le said:
I used Android Pay successfully yesterday. S-OFF, locked, ResurrectionRemix, Magisk.
Click to expand...
Click to collapse
yea, because magisk. but he's full stock with s-off and locked. for some ppl it might happen. not just for HTC, but it's very rarely that a stock htc user has this issue
tibere86 said:
Was this at a NFC payment terminal?
I'm on the latest Lineage 14.1 5/04 nightly and I pass Safety Net with the use of Magisk. I'm able to use Android Pay within the Uber app, but NFC terminal payments at stores don't work for me on thing but the stock HTC Sense software.
Edit: I forgot to mention I'm S-On and bootloader's unlocked.
Click to expand...
Click to collapse
Yeah it was at a terminal.
Related
I have an unlocked HTC 10. I recently received an OTA update.
I have been using android pay just fine with no issues. However after the most recent Android Pay update. I was getting an error message explaining I may need to "unroot" my device..
My device has NEVER been rooted and android pay has worked great!!!
As an extra precaution, I did a factory reset to my phone, and re-downloaded android pay.
Now I get a new error, but very similar. When I try to add a card after installing, now it says
"Android Pay can't be used
Google is unable to verify that your device or the software running on it is Android compatible".
After already factory resetting and uninstalling/reinstalling the app... I'm not sure what to do... I don't want to root or flash... but I am looking for options....
thanks
I read somewhere that flashing elemental X as the kernel will fix this, but I'm waiting for more people to confirm. I'm also guessing flashing a new kernel doesnt requiring wiping or anything? and lastly, how can i backup my existing kernel to reflash in case **** goes haywire? anyway, hope that helps.
Also using S-OFF and LOCKED bootloader will work.
tabp0le said:
Also using S-OFF and LOCKED bootloader will work.
Click to expand...
Click to collapse
RELOCKED bootloader status won't let android pay work?
GottaStayFly said:
RELOCKED bootloader status won't let android pay work?
Click to expand...
Click to collapse
I"m not sure about that.
SafetyNet is looking for the flag that the unlocked bootloader throws, someone more familiar with recent flags than me should know which way the flag is set upon relocking bootloader.
The ElementalX kernel has the option, but I believe that's another option for s-off users, I'm not sure if it will work for s-on unlocked users.
I think if it doesn't pick up "relocked" when it checks SafetyNet, it wont be long until it does. This is a cat and mouse game, and google has the right to "take its ball and go home" with root users, I just wish they wouldn't use that against us enthusiast users, who are their best advocates since we carry so much weight on advising all the non tech oriented unrooted consumers when it's time for them to purchase new smartphones. We are the ones that the rest of consumers call for advice or when something is broken.
Will taking this update break root or cause other issues? Just received the notice a few hours ago.
Current setup:
S-on
Unlocked
Rooted
Stock ROM still (obviously)
SW v1.80.651.1
Sprint
I waited for the N7, and returned it without opening it before the fiasco. Because I was going to wait for the Pixel, which ended up being astronomical in price. So I waited for the V20, only to find it has a "Verizoned" bootloader. And just this past weekend I settled on the HTC 10.
If anybody can provide me helpful information, I would appreciate the consideration.
ETA: NM - simply made a copy on sd card, then renamed with .bak in update folder and nag went away. Seemed to be a small incremental update from .1 to .6.
So it sounds like the lesson here is if you haven't unlocked your bootloader yet, don't, if you want to use Android Pay. From what I've read, using Sunshine to go S-off LOCKED will allow android pay to work, as long as you aren't rooted. Also there are a couple kernels you can use to disable to check for unlocked bootloader.
Is this all correct?
Sent from my HTC One_M8 using Tapatalk
I've unlocked my bootloader but I am stock with no root. I haven't done anything yet because I'm waiting for twrp and Roms to mature a bit before I dive right in. Does anybody know if it's safe to update and keep the unlocked bootloader?
I know it should be safe to do the full image flash from a computer using fastboot. I am specifically talking about the ota
lars1110 said:
I know it should be safe to do the full image flash from a computer using fastboot. I am specifically talking about the ota
Click to expand...
Click to collapse
Yes, it's safe to take the OTA as long as your bootloader is already unlocked.
Yes, I installed it with no problem. Boot loader is still unlocked, and the new move gestures are mostly OK.
I lost the ability to use the native Hotspot with my unlimited data plan on Verizon. It appears the update closed the workaround where you could use network refresher and bypass the provisioning check.
Awesome thanks everybody about to do the OTA now
Mike01680 said:
I lost the ability to use the native Hotspot with my unlimited data plan on Verizon. It appears the update closed the workaround where you could use network refresher and bypass the provisioning check.
Click to expand...
Click to collapse
Damn that sucks. I'll be avoiding it for now then. Really don't want to root. I like android pay. But I need tethering
You can update... The OTA didn't work on my phone so I had to sideload it through ADB, still unlocked and worked like a charm
wrong thread
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Sent from my Pixel XL
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Sent from my Pixel XL
Click to expand...
Click to collapse
You can before this update that was just released. You have to unlock before taking update or you won't be able to unlock. Once you unlock you can still update with no problem
Sent from my Pixel XL using XDA-Developers mobile app
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Sent from my Pixel XL
Click to expand...
Click to collapse
There is a tool that can force unlock the bootloader (depixel8?), but the exploit that it uses has been closed with this update.
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Click to expand...
Click to collapse
You can if your on 7.1 but not if your on 7.1.1
EDIT: I misread the posting. It is locked in 7.1.1.
Scott said:
This is not correct. @jcase stated he updated the tool to work with 7.1.1...
I'll see if I can find that post again...
Click to expand...
Click to collapse
Really?? The news has been all over that the 7.1.1 update patched dePixel8. He even posted on his website about it and said to not ask for further support. I assumed he didn't have a pixel so wasn't going to spend any more time on it. From my understanding the first method was very simple for them to figure out.
Please reply if you can find the post this will be big for everyone!
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Click to expand...
Click to collapse
You can unlock the bootloader with the dePixel8 method
Ad nauseum to the can you unlock or not. The latest update from Verizon makes the Verizon model locked. Period. If you haven't unlocked already, don't update to 7.1.1. If you plan to unlock. Depixel8 DOES NOT work for verizon pixel once the 7.1.1 update has been applied. If you unlock.... Don't relock. End of story. Stop with the round and round.
318sugarhill said:
Damn that sucks. I'll be avoiding it for now then. Really don't want to root. I like android pay. But I need tethering
Click to expand...
Click to collapse
I'm pretty sure you can root, change the build.prop to allow tethering, unroot, then install a custom kernel with the safetynet bypass feature and still use android pay.
So taking the OTA and flashing boot to root after will work if I'm understanding everything I've read this far? Also I have been unable to find the build specific for 7.1.1 for Verizon to download.
cntryby429 said:
I'm pretty sure you can root, change the build.prop to allow tethering, unroot, then install a custom kernel with the safetynet bypass feature and still use android pay.
Click to expand...
Click to collapse
Is this true? If so where is the post to someone doing this exact thing?
I ran the latest RUU to update my US unlocked HTC 10 to 2.41.617.3. I was hoping that it would fix it so I could pass the SafetyNet but even right after a wipe, data format, clean install and no root, the safetycheck test still comes back with CTS profile match: false. Am I doing something wrong here?
ray985 said:
I ran the latest RUU to update my US unlocked HTC 10 to 2.41.617.3. I was hoping that it would fix it so I could pass the SafetyNet but even right after a wipe, data format, clean install and no root, the safetycheck test still comes back with CTS profile match: false. Am I doing something wrong here?
Click to expand...
Click to collapse
The only other thing I can think of that would trip it is an unlocked bootloader.
Other than that, SN would **** up.
My advice is to just install Magisk and enable Magisk hide to pass SafetyNet.
Ariac Konrel said:
The only other thing I can think of that would trip it is an unlocked bootloader.
Other than that, SN would **** up.
My advice is to just install Magisk and enable Magisk hide to pass SafetyNet.
Click to expand...
Click to collapse
Thanks. I tried using Magisk and Magisk hide but unfortunately they don't work at bypass SafetyNet either for me.
ray985 said:
Thanks. I tried using Magisk and Magisk hide but unfortunately they don't work at bypass SafetyNet either for me.
Click to expand...
Click to collapse
If your bootloader is unlocked, it will fail. Install any of the current custom kernels on the forum, they all have the bootloader fix to allow it to pass safetynet. You may even be able to relock your bootloader via sunshine.
ray985 said:
Thanks. I tried using Magisk and Magisk hide but unfortunately they don't work at bypass SafetyNet either for me.
Click to expand...
Click to collapse
aer0zer0 said:
If your bootloader is unlocked, it will fail. Install any of the current custom kernels on the forum, they all have the bootloader fix to allow it to pass safetynet. You may even be able to relock your bootloader via sunshine.
Click to expand...
Click to collapse
That's what I did on my WWE variant. I bought and ran SunShine to set my device S-OFF/locked. Since then it passes SafetyNet on my end.
As it's behaviour is the same as S-OFF/unlocked it even comes in handy as soon as one's going to sell it. In such case one could easily RUU back to stock an set the secureflag back to S-ON afterwards. Renders the device in a state that's looking like you never touched it at all.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
That's what I did on my WWE variant. I bought and ran SunShine to set my device S-OFF/locked. Since then it passes SafetyNet on my end.
As it's behaviour is the same as S-OFF/unlocked it even comes in handy as soon as one's going to sell it. In such case one could easily RUU back to stock an set the secureflag back to S-ON afterwards. Renders the device in a state that's looking like you never touched it at all.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
i was one of the first to mail in, so mine is set to unlocked on vzw by default. I haven't had any need to change it though.
aer0zer0 said:
If your bootloader is unlocked, it will fail. Install any of the current custom kernels on the forum, they all have the bootloader fix to allow it to pass safetynet. You may even be able to relock your bootloader via sunshine.
Click to expand...
Click to collapse
Thanks, I'll play around with some of the custom kernels and see if that fixes it.
Hi guys.
My HTC One m9 has unlocked bootloader, installed TWRP 3.1-0-0, its rooted and I'm using SlimRom 6 . How can I make Android Pay working?
When I tried add card it said "Android Pay can't be used on this device. This may be because your device is rooted, has an unlocked bootloader, or is running custom ROM. as a result, Google can't confirm that your device meets Android Pay's security standards"
Please help me, and write what should I do simple. Thanks
Your phone must be in a stock state to use android pay. Either return your phone to stock or use another device. No other way.
Beamed in by telepathy.
Android pay (just like Pokémon go) shouldn't make any problems as long as you pass the safetynet check. You need to be rooted with magisk if you want to pass that check.
Sent from my HTC One M9 using XDA Labs
Hi just wanna ask if I should be concerned on this. After the nougat update, Device Certification under the settings menu of the Playstore app says my device is Uncertified. I'm not sure if this is the same prior update but I read somewhere else that others only had this after the update. Is there a way to solve this? My current firmware version is 2.41.401.3.
Ms_Trishlee said:
Hi just wanna ask if I should be concerned on this. After the nougat update, Device Certification under the settings menu of the Playstore app says my device is Uncertified. I'm not sure if this is the same prior update but I read somewhere else that others only had this after the update. Is there a way to solve this? My current firmware version is 2.41.401.3.
Click to expand...
Click to collapse
Nothing to worry about from what I've read.
I'm assuming you're bootloader unlocked and rooted?
Using Magisk hide + clearing playstore cache I heard may fix it.
I also think I read if you don't pass safety net is good indicator you'll show as uncertified.
andybones said:
Nothing to worry about from what I've read.
I'm assuming you're bootloader unlocked and rooted?
Using Magisk hide + clearing playstore cache I heard may fix it.
I also think I read if you don't pass safety net is good indicator you'll show as uncertified.
Click to expand...
Click to collapse
Everything is stock and it has never been rooted, aside from bootloader is currently unlocked. That's why i'm confused why it shows Uncertified device.
Ms_Trishlee said:
Everything is stock and it has never been rooted, aside from bootloader is currently unlocked. That's why i'm confused why it shows Uncertified device.
Click to expand...
Click to collapse
Im thinking bootloader being unlocked possibly just from what I've read someplace. Try locking it to see if it changes to certified.
I had the same problem, using sunshine again I locked the bootloader leaving the device s-off. I had to wipe data and running Marshmallow at the time. Message went away. John
johnc0865 said:
I had the same problem, using sunshine again I locked the bootloader leaving the device s-off. I had to wipe data and running Marshmallow at the time. Message went away. John
Click to expand...
Click to collapse
im having the same issue of not certified in playstore in my s8 plus too, no root, nothing, stock