Data Recovery Case File · Memory Cards · One File That Matters

The 64GB card that swore it was 32MB: recovering a proposal from a controller in denial

Some recoveries are measured in terabytes; this one was measured in minutes of footage that can never be re-shot — a wedding proposal, filmed on a GoPro, on a microSD that afterwards refused to be itself. It arrived with something we always appreciate: a thorough, honest write-up from the computer technician who'd tried first, documented exactly what he found, and knew precisely when to hand it on.

The enquiry

“I used a GoPro to video a wedding proposal, but the SD card now isn't working. The technician who looked at it said: the card consistently reports as only 32MB — a direct copy was just 30MB and contained no data at all. This is symptomatic of counterfeit cards, but SanDisk confirmed from photos that the serial number is correct for the card type. They did comment that the card looks slightly bent.”

Why a dying card impersonates a fake

The technician's counterfeit hypothesis was intelligent — fake cards really do announce fantasy capacities — and his diligence in checking with the manufacturer ruled it out properly. What's left when a genuine card reports a fraction of itself is the failure that mimics the fraud: a controller that can no longer bring its real flash online and falls back to exposing only a vestigial sliver — a boot-mode shadow of a card, 32MB of nothing where 64GB of everything should be. The "slightly bent" observation likely wrote the backstory: a monolith card flexed in a pocket or a slot carries invisible fractures, and controllers are the first casualties of flex. Crucially, none of this says anything about the NAND itself — the proposal wasn't gone; its librarian was.

Around the controller, into the chip

So the controller was retired from the conversation. Beneath the card's casing, its technological access points were mapped against the VNR's pinout references and the NAND read out directly and in full via PC-3000 Flash and the Flash Extractor — the entire 64GB the card had been denying it owned. Reconstruction then translated the raw dump back into a card: error correction, the controller's scrambling reversed, page and block geometry established, the translation layer rebuilt, and the exFAT volume rising out of it with the GoPro's folder structure intact. And there, in the recording folder, the file the whole case existed for — extracted, its container verified, and played through end to end, because for a one-file job "recovered" means watchable, nothing less.

Outcome

The proposal, delivered whole — plus the rest of the card's footage as a bonus nobody had dared ask about. A word for the referring technician, on the record: making a read-only copy as his first move, documenting honestly, escalating to the manufacturer, and stopping at the boundary of his tools is exactly the sequence we'd script. Cases arrive ruined by less careful hands weekly. And for anyone filming unrepeatable moments on action cameras: the take-away is dual-recording's absence — one card held the only copy of a once-in-a-lifetime yes. It worked out. It shouldn't have had to.

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.