Question Hard Bricked Pixel 6 Pro Android 13

Search This thread

Rifle003

New member
Aug 20, 2022
2
4
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.
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!
 

kiwi32

Senior Member
Apr 25, 2010
66
7
Just wanted to say, I got exactly the same problem. What a mess.
Was trying to upgrade to Android 13 with PixelFlasher. I had read the warning regarding the dual slot issue.
PixelFlasher hung while waiting for a fastboot reboot of the device that never came. My phone tried to boot a few times, but failed on the google logo.
I guess it then tried to revert to the other slot that was still on Android 12, since it then became completely bricked.
Complete black screen even while charging.
RMA in progress...
 

_BA

Senior Member
Mar 16, 2012
57
19
So that others might feel better: Also happened to me. So many years of happy flashing. Then I took a break for some time and now this.

Question: What reason did you give for the RMA process? Software problem? There is no field to describe the actual problem.
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
5,486
6,544
Google Nexus 5
Huawei Nexus 6P
Just wanted to say, I got exactly the same problem. What a mess.
Was trying to upgrade to Android 13 with PixelFlasher. I had read the warning regarding the dual slot issue.
PixelFlasher hung while waiting for a fastboot reboot of the device that never came. My phone tried to boot a few times, but failed on the google logo.
I guess it then tried to revert to the other slot that was still on Android 12, since it then became completely bricked.
Complete black screen even while charging.
RMA in progress...
Hmm, interesting because the ARB isn't supposed to kick in and blow the eFuse until after a successful boot of A13. Will be interesting to see if they send you a repair card with the cause of the failure like they did with another person here on the forums, unless of course they just send you a new/refurbished one instead of repairing it.

Sorry it happened to you...
 

roirraW "edor" ehT

Forum Moderator
Staff member
Anyone managed to get it fixed? I have the exact same issue black screen and nothing works. I imported my device so warranty is out of the question. I am so pissed at myself.
I apologize for being the bearer of bad news, but there is just no way to fix it other than sending it away for repair (or finding someplace local that does it properly).
 

roirraW "edor" ehT

Forum Moderator
Staff member
  • Like
Reactions: _BA
D

Deleted member 9317882

Guest
Same issue here 😭. Please help, I also Imported the Phone, and I live in India. I'm legit in agony for the screw up I did.
 

NippleSauce

Senior Member
Jun 23, 2013
578
409
Just to chime in late:
As long as you can get into fastboot, your phone isn't bricked. To enter fastboot from the black screen, hold power and volume down for a long while. You might have to do this a few times.
 
  • Like
Reactions: roirraW "edor" ehT

testkhmark

Member
Sep 9, 2022
10
1
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.
 
  • Wow
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
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.
Your phone has a one-year warranty (unless you got yours used). Did they give a reason as to why they won't do anything?
 

testkhmark

Member
Sep 9, 2022
10
1
Your phone has a one-year warranty (unless you got yours used). Did they give a reason as to why they won't do anything?
First they told me that it's because my Google Pay account being not verified, then because of the device being flagged (no further explanation on that) and today they told me that it's because I modified my OS (which I did not).

So, yeah, Google support, ladies and gentlemen.
 
Last edited:
  • Wow
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
First they told me that it's because my Google Pay account being not verified, then because of the device being flagged (no further explanation on that) and today they told me that it's because I modified my OS (which I did not).

So, yeah, Google support, ladies and gentlemen.
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?
 

testkhmark

Member
Sep 9, 2022
10
1
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?
I bought my first P6P in Google Store in US. Long story short, I ended up with it in Germany, where it died on me. I filed RMA claim and got a replacement.
Now this replacement is died after an update and Google's website says that my warranty expired on May 4th (I ordered the replacement on May 5th, by the way), so I can't file RMA claim.
 
  • Wow
Reactions: roirraW "edor" ehT

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    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.
    Reflash the entire android 13 image
    4
    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.
    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!
    4
    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.

    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.
    3
    Try using Platform Tools instead of Minimal ADB.
    3
    Following....

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

    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.