Question Hard Bricked Pixel 6 Pro Android 13

Search This thread
By:
Advanced…
D

dkadds2

Senior Member
Sep 2, 2013
81
5
badabing2003 said:
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
Code: 
fastboot reboot recovery
the phone should reboot and you should see an Android with it's cover open
Click to expand...
Click to collapse
Unfortunately, it doesn't boot to either recovery nor rescue, each time stating there is no bootable OS available.
I did sideload from Recovery previously (prior brick) updates and all worked.
If the sideload you had in mind was Recovery based booted of the phone from either bootloader or "fastboot reboot recovery" which has same effect - then it doesn't work. Really appreciate you trying to help.
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,335
3,346
dkadds2 said:
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.
Click to expand...
Click to collapse
Did you try these steps?
forum.xda-developers.com

Hard Bricked Pixel 6 Pro Android 13

Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel...
forum.xda-developers.com forum.xda-developers.com

It would help to post back what steps worked and what didn't and what were the output.
 
D

dkadds2

Senior Member
Sep 2, 2013
81
5
After it has been bricked all fastboot commands like:
- slot change
- flash boot image
- boot image
- flashing unlock
- reboot recovery
- reboot rescue

Do not work.

It shows up as fastboot device and bootloader screen shows.

Any try to load OS, recovery or rescue, ends with
Code: 
No valid operating system could be found.
The device will not boot.
With only one option selectable "Power off" and if cable is connected it starts bootloader again.

That is really all so far.
I'd be super happy to test any further commands - maybe some EDL level would help, though it all seems to be locked on Tensor CPU.
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,335
3,346
dkadds2 said:
After it has been bricked all fastboot commands like:
- slot change
- flash boot image
- boot image
- flashing unlock
- reboot recovery
- reboot rescue

Do not work.

It shows up as fastboot device and bootloader screen shows.

Any try to load OS, recovery or rescue, ends with
Code: 
No valid operating system could be found.
The device will not boot.
With only one option selectable "Power off" and if cable is connected it starts bootloader again.

That is really all so far.
I'd be super happy to test any further commands - maybe some EDL level would help, though it all seems to be locked on Tensor CPU.
Click to expand...
Click to collapse
What error do you get when you try to flash something?
Bootloader for example
Code: 
fastboot flash bootloader bootloader-raven-slider-1.2-9465321.img
 
D

dkadds2

Senior Member
Sep 2, 2013
81
5
badabing2003 said:
What error do you get when you try to flash something?
Bootloader for example
Code: 
fastboot flash bootloader bootloader-raven-slider-1.2-9465321.img
Click to expand...
Click to collapse
Sorry to ask, though the last what I'd want to test is flashing bootloader as it is the one which loads.
Unless I'd have a bootloader which would forcefully unlock itself and this one is genuine.
Trying to boot/flash (tried boot and recovery) following is shown:
Code: 
fastboot boot boot.img
downloading 'boot.img'...
OKAY [  1.934s]
booting...
FAILED (remote: command (boot) is not allowed when locked)
finished. total time: 1.975s
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,335
3,346
dkadds2 said:
Sorry to ask, though the last what I'd want to test is flashing bootloader as it is the one which loads.
Unless I'd have a bootloader which would forcefully unlock itself and this one is genuine.
Trying to boot/flash (tried boot and recovery) following is shown:
Code: 
fastboot boot boot.img
downloading 'boot.img'...
OKAY [  1.934s]
booting...
FAILED (remote: command (boot) is not allowed when locked)
finished. total time: 1.975s
Click to expand...
Click to collapse
I'm afraid you have managed to lock yourself out permanently.
Sorry for your loss.
 
  • Like
Reactions: dkadds2
You must log in or register to reply here.

Similar threads

Freak07
Development [Kernel][02.06.2023][Android 13.0.0]Kirisakura 1.0.5_6_Raviantah for Pixel 6/Pro aka "RAVIOLE"
Replies
3K
Views
380K
Flyview
Flyview
roirraW "edor" ehT
How To Guide Platform-Tools v34.0.3 has a different bug - May 17, 2023 TQ2A.230505.002.G Verizon/MVNOs - May 1 TQ2A.230505.002 Global - Root Pixel 6 Pro [Raven]
Replies
2K
Views
283K
Lughnasadh
Lughnasadh
Typhus_
Themes / Apps / Mods [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
Replies
1K
Views
137K
Thebear j koss
Thebear j koss
V0latyle
How To Guide [GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
Replies
2K
Views
167K
Nergal di Cuthah
Nergal di Cuthah
Pekempy
How To Guide Working SafetyNet with Pixel 6 Pro Android 12
Replies
635
Views
90K
Nergal di Cuthah
Nergal di Cuthah

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 5
    DespairFactor
    DespairFactor
    PunkOz said:
    Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
    It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.

    Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?


    Thanks in advance.
    Click to expand...
    Click to collapse
    Reflash the entire android 13 image
    View
    4
    Rifle003
    Rifle003
    PunkOz said:
    Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
    It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.

    Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?

    Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
    🥲 willing to pay anyone here if someone helps me to boot my pixel again.

    Thanks in advance.
    Click to expand...
    Click to collapse
    I've ran into this issue, somehow I only used power button, it went to boot loop!! then used power button for a few seconds and pressed volume down with it and released them at the same time!! it worked bootloader popped up, then went to recovery and used adb!
    View
    4
    9
    96carboard
    PunkOz said:
    Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?

    Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
    🥲 willing to pay anyone here if someone helps me to boot my pixel again.
    Click to expand...
    Click to collapse

    The good news is that your phone is still under warranty!
    The bad news is that you now have to USE the warranty.

    A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.

    The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
    View
    3
    Lughnasadh
    Lughnasadh
    Try using Platform Tools instead of Minimal ADB.
    View
    3
    fil3s
    fil3s
    rajchelu said:
    Following....

    I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
    Click to expand...
    Click to collapse

    If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command

    Then direct install in magisk app ;)

    If it fails when booting the image, device will just reboot into normal mode.
    View

New posts