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.
Related
Just got the phone a few hours ago and want to root it and install Xposed. But I'm not sure what's the best path.
So far it seems like VS98610B is an old version nobody is using and that if I root it, I won't be able to upgrade in the future without breaking the phone, is that correct?
If I go to "Check for new system update" it asks if I want to update to 11A. From what I understand from this post http://forum.xda-developers.com/showpost.php?p=64116024&postcount=362 is that I want to take the update, then after it installs that update, it should ask to update again to 13B? And that it is this 13B version that I root?
Am I able to unlock the bootloader on any of these versions? Why does it ask me to go to 11A instead of straight to 13B?
All I can say is that you are damn lucky and DO NOT update or flash a non 10B image of you have any desire to unlock the bootloader and use custom ROMs and such
DerekZ10 said:
Just got the phone a few hours ago and want to root it and install Xposed. But I'm not sure what's the best path.
So far it seems like VS98610B is an old version nobody is using and that if I root it, I won't be able to upgrade in the future without breaking the phone, is that correct?
If I got to "Check for new system update" it asks if I want to update to 11A. From what I understand from this post http://forum.xda-developers.com/showpost.php?p=64116024&postcount=362 is that I want to take the update, then after it installs that update, it should ask to update again to 13B? And that it is this 13B version that I root?
Am I able to unlock the bootloader on any of these versions? Why does it ask me to go to 11A instead of straight to 13B?
Click to expand...
Click to collapse
Just my opinion but holding for a bootloader unlock is pointless and no you can't unlock it on any version. I waited for a year for the note 4 to get root or unlocked and never did. As days pass it's less likely we will ever see it unlocked on the g4.
To root take the OTA and get to 13b then follow the root guide in the forums....with root, xposed, and a little debloat this phone is awesome!
Awesome.that's what I was looking for. If it's already been since june and nobody has cracked it, that's not looking too good. My only worry now is why it's not taking me straight to 13b? It will take me to 13b after 11a right?
Also where is a good up-to-date root thread? There's nothing stickied.
If someone is on the verge of cracking the bootloader, how do I root this version so I can holdout, without killing my ability to upgrade in the future?
I'm also really interested in getting the fm radio working.that was one of the deciding factors when getting the phone. I did not know that Verizon crippled it.
EDIT: Also what's the benefit to upgrading? 10B is already android 5.1 so what is gained?
DerekZ10 said:
I'm also really interested in getting the fm radio working.that was one of the deciding factors when getting the phone. I did not know that Verizon crippled it.
EDIT: Also what's the benefit to upgrading? 10B is already android 5.1 so what is gained?
Click to expand...
Click to collapse
I never ran on 10B, so I don't know what benefits there were going to 11, however, 11 to 13b saw major improvements to touch responsiveness for most people (I never had touch issues on my phone, so I don't know on that count, but maybe I just never noticed); I also found that the phone performs a lot better and the battery lasts a bit more.
ericralph said:
All I can say is that you are damn lucky and DO NOT update or flash a non 10B image of you have any desire to unlock the bootloader and use custom ROMs and such
Click to expand...
Click to collapse
The rumored unlocked bootloader is vaporware. There has been no update on the status of it, especially for the Verizon variant. See here: http://forum.xda-developers.com/g4/general/unlock-unofficial-bootloader-unlock-t3222737
I've already considered of foregoing the mythical v0 unlock bootloader (VS98610B firmware, aka 10B) and move up to VS98613B rooted to enjoy all the fixes to the phone. No point of waiting any longer without any updates.
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 spent a little time browsing around, and I didn't seem to find any straight answers anywhere. I just got my Pixel XL on Verizon, running NDE63P.
Is this build number compatible with dePixel8? I'd like to unlock this bootloader and root the phone before I lose all chance to in the future. On top of that, if it is compatible with dePixel8, where would I find a guide to download fastboot and adb? How would I know if it's working properly with my phone?
Please and thank you to anyone that helps me out here. Again, been out of the Android scene since the S4.
Anthony825 said:
I spent a little time browsing around, and I didn't seem to find any straight answers anywhere. I just got my Pixel XL on Verizon, running NDE63P.
Is this build number compatible with dePixel8? I'd like to unlock this bootloader and root the phone before I lose all chance to in the future. On top of that, if it is compatible with dePixel8, where would I find a guide to download fastboot and adb? How would I know if it's working properly with my phone?
Please and thank you to anyone that helps me out here. Again, been out of the Android scene since the S4.
Click to expand...
Click to collapse
It still works to unlock bootloader on verizon pixel. Jcase said google didnt get the fix out in time for Nov security update so its still a go till Dec update. Adb minimal is at link below just updated on 10-22-16
http://forum.xda-developers.com/showthread.php?t=2317790
Awesome, I just got the bootloader unlocked. In the past with other android phones I've owned I was able to root only due to Verizon's ways. Now that I'm unlocked how would I go about getting SuperSU installed? Or whatever super user program is used for this phone?
Also, it popped up on my phone right before I unlocked it....Is it safe to install 7.1 updates? Will it relock my phone?
Anthony825 said:
Awesome, I just got the bootloader unlocked. In the past with other android phones I've owned I was able to root only due to Verizon's ways. Now that I'm unlocked how would I go about getting SuperSU installed? Or whatever super user program is used for this phone?
Click to expand...
Click to collapse
Root
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------
Anthony825 said:
Also, it popped up on my phone right before I unlocked it....Is it safe to install 7.1 updates? Will it relock my phone?
Click to expand...
Click to collapse
Updates will only affect root currently. I would update before you root but it's completely separate from whether the bootloader is locked or not.
Yea I found the root information and got it rooted last night. This morning I woke up though and realized I was having blue tooth issues which were causing me to lose connection to the Verizon network. Rebooted the phone and all is well.
Hi guys, I finally decided to replace my good old Galaxy S7 edge and I came to the conclusion that I wanted, after using Samsung, OnePlus and Sony phones for years, the most streamlined Android experience possible without having to deal with OEM bloat, delayed updates, etc. anymore.
Result: I made the most obvious choice and I got an unlocked white 128GB Pixel 2 XL from the Google Store directly (I can't wait to receive it!).
I have a few questions though...
1) Will unlocking the bootloader alone (without actually rooting the phone) cause OTA updates to fail?
2) It's now possible to root your phone with Magisk without installing a custom Recovery (TWRP). Once installed, Magisk allows you to temporarily restore the stock, unrooted "boot.img". Is it enough for OTA updates to install properly or will they fail as soon as Magisk has been installed, even if the stock boot.img has been restored?
3) Does the Pixel 2 have an "e-fuse" that will get triggered once the bootloader is unlocked that will cause features to not work properly anymore, like on Samsung phones?
4) Any other recommendations or things I should be aware of?
Thanks guys
Only other thing I would read up on is how to work around the whole dual slots "feature" that these Pixel phones have. The last couple times I've tried to update to the latest security update, I get a "your device is corrupt and cannot be trusted" message and the phone won't boot. I end up have to scramble to flash stock boot.img to both slots A and B, flash the factory image to both slots, and hold my breath as to whether or not it's going to work. I wish there was an idiot's guide to updating firmware for this phone. Everyone that posts on this subject has a different opinion on how to do it properly. Going form any given security update rooted with Magisk, how does one update to the next month's firmware, without temporarily bricking the phone or wiping data? I've been unlocking phones and flashing custom roms since before Android was even invented. So I'm no stranger to this stuff, but it has become quite a production to keep up to date with this stuff.
Phazonclash said:
Hi guys, I finally decided to replace my good old Galaxy S7 edge and I came to the conclusion that I wanted, after using Samsung, OnePlus and Sony phones for years, the most streamlined Android experience possible without having to deal with OEM bloat, delayed updates, etc. anymore.
Result: I made the most obvious choice and I got an unlocked white 128GB Pixel 2 XL from the Google Store directly (I can't wait to receive it!).
I have a few questions though...
1) Will unlocking the bootloader alone (without actually rooting the phone) cause OTA updates to fail?
2) It's now possible to root your phone with Magisk without installing a custom Recovery (TWRP). Once installed, Magisk allows you to temporarily restore the stock, unrooted "boot.img". Is it enough for OTA updates to install properly or will they fail as soon as Magisk has been installed, even if the stock boot.img has been restored?
3) Does the Pixel 2 have an "e-fuse" that will get triggered once the bootloader is unlocked that will cause features to not work properly anymore, like on Samsung phones?
3) Any other recommendations or things I should be aware of?
Thanks guys
Click to expand...
Click to collapse
To answer your questions.....
1. No
2. Yes. But you'll have to unroot and completely uninstall magisk to take the OTA.
3. No
4. There are several guides to explain how to unlock the bootloader, install twrp, kernels, and root. Let me know if you'd like links, or you can search on your own if you'd like. Welcome to the P2XL. We hope you enjoy your stay ??
Hey guys, been lurking until my device finally got here. I'm coming from an LG G3 (yes, I hold on to phones for a long time) which I was able to root pretty easily, so I am not unfamiliar with TWRP, backups, recovery, etc.
I got an unlocked US -01 variant that comes preloaded with Nougat 7.1.1. I haven't connected to a service provider yet. I have notification of a system update to NPSS26.118-24-6 which looks like the Sept 2017 security update.
I wanted to know if it was ok to OTA update and then root. I do want Oreo, but I don't know if that is available OTA in the US yet.
Also, do I still need to contact Motorola about unlocking the bootloader with the option to "OEM Unlocking" available in developer options?
Thanks everyone!
You can update normally before rooting but if you root, be aware that you could end up bricking the device if you try to update while being rooted.
I would suggest you read the guides here in XDA if you really need root, but be aware of problems that may appear.
Fixing a LG device is pretty easy compared to a Moto device.
Regarding unlocking the bootloader, you only need to follow the steps in the Moto site, they send you a code to unlock and everything.
victorhbm15 said:
You can update normally before rooting but if you root, be aware that you could end up bricking the device if you try to update while being rooted.
I would suggest you read the guides here in XDA if you really need root, but be aware of problems that may appear.
Fixing a LG device is pretty easy compared to a Moto device.
Regarding unlocking the bootloader, you only need to follow the steps in the Moto site, they send you a code to unlock and everything.
Click to expand...
Click to collapse
Thanks Victor. Like I said, I have been lurker around the forum for a while now. I think I have a pretty good grasp of the steps for the Z2 Play from a few sources. There just isn't quite a thorough and comprehensive guide or development like other phones I have had.
So I can OTA update and then root if I wanted to. I know never to OTA after rooting.
My LG crapped out on me. I think it's overheating. But you are correct, it is very easy to take apart and troubleshoot. I basically cooked the motherboard at 360 degrees F for 10 minutes in the oven and got it working again for about 4 weeks until it crapped out again.