Case record · SSD & flash · SDR-2025-0939
The USB Stick Every Computer Ignores.
The description of the problem was brief because the testing behind it was extensive. The client can't get at anything on the memory stick
, and it isn't picked up by any of our machines
: four laptops, a desktop and a powered hub between them. The same silence every time. The survey photographs on it had become hypothetical.
Seeing the same thing yourself?
0800 6890668
The translation.
Being rejected by all devices is actually quite a helpful diagnosis: it eliminates every machine you tried and clearly points directly back into your stick. The two main suspects that sit behind this door are the USB connector (with its soldered connections), because it gets jostled each time you insert it into the computer, and the controller chip (which sits between memory and the host computer). Neither of these two faults will ever touch the NAND. That is why chip level repairs so often succeed in recovering flash drives that appear dead.
Kit used on this job.
What happens in a case →| Which platform | Its role in this case | Why we use it |
|---|---|---|
| PC-3000 Flash | Identified the NAND and read it without the dead controller | Pulls data straight from memory chips, with a current library that identifies them automatically |
| Rusolut Visual NAND Reconstructor | Corrected the errors and reordered pages to rebuild the logical map | Rebuilds files from a raw NAND image: ECC, XOR, page transforms, reassembly |
| IR preheater & BGA rework station | Getting the package off and reballed so the NAND could be read | Lifts memory chips off and reballs them without burning what they hold |
In the lab.
Rule out the cheap fault first, then the dear one
Firstly, an optical microscope was used to examine the solder connections on the connector for damage. It takes less time and money to repair a broken connection than fixing memory. The joints proved sound; therefore, the focus could now be solely on the controller (the "brain" of the system), confirming that the cross-machine tests had pointed at the right component.
Read the NAND without asking the controller
The memory was then accessed directly and dumped in its raw state. This is what makes flash recovery possible at all: a controller can be completely dead while the NAND behind it still holds every piece of information ever written to it, laid out in whatever order the controller chose.
Unpick the controller's layout, then rebuild the files
At this point, the raw dump was run through ECC, descrambling and page reordering in order to match the original (logical) layout the controller had presented. Only after the data was laid out as originally intended did a file system become apparent again, allowing the client to see their reports and photographs once again.
The result.
Recovered and delivered on fresh media, bar three photographs from the last site visit, which came back damaged and were flagged as such.
Similar cases on the index.
Also from SSD & flash.
Does this sound like your own drive?
The rule holds as in every case above: switch it off, and let a free diagnosis come before any decision.