macOS Monterey may be bricking some Macs - but there is a fix

AppleInsiderAppleInsider
Posted:
in Genius Bar edited November 2021
Reports are circulating that macOS Monterey is causing problems with a small quantity of upgraders and new MacBook Pro owners -- but the issue appears to be less prevalent than in previous years, and there is a user-executable fix for most recent machines.




Apple's macOS updates, especially new releases, contain one or more firmware updates to assorted chips in the Mac including GPU, storage, the T1 or T2 chips, and more. If interrupted, or if impacted by other factors, a firmware update can fail, and leave a machine in an unusable condition.

This has been happening off-and-on for years, and is most common with new macOS versions that launch in the fall.

Based on AppleInsider collated service data, the problem with Monterey to date is less prevalent than in previous years versus an equivalent time after release. It isn't clear if macOS Monterey's adoption rate is any different than other years, which could impact the estimate -- but it would require half the rate of Monterey adoption versus Big Sur to make a swing to upgraders in 2021 being impacted at a higher rate than any OS of the last five years.

The problem also seems to impact T1-equipped Macs at a higher rate than T2-equipped models.

All of this is, of course, cold comfort to those impacted.

First reported by MacRumors on Monday, users are reporting completely dead machines following a macOS Monterey update. Apple is being asked to step in and help -- but there is already a troubleshooting procedure in place.

Apple has a restoration process for T2 machines, if the user has access to a second Intel-based Mac. Apple's Configurator tool can revive the firmware on a security chip, without erasing data, making any changes to the startup volume, the user's data volume, or any other associated internal storage volumes.

Apple has specific restoration instructions for T2 machines in a support document. A similar document and procedure exists for Apple Silicon, should the problem arise with future macOS revisions, or following the macOS 12.0.1 update on a new machine.

At present, AppleInsider suggests that T1-based machines should be brought in to an Apple Store for evaluation. Apple stores are replacing machines impacted by the problem that are under warranty, without performing the revivification through Configurator or any kind of data migration.

Read on AppleInsider

Comments

  • Reply 1 of 15
    Fred257Fred257 Posts: 252member
    Always best to wait a while before updating software.
    baconstangwilliamlondon
  • Reply 2 of 15
    SebiakSebiak Posts: 2member
    My 2019 MacBook Pro with Touch Bar has been bricked while applying Mac 11.8.1, last Tuesday.
    A local certified retailer told me I've to change mother board + Touch ID module. I refused.
    Anyway, after discussing with Apple Support and following its suggestion, I took an appointment to an Apple Store.
    So I still have hope. 
    edited November 2021 dewme
  • Reply 3 of 15
    Mike WuertheleMike Wuerthele Posts: 6,921administrator
    Sebiak said:
    My 2019 MacBook Pro with Touch Bar has been bricked while applying Mac 11.8.1, last Tuesday.
    A local certified retailer told me I've to change mother board + Touch ID module. I refused.
    Anyway, after discussing with Apple Support and following its suggestion, I took an appointment to an Apple Store.
    So I still have hope. 
    I'd try the Configurator solution first, if Apple Support didn't tell you to do so.
    command_f
  • Reply 4 of 15
    miahmiah Posts: 3member
    My 2019 MacBook Pro was bricked while updating to 11.6.1. I'm still under AppleCare and called Apple. They said I'd have to take the computer into my local 3rd-party Apple dealer for evaluation. That dealer found that the T2 was "stuck," but they were able to "reset" it. I presume they used the Configurator method mentioned here, but I'm not sure. The problem is, they charged me $75 for their half-hour of time, a fee I don't feel I should be responsible for since it was Apple's software/hardware that caused the problem. I will take this up with Apple and hopefully get reimbursed. NOTE: Fix restarted my bricked machine and no data was lost.
    muthuk_vanalingamdewme
  • Reply 5 of 15
    Mike WuertheleMike Wuerthele Posts: 6,921administrator
    miah said:
    My 2019 MacBook Pro was bricked while updating to 11.6.1. I'm still under AppleCare and called Apple. They said I'd have to take the computer into my local 3rd-party Apple dealer for evaluation. That dealer found that the T2 was "stuck," but they were able to "reset" it. I presume they used the Configurator method mentioned here, but I'm not sure. The problem is, they charged me $75 for their half-hour of time, a fee I don't feel I should be responsible for since it was Apple's software/hardware that caused the problem. I will take this up with Apple and hopefully get reimbursed. NOTE: Fix restarted my bricked machine and no data was lost.
    I'm sure they used Configurator to fix it.

    Do try to get reimbursed, but don't count on it.
  • Reply 6 of 15
    elijahgelijahg Posts: 2,831member
    Since this seems to be a common issue with T1/2 chips, it seems Apple has neglected to add an automatic firmware rollback - very common in embedded systems. Pre-T1/2 systems were never bricked, the worst may have required a reinstall. Hopefully they've done a better job of handling a bad firmware flash in the Mx systems.
  • Reply 7 of 15
    Mike WuertheleMike Wuerthele Posts: 6,921administrator
    elijahg said:
    Since this seems to be a common issue with T1/2 chips, it seems Apple has neglected to add an automatic firmware rollback - very common in embedded systems. Pre-T1/2 systems were never bricked, the worst may have required a reinstall. Hopefully they've done a better job of handling a bad firmware flash in the Mx systems.
    Pre T1 and T2 systems did get bricked with firmware updates from time to time, with about the same frequency from 2010 to 2015 as from 2015 to present.

    Worse yet, there wasn't a Configurator option for users to deal with the issue.
    command_f
  • Reply 8 of 15
    elijahgelijahg Posts: 2,831member
    Mike Wuerthele said:
    elijahg said:
    Since this seems to be a common issue with T1/2 chips, it seems Apple has neglected to add an automatic firmware rollback - very common in embedded systems. Pre-T1/2 systems were never bricked, the worst may have required a reinstall. Hopefully they've done a better job of handling a bad firmware flash in the Mx systems.
    Pre T1 and T2 systems did get bricked with firmware updates from time to time, with about the same frequency from 2010 to 2015 as from 2015 to present.

    Worse yet, there wasn't a Configurator option for users to deal with the issue.
    Really? I don't recall seeing much noise about it, and we never had any in the 100 or so Macs I managed back in the early 2010s. I do remember there was a CD you could burn to re-flash the firmware, though I thought that issue had been resolved by the time CD drives were removed.
    FileMakerFeller
  • Reply 9 of 15
    Mike WuertheleMike Wuerthele Posts: 6,921administrator
    elijahg said:
    Mike Wuerthele said:
    elijahg said:
    Since this seems to be a common issue with T1/2 chips, it seems Apple has neglected to add an automatic firmware rollback - very common in embedded systems. Pre-T1/2 systems were never bricked, the worst may have required a reinstall. Hopefully they've done a better job of handling a bad firmware flash in the Mx systems.
    Pre T1 and T2 systems did get bricked with firmware updates from time to time, with about the same frequency from 2010 to 2015 as from 2015 to present.

    Worse yet, there wasn't a Configurator option for users to deal with the issue.
    Really? I don't recall seeing much noise about it, and we never had any in the 100 or so Macs I managed back in the early 2010s. I do remember there was a CD you could burn to re-flash the firmware, though I thought that issue had been resolved by the time CD drives were removed.
    Yup.

    Honestly, this shouldn't have gotten as much noise as it should have which is why we wanted to look more into it after the breathless reports yesterday. The nature of social media gives everybody a bullhorn, as this is not now, and has never been, a major issue popping up in any quantity.
    muthuk_vanalingamelijahg
  • Reply 10 of 15
    miahmiah Posts: 3member
    When at first I called Apple Support, the tech guy said no one had reported my issue: bricking the machine while installing 11.6.1. But while we were on the phone, maybe 20-minutes, he said 3 people had called in with the very same issue. It was enough to raise his concern, issue me a case number, and tell me that if I had to call back I'd be automatically booted up a couple of levels. Fortunately, my local Apple dealer was able to sort the T2 issue, but it still cost me a couple of trips into town, a lost day of work, and $75.
  • Reply 11 of 15
    commentzillacommentzilla Posts: 766member
    Needing a second Mac to fix this issue is ridiculous. I work places where finding a second Mac can be difficult. A better solution would be to use a iPhone or iPad, not just a second Mac. With the M1 Macs it’s hard to see how this couldn’t be possible.
  • Reply 12 of 15
    darkvaderdarkvader Posts: 1,146member
    miah said:
    My 2019 MacBook Pro was bricked while updating to 11.6.1. I'm still under AppleCare and called Apple. They said I'd have to take the computer into my local 3rd-party Apple dealer for evaluation. That dealer found that the T2 was "stuck," but they were able to "reset" it. I presume they used the Configurator method mentioned here, but I'm not sure. The problem is, they charged me $75 for their half-hour of time, a fee I don't feel I should be responsible for since it was Apple's software/hardware that caused the problem. I will take this up with Apple and hopefully get reimbursed. NOTE: Fix restarted my bricked machine and no data was lost.

    Since there's no repair extension yet and Apple doesn't normally reimburse ACSPs for software issues, don't blame the ACSP for charging you $75.  Go after Apple for reimbursement.

    Your local ACSP is no more at fault than you are for Apple bricking your Mac.  And at this point they have no more access to info about this problem than you do.
  • Reply 13 of 15
    miahmiah Posts: 3member
    Darkvader, you misunderstood my comment. I dutifully paid my ACSP upon picking up my repaired machine; none of this was their fault and they have employees to pay for time spent. I previously stated, "I will take this up with Apple" in the hope that Apple will reimburse me for simply running their software installer on their hardware on a machine that's covered by AppleCare. Like Mike Wuerthele said above -- I'm not counting on it -- but I will try.
    muthuk_vanalingam
  • Reply 14 of 15
    SebiakSebiak Posts: 2member
    Mike Wuerthele said:
    Sebiak said:
    My 2019 MacBook Pro with Touch Bar has been bricked while applying Mac 11.8.1, last Tuesday.
    A local certified retailer told me I've to change mother board + Touch ID module. I refused.
    Anyway, after discussing with Apple Support and following its suggestion, I took an appointment to an Apple Store.
    So I still have hope. 
    I'd try the Configurator solution first, if Apple Support didn't tell you to do so.
    I did... And it worked ! Using my mum's old MacBook Air, I followed the "DFU" procedure and the MacBook Pro was living again. So I cancelled my appointment in the Apple Store :)
    command_felijahg
  • Reply 15 of 15
    steingirlsteingirl Posts: 1member
    Both of my daughters' MacBook Pro 2020 computers have been bricked from updating the new OS Monterey. One's was recovered and the other has been sent to repair. It has been 2 weeks since and we have still not received any news about when she will be getting it back or  replaced. All I get is the run around. Apple "Support" has been anything but supportive. What a nightmare.
Sign In or Register to comment.