Question Hard Bricked Pixel 6 Pro Android 13

[PunkOz]

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.

 

[DespairFactor]

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

 

[PunkOz]

Reflash the entire android 13 image

How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.

 

[blackhawk]

Read this thread if you haven't...

 

[PunkOz]

Read this thread if you haven't...

Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.

 

[blackhawk]

Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.

Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed

 

[lottarake]

I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?

If you can get into fastboot even with no display, you should be able to reflash the factory images.

Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.

 

[PunkOz]

I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?

If you can get into fastboot even with no display, you should be able to reflash the factory images.

Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.

Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices

 

[V0latyle]

@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?

 

[lottarake]

Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.

Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices

ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.

If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.

Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.

 

[DespairFactor]

Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.

Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices

it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13

 

[rajchelu]

Following....

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

 

[rhetorician]

Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.

 

[fil3s]

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.

 

[96carboard]

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.

 

[PunkOz]

it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13

I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle

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.

Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked

 

[stmm]

If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour

 

[Markelijk]

So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?

 

[roirraW "edor" ehT]

So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?

We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.

 

[Gytole]

Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".

But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.

I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.

But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.

Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.