Lab accepting new cases ·  Mon–Fri, 9am–5:30pm Urgent? Call 01273 964902
BDR Brighton Data Recovery 01273 964902 Start a case
BDR / Casebook / The USB Stick No Computer Will Read

Case file · SSD & flash · BDR-2025-0939

The USB Stick No Computer Will Read.

The report was brief because the testing process had been extensive. The owner cannot access the files stored on the USB drive, and the stick can't be recognised by my laptop, nor by any other device. No matter what machine she inserted it into, there was an eerie silence from each. The files within the USB drive became purely theoretical.

Outcome verified with the client Details anonymised

Same symptoms on your desk?
01273 964902

The decode.

A universal rejection can be seen as "diagnostically generous", as this clears every computer it was tested with and places full blame for the problem on the door of the USB stick. There are two contenders located behind this door: the USB connector and its solder joints that endure the physical rigours associated with every insertion, and/or the controller chip that displays the memory to the host. Neither type of failure affects the NAND itself, which is why many times when a stick appears to be dead, chip-level recovery is successful.

Equipment on this case.

How a job runs here →
The systemWhat it did on the dayWhy this tool
PC-3000 FlashIdentified the memory and read it independently of the failed controllerReads memory chips directly, with a current chip database for automatic identification
Rusolut Visual NAND ReconstructorError correction and block reordering to rebuild the logical imageTurns a raw NAND dump back into files: ECC, XOR, page transformation, reassembly
BGA rework station & IR preheaterChip access and reballing where the package had to come offRemoves and reballs memory chips without cooking what's inside them

At the bench.

01

Check the cheap fault before the expensive one

The connector joints were examined first, as a fractured solder joint is considerably easier to repair than anything affecting the memory. The joints were solid, which indicated that the issue lay with the controller, and supported the owner's cross-machine testing efforts, and pointed out where to concentrate further investigation.

02

Read the memory without the controller's cooperation

Directly accessing and dumping raw data from the memory was the next step. This is the necessary step required for recovering information from a failed flash storage device. While the controller may have died, the NAND contains all of the data that was written to it by the controller, and in the exact order chosen by the controller.

03

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.

Where it ended up.

The stored files recovered complete and delivered on new media. The stick, its one job permanently delegated, was retired without ceremony.

What this case teaches: When every computer says no, the stick has confessed. Direct memory reads don't need the controller's permission.

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.

01273 964902