I would like to know if Startup security utility was set to same settings in both cases .... could be something to do with since I was doing both on 12.6 to 12.7 (Startup security utility changed and ProMotion disabled ... ) .... just saying ....
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.
M1 Max black screen at boot after updating Ventura 13.6
- Thread starter Renderwarrior
- Start date
- Sort by reaction score
I did not change Startup security settings on both, but the bricked one had FileVault enabled, the surviving one not.
As another data point, all four of the MacBook Pros I experienced this issue with had FileVault enabled.
As I described in my page-2 post earlier: my MBP-m1 bricked during the update from Ventura v13.52(?) to v13.6. Reading more recent posts I will add that FileVault was not enabled, however ProMotion was disabled while using an external display @60hz at home. When I updated I was away on a trip and not connected to an external monitor, using just the internal laptop display. Not sure if ProMotion was still disabled while using the internal display, but it wouldn't surprise me if it was running @60hz.
To me first time happened from 12.6.x to 12.7 with for sure Promotion disabled. You can download 12.6 or 12.7 (depends on you backup version you would like to restore) IPSW and do restore via DFU and use backup for transfer ....
12.7 is still affected by this bug ! 12.6.x is not and you need to downgrade via IPSW and Apple configurator !
Another thing is: you had disabled Promotion when you had no external
monitor connected and Promotion enabled while monitor connected… this setting has memory for each setup so this is why you got bricked when there was external monitor and you did restart !
Nope, i had ProMotion enabled when i had no external Monitor connected and when i switch to my monitor, it changes to 75 Hz.
In my understanding it bricks, if you have ProMotion disabled (external Monitor or not), right?
In my understanding it bricks, if you have ProMotion disabled (external Monitor or not), right?
Problem is: I can only revert to a 12.7. TM Backup and everything before that does not work. Or is there a way to downgrade without any data loss/wiping the system?
Yes this is what I am telling you…
Enabled Promotion won’t brick….
You need to have it enabled in both situations with and without external monitor …. Macos remembers setting per situtation not generally …
Oh, then i misunderstood you, thanks for the correction!
So the solution would be to manually also enable ProMotion, while i am connected to my external Monitor?
Will this prevent the brick, even when i restart with the monitor?
Yes, Promotion needs to be enabled both times, with and w/o external monitor connected ! Maybe also if you have different monitors connected with each of them it needs to be enabled to prevent brick !
But when i connect to the external Monitor (a 27 inch 2k 75Hz one), i dont see the ProMotion option anywhere in the display settings. What do i do?
Thanks for the help! But the thing is, the ProMotion option only appears, when i change my main monitor to my Internal MBP Display (mirrored to the external Monitor). But then the scaling is totally off and the screen sharing introduces latency)Click on Built-in display on top and change Refresh rate for it to Promotion
When i have the external monitor set as my main display, the Promotion options vanishes again (on the section for the internal display).
Do you know what i mean?
Oh I understand now.... never tried with mirror always using them as separate and had this option .... So it is obvious now that even mirror can't work with Sonoma FW (12.7, 13.6, Sonoma and even earlier versions if they were updated via Terminal command since Sonoma is available ) .... There is a lot configurations what works and what not .... !
They really need to fix this thing and it is very widespread ! !!!!!
Latest findings are collected here: https://github.com/AsahiLinux/docs/wiki/macOS-Sonoma-Boot-Failures
(This is not Asahi-Linux specific but is common MacOS bug that is very wide and affects only MBP 14" and 16" with Apple silicone inside ! )
Last edited:
Ahhh okay, i am beginning to understand.
So you mean, if i use them as separate displays (external as the main one with the dock tho), and have the ProMotion setting enabled in the tab for "Internal XDR Display" (but not on the external), am i safe then?
Then i would just do it like you with seperate ones (but simply just not use Macbook Display and let it be around in the right corner).
So you mean, if i use them as separate displays (external as the main one with the dock tho), and have the ProMotion setting enabled in the tab for "Internal XDR Display" (but not on the external), am i safe then?
Then i would just do it like you with seperate ones (but simply just not use Macbook Display and let it be around in the right corner).
Yes, until Built-in one is Promotion it is safe
Joke of the day would be: “Until Apple Promotion is ON, promotion of Sonoma is success !” but I believe this is not their intend, but very bad QA ….. :/
This also worked for me, thanks! I did not select an ISPW for step 2 (just right clicked on the device and selected "Revive"), and got a popup that "A software update is required for this device." I selected "Quit and Update," then repeated step 2 without a specific ISPW and it worked.
This just happened to me this afternoon, when updating to the latest version of Ventura (I believe I was on 13.5 and trying to install 13.6.1). My 2021 14” M1 Max is completely bricked, with the Apple logo and black screen; it bricked in the middle of the install. I can’t even boot into Recovery mode.
I was connected to an external 27” LG monitor during the failed update. Does anyone know if that matters?
In nearly 9.5 years of owning several MacBook Pros, this is the first time I’ve ever bricked on an update. I had just done a Time Machine a few minutes prior to the attempted update.
Now I’m at the Apple Store, and they are attempting to wipe and install Sonoma.
I was connected to an external 27” LG monitor during the failed update. Does anyone know if that matters?
In nearly 9.5 years of owning several MacBook Pros, this is the first time I’ve ever bricked on an update. I had just done a Time Machine a few minutes prior to the attempted update.
Now I’m at the Apple Store, and they are attempting to wipe and install Sonoma.
Last edited:
I could not agree more - I am surprised and disappointed that this happened to my machine today. I’ve never seen anything like this in 9+ years of owning Macs personally, as well as additional time spent working with Macs for an employer. This type of problem would be considered unusual even for a Windows machine in Microsoft’s peak “blue screen of death” era.
I guess in the Windows world, this would be as though a Windows update was somehow over-writing the BIOS with a version containing a bad bug. There does seem to be something to be said for keeping BIOS/firmware revisions “divorced” from operating-system revisions. The Apple approach clearly has some serious land mines built in. Still in shock that these recent serious bugs ever made it out into the hands of the public.