Data Recovery Case File · Solid State & Flash · Lucky Twice

The Format That Failed Was a Reprieve

His enquiry describes an attempt that would have destroyed what he wanted and did not work. A card holding a substantial photograph collection: "my card suddenly stopped working and my phone and PC say it needs to be formatted. I tried to format it but I am even unable to do this." He was following the only instruction he had been given, which is entirely reasonable. The card refusing to be formatted is fortunate twice over — nothing was written over his photographs, and the refusal itself is a genuinely useful diagnostic finding that narrows where the fault sits.

The decode: why the refusal is informative, and why it protected him

What the format prompt actually meant: not that the card needed repairing. It means the host read the filing structures and could not interpret them, so it offered the only remedy it has — writing fresh empty structures so the card becomes usable. Usable, in that sentence, means empty. The wording gives no hint of that, which is why so many people accept it.

Why it not working is the good news: obviously, because nothing was written over his photographs. But there is a second and less obvious benefit, which is what the failure tells us.

The diagnostic value of a failed format: formatting is a write operation. To complete one, the card must accept power, complete its introduction, and then successfully write new structures to its memory. A card that cannot be formatted has failed somewhere in that chain — which means the problem is at device level rather than in the filing structures. If the fault were merely a damaged filesystem, the format would have succeeded, because writing fresh structures over damaged ones is exactly what it does. So the refusal rules out the very explanation the prompt was implying, and points at the controller or the memory instead.

Why that is not bad news for the photographs: in the great majority of these, what has failed is the controller — the chip conducting the introduction and managing the memory — rather than the memory holding the images. Manufacturers place test points on the card giving direct access to the raw memory, bypassing the controller entirely, and the data is read through those and reconstructed in software.

Why the content is certainly unaltered: nothing has been able to write to this card since it failed. Every attempt — the format, any repair prompt, any tool — has been unable to complete a write. From a recovery standpoint that is close to ideal: the medium is in exactly the state it was when it stopped.

The one instruction: stop. No further format attempts, no repair utilities, and no further insertion. Each attempt powers a failing controller for no benefit, and the position is already established across two devices.

On the bench

No further format or write attempts were made, since every one had already failed and each powers a failing controller for no benefit — while the inability to write meant the medium was preserved in exactly the state it failed in. Enumeration was attempted write-blocked behind the DeepSpar USB Stabilizer 10Gb under strict timeouts, establishing where the introduction stopped. Where the controller could not be brought up, the memory was read at chip level through the card's internal test points and reconstructed in software until the filing structures stood up. Photographs were validated by rendering.

The outcome

The failure point established under timeout control, the memory read past the controller and the photographs validated and delivered. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode, for anyone whose card refused to be formatted: that failure was lucky twice. Nothing was written over your photographs — and the refusal itself is informative, because formatting is a write operation, so a card that cannot complete one has a device-level fault rather than damaged filing structures. If the problem were only the filesystem, the format would have worked. Stop trying.

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.