Data Recovery Case File · Solid State & Flash · The Record and the Damage Share a Cause
A Device Destroyed by the Event It Was Recording Still Holds What It Wrote Beforehand
His enquiry concerns a small device whose contents matter more than its condition. A cycling computer "crushed in an accident" where he needs "the detail of the ride that caused the damage", which no longer takes power and can normally be read either wirelessly or as a connected drive. The recording and the destruction have the same cause, and the question is whether the writing finished before the crushing did.
| Media | Cycling computer with internal solid-state storage — housing crushed in an impact; device not accepting power; wireless and connected access routes both unavailable |
| Reported situation | Cycling computer recording a ride · device crushed during an accident on that ride · device no longer taking power when connected · wireless synchronisation unavailable · file access over connection unavailable · record of the ride required |
| Fault class | Physical destruction of housing and board with memory package unimplicated — activity file possibly unfinalised at the moment of impact; chip-level access indicated |
| Equipment used | Memory package condition assessed independently of housing and board damage · no power applied to a crushed board · board examined at component level under magnification · memory read at chip level directly from the package · activity file structure reconstructed and unfinalised records recovered from the raw stream |
The decode: what survives a crushing, and whether the record was finished
What is in a device like this: a small board carrying a processor, sensors, a battery and a memory package. The memory is a sealed component and it holds content without power.
Why crushing damages the board more readily than the memory: the board is large, thin and populated with connections. The memory package is small, solid and mechanically robust, so an impact that destroys the board frequently leaves it intact.
Why it not taking power is expected rather than discouraging: the power path is exactly what a crushing interrupts. A fractured board cannot deliver current to anything, and that tells us nothing about the memory behind it.
Why neither of his normal routes can work: both require the device to run. Wireless synchronisation and file access over a connection are functions of the processor, and a board that cannot power its processor offers neither.
What is done instead: the memory package is read directly, bypassing board, processor and connector entirely. The stored content is addressed at chip level and reconstructed in software.
The substantive question, and it is about timing: whether the activity record was written continuously or held and saved at the end. Devices of this kind generally write as they go, appending records at intervals, which is what makes this recoverable at all.
Why that matters so much here: a device saving only on completion would hold nothing, because the ride never completed. Incremental writing means the record exists up to the moment of impact.
What is likely to be missing: the closing structure. An activity file finalised at the end of a ride never received that step, so the file is present without its summary and may not open in ordinary software.
Why that is a reconstruction rather than a loss: the records themselves are intact. Position, speed and time entries can be read from the raw stream and reassembled into a complete file, including the final seconds.
Why those final seconds are the point: he needs what the ride was doing when it ended. The last records written are the ones closest to the event, and they are the least likely to have been finalised and the most likely to matter.
On the bench
Memory package condition was assessed independently of housing and board damage — the memory being a small, solid, mechanically robust sealed component holding content without power, while the board is thin, populated and readily fractured, so failure to take power reflects an interrupted supply path rather than memory condition. Wireless and connected access both require a running processor. Devices of this type append activity records incrementally, so unfinalised records were recovered from the raw stream.
The outcome
Memory assessed independently of board damage, no power applied to a fractured board, and the activity record reconstructed from the raw stream including unfinalised entries. 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: the crushing took the board and the memory is a different component. Devices like this write as they ride rather than saving at the end — so the record exists up to the impact.
A recording device destroyed by the event it recorded
Don't try to power it, and don't attempt to straighten or open a crushed housing. The memory is a small sealed component that holds content without power and survives impacts the board doesn't, so failing to take power says nothing about what's stored — it means the supply path is fractured. Devices like this append records as they go rather than saving at the end, which is why the ride up to the impact exists. Expect the file to need reconstructing, since it never received its closing structure.
Don't power it — call Manchester Data Recovery on 0161 871 0788; memory assessed independently of board damage, read at chip level, unfinalised records reconstructed from the raw stream.
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.