Question Hard Bricked Pixel 6 Pro Android 13

Search This thread

uoid

Senior Member
Jun 19, 2013
135
32
Manama
Google Pixel 6 Pro
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...
 

uoid

Senior Member
Jun 19, 2013
135
32
Manama
Google Pixel 6 Pro
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...
If anyone can please help me in here
 

Namelesswonder

Senior Member
Jan 26, 2014
432
731
Google Pixel XL
Google Pixel 7 Pro
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...
Try a different cable and USB port, fastboot is waiting for your device to reboot and it is timing out.
 

uoid

Senior Member
Jun 19, 2013
135
32
Manama
Google Pixel 6 Pro
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
 

uoid

Senior Member
Jun 19, 2013
135
32
Manama
Google Pixel 6 Pro
Run fastboot --version
Also need a log of the commands that you are running and the output.


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
 

uoid

Senior Member
Jun 19, 2013
135
32
Manama
Google Pixel 6 Pro
Try using Platform Tools instead of Minimal ADB.
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
 

Namelesswonder

Senior Member
Jan 26, 2014
432
731
Google Pixel XL
Google Pixel 7 Pro
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
Try using Platform Tools instead of Minimal ADB.
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.
 
  • Like
Reactions: roirraW "edor" ehT

Gytole

Senior Member
Aug 7, 2013
768
613
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
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

 

Gytole

Senior Member
Aug 7, 2013
768
613
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
Reboot your pc too
 

uoid

Senior Member
Jun 19, 2013
135
32
Manama
Google Pixel 6 Pro
(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
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.
I downloaded it but I dont know how to install it
 

uoid

Senior Member
Jun 19, 2013
135
32
Manama
Google Pixel 6 Pro
Use W10 instructions.

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.

1660932264546.png
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
5,485
6,544
Google Nexus 5
Huawei Nexus 6P
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
Should probably go over to the Pixel Flasher thread and ask the dev.
 
  • Like
Reactions: roirraW "edor" ehT

V0latyle

Forum Moderator
Staff member
A device isn't hard bricked until it's completely unresponsive.

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
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.
 

uoid

Senior Member
Jun 19, 2013
135
32
Manama
Google Pixel 6 Pro
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.

View attachment 5690517



EDIT: It doesnt move forward from here
 

Spookymyo

Senior Member
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.
 
  • Like
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.