Jump to content
|Topic||Stats||Last action by|
|Samsung 840 EVO SSDs suffer from performance degradation||
|SSD info shows "frozen" state. after secure erasing also shows "frozen" - BIOS probl||
|Trying to download Broadcaster for Touchstar||
|Need a bluetooth trackball mouse!||
|Apple release removal tool for unwanted U2 album||
Posted 14 October 2012 - 00:10
Posted 14 October 2012 - 10:25
exiftool -b file.cr2 > file.jpg
Posted 14 October 2012 - 10:47
Posted 14 October 2012 - 13:33
Posted 11 December 2013 - 04:44
Get ExifTool and try the following.
Drag-and-drop one of your corrupted files on the exiftool executable and see if returns any EXIF data back. If it does and there are no warnings then the file header is in tact. If so then when you are trying to open that CR2 file with some other software that reads RAW files (ie Photoshop), the actual raw data is corrupt. You can't fix or recover that, so just forget about the raw data. If there's a line that says Preview or Jpeg From Raw, then you should be able to extract a fullsize JPEG. Better than nothing I guess.
If exiftool returns some EXIF data and a warning, then the header is partially in tact. If there's no mention of JPEG or Preview data, then you obviously won't be able to extract any previews. Recovering a header is possible, but only the bit that describes the file type. It is always at the beginning of the file. But having that doesn't mean you will be able to recover any data. File header contains pointers as to where to look for a specific file part. If that's missing, the data is useless, even if it's still good.
If the tool returns an error saying it can't read the file, then the header is broken right from the first or two bits of the file. You can fix that by matching it with a healthy file in a HEX editor; can be tricky. This still doesn't mean you will get any results. If the rest of the header or file is broken, you will not get any results.
Command line for extracting JPEG preview:exiftool -b file.cr2 > file.jpg
Hi there, are there any services to do this? I used the first part of your guide and recovered ten shots, but i have 13 more that are 25+Mb but can't be read by an exif reader. Could fixing the HEX file header fix these files or is it possible to at least try? happy to pay of course. firstname.lastname@example.org I had a stack of family shots but just a few (these 13) corrupted when being copied from the card.
Posted 11 December 2013 - 17:49
Posted 06 June 2014 - 08:12
It's possible, can't be guaranteed though obviously.
Let's start off simple though, have you tried re-copying the files from the card?
Otherwise, upload one or two of them so we can get an idea of the state they are in.
Also, what is the state of the card they were on, did you delete the files? Have you re-used the card?
When you said "it's possible" I was very happy, hoping you could give me a little help.
My CR2 file is corrupted, but I can gat a B&W JPEG from it (because this is how I shot the pictures, in B&W mode). I would like to repair the file for getting the color JPEG.
I opened the file in HEX editor, and the header is fine. The problem is with the raw body, the info between the last FFD8 and the very end (FFD9).
I don't know if there is a way to follow the sequences and figure it out what is missing or there is something mixed up.
I have a corrupted CR2 file at this link: http://we.tl/oVMfpYn3wm
Thank you in advance!