yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] blackhawk:
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😖
[Google Pixel 6 Pro] 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.
[Google Pixel 6 Pro] PunkOz:
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 :(
[Google Pixel 6 Pro] 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?
[Google Pixel 6 Pro] lottarake:
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.
[Google Pixel 6 Pro] DespairFactor:
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
[Google Pixel 6 Pro] rajchelu:
Following....

I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
[Google Pixel 6 Pro] 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.
[Google Pixel 6 Pro] fil3s:
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.
[Google Pixel 6 Pro] 96carboard:
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.
[Google Pixel 6 Pro] PunkOz:
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

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 :(
[Google Pixel 6 Pro] 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 :cry:
[Google Pixel 6 Pro] 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?
[Google Pixel 6 Pro] roirraW "edor" ehT:
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.
[Google Pixel 6 Pro] 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.
[Google Pixel 6 Pro] uoid:
I updated to Android 13 everthing was smooth until i decided to flash inactive slot via Magisk and my phone has no display only boots into fastboot.

I tried flashing factory image but it Stop here, tried it multiple times.

Tried doing it to both Slots.

Bootloader Version...: slider-1.2-8739948

Baseband Version.....: g5123b-102852-220720-B-8851166

Serial Number........: 0ab54fde3750

--------------------------------------------

extracting android-info.txt (0 MB) to RAM...

Checking 'product' OKAY [ 0.000s]

Checking 'version-bootloader' OKAY [ 0.000s]

Checking 'version-baseband' OKAY [ 0.000s]

Setting current slot to 'b' OKAY [ 0.378s]

extracting boot.img (64 MB) to disk... took 0.159s

archive does not contain 'boot.sig'

Sending 'boot_b' (65536 KB) OKAY [ 1.511s]

Writing 'boot_b' OKAY [ 0.282s]

extracting dtbo.img (16 MB) to disk... took 0.031s

archive does not contain 'dtbo.sig'

Sending 'dtbo_b' (16384 KB) OKAY [ 0.375s]

Writing 'dtbo_b' OKAY [ 0.063s]

archive does not contain 'dt.img'

extracting pvmfw.img (1 MB) to disk... took 0.015s

archive does not contain 'pvmfw.sig'

Sending 'pvmfw_b' (1024 KB) OKAY [ 0.016s]

Writing 'pvmfw_b' OKAY [ 0.016s]

archive does not contain 'recovery.img'

extracting vbmeta.img (0 MB) to disk... took 0.000s

archive does not contain 'vbmeta.sig'

Sending 'vbmeta_b' (12 KB) OKAY [ 0.000s]

Writing 'vbmeta_b' OKAY [ 0.000s]

extracting vbmeta_system.img (0 MB) to disk... took 0.000s

archive does not contain 'vbmeta_system.sig'

Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.000s]

Writing 'vbmeta_system_b' OKAY [ 0.000s]

extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s

archive does not contain 'vbmeta_vendor.sig'

Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.000s]

Writing 'vbmeta_vendor_b' OKAY [ 0.000s]

extracting vendor_boot.img (64 MB) to disk... took 0.188s

archive does not contain 'vendor_boot.sig'

Sending 'vendor_boot_b' (65536 KB) OKAY [ 1.457s]

Writing 'vendor_boot_b' OKAY [ 0.219s]

extracting super_empty.img (0 MB) to disk... took 0.000s

Rebooting into fastboot OKAY [ 0.000s]

< waiting for any device >

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

fastboot: usage: no command

Press any key to exit...
[Google Pixel 6 Pro] uoid:
If anyone can please help me in here
[Google Pixel 6 Pro] Namelesswonder:
Try a different cable and USB port, fastboot is waiting for your device to reboot and it is timing out.
[Google Pixel 6 Pro] uoid:
tried it, didnt help.

the screen flashes like a glitch btw for a milliseconds
[Google Pixel 6 Pro] Namelesswonder:
Run fastboot --version

Also need a log of the commands that you are running and the output.
[Google Pixel 6 Pro] uoid:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --version

fastboot version 0.0.1-4500957

Installed as C:\Program Files (x86)\Minimal ADB and Fastboot\fastboot.exe
[Google Pixel 6 Pro] uoid:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --version

fastboot version 0.0.1-4500957

Installed as C:\Program Files (x86)\Minimal ADB and Fastboot\fastboot.exe

--------------------------------------------

Bootloader Version...: slider-1.2-8739948

Baseband Version.....: g5123b-102852-220720-B-8851166

Serial Number........: 0ab54fde3750

--------------------------------------------

checking product...

OKAY [ 0.000s]

checking version-bootloader...

OKAY [ 0.016s]

checking version-baseband...

OKAY [ -0.000s]

sending 'boot_a' (65536 KB)...

OKAY [ 1.517s]

writing 'boot_a'...

OKAY [ 0.250s]

sending 'dtbo_a' (16384 KB)...

OKAY [ 0.375s]

writing 'dtbo_a'...

OKAY [ 0.062s]

sending sparse 'system_a' 1/4 (254972 KB)...

OKAY [ 5.971s]

writing 'system_a' 1/4...

(bootloader) failed to write chunk #0

FAILED (remote: failed to flash partition (system_a))

finished. total time: 8.253s
[Google Pixel 6 Pro] Lughnasadh:
Try using Platform Tools instead of Minimal ADB.
[Google Pixel 6 Pro] uoid:
Tried Platforn Tools now and got the same results.

Just curious is this all supposed to be "raw"

(bootloader) partition-type:klog:raw

(bootloader) partition-type:misc:raw

(bootloader) partition-type:frp:raw

(bootloader) partition-type:efs:ext4

(bootloader) partition-type:efs_backup:ext4

(bootloader) partition-type:modem_userdata:raw

(bootloader) partition-type:metadata:raw

(bootloader) partition-type:fips:raw

(bootloader) partition-type:dtbo_a:raw

(bootloader) partition-type:vendor_boot_a:raw

(bootloader) partition-type:modem_a:raw

(bootloader) partition-type:boot_a:raw

(bootloader) partition-type:vbmeta_a:raw

(bootloader) partition-type:vbmeta_system_a:raw

(bootloader) partition-type:vbmeta_vendor_a:raw

(bootloader) partition-type:pvmfw_a:raw

(bootloader) partition-type:dtbo_b:raw

(bootloader) partition-type:vendor_boot_b:raw

(bootloader) partition-type:modem_b:raw

(bootloader) partition-type:boot_b:raw
[Google Pixel 6 Pro] Namelesswonder:
Yes stop using Minimal ADB and Fastboot and don't use it again, it's over 4 years out of date and doesn't have any idea what a super partition or dynamic partitions are so you're never going to be able to flash any modern phone with it.
[Google Pixel 6 Pro] Gytole:
Have you tried Pixel Flasher? I used it to flash both slots INDIVIDUALLY. It doesn't like flashing both slots at the same time, it bricks me. But flashing one slot, then immediately booting into fastboot after a successful flash and switching slots and flashing that slot too works flawlessly each time then manually reroot or what not

📳🔥PixelFlasher for Google Pixel 6 Pro Support Thread.

This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...

xdaforums.com
[Google Pixel 6 Pro] Gytole:
Reboot your pc too
[Google Pixel 6 Pro] Lughnasadh:
Also make sure you have the latest Google USB driver installed. Also try using a A to C cable using USB 2.0 port, if you haven't already.
[Google Pixel 6 Pro] uoid:
(bootloader) partition-type:klog:raw

(bootloader) partition-type:misc:raw

(bootloader) partition-type:frp:raw

(bootloader) partition-type:efs:ext4

(bootloader) partition-type:efs_backup:ext4

(bootloader) partition-type:modem_userdata:raw

(bootloader) partition-type:metadata:raw

(bootloader) partition-type:fips:raw

(bootloader) partition-type:dtbo_a:raw

(bootloader) partition-type:vendor_boot_a:raw

(bootloader) partition-type:modem_a:raw

(bootloader) partition-type:boot_a:raw

(bootloader) partition-type:vbmeta_a:raw

(bootloader) partition-type:vbmeta_system_a:raw

(bootloader) partition-type:vbmeta_vendor_a:raw

(bootloader) partition-type:pvmfw_a:raw

(bootloader) partition-type:dtbo_b:raw

(bootloader) partition-type:vendor_boot_b:raw

(bootloader) partition-type:modem_b:raw

(bootloader) partition-type:boot_b:raw

(bootloader) partition-type:vbmeta_b:raw

(bootloader) partition-type:vbmeta_system_b:raw

(bootloader) partition-type:vbmeta_vendor_b:raw

(bootloader) partition-type:pvmfw_b:raw

(bootloader) partition-type:super:raw

(bootloader) partition-type:userdata:raw

(bootloader) partition-type:bl1_a:raw

(bootloader) partition-type:pbl_a:raw

(bootloader) partition-type:bl2_a:raw

(bootloader) partition-type:dram_train_a:raw

(bootloader) partition-type:abl_a:raw

(bootloader) partition-type:bl31_a:raw

(bootloader) partition-type:tzsw_a:raw

(bootloader) partition-type:gsa_a:raw

(bootloader) partition-type:ldfw_a:raw

(bootloader) partition-type:dpm_a:raw

(bootloader) partition-type:bl1_b:raw

(bootloader) partition-type:pbl_b:raw

(bootloader) partition-type:bl2_b:raw

(bootloader) partition-type:dram_train_b:raw

(bootloader) partition-type:abl_b:raw

(bootloader) partition-type:bl31_b:raw

(bootloader) partition-type:tzsw_b:raw

(bootloader) partition-type:gsa_b:raw

(bootloader) partition-type:ldfw_b:raw

(bootloader) partition-type:dpm_b:raw

(bootloader) partition-type:devinfo:raw

(bootloader) partition-type:mfg_data:raw

(bootloader) partition-type:system_a:raw

(bootloader) partition-type:system_b:raw

(bootloader) partition-type:system_ext_a:raw

(bootloader) partition-type:system_ext_b:raw

(bootloader) partition-type:product_a:raw

(bootloader) partition-type:product_b:raw

(bootloader) partition-type:vendor_a:raw

(bootloader) partition-type:vendor_b:raw

(bootloader) partition-type:vendor_dlkm_a:raw

(bootloader) partition-type:vendor_dlkm_b:raw

I downloaded it but I dont know how to install it
[Google Pixel 6 Pro] Lughnasadh:
Use W10 instructions.

Install OEM USB drivers | Android Studio | Android Developers

Discover links to the web sites for several original equipment manufacturers (OEMs), where you can download the appropriate USB driver for your device.

developer.android.com
[Google Pixel 6 Pro] uoid:
2022-08-19 20:50:39 ERROR: C:\Users\Usama\AppData\Roaming\PixelFlasher\factory_images\image-raven\image-image-raven.zip is not found.

Please check E:\Softwares\raven-tp1a.220624.021-factory-d8ddfdca\raven-tp1a.220624.021\image-raven-tp1a.220624.021.zip to make sure it is a valid factory image file.

PIXEL flasher is giving me this error

EDIT: Got it working but its stuck at

archive does not contain 'vendor_boot.sig'

Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.484s]

Writing 'vendor_boot_a' OKAY [ 0.231s]

archive does not contain 'vendor_kernel_boot.img'

extracting super_empty.img (0 MB) to disk... took 0.000s

Rebooting into fastboot OKAY [ 0.001s]

< waiting for 0ab54fde3750 >

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
[Google Pixel 6 Pro] Lughnasadh:
Should probably go over to the Pixel Flasher thread and ask the dev.
[Google Pixel 6 Pro] V0latyle:
A device isn't hard bricked until it's completely unresponsive.

When using Pixel Flasher, you don't have to extract anything. Select the original factory ZIP you downloaded from the Pixel Images site - the one that the file you selected was in.
[Google Pixel 6 Pro] uoid:
EDIT: It doesnt move forward from here
[Google Pixel 6 Pro] Spookymyo:
I ran into same problem. I tried everything listed here and then some. Nothing worked.

The screen wouldn't come on at all. And the pc wouldn't recognize it as a phone.

I chatted with Google and told them I tried to flash android 13 with the Android flash tool (which I did) and it bricked my phone The tech said it sounded like an eFuse trip. He said to send it in. So I sent it in for warranty repair.
[Google Pixel 6 Pro] Rifle003:
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!
[Google Pixel 6 Pro] kiwi32:
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...
[Google Pixel 6 Pro] _BA:
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.
[Google Pixel 6 Pro] Lughnasadh:
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...
[Google Pixel 6 Pro] ghostechful:
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.
[Google Pixel 6 Pro] roirraW "edor" ehT:
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).
[Google Pixel 6 Pro] cultofluna:
Try pixel flasher
[Google Pixel 6 Pro] ghostechful:
Ouch 😔 thanks tho
[Google Pixel 6 Pro] mike.s:
That won't work unless you can get into the bootloader.
[Google Pixel 6 Pro] angelspid:
Somebody, try this ?

Guide: Unbrick Pixel 6 Oriele or Pixel 6 Pro "Raven"

Pixel 6 Pro runs on a Google Tensor CPU which is in fact an Exynos CPU This means that there is Exynos boot recovery in the CPU You can repair the bootloader using the Samsung Exynos Tool Nothing could be flashed from the mode, however it...

xdaforums.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you check out the last page of posts in that thread, you'll see that no one ever had any luck.
[Google Pixel 6 Pro] :
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.
[Google Pixel 6 Pro] roirraW "edor" ehT:
There is no way to fix the phone except by having Google repair it.
[Google Pixel 6 Pro] cultofluna:
If pixel flasher recognize your phone you can change slot ( to the other slot where the a13 bootloader is) and boot to fastboot ..

From there you can flash bootloader to both slots ...

One user on telegram fixed it this way
[Google Pixel 6 Pro] NippleSauce:
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.
[Google Pixel 6 Pro] testkhmark:
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.
[Google Pixel 6 Pro] roirraW "edor" ehT:
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?
[Google Pixel 6 Pro] testkhmark:
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.
[Google Pixel 6 Pro] roirraW "edor" ehT:
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
[Google Pixel 6 Pro] testkhmark:
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.
[Google Pixel 6 Pro] NippleSauce:
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.
[Google Pixel 6 Pro] testkhmark:
Yes. The phone is bricked, it doesn't respond to anything: buttons, pc, charger.
[Google Pixel 6 Pro] testkhmark:
Also, just double checked with the support: replacement devices are subject to only 90 days of warranty, not a year.
[Google Pixel 6 Pro] roirraW "edor" ehT:
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?
[Google Pixel 6 Pro] testkhmark:
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.