Flash & SSD · job record · HUL-2025-0939
Five Machines. Not One Noticed It.
It read at one pond and was dead at the next. An ecology consultancy in Beverley tried it on two desktops, three laptops and a hub with its own power supply, and got no reaction out of any of them
. Nothing sounded, nothing appeared in Disk Management, and you may as well be plugging in a stone
. The stick held the photographs from a full season of newt surveys.
Sounds like yours? Ring us.
0800 6890668
What causes it.
Six devices tried, no response from any one of them: the computers are in the clear and the fault is inside the plastic. Only two things in there can cause it. Behind the metal connector sit solder pads that flex slightly every time the stick goes in; next to those is the controller, the part that speaks to a host on the memory's behalf. Neither holds a single photograph. They only stand between you and the ones that are held. The flash holds onto what was written to it even when nothing is left that can ask for it, and a lab starts from that.
The tools this one needed.
The steps we follow →| The gear | What this one did | Why we have it |
|---|---|---|
| PC-3000 Flash | Read the bare package directly, with the controller out of the circuit | Goes round the controller and reads the NAND itself, matched to a maker-ID library kept current |
| Rusolut Visual NAND Reconstructor | Rebuilt a logical image from the raw read — ECC, XOR, then page and block order | Makes sense of a raw NAND dump: ECC, XOR, page order, then reassembly |
| IR preheater & BGA rework station | Lifted the BGA cleanly and prepared its pads for the socket adapter | Warm enough to take the NAND off and reball it, never warm enough to risk the data |
The stages.
Rule out the cheap fault first
The stereo microscope came first. A hairline break in the solder under the connector is a bench repair, an hour with a soldering iron at most. There were no breaks. Every track was continuous. Put on power, the controller drew current while its data lines stayed silent, which matched what the office had found.
Read the memory and leave the controller alone
The package was removed, its pads cleaned, and read raw through a socket adapter. Everything after that rests on one fact: when a controller dies, the data does not leave with it. What was written is still in the silicon, laid out however the chip decided to lay it out at the time.
Work out the old layout and the folders come back
Rusolut broke the dump down and built it back up: correction codes applied, the XOR pattern identified, pages and blocks put back where they belonged, until the arrangement the failed controller once presented existed again. A filesystem came up, and the survey folders were in it.
How it finished.
The set went home on fresh media, three frames short, and ahead of the licence deadline. All three losses were from the last pond visit, all three came back damaged, and that is written into the report.
What people read after this.
More on SSD & flash.
Is yours doing the same?
Turn it off. Send it to us. The diagnosis comes first. It says which files are still readable and which are not.