Data Recovery Case File · Mac & Apple Ecosystem · Two Failures, One Narrowing

It Did Not Come Back From the Upgrade

Her enquiry describes an older machine asked to do something it could not manage, and one clever attempt that did not work. A laptop that "has not coped with the upgrade to the new system and now will not start. It is an older machine that I had hoped to use purely for video calls, so did not have a lot of data on it — but now it is not there, I have realised that there are certain documents I would ideally need. I have exhausted support and have tried transferring the data via a direct cable, but this hasn't worked either." That second attempt was a good idea and its failure is informative, because of what it requires the machine to do.

The decode: why the upgrade did it, and what the cable attempt proves

Why an older machine fails an upgrade in this way: a major system upgrade replaces the operating system while the machine runs, then completes on restart. On hardware at the edge of what the new version supports, the failure typically comes at that final handover — a driver the new system expects and the hardware cannot provide, a firmware component that will not update, or an installation interrupted by a machine too slow to finish it in the window allowed. The result is a system that is neither the old one nor a working new one.

Why the data is very likely intact: an upgrade rewrites system files, not user files. Documents, photographs and downloads sit in their own area untouched by whatever went wrong with the system around them. This is a software failure wrapped around undamaged storage — which is the good category.

What the direct-cable attempt actually required, and why its failure narrows things: transferring between machines over a cable puts the failing machine into a special mode where it presents its internal storage as an external disk to the other computer. But entering that mode requires the machine to start up far enough to run it — its firmware must load, accept the key combination, and hand over. So the attempt failing means the machine is not reaching even that limited state, which is a lower-level failure than a system that boots and then stops. That is worth knowing: it says the problem is earlier than the operating system.

What that changes: it makes routes that depend on the machine functioning unpromising, and it points at reading the storage independently instead. On a machine of that generation the storage is a module that unclips from the board and reads on an inexpensive matched adapter, which takes the machine and its failed upgrade out of the question entirely.

The instruction that matters most: nothing should be reinstalled before the contents are captured. Support conversations end, reasonably enough, at reinstalling the system — and the reinstall path offers to erase the drive as part of it. Having exhausted support, that is the obvious next step and it is the one that would turn this into a loss.

On the documents: she needs a few specific ones rather than everything, which makes the job smaller — imaging can be sequenced to reach them first and confirmed before anything else is considered.

On the bench

No reinstall or repair was permitted before capture, since support avenues end at reinstalling and that path offers to erase the drive. The storage module was removed and read on a generation-matched adapter — the failed direct-cable attempt having already established that the machine could not reach even a limited host mode, which makes any route depending on it unpromising. It was imaged write-blocked independently of the machine, and imaging sequenced to the named documents.

The outcome

The storage read independently of the machine, imaged write-blocked and sequenced to the documents needed. 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, for anyone whose machine did not survive an upgrade: your files are very likely fine, because an upgrade rewrites system files rather than user ones. The direct-cable attempt failing is informative rather than discouraging — that mode needs the machine to start far enough to run it, so its failure places the problem earlier than the operating system. Don't reinstall before the contents are captured.

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.