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 in reply to seilogramp

    no, the way out was a couple of miles longer before I reversed on the same route. I managed to recover those 35mins myself but I saw a lof of odd HR data such as 60bpm while climbing at speed etc. This was 30mins in to the ride. NOt sure if the one you partially recovered is also showing that. Would be good to have anyway. Thanks a lot.

  • 0 over 4 years ago in reply to fabjodo
    fabjodo said:
    NOt sure if the one you partially recovered is also showing tha

    Looks normal except for the dropout at 5:24

  • 0 over 4 years ago in reply to seilogramp

    Thanks a lot seilogramp....the HR looks almost perfect on this one although the way out was 50mins and not 35, so I miss my last interval. Anyway, better than nothing for doing some analysis. Could you please post it?

  • 0 over 4 years ago in reply to fabjodo

    Update. I have taken the time to try with the FIt to CSV python script converter

     and get similar output

    C:\Pers\garmin\SDK\java>py FIT_to_CSV_forWin.py.txt
    Traceback (most recent call last):
      File "FIT_to_CSV_forWin.py.txt", line 71, in <module>
        main()
      File "FIT_to_CSV_forWin.py.txt", line 23, in main
        fitfile = fitparse.FitFile(file,data_processor=fitparse.StandardUnitsDataProcessor())
      File "C:\Program Files (x86)\Python38-32\lib\site-packages\fitparse\base.py", line 36, in __init__
        self._parse_file_header()
      File "C:\Program Files (x86)\Python38-32\lib\site-packages\fitparse\base.py", line 105, in _parse_file_header
        raise FitHeaderError("Invalid .FIT File Header")
    fitparse.utils.FitHeaderError: Invalid .FIT File Header

  • 0 over 4 years ago in reply to fabjodo
    fabjodo said:
    Could you please post it?

    I think he already did - see 's first post

  • 0 over 4 years ago in reply to fabjodo
    fabjodo said:
    Update. I have taken the time to try with the FIt to CSV python script converter

    That was unnesessary - as I already wrote the file is empty, filled with zero bytes, except of very few nonsensic bytes at the beginnning. It is enough to look at the file in Notebook to understand it contains no information that could be salvaged.