[Google Pixel 2 XL Questions & Answers] ivivaitylin:
So, my phone's kinda stuck right now. Decided to do a bit of a clean slate and just flash up from 8 to 9. Downloaded the latest factory image from google, updated the platform tools, and ran the flash-all.bat

And I get this:

Sending 'bootloader_a' (36336 KB) OKAY [ 0.829s]

Writing 'bootloader_a' OKAY [ 0.373s]

Finished. Total time: 1.213s

rebooting into bootloader OKAY [ 0.010s]

Finished. Total time: 0.012s

Sending 'radio_a' (60388 KB) OKAY [ 31.819s]

Writing 'radio_a' OKAY [ 0.569s]

Finished. Total time: 32.404s

rebooting into bootloader OKAY [ 0.008s]

Finished. Total time: 0.011s

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

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

Bootloader Version...: TMZ20k

Baseband Version.....: g8998-00253-1805232234

Serial Number........: <Removed>

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

Checking product OKAY [ 0.004s]

Checking version-bootloader OKAY [ 0.002s]

Checking version-baseband OKAY [ 0.001s]

extracting boot.img (40 MB) to disk... took 0.164s

archive does not contain 'boot.sig'

archive does not contain 'boot_other.img'

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

archive does not contain 'dtbo.sig'

archive does not contain 'dt.img'

archive does not contain 'odm.img'

archive does not contain 'product.img'

archive does not contain 'product-services.img'

archive does not contain 'recovery.img'

archive does not contain 'super.img'

extracting system.img (2207 MB) to disk... took 11.705s

archive does not contain 'system.sig'

extracting system_other.img (322 MB) to disk... took 1.760s

archive does not contain 'system.sig'

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

archive does not contain 'vbmeta.sig'

extracting vendor.img (351 MB) to disk... took 1.914s

archive does not contain 'vendor.sig'

archive does not contain 'vendor_other.img'

Sending 'boot_a' (40960 KB) OKAY [ 0.933s]

Writing 'boot_a' OKAY [ 0.376s]

Sending 'dtbo_a' (8192 KB) OKAY [ 0.190s]

Writing 'dtbo_a' OKAY [ 0.081s]

Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 12.344s]

Writing sparse 'system_a' 1/5 OKAY [ 2.452s]

Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 12.275s]

Writing sparse 'system_a' 2/5 OKAY [ 2.389s]

Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 12.322s]

Writing sparse 'system_a' 3/5 OKAY [ 2.444s]

Sending sparse 'system_a' 4/5 (521176 KB) OKAY [ 12.111s]

Writing sparse 'system_a' 4/5 OKAY [ 2.375s]

Sending sparse 'system_a' 5/5 (166784 KB) OKAY [ 3.961s]

Writing sparse 'system_a' 5/5 OKAY [ 0.768s]

Sending 'system_b' (330216 KB) OKAY [ 7.476s]

Writing 'system_b' OKAY [ 1.505s]

Sending 'vbmeta_a' (4 KB) OKAY [ 0.009s]

Writing 'vbmeta_a' OKAY [ 0.019s]

Sending 'vendor_a' (360340 KB)	FAILED (Write to device failed in Sendbuffer() (Unknown error))

Finished. Total time: 138.377s

If I want to try flashing again I need to restart the bootloader from the phone. And worse is that I can't actually boot my phone. It pops up the warning that it's corrupted, and if I continue anyway it just sits on the google screen.

So... any ideas for solutions? I've seen some suggestions through googling that mention trying using different usb cables and ports. Unfortunately this is the only C cable and port I have, so limited options for the moment. But since most of the other large files seemed to transfer ok, would that really do it? And until I can get hold of such a cable, is there anything else I can do to try and get my phone working in the meantime?

Thanks!

Edit: I've now also tried it using the September image as well as the October one. Exactly the same problem with exactly the same file. No idea what that means or if that info helps, but I guess it means the problem wasn't with a bad download or anything.