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

Corrupted FIT File

I have tried the auto correct with http://garmin.kiesewetter.nl/

But no joy

Can one of the Fit file repair gurus please correct this file for me please?

https://www.dropbox.com/s/z32damunth8logp/2020-12-02-12-05-51.fit?dl=0

Thanks in advance

And if anyone can point me to a fit file repair tool that works on OSX I am happy to buy one. They don't corrupt very often but when they do it is always a bigger or better ride that one wants the data from.

Happy trails

Andrew

Top Replies

All Replies

  • As is typical with these issues, there is no stop event, just a start and no stop or summary data. Fit File Repair Tool is good at fixing this. Sorry, not possible on a Mac, unless you want to try it in Boot Camp or Parallels. Looking at the file there are a lot of fluctuations in power value including a "very high power value (811)" warning.

    Have you tried FIT File Tools? This is very good at fixing the issue with summary data missing from the FIT file. Just use the section remover with no adjustments.  I tried it with yours and came up with a fix that resulted in pretty much the same activity and tested with a successful import into Garmin Connect.

    At any rate, here is your fixed file, courtesy of  Fit File Repair tool - 2020-12-02-12-05-51-fixed.zip

  • Hey thanks very much. I did run it through the Fit File Tool "Corrupt Time Fixer" but it still wasn't accepted by Garmin Connect. It did become available for Strava which was nice to have. 

    Thanks very much for your efforts. I paid for Fit File Repair and then realised that it did not have a Mac version so Mathias very kindly refunded me (and PayPal crewed me on the exchange rate difference of course). I am very curious to be able to correct any errors myself.

    This repair is now accepted by Garmin Connect so thank you. You would think that Garmin might have their own repair app? It makes sense because my Edge 520 seemed to accept the 'save ride' at the end of my ride yesterday but then froze so I was fairly certain that the file was going to have an 'end' issue.

    A 811 Watt spike is not unusual for me for a pedal stomp on a technical climb but I would be concerned if it was more than 10 seconds!! 

    Thanks so much once again

    Happy trails

    Andrew

  • I did run it through the Fit File Tool "Corrupt Time Fixer"

    Use the section remover with no adjustments. Seems to work in a lot of cases. On yours it worked, but would need to just change the activity type to cycling after uploading to Garmin Connect.