Case file · SSD & flash · BDR-2025-0939
The USB Stick No Computer Will Read.
The report was short because the testing had been thorough: the owner cannot access the files stored on the USB drive
, and the stick can't be recognised by my laptop
— or by any other machine she plugged it into. Every computer, same silence. The files inside had become theoretical.
Same symptoms on your desk?
01273 964902
The decode.
Universal rejection is diagnostically generous: it exonerates every computer tried and convicts the stick's own front door. Two candidates sit behind that door — the USB connector and its solder joints, which take mechanical abuse every insertion, or the controller chip that presents the memory to the host. Neither failure touches the NAND itself, which is why chip-level recovery so often succeeds on sticks that appear completely dead.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| PC-3000 Flash | Identified the memory and read it independently of the failed controller | Reads memory chips directly, with a current chip database for automatic identification |
| Rusolut Visual NAND Reconstructor | Error correction and block reordering to rebuild the logical image | Turns a raw NAND dump back into files: ECC, XOR, page transformation, reassembly |
| BGA rework station & IR preheater | Chip access and reballing where the package had to come off | Removes and reballs memory chips without cooking what's inside them |
On the bench.
Check the cheap fault before the expensive one
Connector joints were inspected first, since a fractured solder joint is a far simpler fix than anything involving the memory. They were sound — which left the controller, and confirmed the owner's cross-machine testing had been pointing at the right component all along.
Read the memory without the controller's cooperation
The memory was accessed directly and dumped raw. This is the step that makes flash recovery possible at all: the controller may be dead, but the NAND behind it holds everything it was ever given, in the physical order the controller chose.
Undo the controller's arrangement, then rebuild files
The raw dump was processed through error correction, descrambling and page reordering to reconstruct the logical image the controller used to present. Only then did a filesystem appear, and with it the owner's files under their proper names.
The outcome.
The stored files recovered complete and delivered on new media. The stick, its one job permanently delegated, was retired without ceremony.
Related on the index.
More from SSD & flash.
Recognise your own drive in this story?
Same rule as every case above: power it down, and let the diagnosis be free before any decision has to be.