COROS watch update problems: what to do before a firmware update—and if your watch won’t start.

Published 2026-06-21

A watch firmware update is supposed to be routine. When the progress stops, the screen freezes, or the watch never returns to normal, it can put years of trust—and tomorrow’s run—into doubt. The safest response is not a frantic sequence of resets. It is a controlled checklist that preserves data and support evidence while separating a recoverable interruption from a genuinely unusable device.

Start with the scope: reports are not a universal failure

A cluster of failure reports can be meaningful without proving that an entire product line is affected. Different users may have different watch models, firmware builds, app versions, phone operating systems, battery states, connection paths, or failure points.

That distinction matters. “Some watches reportedly failed during or after updates” is supportable. “The latest COROS firmware bricks watches” is too broad unless COROS confirms the specific release, devices, and scope. This guide therefore focuses on durable risk reduction and recovery rather than trying to predict which watch will fail.

Before updating: make the process low risk

The most important work happens before you tap Update. A two-minute preparation routine can protect recent activities, reduce interruption risk, and give support a cleaner record if something goes wrong.

• Sync recent activities first. Open the COROS app, complete a normal sync, and confirm important workouts appear in the account—not only on the watch.
• Charge the watch and phone. Do not begin with either device near empty. The goal is comfortable power margin for the download, transfer, installation, and restart.
• Use a stable connection. Choose the Bluetooth or Wi‑Fi method offered for your device, stay near the phone or access point, and avoid moving between networks.
• Keep the COROS app open. COROS warns that closing the app during the download can interrupt data transfer.
• Document the starting state. Take screenshots of the app version, watch firmware version, device page, and any update notice. Note the date and time.
• Remove the deadline. Do not update immediately before a race, key workout, travel day, or backcountry trip. Leave time to test GPS, sensors, buttons, charging, and syncing afterward.
• Know the fallback. If the watch is essential for an event, have a basic backup: another watch, a phone recording app, course notes, or manual splits.

During the update: boring is good

Start the update when you can leave both devices alone. Keep the watch close to the phone, keep the COROS app in the foreground when instructed, and avoid toggling Bluetooth, rebooting the phone, force-closing the app, or placing either device into a low-power state.

A pause is not automatically a failure. Firmware installation can include periods when the screen changes slowly or the watch restarts. Give the documented process reasonable time before intervening. If COROS publishes a model-specific instruction or status notice, follow that rather than a generic forum recipe.

Classify what happened before trying to fix it

“Bricked” is often used loosely online. A boot loop can look catastrophic and still be recoverable. A failed transfer may leave the previous firmware working. A truly unusable watch is one that remains nonfunctional after normal supported recovery—not merely a watch that showed one error screen.

If the watch will not start: use a controlled recovery ladder

The exact power button varies by COROS model, so do not assume another runner’s button sequence applies to yours. Check the current COROS power-on instructions for the device-specific control.

1. Photograph or record the current state. Capture the screen, logo loop, charging response, app error, and any visible percentage or code before it changes.
2. Confirm basic power. Inspect the cable and contact points, use an appropriate power source, and allow the watch time to charge. A black screen can be a power problem rather than firmware failure.
3. Use the supported long-press restart. COROS currently instructs users with a non-starting watch to connect power and hold the model’s power control for about 15 seconds or until the logo appears. Follow the current model-specific page, not this summary, if the instructions differ.
4. Retest normal startup and syncing. If the watch starts, let it settle, reconnect through the normal app flow, and check core functions before attempting another update.
5. Treat reset as a later step. COROS says a factory reset removes data and personalized settings stored on the device, while already-synced account data is retained. Use the current COROS reset guidance or direct support instructions rather than resetting reflexively.
6. Escalate when normal recovery fails. Use Profile > Customer Support > Contact Support in the COROS app, or the official support request path. Ask for device-specific guidance before repeating resets.

What not to do

• Do not repeatedly disconnect power or force-restart the watch during an active installation without official direction.
• Do not install firmware files from unofficial mirrors or use model-mismatched recovery packages.
• Do not factory-reset before confirming important activities have synced and documenting the failure.
• Do not remove and re-pair devices in multiple places at once; that can create a second Bluetooth problem on top of the update problem.
• Do not claim the watch is permanently dead before completing supported power and restart checks.
• Do not keep retrying the same failed update immediately before a race. Use the working fallback and troubleshoot later.

Build a useful support packet

“My watch is broken” gives support little to work with. A short, structured record can reduce back-and-forth:

• Watch model, serial number, and approximate purchase date.
• Phone model, phone operating-system version, and COROS app version.
• Firmware version shown before the attempt, if recorded.
• Date and time of the update and whether Bluetooth or Wi‑Fi was used.
• Approximate watch and phone battery levels.
• The exact point of failure: download, transfer, install, restart, pairing, or first boot.
• Photos, screen recording, or video of the app error, frozen display, or boot loop.
• Every recovery step attempted and the result of each one.

If the app can still communicate with the watch, submit the request through the app so COROS can associate it with the device and account. Avoid deleting useful logs or resetting until support evidence is preserved.

Race-week rule: stability beats novelty

A firmware update may promise a feature you want, but a known-working watch is more valuable than a newly updated watch the night before a race. Unless an update addresses an urgent issue you already have, delay it until after the event and recovery period.

After any update, test a short easy run before trusting the watch on race day. Confirm GPS lock, heart-rate behavior, buttons and dial, alerts, battery drain, activity saving, and app sync. Our race-day wearable checklist covers the rest of the setup, while the GPS accuracy guide explains how to judge post-update tracking without overreacting to one route.

Bottom line

Recent update-failure reports are a reason to prepare, not a reason to assume every COROS watch is at risk. Sync first, create power and connection margin, document the starting state, and choose a time when failure will not ruin a race or trip. If the watch freezes or will not start, classify the state, preserve evidence, use only current COROS-supported recovery steps, and contact support when normal recovery fails.

FAQ