Catalina bricked my 2015 MacBook Pro. What to do now?
I’ve just “upgraded” to Catalina.
My laptop is now bricked.
All I get is the “folder?” logo or nothing at all if I try “option” or “command R” on boot up.
What to do now?
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.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
I’ve just “upgraded” to Catalina.
My laptop is now bricked.
All I get is the “folder?” logo or nothing at all if I try “option” or “command R” on boot up.
What to do now?
No, when computer gets hot, Fans still runs normal.
As I told earlier, I could install a macOS Mojave on a USB attached to my computer, so that it updated my Boot Rom Version to 263.0.0.0.0.
Does reflashing the EFI do the same thing as what I did by Updating the EFI version or it does sth different?
And another question, Since I have access to my Intenal HD through this OS that is installed on USB, if I could format the internal HD as exFAT and then copy some files on it and then cut the files from it and paste them in OS, can we assume that my internal HD works fine?
Thanks for your kind cooperation.
Well, given this happened during the Catalina upgrade, and given you can still write to the internal HD, it's probably not the HD. Question is whether you have access to a spare HD just to perform a swap test. If not, then I guess your only other bet is to reflash your Boot ROM.
The UEFI BIOS is actually quite complex, and contains multiple parts : code for the Management Engine (aka "ME region"), the BIOS itself (e.g. Internet recovery), some data area (including serial number etc). In my understanding, as part of a regular upgrade, MacOS does not rewrite the ROM in whole, but extracts the BIOS region, applies some patches, repacks and then rewrites everything. So even though you reinstalled MacOS, I believe the ME region was not necessarily rewritten.
At this stage, I think either you find some spare parts to do some swaps and isolate the problem, or you try to rewrite the Boot ROM. Rewriting the Boot ROM requires having a programmer with the appropriate cable, and a reference full ROM image for your exact motherboard. Count up to $100 for the programmer+cable, and make sure you find a proper image before ordering.
Let me know if you want to go this route, I can probably help to some extent.
There's nothing new under the sun Rick. They bricked two of my MBP's Mid 2012 with updates that they suggested that I should apply via the App Store! When I went to report these issues at an Apple Store during an appointment with the Genius Bar I was told that my machine had water damage. My machine has never been around water for any water damage to have transpired. I am the only one that utilizes any of my machines. To add insult of injury it happened with more than one MBP Mid 2012 model of the same type/specs! They refuse to acknowledge that this is an ongoing issue and I'm starting to think that this is being done purposely so that we can purchase new hardware. When it came to my MBP the power malfunctioned after a firmware update that was pushed to my PRAM. The computer wouldn't start nor would it charge the battery. I got no chimes or anything indicative of a boot. I refuse to allow them to render my machines inoperable.
*Since this time I have halted installing or updating my MBP's or IMACS in any way. At this time for the health of my machines I cannot trust Apple to perform updates while there's no Apple Technician to witness any issues that may transpire. It's my word against theirs if I do the updating myself. In every instance that these types of issues have transpired I've been told that I caused the damage to my machines. I've been utilizing these machines for years without any issues until it came to updates and upgrades. To be on the safe side bring all of your machines to the Apple Store and allow them to process any upgrades or updates.
I remain on 10.11.6 forever! I have some work arounds for security. My IMAC can only go up to High Sierra; however, the updates are what got me not the actual OS install. I'm afraid that after your computer is out of warranty and the models have reached end of life they can brick machines at random and at will and they don't have to support you or acknowledge their error. This is also transpiring with IPHONES my battery only remains charged on my IPHONE 6s for about 24hrs. When I first got this phone it would remain charged for a minimum of at least 5 days depending on the usage. I'd like to add that I took full advantage of the battery replacement program that was offered. This was due to the fact that this was their excuse for throttling older IPHONES when newer versions hit the market. They're saying that my battery levels are fine when I know better I use the phone everyday.
*They'll attempt to make this your fault no matter how user savvy you may be.
After my macbook air 2015 died due to catalina update (no keys combinations worked on boot, just flashing question mark in a folder sign on display) I went to an apple service (not an official service where they offer to change logic board) and the EFI was reflashed there for 75$. Now macbook works just fine without any logic board replacement.
No more Apple for me.
I bought another loptop and installed Ubuntu.
I wrote about possible ways to fix MacBook bricked by Catalina, including forcing Apple to do it for free (I succeeded but I pressed really strong), having it done at unofficial shop or doing it yourself. See here: https://www.ifixit.com/Answers/View/612997/Catalina+Bricked+my+Mac.+Now+What
I wrote about possible ways to fix MacBook bricked by Catalina, including forcing Apple to do it for free (I succeeded but I pressed really strong), having it done at unofficial shop or doing it yourself. See here: https://www.ifixit.com/Answers/View/612997/Catalina+Bricked+my+Mac.+Now+What
Alex, read this post: https://discussions.apple.com/thread/250728927?page=1
My assumptions were right, Catalina is ruining the EFI while upgrading.
Maybe a bricked EFI?
I have the same issue. See my thread here. https://discussions.apple.com/thread/250715174?answerId=251484966022#251484966022
went to Apple store. Can’t fix it.
Same thing on my mac mini 2012. No keys recognized. Black screen.
Exchange of defective LogicBoard will cost € 450.
Would you tell us how you did that?
Given that I get no response from any keystroke combination before the dreaded “?folder” icon, I don’t see how I can do the same.
Funnily enough, I had previously installed the Catalina beta without issues. Then this happened with the final release.
Again, Apple does not monitor these threads to keep account of the users affected. Please contact them directly via phone or chat so that they can be made aware of the problem.
Similar thing here I upgraded to Catalina and has been fine. Installed the latest supplements update just released and its bricked my 2017 MacBook Pro with the folder?
Catalina bricked my 2015 MacBook Pro. What to do now?