Storage media · original card and verified image
Scan a verified card image rather than the original
Should I recover from the original card or its clone?
Short answer
From the verified clone, not the original. Once the image matches the card's exact byte size and hash, it allows repeatable reads without extra wear on a possibly weak card. Label the original, store it unused as your fallback, and run every scan and export attempt against the image instead.
The situation
Both a source card and a sector image are available.
With both sources in hand the choice is settled: scan the verified clone and keep the card as your fallback. The clone delivers repeatable reads at full speed, while the original stays untouched in case a later attempt has to start from the card once more.
01 / Diagnose
Work out what actually disappeared
A clone is equivalent to the card only when it was taken from the whole device and nothing was skipped. Short reads during capture, a copy of one partition instead of the disk, or a write that ended early leave an image that looks usable and lacks exactly the region that matters. That is why comparing byte size and checksum comes before any scan.
A verified image provides repeatable reads and preserves the original from additional handling.
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Compare the exact byte size of the image with the capacity the card reports, and confirm the checksum recorded at capture time.
- 2
Mount neither source writable: keep the image read-only and put the card into a labelled envelope, out of the working set.
- 3
Run every scan and every export attempt against the image, repeating passes on it as often as the case requires.
- 4
Store recovered files on a third disk, so that neither the image nor the card serves as a destination.
Do not scan the original because it feels more direct, and do not delete the image once the first export looks complete. If size or checksum disagree, repeat the capture instead of working from an image whose contents nobody can vouch for.
03 / Choose the method
Match the tool to the source
For stable, readable exFAT, NTFS and FAT16/FAT32 or uncompressed IMG, DD, RAW and BIN images.
Unconfirmed exports are marked .UNVERIFIED.
A clone can only be as complete as the reads that produced it, and sectors the card refused stay missing in every copy. File Recovery Hero scans uncompressed IMG, DD, RAW and BIN images as well as stable exFAT, NTFS and FAT volumes.
04 / Verify
Check the recovered content, not just its name
Confidence comes from agreement: the same scan run twice against the image should list identical files at identical sizes, and spot checks of exported photos, clips and takes should open cleanly. Only then does the card become surplus rather than the last line of defence.
Keep the source until two verified copies exist. One working preview is not enough.
Sources and technical references
FAQ
Questions about this recovery case
Can original card and verified image be recovered in this situation?+
With both sources in hand the choice is settled: scan the verified clone and keep the card as your fallback. The clone delivers repeatable reads at full speed, while the original stays untouched in case a later attempt has to start from the card once more. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not scan the original because it feels more direct, and do not delete the image once the first export looks complete.
Does scanning write to my memory card?+
Your memory card is only read. Nothing is saved to it.
How do I know whether the result is complete?+
Confidence comes from agreement: the same scan run twice against the image should list identical files at identical sizes, and spot checks of exported photos, clips and takes should open cleanly.