great expression, and very creative!
now i know what to engrave on my next ipod touch!
bravo!
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Fixes Bug That Bricked Some Intel Macs After macOS Monterey Install
- Thread starter MacRumors
- Start date
- Sort by reaction score
now i know what to engrave on my next ipod touch!
bravo!
Along those lines, I updated late 2014 Mini to 15.1 and AFTER d/l and install but BEFORE reboot it pops up with ANOTHER update for wired/usb backup connection. Weird and sloppy and far from transparently integrated - half-assed and a bit shoddy in fact.
Are you intentionally being a dumbass?
If there is an update available and I am free, I will be installing it.
Apple probably ran out of old Macs to test this on. Probably threw them all out and recycled them. 
I take this as a tongue-in-cheek poke at Apple. Because if they DID do it on purpose, people would figure it out PRETTY quick.
You should HAVE been taking backups! There's no "of" about it!
So what's the difference between a sh*t brickhouse and a brick sh*thouse? ?
You don't know if it was sloppy coding. It could be anything from a bug in the chip itself, its firmware, or a bug in the compiler used to translate the code into executable instructions. There's no way to know that for sure from where we sit, and for that reason, we should never be so quick to throw a developer under the bus or off the island.
This person has it right!
You both need to chill out. Stop being so picky with each other!
You've never written a line of code in your life, have you?
It's not always in our control. My company's Apple devices must be updated within a certain number of days of a new OS being released, or THEY STOP WORKING. So stop blaming customers.
Oh wait, you said that already!
There's an equal number of people who hoot and clap like trained seals if something bad happens to Apple. It goes both ways, and it's just as gross, isn't it?
We will see how Apple handles this, but it looks so far (if you read the earlier pages in this thread) that there IS indeed a way to fix the bricked machines. So there's your "period. end of story.".
Crap happens. We should be testing better, but it doesn't always happen. And who knows, maybe it's possible that this has happened to so few machines so far that none of them had the problem during the alpha OR the beta. You just don't know.
Right!
As I said above, can't always be done. A lot of people are corporate users, and they don't get a choice to decline or delay an update.
You've obviously never worked in a corporate server environment or in any kind of role where you might see the list of security or reliability issues and vulnerabilities. EVERY OS has its share of "messed up systems", even Linux and Unix! Windows has largely been reliable for several years now, both desktop and server. But any environment can fail.
I could say the same thing to anybody still paying for cable or satellite TV! It's all about perspectives, so let's try not to call people mentally unstable just because they think differently than we do.
Strange…I have a MacBook Pro 2018 that had no issues, but it is on the list. Actually, it is running better than ever (while I wait for my new MacBook Pro)..
If it was a T2 problem, would’nt it be all? There are not different T2 chips from different manufacturers etc. ..Interesting.
Well Apple's statement says, "an issue that could cause some Intel Macs with a T2 chip to fail to boot up after macOS Monterey was installed." So I guess we have to imagine that the ones tested had no problem.
There are always issues with new devices and new software, what we see on these forums is an over representation of users who have a problem. The vast majority do not. Like the class action over the "stage lighting" issue on 2018 MBP's, the sudden cracking screen (which just broke by itself) and the USB hubs and ports not powering issues of some users.
I have installed Monterey on an early 2015 13" MBP which is last on the list of compatible devices. If anyone was going to have problems you would think it should be me, of course I don't have a T2 security chip, but my device actually runs better on Monterey than it did on Big Sur. ¯\_(ツ)_/¯
Ummm…but my MacBook Pro 2018 had usb-c power port issues and they replace the entire logic board.
. I guess I was one of the few…But, I fully agree with you. I am puzzled why just some have issues. A bad chip batch maybe? This forum tends to be dominated by complainers or those with issues, but that might be the norm on a forum like this (people trying to also figure out why or find a solution from others).
Yes, my MacBook Pro 2018 AND my Mac Pro 2013 run MUCH better now, including reducing heating issues without much or just a little power loss. The Intel Macs are getting updates still to resolve some issues. That is a good thing.
2019 MBP 13" with 4 TB ports. My first attempt to update from Big Sur resulted in a black screen for an extended period, after the update had almost completed. I held the power button down then couldn't get it to boot or turn back on, so was worried it had been bricked. Eventually the progress bar returned and it actually restored my Big Sur installation. Then I tried the update a second time and it worked flawlessly (without the extended black screen).
Simple. You need a 2nd Mac and Connect a the brocken mac on the USB Port near the Trackpad and the other and on any usb port on the 2nd macbook or mac with usb-c then with a special key combination u start the T2 in DFU mode and Revive the T2 and Flash new Firmware and the Mac Will Work again
There's an issue with the 2020 MacBook Air machines overheating and a constant noisy fan.. when are they fixing that?
I can imagine the damage this is doing to the machine. If they don't fix this issue soon .. I hope we get some compensation .. I'm over shutting the machine down every 5 minutes. The flawed Safari update and now this!
I can imagine the damage this is doing to the machine. If they don't fix this issue soon .. I hope we get some compensation .. I'm over shutting the machine down every 5 minutes. The flawed Safari update and now this!
Do you even understand the QA process? Anybody who has your first sentence of a response should be dismissed. You generally get one chance to mess up before heads should roll. But these Process escapes (do you understand this term?) are not single events. They’re virtually expected at all times during early macOS point releases. This is a tarnished reputation here and anybody that understands QA cost knows field exposures carry exponential costs compared to actual QA testing via plan, specs and real testing in-house.
They said it was a small number, does that mean people who didn’t have the firmware up to date? That is step 1 in an update. If that is not the problem, then how could it be only a small number and not seeming to effect everyone. There are clearly facts missing, but saying the update will be included leads credence to this theory
Better solution, check to see if installation can run before starting. There have also been os file issues before, version checking?
Better solution, check to see if installation can run before starting. There have also been os file issues before, version checking?
Strange considering Apple was a billion dollar company when one guy simply compiled Marklar in a couple hours at home, then showed it Bertrand Serlet who then showed it to Steve Jobs.
It’s not like OS X wasn’t complex code then either. The guy who brought up the OS X project on Intel for commercial use didn’t even work at the main campus, he was in New Jersey and he did it from his home.
He posted all the Macs he had in his home to test the various configurations of OS X for Intel on. ‘One guy’ and he did this for years.
Apple is now a trillion dollar company and you are telling me they can’t go down to the inventory, pull out three of each model they are supporting a release on and find some space on that big old campus and setup an actual test lab? Heck, they could hire me to do the testing myself.
What I think is happening is, they simply dropped the ball, too many projects going on and one suffered for the other, in this case Monterrey. Also, the Intel builds seemed to have suffered over the Apple silicon builds. I have wouldn’t be surprised if Intel Macs get dropped by 2023, with the last Intel release going into long term maintenance support.
I know that sounds weird from an outsider's perspective but if Microsoft manages to hire all users to beta test their own Windows 10 builds for free, Apple certainly can do the same. Heck, iOS public beta program was introduced back in iOS 8 days iirc, and I jumped the gun on iOS 8.4 back then. macOS public beta followed soon after.
They SHOULD'VE actually tested macOS on their real hardware before shipping it out to customers, but they choose not to. I think one of your guesses seems logical, but Apple would never tell us publicly how they do internal testing anyways unless someone decides to blow it up.
Given how hostile Apple towards Intel stuff these days, starting from ripping random non-critical features from Intel Mac, I highly doubt such "long term maintenance support" would happen. Instead, I would not be surprised if they stop supporting Intel Mac in 2022, making ALL current Intel Macs stuck at Monterey forever. 2023 is fine too.
That's back in 1990 days, where people generally were a bit more careful about what they wrote. It's not like you can distribute thousands of floppies for a bug fix that you just found after sending the program to the manufacturer, unlike today.
I know nothing about writing software, let alone an OS that straddles two microprocessor technologies in this day and age, but I know enough about chip manufacturing to accept that not every chip will perform identically in all situations. There only computer I have ever owned that did everything it was expected to do everytime without fail was a Commodore 64.
Swifter, higher, stronger has a price.
I have come to learn that when a .0 release appears on my screen, I come to forums like this to see what the reaction of the user community is.
Backup backup backup.
I trust that Apple will resolve any and all issues in accordance with the licensing agreement that we all accept when we purchase their products. Of course everyone has read and understands their licensing agreement don’t they?
Swifter, higher, stronger has a price.
I have come to learn that when a .0 release appears on my screen, I come to forums like this to see what the reaction of the user community is.
Backup backup backup.
I trust that Apple will resolve any and all issues in accordance with the licensing agreement that we all accept when we purchase their products. Of course everyone has read and understands their licensing agreement don’t they?
Hi man I don’t. Here is a /s
But yah apple is definitely not going to make life easier for intel folks moving forward.
Then in 10-15 years apple will switch over to intels again