Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Interesting how Apple put out the Public Beta months ago and this is discovered just now? You mean nobody with a 2013/2014 MBP ever had a bricking issue all the time during the public beta? Hmmm. Sometimes I get the feeling that these issues are made up in order to crap on Apple when they release new products. Furthermore while I'm not saying bricking should happen I think it's a stretch trying to install the latest OS on near 7 and 8 year old computers and expect to have no issues.
My 2016 MacBook’s flash drive was actually destroyed after installing one of the first Big Sur betas earlier this year making an exchange of the whole motherboard necessary as it’s all soldered in one piece.
The specialists at the Apple Store didn’t seem to be interested in the cause and handed me a quote for estimated repair costs... 🤷‍♂️

(P.S.: I declined the quote and repair and bought an SSD that is since attached on the outside of the screen.)
 
And MS "feature updates" to Windows 10 don't ever break anything. Uh huh. Yeah. What universe are YOU living in?

MS breaks things every update.
Never said they didn't. Just when people are saying that 2013/2014 are old and this sort of things is expected, by the standards of how far back Microsoft supports, Apple doesn't support very far back.

And I'm sorry but MS doesn't break things 'every update', and completely bricking a laptop is far more than something breaking.
 
  • Like
Reactions: chrickers
Big Sur is sure looking like a huge headache more and more by the day. First the Apple servers crashed on launch day, and now this debacle... I usually am the first the jump ship to the latest OS, but gonna wait a bit for this one
Not sure that's a fair assessment. There has never been an OS release of any platform free of bugs. IMHO Catalina was the buggiest macOS release I've ever seen. It's too early to say that Big Sur will be as bad. Also, A 2013-14 MBP, with it's aging hardware will have many problems trying to run the latest and greatest from Apple.

I've been running the betas on my 2015 13' MBP with only a few minor problems, no deal breakers as of yet. I pre-ordered the Silicon MBA M1 which is due to arrive today or tomorrow so I expect that to run macOS Big Sur with even fewer issues since the hardware and OS have been completely optimized for one another. Everybody's mileage will vary but for me Big Sur is looking pretty stable.
 
Upgrading is a choice. Nobody is forcing you. Just stop.
That reply isn't even relevant to what I said.

Myself, I have no issue with jumping in and having a backup if things go wrong. I know that new software can be buggy. The thing is that the majority of Apple users are not technically inclined, they don't know that an update is 'new' and don't pay attention to release cycles.

However the way that Apple displays MacOS version updates now is in a way that is confusing to basic users, who end up installing big updates because they think they are installing bug fix or security updates.

The onus should not be on end users to figure out when an update is safe or not. Apple should have a better way of presenting OS updates to end users. Maybe have a system where auto update has different stages, where by default users aren't notified to do big updates till said big update has received a few months of mainstream testing.

As someone who works in IT support, the current system is very frustrating. If I tell end users to install just security updates or bug fix updates, they accidentally upgrade to new versions of MacOS. If I tell them not to upgrade Mac OS, they think that every update is bad so never install anything.
 
No problems at all upgrading my MacBook Pro 15” Late 2013. Big Sur is a great improvement in terms of usability, personalization and aesthetics. It runs smoother than before, and I haven’t had any compatibility problems running different Apps in there. In fact, it seems to me that everything runs faster than before. 🤷🏻‍♂️
 
  • Like
Reactions: eico720
Huh, I updated on my Late 2013 Retina 15 and the screen did go black during the install but it eventually worked fine after I left it a few minutes.

Haven't tried rebooting yet.
 
Didn’t brick it, but “bricked” the HDMI connection to my external monitor on a MBP16. And a restore back to Catalina didn’t resolve it, so Big Sur seems to be upgrading some firmware which can not be rolled back via OS rein-installation.
Some people are saying the upgrade affects HDMI and can't be fixed by downgrading or re-installing. My late-2013 15" MBP, which is connected to my telly with HDMI (as the screen is smashed and can't be used any other way) upgraded fine. Had I read this thread before upgrading, I wouldn't have taken the risk!
 
  • Like
Reactions: VoipRodrigo
So you clear the checkbox in System Preferences>>Software Update and it doesn't install anything until you tell it to. Not rocket science.
I want macOS to auto install after a set number of days.

I do not want to manually do it in 30 days.

Kindly read the post before replying.

Windows can do this. Why cannot macOS?
 
Fortunately the majority of people here still think very differentiated, but there certainly is some annoying voices defending Apple as if it was their own child...
yes. people need to realise that Apple is not your friend, Apple is a company who's goals is to maximise profits. That means, its goals is to get as much money from the people buying Apple products as possible. The way they're heading, they're taking more control of the hardware and software of Macs to the point where they will be locked down like iOS devices, resulting in every app install dropping pennies in Apples pockets.
 
  • Like
Reactions: Nicole1980
Sadly, This truly shows how poor Apple's quality control has become...
Aren't you all tired of paying to Apple for beta testing their lame OS?

It truly shows from hardware to software how little Apple cares about the entire computer line up.
 
I'm assuming there has been a firmware update causing EFI issues.

My 2017 iMac now takes around 1m30 to boot to refind. Way longer than it originally did under previous versions.
 
That's not evidence of planned obsolescence. That slow down was done in specific circumstances in order to prevent sudden shutdowns. A slightly slower phone is better than one that will randomly switch off due to a degraded battery. The user has the option to disable the throttling. This is not evidence that Apple slows down old devices to force people to upgrade. If it was evidence, then Apple would have to do it to every iPhone 6 for no reason at all.
Just google that.
 
That's not evidence of planned obsolescence. That slow down was done in specific circumstances in order to prevent sudden shutdowns. A slightly slower phone is better than one that will randomly switch off due to a degraded battery. The user has the option to disable the throttling. This is not evidence that Apple slows down old devices to force people to upgrade. If it was evidence, then Apple would have to do it to every iPhone 6 for no reason at all.

Wrong. They only added the option to disable it once they were caught.
 
Never update straight away as there are always bugs.
Well if everyone had that attitude, we’d never get the bugs out. Lol.

I’ve been running Big Sur from the first public beta as an open source developer. I usually file about 2 bugs per beta release, but for Big Sur I had 14. Safari is a hot mess—big WebKit rendering bugs—as well as Preview and seemingly anything that requires GPU rendering. I’m confident they will get it resolved, but I haven’t liked seeing many of the same reported issues present in the release candidate and then in the production build.

I have to agree, if you want a perfect OS build starting out, wait a bit on the upgrade. The good news for other developers is that nothing major breaks as long as you install latest Xcode Command Line Utilities and update system paths accordingly.
 
While after quite a few glitches in the Betas, the final version looks pretty good for me on a MP4.1,MP5,1 and a MB10,1. My guess is that the built in firmware upgrade went wrong.
It could be both the firmware itself, or the upgrade process going wrong.
The release version of Big Sur containers EFI Version 427.0.0.0.0 for the MBP11,1/MBP11,2.
Can anybody out there confirm that EFI version on his MacBook 11,1 or 11,2?
Can anyone confirm it that never tried to install Big Sur on it?
BTW.: My MB10,1 got a 429.50.1.0.0 firmware...
 
  • Like
Reactions: eico720
What seems to be constant on these comments is that people who don't have a problem do not care at all or even try to understand those that are having a problem and even blame the user for having expectations from a trillion dollar company... ie I don't have problem so I don't care about anyone else. Sad.
I had a flawless install and my old computer is working better than ever, with a battery time improvement too.

I'm not alone in reporting this Big Sur update experience.

So, I'm asking for theories, not conspiracy theories about the evil Apple, but guesses from people more knowledgeable than me as to why some installs go fine and others are troublesome to disastrous. Honest inquiry. And please, explain so a grunt like me can understand.
 
One thing that I have learned from being a Mac Admin is that you never do an in-place update of your current OS but you do a clean upgrade. Either create a bootable thumb drive, wipe the hard drive, and then install the new OS or boot into recovery mode, and then wipe the hard drive and install the OS. This has treated me well over the years. It's good to upgrade right away if you have a test Mac to do it on. This way you can find the bugs with regards to the apps you use before making it a production move. If not, wait for the first service pack before upgrading. There are always bugs and it's almost impossible to get them all fixed in betas. If you are not technically inclined to work through these bugs let others who are be the first to adopt and work through them for you. Then you upgrade once the first service pack comes out. Sometimes the first patch comes out within a few weeks so I would suggest waiting at least two months before upgrading. Sometimes it takes more than one patch to fix most of the bugs if they put the new OS into production too fast.


A large number of late 2013 and mid 2014 13-inch MacBook Pro owners are reporting that the macOS Big Sur update is bricking their machines. A MacRumors forum thread contains a significant number of users reporting the issue, and similar problems are being reported across Reddit and the Apple Support Communities, suggesting the problem is widespread.

macbookpro13large.jpg


Users are reporting that during the course of updating to macOS Big Sur, their machines are stuck displaying a black screen. Key reset combinations, including NVRAM, SMC, safe mode, and internet recovery, are all reportedly inaccessible after attempting to install the update, leaving no way to bypass the static black screen.

It appears that the overwhelming number of users experiencing problems are owners of the late 2013 and mid 2014 13-inch MacBook Pro, but it is unclear exactly how many users of these models have been affected. It is also of note that these are the oldest models supported by macOS Big Sur.

One commenter on Reddit said that they were told by Apple support to book their MacBook Pro in for a repair. Another on an Apple Support thread said that the issue has been escalated to Apple's engineering team, so Apple should now be aware of the problem.

Until it is clear what may be causing the issue and Apple releases a fix, late 2013 and mid 2014 13-inch MacBook Pro may wish to hold off on installing macOS Big Sur.

Article Link: macOS Big Sur Update Bricking Some Older MacBook Pro Models
 
  • Like
Reactions: seek3r
Myself, I have no issue with jumping in and having a backup if things go wrong. I know that new software can be buggy. The thing is that the majority of Apple users are not technically inclined, they don't know that an update is 'new' and don't pay attention to release cycles.
WOW the majority? Where's your proof on any of this? I've been a dedicated Mac user for 25 years starting with Windows and I have a degree in electronics. Most Mac users were Windows users first and you have to be pretty technically inclined to deal with anything past reading emails on Windows so your view on this is a view of ignorance, unless you have facts to back any of what you said up.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.