[Google Pixel 7 Pro] simplepinoi177:
Yeah...it still hadn't done the product, system, system_dlkm, system_ext, vendor, & vendor_dlkm that it does in fastbootd. I think I might have been in trouble if it did any of those before crapping out...

This is

exactly

what I was worried about! I was only fairly concerned at ending the process at that point since it wasn't in the middle of doing all the multi-part sparse writing, but I was panicking at the thought that what had already been written wasn't "paired" with the proper accompanying images that is installed in fastbootd and it wouldn't like the older revision versions that were still in place...

I might have considered that, but I was already in fastbootd mode, not bootloader mode. I was there when roirraW "edor" ehT saw a whole lot of people bootlooping their phone because of messing around in fastbootd mode (they would manually select to reboot while flash-all was still flashing the sparse parts or disconnecting device when in that mode while it was writing) and he thus made that big print warning in the OP. I'm even credited in the OP for the info that flash-all flashes in fastbootd, because when up to the Pixel 5, it wasn't flashing in that mode and it surprised newbies like me.

I never considered you could run any commands in fastbootd mode...! when I first learned of adb/fastboot commands, things were only done in bootloader mode where there weren't any real manual button commands; so, for whatever reason, I had the preconceived misconception that you could only do it in that state. I mean it makes sense one should be able to do in fastbootd mode since you could run adb commands in recovery and TWRP environment...

If I knew, I would certainly have tried to run the fastboot command to reboot directly back into fastbootd instead. It might've been tricky since I had to manually close/stop the command prompt because it was stuck at "waiting for any device", but I might've pulled it off opening a second command prompt and attempting that way...🤷‍♂️

hmmm...I wonder. I've never dealt with such a fickle phone like the Pixels; initial problems could be out-of-date drivers, if not then it could be out-of-date platform tools, if not then it could be USB-C and it's better to use USB2.0 for some reason, if not then it could be the factory image and bad "partitioning" (why it validates partitions) and that's why you should check the checksum (glad Google includes it.). Something so randomly fickle, I wouldn't be surprised if, for whatever reason, it was re-using an old, already-completed, different adb-server running command prompt that caused the "hiccup". I didn't think much of it because I've done similar in the past (may be not days later necessarily), but 🤷‍♂️

I know for sure I have no other platform tools because I've seen too many people (since way back from the Pixel 2 XL days) that have unzipped it in multiple places and gotten confused. Now I only keep one set/folder of it extracted, in one specific location (not in documents, desktop, program files, root C is a good idea but i like mine in a specific place because I organize all my phone stuff in a specific spot [ocd mindset]), and I delete it whenever I update platform tools and/or when I want peace of mind and want to extract a fresh folder of it.

Thank you. I am too...it's such a relief because I hate dealing with soft-bricks; I go into panic mode. At least it's better than back with the original Motorola Droids & Galaxy S's.... When I came to the Pixel, I was so happy to see how Google set up bootloader mode and the ability to apply factory images without wiping the device! You could even resize/reflash specific partitions/images! All you could do with the og Motorola Droids and old Samsung Galaxy's were to apply the whole factory images and hope you backed everything up and can apply the backups because everything would be wiped!