You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Catalina bricked my Macbook Pro (Mid-2014, 128G)

I used macOS Mojave on mid-2014 MacBook Pro before update. While installation it forced me to restart. After restart nightmare has been started. The Blinking question mark folder has appeared on my screen.

I tried,

  • Reset SMC and NVRAM (With all combinations these are find on internet and apple support page.)
  • Accsess local and network recovery (with all key combinations)
  • Access to time machine restore (with all key combinations)
  • Mojave installation USB stick (that USB works we tried another Macs)
  • External disk that includes pre installed mojave (that external OS works well we ran on other Macs)
  • Unplug all battery power (black reset)


I've tried all keyboard combinations and nothing works, even with external keyboard!  It seems that there is no start up chime, no USB detection, no key feedback. It‘s bricked.

MacBook

Posted on Oct 14, 2019 6:40 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 14, 2019 7:27 PM

Same here with a 2014 MBP. There are a number of other threads describing the same. The prevailing idea seems to be a fatal corruption of firmware (EFI) during the upgrade. I don't know how Apple has handled issues like this in the past, but would be reasonable to expect some consideration for repair. Hopefully enough users will be affected and enough noise made to spur action. I would guess that we should all be contacting Apple directly via email or chat, and referencing the other threads regarding this issue.


https://discussions.apple.com/thread/250716026


https://discussions.apple.com/thread/250719221


https://discussions.apple.com/thread/250728927

Similar questions

11 replies
Question marked as Top-ranking reply

Oct 14, 2019 7:27 PM in response to Mid-2014MacPro

Same here with a 2014 MBP. There are a number of other threads describing the same. The prevailing idea seems to be a fatal corruption of firmware (EFI) during the upgrade. I don't know how Apple has handled issues like this in the past, but would be reasonable to expect some consideration for repair. Hopefully enough users will be affected and enough noise made to spur action. I would guess that we should all be contacting Apple directly via email or chat, and referencing the other threads regarding this issue.


https://discussions.apple.com/thread/250716026


https://discussions.apple.com/thread/250719221


https://discussions.apple.com/thread/250728927

Oct 15, 2019 7:49 AM in response to Mid-2014MacPro

To those who've experienced this issue: please let Apple know today. These threads are not actively followed and the more users that report to Apple, probably the more likely that there will be some resolution.


I initiated a chat and was then called by a Senior Advisor. I reported the details of the update corrupting my firmware, and sent links to the relevant threads here. Be nice and don't expect a fix over the phone, but they need to be made aware of the number of users affected. For reference, here are the related threads I am following:


https://discussions.apple.com/thread/250716026


https://discussions.apple.com/thread/250745000


https://discussions.apple.com/thread/250719221


https://discussions.apple.com/thread/250728927

Nov 25, 2019 11:13 AM in response to Mid-2014MacPro

i have the exact same problem with my late 2013 imac.

I would advise not to take it to a non apple store because you are likely at least have to pay for the initial consultation which is £50 for stormfront UK.


so far Apple is not admitting the issue and blaming it on hardware problems.

It's highly unlikely right? since I have the latest Mojave version days ago and literally rebooted the imac a few hours ago.

The online apple chat support only advises me about the UK which my imac just passed outside of the limit a few months ago for it to be covered.

now they ask me to take it to an Apple store.

And ask me to submit https://www.apple.com/feedback/.

This does not sound like they understand the severity of this problem.

"How can we ever trust another apple OS upgrade?"

The problem is any possible OS patches or upgrade could render your machine unusable and unrecoverable by any method without opening up your machine.

Not to mention the communication you have to overcome with Apple first to get them to admit it's their fault.

Seriously this damages Apple's reputation!?


I have never seen PC messed up your bootprom this way!


so everyone please submits your feedback to apple if you have not already done so.

Dec 2, 2019 4:48 AM in response to Mujkocka

Hello. I have the same problem with my macbook air 2015 and wrote them to https://www.apple.com/feedback/ about a month ago. They just ignored me - I got no reply.

So I have to pay for their bug with catalina update. (I will not)

As I understood this is the real attitude of Apple towards their customers.

I will never buy anything from apple.

People pay more buying apple devices because they want reliable product and a good service. And not this ... .

Nov 15, 2019 1:37 AM in response to Mid-2014MacPro

I have the same issue. My 2017 Mac Book pro is totally down after installing Catalina. The installation went well and after rebooting it is simply black and off power. The kind lady at apple support told me, that she hard this for the first (!) time. Now the logic board has to be replaced for > 500€ and it is not even possible to send a request for a goodwill solution to apple. It is hard to see that many others face a similar problem after installing Catalina.

Catalina bricked my Macbook Pro (Mid-2014, 128G)

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