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 ?

0 Former Member over 9 years ago

Today I went back to the original maps and used Strava Segments and again didn't suffer any crashes. So it looks like with 5.30 you can have Strava Segments or 3rd party maps but not both.

0 hoegni65 over 9 years ago

my ride today was fine....the only difference was that I had Livetrack disabled

0 the_mushter over 9 years ago

I have stayed on software version 3.00.

I find this to be fine. Haven't seen anything in the later updates that are of use to me (I don't have vector pedals, varia etc etc)

Garmin software releases do seem to be utterly awful

0 svkaster over 9 years ago

I have also done a ride today with f 5.3 i used live track and it stoped in the middle and rebooted the device :(
I could not continue it saved my ride and i had to start a second run :(

I use new opemaps.

0 Former Member over 9 years ago

Today I went back to the original maps and used Strava Segments and again didn't suffer any crashes. So it looks like with 5.30 you can have Strava Segments or 3rd party maps but not both.

I dunno. I have 3rd party maps and was doing repeated strava segs yesterday, worked fine for me.

0 Former Member over 9 years ago

I dunno. I have 3rd party maps and was doing repeated strava segs yesterday, worked fine for me.

What are your 3rd party maps. I was using openstreet maps

0 Former Member over 9 years ago

Same here. Maybe it depends on what area you load?

0 bloom34 over 9 years ago

Rode today with open street maps and strava segments worked fine for me.

0 rmi63 over 9 years ago

Also, shut off like 5 times yesterday. I had strava live segments loaded but it was disabled and using original maps.

0 VORZAP over 9 years ago

I've had issues 5.3 update issues with my 520 which seem far more serious than what anybody else has noted so far.

All was well (I was on 5.2) and whilst on a cycling trip to Mallorca last week I connected via bluetooth to Garmin Connect to transfer a course. The device auto installed the 5.3 firmware, went through the installation process and completed 100%, but when it turned back on it said it was 'unable to apply update'.

I then went out on a ride anyway hoping it would be ok, but straight away I could see there was no distance being recorded on the ride. I tried to stop and discard the ride wt which point the summary (before saving) told me that the distance was something like 26468 miles. I tried to discard the ride, but it would then just hang forever on discarding (not frozen, the circle thing keeps going around as if it was trying to discard).

Only way out of that was to shutdown the device, but when it turns back on the ride is still there in progress. The exact same hanging happens when trying to save the ride too.

I've done a couple of hard resets which don't resolve the issue - it just tells me that the update was unable to apply and then the exact same issues continue to happen.

I'm going to try to roll back to 5.2 now and see if that fixes things.

Has anybody else had these same issues??

Any ideas on how we can get 5.3 installed properly? Maybe roll back further than 5.2 and try installing 5.3?

I have had the mile inflation happen to me for two weekends now. Last weekend 4300 miles, this past weekend 3600 miles. Called Garmin support and they said either my edge 520 or speed sensor is defective and I went ahead and started an advanced exchange. This weekend was really disappointing because after it inflated, it crashed and lost my miles on mile 80 of a century ride. Crazy thing was that after the hang and reset it kept the course I was on and had the next turn ready. The con was that it was super laggy after that crash and took a minute or so to update all my data fields (i.e. speed/power/cadence shown 1 minute after an obvious changes).