Data Recovery Case File · Cameras, Drones & Cards · Failing to Format Is Informative
When Even the Camera Cannot Format the Card
His enquiry contained a detail most people would report as an extra frustration, and it is actually the diagnosis. An SD card from a Canon camera: "suddenly stopped working and won't be picked up by the SD card reader on the PC, and the camera won't format it. It has over 1000 photos that I would like back." Two devices refusing it is a clean elimination. But the specific observation that the camera cannot format it is worth more than that, because formatting is a writing operation — and a device that cannot even write to a card is telling us something quite precise about where the fault sits. There is also an irony worth stating plainly: the camera's failure to format is very likely the reason his photographs still exist.
| Media | Canon camera SD card holding over 1,000 photographs — not detected by a computer's card reader; camera unable to complete a format operation |
| Reported situation | Sudden failure in normal use · card not recognised by a computer reader · camera unable to format the card · photographs required |
| Fault class | Controller failure with no reliable enumeration — card unable to accept writes or present to a host; NAND typically intact |
| Equipment used | No further host or camera attempts · monolith preparation and internal technological pads exposed · PC-3000 Flash Spider Board probing · Rusolut VNR pinout confirmation, XOR descrambling, ECC correction and translation rebuild · photographs validated by rendering |
The decode: why a failed format is informative, and why it saved him
What formatting actually requires: more than reading does. To format a card, a device must power it, complete the identification handshake, and then write new filing structures to it. Writing is more demanding than reading — it requires the card's controller to be functioning well enough to accept data, place it, and confirm it. So a device that cannot format a card is reporting a failure at a low level: not a filesystem it dislikes, but a card that is not responding well enough to be written to at all.
What that combination establishes: the computer's reader not seeing it and the camera not being able to format it point the same way — the card is not reliably answering. That places the fault at the controller, the chip that conducts the introduction and manages the memory, rather than at the filing structures or the photographs. Which is the more hopeful of the two possibilities, because the memory holding a thousand images sits behind that controller and is normally entirely unaffected by its failure.
The irony worth naming: a camera that could format the card would have done so, on his instruction, and written fresh empty structures over everything. Formatting is what people try when a card misbehaves, and it is the most common way photographs are lost after a fault rather than because of one. His camera's inability to complete that operation is, in a real sense, the thing that preserved his position. It is the only case in this archive where a failure to work is straightforwardly good news.
Why the outlook is good: the standard flash anatomy applies. The controller is the doorway, not the storage, and manufacturers leave other ways in — internal technological pads beneath the surface, behind the failed chip, which speak the memory's raw protocol directly. The data is read through those and reconstructed in software: descrambled, error-corrected, and reassembled through the translation layer until the filing structure stands up and the photographs can be extracted and rendered.
What to stop doing: attempting the format again, and inserting the card anywhere further. Each attempt powers a failed controller for no diagnostic benefit — two devices have already established the position — and the one outcome to avoid is a format that succeeds on a partially-responding card.
On the bench
No further host or camera attempts were made, since two independent devices had already established the position and a successful format was the only thing left that could make matters worse. The card was prepared as a monolith and its internal technological pads exposed and probed on the PC-3000 Flash Spider Board, with the pinout confirmed against the Rusolut VNR database — the failed controller bypassed rather than coaxed. The raw memory read out, and reconstruction ran the full pipeline: XOR descrambling for the controller family, ECC correction, and translation-layer rebuild until the card's filing structure stood up. The photographs were extracted, validated by rendering rather than counted, and delivered on fresh media.
The outcome
The contents read at chip level past a failed controller, 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 camera cannot format a card: formatting requires writing, which is more demanding than reading, so a device that cannot complete a format is reporting a card that is not responding well enough to be written to — which places the fault at the controller rather than at your photographs; the memory behind a failed controller is normally entirely intact and reachable through pads it never guarded; and the failure to format is the reason your images still exist, because a format that succeeded would have written empty structures over all of them. Stop trying it.
Camera refusing to format a card that nothing will read
Stop trying to format it — and be quietly grateful it didn't work. Formatting means writing new filing structures over the card, so a successful format on a misbehaving card is the most common way photographs are lost after a fault rather than because of one. That the camera couldn't complete it is what preserved your position. It's also informative: writing is more demanding than reading, so a device that can't write to a card is telling you the card isn't responding properly at a low level, which points at the controller rather than at your images. Two devices failing to see it is a complete elimination — don't keep inserting it elsewhere, because each attempt powers a failed controller for nothing and risks a format eventually succeeding. The memory behind a dead controller is normally untouched and readable directly.
Stop trying — that failure is protecting you. Call Glasgow Data Recovery on 0141 404 0294; read at chip level past the controller, reconstructed in software, every photograph checked by eye.
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.