Question Hard Bricked Pixel 6 Pro Android 13

[NippleSauce]

Does anyone knows the cost of the repairs?
My replacement P6P died 90+ days after I got it, and Google says that they won't do anything, so I have to find someone to fix it for a fee.

I do not know the cost of repairs - but did you try what I have mentioned just above your post? You may need to connect to the device to a charger if it doesn't work at first as battery would be necessary to enter the mode that I described.

Edit - it wouldn't respond to a PC - regardless of its condition - if it were off (nor would it display anything when connecting a charger w/ a corrupt installation)... It would only respond to the buttons being pressed in the way that I have mentioned. And sometimes you have to press and hold power+volume up to force a restart first before trying the power+volume down another few times. That is the only way to really see if your phone is bricked. I have read through countless posts on this forum where people RMA'd their not even bricked phones.

 

[testkhmark]

I do not know the cost of repairs - but did you try what I have mentioned just above your post? You may need to connect to the device to a charger if it doesn't work at first as battery would be necessary to enter the mode that I described.

Yes. The phone is bricked, it doesn't respond to anything: buttons, pc, charger.

 

[testkhmark]

Is it brand new or did you buy it used from someone? If used, maybe the phone was reported stolen. Very strange. I certainly don't know what your Google Pay account would have to do with anything.

Are any of these places where you tried to start the RMA process?

• Repairs, replacements & warranties
• File a warranty claim for your Pixel phone
• Hardware Warranty Center

Also, just double checked with the support: replacement devices are subject to only 90 days of warranty, not a year.

 

[roirraW "edor" ehT]

Also, just double checked with the support: replacement devices are subject to only 90 days of warranty, not a year.

That is indeed unacceptable. What that means is that they'll only cover one occurrence that requires replacement of the phone. If they actually repair a phone, it would still be under warranty, but replace it and the new phone's warranty doesn't transfer? Ugh.

I could've sworn that there are users in this section who had reported getting their phone replaced under warranty at least twice in the last year. I think one person even said so recently. Tried posting on their Reddit here or here about the situation yet?

 

[testkhmark]

That is indeed unacceptable. What that means is that they'll only cover one occurrence that requires replacement of the phone. If they actually repair a phone, it would still be under warranty, but replace it and the new phone's warranty doesn't transfer? Ugh.

I could've sworn that there are users in this section who had reported getting their phone replaced under warranty at least twice in the last year. I think one person even said so recently. Tried posting on their Reddit here or here about the situation yet?

Made the post on Pixel subreddit about the initial issue, and opened a ticket for the Reddit Help desk there, but it went nowhere, and just made the post on both subreddits specifically about the warranty.

Oh, and another fun fact: I ordered the replacement device on May 5th. On the Google warranty website it says, that my replacement phone, that I got around May 10, is out of warranty since May 4th, one day before I ordered it.

 

[gh0stITH]

Has anyone experienced this with the Pixel 5 where it is hardbridcked due to the anti-rollback feature? Had a similar situation happen to me while trying to flash to an older Android version for TWRP with Android 13 in slot A. I thought this was only a situation with the Pixel 6 models.

 

[Lughnasadh]

Has anyone experienced this with the Pixel 5 where it is hardbridcked due to the anti-rollback feature? Had a similar situation happen to me while trying to flash to an older Android version for TWRP with Android 13 in slot A. I thought this was only a situation with the Pixel 6 models.

The new anti-rollback protection only applies to the Pixel 6 series.

 

[gh0stITH]

The new anti-rollback protection only applies to the Pixel 6 series.

Yeah, I don't know exactly why it turned into my new paperweight. I tried to rollback from Android 13 to Android 11, by flashing A11 to slot B and rebooting the bootloader. Time to find a new phone...

 

[Twilightsparklez]

Yeah, I don't know exactly why it turned into my new paperweight. I tried to rollback from Android 13 to Android 11, by flashing A11 to slot B and rebooting the bootloader. Time to find a new phone...

There seemed to be a pretty widespread bug in the 5. They even extended warrenty for whatever it was

 

[dkadds2]

Guys, I've P6p with bootloader loading (locked bootloader), slot b and trying to load OS, it says no

No valid operating system could be found.
The device will not boot.

ID: 42ed1bca
Code:3

Given you guys here were saying that if bootloader works, then it is not a hard-brick, though it looks to me like this.

Any thoughts on how to recover it then? (Recovery/Rescue doesn't load, same as OS and bootloader is locked).

Thanks!

 

[badabing2003]

Guys, I've P6p with bootloader loading (locked bootloader), slot b and trying to load OS, it says no

No valid operating system could be found.
The device will not boot.

ID: 42ed1bca
Code:3

Given you guys here were saying that if bootloader works, then it is not a hard-brick, though it looks to me like this.

Any thoughts on how to recover it then? (Recovery/Rescue doesn't load, same as OS and bootloader is locked).

Thanks!

You can try to connect your phone to PixelFlasher (see my sig)
See if it detects your phone in any mode.

if it does, then download the OTA
choose custom flash (enable it in configuration)
Select SIDELOAD and choose the OTA file and flash

 

[dkadds2]

Thanks @badabing2003 - tried it just now, it uses fastboot commands which are getting refused due to bootloader being locked. With that said, it shown that bootloader flashing worked and refused at level of boot, etc.

What do you mean by "Sideload"? I did select the image and launched flashing, tried to boot live or flash just boot - none worked.
It seems like it refuses to boot live an image as it is in booloader lock mode.

 

[badabing2003]

Thanks @badabing2003 - tried it just now, it uses fastboot commands which are getting refused due to bootloader being locked. With that said, it shown that bootloader flashing worked and refused at level of boot, etc.

What do you mean by "Sideload"? I did select the image and launched flashing, tried to boot live or flash just boot - none worked.
It seems like it refuses to boot live an image as it is in booloader lock mode.

No it does not use fastboot command for flashing OTA
You have to follow the expert mode guide here
Where you see 5 in the screenshot, that is where you select SIDELOAD (the screenshot is showing boot)
And you select the OTA next to it

But your device has to be detected in any mode os that PF can put it to the proper mode to flash the OTA
Hit scan and see if your phone is detected.

 

[ThatAndroidGuy207]

Your best bet at this point is to just completely reflash Android onto the device if you can get it into Fastboot. Whenever you screw something up that's system level I always tell people to just reflash android entirely because even if it did turn back on normally you have no idea what else is screwed up.

 

[dkadds2]

Your best bet at this point is to just completely reflash Android onto the device if you can get it into Fastboot. Whenever you screw something up that's system level I always tell people to just reflash android entirely because even if it did turn back on normally you have no idea what else is screwed up.

Please, can you expand on how to flash whilst in fastboot with bootloader locked?

Thanks!

 

[dkadds2]

No it does not use fastboot command for flashing OTA
You have to follow the expert mode guide here
Where you see 5 in the screenshot, that is where you select SIDELOAD (the screenshot is showing boot)
And you select the OTA next to it

But your device has to be detected in any mode os that PF can put it to the proper mode to flash the OTA
Hit scan and see if your phone is detected.

Phone is detected though as mentioned earlier, all I see it tries to run fastboot commands, in this case, switching slots. This fails and if anything is done in the background not shown on the console it causes phone to try to boot and shows "No valid operating system..." same as message earlier.

Did I miss anything?

 

[ThatAndroidGuy207]

Please, can you expand on how to flash whilst in fastboot with bootloader locked?

Thanks!

You cannot do it while the bootloader is locked. Make sure you have platform tools installed on your PC and open a command window inside of the "Platform Tools" folder (assuming you do not have it setup to recognize ADB in the windows terminal itself) and then type this "fastboot devices" without the quotations to make sure your phone shows up. If it shows up then simply type in "fastboot flashing unlock" once you do this it should take you back to the fastboot screen. Now that you are back to the fastboot page go to flash.android.com and there will be a window or a popup that asks you to enable Web-USB and to allow your browser to access ADB. Once you have the device recognized than simply just choose your software and follow the steps. If your phone does not show up when you type in "fastboot devices" then that is an entirely seperate issue but ill do my best to help.

 

[badabing2003]

Phone is detected though as mentioned earlier, all I see it tries to run fastboot commands, in this case, switching slots. This fails and if anything is done in the background not shown on the console it causes phone to try to boot and shows "No valid operating system..." same as message earlier.

Did I miss anything?

Are you clicking on Flash boot or Flash Pixel Phone?
If you've been clicking on Flash boot, then click on Flash Pixel Phone

Otherwise try this:
While in fastboot mode type

fastboot reboot recovery

the phone should reboot and you should see an Android with it's cover open
Hold down the Power button and press the Volume Up button once.
Try this even if you don't see the phone cover open icon.
You should see something like this

Use the volume up and down button and select Apply update from ADB
Press the power button once

Now in PF, click on the Flash Pixel Phone make sure you keep these choices.

 

[badabing2003]

You cannot do it while the bootloader is locked. Make sure you have platform tools installed on your PC and open a command window inside of the "Platform Tools" folder (assuming you do not have it setup to recognize ADB in the windows terminal itself) and then type this "fastboot devices" without the quotations to make sure your phone shows up. If it shows up then simply type in "fastboot flashing unlock" once you do this it should take you back to the fastboot screen. Now that you are back to the fastboot page go to flash.android.com and there will be a window or a popup that asks you to enable Web-USB and to allow your browser to access ADB. Once you have the device recognized than simply just choose your software and follow the steps. If your phone does not show up when you type in "fastboot devices" then that is an entirely seperate issue but ill do my best to help.

He can't do fastboot flashing unlock because the phone is not OEM unlocked,
And he can't get into adb mode either.
So the only choice is sideload, if he manages to get into that mode.

 

[dkadds2]

You cannot do it while the bootloader is locked. Make sure you have platform tools installed on your PC and open a command window inside of the "Platform Tools" folder (assuming you do not have it setup to recognize ADB in the windows terminal itself) and then type this "fastboot devices" without the quotations to make sure your phone shows up. If it shows up then simply type in "fastboot flashing unlock" once you do this it should take you back to the fastboot screen. Now that you are back to the fastboot page go to flash.android.com and there will be a window or a popup that asks you to enable Web-USB and to allow your browser to access ADB. Once you have the device recognized than simply just choose your software and follow the steps. If your phone does not show up when you type in "fastboot devices" then that is an entirely seperate issue but ill do my best to help.

OEM Unlocking was enabled BUT CalyxOS automatically disabled it
(https://gitlab.com/CalyxOS/calyxos/-/issues/1581)

This means OEM unlocking has been disabled (even if I thought checking on it that was enabled) which effectively means I can not unlock bootloader using standard "fastboot flashing unlock".
Any other ideas are more than welcome as am facing hard brick now.