After reading this I decided to try this for myself and lo and behold, my MBP is functional again! Looks like 11.1 indeed fixed the issue. I already bought a new Windows laptop to replace it, but it's nice to have my MBP available as a fully working backup.Hello everybody,
don`t know if somebody else wrote similiar info. Eventualy sorry for the spam.
I`ve got bricked my Macbook pro mid 2014 by Big Sur 11.0.1 update. Only one way how to partly fix the problem was unplugging I/O board and finish instal.
I tried everything suggested except booting windows 10 and in the end I decided to wait for new update. Because of trying everything possible i ended on last Catalina version before last try.
Last try: Yesterday I updated to Big Sur 11.1. with disconnected I/O board and after update everything works well, and mac booted even i reconnected I/O board. No SMC or NVRAM reset needed. I used normal way through appstore.
Problem solved but shame on Apple for their behavior in this case. I tought my I/O board is dead, but it`s not and everything was apparently SW problem.
I pray for everybody who will try it!
Sorry for my english.
I wound up upgrading via Software Update late last night. Not even 90 minutes from the moment I started the download to being up and running. So far, so good. I'll still likely do a clean install within the week anyway, and I assume internet recovery is the simplest way to do so now that I've upgraded already.
I took the plunge and started it last night. I got a few failure messages, including one that said the Big Sur file was damaged. I left it running over night and got a couple more failed messages but, after a few restarts, it finally "took", so my late 2013 MacBook Pro is now running Big Sur 11.1
I have read on subreddits and on Apple community boards that there have been macbooks, iMacs, etc. that have been bricked dating back to Catalina and affecting multiple years.
Yep - that guy was apple senior support rep. Will try to call them again tomorrow, maybe I will be lucky enough to talk to someone else who will be more helpful.
Did you ever get this fixed? The cure is to Reset Launch Services
Today, I took time to call Apple support again and got to a senior support person again. Got to talk to the nicest lady. Explained the whole situation again, explained that my macbook pro has been in the Apple store since I dropped it there 3 days ago and refused the repair which they told me I have to pay for it(so I can talk to Apple support on the phone in a meanwhile) but havent picked it up yet. It helped that I havent picked up my macbook from the store to expedite the repair process. The senior rep took her time to check my case and probably review the docs on her end - maybe more than 15-20 min I was on hold, but when she came back she told me that they will do a 1 time curtesy exception to cover the repair in the midst of this difficult time we are all in. She called the Apple store and instructed them how to proceed. Now I am waiting 5-7 business days for the repair to complete. I was told that since I havent paid for the repair myself and ask for reimbursement things are going to be a ot easier. Just keep calling apple support and if you get shut down, call them again. I got the stupidest explanation from the apple store that during the upgrade of the OS the hardware is getting stressed out and certain components may fail. I have upgraded many times in the past with no problems except now with Big Sur. And on the other side when I talked the first time to a senior apple rep on the phone and when he told me that upgrading OS cannot cause hardware issue I was stunned. Be persistent when you call Apple support, but be nice to them. I just hope that there will be no more surprises until I get my mac back - repaired.
Yes! yes! yes! Especially when, under the terms of their warranties, you are not entitled to hardware support. I have received considerations talking to Apple (and Toyota) by being persistent and polite.
Your law degree is from where? (Spoiler alert: It really doesn't matter how many times you've said it.) Apple is bound by the State of California Dept. of Consumer Affairs in the USA and their many international agreements regarding what they have to do.
Final update - 5 days later I got my 2015 macbook pro completely fixed - in the repair order it was noted that the logic board, the I/O board and a I/O Coax Cable were replaced.
Yes, I have the exact same behavior on my late 2013 13" MBP. I have FileVault enabled. I have not tried with it disabled.
11.1 solved a large number of problems. Most would agree that the answer is Yes. If your I/O is under any kind of warranty such as a 90 day repair warranty, my answer becomes Hell yes!
