During Install, stuck on Black Screen

[lemonkid]

Most people having the issue report that they had an SD card in a card reader.
I first thought this was not the case for me, but then I noticed my Transcend Jetdrive was in a USB hub I attached to one of the USB ports :-(, so I can count myself in.
So if one wants to install Big Sure on a MBP 13 late 2013/mid 2014 (or to be sure any other model) I recommend to remove all SD cards.

When I read this yesterday I had to sigh. Even though I'm not affected it makes me angry. Reading on I see that some users with different machines and some stating that they had nothing plugged in are also victim of this issue.

However it seems to me not unlikely that 'having something plugged in', may play a role in this bricking update. I am one of the first owners of a MacBook Pro late 2013. And when I just bought it, there was an issue with inoperable machines. Somehow they didn't respond anymore. After waking up from sleep the machines just slept on. Mine was affected too.

Later some users found out that 'plugging something in' would prevent this. The effort to safe power had made the developing technicians create a computer that would safe so much battery power, that it simply stopped responding to the keyboard. By 'putting something in' this could be prevented.

A firmware update took care of the problem. But there is reason to believe that the present day problems with this Big Sur update could be related to those past day problems and could have bricked the computers.

 

[SamSi]

In my case disconnect the I/O board works. Genius Bar staff helped me disconnect it and it finished upgrade. It brick again after reconnect I/O board. Will try downgrade to Catalina in the weekend to see if the I/O board will work again.

 

[mknell]

I posted the below on

MacBook Pro bricked after failed Big Sur … - Apple Community

discussions.apple.com

Folks, one last update from myself.
Might be it gets deleted again by the moderators, but at
least you receive it via email.

As you read it tried all suggested NVRAM, SMC reset, unplugging battery, running battery down
to zero etc. suggestions, but for my MBP Mid 2014 it did not work.
During my initial installation using the installer downloaded via software update
on top of Catalina with latest patch applied after time maschine backup & CCC clone,
I had my transcend jetdrive lite 128GB SD card inserted in the card reader.
This seemed to have triggered somehow during the installation process
a HARDWARE defect BY THE BIG SUR INSTALLATION PACKAGE.

As a workaround I unplugged i/o card then reinstalled Catalina and on top of that Big Sur
using an external USB keyboard and mouse on my functional left USB port.
Today my replacement i/o board I bought on ebay Germany (8.90 EUR) and thermal paste
(2.99 EUR) arrived and I successfully replaced the fried i/o board
by the new one.

Et voila after NVRAM, SMC reset I had a successful reboot.
Everything is working fine again (WLAN, Bluetooth, HDMI port and SD Card reader even with my JetDrive 128GB).
Big Sur performs pretty fast on my MBP Mid 2014 now.

Summary: if your i/o board of a MBP 13 inch Late 2013/ mid 2014
has been fried by the Big sur installer it might be coinciding
with you having an SD Card or other peripherals connected to the right
side of your MBP.
If the i/o board has been permanently damaged (try on your own risk)
to disconnect the i/o board (see step 18) of the ifix guide
Try to finish your reinstallation or installation of the os
reconnect the i/o board
if black screen continues even after all the tipps like NVRAM/ SMC reset etc.
buy yourself a replacement i/o board
use the ifixit guide to replace your i/o board if you are confident
or ask an authorized Apple repair shop to do it for you
then reboot (NVRAM, SMC reset) and if you are lucky like me
you have fixed the black screen issue permanently.

For me the total cost in EUR incl. tools, thermal paste & i/o card
did not accumulate to 25 EUR as I could do the replacement
myself using ifixit guide.

I still think it is a shame that hardware damage has been
obviously caused by a OS upgrade package, but to be honest
Sh.... happens

What I am grateful for is that so many Mac users helped
putting information together for their fellow Mac users
to collect evidence, give advice what works and what does not.
I like you guys!

What I am reluctant about is that obviously like I read happened
in the past, posts on the apple discussion forum incl. my summary
have been deleted by moderators even though there was nothing
wrong with them.
What I also do not like is what happened to a lot of users
that were contacting Apple support and adviced that HW damages
were their issue or that a logic board replacement for several hundred
dollars would be needed.

Macbook Pros even from 2013 or 2014 are still fast & reliable devices
for most use cases.
Even if some sh.... hits the fan as it did for me. If one can fix the
caused damage for such a small amount of money, I think
it is not ok to tell customers nothing about it.

And I am not talking about liability claims. I am also not directly
blaming Apple to be responsible for shipping green bananas
and being liable for hardware damages.
But one could be more relaxed about analysing what happens
and what can be done about.
Especially during a global pandemic people in Ukraine, Brasil, Belgium,Italy, France,
UK, Denmark, USA & Germany were cooperating with each other to help each other
analysing. Would it be to bad for Apple support to help these people?
Some of them do not even have access to a repair shop near them.

Apple users like Apple hardware & software. They also like it to be pretty reliable
and they like that support is not only given by Apple but also by fellow customers.

Apple, please do not upset your customers by deleting simple
information exchange on this forum.
The information flow cannot be stopped anyway.
The same information you deleted here was flowing on external forums around the
world anyway.

The Apple management should take care that this does not repeat itself.
Even if mistakes were made, it is not a shame to say sorry.
Even if Apple does not want to pay for damages or does not feel liable
you could give correct & appropriate information flow between your customers
a chance. Apple can also use the evidence to find the root cause and fix it.
Nothing is wrong about making mistakes, but hiding information is wrong.

I wish all people affected good luck in fixing your situation as fast and cheap as possible.

Thanks, Markus!

 

[na1577]

It’s very disappointing that Apple has not, and will likely not, acknowledge this issue. It is not a coincidence that hundreds of 2013-2014 13” MBPs have failed after trying to install Big Sur. I’m sure some people are fine using this to justify an upgrade, but as someone who can’t afford to replace my laptop right now, this does nothing but leave a bad taste in my mouth. I was planning on upgrading to a new MacBook Air once my financial situation improved, but I don’t really want another Mac after seeing the way Apple treats their customers when Apple’s buggy software is at fault.

I don’t really think it’s fair to ask customers to pay for this repair at all, but I would still pay a reasonable price to have the I/O board replaced because that’s how badly I need a working laptop again. But seeing the $700 figure people are being quoted for a full logic board replacement is absolutely ridiculous. I have a Genius Bar appointment coming up soon and I’m going to ask them to disconnect the board just to see if it will boot, but I don’t anticipate them actually fixing the issue.

 

[mknell]

It’s very disappointing that Apple has not, and will likely not, acknowledge this issue. It is not a coincidence that hundreds of 2013-2014 13” MBPs have failed after trying to install Big Sur. I’m sure some people are fine using this to justify an upgrade, but as someone who can’t afford to replace my laptop right now, this does nothing but leave a bad taste in my mouth. I was planning on upgrading to a new MacBook Air once my financial situation improved, but I don’t really want another Mac after seeing the way Apple treats their customers when Apple’s buggy software is at fault.

I don’t really think it’s fair to ask customers to pay for this repair at all, but I would still pay a reasonable price to have the I/O board replaced because that’s how badly I need a working laptop again. But seeing the $700 figure people are being quoted for a full logic board replacement is absolutely ridiculous. I have a Genius Bar appointment coming up soon and I’m going to ask them to disconnect the board just to see if it will boot, but I don’t anticipate them actually fixing the issue.

Couldn’t agree more.

And I already ordered an Mbp M1 prior to this incident...
... which I will not cancel.

I think Apple‘s behavior is driven by fearing liability claims.

 

[na1577]

Couldn’t agree more.

And I already ordered an Mbp M1 prior to this incident...
... which I will not cancel.

I think Apple‘s behavior is driven by fearing liability claims.

I suspect you’re right. If I were Apple, I would just position an I/O repair as a one time courtesy without admitting that Big Sur was at fault. The cost of repairing the affected machines is probably not that large considering how few people likely use this machines that are this old, and not every unit was affected. Oh well. It’s a shame they’re continuing to distribute this update to people who may not be aware that this is happening.

Thanks for the instructions on how to get the laptop running again, Markus! Perhaps I’ll try repairing mine after my appointment, if Apple can’t help me out.

 

[ajsilesl]

Hello everyone, I have good news or so I think. After giving it many turns and many attempts during this week, I have managed to start my MacBook several times, the first 2 I continue with the installation of Big Sur and when it restarted it was frozen again The 3 and last, (I have not turned off or restarted anymore, I have no thoughts of doing it), this morning and I have been working with him all day. I keep it active with the "Amphetamine" App and connected to the charger all the time.

I get to the point, the sequence I have followed to get it started has been.
1- Portable with the lid, (monitor), closed
2- Connect charger until battery is complete
3- Disconnect charger for at least 30min
4- Open lid and turn on

I hope you can reproduce and get like me to start it.

Hopefully Apple will come out with a definitive solution shortly, I'll try not to turn mine off until then.

————————————————————-

Hola a todos, tengo buenas noticias o eso creo. Después de darle muchas vueltas y muchos intentos durante esta semana, he conseguido arrancar mi MacBook varias veces, las 2 primeras continúo con la instalación de Big Sur y al reiniciarse se quedó nuevamente congelados La 3 y última, (no he apagado ni reiniciado más, ni tengo pensamientos de hacerlo), está mañana y he estado todo el día trabajando con él. Lo mantengo activo con la App “Amphetamine“ y conectado con el cargador todo el tiempo.



Voy al grano, la secuencia que he seguido para conseguir arrancarlo ha sido.

1- Portátil con la tapa, (monitor), cerrado

2- Conectar cargador hasta completar batería

3- Desconectar cargador al menos 30min

4- Abrir tapa y encender



Espero que podáis reproducir y consigáis como yo arrancarlo.



Esperemos que Apple saque una solución definitiva en breve, intentaré no apagar el mío hasta entonces.

 

[vtboyarc]

So, I have a late 2013 MBP and have been holding off on updating.
What I’m getting from this thread is that as long as I only have it connected to power, nothing else, no peripherals etc, I should be ok to update?
someone please correct me if I’m wrong

 

[ajsilesl]

So, I have a late 2013 MBP and have been holding off on updating.
What I’m getting from this thread is that as long as I only have it connected to power, nothing else, no peripherals etc, I should be ok to update?
someone please correct me if I’m wrong

Not my late 2013 MBP did the installation as you say and it crashed

 

[vtboyarc]

Not my late 2013 MBP did the installation as you say and it crashed

Yikes. Well, guess I’m not updating to Big Sur then. Bummer.

 

[jjcv]

I have a mid-2014 MBP and not risking an upgrade yet.

I see there is an updated build out today for Big Sur. Not sure if it addresses this issue.

 

[arslandar]

Hi.

I am having a similar issue. Macbook pro 13" with retina display late 2013 - upgraded from El Capitan to Big Sur on the day it was released...had download interruptions > restarted > black screen for hours at 12 min remaining mark > turned off and turned on > installation continued > and eventually got completed and I was able to login. However I was presented with a black screen at boot right after first restart. (I had windows 10 installed via boot camp too). Tried smc reset, recovery mode, PRAM reset several times, nothing worked. Called up apple support with whome SMC reset seemed to work. But the behavior remained erratic and unpredictable. Mac would boot to black screen 7 out of 10 times - and will boot successfully randomly. I tried reinstall - same issue - did clean install after erasing disk volumes and containers (clean slate including reformatting OS X Extended format to the new APS format) - same issue - tried recovery mode reinstall - same behavior - tried internet recovery model reinstall - same behavior.

I finally decided to go back to the original OS that came with my mac using the specific recovery mode startup key combination and it did reinstall MAC OS Mevericks but went through similar cycle (black screen during install forcing me to turn off and on), was eventually able to complete installation. But unfortunately, the behavior remains the same... if I restart the machine 10 times, it will successfully boot perhaps 5 out of 10 times - and rest of the times will go to black screen. Similar behavior when using SHUT DOWN option.

The diagnostic option (pressing and holding D while starting) shows no error. Have run disk utility multiple times with no issues reported in start up disk.

Given I have tried clean install multiple times, with and without wipe cleaning disk and have now even gone back to Mavericks, I think something during the update of Big Sur has caused a permanent damage to macbook hardware causing this unpredictable behavior. I have scheduled an appointment with apple authorized repair shop - lets see what they tell me but I am unwilling to pay for the repair as it has been caused purely by the big-sur update.

For all folks having the black screen at boot issue, especially the ones with late 2013 model, I suggest keep retrying the key combinations at the startup even if it does not work, because if what I have faced is a wide spread issue, one particular try would probably bring the mac back to life, but unfortunately, only temporarily. So a permanent fix (after a proper diagnosis) will still be required.

An update guys - Took my MBP to apple store. The lady at the genius bar immediately recognized the issue as I started to describe it and told me she has received 4 such cases in last 2 days. I left the machine with them, got a call the same day, telling me i/o board needs replacement and that will cost me $$$. I argued but in vain and asked to speak to supervisor. Got a call from supervisor the next day, and while he was sympathetic about what happened, he said he has no instructions from apple management to do a free repair. So I have given a go ahead to order the part and get it repaired and will eventually paying for it. However, I would keep the repair receipt just in case apple launches a quality program in few weeks/months so I can make a claim. Not happy at all - because apple clearly knows its their fault but refuses to accept it.

 

[na1577]

An update guys - Took my MBP to apple store. The lady at the genius bar immediately recognized the issue as I started to describe it and told me she has received 4 such cases in last 2 days. I left the machine with them, got a call the same day, telling me i/o board needs replacement and that will cost me $$$. I argued but in vain and asked to speak to supervisor. Got a call from supervisor the next day, and while he was sympathetic about what happened, he said he has no instructions from apple management to do a free repair. So I have given a go ahead to order the part and get it repaired and will eventually paying for it. However, I would keep the repair receipt just in case apple launches a quality program in few weeks/months so I can make a claim. Not happy at all - because apple clearly knows its their fault but refuses to accept it.

How much are they charging you for the I/O board repair? That's a good suggestion regarding the repair receipt.

At least Apple is now acknowledging that it is in fact an issue:

Apple Offers Instructions on What to Do if macOS Big Sur Causes Installation Errors on 2013 and 2014 MacBook Pro

Following the release of macOS Big Sur last week, a number of 2013 and 2014 MacBook Pro owners found that the update bricked their machines. Affected...

www.macrumors.com

Of course we all know those steps don't actually do anything for this issue, but I thought Apple was for sure going to just let this slide under the radar like the Macs with the T2 issues.

 

[HDFan]

apple clearly knows its their fault but refuses to accept it.

Macbook pro 13" with retina display late 2013

How is the failure of a hardware component on a 7 year old machine apples' fault?

 

[mknell]

How is the failure of a hardware component on a 7 year old machine apples' fault?

Very simple: Because the HW failure is not a simple hardware defect. It is a firmware update applied by the Big Sur installer, prepared, tested and released explicitely to be applied to these models of A1502 MBP 13 Late 2013 & Mid 2014 causing the need to exchange the i/o board.
I guess the will not admit it, but in fact that is what happened.
It cannot be a coincidence if this happens to hundreds of MBP 13 Late 2013 & Mid 2014 worldwide after
installing the Big Sur update

Furthermore Beta testers reported these issues including going into authorised Apple repair shops getting
it fixed during the beta phase, so it should have been known to Apple development & management.
That exactly is also the source for the solution path of exchanging the i/o board if simple unplugging during
the installation did not work.

One could still argue if the hardware no damaged needs to be replaced by Apple without charge, but
I think one should not argue that these explicit i/o board damages were not caused by Big sure installer.

I fixed the hw issue on my own expense successfully and writing this comment from my MBP 13 Mid 2014
with a nicely performing Big Sur installed on it.

P.S. I wrote an email to Craig Federighi yesterday
because I am especially upset about the moderators in the Apple community
hiding information to cover liability claims.
If they do not want to pay the repairs, ok.
But at least they should give affected customers correct and transparent information about what customers can do.
They also should stop telling customers that a full logic board replacement should be done if only the cheap i/o board
replacement is sufficient.

 

[mknell]

Yikes. Well, guess I’m not updating to Big Sur then. Bummer.

Yes, see also

Big Sur 11.0.1 (20B50) Released to Block Install for 2013-14 13" MBPro's!

Following the problems that 2013 & '14 13" MacBook Pro users were having, Apple released a new version of Big Sur that blocks installation!

mrmacintosh.com

 

[Yurdoy]

Hi. I disconnected i/o card, switched on my MBP and connected i/o card back. Bluetooth and some of ports start working. Then I restarted MBP and it booted normally, all ports working. But if I power off it, I have to conduct above procedure again. So far I keep it always running.

 

[Bmju]

Here's a link to my own post (on what seems to be the more active of the two MacRumors threads discussing this black screen issue) a) giving what seems to be a genuine fix for this problem, for at least some models, and b) pointing out that Apple are removing this information (Why? I genuinely don't fully understand! Is it just over-zealous underlings?) from their own public forums.

 

[arslandar]

An update guys - Took my MBP to apple store. The lady at the genius bar immediately recognized the issue as I started to describe it and told me she has received 4 such cases in last 2 days. I left the machine with them, got a call the same day, telling me i/o board needs replacement and that will cost me $$$. I argued but in vain and asked to speak to supervisor. Got a call from supervisor the next day, and while he was sympathetic about what happened, he said he has no instructions from apple management to do a free repair. So I have given a go ahead to order the part and get it repaired and will eventually paying for it. However, I would keep the repair receipt just in case apple launches a quality program in few weeks/months so I can make a claim. Not happy at all - because apple clearly knows its their fault but refuses to accept it.

Update: Got my MacBook back from apple repair. I was charged AED 475/- and they put on Catalina on it. Below is the work authorization email as well as copy of the receipt I paid to apple for the damage done by apple.

You can clearly see in the work authorization notes that they were well aware of the big sur problem but still had a nerve to charge for the repair.

 

[tommiy]

What can you say. Its obvious that Apple have no respect at all for its customers. They are just items to extract $ from and treat poorly. So they put out a new update to stop the install from being possible but yet will not fix the damage done. I feel for you. This is the exact reason why i stopped doing any updates to my Apple MBP after it died with Catalina.

 

[arslandar]

As the OS update has caused this, will Apple repair for free ?

unfortunately not in my case. Apple store in Dubai has charged me AED 475/- for replacing i/o board that big sir upgrade permanently damaged (see attached). Looks like Apple has learned nothing from battery gate...lawyers must be looking at this closely for a class action suit.

 

[arslandar]

Anyone else have the MacBook Pro stuck on a black screen. I have tried force restarting and then also holding Option. The only choice on the boot screen is MacOS Installer and it goes back to the black screen.

 

[SamSi]

unfortunately not in my case. Apple store in Dubai has charged me AED 475/- for replacing i/o board that big sir upgrade permanently damaged (see attached). Looks like Apple has learned nothing from battery gate...lawyers must be looking at this closely for a class action suit.

Apple had many case of service program for hardware flawed iPhone or Mac before. They will repair for free or refund if you repaired the faulty hardware before. I think you will get your repair money back if Apple issue a repair program for damages 2013/2014 MacBook Pro. I can’t even get it repaired in China. They say no spare parts national wide for this vintage model.

 

[bradbomb]

Wow, although I'm the one that started this thread, I must be lucky that I was able to get mine fixed without opening up the computer or even removing my SD card in the slot. I did the SMC reset and zapped the PRAM a few times. I then was able to hole option to boot and select the installation and it continued for a little. Froze again, and then did that again and the installer then finished and I have been up and running since.

 

[tigger147]

Thanks, that keeps me hoping.
You are now the fourth that I counted replacing the board did the trick.

Felipe Chelaut on the Apple Forum was not Lucky with replacing the I/o board.

how hard to replace the IO board, I’ve seen you have to remove the heat sink and sort out scraping off the thermal paste and reapply it etc