MacBook Pro M1 Pro is death after 26.4

[hnery]

Making an account just to say I also had this on my 2023 M2 Pro Macbook Pro 14 inch. I set the update downloading and when I came back, my machine was completely dead with no signs of life other than Magsafe showing orange and then green once fully charged.

Used A Mac Mini at work with apple config to revive - just some notes though i'd like to add for more detail for anyone who might need it, I was going off 3 different sets of notes to get enough detail for me.

1) get the IPSW file for 26.3.1 from here https://updates.cdn-apple.com/2026W...1973/UniversalMac_26.3.1_25D2128_Restore.ipsw

2) For DFU mode - I found a comment on reddit that had different instructions from Apple but apparently were more reliable. I got into DFU mode on my first try. Make sure the mac is not connected to anything first.

2.1 Press and hold the power button (Touch ID). (Make sure your mac is fully charged if it is a Macbook)

2.2 Immediately hold down these keys as well for 10 seconds:
Left Control, Left Option, Right Shift.
2.3 After 10 seconds, release the keys but continue to hold the power button (Touch ID) for another 8 seconds.
2.4 Plug in USB C cable into DFU port and connect it to your Mac with Apple configurator.
2.5 Drag the IPSW directly onto the Mac in the list on apple config, and click revive.
2.6 Wait. It took about 3-5 minutes, My mac then booted into recovery, I entered my password and it rebooted. The first reboot failed so I manually clicked Macintosh HD, entered my password again and then it worked.

Credit to u/Darthsilicrypt on Reddit for these instructions.

M2 max 14 - this one helped. Had to try maybe about 5-6 times but worked. 10min later everything up again.

Only had an old hackintosh-Sequoia lying around and did the revive with that. Worked. Thank you everyone here.

My computer wasn't "little bit bricked" - it was full on nothing-on-nothing broken after the update.

 

[carym]

Thanks for the help, everyone! I fixed my MacBook using another Mac. Just a tip: the screen might stay black for up to 30 minutes during the update/recovery—this is normal. We often mess up the software by pressing the power button thinking it's not turning on. Just wait it out!

 

[Alameda]

This thread is terrifying, except for the part where everybody who had a dead Mac managed to bring it back with a DFU restore or revive.

 

[bhanne01]

Making an account just to say I also had this on my 2023 M2 Pro Macbook Pro 14 inch. I set the update downloading and when I came back, my machine was completely dead with no signs of life other than Magsafe showing orange and then green once fully charged.

Used A Mac Mini at work with apple config to revive - just some notes though i'd like to add for more detail for anyone who might need it, I was going off 3 different sets of notes to get enough detail for me.

1) get the IPSW file for 26.3.1 from here https://updates.cdn-apple.com/2026W...1973/UniversalMac_26.3.1_25D2128_Restore.ipsw

2) For DFU mode - I found a comment on reddit that had different instructions from Apple but apparently were more reliable. I got into DFU mode on my first try. Make sure the mac is not connected to anything first.

2.1 Press and hold the power button (Touch ID). (Make sure your mac is fully charged if it is a Macbook)

2.2 Immediately hold down these keys as well for 10 seconds:
Left Control, Left Option, Right Shift.
2.3 After 10 seconds, release the keys but continue to hold the power button (Touch ID) for another 8 seconds.
2.4 Plug in USB C cable into DFU port and connect it to your Mac with Apple configurator.
2.5 Drag the IPSW directly onto the Mac in the list on apple config, and click revive.
2.6 Wait. It took about 3-5 minutes, My mac then booted into recovery, I entered my password and it rebooted. The first reboot failed so I manually clicked Macintosh HD, entered my password again and then it worked.

Credit to u/Darthsilicrypt on Reddit for these instructions.

Thank you so much for posting these instructions. I had exactly the same problem in the update process to 26.4.1 this week. Nothing helped - but rolling back to 26.3.1 with the instructiosn posted by you made my MacBookPro functional again. It seems there is something seriously wrong with this update.

 

[pedrogcsb]

I'm having the same problem with my M4 Pro MacBook Pro. Unfortunately, I can't revive or restore it, even with the 26.3.1 IPSW file. Pretty frustrating.

 

[Pataar]

So after safely using 26.3.1 a while, I decided to install 26.4.1. Used the full installer instead of the delta. Installation went smooth.

 

[sayersgram]

I had the same problem. What worked for me:

Boot the problematic Mac into DFU. Start Apple Configurator 2 on a seperate Mac, which is connected to the other one using the DFU guide on the Apple website.

Into Apple Configurator 2, load the IPSW file of 26.3.1. Press revive in the dialog.

After a couple of minutes I saw the Apple logo again on the problematic mac, and could use the system again back on 26.3.1. I did not lose any data.

A couple of notes:
- Reviving using 26.4 does not work! This will be tried by default by the recovery software. You'll need to be using a custom IPSW file. (https://updates.cdn-apple.com/2026W...1973/UniversalMac_26.3.1_25D2128_Restore.ipsw)
- It's hard to get the mac into DFU mode. I had to try this 10-20 times to get this done.

This right here, pure magic. Went to the “Genius Bar” with a MacBook Pro M1. They could not revive or restore. Said the keyboard was dead since the caps lock wouldn’t light which meant the logic board died. I refused to believe an OS update would kill a machine. Sure enough I borrowed a Mac Mini and followed the steps in this post. Bingo, Apple Screen and I’m back in the machine. Thank you!

 

[Macintosche]

I dropped my MacBook off at the Apple Store for this same issue before coming across this thread, and they're insisting that my computer has a hardware problem and needs a new logic board. I found this thread the other day, after already leaving my MacBook at the store, and have tried telling them over the phone to attempt a revive to macOS 26.3.1 like was advised in this thread, although they claim they've been unable to do so. Not sure if they're unable to get into DFU mode or what exactly—I would hope the "Genius Bar" knows how to get into DFU mode in this situation. I have AppleCare+ so they've already ordered the replacement logic board, so I don't know what to do aside from wait for that to come in and get installed. It's frustrating because I'm now stuck sitting around for potentially ~2 weeks waiting on the repairs for what very much seems to be a software problem. Is there no way to convince them that this is a problem with the software and ensure that they are correctly attempting to revive the system, like the steps outlined in this thread? Is Apple at large still not aware of this problem?

 

[BGS]

I dropped my MacBook off at the Apple Store for this same issue before coming across this thread, and they're insisting that my computer has a hardware problem and needs a new logic board. I found this thread the other day, after already leaving my MacBook at the store, and have tried telling them over the phone to attempt a revive to macOS 26.3.1 like was advised in this thread, although they claim they've been unable to do so. Not sure if they're unable to get into DFU mode or what exactly—I would hope the "Genius Bar" knows how to get into DFU mode in this situation. I have AppleCare+ so they've already ordered the replacement logic board, so I don't know what to do aside from wait for that to come in and get installed. It's frustrating because I'm now stuck sitting around for potentially ~2 weeks waiting on the repairs for what very much seems to be a software problem. Is there no way to convince them that this is a problem with the software and ensure that they are correctly attempting to revive the system, like the steps outlined in this thread? Is Apple at large still not aware of this problem?

You could phone and tell them you have revoked all permission to alter your machine in any way and you will be calling to collect it today, then try the DFU restore as per this page, letting them jam the new MB in the machine of the next customer they misdiagnose.

Or (presuming you have a reliable backup of all data) wait and get a new MB.

Toss a coin ...

 

[manhunt7]

Hi everyone,

I ran into a very similar issue with my MacBook Pro 16-inch (M1 Max). After updating to macOS 26.4 / 26.4.1, the device became completely unresponsive — black screen, no signs of life at all.

I was only able to revive it using Apple Configurator in DFU mode, but the process kept failing with errors like:
“The System cannot be restored on this device” and
“Gave up waiting for device to transition from DFU state to DFU state.”

The only thing that worked for me was manually using an IPSW file for macOS 26.3.1 (downloaded from https://ipsw.me/MacBookPro18,2/) and performing a Revive. After that, the Mac finally came back to life.

I really wish I had found this thread earlier. I even had to take my MacBook to a service center, but they couldn’t fix it. My main goal was to recover the device or at least save the data. Luckily, on the second day I managed to revive it myself.

It seems like something in 26.4 / 26.4.1 firmware might be causing this issue, at least on M1 Max devices.

 

[manhunt7]

I dropped my MacBook off at the Apple Store for this same issue before coming across this thread, and they're insisting that my computer has a hardware problem and needs a new logic board. I found this thread the other day, after already leaving my MacBook at the store, and have tried telling them over the phone to attempt a revive to macOS 26.3.1 like was advised in this thread, although they claim they've been unable to do so. Not sure if they're unable to get into DFU mode or what exactly—I would hope the "Genius Bar" knows how to get into DFU mode in this situation. I have AppleCare+ so they've already ordered the replacement logic board, so I don't know what to do aside from wait for that to come in and get installed. It's frustrating because I'm now stuck sitting around for potentially ~2 weeks waiting on the repairs for what very much seems to be a software problem. Is there no way to convince them that this is a problem with the software and ensure that they are correctly attempting to revive the system, like the steps outlined in this thread? Is Apple at large still not aware of this problem?

I was actually in a very similar situation. I also took my MacBook to a service center, and they told me they couldn’t even get it into DFU mode, even though I had done it myself before without any issues. They then told me that the chip would need to be soldered/reworked, which sounded like a hardware issue diagnosis.

I refused that repair and took my MacBook back. I was pretty confident that the real problem was caused by the update rather than hardware failure. After some more research, I found a way to roll it back by manually using an IPSW file and reviving the device to macOS 26.3.1.

After rolling back, everything started working properly again, and the Mac fully came back to life. So in my case, it clearly turned out to be a software/firmware issue, not a chip-level hardware failure.

If your MacBook was working fine before the 26.4 / 26.4.1 update and then suddenly became a brick right after, I would really question a logic board replacement diagnosis. If possible, I would push them to try a proper DFU revive with a known working IPSW for 26.3.1 before replacing the board.

 

[brerlappin]

Is Apple at large still not aware of this problem?

It really doesn't seem like it... I wish there was more awareness since it’s such a serious issue.

 

[veskop]

...

It cost me about 1040 euro! 40 euro for "diagnostic" and 999 euro for a new MacBook Air M4, because technician told me that my logic board is death and if i want to replace it - new cost 700 euro!

FYI, minimal salary in Bulgaria is about 630 euro before taxes!

 

[Laulau]

I had the same experience as OP and some others here. MacBook Pro M2 --> update --> seems dead --> Apple Certified Store does diagnostic for 50 euros --> they come to tell me they need to replace the logic board --> I take it home to test Pataar's method --> Mac comes alive after ONE try.

Of course I'm super happy, but why in god's name are these repair services not aware of this fix?

 

[ignatius345]

I had to fully reset the Mac which had some data on it gone 🙁

I thought I was going to lose all my data and take it to a shop

My main goal was to recover the device or at least save the data.

Are people seriously not backing up their computers anymore? WTF!

I mean, I guess do what you want but the cost of backing up is so low, in terms of time/effort and money. To be stressing out about “saving your data” is such an own goal, honestly.

 

[BGS]

Hi everyone,

I ran into a very similar issue with my MacBook Pro 16-inch (M1 Max). After updating to macOS 26.4 / 26.4.1, the device became completely unresponsive — black screen, no signs of life at all.

I was only able to revive it using Apple Configurator in DFU mode, but the process kept failing with errors like:
“The System cannot be restored on this device” and
“Gave up waiting for device to transition from DFU state to DFU state.”

The only thing that worked for me was manually using an IPSW file for macOS 26.3.1 (downloaded from https://ipsw.me/MacBookPro18,2/) and performing a Revive. After that, the Mac finally came back to life.

I really wish I had found this thread earlier. I even had to take my MacBook to a service center, but they couldn’t fix it. My main goal was to recover the device or at least save the data. Luckily, on the second day I managed to revive it myself.

It seems like something in 26.4 / 26.4.1 firmware might be causing this issue, at least on M1 Max devices.

Glad to hear you got it solved.
As for the blackout issue, I've run both 26.4 & 26.4.1 on my M1 Max with no problems at all.

 

[samuelkcc]

I had the exact same problem! At first, I actually thought my Thunderbolt 3 dock had bricked my M2 Max (64GB/2TB). I usually use it in clamshell mode (lid closed), so I didn't even realize a macOS update was running in the background.

My exact symptoms: The laptop was completely blacked out. There was absolutely no response when pressing the power button (even holding it down for 30 seconds did nothing). The MagSafe charger just showed a solid green light, and when I plugged in a USB-C charge cable with a power meter, it showed it was only drawing a measly 4W of power. It genuinely looked like a dead machine.

It happened on a Sunday, and I desperately needed my Mac for a business case on Monday morning. It was an absolute nightmare. Here is how my timeline went down:

• The Authorized Shop: I immediately booked an appointment through the Apple Support app at a local Authorized Service Provider. They demanded a £49 inspection fee (since I’m out of warranty) and told me it would take 1-2 weeks for engineering to look at it. I couldn't wait that long.
• The Official Apple Store: They advised me to drive 22 miles to an official Apple Store. I arrived just 45 minutes before closing. The staff there were actually very helpful and got a Genius to inspect it immediately for free.
• The £889 Quote: After 20 minutes, they gave me the bad news: "Dead logic board. It will be £889 to replace." I had already done some research online about the DFU mode fix, but I didn't own a second Mac at the time to try it. I discussed it with the tech, and they actually tried a DFU restore in the store, but it failed.
• The Panic Purchase: £889 is a massive repair bill, and I needed a working computer for Monday. Feeling backed into a corner, I bit the bullet and bought a brand new M5 MacBook Air right there on the spot.

When I got home, I set up the new M5 Air to make sure my Monday morning was safe. Then, using my new Mac, I decided to try my luck with the DFU restore on the "dead" M2 Max. I actually followed this exact tutorial on YouTube to make sure I was doing the key combinations correctly:

First, I tried using the latest 26.4.1 IPSW. I tried several times, redownloading it and dragging it into Apple Configurator 2, but it consistently got stuck at the very last installation step.

Then, I saw other posts here advising to use the older 26.3.1 IPSW.

OMG… it worked. The white Apple logo finally appeared! My M2 Max is fully alive again.

It all makes sense to me now. The Apple Store Geniuses couldn't fix it because their internal tools automatically grab and force the latest version (26.4.1), which is clearly bugged and fails the restore. Because of their strict protocols, they won't (or can't) manually downgrade it to 26.3.1 to bypass the glitch.

Now I have a working M2 Max and a brand new M5 Air sitting on my desk! Thanks to everyone sharing the 26.3.1 fix!

 

[LegendaryTechnician]

OMG… it worked. The white Apple logo finally appeared! My M2 Max is fully alive again.

It all makes sense to me now. The Apple Store Geniuses couldn't fix it because their internal tools automatically grab and force the latest version (26.4.1), which is clearly bugged and fails the restore. Because of their strict protocols, they won't (or can't) manually downgrade it to 26.3.1 to bypass the glitch.

Now I have a working M2 Max and a brand new M5 Air sitting on my desk! Thanks to everyone sharing the 26.3.1 fix!

You were still able to do this via Apple Configurator 2 even though Apple already stopped signing 26.3.1?

 

[samuelkcc]

Yes, it still worked perfectly for me just 2 days ago (26 April)!

I downloaded the 26.3.1 IPSW directly from the Mr. Macintosh database (https://mrmacintosh.com/restore-macos-firmware-on-an-apple-silicon-mac-boot-to-dfu-mode/) and manually dragged the file into Apple Configurator 2. It authenticated and went through without a hitch. I'm not entirely sure when Apple plans to stop signing it, but the window was definitely still open this weekend.

Before trying that, I actually attempted to use the standard recovery in Apple Configurator 2 (which automatically downloads the latest 26.4.1). When that didn't work, I even tried manually dropping the 26.4.1 IPSW file in. Both attempts with 26.4.1 failed at the exact same spot: Step 4 of the installation.

It would get stuck at around 60%, sit there doing nothing for 20 minutes, and then eventually throw a "DFU not responding" error.

Because 26.3.1 went through flawlessly on the first try and 26.4.1 consistently crashed at Step 4, I highly believe the 26.4.1 firmware itself is fundamentally bugged for this specific restore process right now.

P.S. I return the M5 MacBook Air yesterday as it is no longer needed

 

[LegendaryTechnician]

I had the same problem. What worked for me:

Boot the problematic Mac into DFU. Start Apple Configurator 2 on a seperate Mac, which is connected to the other one using the DFU guide on the Apple website.

Into Apple Configurator 2, load the IPSW file of 26.3.1. Press revive in the dialog.

After a couple of minutes I saw the Apple logo again on the problematic mac, and could use the system again back on 26.3.1. I did not lose any data.

A couple of notes:
- Reviving using 26.4 does not work! This will be tried by default by the recovery software. You'll need to be using a custom IPSW file. (https://updates.cdn-apple.com/2026W...1973/UniversalMac_26.3.1_25D2128_Restore.ipsw)
- It's hard to get the mac into DFU mode. I had to try this 10-20 times to get this done.

Amazing. This worked like a charm.
Thank you so much.

 

[AslashA]

Because 26.3.1 went through flawlessly on the first try and 26.4.1 consistently crashed at Step 4, I highly believe the 26.4.1 firmware itself is fundamentally bugged for this specific restore process right now.

I recently flashed my MacBook (M1 Pro 16/512) to IPSW 26.4.1 using Apple Configurator via Hackintosh. No issues arose; everything went smoothly.

You were still able to do this via Apple Configurator 2 even though Apple already stopped signing 26.3.1?

Apple stopped signing iOS 26.3.1, not macOS 26.3.1 😉