[Google Pixel 3 XL Questions & Answers] jpactual:
stuck in soft brick

SOLVED: I flashed the correct factory image but this time from WINDOWS 7 instead of Debian or Fedora Linux. It flashed everything flawlessly and the first time. .... I never expected Windows to be the solution to any of my problems. Let it be known to give flashing in Windows a whirl if inexplicably linux isn't working.

----

edit: I have the most recently platform tools and I am using linux

edit: trying to boot to twrp with fastboot boot twrp-3.x.x.img just ends up in a reboot to the bootloader.

Pixel 3 xl bought from google directly for unlocked bootloader, USA, I use Verizon.

I unlocked the bootloader, applied Magisk.

Here comes where I think the big mistake started

I accidently applied the wrong ota

9.0.0 (PQ1A.181205.006.A1, Dec 2018, Docomo) --> yeah Docomo the japanese phone company if I recall correctly.... :(

instead of

9.0.0 (PQ1A.181205.006, Dec 2018 --> which I THINK is the correct one for my device.

and it has been hell ever since.

Then mistake number 2 I accidently flashed twrp over the android install it appears, the phone would only boot into twrp.

I tried a factory image install through fastboot.

flash-all.sh resulted in

$ ./flash-all.sh

Sending 'bootloader_b' (8489 KB) OKAY [ 0.440s]

Writing 'bootloader_b' (bootloader) Flashing Pack version b1c1-0.1-5034669

(bootloader) Flashing partition table for Lun = 0

(bootloader) Flashing partition table for Lun = 1

(bootloader) Flashing partition table for Lun = 2

(bootloader) Flashing partition table for Lun = 4

(bootloader) Flashing partition table for Lun = 5

(bootloader) Flashing partition msadp_b

(bootloader) Flashing partition xbl_b

(bootloader) Flashing partition xbl_config_b

(bootloader) Flashing partition aop_b

(bootloader) Flashing partition tz_b

(bootloader) Flashing partition hyp_b

(bootloader) Flashing partition abl_b

(bootloader) Flashing partition keymaster_b

(bootloader) Flashing partition cmnlib_b

(bootloader) Flashing partition cmnlib64_b

(bootloader) Flashing partition devcfg_b

(bootloader) Flashing partition qupfw_b

(bootloader) Flashing partition storsec_b

(bootloader) Flashing partition logfs

OKAY [ 0.501s]

Finished. Total time: 1.073s

rebooting into bootloader OKAY [ 0.055s]

Finished. Total time: 0.106s

Sending 'radio_b' (71148 KB) OKAY [ 2.830s]

Writing 'radio_b' (bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671

(bootloader) Flashing partition modem_b

OKAY [ 0.296s]

Finished. Total time: 3.265s

rebooting into bootloader OKAY [ 0.043s]

Finished. Total time: 0.093s

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

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

Bootloader Version...: b1c1-0.1-5034669

Baseband Version.....: g845-00023-180917-B-5014671

Serial Number........: [serial number, i don't know if that is sensitive data]

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

Checking product OKAY [ 0.060s]

Checking version-bootloader OKAY [ 0.060s]

Checking version-baseband OKAY [ 0.060s]

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

archive does not contain 'boot.sig'

archive does not contain 'boot_other.img'

extracting dtbo.img (8 MB) to disk... took 0.065s

archive does not contain 'dtbo.sig'

archive does not contain 'dt.img'

archive does not contain 'odm.img'

extracting product.img (194 MB) to disk... took 6.038s

archive does not contain 'product.sig'

archive does not contain 'product-services.img'

archive does not contain 'recovery.img'

archive does not contain 'super.img'

extracting system.img (2158 MB) to disk...W/ziparchive(29946): Zip: unable to allocate 2263691568 bytes at offset 0: No space left on device

fastboot: error:

failed to extract 'system.img': I/O error

Since the system.img extraction failed I tried to extract that zip file manually and flash system.img

fastboot flash system ./image-crosshatch-pq1a.181205.006/system.img

Sending sparse 'system_b' 1/9 (262140 KB) OKAY [ 10.677s]

Writing sparse 'system_b' 1/9 OKAY [ 0.366s]

Sending sparse 'system_b' 2/9 (262140 KB) OKAY [ 10.314s]

Writing sparse 'system_b' 2/9 OKAY [ 0.366s]

Sending sparse 'system_b' 3/9 (262140 KB) OKAY [ 9.534s]

Writing sparse 'system_b' 3/9 OKAY [ 0.366s]

Sending sparse 'system_b' 4/9 (262140 KB) OKAY [ 10.504s]

Writing sparse 'system_b' 4/9 OKAY [ 0.366s]

Sending sparse 'system_b' 5/9 (262140 KB) OKAY [ 10.474s]

Writing sparse 'system_b' 5/9 OKAY [ 0.366s]

Sending sparse 'system_b' 6/9 (262140 KB) OKAY [ 10.804s]

Writing sparse 'system_b' 6/9 OKAY [ 0.366s]

Sending sparse 'system_b' 7/9 (262140 KB) OKAY [ 10.374s]

Writing sparse 'system_b' 7/9 OKAY [ 0.366s]

Sending sparse 'system_b' 8/9 (258820 KB) OKAY [ 10.655s]

Writing sparse 'system_b' 8/9 OKAY [ 0.366s]

Sending sparse 'system_b' 9/9 (116836 KB) OKAY [ 4.824s]

Writing sparse 'system_b' 9/9 OKAY [ 0.660s]

Finished. Total time: 91.903s

Earlier I was booting to the android Setup Screen, but the screen was unresponsive. THe power button and volume buttons responded, but then tapping restart or shutdown were not responsive.

Now I get the red text on boot about corruption. The phone appears stuck on the white background with the colorful GOOGLE image on the screen.

Does anyone have any ideas? Do I need to return this to Google.... and do you think they will exchange it? This literally happened in less than 2 hours of having the device.