SSD & flash · casebook entry · MKD-2025-4939
Working One Pond Visit, Gone the Next.
The Kingston went from working to non-existent between two pond visits. An ecology practice outside Towcester worked through everything it had — three laptops, two desktops, a mains-powered hub — and none of them will even notice it
: no sound, no entry in Disk Management, the same as plugging in a paperclip
. A whole season of newt-survey photographs was on it.
Same fault? Start here.
0800 6890668
Without the jargon.
Five machines and a powered hub, all silent — that is enough testing to clear the computers entirely and put the fault inside the plastic. Only two things there can cause it. Every insertion flexes the solder pads under the connector a little, and the controller does all the talking for the memory. Neither is the data; both stand in front of it. NAND holds what it was given whether or not anything can ask for it, and that is where a lab starts.
The kit this job needed.
See how a job runs here →| Kit | Why it was used | What it gives us |
|---|---|---|
| PC-3000 Flash | Identified the bare package and read it without the controller | Pulls data straight off the flash chips, matching each part to a constantly updated ID library |
| Rusolut Visual NAND Reconstructor | Turned the raw read into a logical image — ECC, XOR, page order | Takes a raw flash dump to readable files: ECC, XOR, page order, reassembly |
| IR preheater & BGA rework station | Took the BGA off intact and prepared it for the socket reader | Removes NAND from the board and reballs it, with the data kept clear of the heat |
What happened on the bench.
Rule out the cheap fault first
A broken joint at the connector is an hour with a fine iron, so the stereo microscope came first. Nothing was cracked and the tracks were clean. Given power, the controller pulled current and then said nothing on its data lines — which confirmed what all that office testing had implied.
Read the memory itself, no controller required
The package came off, was cleaned up and went into a socket reader for a raw read. That is the whole point of the exercise: a controller takes nothing with it when it dies. Every page ever written is still in the memory, filed the way the controller preferred.
Reverse the controller's filing, then get the folders back
Rusolut took the dump apart and put it right — correction applied, the XOR pattern removed, pages and blocks returned to sequence — until the view the old controller had presented existed once more. A filesystem appeared at that moment, and the survey folders with it.
The outcome.
It was back on new media before the licence application went in — three frames short, all from the last pond visit, and those three came back damaged and flagged.
Other jobs from the casebook.
More from SSD & flash.
Does that sound like your device?
One lesson runs through the lot: cut the power, let us look for free, then decide with the facts in hand.