This page has been rewritten. The version published here on August 30, 2025 recommended a step that would have erased a reader’s disk, gave a key combination for buttons no Mac has, and printed two shell commands that aren’t real. Those claims are retracted below by name, not quietly deleted.
The worst first. The old version said that if recovery threw a “device is not booted” error, you should “click ‘Restore’ instead of other recovery options,” adding that “the restore process can proceed even when the device shows as ‘not booted’.” Restore erases the Mac. This page was recommending it as a way past an error message.
Revive and Restore are not two tries at the same thing
This is the distinction the old article got backwards, and the only thing here that really matters. Apple’s revive-or-restore page (published June 16, 2026) puts it in one line each.
| Operation | Apple’s wording | Your data |
|---|---|---|
| Revive | “Try reviving first. It can be faster than restoring, and it doesn’t erase your Mac.” | Kept |
| Restore | “Try reviving your Mac first. If your Mac can’t be revived, follow these steps to erase it and restore it to factory settings.” | Gone |
Revive refreshes firmware and recoveryOS and leaves the data volume alone — afterwards Apple’s steps ask you to “select the volume to recover (such as Macintosh HD)” and then for the login password of a user you know, which only makes sense because the account is still there. Restore returns the machine to factory settings.
The old version was wrong in both directions at once. It listed “Understanding that this process will erase all data on the target Mac” as a prerequisite for the whole procedure — false for Revive — then treated Restore as the natural next click on any error, which makes an irreversible erase sound like a retry button.
Apple Configurator is not the tool anymore
The whole premise of the old article is stale. “Configurator” appears zero times on Apple’s current revive-or-restore page — the flow runs through the Finder: “the Finder on the host Mac should show a DFU window. The DFU window shows ‘Mac’ selected in the sidebar and ‘Mac DFU Mode’ on the right.” You click Revive Mac, or Restore Mac if reviving failed. The old article’s “right-click context menu” and “Advanced Options” menu do not exist.
Apple Configurator still ships (2.20 is the version its user guide lists), but that guide no longer has a Mac in it. The word firmware appears zero times anywhere in it, and its contents offer to revive an iPhone, iPad, or Apple TV, and to restore an Apple Vision Pro. Reviving a Mac is not among them. The procedure moved out of Configurator; this article stayed behind, and so has most of what a search turns up.
What you need, per Apple
Every number the old version gave here was invented or wrong.
- Host Mac: “Another Mac of any model using macOS 14 or later.” The old text said “a second Mac running macOS Monterey (15.6) or later” — Monterey is macOS 12, and no 15.6 of it exists. That looks like a garbled copy of 10.15.6, which is Catalina.
- Free space: “32GB should be more than enough.” The old text said 10GB, unsourced.
- Cable: “A USB-C to USB-C cable that supports data and charging… Don’t use a Thunderbolt 3 cable.” The old text never mentioned the Thunderbolt exclusion — the detail most likely to waste your afternoon.
- Models: “Other Mac models don’t apply” — it’s Apple silicon and T2 only. The old FAQ asked “Is Apple Configurator recovery method safe for all Mac models?” and answered “Yes.” It is not.
A Mac has no volume buttons
The old article instructed: “Press and hold Power + Volume Down + Volume Up for 10 seconds.” That’s an iPhone and iPad procedure. Macs have no volume buttons, and “Volume” appears zero times in Apple’s DFU steps.
On a laptop, Apple’s sequence is to hold power until the Mac turns off, then press and release power and “immediately press and hold all four of these together on the built-in keyboard” — Control ⌃ on the left, Option ⌥ on the left, Shift ⇧ on the right, and power. Apple silicon: hold all four ~10 seconds, release all but power, keep holding power up to 10 more seconds until the DFU window appears. T2: hold all four ~3 seconds. The handedness of those modifiers is load-bearing.
On a desktop — Mac Studio, Mac mini, Mac Pro, iMac — there’s no key combination at all: “Unplug the Mac from power. Press and hold the power button. Keep holding the power button while plugging the Mac into power, and continue holding it for up to 10 seconds, until the host Mac shows a DFU window in the Finder. If it first shows an alert asking you to allow the accessory to connect, release the power button and click Allow.” The trigger is the power cycle, not the USB-C connection. The old “Hold power button for 10 seconds while connecting USB-C” was invented whole.
And the old opening move, “Hold the power button for 10 seconds, then release,” was called DFU entry. It’s a forced shutdown — Apple describes the same gesture as “Press and hold the power (Touch ID) button for up to 10 seconds, until the Mac turns off.”
Two commands this page made up
The old article offered a block of post-recovery “system health verification” commands. Two don’t exist. Nonexistent paths are used below so nothing could be copied if the flag had parsed:
$ ditto --check /nonexistent-osxhub-a /nonexistent-osxhub-b
ditto: unrecognized option `--check'
Usage: ditto [ <options> ] src [ ... src ] dst
$ man ditto | grep -c -- --check
0
$ man diskutil | grep -ci resetUserPermissions
0On macOS 26.5.2 (build 25F84), ditto rejects --check at the argument parser, and the string never appears in its man page. The old sudo ditto --check /System/Library never checked anything. diskutil has no resetUserPermissions verb either. The old article also passed it `whoami`, a user name, where the historical syntax took a numeric UID — wrong twice over about a command that isn’t there.
Everything else being retracted
- “Touch ID and Face ID data require complete re-enrollment” — no Mac has Face ID. And “try resetting the SMC (System Management Controller) on both devices” — Apple silicon Macs have no SMC reset.
- “Run Apple Diagnostics by holding D during startup” — Apple files D under “Key combinations for an Intel-based Mac”. On Apple silicon you hold power for startup options. It also contradicted our own diagnostics article, which has it right.
- “Recovery process requires disabling Secure Boot temporarily” and “All security certificates and encryption keys are regenerated” — neither appears in Apple’s documentation.
defaults write com.apple.TimeMachine DoNotOfferNewDisksForBackup -bool YES, captioned “Set up additional cloud backup verification” — that key suppresses the prompt offering newly attached disks as backup destinations. Nothing to do with cloud backup.- “Try Target Disk Mode to access files from another Mac” — Apple describes it as connecting “an Intel-based Mac to another Mac.” Intel only; this page is about Apple silicon and T2.
- Two fabricated “case studies,” one with “Total recovery time: 90 minutes”; the 60–120 minute estimate; “30-50% of the total time”; “within 30 seconds”; eight FAQ entries written to fill space; and two links that 404,
support.apple.com/mac-recoveryandsupport.apple.com/time-machine(checked 2026-07-17).
Where to stop
Revive should always be first: it doesn’t erase, and if it works the Mac restarts and asks for a password that still exists. If Revive doesn’t fix it, the next click costs you the disk — that’s the moment to stop and get the data off, not to push through an error message. There is no recovery path out of a Restore.
If the DFU window never appears in the Finder, none of this applies yet — the problem is the cable, the port, or power, and Apple keeps a “Don’t see the DFU window?” branch on the same page for that. And if the machine is under warranty, a firmware failure this severe is a reasonable thing to hand to Apple.
Sources: How to revive or restore Mac firmware (Apple, June 16, 2026), Mac startup key combinations, and the Apple Configurator User Guide. Command behavior checked on macOS 26.5.2 (build 25F84), arm64.