Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MalagLagoon

macrumors regular
Original poster
Dec 19, 2019
157
56
I've got a 2015 Mac Book Pro running Mojave. I have no interest in upgrading the operating system because I need to run the following command (using terminal) several times a day to prevent accidental and unwanted macOS upgrades to Catalina:

sudo softwareupdate --ignore "macOS Catalina"
defaults write com.apple.systempreferences AttentionPrefBundleIDs 0
killall Dock


And it sounds like future operating systems will not allow the above commands to work - therefore, I have zero interest using anything beyond Mojave.

Now I hear that Big Sur is destroying perfectly good laptops by corrupting firmware. Is that really true? Damn. Just, damn - that's whacked.
 

Natzoo

macrumors 68020
Sep 16, 2014
2,016
646
I have heard rumors of Catalina doing the same, it’s honestly hit or miss. Updating has become a huge risk as of lately, if you do update, make sure you have a backup and a clone of important data.

i still have Mojave on my 2018 15’
 
I have heard rumors of Catalina doing the same, it’s honestly hit or miss. Updating has become a huge risk as of lately, if you do update, make sure you have a backup and a clone of important data.

i still have Mojave on my 2018 15’
Good advice. Also, it might be better to do a clean, fresh installation of Big Sur, instead of an update in place.

Better yet, maybe wait until after a couple of releases of Bog Sur come out.
 

theMarble

macrumors 65816
Sep 27, 2020
1,024
1,509
Earth, Sol System, Alpha Quadrant
I've got a 2015 Mac Book Pro running Mojave. I have no interest in upgrading the operating system because I need to run the following command (using terminal) several times a day to prevent accidental and unwanted macOS upgrades to Catalina:

sudo softwareupdate --ignore "macOS Catalina"
defaults write com.apple.systempreferences AttentionPrefBundleIDs 0
killall Dock


And it sounds like future operating systems will not allow the above commands to work - therefore, I have zero interest using anything beyond Mojave.

Now I hear that Big Sur is destroying perfectly good laptops by corrupting firmware. Is that really true? Damn. Just, damn - that's whacked.
I've got a 2015 15" (11,4) and I upgraded to 11.0.1 a few days ago. Upgrade went fine, I had Catalina on this machine for about 3-4 months and it sucked, ended up wiping the drive and going to back Mojave then using your command to disable Catalina updates. Big Sur runs perfectly, no issues.
 

filbert42

macrumors member
Jul 20, 2014
92
20
Worcestershire, UK
I have a late 2013 Macbook Pro and was thinking of updating but this has put me off. Is it possible to install the update on an external SSD and boot from that? That would allow me to experiment with it.
 

chrfr

macrumors G5
Jul 11, 2009
13,731
7,308
I have a late 2013 Macbook Pro and was thinking of updating but this has put me off. Is it possible to install the update on an external SSD and boot from that? That would allow me to experiment with it.
The installation is now blocked on the late 2013 and mid 2014 13" MacBook Pros because of the damage that seems to be happening which prevents them from booting. This damage can happen regardless of whether you'd install to an internal or external drive, so you will need to wait until Apple fixes the problem.
 

filbert42

macrumors member
Jul 20, 2014
92
20
Worcestershire, UK
The installation is now blocked on the late 2013 and mid 2014 13" MacBook Pros because of the damage that seems to be happening which prevents them from booting. This damage can happen regardless of whether you'd install to an internal or external drive, so you will need to wait until Apple fixes the problem.
Thanks for the info. I’ll definitely wait!
 
I have a late 2013 Macbook Pro and was thinking of updating but this has put me off. Is it possible to install the update on an external SSD and boot from that? That would allow me to experiment with it.
Yes, you definitely can install it on an external SSD. And that is the smart way to go! I actually plan on doing exactly that (also did it last year with Catalina) on a partition I created on this SSD:


But I'm waiting, as there are still 4 critical applications I use that are not yet compatible with Big Sur. As it is, V11.1 of Big Sur will be arriving shortly, and my plan is to download, install, and test Big Sur on that external SSD after V11.2 arrives.
 

ArPe

macrumors 65816
May 31, 2020
1,281
3,325
Basically fake news and hysteria.

Configurator 2 running on another Mac will restore your Mac in the event of a bad installer or corrupt recovery partition.

The Genius Bar uses the same and other similar tools to restore Macs and other devices.
 
  • Like
Reactions: schlitzz

chrfr

macrumors G5
Jul 11, 2009
13,731
7,308
Basically fake news and hysteria.

Configurator 2 running on another Mac will restore your Mac in the event of a bad installer or corrupt recovery partition.
It's not fake news, and Configurator will only revive T2-based Macs, not the 2013-2014 models in question. If there were no issues with these 2013-14 models, then Apple would not have revised the installer and blocked Big Sur from installing on these affected computers.
 
  • Like
  • Haha
Reactions: ArPe and ouimetnick

ArPe

macrumors 65816
May 31, 2020
1,281
3,325
It's not fake news, and Configurator will only revive T2-based Macs, not the 2013-2014 models in question. If there were no issues with these 2013-14 models, then Apple would not have revised the installer and blocked Big Sur from installing on these affected computers.
Uh...I revived multiple Macs this way including the M1. It’s the quickest way to install a clean OS and fresh recovery partition.

Earlier Macs are too easy to restore without it. Can do it with my eyes ties behind my back.
 

shadyman

macrumors regular
Jun 9, 2015
235
214
Big Sur didn’t really ”brick“ mine, but it was heavily heating up so I had to downgrade to Catalina.
 

juan985_Spain

macrumors member
Jun 30, 2019
68
32
I've got a 2015 15" (11,4) and I upgraded to 11.0.1 a few days ago. Upgrade went fine, I had Catalina on this machine for about 3-4 months and it sucked, ended up wiping the drive and going to back Mojave then using your command to disable Catalina updates. Big Sur runs perfectly, no issues.
This looks just like me!
 

chrfr

macrumors G5
Jul 11, 2009
13,731
7,308
Uh...I revived multiple Macs this way including the M1. It’s the quickest way to install a clean OS and fresh recovery partition.

Earlier Macs are too easy to restore without it. Can do it with my eyes ties behind my back.
You are correct, it will revive Apple Silicon and T2 Macs. It will not revive these 2013/2014 models.
The question is moot anyway because Apple has blocked installation of Big Sur 11.0.1 with the build 20B50 installer after people had problems with the original release on 2013/2014 13” MBPs.
 
Last edited:

anubis1980

macrumors 6502a
Oct 22, 2012
557
406
I had to reinstall macOS yesterday on my m1 MBA. had the personalisation error. spent hours trying the official fixes etc still had same issue. Will admit I started to panic as I didn't want to have to go to an apple store. Apple support were awful and had no idea, told me they hadn't heard of the issue... I then read somewhere that someone had same issue even though they were on newest 11.01. They used iCloud to remotely erase their Mac, did this and hey presto back in. Squeaky bum time for 5 hours haha.
 

Zazoh

macrumors 68000
Jan 4, 2009
1,518
1,122
San Antonio, Texas
I had to reinstall macOS yesterday on my m1 MBA. had the personalisation error. spent hours trying the official fixes etc still had same issue. Will admit I started to panic as I didn't want to have to go to an apple store. Apple support were awful and had no idea, told me they hadn't heard of the issue... I then read somewhere that someone had same issue even though they were on newest 11.01. They used iCloud to remotely erase their Mac, did this and hey presto back in. Squeaky bum time for 5 hours haha.
Also this:

From @Lumpydog on another thread.

1: Shut down your M1 Mac
2: Press and hold the power button down to enter recovery mode
3: Click the "Options" Gear-cog icon and then press the "Continue" button that appears below it
4: On the next screen, STOP. Look to the upper left corner - to the right the Apple Logo in the menu bar, select "Recovery Assistant" (it is the only menu item)
5: In that drop down menu, select "Erase Mac..."
6: Follow the on-screen steps from there

Note - you will need wifi access. From what I can tell, using this process completely reformats the Mac hard drive to a single partition, downloads a fresh copy of Big Sur, creates a new recovery partition and a new OS partition with an OS only install (no Garage Band, iMovie, Pages, Keynote, etc - which you can install later). The process took about an Hour and ten minutes.
************ end quote
It took me 45min but I have Gigabit Fiber connection for internet.
 
  • Like
Reactions: anubis1980

MalagLagoon

macrumors regular
Original poster
Dec 19, 2019
157
56
From Wikipedia: Louis Rossmann (born November 19, 1988)[2][3] is an American independent repair technician, YouTube personality, and right to repair activist. He is the owner and operator of Rossmann Repair Group in New York City, a computer repair shop established in 2007 which specializes in logic board-level repair of MacBooks.

Here is a video from Louis Rossmann published about a week ago about Big Sur bricking Apple computers.

Big Sur delivers big kick in the balls to Apple users

 
  • Like
Reactions: worldvirus
All this "bricking" business seems to be baffling! I have 2 Macs: a late 2018 Mac Mini with a 256 gig SSD and 8 gig of Ram (has a T2 chip), and an early 2017 Mac Book Air with a 252 gig SSD and 8 gig of Ram. For both of them, when I moved to Catalina, and also a few times "within" Catalina, I did a clean, fresh installation of Catalina (did it first with V10.15.3, and subsequently with V10.15.4 (that was a backwards move), V10.15.6, and V10.15.7). And each of those was followed by migrating/coping needed files, folders, apps, settings, etc. from a SuperDuper! backup. Never had an issue doing that.

I plan on first installing Big Sur on an external SSD for testing. This will most likely be when V11.2 is released. What I will do is 1) download the installer file for V11.2 to my Mac Mini, 2) launch it and do a fresh, clean installation onto a partition on a Samsung T7 1 TB external SSD, and (assuming it's the same process) migrate/copy needed files, folders, apps, settings, etc. from my Mac Mini to that partition (am using the latest version of Catalina on both machines).

I assume I will not run into issues doing this, nor when I am testing Big Sur from that external SSD. Is that correct?
 
  • Like
Reactions: haddy

markszachary54

macrumors newbie
Jan 7, 2021
2
0
My late 2018 MacBook Air was completely bricked by upgrading to Big Sur. Apple Genius Bar and support didn't help at all. I had to buy a new laptop. Very disappointing. They claim it screwed up the logic board. They required a $500 payment just to send it in. I tried everything with no luck. Apple screwed me.
 

Aggedor

macrumors 6502a
Dec 10, 2020
799
939
My late 2018 MacBook Air was completely bricked by upgrading to Big Sur. Apple Genius Bar and support didn't help at all. I had to buy a new laptop. Very disappointing. They claim it screwed up the logic board. They required a $500 payment just to send it in. I tried everything with no luck. Apple screwed me.
How can a software update screw up a logic board?
 

markszachary54

macrumors newbie
Jan 7, 2021
2
0
I don't know but that is what the Genius Bar, Apple Support, and the Geek Squad all concluded. It seems crazy to me but the laptop is legitimately a brick now and won't start up all due to upgrading to Big Sur. I've read online it is happening to lots of people.
 

adib

macrumors 6502a
Jun 11, 2010
743
580
Singapore
Yes there were a number of T1 & T2 MacBooks that were bricked by Big Sur beta. However these has been resolved in subsequent beta releases. Furthermore those bricked MacBooks can be revived by resetting the firmware inside those T1/T2 controllers by putting the Mac inside DFU mode and re-flashing it using another Mac.

Thus in terms of permanent hardware damage, there was none caused by Big Sur. That said, be sure to keep current backups. That's what Time Machine is for.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.