[Google Pixel 8 Pro] badabing2003:
You were on Jan release

Selected Device on 2024-03-13 00:25:53:
Device ID: REDACTED
Device Model: husky
Device Active Slot: a
Device Mode: adb
Has init_boot partition: True
Device Bootloader Version: ripcurrent-14.1-11012321
Device is Rooted: True
Device Build: UQ1A.240105.004
Device API Level: 34
Device Architecture: arm64-v8a
Device Kernel Version: 5.15
sys_oem_unlock_allowed: 0
ro.boot.flash.locked: 1
ro.boot.vbmeta.device_state: locked
ro.product.first_api_level: 34
ro.boot.veritymode: enforcing
ro.boot.verifiedbootstate: green
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
vbmeta type: ab
Slot A Verity: Enabled
Slot A Verification: Enabled
Slot B Verity: Enabled
Slot B Verification: Enabled
Magisk Manager Version: 3d91a561:27001
Magisk Path: /data/app/~~Cmq9HUgc5hGbyL_uXE4IPg==/com.topjohnwu.magisk-MCtg8aUiVs1XOV_jAM9oKg==/base.apk
Checked for Package: com.topjohnwu.magisk
Magisk Version: 3d91a561:27001
Magisk Config SHA1: fa62f7786db3053d3e4f04f6eccfe3a5e0d3e9b6
Magisk Modules:
Iconify enabled 6.7.0
Pixel Xpert enabled canary-339
ViPER4Android Reverse Engineered enabled v0.6.1
BCR disabled v1.59 [Update Available]
playcurl enabled v9
Play Integrity Fix enabled v15.9.3 [Update Available]
Zygisk - Sui enabled v13.5.1
Zygisk - LSPosed enabled v1.9.2 (7024)
Shamiko enabled v1.0.1 (300)

It's beyond me why you would try to flash patched init_boot (only) from March release over your January firmware.

==============================================================================
2024-03-13 00:31:22 PixelFlasher 6.7.1.0 Flash Boot
==============================================================================
Flashing / Live Booting
C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4\a06ee98ef5ad217934382f8c875dbebbb4ad6853\magisk_patched_27001_a06ee98e_c802c784.img ...

*** Dialog ***
Live/Flash Boot Options:

Option: Flash
Boot Hash: c802c7842a4ee7d91f41299b1ec55759c64eec4c
Hardware: husky
Patched: Yes
With Magisk: 3d91a561:27001
Patched Method: root
Original boot.img from: husky-ap1a.240305.019.a1
Original boot.img Hash: a06ee98ef5ad217934382f8c875dbebbb4ad6853
Custom Flash Options: False
Flash To Inactive Slot: False
Flash Both Slots: False
Verbose Fastboot: False
boot.img path:
C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4\a06ee98ef5ad217934382f8c875dbebbb4ad6853\magisk_patched_27001_a06ee98e_c802c784.img

Earlier you selected March OTA (which was a good move)

2024-03-12 23:52:49 The following firmware is selected:
husky-ota-ap1a.240305.019.a1-f1130be5.zip
Selected Firmware husky-ota-ap1a.240305.019.a1-f1130be5.zip SHA-256: f1130be5f8ff4f2a2a8c9984d244b47898eaaea924ae9065a4f4ab1bed075442

But then decided to switch to factory (bad move)

2024-03-12 23:59:38 The following firmware is selected:
husky-ap1a.240305.019.a1-factory-1091bcb2.zip
Selected Firmware husky-ap1a.240305.019.a1-factory-1091bcb2.zip SHA-256: 1091bcb2bfa130d53d225bd133b1ea2e3186683bb621785af61777a386aed6b0

Bottom line, there was a communication issue (it could be bad cable, USB port, USB drivers ...) that borked your device

Writing 'super' OKAY [ 0.967s]
Sending sparse 'super' 13/20 (254972 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed

See why even with bad cable / driver ... had you stayed with OTA, your device would still be good, becuase OTA flashes to the inactive slot, and if it fails, you're back to the active slot.

Unlike Factory which overwrote partially your active slot.

How can you recover from this?

If you manage to put your device into bootloader or recovery mode, then you can recover, if your device can't be detected, I'm afraid you're looking at an expensive door stopper.

Try the key combinations for various mode to manage to put your device into recovery or bootloader mode.

If your manage to get into bootloader mode, you would flash factory image.

If you manage to get into recovery, you would flash OTA

Make sure you address the communication issue, install the latest Google USB drivers, use a good cable, and often USB 2 ports are more reliable, never use USB hub.

One other thing, you kept suspect modules active before flashing, they can get you into bootloop even if youd flashing was successfull.

I would never keep these enabled when flashing patched.

Iconify enabled 6.7.0
Pixel Xpert enabled canary-339
ViPER4Android Reverse Engineered enabled v0.6.1

Even LSPosed is supect because of modules it loads. Shamiko could be too.

Better safe than sorry.

If you manage to get into bootloader / recovery mode, make sure you flash stock and not the patched.

Recover your device before you get ahead of yourself and want to root again.

If you want to go back to stock and lock your bootloader, see below for the proper steps to take.

📳🔥PixelFlasher for Google Pixel 8 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