Data Recovery Case File · Mac & Apple Ecosystem · One Keeps Your Data
The Two Options in Apple Configurator
His enquiry described a machine that died between one evening and the next morning, and an attempt to save it. A 14-inch MacBook Pro from 2021: "It was working fine last night. It had downloaded a system update — don't know if it installed — but this morning it was not turning on. I charged it till it was green, still nothing. I attempted the revive through Apple Configurator but it didn't recognise it, and since then the charging light didn't come on either." He then took it to a local specialist. Everything he did was reasonable, and one detail deserves a warning for anybody about to follow the same path: the tool he reached for offers two operations that sound almost identical, and only one of them preserves your data.
| Media | 14-inch MacBook Pro (2021) with soldered, hardware-encrypted storage — failure to power on following an overnight system update; firmware revive attempted without recognition |
| Reported situation | Machine functioning normally before an overnight update · failure to power on the following morning · charging to full indication without response · firmware revive attempted without the machine being recognised · charging indication subsequently absent · assessed locally |
| Fault class | Board-side failure following an interrupted or failed firmware update — storage soldered and cryptographically bound; recovery contingent on restoring board function |
| Equipment used | No erase performed or advised · board assessed to distinguish power-side failure from storage or security-chip damage · micro-level repair to restore operation sufficient to unlock against the owner's credential · imaging on restored access |
The decode: the two operations, and what the update probably did
Revive versus restore, which is the whole warning: Apple's configuration tool offers both for a machine that will not start, and the names do not signal the difference. Revive reinstalls the firmware and the lowest-level system software while leaving the user data volume untouched — it is the one to attempt, and attempting it is not risky. Restore reinstalls the firmware and erases the internal storage completely, returning the machine to factory condition. On a Mac of this generation an erase is a cryptographic operation: the key protecting the data is discarded, after which everything remaining is mathematically meaningless, permanently, for anyone. He chose correctly. A great many people, having found that revive did not work, go on to try restore because it appears to be the next step — and that is the moment the data ends.
What an overnight update failure looks like: a machine that downloads an update and dies before the next morning has very likely failed during the installation. Firmware updates write to low-level storage on the board, and an interruption — a power event, a fault, a bad write — can leave a machine unable to complete its own start-up. That is consistent with everything he describes and it is precisely what a revive is designed to address.
Why the machine was not recognised: the revive process requires the machine to enter a specific low-level mode, which needs a working connection, the correct port, a data-capable cable and a precise key sequence. It also requires enough of the board to be functioning to respond at all. So "not recognised" may mean the procedure did not take, or it may mean the fault is deeper than firmware. Those are worth separating rather than concluding from one attempt.
The charging light going out afterwards: worth reporting and not over-interpreting. It may indicate the board's state changed during the attempt, or simply that a different power negotiation is now happening. It is a data point for a board assessment rather than a verdict.
What the generation means: storage is soldered to the board and encrypted with keys held in a security chip on it. There is no drive to remove. So the route is repairing the board far enough for the machine to run and unlock against his own password, then imaging immediately — and, critically, never allowing a board replacement, which discards the keys and the data with them.
On the bench
No erase was performed and none was advised, since the destructive option is the one that ends the matter permanently on this generation. The board was assessed to distinguish a power-side failure — with storage and security chip intact — from damage to the storage packages or the chip itself, because that determination decides whether a recovery exists rather than how difficult it is. Repair proceeded at micro level with the objective of making the machine run and unlock rather than restoring a fully working laptop, and imaging began immediately on that access against his own credential.
The outcome
The board assessed and repaired far enough to unlock, with the data imaged on that access and no erase performed. Staged assessment with findings in writing, 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, for anyone whose Mac died after an update: the recovery tool offers two operations whose names do not signal the difference — revive reinstalls firmware and leaves your data alone, while restore erases the storage completely and, on these machines, discards the encryption key permanently; attempt revive, and do not progress to restore when it fails; a machine that dies overnight after downloading an update has probably failed during installation, which is exactly what revive addresses; and never allow a logic board replacement while the data matters.
Mac that won't start after an update
Try revive, and stop there — do not move on to restore. Apple's configuration tool offers both, the names give you no clue which is which, and the difference is everything: revive reinstalls the firmware and leaves your data volume alone, while restore erases the internal storage completely. On any Mac from roughly 2018 onwards that erase discards the key protecting your data, so nothing is recoverable afterwards by anyone at any price. The trap is that restore looks like the logical next step when revive doesn't work. If revive fails, that's the point to stop and get the board assessed rather than escalate. Make sure you're using a data-capable cable in the correct port before concluding anything, since a failed revive often means the procedure didn't take. And never authorise a logic board replacement while your data still matters.
Don't try restore — call Glasgow Data Recovery on 0141 404 0294; board assessed to separate a power fault from chip damage, repaired to unlock rather than to restore, imaged immediately.
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.