Big Sur - Black Screen After Update?

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.

Halliday, you said - "However, I highly recommend people not assume there is a hardware failure! I would recommend no such conclusion without good verification!". I strongly hope that full rollback solution is going to appear, but first- all of those solutions with IO board replacement works. Second - they know about issue since 12 of November. Today 20... Is it not ignoring from Apple side?

Why they didn't stop Big Sur distribution on 2013, 2014 devices knowing about the problem? People continue make this great "upgrade" and get a bricks instead laptops..

Pay attention, we do not discuss about some kind of Chinese noname equipment. For about 10 years I owned 4 iphones, 1 airpod, 1 IPod, 2 IPad, 1MBA and 1 MBP. Because I thought that Apple respectable,  reliable company.. And I'm sure that they was but now I become unconvinced.

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…)

Am waiting to hear back from apple store once they finish the repair and i can collect my machine. I will post the receipt here and keep it in case apple does the right thing by starting a quality program and offer free repairs, then i can reclaim the money i paid.

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.

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.

Same here with an IMac 2019. The screen turns black. After a few seconds I hit enter, it turns on again. I have to enter the computer password. It stays on for a few seconds and again... swish... black.

Thats interesting...Apple would normally still issue a receipt (or work confirmation) email which states the service/parts provided and then zero charge to the customer. Would you be kind enough to share a copy of that so I can take it up with Apple store here in Dubai on why I was charged ?

If you fully read what I wrote, arslan77, you’ll see it fully applies.

However, believe what you wish, though that will make little difference in your actual experience, only in how your experience will affect you.

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.

No. It’s like taking your perfectly well running car into the dealership for an oil change, and coming out with the cylinders blown through the engine cover.

My machine was explicitly on the Big Sur approved list. Apple’s update bricked it.

Sorry, RobAtAppleDiscussions, but your attempted analogy simply doesn’t fit, since going from Catalina to Big Sur was such a major upgrade (not simply an update), Apple even changed its major version number from 10 to 11, even though macOS had been version 10 since the very first Mac OS X, not long after Apple bought NeXT.

Apple hasn’t done that since the major upgrade from version 9 to version 10 (with Mac OS X).

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.

No. As I mentioned, it bricked my 2014 13in Macbook Pro. This is a machine explicitly on the approved list. Do not upgrade your 2013 machine. With C.19 closures, I can't even get usable appointment to get the thing looked at.

I do have let Apple push down updates automatically as well. This has frankly worked so excellently over the past years that it's not something I think about. Was Big Sur pushed down on its own? I don't recall.

So, what am I doing now? Apple essentially extorted me into spending $1.1k on an Intel Macbook Air. That's what I'm typing on now. I have Windows XP era Parallel virtual machines that are indispensable. Had I made and kept copies of these as portable VM appliances (instead of jammed into a Time Machine archive) this Air would instead be a Dell XPS13.

As an aside, if you have an Intel Mac, Big Sur is not worth changing to. The Air shipped with Catalina. The first thing I did was load Big Sur - either it was going to run, or the machine goes back to Apple. Big Sur worked, but took hours of additional manual screwing around. All the print drivers broke and required individual manual downloads from Epson and Brother. Parallels itself also needed upgrading to the most current version and explicit re-install.

WOW! I simply can't comprehend what's happening. I was 1 second away of pressing update now :)). Thank god I din't gambled my laptop on this update as I am pretty much dependent on working on it right now. I hope they fix this issue soon. The Late 2013 model was also on the supported list but since it's such a gamble...I prefer to wait.

Thanks for the heads up !