This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New update for FR255 stuck in boot loop

I was asked to install a new update this morning and my watch has been rebooting for the past 45 minutes. It appears to get to a screen where it says "loading FIT files" then crashes and tries again. Any suggestions?

0 2781569 over 2 years ago

I fixed the problem. I connected it to Garmin Express and after a few syncs, a pop up informed me that an error log could not be synced. I went to the Garmin folder and removed the "sync" folder from the watch. Then I resynced the watch and it restarted without an issue.

0 2bluesc over 2 years ago in reply to 2781569

Experiencing the same issue, unfortunately I can't get it to connect to Garmin Express and haven't used Garmin Express in years.

Can you provide more details? My device just repeatedly reboots when plugged in to a computer.

0 Garmin-Sierra over 1 year ago in reply to 2bluesc

Please see My FR255 is in a boot loop all day after an attempt at a firmware update today for the main thread about this. Kevin posted this work around:

First, you will need to get your device into mass-storage mode. You can use instructions contained in (My Forerunner Will Not Fully Turn On).

1. Go to the Garmin Folder of your watch.
2. Go to the Apps Folder
3. Delete the .PRG files
4. Remove from Mass Storage

If you are unable to get the device into mass storage, please attempt a non-vol clear (master reset) which should recover the device.

1. Ensure the watch is powered off.
2. You may need to hold LIGHT for up to 30 seconds to turn the watch off.
3. Press and hold DOWN, START/STOP, and BACK/LAP.
4. Press LIGHT to power the watch on while holding these three buttons.
5. After the first beep release START/STOP.
6. After the second beep release the remaining buttons.

Software version 13.23 should prevent it from happening again, but make sure to update to 14.15 which is the latest version. If you are still experiencing this after the updates, please start a new thread.