Related
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.
Friend bought a used 5x from Swappa and it come with an unlocked bootloader, nbd. We flashed stock firmware and left it as is. He's happy.
Now that Android Pay/Safetynet is detecting his bootloader, he's not having any of it. Wants to lock the bootloader back up to restore AP functionality. I just want to confirm, 1.) this will wipe EVERYTHING on it, correct (I told him to get everything backed up)? And 2.), do I need to flash stock images before locking even though it's a bone stock 7.0 setup?
tallgrasshawk said:
Friend bought a used 5x from Swappa and it come with an unlocked bootloader, nbd. We flashed stock firmware and left it as is. He's happy.
Now that Android Pay/Safetynet is detecting his bootloader, he's not having any of it. Wants to lock the bootloader back up to restore AP functionality. I just want to confirm, 1.) this will wipe EVERYTHING on it, correct (I told him to get everything backed up)? And 2.), do I need to flash stock images before locking even though it's a bone stock 7.0 setup?
Click to expand...
Click to collapse
Never done it but to be safe I'd use a tool like this one.
http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444
tallgrasshawk said:
Friend bought a used 5x from Swappa and it come with an unlocked bootloader, nbd. We flashed stock firmware and left it as is. He's happy.
Now that Android Pay/Safetynet is detecting his bootloader, he's not having any of it. Wants to lock the bootloader back up to restore AP functionality. I just want to confirm, 1.) this will wipe EVERYTHING on it, correct (I told him to get everything backed up)? And 2.), do I need to flash stock images before locking even though it's a bone stock 7.0 setup?
Click to expand...
Click to collapse
There is a Heisenberg thread that will walk you thru it all. Download the image you want, factory reset while booted, auto reboot, bootloader, flash every file according to the thread, then fastboot OEM lock. Reboot and done. Don't lock until you flash every file.
Sent from my Nexus 5X using XDA-Developers mobile app
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
Im replacing my Pixel 6 Pro due to a bad accelerometer sensor. My phone is rooted with latest Magisk, has Kiri kernel installed as well. What's the most efficient way to prep the phone for a return to Google?
Official Google Android Flash Tool
and
Official Instructions for Locking/Unlocking the Bootloader
roirraW edor ehT said:
Official Google Android Flash Tool
and
Official Instructions for Locking/Unlocking the Bootloader
Click to expand...
Click to collapse
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Starzboy77 said:
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Click to expand...
Click to collapse
Yes. All of that.
Starzboy77 said:
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Click to expand...
Click to collapse
If you like, for further explanation, flashing the 100% official stock ROM will both remove root and overwrite whatever kernel you currently have with the stock kernel that's included in the stock ROM. If you choose any option anywhere (on that official stock flashing site of Google's, or via any other method) to *not* factory reset the phone, sure you'd have any root-oriented apps still installed on your phone, but the phone wouldn't be rooted because the stock kernel is 100% official now.
There are many ways to do the same thing, but this is the safest and 100% sure method that it's all stock. i.e. my answering this way isn't dependent on anything you've possibly done to your phone - if you or someone had gone out of the way to modify the software of the phone even more than typically, this method would still completely overwrite any changes you've done, because you're flashing the completely stock ROM.
I haven't used the Official Google Android Flash Tool but countless others in this section alone have reported their situations on their phones being saved by this method - even when flashing the stock ROM in only a slightly more manual way via the official Platform Tools had failed to solve their issues: manually downloading the stock firmware, extracting it, and running the flash-all.bat file included (if on Windows). Since I haven't used it myself, I'm just going by memory of what others have reported about using it and I'm under the impression that it gives you the choice to wipe (factory reset) or not wipe your phone when it flashes it.
I wouldn't be surprised if by default it wipes, as that's what the flash-all.bat script from the manual full factory image zip file does by default.
Also, heads up. You never want to lock the bootloader unless you are 100% certain the phone is 100% stock. Ergo, why even though there are other methods to unroot and "return to stock", there is no good reason to use them unless you just don't have access to a computer, or a cable, or it's some kind of unroot emergency or some other circumstance that calls for more manual methods - which also leave a greater chance for accidental human error and can just plain brick your phone - although that might not matter since you're returning the phone.
roirraW edor ehT said:
If you like, for further explanation, flashing the 100% official stock ROM will both remove root and overwrite whatever kernel you currently have with the stock kernel that's included in the stock ROM. If you choose any option anywhere (on that official stock flashing site of Google's, or via any other method) to *not* factory reset the phone, sure you'd have any root-oriented apps still installed on your phone, but the phone wouldn't be rooted because the stock kernel is 100% official now.
There are many ways to do the same thing, but this is the safest and 100% sure method that it's all stock. i.e. my answering this way isn't dependent on anything you've possibly done to your phone - if you or someone had gone out of the way to modify the software of the phone even more than typically, this method would still completely overwrite any changes you've done, because you're flashing the completely stock ROM.
I haven't used the Official Google Android Flash Tool but countless others in this section alone have reported their situations on their phones being saved by this method - even when flashing the stock ROM in only a slightly more manual way via the official Platform Tools had failed to solve their issues: manually downloading the stock firmware, extracting it, and running the flash-all.bat file included (if on Windows). Since I haven't used it myself, I'm just going by memory of what others have reported about using it and I'm under the impression that it gives you the choice to wipe (factory reset) or not wipe your phone when it flashes it.
I wouldn't be surprised if by default it wipes, as that's what the flash-all.bat script from the manual full factory image zip file does by default.
Also, heads up. You never want to lock the bootloader unless you are 100% certain the phone is 100% stock. Ergo, why even though there are other methods to unroot and "return to stock", there is no good reason to use them unless you just don't have access to a computer, or a cable, or it's some kind of unroot emergency or some other circumstance that calls for more manual methods - which also leave a greater chance for accidental human error and can just plain brick your phone - although that might not matter since you're returning the phone.
Click to expand...
Click to collapse
Thank you for the indepth explanation. Really appreciate it.
Just factory reset it so your data is wiped and send it back. Google has never cared about them being rooted when you return them.
TonikJDK said:
Just factory reset it so your data is wiped and send it back. Google has never cared about them being rooted when you return them.
Click to expand...
Click to collapse
Is this accurate? Can anyone else confirm? What about having a different kernel? Does the bootloader have to be locked?
Starzboy77 said:
Is this accurate? Can anyone else confirm? What about having a different kernel? Does the bootloader have to be locked?
Click to expand...
Click to collapse
As I said, you should not lock the bootloader unless the phone is 100% stock. To me, it doesn't matter what anyone else says about what Google cares about. If it were my phone, I'd restore it 100% stock too. 10 minutes of very little effort for some peace of mind. Rather than meh, they might not care, or meh you might be the unlucky exception. Why take the chance?
But it's your phone, your decision. No one else makes the decision for you.
roirraW edor ehT said:
As I said, you should not lock the bootloader unless the phone is 100% stock. To me, it doesn't matter what anyone else says about what Google cares about. If it were my phone, I'd restore it 100% stock too. 10 minutes of very little effort for some peace of mind. Rather than meh, they might not care, or meh you might be the unlucky exception. Why take the chance?
But it's your phone, your decision. No one else makes the decision for you.
Click to expand...
Click to collapse
This to the millionth degree. and it also goes for when purchasing a used device or a refurbished device. Reflash Android. they make it so simple now that it can be done using another phone. No PC necessary.
Flash Tool changed the game 3 years ago for how easy the process is. Heck I just reflash my phone monthly because it's such great technology (kidding, not kidding?)
My P6P (on T-Mobile) was working fine for me on the November release.
I did not sideload the December release.
With the January release, I started to notice significant radio issues.
I am seeing the same issue with the February release and after taking a look, I see that the radio has NOT changed between January and February. (But is a different radio from the November update)
I would definitely like to try flashing the November radio, but my Pixel bootloader is locked and can't be unlocked since it is still carrier locked. (I am working on that.)
In the meantime, is it possible for someone to make a custom OTA sideload package with just the November radio in it for those with locked bootloaders?
The 12L radio is different. I flashed it yesterday (12L factory image) and Signal is back to normal, and switching from Wifi to LTE/5G is much better than it's ever been on my 6 Pro. but its only been 24hours, but worth a try/
Good to know, but if I don't want to go 12L... again, could someone create a custom OTA sideload package with just the radio from 12L?
If this is even possible, which I'm dubious of, you might want to think twice. With a locked bootloader, your recovery options are more limited, so if someone creates such a custom OTA zip (again, if that's even possible to work with an unlocked bootloader), and something goes seriously wrong, it might be either more difficult or impossible to recover.
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
I just wanted to add, I tried flashing a different radio in December after flashing that image before it got pulled, and my phone wouldn't boot (but my bootloader was unlocked so I was able to save it but I wouldn't try it). I suggest you unlock your bootloader and flash 12L on both slots. That's what I did yesterday. Just kind of kill 2 birds with one stone by wiping, reflashing, and using a new build/radio (3 birds I guess?)
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
It depends on how badly things went wrong. I would hope so, too, but would be a bigger gambler than someone who has the bootloader unlocked in the same situation. But of course, if you had an unlocked bootloader, you could flash only the radio.img without any customization needed. But as @TonikJDK indicates, the question is effectively moot, anyway.
TonikJDK said:
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
Click to expand...
Click to collapse
Interesting. I didn't realize that was in place (signing of the various components such as radio+recovery+bootloader+image), and that the checking was disabled as part of the bootloader being unlocked.
chp said:
and that the checking was disabled as part of the bootloader being unlocked.
Click to expand...
Click to collapse
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
roirraW edor ehT said:
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
Click to expand...
Click to collapse
Ah yes, you're right. I was overthinking it. The sideload OTA does have a cert, so without the private key, we wouldn't be able to create a new cert to match the custom OTA contents.
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
NippleSauce said:
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
Click to expand...
Click to collapse
Thanks. I've been with Android and Pixel/Nexus for a long time, and other than needing to brush up, I'm still familiar with the ins-and-outs to flashing, etc.
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Since my radio issues started with the January update, I was hoping the February update would fix things. At first it did seem better, but then the poor behavior returned. And when I realized that the radio was unchanged in February from January, that explained things.
chp said:
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Click to expand...
Click to collapse
I feel ya. That's partially why I started buying my phones from the company that makes them (and also because my phone carrier stopped offering any interesting upgrades after being with them for a few years lol). But supposedly, a quick text chat with a T-Mo representative via the T-Mobile app can get your device carrier unlocked via the SIM card if you're polite with the whole thing and ask the right questions. I'm not sure if anything specific needs to be asked or stated, but you could always give that a shot. I just quickly skimmed through a post from someone who did that the other day but I didn't give it too much thought since my device is factory unlocked.
But I wish you the best of luck with your phone service!