golfnut1982
macrumors 6502a
Spot on, thats what I meant by "as we know it". Some users may not be as knowledgeable as you about the other methods or usage. But Carbon Copy Cloner can still back up to a Time Capsule, so that might help.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MacOS 26.4 update broke MBP
- Thread starter creativesmith
- Start date
- Sort by reaction score
chrfr
macrumors G5
Macs won’t be able to connect to Time Capsules at all because Apple is removing AFP support altogether. After that happens, Carbon Copy Cloner won’t be able to interact with the Time Capsule at all.
golfnut1982
macrumors 6502a
Mine was an update from 26.3.1 to 26.4 and a reboot about 10 days later and it didn't come back.
I think it's hard to say how many are affected as I know three other friends that have a MacBookPro M2 Pro, same as me and not seeing any issues.
throAU
macrumors G4
It's a good idea to constantly have backups/cloud sync of any computer because they all break eventually.
It had been running Tahoe 23.6.1(a). The issue with restoring or reviving from a backup became a moot point as the machine was effectively dead. For others who've had similar issues upgrading to 26.4, did you subsequently roll the dice and try upgrading to 26.4.1? I'm afraid to do it.
minik
macrumors demi-god
I have done a number of Mac update to 26.4.1 at work, so far so good. However there were a few mentioning on the MacAdmins Slack channel about the 'not turn on after updating to 26.4.1', including M2 and M3 models.
Now think about it, it's hard to say if it's related. Last month, I had a 16-inch MacBook Pro (M4 Pro) bought in and won't power up. The MagSafe light didn't even light up and I didn't document the OS version. 26.3.1 was just released at that time, but the Mac was definitely not up to date. I opened a case with Apple and also mentioned the kernel panic (either memory or storage related). Interestingly enough, I left it overnight unplugged and the next day it powered on like normal. The problem came back at a later time.
Mailed it in for service and came back with a new logic board (physical damage/liquid damage). Although it has AppleCare+, it's still within the first year limited warranty. A liquid damage wouldn't be a free repair (a $299 fee). With the kernel panic, that might be a defected logic board.
A massive massive thank you to everybody who contributed to this thread. This saved me a trip to the Apple Store with my M2 Air.
Having the same issue with my M2 Pro 14”, took it to a repair shop, they said that there is a short in the power delivery chip. Couldn’t get into DFU
I wanted to say a huge thank you to everyone on this thread. I’ve been up for hours trying to figure out what went wrong, and I initially thought I was the one who did it by closing the lid while updating. I have a 2023 MBP M2 Pro, and the update to 26.4 bricked my device. I’ve been up all night trying to sort this out.
I even extended my Apple Care plan for a year just to be prepared for the worst, but the nearest Apple Store is a four-hour drive!
It had priceless videos of my daughter from the last three years! I could never imagine losing those!!
This thread was on the third page of my Google search results! Yes, I was that desperate!
I used DFU Blaster to get into DFU mode, any other methods were not working for me.
Then I downloaded 26.2 IPSW and I revived my Macbook to it using the drag and drop method mentioned here, which was what it was before that dreaded update!!
Now everything is back exactly as it was before! up to the last open apps!
Huge thanks to you all, and I really appreciate it.
I even extended my Apple Care plan for a year just to be prepared for the worst, but the nearest Apple Store is a four-hour drive!
It had priceless videos of my daughter from the last three years! I could never imagine losing those!!
This thread was on the third page of my Google search results! Yes, I was that desperate!
I used DFU Blaster to get into DFU mode, any other methods were not working for me.
Then I downloaded 26.2 IPSW and I revived my Macbook to it using the drag and drop method mentioned here, which was what it was before that dreaded update!!
Now everything is back exactly as it was before! up to the last open apps!
Huge thanks to you all, and I really appreciate it.
boswald
macrumors 68030
This is the kind of positivity and gratitude MR needs more of! Glad you got everything working!
Fishrrman
macrumors Nehalem
eelk wrote in reply 60 above:
"Having the same issue with my M2 Pro 14”, took it to a repair shop, they said that there is a short in the power delivery chip. Couldn’t get into DFU"
Do you have another Mac available with which to try to get into DFU mode yourself?
If so, then I STRONGLY suggest that you download DFU Blaster and give it a try:
twocanoes.com
DFU Blaster operates in "free mode" and in "paid mode".
The paid mode gives you access to all the features, but...
... you don't NEED "all" the features.
All you need is to get into DFU mode, and then use Apple Configurator to do the rest.
Again, I recommend that you give this a try.
It could save you time, trouble... and MONEY.
One other thing:
Use a USBc data cable (can also be a charging cable) to connect the two Macs, and BE SURE that you are connecting to the specific "DFU port" on the target (problem) Mac.
DO NOT USE a thunderbolt cable ! Very high probability that it won't work.
"Having the same issue with my M2 Pro 14”, took it to a repair shop, they said that there is a short in the power delivery chip. Couldn’t get into DFU"
Do you have another Mac available with which to try to get into DFU mode yourself?
If so, then I STRONGLY suggest that you download DFU Blaster and give it a try:
DFU Blaster Pro
twocanoes.com
DFU Blaster operates in "free mode" and in "paid mode".
The paid mode gives you access to all the features, but...
... you don't NEED "all" the features.
All you need is to get into DFU mode, and then use Apple Configurator to do the rest.
Again, I recommend that you give this a try.
It could save you time, trouble... and MONEY.
One other thing:
Use a USBc data cable (can also be a charging cable) to connect the two Macs, and BE SURE that you are connecting to the specific "DFU port" on the target (problem) Mac.
DO NOT USE a thunderbolt cable ! Very high probability that it won't work.
Till this moment I could not believe that I would find the solution to this issue on a random thread where I never even thought to look.
I’m very grateful to you all.
I also never expected apple to screw up this badly with an update, their devices have always been very reliable and worked for years, I still have and use a 2011 MBP 15” for all my legacy software and games and it still runs like day one, except for having to replace the battery every 4 or so years 🙂
genexx
macrumors 6502
Huge thanks to @CMMChris for the DFU + Apple Configurator 2 + previous-IPSW procedure, and @Pataar for confirming it. This thread is literally the reason my MacBook Air M2 isn't bricked this morning — I was on 26.3.1 with 26.4.1 already staged and "install tonight" armed. Reading here made me stop and lock it down.
Also not the first time this pattern has shown up — Ventura 13.5 and 13.6 had their own brick waves (some linked to CrowdStrike, some to ProMotion being disabled pre-update), and Configurator + previous IPSW was the same playbook back then. Good news is Apple Silicon's DFU recovery path is solid, as long as the hardware underneath is actually fine.
@Non-Euclidean — a pinned top-post with the DFU procedure in each brick thread would probably solve most of it without a separate section.
Still undecided on 26.4.1 myself; if anyone went 26.3.1 → 26.4.1 clean, that would be good to know.
Also not the first time this pattern has shown up — Ventura 13.5 and 13.6 had their own brick waves (some linked to CrowdStrike, some to ProMotion being disabled pre-update), and Configurator + previous IPSW was the same playbook back then. Good news is Apple Silicon's DFU recovery path is solid, as long as the hardware underneath is actually fine.
@Non-Euclidean — a pinned top-post with the DFU procedure in each brick thread would probably solve most of it without a separate section.
Still undecided on 26.4.1 myself; if anyone went 26.3.1 → 26.4.1 clean, that would be good to know.
Hey I'm facing a similar issue but it happened after restarting my mac a few days after updating. Apple said the logic board needs to be replaced and DFU mode didn't work. When you said your mac was completely dead was the trackpad click/haptic working? I'm asking since mine isn't working and I read online that it means there's a deeper issue. So just wanted to know if it would still be possible for me to somehow get it into DFU mode since it worked for you. MagSafe glows orange so its charging but other than that it's completely dead.
Huge thanks for sharing this! I’ve been struggling with the exact same issue on my M2 Pro after the latest 26.4.1 update and a minor power surge at home. My Mac was a total brick. Magsafe was orange, but the screen was pitch black.
I even went as far as opening the bottom case to check the hardware. Interestingly, when I disconnected the trackpad cable, the fans immediately started spinning at max speed. That was my first sign that the logic board was actually still alive and just stuck in a firmware loop.
I am going to try the 26.3.1 Revive method tomorrow using your DFU timing (10s + 8s). It is a lifesaver to know that this is a widespread software issue and not a $700 hardware failure. Will report back once I get it running!
I even went as far as opening the bottom case to check the hardware. Interestingly, when I disconnected the trackpad cable, the fans immediately started spinning at max speed. That was my first sign that the logic board was actually still alive and just stuck in a firmware loop.
I am going to try the 26.3.1 Revive method tomorrow using your DFU timing (10s + 8s). It is a lifesaver to know that this is a widespread software issue and not a $700 hardware failure. Will report back once I get it running!
Hey i'm in a similar situation just wanted to know a couple things. Does the trackpad click or is it also dead (no haptic), and do the charging ports work like if you tried to charge your phone from the macbook?
Makisupa Policeman
macrumors 6502a
I’m not sure if my experience is related because nothing was completely bricked for me with 26.4. However it was hella buggy and crashed doing the most random basic things, causing me to have to force shutdown multiple times on my M3 Pro, which I’m not sure I’ve ever had to do on a Mac before.
mrmxts
macrumors member
Exactly the same behaviour. Fixable my downgrading to 26.3.1 yes.
Reporting back with some amazing news. I successfully revived my M2 Pro!
Here is how it went: I followed the DFU timing (10s + 8s) and connected it to a donor Mac Air. When I first tried the "Revive" option in Apple Configurator, it actually threw an error, which honestly terrified me. I thought for a moment that a full "Restore" (factory reset) was my only option and that I’d lose all my logic projects and client work.
However, after some troubleshooting and advice, I tried again. I dragged the 26.3.1 IPSW (the one linked in this thread) onto the DFU icon. Even though I was using the 26.3.1 file to fix it, once the process finished, my Mac booted up perfectly and was actually on version 26.4 (the version I had before the crash). Most importantly - all my data is intact! No format, no wipe. It seems the process just "re-kicked" the firmware back to life.
One warning for others: The 26.4.1 update is still showing up in my System Settings as "Restart Required." Since this specific update is what caused the bricking in the first place, I am currently avoiding it like the plague. I've unchecked all "Automatic Updates" and "Install macOS updates" boxes.
I’m currently looking for a way to completely purge the downloaded 26.4.1 update files from my system so I can safely reboot without the fear of it trying to install again. Regular terminal commands like sudo rm -rf /Library/Updates/* are being blocked by SIP in Tahoe/Sequoia, so if anyone has a workaround to delete the staged update, please let me know!
Huge thanks again to the author of this thread. You saved me from a $700+ logic board replacement and weeks of downtime. Cheers from Azerbaijan!
Just to follow up, in the end Apple have replaced the Mainboard and Touch ID. There was no explanation at all as to the cause, so can't be sure if it was a fault with the update to 26.4 or a genuine H/W issue. The Mac has come back with 26.4.1 installed and the System Firmware Version is 18000.101.7. So not sure what it was before, or if there has been some tweak.
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:
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!
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.
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!
Last edited: