Data Recovery Case File · Cameras, Drones & Cards · Structure Intact, Content Not

A Card That Lists Two Thousand Photographs Has Kept Its Index and Lost Its Reach

His enquiry describes a split that locates the fault. A card corrupted while applications were being moved between phone storage and the card, where "when read by my computer the file names load, but the photographs themselves do not — and the computer stops responding when browsing them." The index survived and the content will not come back, which points at the memory rather than the structures describing it.

The decode: what each half of the symptom locates

What the file names surviving establishes: the structures describing the card's contents are readable. Names, sizes and locations are recorded compactly in a small area, and that area is returning data normally — so the card presents, enumerates and can be read in part.

What the photographs not opening establishes: the regions holding the image data are not returning. Those occupy the overwhelming majority of the card, and a request for one is failing while a request for the index succeeds.

Why that split points where it does: the index and the content are in different physical regions of the same memory. Damage concentrated outside the structural area produces exactly this — a complete-looking listing describing content that cannot be reached.

Why the computer stalling is the same finding in another form: a request that is never answered leaves the system waiting. Browsing thumbnails asks for image data, so browsing is the operation that hangs — and the stalling is the machine waiting rather than any fault in it.

Why the most recent handful still work: they were written last, in regions the earlier content does not occupy. That confirms the damage is regional rather than total — parts of the memory are returning data perfectly well.

What the described cause fits: moving applications between phone storage and the card is a sustained, heavy write operation. It writes and rewrites large volumes across the card in a way ordinary photograph storage never does, and an interruption or a marginal region reached during it can leave the controller's mapping inconsistent.

Why the mapping matters more than it might seem: a flash controller relates a file's apparent position to its actual one. Where that mapping has been damaged, the index can still be read while requests for content are directed somewhere that does not return — which produces this symptom without the memory itself being destroyed.

Why that is the hopeful reading: if the mapping is the problem rather than the memory, the photographs are present and misaddressed. Reading the memory directly and rebuilding the arrangement in software reaches them, because the reconstruction does not rely on the damaged map.

Why the file list is genuinely useful: it says what should be there. Two thousand names, sizes and dates give an expected result to check a reconstruction against, which is a verification that would otherwise not exist.

What must not happen: no further browsing, no repair prompts accepted, and nothing further written to the card. Each browsing attempt stalls the machine and asks a struggling controller to repeat what it cannot do.

On the bench

Index availability was distinguished from content readability — names, sizes and locations being recorded compactly in a small area while image data occupies the overwhelming majority, so a complete listing alongside unreadable content indicates damage concentrated outside the structural region, with recently written items in unaffected regions confirming the fault is regional. Host stalling was interpreted as unreturned requests. Memory was read past the controller with the translation layer reconstructed in software, which does not depend on the damaged mapping.

The outcome

Index availability distinguished from content readability, the card addressed through hardware, and the memory read past the controller with the arrangement rebuilt. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: the index survived and sits in a small area; your photographs occupy everything else. If the controller's mapping is what was damaged, the images are present and misaddressed — and rebuilding the arrangement reaches them.

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.