Bricked devices due to update to 26.4.1. We are restore some with Apple Configurator but will want to see:
a) What is causing this.
b) How can we prevent this.
It would be difficult, if not impossible, to say why a comparatively rare thing happens, especially with so little information.
You may want to contact Apple Support and see if they can run diagnostics.
If you are referring to this posting Software update bricked My m2 MacBook Pro
https://discussions.apple.com/thread/256271299?sortBy=oldest_first
There has been several suggestions to mediate this unfortunate issue which included the Usage of DFU mode
When an update is being installed
It is usually suggested to have the computer running when it is plugged into the charger
From my experience when I have it plugged in to charger and I shut down the computer
It is totally normal for the Mag Safe light to blink from Green to Orange and sometime black back to green( depending on if the batter has reached 100 % charged
You have given us absolutely no useful information that would allow us to help you troubleshoot whatever problem you're having.
I, for one, am not going to try to Hunt down your previous posts regarding similar (similar to what?) issues.
Either explain your problems or contact Apple for support.
The MacBook Air M3 has been bricked mid-way through the macOS 26.4.1 update. It has not recovered since.
Symptoms, precisely:
Forum threads across internet tell us of similar outcomes — following the 26.4.1 update.
daksh_dev wrote:
Forum threads across internet tell us of similar outcomes — following the 26.4.1 update.
You'll find threads after every update. And in every week that includes a Wednesday. That doesn't mean 1) the update (or the Wednesday) is always the problem, and 2) that it's common.
IdrisSeabright wrote:
daksh_dev wrote:
Forum threads across internet tell us of similar outcomes — following the 26.4.1 update.
You'll find threads after every update. And in every week that includes a Wednesday. That doesn't mean 1) the update (or the Wednesday) is always the problem, and 2) that it's common.
The update is the problem.
It might not be common, in a sense you want to accept, but it's there.
daksh_dev wrote:
The update is the problem.
That's impossible to know at this point. Remember, post hoc ergo propter hoc.
It might not be common, in a sense you want to accept, but it's there.
I understand that the fact that it's not common isn't very comforting if the problem is happening to you. However, it's important to realize that uncommon problems are frequently much harder to resolve as there's just less data.
These are not isolated cases.
I posted my case a while ago. It's akin to the one mentioned above.
Bricked devices after update 26.4.1: Cause and prevention
