Corrupt FIT File Repair Requests

hi Daan,

Give this file a try.

cheers
Mike

hi Julian,

Give this file a try.

cheers
Mike

hi Will,

All repairs I do are done with the Fit File Repair Tool. In a case like yours, I would replot the course at https://www.gpsies.com/ and then export it as a .gpx file. I can then import that .gpx file into the .fit file via FFRT. The elevation may not be prefect but it will be a lot better than what it was.

Give this file a try which is the combination of the .gpx file and .fit file that was in your post.

cheers
Mike

Thank you very much!
I have tried to import your corrected fit file, the altitude is indeed much more accurate !
I would like to know, did you just export my GPX file to FIT after adding device information via FFRT?
Does this mean that the GPX file I fixed is usable?

In the future, if I encounter similar problems, I only need to use FFRT, adding device information to my corrected GPX file and exporting it to a FIT file, Strava should be able to identify the correct altitude information.Is that correct?If this works, it seems that I really need to purchase the FFRT license.

Sorry to ask so many questions every time. Because I want to be a self-sufficient person, I don't want to bother others every time.

Mike - thank you so much. This was one of the biggest rides I've ever done and I buried myself, so was gutted when I couldn't see how I went. Huge kudos to you and the other members who take the time to do all of this file-repair work for others on here, for nothing. It is really appreciated, from this mug punter at least.

Cheers
Julian

hi Daan,

Give this file a try.

cheers
Mike

Worked a charm - thanks a lot!

Hello guys,

Sorry to be a hassle. I did a ride today. It was 50km and 2 hours and recorded on my forerunner 235. Watch seemed to track everything nicely along the way and I stopped the activity and saved it as per usual. It did not sync with my phone app. I have been having this sort of issue a lot lately so I did what i have done in the past and I manually retrieved the .fit file from the device then tried to upload it. The file would not upload onto garmin connect so I uploaded the file to the website fitfiletools.com. This has always fixed my previous files, at least enough to upload to Strava however Garmin Connect still usually cannot accept the file.

After doing this the file was able to be accepted to Strava but seemingly only the first 400m and the whole rest of the activity has vanished. The watch was definitely recording the whole time as I checked in a couple of times to see how long I had been going for and my watch was doing my 5km auto lap right on queue throughout the whole ride. The post activity summary was correct as well however now when I look at my activity history on the watch it is showing as a 400m run, the same way Strava took it once I got it 'fixed'.

This is rather unusual as the watch normally has all the time, date and distance info correc in the activity history.

I have looked for other options to try to fix this file. I first tried the http://garmin.kiesewetter.nl site and this threw up the error "Upload status: The file could not be uploaded. The following error occured: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints."

After this I was going to try the tool from http://fitfilerepairtool.info however I don't have a windows machine to run it on.

Would anyone here have any other solutions I could try or be willing to have a look at the file and try a fix for me? Any and all help will be greatly appreciated. Thanks


[Edit]This second file may or may not be something to do with it...[Edit]

hi Will,

The device info was already contained in the .fit file that you provided, but yes if necessary, device info can be added via FFRT.
And yes, the .gpx file that you provided was indeed usable and all I needed to was to tell FFRT, through its 'Advanced Repair Features', was to 'Add position data from GPX or TCX file'.

I can't recommend FFRT highly enough - it really is a fantastically capable Tool.

cheers
Mike

hi Ruzy3,

Your file only contains 440m worth of data - the rest of the data just isn't there. FFRT reported that the recording ended abruptly. Did you save the file as you normally would?

The other thing that may have possibly caused the issue is a lack of storage space on your device. How many completed and upload activities do you have on your device? It is any more than a month's worth then it could be time to archive them off to a folder on your computer. You can't record a 50kb file if there is only 20kb of free storage space.

Other than that, it could just be a glitch with the mini computers that we wear on our wrists or mount to our bikes.

cheers
Mike

Hi :)

I made a separate thread yesterday and only noticed now that there is this collective thread.

Can someone help me with this file, please?
https://www.dropbox.com/s/in4bxl76zamd4nr/888H3257.FIT?dl=0

Any help is highly appreciated! :)

Thanks a lot
and kind regards,
Rilko