Big Sur - Black Screen After Update?

I have a 2014 Macbook Pro 13" Retina that I have installed the new Big Sur OS, I did make sure there was enough space to install beforehand which there was.


I now have a mac that is powered up (apple logo on lid is lit up) but the screen is black and I have no idea what to do?


I don't know of it is still installing the OS or if its locked or something else. I set off the install and just left the laptop to do it's thing


Any help would be greatly appreciated.



Posted on Nov 14, 2020 3:21 AM

Reply
Question marked as Top-ranking reply

Posted on Dec 19, 2020 5:20 PM

The solution I have found is to hold down Option when restarting. This will came up with available hard drives and "Big Sur" (The bootable partition that has been created for the upgrade). Select your main hard drive and it should boot up normally. Not that this only worked with my Apple keyboard - my third party keyboard wasn't recognised by OSX until later.


Hopefully this works for you.

123 replies

Nov 19, 2020 1:05 PM in response to Halliday

I understand your intention. I think it’s arrogant to assume that people don’t understand the implications of installing software, and to think that you need to explain it to them.


People are here because their expensive laptops are broken after a software update promoted by Apple (a fair reason to be upset). They are looking for a fix, not a demeaning lecture on responsibilities or a debate. You are not helping.

Nov 19, 2020 8:44 PM in response to elmarklimov

I simply care about truth, elmarklimov.


While Apple is not here, there are some of us with experience in such matters, and we are trying to help you all, as best we can.


Some of the answer is that not all the systems experiencing problems are actually experiencing hardware failures.


Unfortunately, there have been some that have experienced verifiable hardware failures.


However, I highly recommend people not assume there is a hardware failure! I would recommend no such conclusion without good verification!


The analogy I shared was for those that believe that they truly have hardware failures, and are, basically, grieving their loss, and, all too naturally, looking for the kinds of answers one often looks for when in grief; but are, perhaps, looking for the wrong sorts of answers (as, all too often, occurs with those going through the grieving process.)


This is not at all any sort of dismissal or “ignoring” of the real pain of loss, of those people actually experiencing such a loss!

Nov 19, 2020 9:40 PM in response to mrokloricred37

Well, APPLEAL, in general, at least in the past, upgrades were not shown as an update: one had to actually look for the new macOS within the Mac App Store.


Knowing this, I didn’t even look for Big Sur in the usual macOS software update, but went straight to the Mac App Store.


If this major upgrade was, in fact, offered by way of the usual update mechanism, that may have been a tactical error on Apple’s part.


Unfortunately, because I went straight from the Mac App Store, I can neither confirm nor deny whether the Big Sur major upgrade was offered through the usual update mechanism.

Nov 19, 2020 11:05 PM in response to elmarklimov

Apple did extensive Alpha and Beta testing, including on such affected systems («2013, 2014 devices[MacBooks]»), elmarklimov.


Admittedly, Apple’s Alpha tests would, likely, have been performed on less worn systems.


However, any Beta testers running such systems («2013, 2014 devices[MacBooks]») would have, likely, been more worn, from actual day to day use.


Apparently, this installation issue was, somehow, not seen in any of those tested systems, for, otherwise, these systems would not have been on the hardware list, or the issue would have been corrected before release.


That’s simply standard operating procedure, for such things.


Unfortunately, we have now seen an installation issue with more worn systems.


We have, most certainly, not seen this issue in all «2013, 2014 devices[MacBooks]». Only a subset of such.


Of course, that’s not to say that that subset is “acceptable” to Apple.


I certainly never said anyone—certainly not Apple, but neither I nor other longtime user-contributors, here—were, in any way, «ignoring» this issue.


You have been the only one I have seen, here, use that term, in regard to this issue.


How you interpret what is going on is simply up to you.


Have you not noticed the Apple document, and other articles reporting upon Apple’s actions, with regard to those affected systems («2013, 2014 devices[MacBooks]»), shared by APPLEAL?


Apple is taking action.


(I know. You’ll say something like “too little, too late”. Oh well…)

Nov 19, 2020 11:13 PM in response to Halliday

With your logic of “worn” systems, (i/o board in this case) would you recommend try installing big sur again once a brand new i/o board has been placed in MBP late 2013 ??

and i am talking about the exact build of bigsur that caused this damage in the first place (not the updated build which some users are reporting).


if not, why not? (Now that i/o board is not worn anymore)


if Yes, well thats not what my local apple store technicians are advising me - they want me to go back to catalina or high sierra after replacement.


I am sorry but things dont add up with your logic.

Nov 19, 2020 11:31 PM in response to arslan77

They’re playing it safe, arslan77.


Even before I read what your «local apple store technicians are advising» you, I, too, wasn’t going to go “out on a limb” by telling you, unequivocally, to do the upgrade with the initial installer.


There are simply too many variables, such as wear on other components of your system, including potential affects of having had a hardware failure in the I/O Board (hence, potentially, additional wear upon other components of your system).


(Actually, it is also well known, by various technicians that deal with various hardware, including automobiles, that replacing some parts with new ones, can place additional or new strain upon the old, non-replaced parts.)


In fact, what I have written here is completely consistent with my earlier logic, which is, likewise, consistent with the Alpha and Beta testing protocols.

Nov 21, 2020 3:20 PM in response to elmarklimov

Exactly the same thing happened to me. My MBP 2014 was explicitly on the Big Sur supported list. The update bricked it. After spending two hours on waiting and trying different things with Apple support, the implication is that it was my fault. The only offer of recourse was to take it into an independent shop.


This isn’t right. Apple needs to address this. They’ve done insufficient compatibility testing on Big Sur. They broke my machine. Apple needs to fix this.

Nov 21, 2020 10:40 PM in response to RobAtAppleDiscussions

That would be speculation, RobAtAppleDiscussions.


Additionally, I’m no lawyer!


However, since Microsoft makes even fewer claims about what systems are or are not compatible, and Windows 7 to Window 10 was not claimed (as far as I recall) to be quite like the major upgrade that Apple claimed for Catalina to Big Sur, I would say there is a fair case for similar treatment of Microsoft.


In neither case is the upgrade required by the offering company. You perform the upgrade on your own volition.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Big Sur - Black Screen After Update?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.