Your Pixel Watch 4 lights up with the Google logo, and then nothing. Or it shows the logo, goes black, and loops back to the logo. This usually means Wear OS 6.1 hit a snag during boot. A botched firmware update, a corrupted app, or a one-time glitch are the most common culprits.
The first thing to try is a force restart. On the Pixel Watch 4, press and hold the crown and the side button together for about 35 seconds. Keep holding until you see the Google logo flash and the watch restarts. That’s the full force restart sequence for this model, longer than on most watches.
Force Restart the Pixel Watch 4
Press and hold the crown and the side button simultaneously. These are on the right side of the watch. Keep holding for a full 35 seconds. If the watch makes it past the logo and boots normally, you’re set. It was probably a brief background process hang.
If it still loops to the logo, let go after 35 seconds and try again. Sometimes two attempts do the trick if the first didn’t register properly.
Make Sure You’re Using the Right Charger
The Pixel Watch 4 uses a side-pin charging dock, not the magnetic puck from the Pixel Watch 3. They are not interchangeable. If you’re using an old charger, the watch won’t charge at all. Check that the side-pin dock clicks into place on the left side of the watch.
The dock is designed so you can still see the watch face while charging, which is handy if you’re waiting for it to come back to life. It also charges faster than the previous generation.
Charge for 30 Minutes Before Retrying
A critically low battery can prevent the watch from completing its boot sequence. Place the watch on the side-pin dock and leave it for at least 30 minutes. The side-pin allows the watch to be readable, that’s fine, leave it plugged in.
After 30 minutes, try another force restart. If the watch died mid-update, a full charge sometimes gives it enough juice to finish the process.
Boot Into Recovery Mode and Reboot First
If the force restart doesn’t get past the logo, boot into Recovery Mode. To do this, begin a normal restart (press and hold the crown and side button) and then release both as soon as the watch starts to vibrate. Immediately press and hold the crown and side button together again until you see the recovery menu. This takes some timing; if it doesn’t work on the first try, let the watch fully die or drain the battery and try again.
In Recovery Mode, use the side button to navigate and the crown to select. Choose Reboot first. This often fixes a botched boot without losing any data.
Wipe the System Cache
If rebooting from Recovery doesn’t resolve the loops, the system cache may be corrupted. Go back into Recovery and choose Wipe cache partition. This clears cached system files without removing your apps, settings, or health data.
The process takes about 30 seconds. After it finishes, select Reboot. The watch will boot fresh with a clean cache. Apps may load a little slower the first time as they rebuild their caches, but the boot loop should stop.
Factory Reset From Recovery
If wiping the cache doesn’t work, you’ll need a factory reset. This erases everything on the watch, all apps, settings, and any health data not yet synced to the Fitbit app or Google Fit. Only do this if the cache wipe fails.
Boot back into Recovery Mode and select Wipe data/factory reset. Confirm with the crown. The reset takes 5 to 10 minutes. Once done, choose Reboot. The watch will boot to the initial setup screen. Re-pair it using the Google Pixel Watch app on your phone. Any data already synced to Fitbit or Google Fit is safe.
Reset From the Google Pixel Watch App
If the watch is stuck but still shows as connected in the Google Pixel Watch app on your phone (sometimes it briefly connects between boot loops), you can trigger a remote reset. Open the app, go to Watch settings > General > Reset and confirm. The phone sends the reset command to the watch.
This works only if the Bluetooth connection manages to establish itself during the brief moments the watch is responsive. It’s hit-or-miss, but worth trying if you see the watch appear as connected in the app even briefly.
