Data Recovery Case File · Mac & Apple Systems · One Fact Changes Everything
Between Two Model Years Sits the Difference Between Routine and Impossible
His enquiry contains an uncertainty worth resolving before anything else. A laptop made inoperable by liquid, where he believes it is a particular model year and offers to "double check." That detail is not incidental: within a couple of years either side of it, machines changed from having removable storage to having storage soldered to the board and encrypted to a security component — and the answer differs completely on each side.
| Media | Laptop rendered inoperable by liquid exposure — storage architecture dependent on model generation; removability and key location determinative |
| Reported situation | Laptop sustaining liquid damage · machine inoperable · model year believed known but not confirmed · owner able to verify the model · content required · cost and feasibility sought |
| Fault class | Liquid damage with outcome governed by storage architecture — removable storage recoverable independently; soldered storage encrypted to board hardware recoverable only through board restoration |
| Equipment used | Model generation established before any approach was chosen · powering stopped and board cleaned before assessment · storage removed and read independently where the generation permitted · board restoration pursued where storage was soldered and key-bound · realistic position stated before any commitment |
The decode: the two situations, and how to tell which he is in
Why one fact carries so much weight: the machines look alike and behave differently. Externally identical models a few years apart have entirely different storage arrangements, and nothing about the appearance indicates which.
The earlier arrangement, and it is the good case: storage on a removable module. The module comes out and is read on a matched adapter, independently of the machine — so liquid damage to the board is irrelevant to the data, and this becomes an ordinary transfer.
The later arrangement, and it is the difficult one: storage soldered directly to the main board, with content encrypted at rest and the key held in a dedicated security component on that same board. There is nothing to remove, and the memory alone yields data nobody can interpret.
Why liquid is particularly unkind in the second case: the data's fate is tied to the board's. Damage that would merely destroy a machine in the earlier arrangement can destroy the data in the later one, because the component holding the key is on the damaged board.
What follows for the work: in the earlier case the objective is the module; in the later case it is restoring the board sufficiently to export normally. Those are different jobs with different costs and different odds, which is why a figure cannot honestly be quoted before the model is known.
Why the later case is not automatically hopeless: liquid damage is frequently confined to corrosion on specific areas. Cleaning and component-level repair restore many boards to working order, and a machine made to run exports its content in the ordinary way with everything decrypted as it always was.
Why that route is preferable even where storage is removable: a working machine returns everything in its normal arrangement. It is the best outcome in both cases, and it is attempted first regardless.
What matters more than the model right now: that the machine is not powered. Corrosion requires moisture, contaminants and an electrical potential together, and the liquid supplied the first two permanently while every attempt to switch it on supplies the third.
Why that is urgent in a way the model question is not: the model does not change while he checks it. The corrosion does, and a device left unpowered corrodes slowly where a device being tested corrodes fast.
What is worth doing in the meantime: checking whether any backup exists in an account or on another machine. That would end the question entirely, and it costs nothing.
On the bench
Model generation was established before any approach was chosen — externally similar machines a few years apart carrying entirely different storage arrangements, the earlier holding storage on a removable module readable independently of the machine, the later soldering storage to the main board with content encrypted at rest and the key held in a security component on that same board, so memory alone yields uninterpretable data. Powering was stopped and the board cleaned before assessment.
The outcome
Model generation established before any approach was chosen, powering stopped and the board cleaned, and board restoration pursued where storage was soldered. 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 model year is the question. Either your storage comes out and reads on its own, or it is soldered to the board with its key on that same board — and the answer differs completely.
Liquid damage to a laptop, before you ask what it will cost
Stop trying to power it, which matters more urgently than anything else — corrosion needs moisture, contaminants and a voltage together, and the liquid supplied two permanently while every attempt to switch on supplies the third. Then find the exact model, because externally similar machines a few years apart differ completely: older ones hold storage on a removable module that reads independently of the board, while newer ones solder it down and encrypt it to a security component on that same board. In the second case the data's fate is tied to the board's, so cleaning and repair become the route rather than a preliminary.
Stop powering it and check the model — call Manchester Data Recovery on 0161 871 0788; model generation established before any approach is chosen, board cleaned before assessment, realistic position given 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.