News for hackers. Stuff that matters.
Re:macOS Sonoma Boot Failures by tpmx on Tuesday October 31, 2023 @04:44PM (#38091121)
This is depressing. They clearly have they ability ($$$) to do the required amount of manual QA, but don't. Or there was QA and someone decided that your case still wasn't enough to hold up the release.

In my mind, when we pay that ridiculous Apple Tax on RAM and storage, we pay for excellent quality in SW/HW. They also need to deliver that quality.

Re:macOS Sonoma Boot Failures by mort96 on Tuesday October 31, 2023 @04:54PM (#38091241)
Or they did QA but just happened to miss this issue. Most companies would consider "the upgrade sometimes bricks the device" to be a release-stopping bug, I'm betting Apple is among them.
Re:macOS Sonoma Boot Failures by codr7 on Tuesday October 31, 2023 @05:41PM (#38091776)
Used to be, while Jobs was still around.

These days it's just a bunch of wannabes trying too hard to be him.

Re:macOS Sonoma Boot Failures by krackers on Tuesday October 31, 2023 @05:05PM (#38091373)
Apple still hasn't put up any official page about the issue though, nor does it appear they've pulled the update. Even if it missed QA, why haven't they made any official comment?
Re:macOS Sonoma Boot Failures by FirmwareBurner on Tuesday October 31, 2023 @05:52PM (#38091912)
You clearly don't know Apple as a company. Last most big companies, they never EVER publicly admit any faults or mistakes with their products (unless forced to by large scale fiascos) because that would damage their perfect brand image. It's why they have comments disabled on all their social media accounts.
Re:macOS Sonoma Boot Failures by JumpCrisscross on Tuesday October 31, 2023 @06:10PM (#38092124)
> they never EVER publicly admit any faults or mistakes with their products

Of course they do. They’re just secretive in general, and keep communications edited. Compared to the word salad of modern companies on social media, I find it refreshing. Just fix the problem, issue replacements for those affected and move on quietly.

Re:macOS Sonoma Boot Failures by FirmwareBurner on Tuesday October 31, 2023 @06:19PM (#38092200)
>Of course they do.

Where? Do you have any examples?

Re:macOS Sonoma Boot Failures by JumpCrisscross on Tuesday October 31, 2023 @07:03PM (#38092563)
> Where? Do you have any examples?

The whole battery gate saga. Touch Bar. The 2013 Mac Pro [1].

[1] https://www.theverge.com/2017/4/4/15175994/apple-mac-pro-fai...

Re:macOS Sonoma Boot Failures by FirmwareBurner on Tuesday October 31, 2023 @07:09PM (#38092608)
Yeah but that only proves my original point that Apple only admits mistakes when the public scandals are so violent it can't possibly deny them anymore as the shit pile broomed under the carped has grown so large it makes even them trip on it, so then they just enter damage control mode and PR recovery but not out of the kindness of their heart but because of media backlash.

But they never have the common sense to release statements like "hey, the latest MacOS update might brick some systems so we're pulling the updated until we can do further testing and patching, if you've been affected by the bug already go to a Apple store and have it fixed for free".

Re:macOS Sonoma Boot Failures by JumpCrisscross on Tuesday October 31, 2023 @07:48PM (#38092875)
They have pulled updates [1]. The one person I know who was affected was given a replacement.

I suppose I'm failing to see the need for a public statement if you've fixed the problem and provide service to those affected. Nobody can pull the faulty update anymore. And it's not like someone with a bricked device is more likely to see a PR statement than seek out support.

[1] https://osxdaily.com/2023/07/11/apple-pulls-rapid-response-u...

Re:macOS Sonoma Boot Failures by pmarreck on Wednesday November 01, 2023 @08:02AM (#38097151)
methinks you're the self-victim of some confirmation bias here, sir.
Re:macOS Sonoma Boot Failures by tpmx on Tuesday October 31, 2023 @07:14PM (#38092644)
It's not "refreshing" to hide problems.
Re:macOS Sonoma Boot Failures by JumpCrisscross on Tuesday October 31, 2023 @07:49PM (#38092880)
> It's not "refreshing" to hide problems

Hiding entails ignoring the problem. They're not doing that. Their track record is to fix it. Not every action needs an accompanying tweet and blog post.

Re:macOS Sonoma Boot Failures by tpmx on Tuesday October 31, 2023 @08:15PM (#38093092)
Of course they are not ignoring the problem, internally. The issue issue at hand is that they are not being open about the problem.
Re:macOS Sonoma Boot Failures by TylerE on Tuesday October 31, 2023 @08:05PM (#38093009)
It IS refreshing not to be insulted by the usual "You are important to us and we're taking this very seriously" PR fluff.
Re:macOS Sonoma Boot Failures by cirrus3 on Tuesday October 31, 2023 @09:24PM (#38093527)
Maybe because it isn't that big of an issue? Have you heard about this anywhere besides HN? If it were a big deal you know all the websites would be all over it as if the Mac were doomed.
Re:macOS Sonoma Boot Failures by gcr on Tuesday October 31, 2023 @10:01PM (#38093762)
Google this week seems to be going through a similar bug on their flagship Android 14 release, affecting users who have multiple accounts set up. They also seem to be favoring a "minimal" strategy when it comes to PR communication surrounding this issue.
Re:macOS Sonoma Boot Failures by tpmx on Tuesday October 31, 2023 @11:14PM (#38094229)
Okay?
Re:macOS Sonoma Boot Failures by tpmx on Tuesday October 31, 2023 @04:56PM (#38091255)
That would be: not delivering while still charging a premium.
Re:macOS Sonoma Boot Failures by rainbowzootsuit on Tuesday October 31, 2023 @09:02PM (#38093398)
"You're updating it wrong." —Steve
Re:macOS Sonoma Boot Failures by solarkraft on Sunday November 05, 2023 @09:45AM (#38151565)
> Most companies would consider "the upgrade sometimes bricks the device" to be a release-stopping bug

I've run into such horrific bugs during pretty normal use that I don't think this anymore.

Re:macOS Sonoma Boot Failures by pb7 on Tuesday October 31, 2023 @06:00PM (#38092009)
It's a bug...
Re:macOS Sonoma Boot Failures by tpmx on Tuesday October 31, 2023 @06:03PM (#38092044)
It's a device bricking bug.
Re:macOS Sonoma Boot Failures by astrange on Tuesday October 31, 2023 @09:42PM (#38093663)
Brick usually means unfixable without an EEPROM replacement or data loss.

It's not possible (well, it's very difficult) to do this on an Apple Silicon Mac; once there's an update you can always apply it from another Mac, like the steps on this page do, and your data is still there. With Intel Macs it's possible.

Re:macOS Sonoma Boot Failures by cesarb on Tuesday October 31, 2023 @10:22PM (#38093885)
> Brick usually means unfixable without an EEPROM replacement or data loss.

The definition of "bricked" is not set in stone; a lot of what a normal person would consider "bricked" (doesn't turn on, or turns on to an unresponsive black screen, and no magic sequence of button presses can reset it to working order) could be fixed by a power user with the right equipment, software, and knowledge.

In this case, it requires fairly expensive equipment (another $2.5-10k device), somewhat easy to acquire software, and the appropriate set of instructions, to overwrite the device's broken firmware with a working copy; you don't have to open up the device and plug a JTAG adapter, but using the DFU protocol is very similar to that, since in both cases you're writing directly to the firmware under control of an external device. This is not like "BIOS FlashBack" and similar on non-Apple PCs, in which the device can rewrite its firmware by itself from a common USB stick.

(Also, about data loss: a device with removable storage could get bricked without any data loss, and fixed also without any data loss, simply because the data storage is separated from the firmware and from most of the hardware. It's Apple's insistence on non-removable storage which risks losing data when something else makes the device fail to boot.)

Re:macOS Sonoma Boot Failures by astrange on Tuesday October 31, 2023 @10:35PM (#38093960)
> In this case, it requires fairly expensive equipment (another $2.5-10k device)

A few minutes of access to one, not ownership of it, and hardly any system requirements on it.

> It's Apple's insistence on non-removable storage which risks losing data when something else makes the device fail to boot.

That's actually not the reason. All storage is removable if you just desolder it. It's because the storage is encrypted and you can't extract the keys.

Re:macOS Sonoma Boot Failures by Joeri on Wednesday November 01, 2023 @03:38AM (#38095531)
But how would they then keep up their profit margins to keep shareholders happy? Their first obligation is to the shareholder, not to the customer.

(I think it is ridiculous that the system works in that way, especially for a company that hasn’t needed investors in over a decade, but it is what it is.)