Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

creativesmith

macrumors member
Original poster
A cautionary note: Upgrading to MacOS 26.4 broke my M1 Pro MacBook Pro. (Broke it real good!—a machine that was four years old, in nearly pristine condition, and in superb working order.

On the day that Tahoe 26.4 was released, I backed up my MBP, initiated the process, waited. It lumbered along, was a large update. I waited and waited.

Eventually, at the very end of the process, the machine froze.

Couldn’t awaken or reboot the Mac. Tried to Revive it via connection to a second MBP and with the help of DFU (Device Firmware Update).

Another long process. Wait, wait, wait. Watch the progress bar until… it freezes again.

Next, tried a Restore rather than a Revive. A Restore wipes the SSD, etc. But no luck. Just mounting stress.

Brought the MBP to an Apple Store (hours away) where they performed the very same steps I had taken. Again, my Mac failed to respond. They kept it overnight, fiddled with it. The machine remained absolutely, stubbornly, irreversibly dead.

Because my MBP was no longer covered by AppleCare (because I was a jerk and forgot to renew it) the only course of action is a $700 replacement of the logic board. Wow! Because a system update went sideways? I swear, it was a healthy machine.

From Apple’s perspective, this clearly isn’t a big deal. From my perspective, seeing my four year-old machine succumb to a heart attack during an OS update… well, it was shocking. Call me naive. (No, please don’t.)

Why am I sharing this with you? It’s a cautionary note.

Be sure to have a full backup of your system before embarking on an OS update. I’m also writing because of how upsetting it is that Apple didn’t seem to care that the update process caused such a messy failure.

“Something must have been wrong with your MBP,” said each of several reps with whom I discussed this. “We can’t attribute it to the update. Must have been a problem with the machine. We can’t tell if it won’t boot.” But, but…

Here I am, fresh out of AppleCare (my mistake for forgetting to re-up it) and fresh out of any “human consideration” from Apple. Nothing along the lines of: We’re so sorry this happened, how can we help resolve this? Just: $700.

I’m not going to spend that $700 on fixing this Mac. The question now is whether I buy a new one, or look for something else.

Take care and take precautions with your software updates.

PS - I’ve been pumping money into Apple for decades. This is the first time I’ve felt that they truly just don’t care. And yeah, I know… dream on.
 
I sympathize with your situation. Years ago I updated MBPro early 2008 to Mavericks OS and it broke my Mac Laptop. I needed to have the Motherboard replaced back then the cost was only about $300.

Edit: Did you or Apple Reps do a hardware test?
 
Last edited:
  • Wow
Reactions: brandoman
I certainly understand your distress about the update. While it's true that "Correlation is not causation" any software update is also a period of higher stress on the hardware, that can uncover/"push over the brink" hardware issues. The update may well have precipitated the failure, but it's likely failure was imminent regardless.
 
It can simply be a coincidence of having machine failing on the very same reboot when update was being installed. As all is installed on same SSD/NAND, then it is possible that updating some part of the system touched the parts of flash that had essentially failed before that (and are not written to in normal operation).

I have had network equipment failing the same way at the time of updating the firmware - in a way that low-level reflashing failed after that hinting to flash storage failure.
 
Last edited:
I wonder if the SSD failed.

One reason why Apple should reconsider soldering SSDs.
Reality is that modern day NAND chips are replaceable if proper parts, skills and equipment is available. However it is obvious that Apple itself does not support component level board repair nor upgrades (storage can actually be upgraded by replacing the chips with ones of bigger capacity if they are available).
 
Last edited:
  • Love
Reactions: _Mitchan1999
Yup,
the EXACT same thing happened to my Macbook Pro M1Pro at the completion of the 26.4 update. it went Bricked. I finally got it into DFU mode with 2 different host MACs and both of them errored out at Step 4 of Revive and then when i gave up and tried Restore also . Apple Store couldnt either and were even using the wrong USB ports on my Mac for that and then said $698 for new logic board since then couldnt get even into DFU mode. (which i got that far later on my Mac Mini M4Pro )
 
It is possible that some sort of bug exists in 26.4 which causes DFU restore to fail (can be related to certain chips or not)...
 
I sympathize with your situation. Years ago I updated MBPro early 2008 to Mavericks OS and it broke my Mac Laptop. I needed to have the Motherboard replaced back then the cost was only about $300.

Edit: Did you or Apple Reps do a hardware test?
I appreciate your sympathy. Sorry you had a similar headache.
No hardware tests that I know of, and am now in limbo after connecting with an Apple Specialist who issued a one-time exception. Waiting to hear back from her. They want to make sure I didn’t spill a beverage in the machine. I absolutely didn’t. But that’s only my word. She’s been trying to coordinate with the Apple Store I visited. This has been a stressful situation.
Meanwhile, I need a machine.
 
Might not be an isolated incident. See — https://forums.macrumors.com/threads/macbook-pro-m1-pro-is-death-after-26-4.2479891/post-34507158

Looks like you might be able to get out of it with DFU mode.
Well, as luck would have it, DFU didn’t help, neither in Revive mode nor Recover. They tried several times at the Apple Store.
It is possible that some sort of bug exists in 26.4 which causes DFU restore to fail (can be related to certain chips or not)...
Hm… wish I knew. Am so leery to make another MBP purchase. Though I doubt this sort of thing is brand specific.
 
Hm… wish I knew. Am so leery to make another MBP purchase. Though I doubt this sort of thing is brand specific.

Hopefully Apple can figure something out and also take care of you.

And updates or upgrades bricking computers can happen with any OS and any brand of hardware. There has been plenty of documented cases of Windows 11 updates crashing computers with certain brands of NVME drives and/or certain brands of graphics cards.
 
Same problem with my MBP14 M2 Max, apple store tried Revive and battery disconnection with no luck and ordered new logic board (luckily I have apple care). Going to try with Apple Configurator 2 way while I wait for the spare parts.
Just died after the first reboot with 26.4.
 
Same problem with my MBP14 M2 Max, apple store tried Revive and battery disconnection with no luck and ordered new logic board (luckily I have apple care). Going to try with Apple Configurator 2 way while I wait for the spare parts.
Just died after the first reboot with 26.4.
Try what I wrote above, will likely make your machine work again.
 
Just finished the procedure of @CMMChris and @Pataar with the 26.3.1 image and it is back online with no data loss!
Connected with thunderbolt5 cable, DFU (use the correct port), dragged the ipsw (https://updates.cdn-apple.com/2026W...1973/UniversalMac_26.3.1_25D2128_Restore.ipsw) in apple configurator 2, REVIVE, and back online in 10 minutes (it asked for a new activation but done with no issues)!

Thank you for the infos

dfu procedure: https://support.apple.com/en-us/108900
 
Last edited:
Updated my MBP M1 Pro to 26.4 without any issues.

And yes, a good idea to backup your Mac before you update.
 
  • Like
Reactions: bapegg
I agree that one should always do a backup before any OS upgrade or update. This goes for any operating system.

I do a Time Machine backup at minimum when updating my Mac's. I also backup my iPhone and iPad to my Mac mini before any updates.
 
Have seen M3 and M4 series affected as well on other places, so does not seem to apply to specific generations.

I have been debating on upgrading to Tahoe on my M4 Mac mini now that I have a Neo. But I think I will wait until 26.4.1 or wait for MacOS 27.
 
I'd say skip Tahoe on your Mini. Still feels half baked on my M4 Max Mac Studio. So many unresolved issues still, some of them dating back to first developer beta release back during WWDC '25. I still feel like downgrading to macOS 15 but don't want to lose the gaming improvements on Tahoe which is the main reason I stick with it.
 
  • Like
Reactions: bapegg
I never bricked my computers entirely with updates, but I had this issue recently where erasing my M4 from recovery assistant (running 15.7.5) nuked the recovery image and it ended up requiring DFU restore to install the OS.

I did it the exact same way in past with no issues, so that's pretty weird. Wonder if there could be something about new firmwares (late Sequoia versions have the same firmware as Tahoe IIRC).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.