Firmware Version 5.3 issue

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?

Here's the error log for my device, but I don't know if it'll be much use as I've hard reset it a couple of times trying to sort this out....

Error File

Here's my error file. Not sure how much info it will hold as I've done a couple of hard resets trying to fix this.

Thanks for any help!

yesterday i missed for about 15 seconds the heardrate and cadenz Sensor and exactly on the same place the LiveTrack missed the connection.

For those of you that are getting the crash have you replaced the map file that is shipped with unit with another file?

For those of you that are getting the crash have you replaced the map file that is shipped with unit with another file?

I have replaced the supplied map with an Opensource Map. Today I went out a ride but disabled Strava Live Segments and just to be sure deleted all my Strava Segments on my Edge. I had no crashes and even went past one of the points on the road where I have had several crashes. I'm now thinking about the places where the crashes occur and wonder if there may be a convergence of segments at these areas that could be confusing the Edge.

For those of you that are getting the crash have you replaced the map file that is shipped with unit with another file?

I had a map from OpenStreetMap.nl which was 22mb and of Mallorca only, but my issues don't sound the same as the others.

I did just replace the map with the original basemap at the same time as rolling back to 5.20 and it seems ok at the moment (haven't done a ride yet, but no hanging on saving or discarding).

Strange thing now - when I go to settings to check the software it says that 5.30 is running even though I've just done the 5.20 rollback. Is this normal? How can I find out which version is actually running??

For those of you that are getting the crash have you replaced the map file that is shipped with unit with another file?

I have the map it shipped with.

I have done 2 rides since then with no issues. Both of these routes were completely different than the one I had issues on though.

I am going to try and get back out there at some point this week and see if I have the problem again.

Crashed for the first time (version 5.30)

If anyone is experience the 520 crashing could you post the
Garmin\Debugging\err_log.txt

I would be interested in taking a look.

I was not following a course. Relevant portion of err_log.txt:

2067 (Edge 520) SW ver: 530
ParserVersion 3
UnitId: {3907874252}
Product: {Edge 520}
SoftwarePartNumber: {006-B2067-00}
Time: {2016-4-19 19:57:29}
PackageVersion: {}
SystemVersion: {5.30}
PackageName: {RELEASE}
Build_Tag: {RELEASE}
build_type: {RELEASE}
Backtrace: {}
Assert_Info: {}
RTL_Trap_Info: {}
Exception_Info: {}
Error_Cause: {8}