Big Sur - Black Screen After Update?

Car analogies do not help and they never have. If you can't make your case without an analogy, you need to work on your communication skills. You're not helping anybody here.

Halliday wrote:

Unfortunately, this is, often, a matter of experience.

Those with too little related experience, can have difficulty understanding the concept, unfortunately.

Well stated :)

Guys, let’s find a solution here and not this forum typical bashing.

lets look at the target picture: how do I revive my MacBook?

I can't believe this is happing to so many people and Apple have nothing to say!

https://discussions.apple.com/thread/252034110?answerId=254196813022#254196813022

just FYI and some salt at your optimistic thoughts about the issue...

Me too, I thought that waiting three months after the initial release would have allowed enough time for them to fix the issue but no. One very expensive 2019 MBP brick!

For me it did show as an “update” and now I have a brick instead of a working laptop.

Have you installed or run any "cleaning", "optimizing", "speed-up" or anti-virus apps on your Mac?

Did you manage to do smth about the problems you were facing? What year was your machine?

Thanks

I'm in the same((Macbook Pro Mid 2014. Black screen of death and nothing else(Official support says - You update OS on your own risk!!!!)) You hear that?))They broke my device and says that it is my problems because mbp is warranty out..... i'm in shock!

[Edited by Moderator]

Thank you for your reply. Sorry, but I have to disagree with you. Updates is NOT a trailer.

1. I bought this notebook with OS preinstalled.
2. Apple recommends update their devices. Isn't it?
3. Following manufacturer recommendations I did it. I didn't do something wrong or illegal I just make an another suggested update, which caused (probably) physically damage of a IO board. If the update turned out to be disastrous for some devices. Where is my fall?

I saw it within the Apple Support Communities fora. In a discussion much like this one. (It’s one of the problems with have multiple, disjointed discussions on the very same topic.)

If there is actual, observable damage, mknell, then, yes, it is “permanent”. Fixable only by replacement of components, or the entire I/O board.

However, such physical damage need not be the only cause for the malfunction.

I thought I am following the various discussions, not seeing any "indication" that there was some firmware-like fix

for the i/o board issue. I would be glad to get an exact link.

To me the i/o board is not working at all and it has been caused by the Big Sur installation,

as Catalina last patch was still running fine incl. reboot and all components from the i/o board

working before one day later the Big Sur installation ended after a reboot triggered within the installation

routine in the Black screen, that only disappears if the i/o board is unplugged.

So if there would be a "firmware-like fix" avoiding the i/o board needed to be replaced

I would like somebody to pointing out how that fix can be applied.

Thanks!

No, elmarklimov. You did nothing «wrong or illegal».

That is, most certainly, not the point.

It’s just as with pulling the trailer: nothing «wrong or illegal».

The manufacturer’s recommendation is to keep your Operating System (OS) up-to-date, by way of updates.

Going from Catalina (10.15.x) to Big Sur (11.0.x) is not an update, but an upgrade. A major upgrade.

It is like taking a car that hasn’t been pulling a trailer, and, “suddenly”, deciding to start pulling said trailer.

Just as a car can seem to be running “just fine”, even though it harbors a “borderline failure”, which can become manifest by changing its load (towing a trailer), the very same can occur with any other hardware, such as computer hardware.

You simply were not aware of the “borderline” failure.

The new “load” of a new OS, could have just as well been the new “load” of a new, “heavier”, more demanding application.

It’s no more, but, also, no less your “fault” than deciding one day to use your car to tow a trailer, that you haven’t been doing, even though the trailer is within the rating of your car (at least when in very good condition).

Apple tested this OS upgrade (Big Sur) on such very good condition MacBook Pros (and others).

Such were within the “rating” for this OS upgrade.

“Worn” systems may be on the borderline.

No one can test for all possible conditions of “wear”.

Unfortunately, mknell, I can not remember which of these Big Sur “broke my” MacBook Pro (or whatever) discussions I saw it in. Nor can I recall what the non-hardware solution was.

However, I do seem to recall it having to do with rebooting back into Catalina.

At the very least, rebooting back into Catalina can be a reasonable test for whether the I/O Board is actually, physically damaged.

(I’m not sure, but I seem to recall that even going into Catalina, it may take more than one boot attempt to succeed.)

I do wish I could provide a link for y’all!