5 ms·

Interestingly I ran into this exact problem with my work MacBook Pro M1 upgrading to Ventura 13.6 and assumed it was a totally isolated incident. I don't have a

Interestingly I ran into this exact problem with my work MacBook Pro M1 upgrading to Ventura 13.6 and assumed it was a totally isolated incident. I don't have a dual-boot setup either, just a single macOS install. The computer was connected to a Thunderbolt Display during the update which I assume had the same effect of changing the refresh rate to something other-than-ProMotion that the linked article mentions. I had to do a DFU restore from another Mac and then run the macOS Sonoma installer from USB, which thankfully detected the existing install and did an in-place upgrade, preserving all of my data. Nothing else worked. I also wasted far too much time trying to get the DFU restore to work before discovering that you cannot use a Thunderbolt cable — it has to be done using a plain USB-C cable, otherwise the Apple Configurator simply won't detect the other Mac.

alsetmusic 3y ago
> I also wasted far too much time trying to get the DFU restore to work before discovering that you cannot use a Thunderbolt cable — it has to be done using a plain USB-C cable, otherwise the Apple Configurator simply won't detect the other Mac. I would have expected a Thunderbolt cable to be required, if either was. This is quite surprising to me. Usually, the more capable (higher bandwidth) cable works if one isn’t supported. I’ll hope to remember this is I ever find myself reviving a bricked Mac in the future.
- vbezhenar 3y ago
  I restored my Macbook just one hour ago with crappy USB-C USB-A cable, god bless the libimobiledevice creator.
- spacedcowboy 3y ago
  I am currently restoring an MBP using Configurator and a thunderbolt cable. You definitely can use one, perhaps your TB cable is buggered ?
- brigade 3y ago
  It's done over USB 2.0 largely because that's simpler than involving newer and faster specs, and partly because that's how the original iPhone did it. My understanding is that all complaint USB USB-C cables should work for USB 2.0, even USB4/TB4 cables, but active TB3 cables might not hook up the USB 2.0 pins.
- phillco 3y ago
  I've used a Thunderbolt cable as well successfully, but one note is that they're very picky about which port you use. On my Mac mini, I had to use the exact port outlined here or it did not show up: https://support.apple.com/guide/apple-configurator-mac/revive-or-restore-a-mac-with-apple-silicon-apdd5f3c75ad/mac https://support.apple.com/guide/apple-configurator-mac/reviv...
  - microtherion 3y ago
    Yes, this is absolutely key. Only one of the USB ports per machine supports this functionality.
- nnf 3y ago
  From Apple’s support page on how to revive or restore after a failed upgrade [1]: > A supported USB-C to USB-C charge cable, such as the one sold by Apple (may not be available in all countries or regions) or a supported USB-A to USB-C cable > The USB-C cable must support both power and data. Thunderbolt 3 cables aren’t supported. [1] https://support.apple.com/guide/apple-configurator-mac/revive-or-restore-a-mac-with-apple-silicon-apdd5f3c75ad/mac https://support.apple.com/guide/apple-configurator-mac/reviv...
JohnMakin 3y ago
Exact same thing happened to me.
- tpmx 3y ago
  What kind of HW?
  - JohnMakin 3y ago
    same specs as OP
    - tpmx 3y ago
      :(
tpmx 3y ago
This is depressing. They clearly have they ability ($$$) to do the required amount of manual QA, but don't. Or there was QA and someone decided that your case still wasn't enough to hold up the release. In my mind, when we pay that ridiculous Apple premium on RAM and storage, we pay for excellent quality in SW/HW. They also need to deliver that quality.
- mort96 3y ago
  Or they did QA but just happened to miss this issue. Most companies would consider "the upgrade sometimes bricks the device" to be a release-stopping bug, I'm betting Apple is among them.
  - tpmx 3y ago
    That would be: not delivering while still charging a premium.
  - krackers 3y ago
    Apple still hasn't put up any official page about the issue though, nor does it appear they've pulled the update. Even if it missed QA, why haven't they made any official comment?
    - deleted 3y ago
      [deleted]
    - FirmwareBurner 3y ago
      You clearly don't know Apple as a company. Last most big companies, they never EVER publicly admit any faults or mistakes with their products (unless forced to by large scale fiascos) because that would damage their perfect brand image. It's why they have comments disabled on all their social media accounts.
      - JumpCrisscross 3y ago
        > they never EVER publicly admit any faults or mistakes with their products Of course they do. They’re just secretive in general, and keep communications edited. Compared to the word salad of modern companies on social media, I find it refreshing. Just fix the problem, issue replacements for those affected and move on quietly.
user9163 3y ago
ya - I cant update my m1 macbook air without going into DFU mode and using configurator to “revive” my macbook. Otherwise it just tells me “Failed to personalize the software update”. Made the mistake of going to the Apple Store where they promptly restored my machine deleting all my data - only to encounter the exact same issue when the next update is shipped. This way you cant even show them that their fix did not actually fixed it permanently.
atregir 3y ago
Also what's with the magic trick of entering DFU mode by pressing the buttons at a very specific time for a very specific number of seconds? Felt like singing a song to some fictional Mac OS gods and hoping for the stars to align for the laptop to show up in the second Mac. Ah, also the port you use for the USB-C cable matters!! Has to be the first from the left? But why? Anw, I followed a video by Mr. Macintosh and managed to get mine up and running, whew.
- adamomada 3y ago
  Well it’s a mode you really don’t want users going into if they didn’t intend to, so it kind of makes sense to only activate if the user has deliberately done an action that would not happen randomly. See Also: entering bootloader mode in android devices
samcat116 3y ago
I've done this several times with a TB3 cable. Has to be the right port for DFU.
magicpointer 3y ago
Also with the M1 Pro MacBook, my LG USB-C monitor broke during the upgrade. Black screen, same on another connected USB-C laptop. Tried different cables, unplugging power from the monitor and factory reset on the monitor, no luck. Other inputs like HDMI and DisplayPort still work. I don't think the breakage during the upgrade is a coincidence. I would really advise against having anything connected to the Macbook during upgrades, except the charger...
spondylosaurus 3y ago
The exact same thing happened to me (M2 Pro) and I had to take the exact same steps to fix it! Thankfully my data was also intact after the DFU revival, but I also thought it was an isolated incident—that maybe the battery ran dry before the update finished and something got corrupted. But my spare monitor must've been the culprit.

alsetmusic 3y ago

> I also wasted far too much time trying to get the DFU restore to work before discovering that you cannot use a Thunderbolt cable — it has to be done using a plain USB-C cable, otherwise the Apple Configurator simply won't detect the other Mac. I would have expected a Thunderbolt cable to be required, if either was. This is quite surprising to me. Usually, the more capable (higher bandwidth) cable works if one isn’t supported. I’ll hope to remember this is I ever find myself reviving a bricked Mac in the future.

vbezhenar 3y ago
I restored my Macbook just one hour ago with crappy USB-C USB-A cable, god bless the libimobiledevice creator.
spacedcowboy 3y ago
I am currently restoring an MBP using Configurator and a thunderbolt cable. You definitely can use one, perhaps your TB cable is buggered ?
brigade 3y ago
It's done over USB 2.0 largely because that's simpler than involving newer and faster specs, and partly because that's how the original iPhone did it. My understanding is that all complaint USB USB-C cables should work for USB 2.0, even USB4/TB4 cables, but active TB3 cables might not hook up the USB 2.0 pins.
phillco 3y ago
I've used a Thunderbolt cable as well successfully, but one note is that they're very picky about which port you use. On my Mac mini, I had to use the exact port outlined here or it did not show up: https://support.apple.com/guide/apple-configurator-mac/revive-or-restore-a-mac-with-apple-silicon-apdd5f3c75ad/mac https://support.apple.com/guide/apple-configurator-mac/reviv...
- microtherion 3y ago
  Yes, this is absolutely key. Only one of the USB ports per machine supports this functionality.
nnf 3y ago
From Apple’s support page on how to revive or restore after a failed upgrade [1]: > A supported USB-C to USB-C charge cable, such as the one sold by Apple (may not be available in all countries or regions) or a supported USB-A to USB-C cable > The USB-C cable must support both power and data. Thunderbolt 3 cables aren’t supported. [1] https://support.apple.com/guide/apple-configurator-mac/revive-or-restore-a-mac-with-apple-silicon-apdd5f3c75ad/mac https://support.apple.com/guide/apple-configurator-mac/reviv...

JohnMakin 3y ago

Exact same thing happened to me.

tpmx 3y ago
What kind of HW?
- JohnMakin 3y ago
  same specs as OP
  - tpmx 3y ago
    :(

tpmx 3y ago

This is depressing. They clearly have they ability ($$$) to do the required amount of manual QA, but don't. Or there was QA and someone decided that your case still wasn't enough to hold up the release. In my mind, when we pay that ridiculous Apple premium on RAM and storage, we pay for excellent quality in SW/HW. They also need to deliver that quality.

mort96 3y ago
Or they did QA but just happened to miss this issue. Most companies would consider "the upgrade sometimes bricks the device" to be a release-stopping bug, I'm betting Apple is among them.
- tpmx 3y ago
  That would be: not delivering while still charging a premium.
- krackers 3y ago
  Apple still hasn't put up any official page about the issue though, nor does it appear they've pulled the update. Even if it missed QA, why haven't they made any official comment?
  - deleted 3y ago
    [deleted]
  - FirmwareBurner 3y ago
    You clearly don't know Apple as a company. Last most big companies, they never EVER publicly admit any faults or mistakes with their products (unless forced to by large scale fiascos) because that would damage their perfect brand image. It's why they have comments disabled on all their social media accounts.
    - JumpCrisscross 3y ago
      > they never EVER publicly admit any faults or mistakes with their products Of course they do. They’re just secretive in general, and keep communications edited. Compared to the word salad of modern companies on social media, I find it refreshing. Just fix the problem, issue replacements for those affected and move on quietly.

user9163 3y ago

ya - I cant update my m1 macbook air without going into DFU mode and using configurator to “revive” my macbook. Otherwise it just tells me “Failed to personalize the software update”. Made the mistake of going to the Apple Store where they promptly restored my machine deleting all my data - only to encounter the exact same issue when the next update is shipped. This way you cant even show them that their fix did not actually fixed it permanently.

atregir 3y ago

Also what's with the magic trick of entering DFU mode by pressing the buttons at a very specific time for a very specific number of seconds? Felt like singing a song to some fictional Mac OS gods and hoping for the stars to align for the laptop to show up in the second Mac. Ah, also the port you use for the USB-C cable matters!! Has to be the first from the left? But why? Anw, I followed a video by Mr. Macintosh and managed to get mine up and running, whew.

adamomada 3y ago
Well it’s a mode you really don’t want users going into if they didn’t intend to, so it kind of makes sense to only activate if the user has deliberately done an action that would not happen randomly. See Also: entering bootloader mode in android devices

samcat116 3y ago

I've done this several times with a TB3 cable. Has to be the right port for DFU.

magicpointer 3y ago

Also with the M1 Pro MacBook, my LG USB-C monitor broke during the upgrade. Black screen, same on another connected USB-C laptop. Tried different cables, unplugging power from the monitor and factory reset on the monitor, no luck. Other inputs like HDMI and DisplayPort still work. I don't think the breakage during the upgrade is a coincidence. I would really advise against having anything connected to the Macbook during upgrades, except the charger...

spondylosaurus 3y ago

The exact same thing happened to me (M2 Pro) and I had to take the exact same steps to fix it! Thankfully my data was also intact after the DFU revival, but I also thought it was an isolated incident—that maybe the battery ran dry before the update finished and something got corrupted. But my spare monitor must've been the culprit.