Data Recovery Case File · Solid State & Flash · A Fault Travels Along the Connection
Whatever Reached the Board May Have Reached the Drive as Well
His enquiry describes a machine destroyed by something plugged into it. A laptop "turned into a brick by plugging it into a docking station", assessed by a repairer as having a failed board and further damaged components, after which he "put the drive in an enclosure to try to recover the data — no luck." Removing the drive was the right move, and the enclosure showing nothing does not establish that the drive is finished.
| Media | 128GB solid-state drive removed from a laptop damaged by an attached docking accessory — not presenting through an external enclosure |
| Reported situation | Laptop ceasing to function on connection to a docking accessory · repairer reporting board failure and further damaged components · drive removed by the owner · drive placed in an external enclosure · no result obtained · contents required |
| Fault class | Possible electrical damage propagated through shared supply — drive not enumerating through an enclosure; controller condition to be established independently |
| Equipment used | Enclosure result interpreted as absence of enumeration rather than absence of data · propagation of the electrical event assessed across board and drive · current-limited assessment on a controlled bench supply · controller state assessed in vendor technological modes · chip-level read past the controller with translation layer reconstructed in software |
The decode: how far the damage travelled, and what the enclosure proved
What a docking accessory does electrically: it supplies power to the machine and carries data between them. A fault in that accessory can deliver voltage the laptop was not built to accept, and it arrives on the connection every internal component ultimately shares.
Why the damage was not confined to one part: the repairer found the board failed and other components damaged too. An over-voltage event follows the supply wherever it goes, which is why these failures are rarely tidy — and it is the reason the drive has to be treated as possibly affected rather than assumed intact.
Why removing the drive was nevertheless correct: it separates the question. The machine's condition has been established and is not recoverable in any useful sense, so the only remaining question is what the drive holds — and that is answered away from the laptop.
What the enclosure result actually establishes: that the drive is not presenting itself. An enclosure converts a connection; it does not make a silent device speak — so no result means the drive did not complete its introduction, and nothing more specific than that.
Why that is not the same as the drive being finished: a controller that cannot complete its start-up produces exactly this outcome, and the memory behind it is a separate component. The great majority of solid-state recoveries begin from precisely this symptom — a device that appears nowhere.
What the specific possibilities are: the drive's own supply stage damaged by the same event, leaving the memory untouched; the controller damaged, with the memory again untouched; or the memory itself affected, which is the least likely and the only genuinely bad case.
Why the first two are far more common: the supply stage and controller sit between the incoming power and the memory. They are what an electrical event reaches first, and they frequently fail in a way that protects what is behind them — which is the same reason a drive killed by a supply fault usually keeps its data.
Why the assessment must not repeat what he did: connecting a possibly-shorted drive to an ordinary enclosure applies power without limiting it. Where a fault path exists, that is current flowing through damage, so the drive is assessed on a supply that limits current and reveals the draw rather than one that simply delivers it.
What must not happen: no further enclosure attempts, and no trying other adapters. Each is the same test with the same result and a further application of power to a drive that may be shorted.
On the bench
The enclosure result was interpreted as absence of enumeration rather than absence of data — an enclosure converting the connection without enabling a device that cannot complete its introduction to present itself, so no result indicates failed enumeration only. Propagation of the electrical event was assessed across board and drive, an over-voltage arriving via a docking accessory following the shared supply, with the drive's supply stage and controller lying between incoming power and memory and commonly failing in a manner that leaves stored content unaffected. Chip-level reading was performed past the controller.
The outcome
The enclosure result read as absence of enumeration, propagation assessed across board and drive, and the memory read 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: pulling the drive was right, and the enclosure showing nothing only means it did not introduce itself. The supply stage and controller sit between the incoming fault and your memory, and they are usually what absorbs it.
A drive pulled from a machine killed by an accessory
Stop trying enclosures and adapters — each one repeats the same test and applies power again to a drive that may be shorted. Removing it was the right move, since the machine's condition is settled and the only remaining question is what the drive holds. But an enclosure only converts a connection; it can't make a device that failed to introduce itself speak, so no result means failed enumeration rather than lost data. A fault delivered through a docking accessory follows the shared supply, and the drive's own supply stage and controller sit between that and the memory — which is usually what absorbs it.
Stop trying enclosures — call Easy Data Recovery on 028 9002 0144; enclosure result read as absence of enumeration, assessed on a current-limited bench supply, memory read past the controller.
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.