Cannot upgrade MacOS due to Firmware in MBP M2 Max

I got this MBP M2 Max in 2023 which came with Ventura 13.0 and honestly never checked if updates were successful because I trusted they were correctly applied overnight. But one time due to an app incompatibility I found out that it never updated anything. This was after the warranty expired, of course.


Any attempt to upgrade, via UI, softwareupdate CLI, full installers, App Store, recovery pendrive and so on, just restarted the computer without any change.


I backed up everything (sadly not sticky notes which later I found out are not sync'd!) and tried DFU revive with another MBP using Sequoia 15.6 and the Finder app, a process that died half way, then freaked out because I thought I bricked the device getting the dreadful error 21 repeatedly...


But after 3 or 4 DFU (full) restore attempts, I was able to finally install Sequoia 15.6. I'm not sure if it was the repeated attempts or getting the exact key combination and timings right with the blank screen and no feedback whatsoever, as the faulty MBP showed up in the other computer's Finder EVEN when it didn't seem to be correctly set in DFU mode... But in the end I was able to do it, checked the firmware at System Information and it's OK. I hope this brings some light at the end of the tunnel for all my fellow users suffering from install issues.


I thought that was it, I'm on the clear, but when the 15.6.1 critical security update came out I was in the same rut, couldn't upgrade at all. And now I can't upgrade to Tahoe (26) neither.


Reading the installer logs it's obvious there is almost no attention to the user experience from Apple anymore, seems like they don't even test things on their own relatively small set of hardware, as the install.log file is plastered with a lot of failures from badly written javascripts trying to install Intel stuff on Apple Silicon computer:

TypeError: null is not an object (evaluating 'cpuFeatures.split') at x-distribution:///installer-gui-script%5B1%5D/installation-check%5B1%5D/@script


After countless wasted hours I thought this was the problem, but upon further investigation I pinpointed the exact issue. It seems there is a problem writing the the firmware hardware from the installer, which seems to make upgrades only possible through DFU. This is the error

softwareupdated[737]: Apply failed with: Error Domain=SUMacControllerError Code=7760 "[SUMacControllerErrorApplyFailed=7760] Failed to perform Apply operation: [MobileSoftwareUpdateErrorDomain(MSU):1041_1_RamrodErrorDomain:1014_2_MSUFirmwareUpdaterErrorDomain:3_3_MSUFirmwareUpdaterErrorDomain:-536870167]" UserInfo={NSLocalizedDescription=Failed to apply the software update. Please try again., SUMacControllerErrorIndicationsMask=0, NSDebugDescription=[SUMacControllerErrorApplyFailed=7760] Failed to perform Apply operation: [MobileSoftwareUpdateErrorDomain(MSU):1041_1_RamrodErrorDomain:1014_2_MSUFirmwareUpdaterErrorDomain:3_3_MSUFirmwareUpdaterErrorDomain:-536870167], NSUnderlyingError=0x5b258dce0 {Error Domain=MobileSoftwareUpdateErrorDomain Code=1041 "failed to perform limited firmware update" UserInfo={NSUnderlyingError=0x5b258c780 {Error Domain=RamrodErrorDomain Code=1014 "update_iBoot: BootFirmware update failed" UserInfo={NSDescription=update_iBoot: BootFirmware update failed, NSUnderlyingError=0x5b258d1d0 {Error Domain=MSUFirmwareUpdaterErrorDomain Code=3 "Updater <IODualSPIWriter: 0x600013c91f40> failed to write to SPI" UserInfo=0x5b0a72c00 (not displayed)}}}, NSLocalizedDescription=failed to perform limited firmware update, target_update=24G90}}}

Cleaning up the error stack a bit:

  1. MobileSoftwareUpdateErrorDomain Code=1041 "failed to perform limited firmware update"
  2. RamrodErrorDomain Code=1014 "update_iBoot: BootFirmware update failed"
  3. update_iBoot: BootFirmware update failed
  4. MSUFirmwareUpdaterErrorDomain Code=3 "Updater <IODualSPIWriter: > failed to write to SPI
  5. failed to perform limited firmware update, target_update=24G90


This happens EVERY TIME.


Here I'm guessing SPI means Serial Peripheral Interface, a way to communicate hardware, which has a problem. Everything points to a hardware malfunction or bad design, which is never checked/reported correctly to the non-engineer user base until it's too late and you have to pay 1k to change the logic board, but on the other hand I was able to upgrade through DFU so it could theoretically be just bad update software.


Will I need to wipe everything and DFU restore/reinstall from backups on each important update?

Will Apple ever develop a reliable upgrade procedure?


I bought a Mac to make my life easier but this issue is turning it into a PITA to use. Now every time I use it I have to be either afraid I'll be hacked from not upgrading or I'm afraid that if I do another DFU it will brick my 3k investment. Pathetic.


Related closed question with the same issue:

Failed to install macOS Monterey to 2020 … - Apple Community


MacBook Pro 14″, macOS 15.6

Posted on Sep 26, 2025 4:57 AM

Reply
7 replies

Sep 26, 2025 9:13 PM in response to 2bam

2bam wrote:

Or maybe they're underreported? Without internal apple support/returns numbers it's impossible to assert.

What I can do, from all the visibly cases I do see reported without solution or even a valid explanation, is make the decision to not play "problem roulette" again.

People only post here when they have problems. So most everything eventually shows up. Also, my workplace has about 3000 Macs in use, most are laptops, and most of those are MacBook Pros (versus MacBook Airs). I have never seen there what you are reporting, and I monitor our Slack channel for Apple and Mac products. Which makes me think you have a laptop with a faulty chip and that such failures are rare.


Applecare+ extends the warranty, indefinitely if you choose.


It might be interesting to see what Silent Knight reports. But I agree with Mac Jim D, take the laptop to Apple for service.

Sep 26, 2025 9:33 PM in response to 2bam

A full restore using the second Mac running Apple Configurator should completely erase and redo the internal SSD. Put the broken Mac into DFU Mode and install Apple Configurator on the good Mac. Be sure you are using Thunderbolt cables as the USB-C charging cables are not sufficient. Once the bad Mac shows up in Apple Configurator then you can restore macOS to the latest Tahoe 26 version.


Correction: It appears that Apple did add a Revive / Restore option to Finder when a 2nd Mac is in DFU Mode. I would still use Apple Configurator App instead of the Finder.


If you wish to use an older macOS version, you'll need to download an IPSW file for that version. By default the latest macOS release will be selected.


The utility below by Eclecticlight.co - Mac blog will check your firmware and update it. In years past there were issues with some Macs not receiving appropriate firmware updates. Try this utility.

SilentKnight 2.12 (Universal App for Big Sur to Tahoe)


It looks like this: (secure boot and kernel extensions are due to Enterprise managed Mac)



[Edited by Moderator]

Sep 26, 2025 6:52 AM in response to 2bam

dialabrain is correct, for the very few reported cases of an upgrade problem with the millions of devices in existence, you need to look more closely at another issue such as third party conflicts, or hardware problem. No, we do not see things underreported here, in fact, even a small issue such as people not liking the caps lock indicator gets overblown.


No need to attempt to read log files yourself, nowadays that is just a not as useful as it once was. You may remember a time when they only reported a problem that needed to be addressed, back when computers had low CPU speeds, limited RAM and storage. Now there are thousands of logs constantly being produced and older logs automatically deleted. You also see logs with a failed message that are expected, just to tell the engineer a branch occurred like it was supposed to do. The only use for them is when you open a support ticket with Apple and get a request for a specific log related to the issue. Apple has specialized decoding software to make sense of the log for the issue being investigated.


Contact Apple or schedule an appointment and your problem will be solved. You may not like the solution, especially if it requires a logic board replacement, but that is the path that you need to take. Yes, logic boards fail and Apple does not do component repair if one chip has failed.

Sep 26, 2025 6:13 AM in response to dialabrain

Or maybe they're underreported? Without internal apple support/returns numbers it's impossible to assert.


What I can do, from all the visibly cases I do see reported without solution or even a valid explanation, is make the decision to not play "problem roulette" again.


For example, it's always funny to me when the internet connection is blamed, I can reliably connect to my linux box from the mountains via mobile, and back at home with 9Gbps up/down wifi 6 I'm told to plug an ethernet cable that solves nothing. It's hocus pocus.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Cannot upgrade MacOS due to Firmware in MBP M2 Max

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.