Data Recovery Case File · Solid State & Flash · The Light Is Wired to the Power
USB Not Recognised: the Light Is Wired to the Power
His enquiry contained its own reasoning, and the reasoning is the thing worth correcting. An unbranded 8GB memory stick not recognised by his Mac: "red light comes on, so the power is getting through, but no connection to the memory on the stick to retrieve data." His inference — light means power, power means the stick is partly alive — is entirely sensible, and it is also the reason so many people keep trying. The correction is small and it changes the picture: the light on a memory stick is wired to the supply, not to the controller. It illuminates when voltage arrives at the board, and it will do that just as cheerfully on a stick whose controller is completely dead. So his light proves the port works. It says nothing at all about whether anything inside is still answering — and the specific kind of stick he has makes the likely answer worth spelling out.
| Media | Unbranded 8GB USB flash drive — indicator illuminates on connection; not enumerated by the host; contents inaccessible |
| Reported situation | Stick powers and indicates but is not recognised · no device presented to the operating system · data retrieval sought |
| Fault class | Controller failure with power present — NAND typically intact; chip-level access required, complicated by unbranded controller identification |
| Equipment used | Enumeration attempt behind DeepSpar USB Stabilizer 10Gb · PC-3000 Flash with Spider Board probing for chip-level reads · Rusolut VNR pinout identification and reconstruction — XOR, ECC and translation rebuild · files verified by opening |
The decode: what the light means, and what an unbranded stick changes
Why the LED tells you almost nothing: a flash drive's indicator is a simple circuit driven by the incoming supply, sometimes with a flicker tied to activity. It lights on power alone. That makes it useful for exactly one thing — confirming that the port, the cable and the stick's power path are working — and useless for everything else. A controller that has failed leaves the light on and the drive silent, which is precisely his description. It is worth knowing because the light is the reason people keep plugging a dead stick into one more machine: it looks like something is happening.
What is actually failing: a memory stick is essentially two components — a controller that manages the memory and presents the device to the computer, and the NAND that stores the data. When the computer reports nothing at all, the controller has stopped conducting the introduction. And the constant that runs through every flash case in this archive applies here too: the memory behind a dead controller is normally untouched. The files are not lost; the thing that fetches them has stopped.
What an unbranded stick changes: honestly, and without disparaging anyone's purchase — this matters for the work rather than for blame. Recognised manufacturers use documented controller families, and a recovery platform can identify the controller, look up its pinout and its scrambling scheme, and get to work. Unbranded and generic sticks frequently use whatever controller was cheapest that quarter, sometimes paired with lower-grade or downgraded NAND, and the same product name can hide several different internal designs. For chip-level recovery that means an extra research stage: identifying the controller from the die markings and the board layout, determining the pinout, and establishing the correct descrambling and error-correction scheme before a single file can be reconstructed. It is entirely doable — the databases these platforms carry exist for exactly this — but it is why an unbranded stick can take longer than a name-brand one holding the same amount of data.
The practical instruction: stop inserting it. Each attempt powers a failed controller for no diagnostic benefit — the light will keep coming on, and the answer will keep being the same. And when the files are back, the general lesson stands: a stick is transport, and an unbranded one is transport you should trust least of all.
On the bench
An enumeration attempt ran first behind the DeepSpar USB Stabilizer 10Gb, write-blocked — a controller that responds even briefly changes the route entirely, and that possibility is always tested before anything invasive. It did not respond. The chip-level road followed: the memory probed on the PC-3000 Flash Spider Board, with the controller identified from its markings and layout and the pinout confirmed against the Rusolut VNR database — the research stage that an unbranded device makes unavoidable. The raw NAND read out, then XOR descrambling, ECC correction and translation-layer rebuild until a filesystem stood up. His files were verified by opening and delivered on fresh media.
The outcome
The contents recovered at chip level past a failed controller, verified and delivered. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The correction worth carrying: the light on a memory stick is wired to the power supply, not to the data, so it will shine just as brightly on a stick whose controller is dead — it confirms your port works and nothing more; a stick that is entirely unrecognised has stopped conducting its introduction, and the memory behind it is normally perfectly intact; and unbranded sticks add a research stage at chip level, because the same product name can hide several different controllers.
Memory stick lights up but nothing sees it
Don't read the light as a good sign — it's wired to the incoming power and will illuminate on a stick whose controller has completely failed. All it proves is that your port and cable work. So stop plugging it into more machines: each attempt powers a dead controller and tells you nothing new. Don't run repair or format utilities at it, don't let anything reformat it if a computer ever does see it briefly, and don't take it apart. The good news is the usual flash anatomy: when nothing enumerates, it's almost always the controller that has stopped, and the memory holding your files sits behind it untouched, reachable by reading the chip directly. Be aware that unbranded sticks take longer at that stage, since the controller has to be identified before the data can be descrambled — and once you have your files back, treat any stick as transport rather than storage.
The light is the power, not the data — call Leeds Data Recovery on 0113 322 3083; enumeration tested first, memory read at chip level past the dead controller, files verified by opening.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.