# Mac “SOS” signal

**URL:** <https://talk.tidbits.com/t/mac-sos-signal/33061>\
**Category:** TidBITS Talk\
**Created:** [March 12, 2026, 3:55am UTC](https://talk.tidbits.com/t/mac-sos-signal/33061 "2026-03-12T03:55:32Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 12, 2026, 3:55am UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/1 "2026-03-12T03:55:32Z")

</div>

Today is a bad day. Installed the latest macOS update and it bricked my Mac. Never happened before (IIRC) and I’ve been using Macs since 1984.

Won’t even power on. Finally saw this light flashing a strange pattern. Watched close and noticed it’s SOS! Started thinking it was ransomware but then Google said it’s a firmware issue.

![image](https://talk.tidbits.com/uploads/default/original/3X/4/5/451748de1f2d372e8dc19b909da5233b300f3c3a.gif)

Tried recovering from another Mac but that failed. Now the other Mac can’t even connect to it.

Genius Bar appointment tomorrow but the recovery process warned my data might be lost. Seems unacceptable to me that a firmware issue should trash a terabyte of good data.

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 12, 2026, 4:10am UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/2 "2026-03-12T04:10:32Z")

</div>

First I tried the Apple Configurator tool per something online, but it offered no help.

 ![Screenshot 2026-03-11 at 9.19.24 PM](https://talk.tidbits.com/uploads/default/original/3X/c/f/cfb24e013668e12bc1c90b45725e7eca917f69c1.jpeg)

Then I found this support article:

> **[How to revive or restore Mac firmware - Apple Support](https://support.apple.com/en-us/108900)**
>
> Rarely, a Mac with Apple silicon or the Apple T2 Security Chip might experience an issue that requires its firmware to be revived or restored by another Mac.

It seems Finder should handle it. So I connected to my MacBook with a USB C cable (both ends) and got this on the MacBook (the working device):

 ![Screenshot 2026-03-11 at 9.05.04 PM](https://talk.tidbits.com/uploads/default/original/3X/9/c/9cf05638f9d4b3155b897ef79e2efdfa149b3485.jpeg)

This was not encouraging:

 ![Screenshot 2026-03-11 at 9.05.16 PM](https://talk.tidbits.com/uploads/default/original/3X/d/0/d002ddadba51c72d48c31aeca429a9c095c17150.jpeg)

After it installed a multi-GB firmware and tried to install it, I got this:

 ![Screenshot 2026-03-11 at 9.18.08 PM](https://talk.tidbits.com/uploads/default/original/3X/5/2/525be211ea6c99c9600e59c1263bc644df02925d.jpeg)

Now I cannot even connect to the other Mac.

This feels fascist. Not sure if Apple is trying to protect from hacking, but a firmware problem shouldn’t brick all your data.

---

<div class="post-metadata">

**Author:** ![ace](https://talk.tidbits.com/user_avatar/talk.tidbits.com/ace/32/19369_2.png) [@ace](https://talk.tidbits.com/u/ace)\
**Post date:** [March 12, 2026, 1:49pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/3 "2026-03-12T13:49:27Z")

</div>

> [@dave1](#):
>
> This feels fascist. Not sure if Apple is trying to protect from hacking, but a firmware problem shouldn’t brick all your data.

Let’s not jump to attributing malicious intent to what would seem most likely to be a hardware failure. A modern Mac is a highly complex system, so it doesn’t surprise me at all that a firmware failure would render the entire thing unusable.

I hope you have a current backup!

---

<div class="post-metadata">

**Author:** ![mikebhm](https://talk.tidbits.com/letter_avatar_proxy/v4/letter/m/977dab/32.png) [@mikebhm](https://talk.tidbits.com/u/mikebhm)\
**Post date:** [March 12, 2026, 1:58pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/4 "2026-03-12T13:58:20Z")

</div>

Not clear to me whether you got that message after attempting “Revive” or “Restore”. I have never had any joy with “Revive” but always have with “Restore”.

---

<div class="post-metadata">

**Author:** ![bb1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/bb1/32/13421_2.png) [@bb1](https://talk.tidbits.com/u/bb1)\
**Post date:** [March 12, 2026, 3:19pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/5 "2026-03-12T15:19:34Z")

</div>

If encryption keys are lost, then yes, your data is lost too. That’s not fascist, its math. :)

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 12, 2026, 5:20pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/6 "2026-03-12T17:20:24Z")

</div>

> [@ace](#):
>
> Let’s not jump to attributing malicious intent

Yea, sloppy use of words. I don’t mean malicious intent. Just heavy-handed from the Big Guy with careless disregard for the impact on us Little People.

> A modern Mac is a highly complex system, so it doesn’t surprise me at all that a firmware failure would render the entire thing unusable.

Yea, sorry… that’s not okay. That’s not progress. I get security, and having the entire disk decrypted on the fly, and protection from USB hacks, etc. But if the firmware gets screwed up, you should be able to fix that with connection to a remote Mac without losing any of your data.

Stay tuned… with the Genius now :-)

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 12, 2026, 5:34pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/7 "2026-03-12T17:34:20Z")

</div>

> [@mikebhm](#):
>
> Not clear to me whether you got that message after attempting “Revive” or “Restore”.

Restore said it would erase everything, so that was not high on my list of preferred choices :-) I tried Revive, which apparently just tries to fix the firmware.

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 12, 2026, 5:38pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/8 "2026-03-12T17:38:48Z")

</div>

> [@bb1](#):
>
> If encryption keys are lost, then yes, your data is lost too. That’s not fascist, its math. :)

I’m not sure how their key management works. But it should be under my control. I’m still me, it’s still my Mac, and I authorize the recovery of that data. How Apple accomplishes that goal determines whether their architecture is lousy or not. Might not be fascist, but it’s more than simple math; it’s a design choice.

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 12, 2026, 5:52pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/9 "2026-03-12T17:52:33Z")

</div>

UPDATE: currently at the Genius Bar. Some definite progress.

He’s using some Apple diagnostic app, btw; not Apple Configurator. Anyway, the Apple Support article CLEARLY stated to use a USB-C cable and NOT a Thunderbolt cable:

> A USB-C to USB-C ![USB-C to USB-C](https://cdsassets.apple.com/live/7WUAS350/images/inline-icons/usb-icon.png) cable that supports data and charging, such as the Apple USB-C Charge Cable included with some Apple products. It works with [ports on Mac](https://support.apple.com/en-us/109523) that accept a type USB-C connector._Don’t use a Thunderbolt 3_ ![Thunderbolt 3](https://cdsassets.apple.com/live/7WUAS350/images/inline-icons/thunderbolt-icon.png)_cable._

The Genius tried that ( **USB-C** ) and, like me, failed.

He then tried a newer **Thunderbolt Cable (he thinks 4 or 5),** and that also didn’t work.

Finally, he tried a **Thunderbolt 3** (he thinks) cable. That actually made progress. It connected to the app on his MacBook and presented recovery options. I’m not sure what all went on inside his app, what he clicked on, etc. The background image on his app said “DFU”. Whatever he did ultimately lit up the screen on my Mac mini for the first time since this all started, including my familiar wallpaper and avatar and login prompt. I logged in several times, and saw my Finder with all my favorites in the sidebar, etc. A good sign.

Then we noticed it’s running **26.2, not 26.3.1**. The update to the latter is what bricked this so I told him I want that upgrade done before I leave the store :-D So that’s currently in progress…

---

<div class="post-metadata">

**Author:** ![Simon](https://talk.tidbits.com/user_avatar/talk.tidbits.com/simon/32/1180_2.png) [@Simon](https://talk.tidbits.com/u/Simon)\
**Post date:** [March 12, 2026, 6:27pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/10 "2026-03-12T18:27:15Z")

</div>

> [@dave1](#):
>
> But if the firmware gets screwed up, you should be able to fix that with connection to a remote Mac without losing any of your data.

Which is exactly what Revive does.

> **[Use Fallback Recovery on Apple silicon Macs](https://eclecticlight.co/2026/02/24/use-fallback-recovery-on-apple-silicon-macs/)**
>
> What do you do if you can’t start your Apple silicon Mac in Recovery? Try Fallback Recovery, as explained in detail here.

> **[How to revive or restore Mac firmware - Apple Support](https://support.apple.com/en-us/108900)**
>
> Rarely, a Mac with Apple silicon or the Apple T2 Security Chip might experience an issue that requires its firmware to be revived or restored by another Mac.

Also important is to use the right port. And Apple doesn’t make that easy if you’re trying to wing it. But there is a doc that explains exactly which port to attach that USB-C (non-TB!) cable to.

> **[Apple silicon Macs have 2 types of Thunderbolt ports](https://eclecticlight.co/2026/02/06/apple-silicon-macs-have-2-types-of-thunderbolt-ports/)**
>
> One Thunderbolt port is the designated DFU port, to be used when connecting via USB-C in DFU mode, and to be avoided for external bootable disks. But how can you identify it?

> **[How to identify the DFU port on Mac - Apple Support](https://support.apple.com/en-us/120694)**
>
> Learn how to find the device firmware update port on your Mac.

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 12, 2026, 10:47pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/11 "2026-03-12T22:47:18Z")

</div>

Okay, well this is just loaded with interesting info! I know the ports on the new Neo are not identical.

Anyway, note that I did try Revive. It tried and failed. Apparently it won’t even try if you’re not in the DFU port. See screen shots. But choosing the **right port** (and apparently **correct cable** ) will apparently be two (cryptically obfuscated) details I’ll double check next time this happens! Nota bene!

---

<div class="post-metadata">

**Author:** ![mpainesyd](https://talk.tidbits.com/user_avatar/talk.tidbits.com/mpainesyd/32/3272_2.png) [@mpainesyd](https://talk.tidbits.com/u/mpainesyd)\
**Post date:** [March 12, 2026, 11:48pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/12 "2026-03-12T23:48:46Z")

</div>

I might mark my “DFU” port with a pen - just in case!

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 13, 2026, 12:12am UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/13 "2026-03-13T00:12:00Z")

</div>

> [@mpainesyd](#):
>
> I might mark my “DFU” port with a pen - just in case!

Yes! God forbid Apple would ever mark something like that! At least the software tells you when you’re in the wrong port on the Neo!

[https://medium.com/apple-fanboy/the-wrong-hole-alert-the-confusing-reality-of-the-macbook-neos-unbalanced-usb-c-setup-60d69041b248](https://medium.com/apple-fanboy/the-wrong-hole-alert-the-confusing-reality-of-the-macbook-neos-unbalanced-usb-c-setup-60d69041b248)

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 13, 2026, 7:47pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/14 "2026-03-13T19:47:52Z")

</div>

Shout out to Jason at the Apple Store in King of Prussia, PA, for being a rock star!

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 13, 2026, 10:40pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/15 "2026-03-13T22:40:32Z")

</div>

> [@mpainesyd](#):
>
> I might mark my “DFU” port with a pen

If I mark mine, I’ll leave off the “D” 😅

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 14, 2026, 12:33am UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/16 "2026-03-14T00:33:36Z")

</div>

Small updates for the record:

- I keep an **external SSD** where my Photos Library is stored. When I reconnected it to the recovered Mac, it didn’t mount. After I ran First Aid on it with Disk Utility, it was able to mount. Not sure what that was about, but glad it was uneventful.
- Also since the recovery / upgrade, my **Arq** backup started complaining about errors accessing files under my wife’s account. I’m currently troubleshooting that. Don’t know if it’s related to the upgrade or the recovery.

---

<div class="post-metadata">

**Author:** ![Simon](https://talk.tidbits.com/user_avatar/talk.tidbits.com/simon/32/1180_2.png) [@Simon](https://talk.tidbits.com/u/Simon)\
**Post date:** [March 14, 2026, 3:20pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/17 "2026-03-14T15:20:38Z")

</div>

> [@dave1](#):
>
> When I reconnected it to the recovered Mac, it didn’t mount. After I ran First Aid on it with Disk Utility, it was able to mount.

Did it just not auto-mount? Or did it refuse to mount when you opened Disk Utility, selected the disk, and hit mount?

I’ve seen an intermittent macOS bug where USB-attached storage from time to time just fails to auto-mount. It seems worse with encrypted volumes while TB instead of USB helps, but due to the bug’s intermittent nature, it’s hard to nail down.

---

<div class="post-metadata">

**Author:** ![dave1](https://talk.tidbits.com/user_avatar/talk.tidbits.com/dave1/32/13937_2.png) [@dave1](https://talk.tidbits.com/u/dave1)\
**Post date:** [March 14, 2026, 3:37pm UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/18 "2026-03-14T15:37:19Z")

</div>

> [@Simon](#):
>
> Did it just not auto-mount? Or did it refuse to mount when you opened Disk Utility, selected the disk, and hit mount?

Great question. I should recall, but I don’t. I feel like I tried that (and failed), but I’m not sure. But it’s also possible that its failure to auto-mount, combined with the recent Mac recovery, made me feel that it was wise to run First Aid regardless, and so I did.

I will say that I did try reseating both ends of the cable several times before taking the steps with DU.

> [@Simon](#):
>
> I’ve seen an intermittent macOS bug where USB-attached storage from time to time just fails to auto-mount.

Yes, this drive has the bad habit of unmounting randomly. Sometimes I’ll find out because Photos has quit; other times my Arq backup will give errors.

---

<div class="post-metadata">

**Author:** ![bjbear71](https://talk.tidbits.com/letter_avatar_proxy/v4/letter/b/cdc98d/32.png) [@bjbear71](https://talk.tidbits.com/u/bjbear71)\
**Post date:** [March 19, 2026, 8:36am UTC](https://talk.tidbits.com/t/mac-sos-signal/33061/19 "2026-03-19T08:36:42Z")

</div>

Yay! My former work location (now retired). Glad they fixed/helped with your Mac issue.
