[Google Pixel Watch 2] badabing2003:
Thanks for the support file.

This is the script that PF executed

@echo off
setlocal enabledelayedexpansion
chcp 437
:: This is a generated file by PixelFlasher v6.6.0.1
:: cd C:\Users\REDACTED\AppData\Roaming\PixelFlasher\factory_images\aurora-ota-twd9.240105.004.a1
:: pf_boot.img: C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4\fa62f7786db3053d3e4f04f6eccfe3a5e0d3e9b6\magisk_patched_26400_fa62f778_8957aa0e.img
:: Android Platform Tools Version: 34.0.5-10900879

set "ACTIVE_SLOT=a"
set "INACTIVE_SLOT=b"
echo Current active slot is: [%ACTIVE_SLOT%]
echo Current inactive slot is: [%INACTIVE_SLOT%]
call "S:\PixelFlasher\platform-tools\adb.exe" -s REDACTED sideload "S:\PixelFlasher\Firmware\aurora-ota-twd9.240105.004.a1-08b3c41d.zip"
if errorlevel 1 (
echo Error: The sideload command encountered an error, aborting ...
echo You should manually reboot to system if necessary.
exit /b 1
)

As you can see, there's really not much in there, top part is comments, then some echo statements, the main call is basically this:

call "S:\PixelFlasher\platform-tools\adb.exe" -s REDACTED sideload "S:\PixelFlasher\Firmware\aurora-ota-twd9.240105.004.a1-08b3c41d.zip"

That part succeeded even though we see 94%, for whatever reasons 94% is actually 100% (I suppose Platform tools progress measuring bug)

and the sideload command did not encounter an error.

Then next thing PF does is this

2024-01-10 16:41:07 Done script flashing!
Sleeping 10 seconds ...

2024-01-10 16:41:17 Getting device: REDACTED state ...
Currently the device is in ERROR mode.

2024-01-10 16:41:18 Getting device: REDACTED state ...
Rebooting device: REDACTED to bootloader ...
Updating connected devices ...
Sleeping 5 seconds to find the device ...
Updating connected devices ...

2024-01-10 16:41:25 ERROR: Your device is not found in bootloader mode.

Sleeps 10 seconds and tries to detect the device.

It couldn't, hence it reports as ERROR mode, though technically that is not necessarily an ERROR, it's just that it is not detected.

Then PF proceeds to reboot to bootloader

This is mainly done to check if the slot was properly switched (that is why there were those echo statements about the slots prior to flashing)

If the slot was not properly switched, PF will not attempt to flash a patched boot / init_boot (to avoid messing up the device)

Otherwise if root option was selected, the patched image will be flashed.

Then the device should reboot to system.

It is not clear if the device actually rebooted to bootloader mode or not, because PF couldn't detect it and aborted at that point.

Do you recall the state of your watch after all was done?

Was it still in sideload? bootloader? or did it reboot to system?

I'm beginning to believe that the newer devices Pixel 8 or newer (mine is p7p) don't get detected after sideload.

The only devices I have seen this happen is Pixel 8 or newer ones.

I wonder when people are manually doing sideload with newer devices, are they able to get any output (after sideload completes) with

adb devices

fastboot devices

and does adb reboot fastboot is working in those cases (so that patch could be flashed prior to booting)

I can never reproduce this on any of my devices.