Data Recovery Case File · Cameras, Drones & Cards · A Year's Worth of Travel

"Every single file is corrupted but still has >0kb data, so I am hoping they are recoverable" — she was right to hope: the dual-card organising disaster decoded, and a year of travel photographs reassembled from cards that still held their contents

Her enquiry was a cascade told with painful honesty. She'd backed a phone to an SD card and copied photos from two phones onto two cards; then tried to tidy the mess — "it was messy with all the different folders and random unreadable json files etc" — by moving photos out of the backup folders and "deleting all these random folders with unreadable file types." The result, all at once: "I've now somehow corrupted every single file on the two SD cards." The aggravating detail she flagged herself: "I had an adapter with 2 SD cards plugged into my Android phone that I was organising photos between." And the loss that turns a mishap into a heartbreak: "I deleted all these photos from my phone… they are a year's worth of travel photos. I am gutted." But she closed on the one technical detail that mattered most, spotted unprompted: "every single file is corrupted but still has >0kb data, so I am hoping they are recoverable." That hope is well-founded, and this page explains why — decoding the dual-card danger, the truth about those "junk" files, and the >0KB clue she read correctly.

The decode: the dual-card trap, the "junk" that wasn't, and why size meant survival

Why organising across two cards at once is uniquely hazardous: moving files between two cards mounted through one adapter, on a phone, stacks several fragilities into one operation. The phone must track two filesystems simultaneously; each move is a delete-here-write-there requiring both cards' bookkeeping to update in lockstep; and a single interruption — a slipped contact in the adapter, a moment's power dip, an app losing its place — can leave both filesystems half-updated at once. That both cards corrupted together is the signature of exactly this: not two coincidental card failures, but one botched multi-card transaction damaging both sets of structures in the same instant. The lesson, filed for everyone: organise one card at a time, and never card-to-card through an adapter — copy to a computer, organise there, write back.

The "random unreadable json files," identified: those weren't junk — they were the metadata and structure files a phone backup writes to describe its own contents: which photo belongs where, album groupings, the index tying the backup together. Unreadable to her by eye, essential to the system. Deleting them is part of how the corruption spread — she removed the connective tissue while the photo files themselves remained. No blame attaches; nobody recognises those files as load-bearing. But it explains the shape of the damage: the pictures survived, their organising framework didn't.

The >0KB observation, credited: her hopeful detail was genuinely diagnostic. A file showing more than zero kilobytes still contains data — the photograph's actual bytes are present on the card; what's broken is the filesystem's ability to read them properly (wrong size recorded, broken links, damaged directory entry). Zero-byte files would mean the content was truly gone; non-zero size means the pictures are there, mis-catalogued — which is the recoverable case, exactly as she'd guessed. She read her own evidence correctly.

The recovery: both cards rebuilt, the year reassembled

Both cards were imaged write-blocked before anything else — freezing their state against any further organising. On the images, the damage resolved as predicted: photograph data overwhelmingly intact, directory structures and metadata torn by the concurrent operation. The recovery ran two complementary methods — reconstructing the surviving filesystem structures where they held, and carving photographs directly from their content where structure was gone — reuniting images with whatever framework survived. A year of travel came back across both cards, verified by opening, and organised into a clean delivery to replace the framework her tidying had destroyed.

On the bench

Both cards went behind the DeepSpar USB Stabilizer 10Gb in turn — imaged write-blocked, the botched multi-card transaction frozen exactly where it had torn. On the images, the two complementary recoveries ran side by side: surviving directory structures reconstructed where the >0KB entries still pointed true, and OSForensics carving photographs directly by signature where the metadata her tidying had deleted once did the pointing. Its integrity checks culled the duplicates and confirmed each recovered image rendered whole. A year of travel came back organised — the tidy-up she'd attempted, finished on copies where mistakes cost nothing.

The outcome

The travel photographs recovered and delivered on new media, sorted into a sensible structure — the tidying she'd attempted, completed safely from the recovered files. Free assessment, one fixed written figure including VAT; on cards and sticks where content has been deleted or overwritten, the figure is payable upfront. "I am gutted," she'd written; the reply was the better tense, and a gentle rule for next time: originals stay put until copies are verified, and cards get organised one at a time, on a computer — never two-at-once through an adapter.

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.