Skip to content
macOSFix Published Updated 4 min readViews unavailable

Fixing a Mac Stuck on the Apple Logo or Stuck Rebooting

A Mac stuck on the Apple logo, or restarting in a loop, has a specific ordered set of causes — work through them from least to most invasive.

A Mac stuck on the Apple logo, or one that reboots repeatedly without ever reaching the desktop, is stuck somewhere in the macOS boot process — this works through the most common causes in order of how invasive the fix is.

Step 1: try a simple forced restart first

Hold the power button for 10 seconds, then power on normally.

A surprising fraction of boot-loop situations are resolved by nothing more than this — worth ruling out before anything more involved.

Step 2: boot into Safe Mode to rule out a third-party extension or login item

Apple Silicon: hold the power button until "Loading startup options"
               appears, select the volume, hold Shift, click
               "Continue in Safe Mode"
Intel Macs:    hold Shift immediately after powering on

Safe Mode disables non-essential kernel extensions, login items, and font caches — if the Mac boots successfully in Safe Mode but not normally, the cause is one of these, not a deeper system problem.

Step 3: check Disk Utility for a filesystem problem

Boot into Recovery Mode → Disk Utility → select the boot volume →
  First Aid

Apple Silicon: hold the power button until startup options appear, then choose Options → Continue. Intel: hold Cmd+R at startup. A filesystem-level problem on the boot volume is a common, directly fixable cause of a boot loop, and First Aid will report explicitly whether it found and fixed anything.

Step 4: check for a problematic login item or kernel extension, if Safe Mode fixed it

System Settings → General → Login Items

If Step 2 confirmed a third-party item is responsible, removing recently-added login items or kernel extensions (particularly ones added right before the problem started) one at a time isolates the specific culprit.

Step 5: reset NVRAM

Apple Silicon: NVRAM resets automatically as part of the startup
               security process — no manual key combination needed
Intel Macs:    hold Cmd+Option+P+R at startup until the second
               startup chime

NVRAM stores certain low-level settings (display resolution, startup disk selection, among others) that can occasionally cause boot problems when corrupted — see resetting NVRAM and SMC for the full walkthrough.

Step 6: reinstall macOS without erasing data, as a more invasive step

Boot into Recovery Mode → Reinstall macOS

This reinstalls the operating system over the existing installation, leaving user data and applications intact — a meaningfully more invasive step than the above, appropriate once simpler causes have been ruled out.

Step 7: check Console logs from Recovery Mode, if available

Recovery Mode → Utilities → Terminal →
  log show --last 1h --predicate 'eventType == "logout"'

Reviewing recent system logs (where accessible) can sometimes surface the specific error or panic responsible, narrowing down which of the steps above is actually most relevant rather than working through all of them blindly.

Why working through these in order matters

Each step here is progressively more invasive and time-consuming than the last — a forced restart costs nothing to try, while reinstalling macOS takes real time and, while non-destructive to data, is still a significant operation. Starting with Safe Mode specifically is valuable beyond just being non-invasive: it directly tells you whether the cause is a third-party addition (fixable by removing it) or something in the core system itself (requiring the more invasive steps further down this list).

Step 8: when nothing above works, revive the Mac from another machine

Apple Configurator 2 → connect the stuck Mac in DFU mode via USB-C →
  select the device → Actions → Advanced → Revive Device (or Restore, as a last resort)

For an Apple Silicon Mac too deeply stuck to reach even Recovery Mode, DFU (Device Firmware Update) mode provides a lower-level recovery path entirely separate from anything the stuck Mac’s own software needs to cooperate with — a second Mac running Apple Configurator 2, connected via USB-C while the stuck Mac is held in a specific button-and-cable sequence documented per model, can “revive” the firmware without touching user data, or as a last resort, fully restore the machine. This is meaningfully more invasive than reinstalling macOS from Recovery (Step 6) and generally reserved for cases where the Mac can’t even boot into Recovery Mode at all — a genuinely lower-level intervention than anything achievable from the stuck machine’s own keyboard.

Distinguishing a boot loop from a panic loop

A Mac that reaches the desktop briefly before crashing and restarting — rather than never getting past the Apple logo at all — is showing a genuinely different symptom: a kernel panic loop, where the actual panic report is the more direct diagnostic path than the boot-troubleshooting steps above, since the system is booting successfully but then crashing afterward rather than failing to boot in the first place. Confirming which of the two you’re actually facing — stuck before the desktop versus crashing shortly after reaching it — determines which of these two guides is the more directly useful starting point.

Related:

Sources:

Comments