Emergency · failing SD card
Recover a failing SD card: classify the failure first
Can I recover data from a defective SD card?
Short answer
Often, if the fault is logical: exFAT damage on a card that still reads stably can be imaged once and then scanned. Physical flash or controller failure needs a different route. Stop all DIY attempts if the reported capacity is wrong, the card heats up or reads get worse with each try, and take it to a laboratory.
The situation
The card disconnects, slows down, or produces intermittent read errors.
Classification comes before recovery here, because logical damage and physical failure pull in opposite directions. A logically damaged card tolerates one careful pass and gives its data up; a physically failing one loses a little more with every attempt you make.
01 / Diagnose
Work out what actually disappeared
Logical damage means the exFAT structures are inconsistent while the flash still answers every request: the card mounts, reports its true capacity and reads at a steady speed. Physical failure shows itself differently, through disconnects under load, a capacity that does not match the label, long pauses, heat, or read speeds that drop from one try to the next.
Logical exFAT damage and physical flash or controller failure require different workflows.
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Plug the card in once and watch the system report: capacity, transfer speed, and whether the device stays present for a full minute.
- 2
If everything looks stable, make one uncompressed sector image straight away instead of browsing the card by hand.
- 3
Disconnect the card and do all further work on the image, scanning it read-only for the formats you are missing.
- 4
If the card heats up, drops out or reports a wrong capacity, stop at once and contact a flash recovery laboratory.
Do not try one tool after another on the card itself, and do not run write tests, formats or firmware utilities in the hope of reviving it. Every further access costs reads that a failing card has in limited supply, and some of those tools write by design.
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.
Only the logical half of this belongs to software. File Recovery Hero reads stable exFAT, NTFS and FAT16/FAT32 media and uncompressed images, read-only; a failing controller, worn cells or a card that never enumerates correctly need laboratory equipment instead.
04 / Verify
Check the recovered content, not just its name
A successful image reads through to the declared capacity without skipped ranges; anything else is a partial image and should be labelled as one. Then judge the exported files themselves, opening a sample from across the whole shoot rather than only the first few items in the list.
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 failing SD card be recovered in this situation?+
Classification comes before recovery here, because logical damage and physical failure pull in opposite directions. A logically damaged card tolerates one careful pass and gives its data up; a physically failing one loses a little more with every attempt you make. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not try one tool after another on the card itself, and do not run write tests, formats or firmware utilities in the hope of reviving it.
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?+
A successful image reads through to the declared capacity without skipped ranges; anything else is a partial image and should be labelled as one.