Develop Bugs

Need Help - New to this

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.

Is it safe to relock the bootloader in the current update?

Hi guys, a while back I unlocked my bootloader since I wanted to root, however, I decided to change my mind and never rooted or did anything. So my bootloader is unlocked, and I do not see the need to root or install a rom. I am stock. Security patch Sep 5 on Android 8.0.0.
If it's safe, how do I proceed to relock the bootloader? thanks again, and sorry if this question gets asked a lot, I did some research but everything I found was not up to date. Thanks.

I got a little impatient and decided to just go ahead and try it.
Yes it's safe. Just make sure you dfidnt install roms or rooted your phone.
https://www.youtube.com/watch?v=7H79ooWiAso
Watched that video and did his steps and everything turned out OK!
Now I can use Android Pay!

Couldn't you have used Android pay with SUhide, while still maintaining the benefits of an unlocked bootloader/root privileges?
For me, an unlocked bootloader is a security blanket I'm not willing to give up easily. If my phone decides to go into boot loop tomorrow I can just restore a nandroid or reflash the latest factory images from Google....with my bootloader locked Im pretty much out of luck.

Pain-N-Panic said:
Couldn't you have used Android pay with SUhide, while still maintaining the benefits of an unlocked bootloader/root privileges?
For me, an unlocked bootloader is a security blanket I'm not willing to give up easily. If my phone decides to go into boot loop tomorrow I can just restore a nandroid or reflash the latest factory images from Google....with my bootloader locked Im pretty much out of luck.
Click to expand...
Click to collapse
So true.. thats why the Verizon version is trash
Sent from my Nexus 6 using Tapatalk

Pain-N-Panic said:
Couldn't you have used Android pay with SUhide, while still maintaining the benefits of an unlocked bootloader/root privileges?
For me, an unlocked bootloader is a security blanket I'm not willing to give up easily. If my phone decides to go into boot loop tomorrow I can just restore a nandroid or reflash the latest factory images from Google....with my bootloader locked Im pretty much out of luck.
Click to expand...
Click to collapse
Exactly, having an unlocked bootloader helped me out greatly when my nexus 6p got stuck in a bootloop. No need to relock unless you are sending it back to Google for an RMA and even then you don't have to. Cheap insurance. It is the first thing that I did when I got my Pixel XL.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
titaniums4 said:
I got a little impatient and decided to just go ahead and try it.
Yes it's safe. Just make sure you dfidnt install roms or rooted your phone.
https://www.youtube.com/watch?v=7H79ooWiAso
Watched that video and did his steps and everything turned out OK!
Now I can use Android Pay!
Click to expand...
Click to collapse
If Android Pay is so important to you all you have to is install Magisk 14.2.

Need unlocked bootloader to install Magisk?
mochamoo said:
Exactly, having an unlocked bootloader helped me out greatly when my nexus 6p got stuck in a bootloop. No need to relock unless you are sending it back to Google for an RMA and even then you don't have to. Cheap insurance. It is the first thing that I did when I got my Pixel XL.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
If Android Pay is so important to you all you have to is install Magisk 14.2.
Click to expand...
Click to collapse
As far as I know, you still need to unlock the boot loader to install Magisk.
I tried to install both TWRP recovery and Magisk at different times as an experiment and, I was not able to install either until I unlocked the bootloader which make sense.
TWRP replaces the stock recovery and Magisk modifies the boot image. Thus, you are not able to modify any of the partitions with a locked bootloader so, the boot loader needs to be unlocked.
Regards

Never ever relock the bootloader. Unless you're ok with bricks.

Phalanx7621 said:
Never ever relock the bootloader. Unless you're ok with bricks.
Click to expand...
Click to collapse
Seconded. Install Magisk if you need Google Pay.

Just bought a Pixel on 7.1.1, safe to update to 8.0?

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.

Return One plus in stock origin

Hello, I have a One plus 5, rooted, with bootloader unlocked, decrypted and with xxx_limits rom, the last one.
Now I want to sell it and I want return the phone like new, with unroot, with bootloader locked, crypted and stock firmware.
I try before but I brick the phone and I reput the rom. Now it works.
But how can I do? Which are the steps to follow?
Thank you very much for your time

maxvim03 said:
Hello, I have a One plus 5, rooted, with bootloader unlocked, decrypted and with xxx_limits rom, the last one.
Now I want to sell it and I want return the phone like new, with unroot, with bootloader locked, crypted and stock firmware.
I try before but I brick the phone and I reput the rom. Now it works.
But how can I do? Which are the steps to follow?
Thank you very much for your time
Click to expand...
Click to collapse
Post the same in the help and trouble shooting section. You have guide posts/threads. You have posted in the wrong section currently.

Unrooting a partially rooted Pixel 2 XL

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