yashsingh1/xdaforums huggingface dataset:
[Google Pixel Watch 2] roirraW "edor" ehT:
Pixel 8 Pro (already rooted on UQ1A.240105.004, but what the hell):

S:\platform-toolsP8P&PW2&P7P&S\P8P>adb sideload "S:\platform-toolsP8P&PW2&P7P&S\P8P\husky-ota-uq1a.240105.004-dbd5246a.zip"
Total xfer: 2.00x

S:\platform-toolsP8P&PW2&P7P&S\P8P>adb devices (worked)
List of devices attached
none ya recovery

S:\platform-toolsP8P&PW2&P7P&S\P8P>fastboot devices (didn't produce anything)

S:\platform-toolsP8P&PW2&P7P&S\P8P>adb reboot fastboot (worked to get to fastbootd)

Pixel Watch 2 (already on TWD9.240105.004.A1, not rooted):

S:\platform-toolsP8P&PW2&P7P&S\PW2>adb sideload "S:\platform-toolsP8P&PW2&P7P&S\PW2\aurora-ota-twd9.240105.004.a1-08b3c41d.zip"
Total xfer: 2.00x

S:\platform-toolsP8P&PW2&P7P&S\PW2>adb devices
List of devices attached

S:\platform-toolsP8P&PW2&P7P&S\PW2>fastboot devices

S:\platform-toolsP8P&PW2&P7P&S\PW2>adb reboot fastboot
error: no devices/emulators found

On the Pixel Watch 2, adb reboot fastboot resulted in:

Oh, I couldn't read it on the actual screen. Recovery is touch - I was trying to rotate the bezel! :) Maybe I'll remember.
[Google Pixel Watch 2] badabing2003:
Many thanks for testing this.

After typing adb reboot fastboot it actually went into fastbootd and not bootloader? wow.

And did you test if at that point fastboot devices produced anything, ie device was properly detected?

If yes, I'd be curious to know if fastboot reboot bootloader puts it into bootloader mode and gets detected (ie when it is in fastbootd mode)

Actually no, at that point after sideload is completed, PF does

adb -s device_id get-state and if it gets no match, it tries fastboot devices just in case the device is in bootloader / fastboot mode, and when none of them match that is when it reports mode: ERROR

This is followed with

adb reboot bootloader and not adb reboot fastboot

That explains why you got into fastbootd and not bootloader.

And again after attempting to reboot to bootloader, it does fastboot devices to make sure the device is in bootloader mode.

I'm assuming this is right after completing the sideload?

So it is confirmed that adb cannot detect a watch in sideload mode after completing the sideload.

And adb reboot fastboot actually rebooted back to recovery? or was it already in recovery and the command did nothing? (I'm not even sure if the watch supports fastbootd.

Again just like for the phone, PF reboots to bootloader not fastboot.

If it is actually rebooting back to recovery it could be because it does not support fastbootd, I'd be curious if adb reboot bootloader would work and afterwords fastboot devices sees it.

But I suspect not, otherwise PF would have seen it.

It sounds like when sidleload script execution is completed PF should popup a dialog to instruct the user for the next steps.

If they want to root, to select Reboot to Bootloader option (I assume with touch) and then press the right button? and of course click on Continue in PF for it to continue flashing the patch.

Otherwise select Reboot to system now.

PS: You don't have to test, but if you happen to be doing some flashing, keep an eye on the behavior, or if someone reports their experiences, please keep me informed.

At this point I think I have to add that popup for the watch, as I suspect the watch will not be detected and would require user interaction.

But perhaps that is not really the case for the phones (at least based on the above)

Again manh thanks

By the way, I'm ataching the flow diagram of your flashing experience.
[Google Pixel Watch 2] roirraW "edor" ehT:
You're welcome!

I did not, maybe tomorrow. :)

Adding to the queue.

Should I still test the further above two things?

That is correct.

adb reboot fastboot actually rebooted back to recovery.

Adding to the queue.

Will do.

Oh, cool, and cool that Chrome opens SVG just fine - I couldn't remember.
[Google Pixel Watch 2] badabing2003:
Much appreciated

No rush, whenever if ever.

Not really needed, adb reboot bootloader is more important,

Interesting, even though it couldn't be detected, it actually invoked the command and rebooted back to recovery.

If adb reboot bootloader also reboots to recovery, then I need to add the popup, but if for some reason it actually reboots to bootloader, then it could be a timing issue,I can add retry or wait longer.

Thanks
[Google Pixel Watch 2] simplepinoi177:
I intend on updating my and my wife's PW2's sometime in the next 7 days....I updated mine manually for December's, but maybe I'll test out using PF and do those tests and such -- make a support log or something. I just have to really read into the last couple of posts as to what to expect and/or what to look out for....
[Google Pixel Watch 2] roirraW "edor" ehT:
TL;DR - the Watch will be updated 100% just fine by PixelFlasher - you just might find your watch off when it's done sideloading, and I don't know how you boot straight to bootloader or another mode from the Watch being off so that you or PixelFlasher can flash the rooted kernel, and maybe I'm misremembering, but you might have told me how. If not, it was someone else, I just don't recall what it was without researching. :)
[Google Pixel Watch 2] simplepinoi177:
There is a manual way to load into bootloader mode from being off....I learned it through talking to customer support, but found the documentation and put it somewhere in this thread....

But when I manually did it (when first rooting and not sideloading), I just entered into the OS and ran the adb command to get into it...

I wonder if PF waits for the command and if I were to manually boot into bootloader/fastboot mode, will PF continue with what it was trying to do after sideloading/flashing, @badabing2003 ?
[Google Pixel Watch 2] badabing2003:
Right now, PF is not expecting the need for manual intervention and expecting that the commands to detect the device in certain modes and to switch to other modes work.

This is exactly what @roirraW "edor" ehT is testing / tested, to determine if they do.

If it turns out for sure that manual intervention is necessary, I will modify PF to pop a message exactly at the point that is expected and wait for the user to perform the manual step and hit continue when done.

For the watch, @roirraW "edor" ehT already established that when sideload is completed, the device is not detected with either of the two commands.

adb devices

fastboot devices

There is also the command adb get-state, I don't think that was tried manually, but pf logs shows that, that too does not detect.

But regardless of it being detected or not, it looks like adb reboot fastboot worked and the device rebooted to recovery (not fastboot, which doesn't help)

Next is to determine is adb reboot bootloader works and it reboots to bootloader,

For the watch that's the only thing that wasn't manually tested (aside from get-state)

If that works, manual intervention won't be necessary.

Let me know when you're ready to test and I can work with you in pm or here if there is any ambiguity about any of the details.

And thanks again to both of you.
[Google Pixel Watch 2] roirraW "edor" ehT:
S:\platform-toolsP8P&PW2&P7P&S\PW2>adb reboot sideload

S:\platform-toolsP8P&PW2&P7P&S\PW2>adb sideload "S:\platform-toolsP8P&PW2&P7P&S\PW2\aurora-ota-twd9.240105.004.a1-08b3c41d.zip"
Total xfer: 2.00x

S:\platform-toolsP8P&PW2&P7P&S\PW2>adb get-state
error: no devices/emulators found

S:\platform-toolsP8P&PW2&P7P&S\PW2>adb reboot bootloader
error: no devices/emulators found

Tried for the heck of it in that after-sideload state, no luck:
S:\platform-toolsP8P&PW2&P7P&S\PW2>fastboot reboot bootloader
< waiting for any device >
^C

I chose the on-screen after-sideload option to boot bootloader via a swipe down and press the bezel
once, and confirmed fastboot sees the watch:
S:\platform-toolsP8P&PW2&P7P&S\PW2>fastboot devices
none ya fastboot

S:\platform-toolsP8P&PW2&P7P&S\PW2>
[Google Pixel Watch 2] badabing2003:
Thank you, that confirms it for the watch, it requires manual intervention after sideloading.

Interestingly and thankfuly, prior to sideloading, when the device is put into sideload mode, it is detected

Android Platform Tools Version: 34.0.5-10900879

2024-01-10 16:33:22 Getting device: REDACTED state ...
Currently the device is in adb mode.

2024-01-10 16:33:22 Getting device: REDACTED state ...
Rebooting device: REDACTED to sideload ...
ADB waiting device: REDACTED for sideload ...

2024-01-10 16:33:48 Getting device: REDACTED state ...
Device is now in sideload mode.

I'll make the necessary change to guide the user for the manual steps.

Thanks again for the tests.

In your future Pixel 8 flashing, (no need to test now) if you come across similar situation (I hope not) please keep me informed.
[Google Pixel Watch 2] roirraW "edor" ehT:
You're welcome, and I will, thanks!

I wonder if there's any chance Google will change the post-sideload ADB situation on the Pixel Watch 2 at a later date? We shall see.
[Google Pixel Watch 2] badabing2003:
One would hope so.

I see that you're using the latest Platform Tools 34.0.5-10900879

I wonder if you experience similar behavior with 33.0.3 (no need to test now, on next month's update should be good enough)

Incidentally I still use 33.0.3
[Google Pixel Watch 2] roirraW "edor" ehT:
I'll try to remember to keep it in mind. Thanks.
[Google Pixel Watch 2] badabing2003:
New Release:

Jan 20, 2024 v6.7.0.0 change log:

Added history to device image selection (Max 16)

#133 Fix for Get Xiaomi.eu print when version_class is missing.

Improved device state detection with retry attempts.

Updated 7zip binaries to v23.01

Added line numbers to Active Pif window and Output Console window, along with an option to sort FP keys for easy visual comparison.

Pixel watches require user intervention after flashing OTA, added popup messages to guide the user for the next steps.

You can now easily save the Active Pif content into a pif json file (filename automatically build from print information, however user can change before saving)

Keep splash screen visible until the main window shows up.

Under the hood improvements and bug fixes, improved logging and refactoring code.
[Google Pixel Watch 2] fma388:
@badabing2003 Hi !

Is it possible to use your wonderful software just for a full OTA without root and lock bootloader? (I use it with my rooted P8P, but I want to use it with my stock Watch 2)

Thanks again for all your work ! He really deserves donations!
[Google Pixel Watch 2] roirraW "edor" ehT:
I don't have my Pixel Watch 2 rooted, or even bootloader unlocked, and I used PixelFlasher with the Full OTA for the most recent firmware update. Make sure and grab the correct (Wi-Fi or LTE) firmware.

You may have noticed in the changelog that the Pixel Watch 2 so far requires a minimum user interaction during the PixelFlasher process, but the changelog notes that one or more informative interaction dialogs will be presented to you when appropriate.
[Google Pixel Watch 2] fma388:
Thank you for your reply, I'll hurry up and update it then :D:D
[Google Pixel Watch 2] badabing2003:
New Release:

Jan 29, 2024 v6.7.1.0 change log:

Added an checkbox in Pif Manager. Keep All Keys which allows any unrecognized key to be kept in the json file when using smart paste. This allows support for future keys that could be added but are unrecognized today. (Example: KERNEL)

Added Cleanup DG but in Pif Manager to clean up Droidguard cached files. Helps in some situations.

Miscellaneous small improvements.
[Google Pixel Watch 2] roirraW "edor" ehT:
Hello! Me again.

No emergencies and things went really well, but just a few weird things.

First time flashing the Pixel Watch 2 since you gave PixelFlasher the dialog box for after the watch reaches recovery mode, although in my case since I'm not rooted/not bootloader unlocked and therefore not flashing a kernel, there's no actual need for me to do anything but tell recovery to reboot. Also note that by default (at least currently), the reboot to system option is chosen already.

I flashed the February update OTA twice without any additional options chosen. After the first slot was done flashing, and I got the PF dialog box, but I did as instructed - had the watch reboot to system, and clicked the dialog box's button to continue, even though there wasn't anything to really continue with, then I had PF flash the other slot.

I noticed the second time around that PF brought up a dialog box saying something like "my current phone is" (it didn't specify), and telling me I'm flashing Aurora (Pixel Watch 2 Wi-Fi) firmware, so be careful, etc.

Then, when I started the process, the log said:

Current active slot is: []
Current inactive slot is: [a]

For the first OTA, previous to this second OTA, everything was normal, with current being a and inactive being b.

Lastly, after the second OTA was done and the dialog was brought up, the log said that the device was in error mode, but it was actually in recovery mode as normal, with "reboot to system" pre-selected as always.

The watch is working as normal.
[Google Pixel Watch 2] roirraW "edor" ehT:
That's correct, I did click on it right away after telling the watch to reboot. I second-guessed my initial interpretation of the dialog message, and I thought it couldn't ultimately hurt (which it didn't), so I thought I'd try. I think a second/middle part of the dialog message is what influenced me to guess wrong.

I didn't even think to try re-scanning. Thank you!

Thanks!

I've now given both phones Shell root permission. I don't recall ever being prompted to give it permission, but if I was and just forgotten, it's possible I denied it because I didn't know why I was being prompted to grant it.
[Google Pixel Watch 2] LLStarks:
For watches, it might be helpful to add a toggle in the Magisk menu to set root response (grant, deny, prompt).
[Google Pixel Watch 2] badabing2003:
I'll see if Prompt is an option that I can set.

Allow and Deny are already there.
[Google Pixel Watch 2] LLStarks:
Is that per app or global? I'm referring to global automatic response, which you have to set the first time manually.
[Google Pixel Watch 2] badabing2003:
I checked, and I remember now, that is not saved / read from magisk.db

I would have added it otherwise.
[Google Pixel Watch 2] badabing2003:
New Release:

Feb 16, 2024 v6.8.0.3 change log:

Added untested support for patching with KernelSU for Pixel phones. Patching with APatch is in the works.

Detect known blacklisted kernel names, and notify the user. (list is current as of this release date).

Rename the SOS button to reflect that the modules would be removed instead of being disabled.

Removed bulk install APK feature which installed all APKs in a directory, instead reworked the Install APK feature to allow user choice multi-select, and added another option Bypass low target SDK block.

Report device Kernel and KMI.

Added Android Platform Tools 34.0.4 to known problematic versions list, which when detected warns the user.

Improved Pixel Watch flashing dialog messages.

New feature: #152 Show System Apps and Show 3rd Party Apps in Package Manager.

Bug Fix: #157 'PifManager' object has no attribute 'first_api' in some situations.

Bug Fix: scrcpy download link was not working.

Support for upcoming PlayIntegrity Fork v8 changes by @osm0sis.

Added Special Magisk 27001 install option when selecting Magisk install. (This is similar to Special Magisk 26401, just a version difference).

Support for SSL error fallback for all https requests (previously was only for PIF downloads).

Improved factory / image downloading with lower memory footprint.

Miscellaneous minor bug fixes and enhancements.
[Google Pixel Watch 2] badabing2003:
Update Release:

Feb 17, 2024 v6.8.0.4 change log:

Use MacOS 13 to build with Github actions instead of MacOS 11, sorry to folks who use older MacOS, unless I get it to build it successfully on Github, MacOS 13 will have to do.

#158 Fix the App version.

Note: The following versions have identical code 6.8.0.0, 6.8.0.1, 6.8.0.2, 6.8.0.3, 6.8.0.4, the differences are in Github actions.
[Google Pixel Watch 2] badabing2003:
Update Release:

Feb 29, 2024 v6.8.1.0 change log:

Update Xiaomi apk download function to handle exceptions and work with the latest version.

#160 Update readme to add pre-requisites for MacOS and Windows platforms.

#161 Auto detect file encoding before opening a file.

Don't check for Magisk path if in recovery mode.

Misc. bug fixes and improvements.
[Google Pixel Watch 2] badabing2003:
New Release:

Mar 03, 2024 v6.8.2.1 change log:

Bundle in the executable the missing files android_version.json and android_devices.json otherwise patching with KernelSU won't detect your Pixel as Pixel device.

Add back Magisk Alpha install option, thanks to pull request from @hldr4

Make Magisk install window resizable.

Add right click option on the selected Magisk to download in case you just want it downloaded and not installed.

Update all old forum.xda-developers.com links to xdaforums.com

Make Pif Manager work without a device being connected (obviously for props / pifs management and not for updating / testing pifs).

Typo fixes and other minor improvements.
[Google Pixel Watch 2] badabing2003:
Update Release:

Mar 11, 2024 v6.8.3.0 change log:

Fix MacOS builds, we're finally back to buiding with MacOS 11 (fingers cross it lasts).

If internet is not available, do not try to build a menu with Google Devices.
[Google Pixel Watch 2] badabing2003:
New Release:

Mar 19, 2024 v6.8.4.0 change log:

When patching with KernelSu on devices that have init_boot partition, patch boot partition, not init_boot.

Added Dev Tools | keybox.xml validity checker (credit to @hldr4)

Extra Img Extraction setting now additionally extracts dtbo, vendor_boot, vendor_kernel_boot, super_empty (useful for some ROMs).

When custom patching, Paste button will automatically paste the path to the (extra) image type selected.

Improved logging.
[Google Pixel Watch 2] badabing2003:
New Release:

Mar 26, 2024 v6.9.0.0 change log:

Add support for patching KernelSU LKM (Kernel modules, GKI only). This is in addition to the classic KernelSU support.

Add support for patching with APatch

Rename Install Magisk to Install Root App as it now supports directly installing KernelSU and Apatch through PixelFlasher.

Add Install ZygiskNext module option in Magisk tool options.

Use UTF-8 encoding for the logifile instead of ISO-8859-1

Miscellaneous minor improvements.
[Google Pixel Watch 2] badabing2003:
New Release:

Apr 05, 2024 v6.9.1.0 change log:

#181 Handle KernelSU new output filename format.

#187 register exit menu id for MacOS to OS's "Exit" menu.

KernelSU bug fix and improvements.

Improved logging to further easy troubleshooting.

Update banned kernels list.

Update and re-add Magisk zygote64_32 canary with a forked URL.

Minor typo corrections and other improvements.
[Google Pixel Watch 2] badabing2003:
Update Release:

Apr 09, 2024 v6.9.1.3 change log:

Fix regression introduced when refactoring code in KernelSU Patching.

#187 On MacOS, move the exit menu into PixelFlasher's file menu from the OS's native Exit menu.
[Google Pixel Watch 2] badabing2003:
New Release:

Apr 14, 2024 v6.9.2.0 change log:

Add a new experimental feature to downgrade without a wipe and potentially switch from Beta to Stable without a wipe (untested).

Credit to @tbalden for the discovery and @capntrips for the details of the process.

Select any img file and get additional image info.

#190 fix, scrcpy launch improvement.

Improved Menu to disabled advanced features when it's not enabled in the settings. (Previously only other GUI elements were hidden or disabled).

If KernelSU or APatch is installed, report their version as part of device details.

Improved logging.

Improved santization.

Other minor improvements and added stability.
[Google Pixel Watch 2] badabing2003:
Update Release:

Apr 16, 2024 v6.9.2.5 change log:

Roll up MacOS related changes. #187 and #190

Logging improvements

When Magisk delta is installed, automatically set the package to: io.github.huskydg.magisk
[Google Pixel Watch 2] Griggabyte:
Hello. Hoping someone can provide some guidance, first time rooting anything but I'm usually pretty cluey with this stuff.

Just to summarise, I'm hoping to root my PW2 so I can trim down some of the factory loaded apps and features that slow it down or reduce battery performance. Ideally I'd like a custom ROM, but I don't think there are any out yet, I'll be monitoring that space, though.

I've followed this guide (https://xdaforums.com/t/april-2-202...-updates-root-directions-by-llstarks.4635402/) from user: (roirraW "edor" ehT) but I'm stuck on the final few steps. The error I keep encountering is that I am losing connection to the watch when the bootloader reboots and it times out.

I believe I have the correct Google USB Drivers installed, but I'm obviously missing something. Hoping someone can provide some clarity, thanks.

JG
[Google Pixel Watch 2] badabing2003:
Have you unlocked the bootloader first? which will do a data wipe.
[Google Pixel Watch 2] Griggabyte:
Possibly not, where would I initiate that?
[Google Pixel Watch 2] badabing2003:
Follow the guide written by @roirraW "edor" ehT

After step 5, you can use PixelFlasher's built in unlock feature or continue the steps in the guide.
[Google Pixel Watch 2] Griggabyte:
Yeah, I did try that but the option is greyed out, I did get the watch through my Telco so it's potentially locked.

Thanks for your help, anyway.
[Google Pixel Watch 2] roirraW "edor" ehT:
If "OEM unlocking" is grayed out, and therefore you can't enable it, then indeed, until/if you can ever unlock the bootloader, you won't be able to root your device. You can still use PixelFlasher to update your device - just not patch/root it.

Different telco's have different standards of operation regarding if or when you would be able to unlock the bootloader (if ever). With some, you can never, with some others you can once various combinations of paying off the device(s) and/or enough time has passed. In some cases, merely talking to the carrier and asking will convince them to "carrier unlock" it - also sometimes referred to as "SIM unlock", but I prefer the former terminology as there's something completely separate where you can electronically "lock" a SIM to a device, so it sounds too similar while not even being close.

Carrier unlocking a device isn't the same thing as bootloader unlocking, but the latter frequently depends on the former being enabled, and only your carrier can set your device to be carrier unlocked.
[Google Pixel Watch 2] badabing2003:
One other thing,

If you want to freeze / disable some apps / packages, you can still do so with PixelFlasher

Use the App Manager feature, Click on Get All Application Names (so that you know what they are) then select the ones you want to disable and disable them.

You want be able to delete the system apps and get space back, but you would be able to freeze them and not have them consume cpu / battery.
[Google Pixel Watch 2] badabing2003:
Update Release:

Apr 19, 2024 v6.9.3.0 change log:

Update AVBTool to use RSA library instead of depending on an external openssl.

English typo corrections.

When flashing OTA, give the option to continue, even if it is a downgrade.

Github action: Fix MacOS build deployment issue.
[Google Pixel Watch 2] badabing2003:
Update Release:

May 08, 2024 v6.9.4.0 change log:

Added encryption to support.zip for extra privacy / security.

Regression bug fix: When a Magisk module was disabled in Magisk, it was not reflected in PixelFlasher.

Added Refresh button to refresh Magisk module list at will.

When Apply Custom ROM checkbox is checked, make sure that a ROM file is also selected, otherwise ignore the selection.

After rebooting to bootloader, if the device is not detected, sleep 5 seconds and try again.

Update Readme to include a link to proper USB driver setup on Linux systems.