Image: Apple

If you’re an owner of an older MacBook Pro, you may want to hold off on updating to Apple’s latest version of macOS. An increasing number of users are reporting that the Big Sur update is bricking their devices, many of which were produced in late 2013 and mid 2014.

“I’m getting a black screen with backlight when I power on, can’t enter recovery mode, no startup sound, nothing,” wrote one user on r/MacOS. “Not impressed at all. Apple support tried getting me to reset the PRAM, SMC, etc., and when that didn’t work, they asked me to take it for in-person servicing.”

“I’m experiencing a similar issue,” warned another on the MacRumors forum. “It got stuck on a black screen during installation so I restarted my MBP. Now it won’t show boot options, recovery mode, nothing. The backlight comes on and that’s it.”

“[…] the screen was black – no status bar, no nothing, but I could tell the LED was on,” an additional post on Apple’s support forum reads. “Nothing would wake it up so I eventually held the power button to force a shutdown. Now it won’t boot. Tried SMC, PRAM, holding shift, option keys, recovery mode etc etc. Tried all many many times.”

Replies on the MacRumors forums suggest that the problem may be even more widespread, with other, newer Mac models (e.g., 2019 iMac) being affected. In any case, users will definitely want to wait for Apple to release a fix before applying the Big Sur update.

Don’t Miss Out on More FPS Review Content!

Our weekly newsletter includes a recap of our reviews and a run down of the most popular tech news that we published.

Join the Conversation

7 Comments

  1. [QUOTE=”Grimlakin, post: 23528, member: 215″]
    And you just know in person servicing is going to come with a 1000 dollar bill.
    [/QUOTE]
    More than likely the users are gonna be screwed because of the T2 chip having its full drive encryption turned on by default with Apple’s previous update. At least this is what I’m calling. Screwed.. Gotta start from scratch..

  2. [QUOTE=”Space_Ranger, post: 23533, member: 52″]
    More than likely the users are gonna be screwed because of the T2 chip having its full drive encryption turned on by default with Apple’s previous update. At least this is what I’m calling. Screwed.. Gotta start from scratch..
    [/QUOTE]
    Time machine has saved me more than once, and the models listed as having issues don’t have a T2 chip. So I guess the lesson is there is no substitute for having backups. It’s not like a Windows update has never went awry…

    That said, no issues on my mid-2014 MBP

  3. [QUOTE=”Brian_B, post: 23536, member: 96″]
    Time machine has saved me more than once, and the models listed as having issues don’t have a T2 chip. So I guess the lesson is there is no substitute for having backups. It’s not like a Windows update has never went awry…

    That said, no issues on my mid-2014 MBP
    [/QUOTE]
    Who was claiming Microsoft was perfect here?

  4. [QUOTE=”Space_Ranger, post: 23542, member: 52″]
    Who was claiming Microsoft was perfect here?
    [/QUOTE]
    In [USER=96]@Brian_B[/USER]’s defense, I read sarcasm from his post, and I’m terrible at that…
    [QUOTE=”Brian_B, post: 23536, member: 96″]
    Time machine has saved me more than once, and the models listed as having issues don’t have a T2 chip. So I guess the lesson is there is no substitute for having backups. It’s not like a Windows update has never went awry…
    [/QUOTE]
    Lose your Bitlocker key and you’re SOL there too. More of a problem of poorly managed corporate domains of course, or those that choose not to use a Microsoft account on their laptop.

  5. As far as I’m concerned that is a blessing.

    Better bricked than sending all of your data to Apple.

    [URL]https://sneak.berlin/20201112/your-computer-isnt-yours/[/URL]

Leave a comment