Data Recovery Case File · Solid State & Flash · The Controller Is Running
On a Stick, the Light Tells You More Than Usual
Her enquiry offers an observation this archive usually dismisses and here does not. A stick that stopped working with no visible damage: "the indicator is still working. When I plug it into a PC or laptop — I've tried several — it isn't detected by the machine and it doe"s not appear anywhere. On an external hard drive, a light generally reports only that power arrived. On a flash drive it is usually driven by the controller itself, which makes a lit indicator a genuine finding about what is happening inside.
| Media | USB flash drive — activity indicator illuminating on connection; not enumerated by any host; no physical damage present |
| Reported situation | Stick ceasing to function without warning · no physical damage apparent · indicator illuminating normally on connection · not detected by several computers · not appearing in any device listing · contents required |
| Fault class | Controller powering and executing without completing enumeration — configuration read failure indicated; memory unaffected |
| Equipment used | No repeated connection attempts · indicator behaviour on connection recorded as evidence of controller execution · enumeration state read write-blocked under strict timeouts (DeepSpar USB Stabilizer 10Gb) · chip-level read past the controller · translation layer reconstructed in software |
The decode: why this light is different
Why lights are usually uninformative: on an external hard drive the indicator is typically wired to the enclosure's power stage, so it illuminates because electricity arrived and nothing more. This archive repeatedly points out that such a light says nothing about whether anything is working.
Why a flash drive's indicator is different: there is no room inside for separate indicator circuitry, so on most designs the light is driven directly by a controller output — usually as an activity indicator the firmware operates. For it to illuminate, the controller must have powered up, begun executing its firmware, and reached the point of driving that pin. That is a real sequence of things having gone right.
What that narrows the fault to: a controller that is alive and running, and failing somewhere after that. The commonest place is the configuration read — the controller loads its capacity, geometry and the tables mapping logical addresses to physical memory before it can introduce itself, and where those cannot be read it never completes enumeration. So the device is executing and cannot describe itself, which is why no host sees anything.
Why that is a good position: a controller that cannot read its own configuration has not written to or erased anything. The memory holds exactly what it held. And on a stick the memory can be read directly through the manufacturer's test points, bypassing the controller entirely, then descrambled, error-corrected and reassembled in software — with the addressing pattern reconstructed from the memory contents themselves.
Why the light is worth reporting rather than mentioning in passing: a stick that shows nothing at all on connection points at a controller that never powered — a different and less tractable position. Distinguishing the two costs nothing and changes the assessment.
Why more computers will not help: the fault is internal and every host will get the same answer. Her testing across several machines was worth doing once and has done its job thoroughly.
What must not be run: nothing, because there is nothing to run anything against. Where a device does not enumerate, no software reaches it — which is worth knowing before paying for a tool that promises to.
On the bench
No repeated connection attempts were made, the fault being internal and every host returning the same answer. Indicator behaviour on connection was recorded as evidence of controller execution — a flash drive's light being driven directly by a controller output rather than a power stage, so illumination confirms the controller powered, began executing and reached the point of driving that pin. Enumeration state was read write-blocked under strict timeouts behind the DeepSpar USB Stabilizer 10Gb, and the memory read at chip level past the controller with the translation layer reconstructed in software.
The outcome
The controller confirmed as executing, enumeration read under strict timeouts and the memory recovered past the controller. 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 decode: on an external hard drive an indicator usually reports only that power arrived. On a stick there is no room for separate circuitry, so the light is driven by the controller itself — meaning it powered up, started executing, and then failed to complete its introduction. Your memory is untouched behind it.
Stick with a working light that nothing detects
Mention that light when you ask, because on a flash drive it's genuinely informative. External hard drives usually wire their indicator to the power stage, so it lights because electricity arrived and nothing more — which is why lights are normally worth ignoring. A stick has no room for separate indicator circuitry, so on most designs the light is driven directly by a controller output, meaning the controller powered up, began executing its firmware and got as far as driving that pin. So the fault is after that, most often at the configuration read where it loads its capacity and addressing tables. Your data is untouched behind it. Stop trying more computers — the fault is internal and every one will answer the same.
That light is useful information — call Guildford Data Recovery on 01483 901310; enumeration read under strict timeouts, memory read at chip level past the controller, translation layer reconstructed in software.
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.