Data Recovery Case File · Mac & Apple Systems · Nothing to Remove
On Machines With Soldered Storage, Not Caring About the Computer Does Not Help
Her enquiry separates the machine from the data, which is usually the right instinct and here does not apply. A laptop of a particular generation killed by a suspected power surge, where "I don't care much about the computer itself but the data inside is what's more worthy to me." On machines of that period the storage is soldered to the main board — so the dead board is not merely the machine, it is also the drive.
| Media | Laptop of a generation with storage soldered directly to the main board — board failure following a suspected supply surge; machine not powering |
| Reported situation | Suspected power surge affecting a laptop · main board reported as damaged · machine not powering on · content valued above the machine itself · owner currently outside the country · postal submission proposed · correspondence by email requested |
| Fault class | Board failure on a machine with integrated storage — memory not removable as a unit; recovery requiring board repair to a working state or reading of the memory in place |
| Equipment used | Storage architecture established from the machine generation before any expectation was set · board examined at component level under magnification with the affected supply stage identified · power stage repaired to a state sufficient for reading where components were recoverable · memory read in place past the controller where repair was not viable · encryption dependency established before any commitment |
The decode: what soldered storage changes, and the second complication
What machines of earlier generations allowed: removal. The drive was a separate module that could be taken out and read on other equipment, so a dead machine was an inconvenience rather than an obstacle.
What changed: storage became part of the board. Memory packages are soldered directly alongside the processor, with no connector and nothing to unplug.
Why that turns her situation around: the board she does not care about is the only thing holding her data. There is no drive to remove from a machine she is willing to abandon.
What follows for the work: one of two routes. Either the board is repaired far enough to read the storage, or the memory is read in place on the board itself.
Why repair is preferred where it is possible: it uses the machine's own controller. A board brought back far enough to power the storage returns content in its intended arrangement, which is considerably simpler.
Why a surge is a reasonable candidate for a repairable fault: such events damage the protective components first. Parts along the supply path are designed to fail before what sits behind them, and replacing them frequently restores function.
The second complication, and it must be raised before anything else: storage on these machines is encrypted by hardware. The encryption is tied to a security component on that same board, so reading the memory alone yields content nobody can interpret.
Why that changes the priority entirely: the board cannot simply be discarded. Its security component must remain intact and paired with the memory, which makes board repair the primary route rather than one of two.
Why that should be said before she posts anything: the honest position affects whether it is worth sending. A board whose security component has failed is not recoverable by anyone, and she deserves to know that in advance.
What is worth checking before any of it, and it costs nothing: whether the machine was backing up to a service or a drive. Content synchronised elsewhere is retrievable without touching the machine at all.
On the bench
Storage architecture was established from the machine generation before any expectation was set — earlier designs providing a removable module, later ones soldering memory packages directly alongside the processor with no connector, so a failed board is also the storage. Content on such machines is encrypted by hardware bound to a security component on the same board, so reading memory alone yields uninterpretable data. The power stage was repaired to a state sufficient for reading where components were recoverable.
The outcome
Storage architecture established before expectations were set, the affected supply stage identified at component level, and encryption dependency established before any commitment. 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 board you do not care about is holding your data. On this generation the storage is soldered to it and encrypted by a component on it — so repairing the board is the route rather than bypassing it.
A dead machine whose storage is part of the board
Check first whether anything was syncing to a cloud service or a backup drive, since that would be retrievable without touching the machine at all. Then understand why separating the computer from the data doesn't work here: on this generation the memory is soldered alongside the processor with nothing to unplug, and it's encrypted by hardware tied to a security component on that same board. So the board can't be discarded — it has to be repaired far enough to read the storage. A surge often damages protective components first, which are replaceable.
Check your backups first — call Manchester Data Recovery on 0161 871 0788; storage architecture established before expectations are set, supply stage identified at component level, encryption dependency established before commitment.
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.