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.
WARNING macOS Catalina 10.15.4 Supplemental Update BRICKED my 13 inch Macbook 2018!
- Thread starter skardvin
- Start date
- Sort by reaction score
I had to restore my machine too doing the T2 reset
[automerge]1587237976[/automerge]
Anybody has troubles syncing the iCloud Drive after the restore?
[automerge]1587237976[/automerge]
Anybody has troubles syncing the iCloud Drive after the restore?
I installed the update on my 13" Mid-2013 MBA and had no problem. I cannot say the same thing when I installed it on my 15" late-2013 MBP. For some reason it borked my Apache2 server by relocating two of the Apache2 config files to the "Relocated Items" folder. Once I put them back, Apache2 ran without any errors. Hmmmmm....
Hello guys
I have Macbook pro 15” 2017 fastest cpu (i9) and 32GB, I have the same issue after the update the usb-c ports are not working till the laptop shutdown after the battery got empty, I don't have warranty, why should I pay for repair ? it was working normally, is this fair ?
I have Macbook pro 15” 2017 fastest cpu (i9) and 32GB, I have the same issue after the update the usb-c ports are not working till the laptop shutdown after the battery got empty, I don't have warranty, why should I pay for repair ? it was working normally, is this fair ?
Not fair no. But life isn’t fair. I’d speak to Apple and see what they can do. My mini had to have a new logic board. Under AppleCare so fine for me, but I’d have been pretty pissed off if I’d had to pay for it.
Installed on 2019 16" MacBook Pro and 2017 13" MacBook Air without issue. I've been holding off upgrading my Mac Pro to Catalina. I know there are options, but I'd be entering into unsupported territory. I'll stay away until Mojave itself becomes obsolete.
Hi All, my first post here.
I arrived here after my MBP 2018 w/TB was bricked dead during Catalina 10.15.4 update.
Same signs as reported by others:
This happen in the middle of the night at 3am. A quick 15 mins researching on the internet and I knew this was trouble. I didn't have any time machine backup and here in India there is an ongoing lockdown (curfew) since the last 40 days so I wouldn't be able to take this Apple either.
Next day, I was lucky to be able to borrow a friends MBP2018 w/TB for few hrs. But after reading the experiences of many, all mentioned that they had to wipe clear the HDD and do a fresh install to recover the laptop. However since I didn't have any backup and really didn't want to loose the data, so I did a little more research on this.
Two very helpful resources which helped me in fixing this issue were:
As mentioned in the post by @ClassicII, the older AC2 (2.10) did not force me to clean wipe the HDD
I was able to get an dmg file of AC2 2.10-beta from a post on reddit (link) and got the bricked MBP to connect with host MBP in DFU mode.
I choose the option as follows from menu: Actions > Restore
On the host machine, the first time the process failed and gave an error. So I tried the same steps again for the 2nd time which seems to work.
The bricked MBP showed some sign of life after 2-3 mins. Kept doing its thing with no input from my side.
Eventually the Apple logo appeared, then after few mins the progress bar below and then it was showing the estimated time.
Meanwhile the process failed on the host machine attempting DFU after trying for 5-7 mins, but it continued on the bricked MBP.
Finally, I was able to restore the T2 chip with latest FW.
What the process essentially did was perform a successful DFU on the T2 chip, and with a working T2 chip when the bricked MacBook booted, it resumed the installation of the latest Catalina (10.15.4) update it was doing (it took about 30 more mins) and then it came back to life as if nothing ever happen.
I know that in a couple of days apple will fix this issue, but in the meantime I hope this post can help anyone facing this issue.
I genuinely thank @ClassicII and Rossmann Repair (on YouTube) who helped me recover the device and the DATA!!
I arrived here after my MBP 2018 w/TB was bricked dead during Catalina 10.15.4 update.
Same signs as reported by others:
- MBP tries to reboots during update but doesn't show any signs of starting up even after 30 mins of blank screen (without backlight)
- No response to charging
- Will not even try to power up even after holding power button for few secs and trying SMC reset.
Next day, I was lucky to be able to borrow a friends MBP2018 w/TB for few hrs. But after reading the experiences of many, all mentioned that they had to wipe clear the HDD and do a fresh install to recover the laptop. However since I didn't have any backup and really didn't want to loose the data, so I did a little more research on this.
Two very helpful resources which helped me in fixing this issue were:
- Post by macrumors forum user @ClassicII - Here
This post clearly explains the process and all steps involved. However it also mentions that the latest Apple Configurator 2 (2.12.1) does not show the option to revive the device without wiping the data. - This video shows the process of recovery but few steps are unclear for first time viewer. In the video we see that the device was recovered without any data loss.
As mentioned in the post by @ClassicII, the older AC2 (2.10) did not force me to clean wipe the HDD
I was able to get an dmg file of AC2 2.10-beta from a post on reddit (link) and got the bricked MBP to connect with host MBP in DFU mode.
I choose the option as follows from menu: Actions > Restore
On the host machine, the first time the process failed and gave an error. So I tried the same steps again for the 2nd time which seems to work.
The bricked MBP showed some sign of life after 2-3 mins. Kept doing its thing with no input from my side.
Eventually the Apple logo appeared, then after few mins the progress bar below and then it was showing the estimated time.
Meanwhile the process failed on the host machine attempting DFU after trying for 5-7 mins, but it continued on the bricked MBP.
Finally, I was able to restore the T2 chip with latest FW.
What the process essentially did was perform a successful DFU on the T2 chip, and with a working T2 chip when the bricked MacBook booted, it resumed the installation of the latest Catalina (10.15.4) update it was doing (it took about 30 more mins) and then it came back to life as if nothing ever happen.
I know that in a couple of days apple will fix this issue, but in the meantime I hope this post can help anyone facing this issue.
I genuinely thank @ClassicII and Rossmann Repair (on YouTube) who helped me recover the device and the DATA!!
I am sorry, but in all these years, I have never had a Microsoft update that "bricked" any computer. Most of the issues with Microsoft updates stem from third party anti virus software. But again it amazes me how people having issues with Apple and Mac start to bash Microsoft. Stop projecting... Mac isn't the end all be all. I have Windows and Macs and I have far more issues with Mac, and Mac's recovery is far more difficult to deal with.
The T2 chip is run by software called BridgeOS. With each Apple Combo & Security Update this software is updated. If this update goes wrong, it can prevent your Mac from booting. This is exactly what happened to the users in this thread.
I wrote an article on it last night explaining the issue, I also talk about how you can revive the Mac by reinstalling BridgeOS.
10.15.4 Supplemental Update Bricking Small Number of T2 Macs
After installing the 10.15.4 Supplemental Update, a small number of users are reporting their T2 Macs are bricked. Only a DFU BridgeOS Restore will fix it!mrmacintosh.com
And this is why I will NEVER ever get a T2 Mac because Apple controls it. No wonder my 15 inch 2015 was able to update 10.15.4 without error. I hope Apple does away with this T2 crap when they move to ARM.
Apple bricked their own computer because some updates involved low level updates such as firmware.When update failed, it also messing up firmware on device, causing device bricking.
On MS, most of updates only touched at OS level. It rarely involving firmware, since low level updates often came directly from manufacturers (BIOS update, etc). At the worst scenario, only OS being affected in case failed / doomed updates.
At least the majority of the laptops with Windows are not so expensive like Apple computers. For me a Lenovo laptop with Linux will give me less headaches than Apple right now and cost me less than one third!
To the person who agreed with me, NO, I am DEAD serious - this T2 chip is, I think a violation of privacy rights as well its a way for Apple to keep a tight control over their machines. To those who are suffering from the bricking of their machines, my thoughts are with you. Never in my life with Apple have I seen such "draconian" measures with a T2 chip. Even PowerPC didn't have this and nether did the mid 2010's model of intel macs. I have a 2015 15 inch MacBook pro which does not have a T2 chip. However, once Apple moves to ARM and if they drop the T2 crap, then maybe I will consider upgrading my 2015. Until then, with COVID19 who knows what the future will be like.
My prayers and thoughts to all of you who are still locked at home during this pandemic. I am praying for you all.
You can be assured of one thing if Apple moves the main CPU to ARM: these computers will be at least as "locked down" as the Intel powered T2 models are. Apple isn't going to go backwards on security.
My experience is more issues with Windows than Mac. I have around 4 dozen of each machines I take care of.
More recently a Windows Update that knocked wifi out on close to 2/3 of these machines. Wifi would connect to an access point, pull an IP address, completely appear to be working but would not connect at all. A forced Windows update wifi driver build was the issue. Troubleshooting that down during the middle of a hectic workday was a little bit of a PITA. But again the majority of issues I have with either system, Windows takes the larger piece of the pie.
Also had Windows not update due to the bios requiring to be upgraded. Windows would pull the update, start the update, countdown, restart, 20 minutes or so and be back at the desktop and restart the procedure over and over. Most users were confused because it was continuously telling them they required an upgrade and a lot of times just spontaneously restarting in the middle of the day.
I have my macOS issues as well, so I can not paint one over the other to be significantly more stable at all times. For some people one is much better than the other. For myself, once you arre going over 10-12 workstations for each, the little annoying things really start rearing their heads.
I've never experienced either os bricking itself either.
For backup and recovery I have a common software that works fairly consistent across both platforms. No Windows backup, no Time Machine.
If I don't want to pull my hair out, I have my. Linux machines.
More recently a Windows Update that knocked wifi out on close to 2/3 of these machines. Wifi would connect to an access point, pull an IP address, completely appear to be working but would not connect at all. A forced Windows update wifi driver build was the issue. Troubleshooting that down during the middle of a hectic workday was a little bit of a PITA. But again the majority of issues I have with either system, Windows takes the larger piece of the pie.
Also had Windows not update due to the bios requiring to be upgraded. Windows would pull the update, start the update, countdown, restart, 20 minutes or so and be back at the desktop and restart the procedure over and over. Most users were confused because it was continuously telling them they required an upgrade and a lot of times just spontaneously restarting in the middle of the day.
I have my macOS issues as well, so I can not paint one over the other to be significantly more stable at all times. For some people one is much better than the other. For myself, once you arre going over 10-12 workstations for each, the little annoying things really start rearing their heads.
I've never experienced either os bricking itself either.
For backup and recovery I have a common software that works fairly consistent across both platforms. No Windows backup, no Time Machine.
If I don't want to pull my hair out, I have my. Linux machines.
Not too bad, it is only a year old or maybe less.
What a sad state of affairs. But take comfort, some useless Apple Glasses are on the way...Not too bad, it is only a year old or maybe less.
The machine has less than 6 months and I never used it. I only saw a Netflix movie on it. 😡
Last edited:
If the firmware on the motherboard is being updated, an interruption can corrupt it.
I can't see this issue being a T2 issue unless the T2 is somehow causing a firmware update to fail.
All Windows based computers are different so I doubt that Microsoft can and does update the firmware on the main logic board.
[automerge]1589556815[/automerge]
The T2 chip is actually an ARM chip.
When Apple produces their own CPU, it will most likely include the T2 functionality (i.e. the T2 chip will go away and the T2 will move internally into the new CPU).
Last edited:
but is it a problem with the T2 firmware update itself (Catalina update) or is it a problem with the firmware update being interrupted causing the firmware update of the T2 to be corrupted ?
I think that it's probably the latter choice since it is not affecting everyone.
The T2 chip is not necessarily causing an interruption of the firmware update (causing the problem) but a firmware interruption is definitely causing a T2 firmware corruption.
Any time a remote firmware update is attempted in any electronic device, there is a chance of catastrophically corrupting the firmware.
For something like the T2 chip, Apple should probably not be updating the firmware or separate any firmware updates from the macOS update.
Updating the T2 chip firmware in very exceptional cases goes wrong. Apple should test the updates thoroughly before making them public.
It may not be just a case of testing it some more.
Any interruption by the Mac during a firmware update can corrupt the firmware.
I believe that any firmware updater should be independent of the macOS update.
No interruption. In my case is needed a new Logic Board on my MacBook Pro 16 inch 2019. When I made the update everything went well. After restarting it, the computer never came to life.
Same on my Mac mini. Fine now though. No more updates until the Apple stores are open. I don’t need another three weeks without a Mac.