Unable to install macOS Sequoia update 15.4 on my MacBook Pro

Good morning. If it's not difficult, share the way that allowed you to restore the mac? I don't have a second mac, I only have a laptop on Windows.

Update to MacOS Sequoia 15.4.1

HTH

I’m having this exact same problem now with my M1 Studio. Did you find a working solution in the comments here by chance ?

Has SIP ( System Integrity Protection ) been disabled

To check if System Integrity Protection (SIP) is enabled or disabled on your macOS, open Terminal and type csrutil status then press Enter. The Terminal will then display whether SIP is "enabled" or "disabled". 

% csrutil status

System Integrity Protection status: enabled.

Same , had to reinstall to a different volume and move all the data.

Thankfully it s much easier these days with lots of cloud based app , just a few config files and I was all set .

Still pretty ****** at Apple , lost abt 2 days and I m still not running 15.4

I just found this relative to the Beta for 15.4 (seems like this problem was present for some even during beta). At that time the solution was perceived to be a DFU restore was the only solution. It comes from this Reddit website (you have to scroll down load more comments to get to it): https://www.reddit.com/r/MacOSBeta/comments/1j2q230/154_developer_beta_2_released/?rdt=62051

The original Post and response was in Portuguese (this is translation):

I installed 15.4 Beta via the Beta Development Version on my external HD. It worked, but when I turned it off and booted from the internal HD with 15.3.1. The installation was corrupted. I cleaned the disk with Recover Sonoma, but now the Mac no longer accepts the installation of version 15.3.1. It always crashes and stays in a loop...I can only install 15.4 when this is only the Beta Development version on both the internal and external disks. Now when I try to update it always crashes with this LOG:

panic(cpu 0 caller 0x0): t6000dart 0xfffffdf03f8c2850 (dart-disp0): Can't ignore lock validation u/t6000dart.c:437

Reply #1:

Hi, I’m going through the same issue. I guess you haven’t found a solution other than DFU restore either, right?

Reply #2:

Unfortunately not, only restoring via DFU. After I restored everything worked normally.

Having the same problem. That bricked my m1 mba. It says the version of macOS on the selected disk needs to be reinstalled. Then I went into recovery mode and reinstalled macOS sequoia. After it did the install and want to reboot I just get the same message again. I can’t recover my M1 MBA.

@edward

Edward Martz wrote:

This morning, I contacted Apple Support to continue troubleshooting after backing up my important documents. I explained the steps I had taken and shared insights I found online from the apple forum. They informed me that I would need access to another Sequoia Mac in order to attempt further recovery methods. Unfortunately, my only remaining option would be to wipe and reinstall, although they cautioned that this might not resolve the issue, as the M-series chips don’t allow downgrades.

As an alternative, they recommended scheduling a Genius Bar appointment, where they would have the necessary tools to explore additional recovery options before resorting to a clean install. I’m heading in this afternoon to see if any progress can be made before taking that final step.a

Likely you can install Sonoma on a different partition of the disk ( volume) then you will see your files/datas and move them over ( external or the new install ).

Then that new Sonoma installation can be updated up to 15.3.2.

At this stage , you can delete the faulty partition to reclaim the space back.

A few days ago the App Store had 15.3.2 as the "current" Sequoia OS. I downloaded that and ran it. It resulted in the same failure that I was getting from the "Software Update" in "System Settings".

Can you test a system on 15.3.2 using LittlebigalanCM's sudo command below:

sudo softwareupdate --fetch-full-installer --full-installer-version 15.4 --launch-installer -R

I've run it successfully on an already erased mac (M1 Pro) without issue, just curious as to the result on a machine already getting crash reports or with a user who doesn't want to wipe their device until the next incremental is released.

Does the command you used work from the “Terminal” app in “Recovery” mode?(It works in the terminal app in safe mode).

I tried it in “Recovery” but it kept giving me an error and wouldn’t execute the command. This is what I was using.

sudo softwareupdate --fetch-full-installer --full-installer-version 15.4 --launch-installer -R

Any ideas?

I haven't been able to get it to work from the terminal within recovery mode. I am trying some things to see if there is something that works for recovery mode as my company has a few devices that we need to reinstall the OS on.

Hello, widohmakr. DFU restore DOES work, revive no bueno + your other troubleshooting efforts mentioned. However, working towards a temporary workaround for end users NOT wanting to wipe out their current profile, environment, development setup, etc. even if a backup is/isn't available. Thoughts?

That's odd you weren't able to fetch the full installer via the terminal command. Worked for me earlier:

sudo softwareupdate --fetch-full-installer --full-installer-version 15.4 --launch-installer -R

Hi darrieus179. The 'fetch full installer' terminal command did not work for me. Have no idea why. Could have been a glitch with the servers that day. Honestly, I would bear the cost of the DFU restore. It's so quick. The troubleshooting route ends up costing way more in time. You can still do a Time Machine restore after. I've faced issues with clean installs on every major MacOS release since the 2021 MBP redesign was released. I'm glad to see the base recovery image/software be updated as well.

Thought it was just me but it seems it's the same problem for everyone else. Tried everything to 'upgrade' from Sonoma to Sequoia on my MacBook Air M1 but although it goes through all the motions of seemingly installing Sequoia it always ends up with Sonoma. Have tried installing from the update in software updates, from the full app and also from a USB stick. All fail. A waste of time and I think having read some horror stories in this thread that it really is not worth persevering in case I brick the laptop. Apple needs to do something about this and PDQ.