Hi can anyone help me fix this corrupted file the standard garmin fix tools don't seem to work
https://www.dropbox.com/s/fw23bauqvo92t9f/A7FA0353.FIT?dl=0
Many thanks
Jean Shotter
Hi can anyone help me fix this corrupted file the standard garmin fix tools don't seem to work
https://www.dropbox.com/s/fw23bauqvo92t9f/A7FA0353.FIT?dl=0
Many thanks
Jean Shotter
Former Member
hi, sorry to hear about your mishap again
some advice
contact Garmin Support by phone and tell them about your mishap
avoid pausing during activities
clean activity folder on a regular base
Fit File Repair Tool can repair your fit file, time for an investment when you keep using the FR35
want a fr35 fit file repair, get a Garmin Support Case Number
check this file jeanshotter-n°4-fr35-kaput-part18-A7FA0353.zip
happy & safe sporting
Many thanks both for the advice and the fixed file, which works a treat. I've checked the repair software but unfortunately it doesn't work on a mac :(
I will contact garmin, I have already had them replace one watch for failing in this way on a regular basis, this problem was on my partners watch and has only just started to have a problem.
thanks again
Jean
Jean - I found your message while searching for examples of corrupted FIT files. I downloaded yours and was able to repair it simply by uploading it here: https://gotoes.org/strava/Combine_GPX_TCX_FIT_Files.php I know this question is 8 moths old, but figured I would share this info for other people in need.
Did you look at the File After You Fixed It using gotoes.org.
I suggest you do that.
Here is the uploaded file (original). It has one corrupted point at the end. This view is when you click "Edit Points" on the 2nd page. From there, you just click the trash can and delete the bad point. You can then export a clean file. See Images Before and After.
I'm trying to get corrupted FIT files for testing to see if there are any that the tool cannot handle. The intention is to find a corrupted file, see what is wrong with it, and then figure out a way to extract as much data as possible.
But The Run Looks Like this 13.1 km (So a very Partial Fix)
Your Parser Stopped After the Real Error Which is
@ 48420 +- A few Bytes (Decimal Offset)
There is a Lot of Data Beyond that Point
The Problem with most of the Parsers is that they cannot get past the Error and Continue to read the data in the File.
They Just Stop at the real Error.
Attached is a Fixed File.
Human Intelligence Beats Artificial Intelligence (LOL)