Question Unbrick P6P with locked bootloader - Google Pixel 6 Pro

Hello,
I've recently switched to Android 13 B2 and after the restart required for 2.1, the phone immediately went into a bootloop.
Android Flasher requires the bootloader to be unlocked, which I can't do now as Oem unlocking was disabled in developer options. Pixel repair also doesn't work as it is not compatible with Android 13. (Your phone's current software version:TPBB.220414.015 is newer than what this repair tool has.)
Does anyone know how I can recover the phone? Thank you.

Hopefully you had USB debugging enabled could sideload an ota

fil3s said:
Hopefully you had USB debugging enabled could sideload an ota
Click to expand...
Click to collapse
I don't think he can. I'm almost positive that you need to have the bootloader unlocked to sideload any updates. If it's not unlocked then you are often close to SOL =(.

IonutP said:
Hello,
I've recently switched to Android 13 B2 and after the restart required for 2.1, the phone immediately went into a bootloop.
Android Flasher requires the bootloader to be unlocked, which I can't do now as Oem unlocking was disabled in developer options. Pixel repair also doesn't work as it is not compatible with Android 13. (Your phone's current software version:TPBB.220414.015 is newer than what this repair tool has.)
Does anyone know how I can recover the phone? Thank you.
Click to expand...
Click to collapse
1. have you have any chances that you still have warranty?
2. had you already went to recovery mode and wiped cache? if still not boot try wipe userdata?
edit: OP had solved the problem.

fil3s said:
Hopefully you had USB debugging enabled could sideload an ota
Click to expand...
Click to collapse
Thank you, much appreciated! I had this option enabled and was able to sideload the OTA from here https://forum.xda-developers.com/t/...e-with-a-new-predictive-back-gesture.4380119/.
Then I've enabled oem unlocking and flashed 12.1 with Android Flasher. Everything's back to normal now.

Related

How I can install the factory image 8.1 on Google pixel XL boot locked help please

hello could you help me install the system image in pixel xl 8.1, the bootloader can not unlock it when I want to select oem unlock in programmer settings oem unlock is in gray help please,sorry my English is bad but I try learn thanks
stell1234 said:
hello could you help me install the system image in pixel xl 8.1, the bootloader can not unlock it when I want to select oem unlock in programmer settings oem unlock is in gray help please,sorry my English is bad but I try learn thanks
Click to expand...
Click to collapse
I do not believe you can flash factory images on a device with a locked bootloader. You must unlock the bootloader to flash factory images. If you are attempting to move from 8.0 to 8.1, I believe your best, and perhaps only, options would be to either take the OTA through the normal process from within Android when it is offered to you or you may also be able to sideload the OTA by following the directions on the Google page linked here: https://developers.google.com/android/ota. Good luck!
S
sb1893 said:
I do not believe you can flash factory images on a device with a locked bootloader. You must unlock the bootloader to flash factory images. If you are attempting to move from 8.0 to 8.1, I believe your best, and perhaps only, options would be to either take the OTA through the normal process from within Android when it is offered to you or you may also be able to sideload the OTA by following the directions on the Google page linked here: https://developers.google.com/android/ota. Good luck!
S
Click to expand...
Click to collapse
Thank for your response I upgrade for ADB the ota 8.1 thanks :laugh:
because the factory images from google are properly signed you should be able to flash them with locked bootloader no problem.
lol nevermind, newer devices do require you to unlock bootloader to flash even factory images!?
https://developers.google.com/android/images
though official instructions tell you to re-lock after for security (don't do this if you installed root/supersu/magisk or anything else! lol)

How to install Hydrogen OS?

I've got a completely stock 5t that's running the last OTA (I believe it's 5.03). I'm interested in trying the Hydrogen OS variant, but wasn't able to flash the official ROM. I followed the instructions on OnePlus' website how to do it (tried both installing from stock recovery & the update installer), but the update failed.
Any suggestions? I thought if I was just switching from Oxygen OS -> Hydrogen OS I could update it from stock recovery, but it doesn't seem to be working.
1. Download HydrogenOS from http://www.h2os.com/download
2. Use TWRP to load it, see https://dl.twrp.me/dumpling/ for the 5T.
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery twrp.img
volume/power keys to boot into recovery mode
ClinicalTrack said:
1. Download HydrogenOS from http://www.h2os.com/download
2. Use TWRP to load it, see https://dl.twrp.me/dumpling/ for the 5T.
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery twrp.img
volume/power keys to boot into recovery mode
Click to expand...
Click to collapse
Oh, I didn't think I had to do all that since Hydrogen OS is a stock OS.
Thanks for the codes. Now, let's say I wanted OTA Hydrogen updates. It wouldn't work because the bootloader is unlocked, correct? So I'd basically do everything in reverse, such as 'fastboot oem lock' ? And flash the stock recovery? Speaking of which, how would one download the stock recovery -- I couldn't find a direct link to it.
Also, it's been awhile since I've paid attention to the android development stuff -- unlocking a bootloader will still allow me to encrypt the phone, so thieves can't access the data, correct?
Listerine said:
Now, let's say I wanted OTA Hydrogen updates.
Click to expand...
Click to collapse
I left my bootloader unlocked, and still received HydrogenOS OTA updates. It was quite annoying, actually.
Listerine said:
Unlocking a bootloader will still allow me to encrypt the phone, so thieves can't access the data, correct?
Click to expand...
Click to collapse
My phone was unlocked but fully encrypted. If you're worried about thieves, please consider putting a PIN on your SIM, thieves don't even need access to your device to use 2FA on your online accounts and take them over.

Android 8.1 with unlocked bootloader, update to Pie? What can I expect

I did some searching and I see the threads for unlocking and rooting 8.1 and 9 but couldn't find much reference to updating from 8.1 to 9 when I am already unlocked and rooted.
So if I accept the update Verizon is pushing down, is this going to basically lock the bootloader and unroot me back to stock essentially?
I just don't want to brick my phone because I am not comprehending some details I am reading in all these threads.
Just decided to go for it and see what happens..
after taking the OTA it restarted and bootloader still unlocked..
Android launched fine
had to reactivate Developer Options
OEM Unlock grayed out but says "Bootloader already unlocked" so that's good
Thanks for posting this. I'm assuming from your post that you're using the Verzon branded model?
I'm using the unlocked version on Verizon, and there's no way in hell I would take an OTA update. However, I'm about to update to 9 via image.
MuGGzyx said:
Just decided to go for it and see what happens..
after taking the OTA it restarted and bootloader still unlocked..
Android launched fine
had to reactivate Developer Options
OEM Unlock grayed out but says "Bootloader already unlocked" so that's good
Click to expand...
Click to collapse
Yes you'll be fine on Android P it give Verizon Pixel the option to unlock the boot loader
absolvi said:
I'm using the unlocked version on Verizon, and there's no way in hell I would take an OTA update. However, I'm about to update to 9 via image.
Click to expand...
Click to collapse
I'm back with an update. I used the Google notification on my rooted phone (Magisk/TW) to begin the installation. The update went okay, but custom recovery and Magisk root were wiped out. I was still able to use OEM Unlock to unlock the bootloader. The downside is, if I install custom recovery again I will lose access to my encrypted storage, meaning I'll have to reset my phone.
If your going to update, backup everything you can first; you'll need to reset.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
My advice has always been to never OTA update between Android versions, always better to fastboot flash a fresh image with a complete wipe of the system.

Question How to relock bootloader on Pixel 6 Pro

I have to return my old phone today and need to lock the bootloader back. I already did a factory reset which did not work. Could someone please give me the directions on how to relock it so I can get it sent off? Thanks.
Oaklands said:
I have to return my old phone today and need to lock the bootloader back. I already did a factory reset which did not work. Could someone please give me the directions on how to relock it so I can get it sent off? Thanks.
Click to expand...
Click to collapse
Haven't done it in a while but I'm sure it's the same. Go into fastboot and make sure the device is recognized with "fastboot devices" then " fastboot flashing lock " and it will wipe device and reboot.
bobby janow said:
Haven't done it in a while but I'm sure it's the same. Go into fastboot and make sure the device is recognized with "fastboot devices" then " fastboot flashing lock " and it will wipe device and reboot.
Click to expand...
Click to collapse
Thank you. I will give it a try.
That did not do it. What I tried was flashing the Raven Rom again with a standard flash-all.bat.
The bootloader was still locked then I ran the "fastboot flashing lock" command and it worked.
Oaklands said:
That did not do it. What I tried was flashing the Raven Rom again with a standard flash-all.bat.
The bootloader was still locked then I ran the "fastboot flashing lock" command and it worked.
Click to expand...
Click to collapse
Maybe this isn't up to date, then? Weird. Not so uncommon if it is out of date, but it's such a big thing I would expect it to be up to date. You're using the latest Platform Tools, correct? I'm confused because you start the first sentence "That did not do it" but then say "and it worked" at the end, so I'm missing something.
https://source.android.com/setup/build/running#relocking-the-bootloader
Re-locking the bootloader​To re-lock the bootloader:
For newer devices (2015 and higher):
fastboot flashing lock
For older devices (2014 and lower):
fastboot oem lock
Note: Re-locking the bootloading on a
Click to expand...
Click to collapse
You could also try the flashing tool from Google that makes it extremely easy. Before you flash you can choose to lock the bootloader as one fo the options. https://flash.android.com/welcome?continue=/back-to-public
liljq said:
You could also try the flashing tool from Google that makes it extremely easy. Before you flash you can choose to lock the bootloader as one fo the options. https://flash.android.com/welcome?continue=/back-to-public
Click to expand...
Click to collapse
This. Android Flash Tool is the #1 best option for returning to complete stock.
Select the "Wipe Device", "Lock Bootloader", and "Force flash all partitions" options. When the process completes, the device will be back to absolute factory.
roirraW edor ehT said:
Maybe this isn't up to date, then? Weird. Not so uncommon if it is out of date, but it's such a big thing I would expect it to be up to date. You're using the latest Platform Tools, correct? I'm confused because you start the first sentence "That did not do it" but then say "and it worked" at the end, so I'm missing something.
https://source.android.com/setup/build/running#relocking-the-bootloader
Click to expand...
Click to collapse
Just running the command he gave me did not work. The phone would not respond to locking the bootloader. I updated again using the standard .37 image with the -w command. The ran the "fastbopt flashing lock" command and it then responded fine.
V0latyle said:
This. Android Flash Tool is the #1 best option for returning to complete stock.
Select the "Wipe Device", "Lock Bootloader", and "Force flash all partitions" options. When the process completes, the device will be back to absolute factory.
Click to expand...
Click to collapse
I didn't know about this tool beforehand. I have unlocked and rooted a phone in a few years. It's like learning it all over again. I appreciate you letting me now about this.
Oaklands said:
I didn't know about this tool beforehand. I have unlocked and rooted a phone in a few years. It's like learning it all over again. I appreciate you letting me now about this.
Click to expand...
Click to collapse
This tool is specific to Pixel devices only and cannot be used with any other platform.
V0latyle said:
This. Android Flash Tool is the #1 best option for returning to complete stock.
Select the "Wipe Device", "Lock Bootloader", and "Force flash all partitions" options. When the process completes, the device will be back to absolute factory.
Click to expand...
Click to collapse
I concur!
Hello,
I did uninstall the magisk I had in my pixel 6 pro and now I don't have root, but now when I start the device I see lines at the boot about the fastboot so as I understand I should lock it for the OTA's of google, (is it right?)
So i saw here the command: fastboot flashing lock
or to use the google tool
https://flash.android.com/welcome?continue=/back-to-publicdoes the usage of the tool meaning that the device will be wiped? (I have the stock rom ->rooted -> uninstall magisk) and I want to be original with that stock to get updateds,
Thanks
I7210I said:
Hello,
I did uninstall the magisk I had in my pixel 6 pro and now I don't have root, but now when I start the device I see lines at the boot about the fastboot so as I understand I should lock it for the OTA's of google, (is it right?)
So i saw here the command: fastboot flashing lock
or to use the google tool
https://flash.android.com/welcome?continue=/back-to-publicdoes the usage of the tool meaning that the device will be wiped? (I have the stock rom ->rooted -> uninstall magisk) and I want to be original with that stock to get updateds,
Thanks
Click to expand...
Click to collapse
As you may know, even though you uninstalled Magisk and don't have root, you could still have modified partitions on the phone.
You can use:
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
(same as your link) but uncheck the option to wipe, then the phone won't be wiped.
Only then re-lock the bootloader.
roirraW edor ehT said:
As you may know, even though you uninstalled Magisk and don't have root, you could still have modified partitions on the phone.
You can use:
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
(same as your link) but uncheck the option to wipe, then the phone won't be wiped.
Only then re-lock the bootloader.
Click to expand...
Click to collapse
Thank you, the lock of the bootloader will be how?
And in that point i'm going back to the start right?
I7210I said:
Thank you, the lock of the bootloader will be how?
And in that point i'm going back to the start right?
Click to expand...
Click to collapse
You're welcome. I believe you have the lock command correct. See here -> Re-locking the bootloader
Keep in mind that when you do that, it will factory reset your device, and there's no way around that. Every single time you unlock the bootloader or lock it, it forces the phone to factory reset.
Also note that after re-locking the bootloader, you should toggle OEM unlocking in Developer options back to disabled.
roirraW edor ehT said:
You're welcome. I believe you have the lock command correct. See here -> Re-locking the bootloader
Keep in mind that when you do that, it will factory reset your device, and there's no way around that. Every single time you unlock the bootloader or lock it, it forces the phone to factory reset.
Also note that after re-locking the bootloader, you should toggle OEM unlocking in Developer options back to disabled.
Click to expand...
Click to collapse
and....when I will do factory reset = the device will be wiped , right? no way to do it without that
I7210I said:
and....when I will do factory reset = the device will be wiped , right? no way to do it without that
Click to expand...
Click to collapse
Correct.
Looks like @fil3s gave you some of this information in the separate thread you created here. Since I haven't used Official Google Android Flash Tool, I forgot that it appears there's an option right on that site to lock the bootloader. You should follow the directions that @fil3s gave you there, and yes, it will wipe. Factory Reset = Wipe
Ok no way so no way
Will do that
Thank you
I7210I said:
Hello,
I did uninstall the magisk I had in my pixel 6 pro and now I don't have root, but now when I start the device I see lines at the boot about the fastboot so as I understand I should lock it for the OTA's of google, (is it right?)
Click to expand...
Click to collapse
Everything @roirraW "edor" ehT said, but just to be clear, if you only have the bootloader unlocked but nothing else modified, you should still be able to take OTAs. You don't need a locked bootlaoder to take OTAs.
Lughnasadh said:
Everything @roirraW "edor" ehT said, but just to be clear, if you only have the bootloader unlocked but nothing else modified, you should still be able to take OTAs. You don't need a locked bootlaoder to take OTAs.
Click to expand...
Click to collapse
So I think I will leave it like this if I will still get the OTAs, there is no problem with that right?
Thanks

Question Locked phone stuck in Fastboot mode

Hey everyone!
I was updating to the latest Android beta to try to get the Move to iOS app to work. The update seemingly went fine and I was using my phone (on reddit lol) and suddenly it powered off.
Now when it starts I get a black screen that asyas "Fastboot Mode". My phone isn't unlocked so I haven't done anything funky with the firmware.
I'm afraid I've lost everything on the phone
Here's a picture of what the phone shows:
https://imgur.com/oBpGFGX
Well, the fact you can boot into fastboot is good news
Before we talk about possible actions:
- what ROM exactly were you coming from ? Was that rooted or with a custom kernel ? Was the device unlocked ?
- what ROM exactly have you been flashing ? By using which method ? Any additional steps you did while/after flashing this ?
s3axel said:
Was the device unlocked ?
Click to expand...
Click to collapse
Besides @adamkparker's statement below, the screenshot shows the bootloader is locked, unfortunately.
adamkparker said:
My phone isn't unlocked so I haven't done anything funky with the firmware.
Click to expand...
Click to collapse
You should never install Betas without having the bootloader unlocked. Is OEM unlocking at least enabled in Developer Options (I know you can't get in there right now, but was it enabled before the phone stopped being able to boot to Android)? If OEM unlocking is enabled, even with the bootloader locked now, you can try Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
If OEM unlocking isn't enabled, there's probably nothing you can do to fix the phone - you'll have to RMA it.
Pretty sure he can sideload an ota if USB debugging was enabled. One user reported they were able to sideload with locked bootloader
fil3s said:
Pretty sure he can sideload an ota if USB debugging was enabled. One user reported they were able to sideload with locked bootloader
Click to expand...
Click to collapse
You can sideload OTA updateds without USB debugging enabled. It's really the only way forward for op.

Categories

Resources