Question Bricked Pixel 6 Pro Help needed

Search This thread

sintboy2020

Member
Jun 26, 2018
17
0
Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.

Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!
dear which ota file u used .i have the same problem .i tried many ota files but when i used the sideload command it gives error cant read file.any help please
 

bramgg

Senior Member
May 12, 2009
294
20
Select recovery mode.
When you see No Command, press power and volume up at the same time (quickly). Then try factory reset. If that doesn't work, choose ota update and follow the links above.

Hi Alekos, I have the same issue as the OP. Pixel 6 pro is bricked, will only boot into recovery. Power+ Vol Down will not work as it boots traight back into recovery. Fastboot flashing doesn't work since bootloader is locked, and there is no way to unlock it since I can't boot into Android to turn on the Setting that allows me to perform an OEM Unlock. So, I'm in an endless loop, and it looks like literally no one on the interwebs has a solution on this.

Since you seem to have a lot of knowledge on this, would you possibly have any other things to try?
 

roirraW "edor" ehT

Forum Moderator
Staff member
OEM can't be unlocked it is a Verizon Pixel Pro

Hi Alekos, I have the same issue as the OP. Pixel 6 pro is bricked, will only boot into recovery. Power+ Vol Down will not work as it boots traight back into recovery. Fastboot flashing doesn't work since bootloader is locked, and there is no way to unlock it since I can't boot into Android to turn on the Setting that allows me to perform an OEM Unlock. So, I'm in an endless loop, and it looks like literally no one on the interwebs has a solution on this.

Since you seem to have a lot of knowledge on this, would you possibly have any other things to try?

I take no pleasure in giving you this bad news, but without an unlocked bootloader, there's not a thing you can do except request an RMA.
 

Lughnasadh

Senior Member
Mar 23, 2015
3,526
3,609
Google Nexus 5
Huawei Nexus 6P
Hi Alekos, I have the same issue as the OP. Pixel 6 pro is bricked, will only boot into recovery. Power+ Vol Down will not work as it boots traight back into recovery. Fastboot flashing doesn't work since bootloader is locked, and there is no way to unlock it since I can't boot into Android to turn on the Setting that allows me to perform an OEM Unlock. So, I'm in an endless loop, and it looks like literally no one on the interwebs has a solution on this.

Since you seem to have a lot of knowledge on this, would you possibly have any other things to try?
Since you can get into recovery, and assuming you have USB Debugging enabled, have you tried to sideload the OTA?
 

bramgg

Senior Member
May 12, 2009
294
20
Since you can get into recovery, and assuming you have USB Debugging enabled, have you tried to sideload the OTA?
Yes, I've tried to side load the OTA. But it failed at 50ish % since it didn't have permission to flash the image. USB debugging is not enabled, neither is the 'unlock OEM' developer option. Phone was already bricked before this was set.

Pixel software repair and android flash tool also don't work for this reason I guess. I'm lost.
 

banshee28

Senior Member
Aug 31, 2010
219
36
I am in a similar situation.. Is there anyways to have access to delete files with only fastboot available?

I think I need to free up space on my partition before it will flash properly?
 

Alekos

Senior Member
Feb 18, 2008
538
407
Apps & Games
Google Pixel 3 XL
Hi Alekos, I have the same issue as the OP. Pixel 6 pro is bricked, will only boot into recovery. Power+ Vol Down will not work as it boots traight back into recovery. Fastboot flashing doesn't work since bootloader is locked, and there is no way to unlock it since I can't boot into Android to turn on the Setting that allows me to perform an OEM Unlock. So, I'm in an endless loop, and it looks like literally no one on the interwebs has a solution on this.

Since you seem to have a lot of knowledge on this, would you possibly have any other things to try?
did you download the latest platform tools? make sure you are using 33.0.1 (run the command " adb --version ")
then try again (different usb port and/or cable). It should succeed in flashing the ota. it sounds like that permission error is either invalid platform tools or something else.

remove all previous platform tools (never use mininal adb). go into recovery mode and do a factory reset. go to adb update, plug it into the computer, and run the update again. make sure you are using the OTA image here.

maybe even before you start, on a windows machine, download Google USB Driver, extract it, right click on Android_winusb.inf (and find "install"). then plug it in while in ota update mode and flash the ota image.

make sure you flash the same OTA image (or newer) that you currently have installed - downgrading won't work.
 
Last edited:

Alekos

Senior Member
Feb 18, 2008
538
407
Apps & Games
Google Pixel 3 XL
I am in a similar situation.. Is there anyways to have access to delete files with only fastboot available?

I think I need to free up space on my partition before it will flash properly?
space won't be an issue. boot into recovery mode and factory reset the device (remember the no command window is normal, just hit power and vol-up at the same time to bypass it). Then with the latest platform-tools (not minimal adb) and google driver, flash the ota (look at my previous comment).

make sure you flash the same OTA image (or newer) that you currently have installed - downgrading won't work.

if you are trying to save data with a locked bootloader, then skip the factory reset part in recovery mode.
 
Last edited:

banshee28

Senior Member
Aug 31, 2010
219
36
space won't be an issue. boot into recovery mode and factory reset the device (remember the no command window is normal, just hit power and vol-up at the same time to bypass it). Then with the latest platform-tools (not minimal adb) and google driver, flash the ota (look at my previous comment).

make sure you flash the same OTA image (or newer) that you currently have installed - downgrading won't work.

if you are trying to save data with a locked bootloader, then skip the factory reset part in recovery mode.
So mine is fully unlocked and was rooted with Magisk before the issues. I just did not want to loose data.
 

banshee28

Senior Member
Aug 31, 2010
219
36
I can always choose to wipe data and I think that will work fine, but was saving that for last resort.
 

Alekos

Senior Member
Feb 18, 2008
538
407
Apps & Games
Google Pixel 3 XL
I can always choose to wipe data and I think that will work fine, but was saving that for last resort.
If you are fully unlocked and can boot to fastboot/bootloader you are good. That's not a brick. That's a glitch.

For everyone else, keep the "OEM Unlocking" option enabled in developer options so you can easily save your device. first thing I do when I get my devices (this doesn't mean your Bootloader is unlocked but it allows you to unlock it without booting into Android, which can save your device).
 

bramgg

Senior Member
May 12, 2009
294
20
did you download the latest platform tools? make sure you are using 33.0.1 (run the command " adb --version ")
then try again (different usb port and/or cable). It should succeed in flashing the ota. it sounds like that permission error is either invalid platform tools or something else.

remove all previous platform tools (never use mininal adb). go into recovery mode and do a factory reset. go to adb update, plug it into the computer, and run the update again. make sure you are using the OTA image here.

maybe even before you start, on a windows machine, download Google USB Driver, extract it, right click on Android_winusb.inf (and find "install"). then plug it in while in ota update mode and flash the ota image.

make sure you flash the same OTA image (or newer) that you currently have installed - downgrading won't work.
Wow, that did the trick! I downloaded platform tools just yesterday, but was outdated for some reason. Also, the OTA from your source worked flawlessly. I was finally able to flash working OS, even with bootloader locked, turn on unlock OEM as well as USB debugging in dev options, and then flashed to stock android using flash.android.com. My dad couldn't be happier to not have to send the device to Google, since the Pixel 6 Pro is not officially supported in my country. You're a hero Alekos, many thanks!
 

djsonicdh

Member
Mar 13, 2011
46
10
Hi, I had the same problem on my PIXEL 6, usb debugg not enabled and stuck in fastboot.

1. I solved it by entering recovery mode:
1.1 In fastboot choose recovery mode
1.2 when entering "No command" press the power button and volume up
1.3 select "Apply update from ADB"

On the computer opening ADB flash the android 13 beta 3.3 OTA image (which was the one I had before the phone stopped working).
use adb sideload oriole-ota-tpb3.220617.002-f7188a41.zip
After a few minutes it came back to life and only on the first try.

The file I used oriole-ota-tpb3.220617.002-f7188a41.zip
 

Nergal di Cuthah

Senior Member
Sep 20, 2013
1,792
870
Google Pixel 6 Pro
Hi, I had the same problem on my PIXEL 6, usb debugg not enabled and stuck in fastboot.

1. I solved it by entering recovery mode:
1.1 In fastboot choose recovery mode
1.2 when entering "No command" press the power button and volume up
1.3 select "Apply update from ADB"

On the computer opening ADB flash the android 13 beta 3.3 OTA image (which was the one I had before the phone stopped working).
use adb sideload oriole-ota-tpb3.220617.002-f7188a41.zip
After a few minutes it came back to life and only on the first try.

The file I used oriole-ota-tpb3.220617.002-f7188a41.zip
Pixel 6 pro is not oriole, its raven. Are you sure you hava the right rom
 
Last edited:

JustMarv

New member
Jul 3, 2022
1
1
Hi, I had the same problem on my PIXEL 6, usb debugg not enabled and stuck in fastboot.

1. I solved it by entering recovery mode:
1.1 In fastboot choose recovery mode
1.2 when entering "No command" press the power button and volume up
1.3 select "Apply update from ADB"

On the computer opening ADB flash the android 13 beta 3.3 OTA image (which was the one I had before the phone stopped working).
use adb sideload oriole-ota-tpb3.220617.002-f7188a41.zip
After a few minutes it came back to life and only on the first try.

The file I used oriole-ota-tpb3.220617.002-f7188a41.zip
Thx for that Huge Tip :D
Just Flashed my bricked and Locked Pixel 6 Pro with no USB Debugging activated .
Just downloaded hte last Beta Build my Pixel was running and flashed it over ADB Sideload

Thanks alot !
 
  • Like
Reactions: Alekos

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.

    Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!
    3
    No Verizon device can ever have its bootloader unlocked. Sorry, you're just out of luck. With a locked bootloader, you can only ever upgrade to other official ROMs, such and Android 13 Beta 3, 4, and final release.
    Thanks for your feedback.... just bad luck
    3
    My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.

    I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.

    Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.
    Since you are able to boot into fastboot, your device isn't bricked and should be recoverable. The first thing you will want to try is booting into Safe Mode to enable OEM unlocking:

    1. Press your phone's power button.

    2. When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.

    3. You'll see "Safe mode" at the bottom of your screen.

    If that doesn't work, you can also try to flashing the OTA in recovery mode. Lots of videos on YouTube on how to update via OTA in recovery mode. Here's the Android OTA download page - you won't lose your data with this method. Chose the right image.

    Next option would be to try wipe or reset by using the Recovery Mode (this will wipe your phone): While in Fastboot/Bootloader, choose Recovery Mode with the Volume buttons. On your screen, “No command” is displayed. Press and hold the Power button. While you hold Power, press the Volume Up button and let go of both buttons quickly. Choose factory reset option (this will wipe your device so be sure to try safe mode and OTA update methods before this option if you are trying not to wipe the phone).

    If you just want to get your phone back without trying to save data, try Google's Official Flash Tool. I know most will say it's a waste of time if your BL is locked - but there have been many reports of users fixing issues just like yours even with a locked Bootloader.


    You'll need a Chrome browser.

    Because you're on 13 Beta, you could try just reinstalling the Core OS with the web flash Tool. Uncheck all the boxes (don't wipe or re-lock etc).
    3
    Please how did you do for ADB sideload, because I now have the same problem as you and I'm still stuck on fastboot modeView attachment 5618033
    Select recovery mode.
    When you see No Command, press power and volume up at the same time (quickly). Then try factory reset. If that doesn't work, choose ota update and follow the links above.
    3
    did you download the latest platform tools? make sure you are using 33.0.1 (run the command " adb --version ")
    then try again (different usb port and/or cable). It should succeed in flashing the ota. it sounds like that permission error is either invalid platform tools or something else.

    remove all previous platform tools (never use mininal adb). go into recovery mode and do a factory reset. go to adb update, plug it into the computer, and run the update again. make sure you are using the OTA image here.

    maybe even before you start, on a windows machine, download Google USB Driver, extract it, right click on Android_winusb.inf (and find "install"). then plug it in while in ota update mode and flash the ota image.

    make sure you flash the same OTA image (or newer) that you currently have installed - downgrading won't work.
    Wow, that did the trick! I downloaded platform tools just yesterday, but was outdated for some reason. Also, the OTA from your source worked flawlessly. I was finally able to flash working OS, even with bootloader locked, turn on unlock OEM as well as USB debugging in dev options, and then flashed to stock android using flash.android.com. My dad couldn't be happier to not have to send the device to Google, since the Pixel 6 Pro is not officially supported in my country. You're a hero Alekos, many thanks!