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
Related
I don't get it....
I have been rooting and customizing since my Droid 1. In all that time over several devices...there was never a need to un-root and take an OTA...that was not soon made available through Dev's that could be flash via customer recovery, or pushed via ADB.
But I keep reading how all these HTC One users are doing just that.
I got my One on Thursday from VZW store, and it was still running 1.10.605.8. I figured that once s-off and rooted I could flash any new radios/modems...and the ROMs would take care of the rest...so no need to update to 1.10.605.15.
Currently running EclipticOne with the 1.10.605.15 radios.
Am I wrong? Is there something I missed?
Thanks,
I think it's the amount of people who are new to the process of how to handle taking updates when they're S-Off/Unlocked Bootloader/Rooted. The only way they've ever known to do Android updates is taking OTA's. They're new to the paradigm of manually updating radios, hboot, and /system.
It can't be stressed enough that OTA's are designed for completely stock, untouched devices. OTA's aren't made with hacks in mind, nor will they ever be, nor should they be.
If you want to go S-OFF, unlock the bootloader, install a custom recovery, and get root, you have to be willing to take on some of the extra responsibilities that come along with it. One of those is forfeiting a normal OTA process. OTA's will, at the very least, remove root. You're going to have to boot to recovery to reinstall superuser so you might as well just do all the updates manually.
Really just a matter of preference and what you are after. This is the first phone I have owned that I am content running stock, other than a few apps that require root. It's actually faster for me to take the OTA and reflash custom recovery/supersu which are already on my computer than to wait for someone to upload the goods.The end result is the same, just different ways of getting there, none better than the other.
xenakis said:
Really just a matter of preference and what you are after. This is the first phone I have owned that I am content running stock, other than a few apps that require root. It's actually faster for me to take the OTA and reflash custom recovery/supersu which are already on my computer than to wait for someone to upload the goods.The end result is the same, just different ways of getting there, none better than the other.
Click to expand...
Click to collapse
I could be wrong but if you take an ota and expect to retain root and s-off every time, you might be in for a surprise. im pretty sure certain updates have been pushed that relocked bootloaders and removed s-off.
MJL99 said:
I could be wrong but if you take an ota and expect to retain root and s-off every time, you might be in for a surprise. im pretty sure certain updates have been pushed that relocked bootloaders and removed s-off.
Click to expand...
Click to collapse
It was my understanding S-OFF stays on/off (whatever) no matter what OTA you take.
Sent from my HTC6500LVW using Tapatalk
Though folks often warn that an OTA may remove s-off, I have never seen evidence of one doing this and could not find any posts on XDA or anywhere else about this happening. And while it is technically feasible for an OTA to remove s-off, I can't imagine any phone maker or carrier doing so. More important for them is patching known exploits, which if you already have s-off is not an issue since the exploit was only needed to get you s-off, not to keep you there.
Obviously, this wouldn't be the first time that I am wrong and welcome anyone to post a link to an example of an OTA undoing s-off. I'm only here to learn and if you keep me from screwing up my phone, I'll thank you!
I've got a new t807a from AT&T. According to the "about device" settings page, SE is "enforcing." My understanding is that this conclusively indicates that my bootloader is locked. It's currently running Android version 4.4.2, build number kot49h.T807aucu1ank1
I don't need a custom ROM and I don't care about tripping my knox counter (per se). I just want root. I've asked this in several relevant threads this week and gotten contradictory responses. Is there or is there not currently a method to root my tablet?
If not: is there hope? This is a great tablet but I can't live with the bloat for 18 months until I can afford a replacement. I CAN still return it and eat the 70-dollar "restocking" fee.
Thanks in advance.
Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.
TheArtiszan said:
Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.
Click to expand...
Click to collapse
So what does that mean for my t807a?
thorvindr said:
So what does that mean for my t807a?
Click to expand...
Click to collapse
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.
skeeterpro said:
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.
Click to expand...
Click to collapse
Thanks. I have been following that. Just hoping someone knows something I don't I suppose.
ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!
DUHAsianSKILLZ said:
ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!
Click to expand...
Click to collapse
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?
thorvindr said:
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?
Click to expand...
Click to collapse
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).
DUHAsianSKILLZ said:
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).
Click to expand...
Click to collapse
Well that blows. I guess that's what I get for buying off-the-rack.
Is this info outdated?
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work
JMVPSlash said:
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work
Click to expand...
Click to collapse
The built-in app manager lets you move apps to SD but I also have not found a solution to install directly to SD (without repartitioning the card). After several months of despair, I'm just now checking back to see if there's been any development on the bootloader front. It appears not. You can get root with Kingroot (also check out supersume, if that's still around, to replace kingroot's su app with supersu) but apparently the bootloader being locked prevents any non-official ROM from booting.
My UK unlocked M9 is still on v2.10.401.1, even though v.2.11 has has been out a few months now in Europe.
I ran 2 root checkers on it and got 2 results:
From the 2 screenshots, can anyone tell me if my device has been tampered with and not rooted properly or is not rooted at all... Its hard to tell.
Might it be worth me re- flashing a stock rom to trigger the OTA.
Thanks
Surely 2.10 is still current version for WWE as all the custom roms are still on it......what did you actually do to try and root it? Do you have superSU installed? Have you tried any apps that require root to see if they function? Are you running stock rom or custom?
Ive added 2 screenshots of my version. I bought my M9 from a pre-owned store yester, which should be 100% unlocked unrooted, but the reason Im asking about 2.11 is because of the link below dated back to June:
http://blog.htc.com/2015/06/htc-one-...ftware-update/
So either one of the root checkers is wrong.. or this m9 rooting was messed up by a noob and traded in OR we are still on 2.10 and im reading into this to much.
Some advise would be great..
Thanks
]I just thought Ide add alittle more info.. After searching around, I checked for root Using both Terminal Emulator and ConnectBot and came up ewith No root access, So im hoping Root checker Basic is wrong. I also checked BusyBox Checker and AM I Root? Apps for BusyBox with SuperSU root, Both showed No Root.
Buying 2nd hamd/Pre-owned Phones, even from a high street store can always be a cheaper alternative, but can also run the risk of an attempted root and messed up by the person who traded it in, although I know stores are supposed to have software to check for this.
Any more advise or help anyone has would be greatly appreciated
I hope this thread helps others who have bought 2nd hand/pre-owned Phones and want to make sure their device is actually Factory unlocked and not Modded/Rooted when purchased.
Thanks
Check bootloader if it is "Locked" or "Relocked".
If it shows "Locked" then it was either never rooted, or was rooted & returned to 100% stock @ at which you won't be able to know if it ever rooted (except, maybe, if you unlock it & try to run Sunshine S-Off & it doesn't require a payment meaning it was used previously on the device).
Have you try to flash BETA-SuperSU-v2.52.zip in the recovery?
Check bootloader if it is "Locked" or "Relocked".
If it shows "Locked" then it was either never rooted, or was rooted & returned to 100% stock @ at which you won't be able to know if it ever rooted (except, maybe, if you unlock it & try to run Sunshine S-Off & it doesn't require a payment meaning it was used previously on the device).
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
My Bootloader says "S-ON" "Locked" Software Status "Official",
Does that mean then that it should take an OTA?
-------------------------------------------------------------------------------------------------------
Have you try to flash BETA-SuperSU-v2.52.zip in the recovery?
-------------------------------------------------------------------------------------------------------
Not sure what you mean!!
No, I havent tried to flash anything, Ive just bought the M9.
But to Answer your question, when I try to boot into Recovery from HBoot, all I get is a black screen with a with a RED Triangle and RED "!" mark through it,
but that could be me not knowing how to boot into Stock Recovery. Theres no Other 3rd party Recovery on the M9
So all in all... am i right in thinking that my M9 is fine with no tampering... and 2.10.401.1 is the current factory unlocked OS in Europe.
Hope that gives more info
If your device is "Locked" and you get a black screen with a with a RED Triangle and RED , it seems to be stock and not rooted and should receive the next OTA.
Yes. Your device is fine & should receiveu plates (OTA) when they arrive.
Sorry Mods for not using correct "Quote" and "thanks" buttons, not sure how they work in this new XDA forum layout: )
---------------------------------------------------------------------------------------------------------------------------------------
omar302's Avatar
Yes. Your device is fine & should receiveu plates (OTA) when they arrive.
---------------------------------------------------------------------------------------------------------------
Great!
---------------------------------------------------------------------------------------------------------------
If your device is "Locked" and you get a black screen with a with a RED Triangle and RED , it seems to be stock and not rooted and should receive the next OTA.
---------------------------------------------------------------------------------------------------------------
Many Thanks for putting my mind at reast.. I really appreciate it... Happy guy now
Thanks to everyone for taking the time to help me out with this and I just hope this thread helps someone else check their 2nd hand/pre-owned device
Peacr All
Download Terminal Emulator, open it up, and type "su." If it asks for root permissions, you're rooted.
Already done... I provided svreenshots further back.. Checked for Both SuperSU and BusyBox root using ConnectBot & Terminal Emulator.
All sorted.. Thanks though
Get into the bootloader and if it says "locked" then no.
I wish I stole my HTC M9.
Hello. I'm pretty terrible at all this rooting stuff (or at least, I only do it once for each android phone I get, and then don't really look into it or stay up to date on all of it afterwards, I just use a few pluses that come along with being rooted).... Anyways, I really do need some help this time, as the confusion has really gotten to me, and I've lacked being able to find some simple answers (probably because they are just THAT simple) on google/reddit/on this forum.
Anyways, I've rooted my phone awhile back, lost it when my verizon pixel auto updated to 7.1.1 (idk how or why, pretty sure I had that disabled with root even, very frustrated) and even attempted to regain root by flashing SU with TWRP, but for some reason SU said I didn't have root still, and eventually just gave up in frustration. But now, my verizon pixel has been shutting off at ~40% battery power, and I read in the google forums that this was patched in the 7.1.2 update for pixels, and it was a software glitch rather than a malfunctioning/bad battery... So now I really want to upgrade to 7.1.2 from 7.1.1 not only to fix the battery/software issue, but also because I really want root.
I have an unlocked bootloader from when i first got my pixel and did this stuff, but now im unrooted on 7.1.1 because of that update awhile back, and want to update to 7.1.2 and root, but I've heard theres issues with rooting on the verizon because of bootloader, but that shoulden't be an issue since I unlocked it already (right? at least, I think? please let me know).
My only question (since i think i'll be able to follow this guide once I get the answer to this) is in the post he says: "Works with 7.1.2 (NJH47F, Aug 2017)".......... but since i have the verizon pixel (small version, not XL), should i be downloading this version: 7.1.2 (NHG47Q, Aug 2017, Verizon).... Or would it just be acceptable to allow my phone to auto download the update i have on it right now? Or must I download the NON verizon version as stated in the post and flash that one? Thanks for the help guys!
Thanks for any help!
-Synk
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
jhs39 said:
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
Click to expand...
Click to collapse
Thank you so much for the explanation. Truly, it's actually crazy how I was unable to find all of this neatly, nicely, and simply stated. Great to hear, I'm going to go on rooting, here's to hoping I don't blow it up.
I was given a Google Pixel 2 XL from a friend, who told me he partially rooted it. And indeed, the bootloader is unlocked, but I can't tell if he went further than that, and I can't ask him because he's... inaccessible at the moment, but another mutual friend seems to think that unlocking the bootloader is as far as he got. I want to undo what he did though, and return it to stock, but I'm wary without knowing for sure. Is there a way to see how far he got? I know that's kinda vague. Or would flashing a stock image and then locking the bootloader fix it regardless of how far he got? I wish I knew if it was as simple a job as just relocking the bootloader but I can't know for sure.
A root checking app from the Play Store indicated that root wasn't properly installed.
Ultimately, I'd like to update my phone to Android 11 (as it's still on 10), and potentially use Google Pay.
Flashing a stock Android 11 image will remove root from the device if it is installed, so that will take care of any issues you may have. Locking the bootloader afterward is up to you. Personally I wouldn't bother; the bootloader status I don't believe affects your use of Google Pay.
Strephon Alkhalikoi said:
Flashing a stock Android 11 image will remove root from the device if it is installed, so that will take care of any issues you may have. Locking the bootloader afterward is up to you. Personally I wouldn't bother; the bootloader status I don't believe affects your use of Google Pay.
Click to expand...
Click to collapse
Thank you, I thought that was probably the case, but wanted to make sure. I wanted it undone but also didn't want to brick my phone either. Lol