Data Recovery Case File · Cameras, Drones & Cards · Where Software Stops
Recovery software failed on an unreadable card — as it had to: why software can't recover what it can't see, and how the chip-level pipeline on the PC-3000 Flash reads the memory the card can no longer present
His enquiry did the elimination work up front. A SanDisk Extreme 32GB microSD: "corrupt… unreadable from any device. Have tried recovery software, which has failed." That last line deserves its own decode, because the software's failure was inevitable — and understanding why is the key to understanding what this recovery actually requires. Recovery software, however good, operates through the computer's normal access to a device: it can only search, carve and reconstruct data on a card the system can read in the first place. A card that is "unreadable from any device" offers software nothing to work on — the failure isn't the software's quality, it's that the job sits below software's reach entirely. This page covers where that boundary lies, and how the recovery proceeded on the other side of it: at chip level, reading the card's memory directly.
| Media | SanDisk Extreme 32GB microSD — corrupt, unreadable from any device; consumer recovery software already attempted without success |
| Reported situation | Card unreadable across all devices tried · recovery software run and failed · owner seeking professional recovery |
| Fault class | Card-level failure (controller or deep corruption) below software's reach — requiring hardware/chip-level access to the NAND |
| Equipment used | PC-3000 Flash chip-level access · Rusolut VNR analysis (including its dedicated SanDisk monolith adapters) · XOR/ECC/FTL reconstruction · verified extraction |
The decode: the boundary software can't cross
Why the software had to fail: recovery applications work through the operating system's access to a device — they scan a readable card for lost files, deleted entries, or recoverable structures. That model has a hard prerequisite: the card must present itself to the system as something readable. "Unreadable from any device" means that prerequisite is gone — the card isn't offering a surface for software to scan. Running recovery software against it is like asking a librarian to search a building that won't open its doors: the failure says nothing about the librarian and everything about the doors. His software didn't fail at recovery; it never got the chance to start.
What "unreadable from any device" tells us: a card that no reader, phone or computer can read has failed at the card level — most often its controller (the chip that manages the card and presents it to the world) has died or locked up, or corruption runs deep enough that the controller can't mount anything. Either way, the memory itself — the NAND holding his data — is typically intact behind the failure. The controller is the spokesman; the NAND is the archive. When the spokesman falls silent, the archive doesn't vanish — it just needs to be read directly, without the spokesman's help.
Where the chip-level work begins: that direct read is precisely what professional flash recovery does and software cannot: accessing the NAND memory beneath the failed controller, extracting its raw contents, and reconstructing the data in software built for the purpose — reversing the controller's scrambling, correcting errors, and rebuilding the layout until files emerge. It's a different category of work operating a level below where any application can reach — which is why "software failed" isn't the end of the road; it's the signpost to the right road.
On the bench
The card went straight to chip level. Modern microSDs are monolithic — controller and NAND sealed in one package — so the card's technological access points were exposed and read on the PC-3000 Flash, with the Rusolut VNR toolset alongside; its adapter library includes dedicated support for SanDisk's common monolith layouts, which sped the pinout work considerably. The raw NAND dump then ran the standard reconstruction: XOR descrambling against the controller family's known keys, ECC correction of bit errors, and rebuilding of the flash translation layer until physical pages resolved into the card's filesystem. The photos and files his software could never see were extracted and verified — recovered from exactly the layer the software couldn't reach.
The outcome
The card's contents recovered from the NAND and delivered verified. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The boundary made plain for every reader who's tried software first: recovery applications need a readable card to work on, so "unreadable from any device" is the signal that the job sits below software entirely — at chip level, where the memory is read directly and the data usually survives whatever silenced the card.
Recovery software failed on an unreadable card
Don't take the software's failure as a verdict on your data — it's a boundary marker. Recovery applications can only scan cards the system can read; a card that's unreadable from every device gives software nothing to work on, so the failure was inevitable and tells you nothing about whether the data survives (it usually does, intact in the NAND behind a failed controller). Stop running more applications against it — each is doing the same doomed thing — and stop reinserting it everywhere. The job is chip-level: the memory read directly beneath the failure, which is professional-lab work, and it's exactly where recoveries that software "failed" routinely succeed.
The data's below software's reach, not gone — call Edinburgh Data Recovery on 0131 202 0491; read at chip level on the PC-3000 Flash, one written figure.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.