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

Firmware Version 5.3 issue

I used Garmin Express to update from 5.2 to 5.3.

Garmin Express synced -found the update , went thru the install process and finally reported that the update was successfully installed. (However it did not install the update on the device the firmware is still at 5.2 after rebooting the device)

If I resync in Garmin Express it will go thru the whole process again, and finally say that the update was successfully installed- but guess what ...its not installed!

I have uninstalled Garmin Express from the PC and reinstalled it but got exactly the same issue.
I have updated firmware many times and never had this issue.
Any ideas ?
  • Former Member
    0 Former Member over 9 years ago
    Does Garmin even bother to test these updates before shoving them down our throats? This is shameful. I regret replacing my trusty 500.
  • Former Member
    0 Former Member over 9 years ago
    Just out of curiosity, do any of the guys having problems with their updated Edges randomly shutting down have Auto-Shutdown enabled? I've disabled this but haven't been out a ride yet to see if it makes any difference.
  • If anyone is experience the 520 crashing could you post the
    Garmin\Debugging\err_log.txt

    I would be interested in taking a look.
  • Former Member
    0 Former Member over 9 years ago


    Hopefully this is helpful to you
  • Can you recall what you were doing when it crashed? Following a course for example.
  • Former Member
    0 Former Member over 9 years ago
    Here is the text file and one of the .fit files that I had a issue with.

    I actually just ended up stopping this ride and saving it before turning the unit off and starting new ride to return.

    I was not following a course but one thing that did occur to me is that the two times the unit appeared to shut down were right where a bunch of strava segments start and end.

    In the .fit file you can see the Power Up event in the event log happens at 12:16:01 PM. I didn't notice until 12:19:00 , where I started it again. This incidentally is where distance values go haywire too.

    Everything goes crazy again at 1:08:57
  • Former Member
    0 Former Member over 9 years ago
    I wasn't on a course when these crashes occurred. I don't use courses at all. Now I think about it I was maybe just at the start of a segment when some of the crashes happened. One was just at the end of a segment though.
  • Thanks for the information. The good news is that you both hit the same error. I will add some additional segments to my unit and see if I can reproduce it.

    If you find that problem is repeatable drop me a private message.
  • Hi All,

    I had my 520 shutdown today as well. It happened right at the end of my ride so not too much of an issue - but would be annoying right in the middle of my ride.
  • Former Member
    0 Former Member over 9 years ago
    Shutdown once on todays ride. Again, it happened at roughly the same spot as Saturday's shutdown but going in the opposite direction. There are Strava segments in both directions in this area so I'm going to disable Strava Live for tomorrows ride and see what difference that makes.