Call us — 0131 202 0491
Mon–Fri · 9am–6pm · No fix, no fee
Start a free diagnostic →
Guide · from the Princes Street bench

Monolith cards, and reading the chip directly.

Crack open a microSD — conceptually, please — and you won’t find components: you’ll find one thing, a ‘monolith’, controller and flash memory fused into a single resin-sealed sliver. It’s why cards survive washing machines — and why, when they do die, ordinary recovery hits a wall that only chip-level work gets past. This lab helped pioneer that work in the UK; here’s what it actually involves.

25 years’ experience
In-house, never outsourced
No fix, no fee · most jobs
// the craft

One chip, no moving parts.

Inside every microSD is a single resin-sealed sliver — here's what reading it directly actually involves.

1 chip
Controller + flash fused
Test points
Beneath the resin
Raw NAND
Read, then decoded
UK-early
Adopter of the technique
// when cards really die

Past the reader, past the software.

Most ‘dead’ cards aren’t — corruption over intact photos is the common case, fixed at the file-system level. True card death is different: the controller portion fails, or the shell snaps through, and the card stops existing electrically — no reader, no computer, no software will ever see it again, because the machinery that presented the flash to the world is gone. The flash itself, though, very often survives: NAND cells are passive and tough, sitting there holding their charges inside the resin, waiting for someone with another way in.

// the other way in

Test points, raw dumps, and undoing the scramble.

The other way in is the monolith’s own service interface: microscopic test points beneath the resin, placed at manufacture for factory programming. Chip-level recovery maps them — sanding back coating under magnification, identifying the pinout for that monolith family — and reads the raw NAND directly, bypassing the dead controller entirely. What comes out is deliberately unreadable: controllers scramble data across the flash with wear-levelling, interleaving, XOR patterns and error-correction coding, all vendor-specific. The second half of the job is mathematically undoing that scramble — reconstructing the controller’s logic from the patterns in the dump until files reassemble. It’s the same discipline the Vaio SSD case ran at larger scale, and it’s been in this lab’s toolkit since the technique’s early UK days.

// what it means for you

Practical consequences.

Three takeaways travel home from this. A snapped card is a diagnostic question, not a verdict — the break’s path decides everything, and the free look answers it. ‘Nothing can read it’ means ordinary channels are exhausted, not extraordinary ones — second opinions exist precisely for the gap between shops and benches. And prevention remains embarrassingly cheap: cards are the only storage most people carry unbacked-up through weddings, holidays and once-in-a-lifetime days — the memory card page ends every answer the same way this post does: copy the card tonight.

// if this is you

The bench is a phone call away.

Holding a card no reader will acknowledge — snapped, silent, or simply absent? The diagnostic is free, the quote is fixed in writing, and honest advice on 0131 202 0491 costs nothing at all.

0131 202 0491