Data Recovery Case File · Cameras, Drones & Cards · Not a Plain Card
A Card With Its Own Electronics Is Not Laid Out the Way Software Expects
His enquiry describes a card that behaves unlike an ordinary one, because it is not one. A camera card that began reporting itself unformatted when nearly full, where "none of the recovery software I have tried has found any files" — and which is a wireless-enabled model carrying its own processing and network hardware. That changes how the card is arranged internally, and it explains an empty result better than absent data does.
| Media | 32GB camera memory card incorporating wireless transfer hardware — reporting as unformatted; consumer recovery software returning no files |
| Reported situation | Card in use in a camera storing photographs · card approaching capacity · card beginning to report an unformatted error · multiple consumer recovery packages run · no files located by any of them · photographic content required |
| Fault class | Structure damage on a card with non-standard internal layout — embedded controller and reserved areas altering the arrangement software expects; content retained |
| Equipment used | Non-standard internal layout identified before conclusions were drawn from software results · card imaged write-blocked at the block level before any scanning · reserved and vendor areas mapped separately from the user region · signature carving performed across the user region independently of any directory · recovered images validated by opening |
The decode: what makes this card different, and why software found nothing
What an ordinary card contains: memory and a controller, presenting a single straightforward region with a filesystem on it. Recovery software assumes exactly that, and it is right almost always.
What this one contains additionally: a processor and wireless hardware, with its own firmware and working storage. Those need space, and that space is taken from the same memory — arranged in reserved areas the card manages itself.
Why that defeats a naive scan: software looking for a filesystem at the expected place may find vendor structures instead. Finding nothing it recognises, it reports nothing — which describes its assumptions rather than the card's contents.
Why the unformatted message arises for the same reason: the camera or computer read the region it expects a filesystem in and could not interpret what it found. That is a failure to read rather than a discovery that the card is blank.
Why the card being nearly full is relevant: a card working near capacity has less free space for its controller to manage wear across. Both the storage controller and the card's own firmware are working hardest at that point, which is when structures are most likely to be left inconsistent.
What is done differently: the card is imaged at the block level exactly as it stands, and the reserved and vendor areas mapped separately from the region holding photographs. Knowing which part is which is most of the work.
Why the photographs are then straightforward: once the user region is identified, images are located by their own recognisable openings. That requires no filesystem and no knowledge of the card's peculiarities.
Why the software results should not be read as bad news: nothing about them indicates the memory is empty. They indicate that tools built for plain cards did not find what they expected on a card that is not plain.
Why the wireless function is worth mentioning separately: cards of this kind can transfer images automatically. Some of the photographs may already exist on a phone, tablet or computer the card was paired with — which costs nothing to check and could end this.
What must not happen: no formatting, no further scanning, and no attempts to use the card's own utilities to repair it. Those write to the very region the images occupy.
On the bench
Non-standard internal layout was identified before conclusions were drawn from software results — an ordinary card presenting a single region with a filesystem, whereas this class incorporates a processor and wireless hardware requiring firmware and working storage taken from the same memory and arranged in reserved areas, so software looking for a filesystem at the expected location encounters vendor structures and reports nothing. Reserved and vendor areas were mapped separately from the user region.
The outcome
Non-standard layout identified before conclusions were drawn, the card imaged at the block level, and carving performed across the user region independently of any directory. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: your software found nothing because it was looking in the place a plain card keeps its filesystem. This card carries its own processor and firmware in reserved areas, so the layout is not what those tools assume.
A camera card with wireless hardware built in
Check whatever device the card was paired with first — cards of this kind transfer automatically, so some photographs may already exist on a phone, tablet or computer, and that costs nothing to establish. Then stop scanning and refuse any format prompt. An empty result from consumer software isn't evidence your memory is blank: these cards carry a processor and wireless firmware in reserved areas taken from the same memory, so tools looking for a filesystem where a plain card keeps one find vendor structures instead and report nothing. Once the user region is mapped, images are found by their own signatures.
Check the paired device first — call Manchester Data Recovery on 0161 871 0788; non-standard layout identified before conclusions are drawn, imaged at the block level, reserved areas mapped separately from the user region.
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.