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 bike ride 100km ride. Already tried to recover w/ online tools and it only recovered the first 40k.m.

Hi, good day!

I rode a 100km ride today that was corrupted and I tried repairing the file via https://www.fitfiletools.com/#/top  (it only repairs to the first 40km of the ride)

Would love if somebody has an idea why this particular ride is corrupted and if it can be fixed? I am using a mac and can't use https://www.fitfilerepairtool.info/ to manually repair the file

I attached below the .fit file.

Thank you.

[solved]

  • Former Member
    0 Former Member over 3 years ago

    solved

  • Hi there, thanks for the reply!

    We stopped at km43, then resumed the ride to finish a 100km ride. In cycling activities in my garmin, it lists the activity as 100k.m. but I can't expand the ride to view the ride details (because it's corrupted).

    Hmm, interesting find about the forerunner745 issues. I guess I have the asian version. I'll take a look at it.

    Again, thanks for the help. I've already contacted garmin support.

  • Hi, why do you believe the file was corrupted? Files can be missing data due to sensor issues, etc, but it doesn't mean they are corrupted. Did the activity sync into Garmin Connect ok? Or did it fail or give an error?

    That there is no data after your stop at 43 km seems significant. I'm not familiar with using watches to record rides, but I wonder if you stop long enough, is it possible for the watch to lose pairing with the sensors (sleep, auto power off, etc), and when you resumed they were no longer connected. Since your total distance is correct, but your other data is missing, this sounds like a likely possibility.

    Is the fit file you posted the original file? Or the "repaired" version. What repair option did you do?

  • other

    The uploaded file is the original version I copied straight from my Garmin watch. It's possible that what you said might be the case. I've noticed the same pattern on my other rides (pausing too long "corrupts" the file). Still, for a watch that is designed to track runs/cycling, this shouldn't happen. My phone is much reliable tracking Strava than my Garmin so far Disappointed

    I both used the Corrupt Time Fixer & Section Remover and it showed the same 43km results.

  • Ok I pulled the file into Fit File Repair Tool (toss your Mac haha!) and indeed it reported some corruption. Some data rows during your half-hour stop for chicken around 8pm are garbled. All the data before and after that appear to be good, so you didn't lose anything. I nuked the garbled section and here is the repaired file.

    [solved]

    As for why it did that, I'm still kinda new to these files so I honestly don't know. About a minute before your stop the recorded battery level crashed to 0%, but I don't know if that is bad data, or a clue about the problem. After the bad section the batt level went back to normal.

  • How did you know we stopped for chicken? I'm starting to think you're a wizard, man.

    The culprit is definitely the pit stop, as I tend to notice that my files get corrupted more often if I stop for a longer period of time. I'll be definitely recording/saving rides separately from now on if I ever plan to stop for a ride. 

    Anyways, the file is indeed fixed and I can finally upload the ride to Strava. Big kudos to you, appreciate the help and many thanks! 

  • Haha well when I checked the map in Fit File Repair Tool to inspect the bad section at your stop I saw the restaurant and made a wild guess Smile

    It might be worth contacting Garmin support to ask why it does that in case it really has a problem, or checking some of the other ideas posted.

    Cheers!

  • Haha I figured after realizing that you have the data for the route I did. I am currently contacting support to see what's the issue.

    Again, thanks for saving the file. Much appreciated. Cheers!