Related
Hey all,
I caught wind of the 4.4.2 update, so I decided to see how it is. I had used saferoot to gain root access to it, but all I did was use Xposed to modify my phone. No recoveries or anything, and the warranty bit is 0 on the download mode screen. Just to be safe, I wiped data/factory reset to make sure everything was gone, then I started the OTA download. All goes as it should until it reboots to install it, where it gets stuck at 25%, then says "update failed". Phone reboots, and then a window pops up saying the update was interrupted. Anyone else having this issue? Anyone know any workarounds? Because if this phone just won't update, there it no reason for my to keep my warranty bit, since I have less than a week on the warranty left anyhow.
TH3F4LL3N said:
Hey all,
I caught wind of the 4.4.2 update, so I decided to see how it is. I had used saferoot to gain root access to it, but all I did was use Xposed to modify my phone. No recoveries or anything, and the warranty bit is 0 on the download mode screen. Just to be safe, I wiped data/factory reset to make sure everything was gone, then I started the OTA download. All goes as it should until it reboots to install it, where it gets stuck at 25%, then says "update failed". Phone reboots, and then a window pops up saying the update was interrupted. Anyone else having this issue? Anyone know any workarounds? Because if this phone just won't update, there it no reason for my to keep my warranty bit, since I have less than a week on the warranty left anyhow.
Click to expand...
Click to collapse
Did you try re-downloading it?
BWolf56 said:
Did you try re-downloading it?
Click to expand...
Click to collapse
This is my 3rd attempt to re-download it. It's currently at 94%, so I'll let you know how it goes.
TH3F4LL3N said:
This is my 3rd attempt to re-download it. It's currently at 94%, so I'll let you know how it goes.
Click to expand...
Click to collapse
After my 3rd attempt, without my sd card inserted this time, the update failed again! This is starting to get irritating. Maybe I should just flash CM11 or something like that.
TH3F4LL3N said:
After my 3rd attempt, without my sd card inserted this time, the update failed again! This is starting to get irritating. Maybe I should just flash CM11 or something like that.
Click to expand...
Click to collapse
It's kinda odd that it still fails after so many downloads (and so close to being complete).
If there's only a week left to your warranty, you can start looking at custom ROM you might like (AOSP or TW). By the time you find one you really like and understand how to flash it (without any issue), you will have time to give the OTA another shot. Will be some good knowledge reading in the meantime
Little advice: Don't flash a custom ROM while annoyed/mad. That's how 80% of bricks happen.
BWolf56 said:
It's kinda odd that it still fails after so many downloads (and so close to being complete).
If there's only a week left to your warranty, you can start looking at custom ROM you might like (AOSP or TW). By the time you find one you really like and understand how to flash it (without any issue), you will have time to give the OTA another shot. Will be some good knowledge reading in the meantime
Little advice: Don't flash a custom ROM while annoyed/mad. That's how 80% of bricks happen.
Click to expand...
Click to collapse
Ok thanks for the advice, mate. I heard if I take it to Best Buy, they can update it. Do you know if it's free?
TH3F4LL3N said:
Ok thanks for the advice, mate. I heard if I take it to Best Buy, they can update it. Do you know if it's free?
Click to expand...
Click to collapse
Imo it should be but you can always give them a call to make sure.
Just make sure you aren't rooted when going there lol.
BWolf56 said:
Imo it should be but you can always give them a call to make sure.
Just make sure you aren't rooted when going there lol.
Click to expand...
Click to collapse
Haha I know the basics of rooting. If I go, my phone will be the way it is right now: stuck on stock 4.3 with nothing on it but the bloatware from Sammy and AT&T
TH3F4LL3N said:
Haha I know the basics of rooting. If I go, my phone will be the way it is right now: stuck on stock 4.3 with nothing on it but the bloatware from Sammy and AT&T
Click to expand...
Click to collapse
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Yea when you modify the system at all it trips the modified flag and that's probably where its failing (not the warranty bit flag that's at 0 but the one that's in the system itself) try to Odin to full stock and try it again this should revert it back to official
Sent from my ATT Samsung Galaxy SIII using TapaTalk
TH3F4LL3N said:
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Click to expand...
Click to collapse
You need to run Triangle Away whiule rooted to change it back to official
audit13 said:
You need to run Triangle Away whiule rooted to change it back to official
Click to expand...
Click to collapse
Will this work for 4.3?
I never tried it on 4.3, only on 4.1.2. Since you have Knox, rooting and installing SU may trip the knox counter. Did you try uninstalling Xposed and running the update?
TH3F4LL3N said:
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Click to expand...
Click to collapse
crazymonkey05 said:
Yea when you modify the system at all it trips the modified flag and that's probably where its failing (not the warranty bit flag that's at 0 but the one that's in the system itself) try to Odin to full stock and try it again this should revert it back to official
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
One thing, don't downgrade bootloaders doing so. That will result in a brick.
audit13 said:
I never tried it on 4.3, only on 4.1.2. Since you have Knox, rooting and installing SU may trip the knox counter. Did you try uninstalling Xposed and running the update?
Click to expand...
Click to collapse
I have, and I've wiped the phone at least 3 or 4 times!
BWolf56 said:
One thing, don't downgrade bootloaders doing so. That will result in a brick.
Click to expand...
Click to collapse
How would I go about this? I have the stock 4.1.1 tar file, and I can't get the 4.3 file because AT&T's update was OTA only, and I can't find the 4.3 tar file anywhere!
TH3F4LL3N said:
I have, and I've wiped the phone at least 3 or 4 times!
How would I go about this? I have the stock 4.1.1 tar file, and I can't get the 4.3 file because AT&T's update was OTA only, and I can't find the 4.3 tar file anywhere!
Click to expand...
Click to collapse
Is your current baseband LK3? If so, 4.1.1 should be fine.
BWolf56 said:
Is your current baseband LK3? If so, 4.1.1 should be fine.
Click to expand...
Click to collapse
I am in the about device section of the settings, and it says the baseband version is I747UCUEMJB. Is this the right one?
TH3F4LL3N said:
I am in the about device section of the settings, and it says the baseband version is I747UCUEMJB. Is this the right one?
Click to expand...
Click to collapse
That would be the 4.3. You can't downgrade from those bootloaders. Therefor, you need stock 4.3
BWolf56 said:
That would be the 4.3. You can't downgrade from those bootloaders.
Click to expand...
Click to collapse
Well that's just great. I'm stuck on 4.3. Could I possibly flash something like CM11 to get to kitkat? Of course, I'd like to back up the stock rom in case something goes wrong, but it would be wonderful if I could use CM on my phone again! I used the saferoot method to gain root access in the first place, which disabled KNOX if that means anything.
TH3F4LL3N said:
Well that's just great. I'm stuck on 4.3. Could I possibly flash something like CM11 to get to kitkat? Of course, I'd like to back up the stock rom in case something goes wrong, but it would be wonderful if I could use CM on my phone again! I used the saferoot method to gain root access in the first place, which disabled KNOX if that means anything.
Click to expand...
Click to collapse
Yes you can, it's fairly simple too. Just gotta follow their instructions (don't skip anything).
As for recovery, I recommend TWRP, which you can get on the Play Store.
Hi, i have some kind of problem with my nexus 7 2013.. I already have lollipop 5.1.1 official on my tablet and have root and unlocked bootloader (root with king root, yes it works and is rooted.. And bootloader unlocked with boot unlocker.. I know you might think that this are not the best way of rooting or unloking the bootloader but it worked for me and im happy) and since yesterday the tablet keeps telling me to update via OTA the 5.1.1 update witch i already have..i press update to install it as normal, it reboot as normal too and when it shows me the parte where it suppose to be installing the update (you know, with the android with the chest open part) the only thing that says is "error" it doesn't install anything..i did this like 3 times now and every one of them says error.. The annoying part is that it keeps showing me the notification to update it..so any solutions? Thanks!
Sorry for bad english blah blah...
You can't take ota updates if you modify system files, you did that with root. Don't know why it's showing you 5.1.1 when you already have it.
Just flash the factory image with fastboot (probably no need to wipe, just flash boot.img and system.img and format cache).
That should fix the problem. It will also remove root. I'd recommend not using that king root **** but whatever. Probably better to just flash the su zip in twrp or use CF-Auto-Root.
When the next update comes remember you won't be able to take the ota. But that doesn't matter since google posts factory images and all you need to do is flash it with fastboot, then root again.
yosmokinman said:
YDon't know why it's showing you 5.1.1 when you already have it.
Click to expand...
Click to collapse
There's a new 5.1.1 = LMY48G
Original 5.1.1 is LMY47V
^Oh yeah, lol.
Still the rest of my post will get it installed for op.
So I have a Verizon Pixel XL that has been unlocked, TWRP alpha installed, and rooted....
How shall I update my build? Should I even update the build?
My goal is to have the latest update running on my system (manually flashing or OTA I don't care) with an unlocked rooted Pixel XL that can broadcast wifi natively.
I have everthing down except the update piece. Any advice?
You have TWRP and root? How is that working? I was reading that SuperSu needs an update to work with it. Also many people who have taken the OTA (or even flash full system image) are getting stuck in the bouncing balls boot loop. I would hold off on updating. No real major changes as of yet.
Twrp is working fine but I have nothing to flash to test...????
networx2002 said:
Twrp is working fine but I have nothing to flash to test...????
Click to expand...
Click to collapse
Yeah that is what I'm hinting at.... There is no updated ROM to work with TWRP yet that is updated to the latest Google Build
Root is working. I have twrp alpha 2. Root and elementalx 8 all installed. Although, im getting my daydream headset tomm. And when you install the app it tells you to check for updates. It says I have one. But if you look at the OTA updates NDE63 is the newest. Which im on. So I dn at this point. I guess i'll just roll with it for now. The dev that made purenexus that I ran on my nexus 6. Says hes working on it already and gets his on the 21st. So i'll just stick with what I have for now. I'm sure we'll see roms pretty soon
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
s1dest3pnate said:
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
Click to expand...
Click to collapse
jreink01 said:
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
Click to expand...
Click to collapse
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
DeathSentinels said:
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
Click to expand...
Click to collapse
If you edit the flash-all.bat file and take out the -w near the end you wont flash user data. So you can skip restoring your cloud backup and apps. Backup just to be safe though.
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
jreink01 said:
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
Click to expand...
Click to collapse
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
TonikJDK said:
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
Click to expand...
Click to collapse
OK, thanks, that's good to know. When I lose root, will that mess with any of my apps that need root to work like titanium backup? Or will I just need to grant it user privileges again? I have never done this particular process before so I am a little weiry. Do you know of a step by step guide to do this? Sorry but I would feel more comfortable that way. Thanks for all you help and feedback, it's been years since I last went through the rooting, flashing process so, I guess I am being extra cautious. I have/am learning by the feedback you have given me.
Sent from my Pixel XL using Tapatalk
I am rooted with TWRP RC1
i never sideloaded an OTA before, alway applied factory images. Too lazy, but tired of all the rework.
i folllowed,
https://9to5google.com/2016/12/05/how-to-sideload-android-7-1-1-nmf26o-onto-the-pixel/
no data loss.
just had to use fastboot to reinstall TWRP and reflash SUPERSU.
All is well.
If I choose to side load it, do I root and install TWRP the same way I did when I first did this, with ADB on my windows PC? And side loading will work with a new operating system (when it comes out) along with the monthly security updates? I just checked and my latest security update is from January. If I updated March's update, would that automatically have the February one with it?
---------- Post added at 02:10 AM ---------- Previous post was at 02:02 AM ----------
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
jreink01 said:
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
Click to expand...
Click to collapse
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
TonikJDK said:
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
Click to expand...
Click to collapse
Yes, I am in the beta program, that's why I am on this version. So, I'm assuming the beta's don't get updates then? I have turned off automatic updates since I'm rooted. Would you recommend I turn that back on or no? If I'm correct, I can't take a OTA since I'm rooted so I was correct in turning off automatic updates then? I will probably stay on this version since the difference is improvement and bug fixes. So, when 7.1.2 rolls out to everyone, then I would assume that that version would show up on the Google page then?
Sent from my Pixel XL using Tapatalk
Searched from 10pm to 7am, I give up. Refurbished phone came with the new CPG2, am I screwed?
The stock download mode doesn't seem to play with Odin, is there any way to downgrade to any other baseband for rooting, or even better, unlock this accursed bootloader?
I've seen hints, but no posts or threads with any definitive answers. Help me, Obi Wan, I'm so tired...
gingerbate said:
Searched from 10pm to 7am, I give up. Refurbished phone came with the new CPG2, am I screwed?
The stock download mode doesn't seem to play with Odin, is there any way to downgrade to any other baseband for rooting, or even better, unlock this accursed bootloader?
I've seen hints, but no posts or threads with any definitive answers. Help me, Obi Wan, I'm so tired...
Click to expand...
Click to collapse
****I think we're screwed. I've been trying to downgrade to 5.1.1 from the latest 6.0.1 for the last few hours and it seems to have borked my phone pretty bad. Hopefully reflashing the current firmware will fix it.****
Cancel that, I apparently just flashed the wrong file and its now downgraded to 5.1.1
Just need to use Odin to flash a older firmware and you should be good to go
ajohn7211 said:
****I think we're screwed. I've been trying to downgrade to 5.1.1 from the latest 6.0.1 for the last few hours and it seems to have borked my phone pretty bad. Hopefully reflashing the current firmware will fix it.****
Cancel that, I apparently just flashed the wrong file and its now downgraded to 5.1.1
Just need to use Odin to flash a older firmware and you should be good to go
Click to expand...
Click to collapse
May I ask what files you used? I was on 5.1.1 rooted until this morning when I tried to get to 6.0.1. No matter what I tried to do, my phone would not root. Tried KingRoot and KingORoot a bunch of times, and root checker always said that root was not successful. Then I got into a boot loop, so I ran the Verison repair utility and now I'm on the latest and greatest 6.0.1.
Even after the repair utility ran, when I reboot my phone, it still says "Custom", with the unlocked padlock on the boot screen.
I'd like to get back to 5.1.1. with root again and I'm fine with not having 6.0.1.
usmaak said:
May I ask what files you used? I was on 5.1.1 rooted until this morning when I tried to get to 6.0.1. No matter what I tried to do, my phone would not root. Tried KingRoot and KingORoot a bunch of times, and root checker always said that root was not successful. Then I got into a boot loop, so I ran the Verison repair utility and now I'm on the latest and greatest 6.0.1.
Even after the repair utility ran, when I reboot my phone, it still says "Custom", with the unlocked padlock on the boot screen.
I'd like to get back to 5.1.1. with root again and I'm fine with not having 6.0.1.
Click to expand...
Click to collapse
I'm in a similar boat, where i bought a Verizon Note2 phone that had android 6.0.1 N910VVRU2CPG2 when I got it. Has any one found any way to root/unlock bootloader so we can put a custom ROM on it?
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
This excellent guide by HomeBoy76 should give you all the info that you need....
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
It's actually pretty simple, just download the latest factory image of either Oreo,. Flash the flash all script included with fast boot. Afterward boot into the system without setting up a pin or password or anything, set it up, then reboot into boot loader and boot the latest TWRP, then within TWRP flash TWRP zip file and Magisk root. Reboot system.
Homeboy76 said:
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
Click to expand...
Click to collapse
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Hobocoe said:
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Click to expand...
Click to collapse
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Homeboy76 said:
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Click to expand...
Click to collapse
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Hobocoe said:
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Click to expand...
Click to collapse
You're welcome