Related
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

Upload status: The file could not be uploaded. The following error occured: Unexpected end of file while parsing Name has occurred. Line 151558, position 9.

fabjodo
over 4 years ago

8168.2021-01-05-16-14-42.zip

Hello guys,

could anyone please try to fix this fit file?

I get the error in the subject when I try to fix it with the Garmin Online fit repair tool .

This file was accidentally deleted from a Garmin Edge 820, then recovered with Recuva to my Hard drive however neither Garmin connect nor Strava will let me import it as it seems corrupt. 

The file had been saved after the ride and was showing in the Garmin history, so it had not been discarded before saving.

I have tried to fix it with Fit file Repair Tool but the Antivirus on my PC blocks the Ms Access macro and I cannot disable it.

I have tried with Fit SDK and I get an error both in DOS and in WIndows: FIT decode error: Endian 8 not supported. Error at byte: 5188

Looks like a tough one to fix! Would really appreciate any help from the experts as I am now desperate.

Thanks a lot in advance.

Fabio

Top Replies

All Replies

  • 0 over 4 years ago

    Try the Section Remover in FIT File Tools (without removing anything, just passing it through it).

  • 0 over 4 years ago in reply to trux

    Thanks but no luck. The resulting file is only 5kb and Garmin connect won't like it

  • 0 over 4 years ago

    Well, it looks like some sectors that the file originally occupied were already overwritten before you performed the recovery. I managed to hack the file with a hex editor, so that the SDK can convert it to a CSV file, but it contains only around 40 GPS trackpoints (40 seconds - it seems you used the Every Second Recording mode), so likely not what you are looking for. Then there are ~20 lines with the device info. On my mind, it comes from a monitoring file that overwrote the sector of the activitiy before you performed the recovery.

    With some more manual hacking, it could be perhaps possible to save more data, by removing the alien parts, and trying to stick the rest together, but that would represent a lot of work. It will be simpler to repeat the ride Slight smile

    Not sure whether the Fit File Repair Tool can do something with it, but I doubt it a bit.

    You can have a look at the CSV file here: test1.zip

  • 0 over 4 years ago in reply to trux

    Thanks for your time Trux. I think you are right because when I used recuva to recover the deleted file it shows State: poor Comment: The file was overwritten with D:Garmin\GPS\EPO.bin

    I managed to open the recovered file with FFRT and it actually shows much more data (36min out of 61mins total) but when I look closer lots of the data is corrupt. Only the first 18mins are good. The rest shows crazy values for watts, altitude, HR etc...

    It was a quite hard climbing training ride so not planning to re-do it very soon....anyway. I created a manual entry and next time will try to be more careful with the awful Garmin 820 display.

    Thanks again for trying!

  • 0 over 4 years ago in reply to fabjodo

    8473.2021-01-05-16-14-42.zip

    Recuva found this one which is in status Excellent and Not overwritten. However FFRT is struggling to open it. Could you please try to open it and save it for me?

  • +1 over 4 years ago in reply to fabjodo
    fabjodo said:
    I managed to open the recovered file with FFRT and it actually shows much more data (36min out of 61mins total)

    What should the ride have been? I used a licensed copy of Fit File Repair Tool. 

    The fixed file is 35 minutes - 2021-01-05-16-14-42-fixed.zip

    fabjodo said:
    Antivirus on my PC blocks the Ms Access macro and I cannot disable it.

    According to the developer, this is a false warning and caused by the fact that the tool is a MS
    Access application. I was able to "download anyways" the installation zip file to get it installed on a Windows 10 PC with Microsoft 365 (includes MS Access). If you do decide to install it, you might need to modify MS Access options. Trust Center > Trust Center Settings > Trusted Locations > Add the path to FitFileRepairTool

  • 0 over 4 years ago in reply to fabjodo
    fabjodo said:
    Recuva found this one which is in status Excellent and Not overwritten. However FFRT is struggling to open it. Could you please try to open it and save it for me?

    Unfortunatelly that's not a FIT file. Just a few bytes without interest (possibly from autorun.inf), and practically all the 250kB just filled with zeros

  • 0 over 4 years ago in reply to seilogramp

    Thanks seilogramp..the ride should have been about 61minutes. Please try with the latest zip file I have posted above as this one is marked with staus Excellent and no overwritten clusters when recovered with Recuva. The only issue with this seems that it has not been finalized as described in this post https://forums.garmin.com/developer/connect-iq/f/discussion/217798/remarks-about-saving-replaying-a-fit-with-sim

    and I do not know how to fix it. If I try to pen it with FFRT it hangs and returns no results.

    When I try to convert it to csv with Fit SDK returns and error described in the Garmin Forum URL I posted.

  • 0 over 4 years ago in reply to trux

    Disappointed   Very weird. Thanks

  • 0 over 4 years ago in reply to fabjodo
    fabjodo said:
    Please try with the latest zip file

    Like trux said, that is not a fit file, which is why FFRT is hanging.

    Was your ride an out-and-back, so you're just missing the return route?