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
Related
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.
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
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.
Pretty self explanatory. I have the update pending for 8.0 but I've heard mixed reviews of the Oreo updates. So please, if anyone can be honest and tell me weather to proceed, or should I wait and why. Thanks you.
If it's a Verizon model you just have a gem in your hands, look on how to unlock the bootloader before update, if it's a Google version, then all you get are improvements and new features without compromises.
liriolebron said:
If it's a Verizon model you just have a gem in your hands, look on how to unlock the bootloader before update, if it's a Google version, then all you get are improvements and new features without compromises.
Click to expand...
Click to collapse
What's the best way to check if it's Verizon? And I don't need to root or anything honestly. I'm asking if the bugs with 8.0 are worth updating at the current state.
I recommend unlocking bootloader first and then update
So by unlocking the bootloader, I won't run into problems taking official updates?
nellycruzz said:
So by unlocking the bootloader, I won't run into problems taking official updates?
Click to expand...
Click to collapse
No. If you modify system (root, Magisk, custom ROMs/kernels, TWRP recovery, etc) then you won't be able to take official OTA updates. But you can take them just fine with an unlocked bootloader.
Also, I'm on stock 8.1 and have no issues to speak of. I say go for it.
Sent from my Pixel XL using Tapatalk
nellycruzz said:
So by unlocking the bootloader, I won't run into problems taking official updates?
Click to expand...
Click to collapse
FYI If phone is a Verizon version an on 7.1.1 you are able to unlock it. If you update beyond 7.1.1 without unlocking you will Never be able to unlock it. If it's a Google version no worries.
There's no reason to unlock the bootloader if you're not rooting. That's just introducing a security issue. The Oreo update is safe and stable to install. You're good to go on hitting that update button.
asj0422 said:
There's no reason to unlock the bootloader if you're not rooting. That's just introducing a security issue. The Oreo update is safe and stable to install. You're good to go on hitting that update button.
Click to expand...
Click to collapse
I disagree. On rare occasion, the OTA update can cause issues, and with a locked bootloader you are unable to install an image. Even if I don't root my devices, I still unlock the bootloader just so I can have the option of installing a factory image just in case something goes wrong.
Sent from my Pixel XL using Tapatalk
borxnx said:
I disagree. On rare occasion, the OTA update can cause issues, and with a locked bootloader you are unable to install an image. Even if I don't root my devices, I still unlock the bootloader just so I can have the option of installing a factory image just in case something goes wrong.
Click to expand...
Click to collapse
He's right though. Unlocking will lead to security issues and may take away the ability to use important apps. If he prioritizes functionality, then it's best to keep it locked but if he wants to tinker, it'll come with compromises.
Since he just bought it, I don't see why he couldn't just warranty it if an update goes wrong, which is extremely rare. From what I've seen from people with bricked devices, the majority of them were unlocked and tried to update using non-conventional ways.
Bootloaders are locked from factory for a reason, not for inconvenience.
I came across this post on GitHub
https://github.com/topjohnwu/Magisk/issues/2534
I wanted to ask if I should continue using root or just relock my phone ?
tanzeel.ahmed1306 said:
I came across this post on GitHub
https://github.com/topjohnwu/Magisk/issues/2534
I wanted to ask if I should continue using root or just relock my phone ?
Click to expand...
Click to collapse
Unlocking your bootloader and rooting your devices is a choice that you and only you can make. There are always risks when modifying your devices. When you unlock the bootloader on most devices it will void your warranty unless stated otherwise by the manufacturer.
When it comes to root access there is always a chance for things to stop working. That is why it is up to you to do your research and make an informed decision before taking any action.
To some people, including me, an unlockable bootloader and gaining root access over a device is a must. I am paying for it and I want to use my devices how I see fit.
If you are concerned about an issue that may arise because you have an unlocked bootloader and root access I always try to look at it from both sides. Why did I unlock the bootloader? Why did I root? Am I able to do what I intended to do or not?
Sent from my OnePlus HD1907 using XDA Labs
tanzeel.ahmed1306 said:
I came across this post on GitHub
https://github.com/topjohnwu/Magisk/issues/2534
I wanted to ask if I should continue using root or just relock my phone ?
Click to expand...
Click to collapse
I'm kinda in the same boat. While I don't use GPay that often (and I can currently use it through Magisk), occasionally it would be nice for it to work without issue. However, the main reason I root is so that I can manually edit my HOSTS file to block ads.
Like fast69mopar mentioned, it's an individual preference. What do you gain by unlocking the bootloader and rooting?
In my opinion, the OP7T is a fantastic phone right from the get-go. So was the OP6T. Both phones I used for almost a full week before unlocking and rooting.
Got the OP7T a month ago and was faced with the same decision. All phones since Samsung Galaxy I have rooted.
Decided not to root the OP7T. So far couldn't be happier. Maybe missed it once. Everything working without issue is nice.
As for Ads.
Built in Private DNS in Android 10 with dns.adguard.com works pretty damn good.
I'm rooted, using magisk and edxposed with aosip. Definitely no loss of function comparing to stock. I don't use Google pay, but Samsung pay, bank apps, snapchat, everything works. Currently magisk and edxposed could be hidden without any loss of function when it comes to bank or paying apps. I don't use Google pay but safety net passes just fine with my setup
fast69mopar said:
Unlocking your bootloader and rooting your devices is a choice that you and only you can make. There are always risks when modifying your devices. When you unlock the bootloader on most devices it will void your warranty unless stated otherwise by the manufacturer.
When it comes to root access there is always a chance for things to stop working. That is why it is up to you to do your research and make an informed decision before taking any action.
To some people, including me, an unlockable bootloader and gaining root access over a device is a must. I am paying for it and I want to use my devices how I see fit.
If you are concerned about an issue that may arise because you have an unlocked bootloader and root access I always try to look at it from both sides. Why did I unlock the bootloader? Why did I root? Am I able to do what I intended to do or not?
Click to expand...
Click to collapse
Thanks a lot for your response
I actually rooted because I wanted to use substratum themes and enable aux module in gcam. Apart from that no other reason.
So I guess I am not missing out on too much .
I actually unrooted my phone and relocked the bootloader.
But again thanks for the response!
I had unlocked the bootloader and tried a couple of custom ROMs a few months back but decided it isn't worth it because my main hindrance of adblocking is addressed using DNS and any unneeded app can be disabled using adb. On the flip side, I need Widevine L1 for Netflix/Prime and no custom ROM can offer that on the 7T.
Makes more sense to me to stay within the walled garden, especially with the higher risk brought about by rogue Android apps that are now far too prevelent. The mods too are not that much value adding than it was may be when I first started using custom ROMs nearly a decade ago.