Data Recovery Case File · Cameras, Drones & Cards · Silence Is a Diagnosis
When the Computer Doesn't React At All
His enquiry reached a reasonable conclusion from an accurate observation. The microSD card from a family phone "suddenly stopped working. I have tried various recovery software, but at the end of the day Windows does not react at all when the card is inserted, so my assumption is that it is simply broken. It was a cheap 32GB card." The photographs on it are of his young child and exist nowhere else, which is the whole of why this matters. His assumption is understandable and only half right. Total silence is a specific finding rather than a general one — and it points at the part of a card that fails most often and matters least, while the part holding his photographs is usually untouched.
| Media | 32GB microSD card from a mobile handset — producing no host response of any kind on insertion; irreplaceable family photographs held |
| Reported situation | Card ceasing to function in normal use · no reaction from the operating system on insertion · multiple recovery applications attempted without result · card of low-cost marketplace origin · photographs held nowhere else |
| Fault class | Controller failure with no enumeration — electrical handshake not completed; memory die typically intact and reachable through internal pads |
| Equipment used | No further insertion · monolith preparation and internal technological pads exposed · PC-3000 Flash Spider Board probing · Rusolut VNR pinout confirmation, descrambling, ECC correction and translation rebuild · photographs validated by rendering |
The decode: what silence means, and why the software never had a chance
Why nothing happening is informative: when a card is inserted, the host applies power and waits for the card to identify itself. Only after that handshake does anything else occur — no sound, no notification, no drive letter, no error. A card that produces no reaction whatsoever is one that never completed that first exchange. That is a narrower finding than "broken": it places the fault at the controller, the small chip that conducts the introduction and manages the memory, rather than at the memory itself.
Why that distinction is the good news: the controller is the doorway. The memory die behind it holds the photographs, and a controller failing does not damage what is written in the NAND. Manufacturers also leave internal technological pads beneath the card's surface, behind the controller, which speak the memory's raw protocol directly. The data is read through those and reconstructed in software — descrambled for the controller family, error-corrected, and reassembled through its translation layer until a filesystem stands up. The failed part is bypassed rather than repaired.
Why the recovery software could never have worked: worth explaining, because he tried several and reasonably concluded the card was beyond help. Those applications scan a device the operating system has presented to them. Where the card never enumerates, Windows has nothing to hand over, so the software has nothing to scan. Its failure says nothing at all about whether the photographs survive — only that the card is not connecting. Trying more applications would produce the same result for the same reason.
On the card being an inexpensive one: relevant and not decisive. Low-cost cards from marketplace sellers are frequently built with lower-grade controllers, and some are relabelled to claim capacities they do not have. Those cards fail earlier and more abruptly than branded ones, and abrupt controller death is exactly the failure they tend to have. But the memory die is still a memory die, and the recovery route is the same. The lesson for afterwards is about where irreplaceable photographs are kept rather than about blame.
What to do now: stop inserting it. Every attempt applies power to a failed controller and returns the same silence, and the card should be kept flat, dry and away from anything that might flex it.
On the bench
No further insertion was attempted, since the card had already given the only answer a host can produce. It was prepared as a monolith and its internal technological pads exposed and probed on the PC-3000 Flash Spider Board, with the pinout confirmed against the Rusolut VNR database — bypassing the failed controller rather than attempting to revive it. The raw memory was read out and reconstruction ran the full pipeline: descrambling for the controller family, ECC correction, and translation-layer rebuild until the filesystem stood up. Every photograph was validated by rendering at full resolution and delivered on two separate media.
The outcome
The memory read at chip level past a failed controller, every photograph validated by rendering and delivered on more than one copy. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode, for anyone whose card produces no reaction at all: that silence is a specific finding rather than a general one, because a host applies power and waits for the card to identify itself before anything else can happen — so a card that produces nothing never completed that first exchange, which places the fault at the controller rather than at your photographs; the memory behind it is normally intact and reachable through pads the controller never guarded; and recovery software could not help because the system never presented a device for it to scan, which says nothing about whether the images survive.
Card that produces no response at all
Stop inserting it, and don't read the silence as the worst answer — it's a narrower finding than it feels. A computer applies power to a card and waits for it to identify itself, and only after that does anything else happen. So a card that produces no sound, no notification and no error never completed that first electrical exchange, which points at the controller chip rather than at the memory holding your photographs. That memory is normally completely unaffected and can be read directly through connections behind the failed controller. It also explains why recovery software achieved nothing: those tools scan a device the system has handed to them, and yours was never presented, so there was nothing to scan — their failure tells you about the connection, not about your pictures. Keep the card flat and dry, and don't try more software.
Silence points at the controller — call Glasgow Data Recovery on 0141 404 0294; read at chip level through the card's internal pads, every photograph checked by eye and delivered on two copies.
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.