Unable to update MacBook Pro M1 to macOS 15.4

This WORKED, even though a live Apple agent said it wouldn't.

How to revive or restore Mac firmware - Apple Support

You will need a USB-C to USB-C cable, and another Mac with a USB-C port that is already running Sequoia. The Apple agent said that the MBP that was giving me trouble wouldn't accept a macOS higher than what was installed, but it did. It took several attempts to get the Sequoia computer to see that I was trying to connect the MBP I was trying to upgrade. You know how it is when instructions say to hold a combination of keys for X number of seconds... it has to be exactly precise for the computer to interpret your command or it doesn't register. I found this video to help get me through it https://www.youtube.com/watch?v=q-FsB2onSx0 Just keep trying and eventually they will connect. When given the option to revive or restore, select restore. Expect status bars on both screens, and for the process to take at least several minutes.

IMPORTANT. I have no idea what info will be preserved or erased when you do this. I only know that after several hours of unsuccessfully trying to upgrade my factory reset 2021 MacBook Pro with M1 Max to Sequoia, this was the one thing that worked.

Other things to check to rule out hardware issues

• open Disk Utility and run First Aid on your internal drive
• Use Apple Diagnostics to test your Mac - Apple Support

I would also disconnect everything from both Macs except power (and the cable connecting them together, obviously), and internet I suppose if you have/need a physical connection; I used wifi (my wifi internet is strong and stable)

Good luck!

bucketofish wrote:

This WORKED, even though a live Apple agent said it wouldn't.

How to revive or restore Mac firmware - Apple Support

Just keep trying and eventually they will connect. When given the option to revive or restore, select restore. Expect status bars on both screens, and for the process to take at least several minutes.

IMPORTANT. I have no idea what info will be preserved or erased when you do this.

The "Revive" resets the security enclave chip & system firmware. Normally this won't affect any data on the internal SSD, but if the process fails to complete, then who knows if the data on the internal SSD can still be accessed.

The "Restore" does the same thing as the "Revive", but also resets the internal SSD thereby destroying all data on the internal SSD. The "Restore" also pushes a clean copy of macOS onto the internal SSD (I'm not sure what version of macOS is installed). The user will need to restore their data from a backup made prior to the DFU Firmware Restore process.

I am also in this situation But I have already resolved it

1. Prepare a normal Mac and download the app configurator from the App Store

2. The problematic computer enters DFU mode

3. Use app configurator to restore the system

I resolved this issue by downloading an intermediate version from https://www.iclarified.com/94896/where-to-download-macos-sequoia , such as 15.3.2. I first upgraded my macOS from 14.7.5 to 15.3.2, and then used Software Update in System Settings to successfully upgrade to 15.4. It seems the latest macOS 15.4 version is too new to upgrade directly from 14.7.5.

I experienced the same problem trying to up date my MBP M1 from MacOS 14.7.5 to MacOS 15.4 until today when I saw that Apple had released MacOS 15.4.1 and this worked for me. Hopefully it will be the answer for you and everyone else.

Related topic here: Kernel panic during Sequoia 15.4 installa… - Apple Community

Looks like this still isn't getting any actual recognition from Apple yet.

Has anyone managed to find a fix yet?

I have 5 M1 macs in my org that have this particular Issue.

Tried all of the following options (fixes) with no success:

• updating in Safe mode
• downloading the update via terminal: softwareupdate --fetch-full-installer --full-installer-version 15.4 (though I can confirm that the last stable update is: softwareupdate --fetch-full-installer --full-installer-version 15.3.2 and this does work
• reinstalling Rosetta
• disabling Docker from start up (https://forums.docker.com/t/docker-desktop-causing-kernel-panic-on-macos-15-4-developer-beta-1-apple-silicone/146811)

I spoke with Apple support who could only suggest the nuclear option of a wipe and reinstall of MacOS

I'm about to test this out How to revive or restore Mac firmware - Apple Support ....

15.4.1 fixed the issue for me.

With 15.4 had exactly same issues as all here, but the 15.4.1 just installed correctly 🥳

Mishmich wrote:

Cleared out space (300GB available).

Find My was not turned on.

Start of error log:

panic(cpu 0 caller 0x0): t6000dart 0xfffffdf034198d70 (dart-dispext0): Can't ignore lock validation @t6000dart.c:437

Debugger message: panic

Memory ID: 0x6

OS release type: Not set yet

OS version: Not set yet

Kernel version: Darwin Kernel Version 24.4.0: Wed Mar 19 21:16:34 PDT 2025; root:xnu-11417.101.15~1/RELEASE_ARM64_T6000

Fileset Kernelcache UUID: 64910CF20FBC3B619F5B9FEDE3E907C5

Kernel UUID: 0DBF4FC4-B7A0-303C-9143-63308FC1EA62

Boot session UUID: F441831E-AD36-4128-B453-40C434AA9830

iBoot version: iBoot-11881.101.1

iBoot Stage 2 version: iBoot-11881.101.1

secure boot?: YES

roots installed: 0

Paniclog version: 14

unplug all non-essential peripherals when testing...

reboot into SafeBoot mode and try again your update:

Start up your Mac in safe mode - Apple Support

Download it on another Mac or download a Sequoia installer from the internet (I personally don't recommend trying download it from the internet, because the source can be insecure) and make a bootable drive (like a pen): Create a bootable installer for macOS - Apple Support. If this don't work, consider doing a Time Machine backup and erasing the Mac.

Contact Apple , create case with them and escalate it.

Same here, 15.4.1 solved the issue.

Related topic is here: macOS 15.4 update failed on external disk - Apple Community