[Hint] How did I fix my ODT file

[robleyd]

If you upload the file, someone will see if it can be recovered.

[Forum] How to attach a document here Note maximum file size is 128K. If your file is larger, use a file sharing site such as Mediafire and post the link here.

[John_Ha]

Welcome to the forum.

See [Tutorial] Format error discovered in sub-document for instructions on repairing the file.

If you want someone to repair the file for you you will need to upload the original file before you sent it to the file converter to a fileshare site somewhere. The file conversion almost certainly truncated the file at the location of the first error and all content after the error will have been lost in the converted file.

Or see [Tutorial] How to find and un-delete AOO temporary files for

a) detailed instructions on how to recover your file as it was when you last opened or saved it, or as it was when it was last saved with AutoRecovery;

b) how to find previous versions of the file in the folder it is located in, but which have since been deleted;

c) how to un-delete the temporary files AOO wrote while you were editing the file, and then deleted. This will recover your file as it was when you last opened or you last saved it and is probably your best hope.

[larryhpaterson]

{solved}

Hello smart people!
I tried to fix the file myself but I have no idea what I'm doing. If anyone with a better brain suited for this kind of problem could help I'd be grateful.

And to clarify...how do I stop this from happening again?

[RoryOF]

Try the attached.

Do not attach comments to extents of text.

[John_Ha]

how do I stop this from happening again?

These errors are thought to happen when a file is exchanged between AOO/LO and MS Word and changes are recorded. We believe, but are not certain, that MS Word corrupts the file. As the corruption seems to be associated with comments applied to a range of text do not use that feature.

See [Tutorial] Format error discovered in sub-document where your error was "office:name redefined".

[LordEos]

Hi everyone!
Long story short HDD packed in without any warning and took my .odt file with it, no backups unfortunately (I'm an idiot I know).
Ran Recuva and retrieved a .tmp file that matches my lost file in size but no clue what to do now - turned it to .zip no luck there, can't unzip it...turned it to .odt but it just shows wierd symbols or #####.
Can anyone here give it a spin and see if anything can be done? It's probably a lost cause but I'd be grateful either way.
Thanks.
https://drive.google.com/open?id=1FdVjK30yQtL00QLhE5_PuoF66VrRKmIo
https://drive.google.com/open?id=1D6XUUVEmS_H1GBiLJrlrr-dSRsZYxh1d

[RoryOF]

If it won't unzip it may possibly be repaired by powerful tools, but may have only partial or more likely, no content/ If it opens and shows ### there is nothing to be done - experience tells us that there will be no usable content.

[RoryOF]

I got nothing usable from either file.

[LordEos]

Figured that might be the case. I appreciate the effort though, thank you