Data Recovery Case File · Cameras, Drones & Cards · Not Detectable Anywhere
The silent card: not detected on phone or PC, no error, no drive letter — why total absence means the controller is gone, and how the Spider Board reads the memory it left behind
His report was short because there was nothing to report. A microSD card: "not detectable on phone or Windows PC — unable to access data." Not erroring, not crashing anything, not showing and then failing — simply absent from every device, as if never inserted. Total silence is its own diagnosis: where other cards in this volume erred, crashed readers, or appeared-but-refused, a card that no device registers at all has stopped answering at the most basic level — its controller is no longer responding to the world. That verdict sets the route immediately: there is no software path to a device that doesn't appear, and no reader or setting that summons a dead controller. The recovery goes straight to chip level, reading the card's memory directly — and this page walks that pipeline, from probing a monolithic card's hidden test points to reconstructing its data.
| Media | MicroSD card — completely undetected on phone and PC; no enumeration, no error, no response |
| Reported symptoms | Card absent from every device tried · no drive letter, no error message, no reaction to insertion · data inaccessible |
| Fault class | Dead controller — the card no longer enumerating at all; NAND memory typically intact behind it; chip-level recovery the only route |
| Equipment used | PC-3000 Flash with Spider Board monolith probing · Rusolut VNR pinout database and analysis · raw NAND dump; XOR descrambling, ECC correction, FTL reconstruction · verified extraction |
The decode: what total silence means, and the road it dictates
Reading the silence: the spectrum of card failure is diagnostically ordered. A card that errors is talking, badly. A card that crashes its reader is talking, poisonously. A card that appears but reports no media is half-talking — alive enough to announce itself, too broken to serve. And a card that no device registers at all has fallen off the far end: its controller — the chip whose first job is simply to answer "I'm here" when power arrives — isn't answering. No enumeration means no conversation to have, however patiently; his card's silence across phone and PC alike says the controller has died or locked beyond response. The one consolation of the bluntest failure is the clearest routing: there's nothing to try, no adapter or setting or software to attempt, because every possible attempt requires a card that appears. The road is chip-level from the first minute.
Why the memory survives the silence: the pattern this volume keeps confirming holds at its extreme: the controller and the NAND are separate components with separate fates, and a controller dying takes the card's voice, not its memory. His photos and files sit in NAND cells that were never part of the failure — an archive whose only spokesman has died. In the large majority of dead-card cases, the memory behind the silence is substantially intact, waiting on equipment that can address it without the controller's help.
The monolith road: modern microSDs are monolithic — controller and NAND fused in one sealed package, no separate chip to lift off — so reading the memory directly means reaching the technological test points hidden on the card itself: the manufacturer's own access pads, exposed by carefully removing the card's coating, identified against pinout references, and probed to speak the NAND's raw protocol past the dead controller entirely. What comes off is a raw dump — scrambled, error-laden, ordered by the controller's private logic — which reconstruction then unwinds: the scrambling reversed, the errors corrected, the layout rebuilt until a filesystem stands up. It's the deepest route in flash recovery, and for a silent card it's the only one — and it works precisely because the data never depended on the part that died.
On the bench
The card was prepared for chip-level access — its coating carefully removed to expose the monolith's technological pads — and probed on the PC-3000 Flash Spider Board, its twenty-five sprung needles making solder-free contact, with the pinout confirmed against the Rusolut VNR monolith database. The raw NAND read out past the dead controller entirely, and reconstruction ran the full pipeline: XOR descrambling against the controller family's keys, ECC correction of accumulated bit errors, and rebuilding of the flash translation layer until physical pages resolved into his folders and files. The card that no device could detect gave up its contents to the one road that never needed it to answer — extracted and verified.
The outcome
The silent card's data recovered from the NAND and delivered verified. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The bluntest failure decoded for every owner who's met it: a card absent from every device has lost its controller, not its memory — there's nothing to "try," because trying needs a card that appears — and the chip-level road reads the archive directly, past the spokesman that fell silent.
Card not detected on any device at all
Stop cycling it through readers and phones — a card that's completely absent (no letter, no error, no reaction) has a controller that's stopped answering, and no adapter, setting, or software can summon a dead controller, because every attempt requires a card that appears. The good news is the pattern that holds across flash: the controller's death takes the card's voice, not its memory — your data sits intact in the NAND behind the silence in the large majority of these cases. The route is chip-level: the card's hidden test points probed directly and the memory read past the dead controller. That's lab work — and it's exactly what total silence calls for.
The memory doesn't need the controller — call Edinburgh Data Recovery on 0131 202 0491; probed on the Spider Board, reconstructed, verified, one written figure.
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.