SSD & flash · casebook file · MHD-2025-6939
The USB Stick Nothing Will Acknowledge.
Between one pond visit and the next, the Kingston stopped existing. An ecology practice near Henley-on-Thames tried everything in the office — three laptops, two desktops and a mains-powered hub — and not one of them reacts to it at all
: no chime, nothing new in Disk Management, you might as well be plugging in a paperclip
. An entire season of newt survey photographs sat on it.
Much the same fault? Call us.
0800 6890668
In everyday terms.
Five computers and a mains-powered hub, all of them silent: that clears the machines and places the fault inside the casing. Only two components there are capable of causing it. The solder pads beneath the metal connector flex a little on every insertion, and the controller conducts the whole of the conversation on the memory's behalf. Neither one holds a single file; both merely stand in front of the files. Flash keeps what was written to it whether or not anything can still ask for it, and a lab begins from that fact.
What the bench used here.
How a job is handled →| Tool | Why we used it | What it brings |
|---|---|---|
| PC-3000 Flash | Recognised the bare package and read it with the controller bypassed | Reads the NAND chips directly, matched against a maker-ID library that is kept up to date |
| Rusolut Visual NAND Reconstructor | Converted the raw dump into a logical image: ECC, XOR and page order | Turns a raw NAND dump into readable files: ECC, XOR, page order, reassembly |
| IR preheater & BGA rework station | Lifted the BGA off undamaged and dressed it for the socket adapter | Lifts the NAND off the board and reballs it, keeping the heat away from the stored data |
The lab work.
Start with the fault that is cheap
The first instrument out was the stereo microscope, because a fractured joint behind the connector is only an hour under a fine iron. No cracks, and the tracks were clean throughout. Given power, the controller drew current and then stayed silent on its data lines, which confirmed what the office testing had already implied.
Read the flash itself, with no controller involved
The package was lifted, cleaned and seated in a socket reader for a raw dump. That is what the whole procedure rests on: a failing controller carries nothing away with it. Every page ever written remains in the silicon, arranged in whatever order the controller preferred.
Undo the controller's arrangement, and the folders return
Rusolut pulled the dump apart and put it back together: error correction applied, the XOR pattern stripped out, pages and blocks restored to their original order, until the arrangement the dead controller once presented existed again. A filesystem appeared at that point, and the survey folders within it.
How the job closed.
The set was back on fresh media before the licence application was due, three frames short. All three came from the final pond visit, returned damaged, and were flagged as such.
More of the jobs we've closed.
Filed beside SSD & flash.
Does any of that match your case?
Nothing needs deciding until the diagnosis is back: switch the device off, send it in, and let the findings settle it.