SSD & flash · job on file · BHD-2025-8939
Plug It In and Nothing at All Reacts.
Somewhere between one pond and the next, the Kingston stopped being a device. An ecology practice outside Worcester tried it on everything they had — three laptops, two desktops and a powered hub — and none of them so much as blink when it goes in
: no chime, nothing appearing in Disk Management, it may as well be a bit of bent wire
. A full season of newt survey photographs was on it.
Sounds like yours? Give us a ring.
0800 6890668
What that means.
Five computers and a powered hub, none of them reacting: that rules out the machines and puts the fault inside the plastic. Two parts in there can produce it. The solder pads under the metal connector take a small flex on every insertion, and the controller does all of the talking on the memory's behalf. Neither of them stores anything. They stand between you and what is stored. Flash holds on to whatever was written into it regardless of whether anything is still able to ask, and that is where a lab starts from.
What did the work here.
The order of the work →| Equipment | The job it did | What it adds |
|---|---|---|
| PC-3000 Flash | Read the bare package direct, with the dead controller out of circuit | Goes straight to the NAND chips, checked against a maker-ID library that is kept current |
| Rusolut Visual NAND Reconstructor | Rebuilt a logical image out of the raw dump: ECC, XOR, page and block order | ECC, XOR, page order and reassembly: what makes a raw NAND dump readable |
| IR preheater & BGA rework station | Removed the BGA undamaged and made it ready for the socket adapter | Heat held low enough to free the NAND and reball it while the contents survive |
What we did.
Rule out the cheap fault first
Out came the stereo microscope first, since a cracked joint behind the connector is an hour's work with a fine iron and nothing more. Nothing was cracked, and the tracks ran clean the whole way. On power, the controller drew current and its data lines stayed dead, which put the office findings beyond doubt.
Go to the memory and leave the controller behind
Off came the package, cleaned and set into a socket reader to be dumped raw. Everything else follows from a single fact: when a controller dies it carries none of the data away with it. All the pages ever written stay in the silicon, sitting in whatever order the chip once chose to use.
Unpick the controller's own layout and the folders come back
Rusolut took the dump to pieces and reassembled it: error correction run, the XOR pattern lifted out, pages and blocks returned to their proper order, until what the dead controller used to present existed once more. A filesystem showed up, and the survey folders inside it.
How it closed.
The whole set went back on fresh media in time for the licence application, three frames short. All three were from the last pond visit, came out damaged, and were marked up as such.
Other pages worth a look here.
Alongside SSD & flash.
Is yours behaving the same way?
Switch the device off, post it in, and decide nothing until the diagnosis comes back to tell you where you stand.