Hello,
I own the 32gb h791 nexus 5x and the phone is bootlooping after android 7.0 update.
so basicly the phone showing google logo and then reboot back..
My bootloader is unlocked, so I tried to flash marshmellow without any success.
I can not access the recovery.
I saw a thread about flashing tot but i read in the thread that It is re lock the bootloader.
I dont have efs backup..
Any help?
Thanks,
Nimrod
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
But that's a hardware bootlop no software
How many files had been flashed when you've tried to flash it? If any, have you done any modifications like root etc ?
If no, just lock bootloader and send RMA
If you can send to Google, you don't have to lock bootloader.
If your warranty expired, try to talk to Google may they will give you a replacement anyway, if not Google, you can try to LG because of 15mo warranty from production date
TypNguy said:
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
Click to expand...
Click to collapse
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
His problem is a hardware issue not software. Might get lucky and volte it back to life but I highly doubtful . LG notorious for certain models that infinite bootloop issue g4 was the worse.
Yes, the root toolkit worked for me. I still don't know how to flash correctly, so if you have the right driver's associated with your phone/laptop it should be a breeze. The best part is that there's a log, so you know what the toolkit is doing. For example, it may unroot your phone before it flashes the new stock image for you.
---------- Post added at 02:40 AM ---------- Previous post was at 02:36 AM ----------
Just found wugfresh's answer to your question I think.
Link
Address: http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
Related
http://forum.xda-developers.com/showthread.php?p=63255820
Sent from my VS986 using Tapatalk
Has anyone had luck doing this yet? When I get home from work I'm going to try it. I'll put together a walk-through guide with screenshots if I do.
chubbrock said:
http://forum.xda-developers.com/showthread.php?p=63255820
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
The user "jesssiii" reposted the download link since it was encrypted and others in the thread were having problems downloading.
Here's his new post with the corrected link: http://forum.xda-developers.com/showpost.php?p=63262160&postcount=231
I think you have to be on official 12A to push the rooted 12a over, but not 100% sure. Also, if you're still on 10b, I'd hold off on any Ota because bootloader unlock is rumoured to be available soon!
Sent from my VS986 using Tapatalk
chubbrock said:
I think you have to be on official 12A to push the rooted 12a over, but not 100% sure. Also, if you're still on 10b, I'd hold off on any Ota because bootloader unlock is rumoured to be available soon!
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
if you are on 11a then you are on v1
they are saying if you are on v0 you are the only one who would be getting the bootloader unlock right now.
11a has been out long enough for them to kow if v1 would work.
cmsjr123 said:
11a has been out long enough for them to kow if v1 would work.
Click to expand...
Click to collapse
I agree with that. I think they should be able to pull it off for us on 11a. I'm patient and I knew it would happen soon like the g3 bump. Just wait and watch....? just give it time they will unlock this phone
Sent from my VS986 using Tapatalk
chubbrock said:
I think you have to be on official 12A to push the rooted 12a over, but not 100% sure. Also, if you're still on 10b, I'd hold off on any Ota because bootloader unlock is rumoured to be available soon!
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
krazy_smokezalot said:
I agree with that. I think they should be able to pull it off for us on 11a. I'm patient and I knew it would happen soon like the g3 bump. Just wait and watch.... just give it time they will unlock this phone
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Thing is if they knew 11a would work i bet they would have said it.
12a is out already...
11a has been out for what 2 months now? they would know
If anyone has successfully used the rooted 12a image and had the phone boot correctly with no issues, please post. The rest of us need to know if it's worth the risk.
I was on rooted 11a, had to restore to stock 11a to take the OTA and went to 12a. I used the root injection method (pulled stock sys img, injected root and reflashed image) and everything is working very well. I have all the fixes of 12a plus root. However a factory reset does not lose root. Since I can't KDZ back to 11a without bricking my phone (hurry up 12a KDZ) I held the pwr+vol- buttons to get to LGs recovery screen and chose factory data reset. It resets everything to default like it came out of the box (starts at the setup wizard) but I still have root with SU app installed. For those who are hesitant, the instructions in the thread of root injection are really easy. I just downloaded Ubuntu ISO, burnt it to DVD and booted from DVD. Or just download a prerooted 12a image from one of the threads. Remember that if you want to go back to unrooted stock, save a copy of your own stock system image before you flash a rooted one since the only other way to get back to factory unrooted stock will be whenever a 12a KDZ is release.
This will not work. I've said this in the other threads. You cannot copy over a mismatched system image that differs from the bootloader. The actual OTA will update the bootloader to V2 and this will work.
If you are on 11A (like we all are) then this will result in a nice little Error message that the system image is corrupt and will just turn off until you flash a matching system image that matches the bootloader.
So THIS WILL NOT WORK. I've tried. Many times. Trust me.
Also the 12A update has been pulled because it will stop app updates while on wifi (no notifications while on WiFi). It is a huge bug and thus the update has been pulled. Even if we could flash this, you don't want to flash this.
Update: Only people who took the OTA can flash this rooted 12A system image. Everyone else has to wait for a fix.
player911 said:
This will not work. I've said this in the other threads. You cannot copy over a mismatched system image that differs from the bootloader. The actual OTA will update the bootloader to V2 and this will work.
If you are on 11A (like we all are) then this will result in a nice little Error message that the system image is corrupt and will just turn off until you flash a matching system image that matches the bootloader.
So THIS WILL NOT WORK. I've tried. Many times. Trust me.
Also the 12A update has been pulled because it will stop app updates while on wifi (no notifications while on WiFi). It is a huge bug and thus the update has been pulled. Even if we could flash this, you don't want to flash this.
Update: Only people who took the OTA can flash this rooted 12A system image. Everyone else has to wait for a fix.
Click to expand...
Click to collapse
Am I the only one who HASN'T experienced this wifi push notification bug? Things are running really well for me. I was shipped a replacement phone about 10 days ago though, but it did still come with 11a on it.
Edit: Actually let me take that back, snaps are only coming in over 4g. Weird. I guess I'll wait for an official fix as well. Until then the other issues were fixed anyway.
IPV6 appears to be causing the notification bug
I read on Android Authority that it's an IPV6 bug. Disable IPV6 (or wait for a new build) and notifications should work.
http://forums.androidcentral.com/lg-g4/592446-new-verizon-g4-update-4.html
xgerryx said:
I was shipped a replacement phone about 10 days ago though, but it did still come with 11a on it.
Click to expand...
Click to collapse
Damn, I bricked mine using 11A KDZ after updating to 12A. Was hoping my replacement tomorrow would be back on 10.
jesssiii said:
Damn, I bricked mine using 11A KDZ after updating to 12A. Was hoping my replacement tomorrow would be back on 10.
Click to expand...
Click to collapse
It COULD but at this point, unless they just shipped you one from the Verizon store, it'll probably have 11a. Considering the weird recall thing that Sprint had that I saw in another thread, I wouldnt be surprised if it came with 12a.
player911 said:
This will not work. I've said this in the other threads. You cannot copy over a mismatched system image that differs from the bootloader. The actual OTA will update the bootloader to V2 and this will work.
If you are on 11A (like we all are) then this will result in a nice little Error message that the system image is corrupt and will just turn off until you flash a matching system image that matches the bootloader.
So THIS WILL NOT WORK. I've tried. Many times. Trust me.
Also the 12A update has been pulled because it will stop app updates while on wifi (no notifications while on WiFi). It is a huge bug and thus the update has been pulled. Even if we could flash this, you don't want to flash this.
Update: Only people who took the OTA can flash this rooted 12A system image. Everyone else has to wait for a fix.
Click to expand...
Click to collapse
The system image doesn't care about the boot loader. The system image isn't working because the boot image (the kernel) doesn't match. The system image may work if you also flash the boot image, but the older boot loader may not like the signature on the newer boot image.
And if you're only flashing the boot image and the system image, you could still kdz everything back to 11a or 10b (whichever you were on before), so if we can get a rooted 12A user to rip the system and boot, we may be able to get 12a without OTA
danaff37 said:
The system image doesn't care about the boot loader. The system image isn't working because the boot image (the kernel) doesn't match. The system image may work if you also flash the boot image, but the older boot loader may not like the signature on the newer boot image.
And if you're only flashing the boot image and the system image, you could still kdz everything back to 11a or 10b (whichever you were on before), so if we can get a rooted 12A user to rip the system and boot, we may be able to get 12a without OTA
Click to expand...
Click to collapse
You cannot KDZ back to an older version. Once you are on 12A, you are stuck with it. Apparently there is a trip timer that is stored in NAND. 12A is v2... so you can no longer run v0 (10A) or v1 (11A).
I am not saying it is impossible. We can get low level partition backups (like how we pull and push the system image for root). I just have not heard of anyone allowing backups or fixes yet.
I think once the Devs are able to bootloader unlock v0 devices, they will be able to pull bits and pieces from other sections of the devices and work from the other side of the wall.
That's not what I'm saying... I'm saying if we get boot partition and system partition from 12a, we may be able to run them on 10/11b boot loader. Without having to ota
danaff37 said:
That's not what I'm saying... I'm saying if we get boot partition and system partition from 12a, we may be able to run them on 10/11b boot loader. Without having to ota
Click to expand...
Click to collapse
I get what you're saying but I do not think that is possible, at least not at this time. If it was, we would all be on 10A right now.
Maybe once they release the bootloader unlock, they can pull additional information. The way I understand it is that all of the parts must match the same software revision number and that there is a NAND partition that keeps track of the version numbers. So once the NAND says "v2", everything else must match or else it throws a system error on boot.
Now if they can find a way to edit that NAND section and edit that to v0, then we can push over the v0 partitions and effectively flash back.
All we can do right now is stop accepting OTAs because the further we go, the less likely we will be able to recover.
A little off topic but I can't seem to find the original 12a update anywhere. I'm on stock 11a and I am trying to find the stock 12a update file so I can update and see what I can do about IPV6. Can someone please help me find the 12a stock update ota file?
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
anshuashmeet said:
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
Click to expand...
Click to collapse
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Flippy498 said:
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Click to expand...
Click to collapse
Thanks for your reply!
I've submitted an enquiry form to them. Didn't know that service existed. Hopefully they have the RUU file that I need.
I did download the stock backup file from that link but I thought before I give it a go, I'll try and get an OTA and get an official update. That failed so I decided to flash the firmware before going to the latest rom. Forgetting I just locked my bootloader with stock recovery, completely unaware of this 5.1 developer option issue. My fault for not doing research, but I didn't know such issue could exist as for the last few years, I haven't had an issue like this. Normally issues occur if I flash a newer ROM without firmware so was trying to avoid that.
Hello all!
I've gotten too lazy to maintain updating my rooted Pixel XL whenever there's a security patch.
I've re-locked the boot-loader and done a full stock flash from google's stock images, but now i get this warning when it boots up:
"Your device has loaded a different operating system. "
It then boots up fine, barring the fact OTA's still fail, the one thing I was trying to get working.
Any advice?
Thanks in advance.
You skipped flashing the bootloader and radio without those ota will fail.
Am i mistaken in thinking the "flashall.bat" from google does that as well?
Thanks
Edit.
Think i found it, your comment made me watch for the radio and boot-loader when i tried the flash-all batch script again, I believe i Locked the boot-loader before flashing it to stock again.
Unlocked, flashed, re-locked and it appears to be working now.
Thanks!
Help me
Vacross said:
Am i mistaken in thinking the "flashall.bat" from google does that as well?
Thanks
Edit.
Think i found it, your comment made me watch for the radio and boot-loader when i tried the flash-all batch script again, I believe i Locked the boot-loader before flashing it to stock again.
Unlocked, flashed, re-locked and it appears to be working now.
Thanks!
Click to expand...
Click to collapse
Can you help me... I have same problem...
DR3W5K1 said:
You skipped flashing the bootloader and radio without those ota will fail.
Click to expand...
Click to collapse
Can you pls explain on how to do that
Follow the guide for flashing stock images via fastboot and you shouldn't have this problem.
Stop after step 4
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I also had the same issue on Nexus 6p.. after I realised that I forgot to flash boot.img from stock firmware.. anyway it is resolved...
UI Design Services with Compelling and Engaging User-Experience
Get user-centered UI Design for your mobile app or website.
UI Design services
Hey there Xda.
So basis what happened was I wanted to try and test "SlimDesire" and flashed I'm TWRP before realizing it wasn't boot able yet. But when I return to TWRP all of my backup partitions were gone except /data. So I thought flashing the unlocked version would at least get it blogging. So I Flashed the system.img and boot.img. It took forever to boot but mobile network said service unavailable. The device wouldn't stop randomly rebooting.
So very noobly decided to SUPERCID and change my MID to the T-Mobile variant and flashed the entire RUU in windows. It changed everything. Now my Model is an A16ul instead of A16wl. It also installed the HBOOT and everything else. Mobile network still not there. Still random reboots.
So I know there is absolutely no stock software that is available. So I was thinking of compiling from the HTC Kernel Source available. But I've never done it. Can you guys help me get everything installed and ready to go? I'll post a stock ROM thread when I can get started.
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