Data Recovery Case File · Mac & Apple Ecosystem · Board Damage and the Order of Operations

Two wishes, one board: why data and repair compete on modern Macs — the liquid path decoded, the board-level route that can serve both, and the sequence that prevents a legitimate repair from erasing everything

His enquiry was two sentences carrying two hopes. A 16-inch MacBook Pro from 2020 that "has undergone some liquid damage. There is some damage to the main board according to Apple. I am hoping my data can be salvaged and my laptop fixed." Both hopes are entirely reasonable — and on this specific generation they are in tension, which is the single most useful thing this page can tell him. Because a 2020 16-inch stores its data on storage soldered to that same main board, encrypted by a security chip that also lives on it. So the conventional remedy for board damage — replace the board — is simultaneously the most complete data deletion available: the files leave in the old part. His two wishes can both be served, but only in one order, and only by a route that treats the damaged board as something to be repaired rather than exchanged. Below: what liquid does to a board of this design, the honest odds of the repair-for-data route, and where the limits are real.

The decode: what liquid does here, the repair-for-data route, and the order that protects him

Liquid on a modern board: a spill in a machine of this design does its damage in two waves. The immediate wave is electrical: liquid bridges circuits, current flows where it shouldn't, and protective components or power rails fail — which is what typically produces the total silence owners report. The slow wave is chemical: residues and corrosion continue eating traces, pads and component legs for as long as they remain, which is why time genuinely matters and why "it dried out, I'll deal with it later" is the most expensive sentence in liquid damage. Apple's finding of board damage is consistent with both waves having run. Importantly, it is a finding about the board — not a verdict on the storage, which on this generation is a passenger on that board and often entirely undamaged beneath a failure that is merely electrical.

Why repair-for-data is the only route that serves both wishes: because the keys are held by the security chip on the board, the data can only be released by the machine itself, running, against his own password. Therefore the recovery is a repair: corrosion cleaned, damaged rails and components restored at micro level, the board brought back far enough to boot and unlock. Where that succeeds, both his hopes are met at once — the data comes out complete, and the machine he wanted fixed is the very thing that was fixed to get it. Where it fails, the honesty must be equally complete: if the corrosion has reached the storage itself or the security chip, the data is beyond any lab's reach, because there is no chip-off fallback on this architecture and no honest way to break the encryption. That is why the work is staged: assessment first, corrosion mapped, findings written down, and his decision made on facts.

The order of operations, stated plainly: whatever he decides about the machine long-term, one sequence protects him and one destroys him. Data first, repair-by-replacement second. If a board swap is ever accepted — by Apple, by insurance, by anyone — the old board and its storage leave permanently, so every question about the data must be answered before that authorisation is given. His enquiry arriving before any replacement is the reason this case has a good ending available at all.

On the bench

The machine was opened and assessed before any commitment: the liquid's tracking mapped across the board, corrosion documented, the failed rails and components on the power side identified — and, crucially, the storage and security chip inspected and found clear of the damage path. The findings went to him in writing, with the route and its honest odds. The board was then cleaned and repaired at micro level, restored to operation, and the machine did the one thing only it can: unlocked its own soldered storage against his password. A complete image was taken immediately on the restored path, the volume verified, and his files checked by opening before delivery. Both wishes, in the only order that could grant either.

The outcome — and a repair that didn't erase anything

The data recovered by repairing the damaged board far enough for the machine to decrypt its own storage — verified and delivered — with the machine itself returned functional rather than exchanged. Staged assessment, findings in writing, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on success. The doctrine, posted for every owner of a liquid-damaged modern laptop: liquid damages boards electrically and then chemically, so speed matters and "it dried out" is not a plan; a manufacturer's finding of board damage is not a verdict on your storage, which usually rides out the failure intact; on soldered, encrypted machines the recovery is a board repair, because only the machine can release its own keys against your password; and a replacement board — however legitimate a repair — takes your data with it. Settle the data question before you authorise the part.

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.