Corrupted CR2 files repairable?

Started by jkientop, May 24, 2015, 12:27:27 PM

Previous topic - Next topic

norbi

Thanks, Phil!

One thing I overlooked last time is that aside from those 3 jpgs, there is also a block of 16-bit uncompressed image data (the dimensions are 362x234). This block is pointed to by the third top-level IFD. So I fixed-up a couple offsets, made the 3rd IFD the only IFD (pointed to by offset at position 4). Then I just changed extension to tiff and most programs were able to open it. The resulting image itself is very dark (almost black), but so is the same image extracted from another valid CR2, so it seems the purpose of this block is something other than preview. I used auto-adjustment in FastStone to make it brighter. Colors may be wrong (because of the damage), but I'm not sure. The result is attached.

Phil Harvey

...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

johnnyyn

Hi phil, i also have a corrupted file problem,

ive taken 900 photos but half of them are corrupted with no preview and an error in exiftool.
I believe it happened when i was taking raw images too fast and i couldnt write properly.

https://www.dropbox.com/s/tiv5i9l486w9dkn/IMG_0603.CR2?dl=0

This is one of the images if you could please take a look at them thank you

hopefully the JPEG can be extracted but i dont know how

norbi

johnnyyn,
I downloaded your image and unfortunately, it's full of 0xFF bytes, so there is nothing to save whatsoever  :-\, not a single bit of information. Maybe other damaged images are different, but only you can tell.

Phil Harvey

I confirm Norbi's conclusions.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).