[Google Pixel 7 Pro] Ingenium13:
I'm unable to run fastboot update from an m1 Mac. It flashes the initial set of partitions fine, but when it reboots to fastbootd, it hangs and never moves on to the "waiting for device" step.

Bootloader Version...: cloudripper-1.0-9074510
Baseband Version.....: g5300g-220908-220908-B-9040061
Serial Number........: <redacted>
--------------------------------------------
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 'a' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.213s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.573s]
Writing 'boot_a' OKAY [ 0.086s]
extracting init_boot.img (8 MB) to disk... took 0.044s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.197s]
Writing 'init_boot_a' OKAY [ 0.017s]
extracting dtbo.img (16 MB) to disk... took 0.057s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.394s]
Writing 'dtbo_a' OKAY [ 0.023s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.006s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.025s]
Writing 'pvmfw_a' OKAY [ 0.004s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_a' OKAY [ 0.003s]
extracting vendor_boot.img (64 MB) to disk... took 0.214s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.571s]
Writing 'vendor_boot_a' OKAY [ 0.086s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.167s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_a' (65536 KB) OKAY [ 1.578s]
Writing 'vendor_kernel_boot_a' OKAY [ 0.079s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]

On my Linux computer, once it gets to "rebooting into fastboot", the next step is "waiting for device". Then the flashing continues. But on my Mac it gets stuck here. It's as though it doesn't recognize that the USB device disconnected. I tried unplugging the cable and plugging it back in, but it remains stuck and doesn't continue. I tried using a USB 2.0 cable (both USB-C to C, and a C to A adapter with an A to C cable), but that didn't help. I also tried forcing it to run in x86 mode via Rosetta 2. "Fastboot devices" correctly shows that the phone is detected.

On my Pixel 6 Pro, I was able to just interrupt fastboot update and run it again while the phone was in fastbootd, and it would flash fine. But things changed on the Pixel 7 Pro and it can't get past dtbo while in fastbootd

extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.002s]
extracting boot.img (64 MB) to disk... took 0.211s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.617s]
Writing 'boot_a' OKAY [ 0.095s]
extracting init_boot.img (8 MB) to disk... took 0.044s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.203s]
Writing 'init_boot_a' OKAY [ 0.017s]
extracting dtbo.img (16 MB) to disk... took 0.065s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.408s]
Writing 'dtbo' FAILED (remote: 'No such file or directory')

Has anyone been able to get fastboot update to work correctly on a Mac? Or have any other suggestions or workarounds?