Related
Options

Crashing on boot 18.14

7895069
8 months ago

Is anyone else stuck in the boot phase after updating to 18.14?

I have a 7 Pro Sapphire. After update the watch was stuck in boot phase. I have tried a hard reset, and repairing with the phone, and will work after that. But once i try to sync with garmin explore, the watch crahses when it’s loading the coarses and then begins the bootloop constantly again. I have tried this 3 times already. I also plugged into Garmin express with no fix. Very frustrating. 

  • 0 8 months ago

    Same here, but F7X Solar Sapphire. After the update, my watch boots but restarts itself after about 5 seconds. Did several soft resets with no result. After a hard reset the watch booted correctly. After setting it up as new device in connect, als synched well. But when I started an activity, the watch started rebooting itself again and again. Tried several times, also with loading a back-up from connect, which resulted in the same behaviour. Until now I had no issues with my watch.

    Any advice on how to get back a functional F7X?

  • 0 8 months ago

    if this help

    ------------------------------------------------

    Escaping from the boot loop

    Next let's get your watch cleaned up so it stops boot looping. We will master reset the watch to do this, however, we have a feature that will help you recover your preferred settings easily.

    Once again we need to start with the watch turned off, so if needed, repeat #2 in the section above.

    1. With the watch Off, press the Power button once to tell it to begin powering on. Then immediately begin pressing and holding the Start and Back buttons.
    2. Wait for the watch to beep once, then release the Start button.
    3. Wait for the watch to beep a second time, then release the Back button.
    4. This will have initiated a master reset on the watch. In the majority of cases, this master reset will clear out the problem causing the boot loop and bring your watch back to normal functionality.
    5. If your watch continues to boot loop after this master reset, or if you fail to hear the beeps, please comment again to let us know, and we can continue troubleshooting.
    6. While the watch is resetting, take a moment to clean up the Garmin Connect Mobile app (and your phone) to ensure that re-pairing works smoothly.
    7. Open GCM and go to the More menu, then scroll down and select Garmin Devices.
    8. From the Garmin Devices page, tap and hold on your Fenix/Epix watch. Select the option for Remove Device.
    9. Then also open the Bluetooth menu of your phone and remove your fenix/epix watch from here too.
    10. By this time your watch should have finished resetting, or be close to it. You can now re-pair the watch to Garmin Connect Mobile.
    11. During pairing, the app will prompt you and ask if you would like to restore from a backup. For ease of use, I would recommend following these steps.
    12. Our Device Settings Backup feature will help you reapply your desired settings, such as watch face options and which activity profiles you use. By default, backups are automatically generated around midnight every day. So there should be a recent backup pending for you to be able to restore from.
    13. Following the steps to restore from backup will help your watch get back up and running without you needing to remember all your preferred settings. Please note that wifi networks and Garmin Pay details are not included in the backup, for privacy reasons.
    14. There is a rare chance that the boot loop you experienced is because of a specific device setting. In which case restoring from the backup might reintroduce the boot loop you've seen. I do not expect this to occur for you, but if this happens please let us know, and we can investigate further.
    15. More info on using this Backup and Restore feature is available here:  https://support.garmin.com/en-US/?faq=fLogiPl4Vr5p8u0bFNWmK7
    16. You do not have to restore from a device backup if you do not want to do so.

     

    Thanks, 

    Garmin Outdoor Quality Team

  • 0 8 months ago in reply to socorsu

    Thanks a lot, the master reset seemed to have solved the issue for me. At least the watch boote up as normal, I was able to synch with Garmin Connect (without re-installing the back-up or previous settings, just as recommended). However, VO2max as well as other metrics synched automatically to the watch (is that due to true up?), so I only have to reconfigure the data pages for my activities and the watch face. I even did a short 30 minutes trail run, and everything performed as expected (using firmware 18.14).

    Cheers,

    Eike

  • 0 8 months ago in reply to _Eike

    my pleasure if this help this help you.

    the good solution now would be that Garmin works on software quality, we will have a better user experience with our 800-1000€ watches

  • 0 8 months ago in reply to _Eike

    Vo2max and other datas are stored in your garmin connect acct.  So even without restore, you get those back (as long as you are logged in Garmin connect app

  • 0 8 months ago in reply to Mike Y

      Thanks for the clarification!

  • 0 8 months ago

    All just to add some closure. I was in Garmin support chat for a few hours (thanks Chandon). It was determined there might have been a corrupted waypoint or course in Garmin Explore, that was causing the crash. 

    To fix, I had to perform a hard reset, then force close Explore on my phone so it wouldn’t auto sync, then resync the watch with Connect after the watch reset. I did perform the backup/restore for my settings. Then I shut the bluetooth off on the watch, opened explore, and deleted all courses and waypoints. Then was able to resync with Explore, and created new waypoints and courses that sync’d okay with the watch. 

    These courses/waypoints were on the watch and functioning prior to the update. But something in the update didn’t mesh with at least one of these. 

  • 0 8 months ago in reply to socorsu

    I have the Garmin Tactix 7 Balistic and after applying the update, It is in a boot loop and cannot get it to shutdown in time before the boot loop kicks in