Forum menu
My battery died this morning on my commute and now the upload won't work properly. Strava says the file is malformed and can't be processed. A bit of googling tells me it might be the endsum missing what ever that is .
Does anyone know how to convert the file or repair it as I'm keen to see if my new tyres have made me any quicker or slower.
https://drive.google.com/file/d/1v40M5_VRQ7LQADq6fNCCt8r8rMPuoMnN/view?usp=drivesdk
This is the file if anyone can help me please
Try the corrupt time fixer on fitfiletools.com
Has worked for me in the past when either Strava or Garmin connect has refused the file
Strava themselves link to this site which I've used with success before; https://www.fitfiletools.com/#/ctf#view
Thats worked but seems to have me down as 7 miles and I did around 15 before the battery died
I had this with a file a while ago (not Wahoo but the same problem) fitfiletools wasn't able to sort it.
I went to this site http://garmin.kiesewetter.nl/ . and the first option didn't fix it. What I then did was to use the "Convert to CSV" utility further down the page then upload that CSV file back to the site to generate a new .FIT file.
FYI, endsum is a mathematical check. Simplistically the value of each byte in the file is added together and the result is tacked on to the end of the file using say four bytes. A FIT file reader will look at the last four bytes then do the adding of the rest of the file and then compares the two values. If they are different then the file has been corrupted in some way. It's not done in exactly that way but the concept is similar.
If this is a commute and it’s the same route you do daily, download the GPX from Strava of a different day, edit all the time and date stamps to the day it failed and reupload it. I’ve done that before when a commute failed.