Apple Admits iPhone 18 Pro Max Glitch Leaves AT&T Users Stuck on 'SOS'

Where the signal bars should be in the status bar, there's just an "SOS" label instead — that's what some iPhone 18 Pro Max owners have been seeing on their screens these past few days. No calls, no texts, no 4G or 5G data at all. According to 9to5Mac, Apple has confirmed this is a real hardware issue, currently limited to users on AT&T's network in the US.

In a statement to 9to5Mac, Apple said: "We've identified an issue affecting a small number of iPhone 18 Pro Max users on AT&T's network that can cause the device to lose signal and become unable to make calls. We released iOS 27.0.1 earlier this week and strongly recommend all iPhone 18 Pro Max users update immediately. We're also rolling out a carrier settings update today. Together, these two updates are designed to prevent this issue from occurring."

The key word here is "prevent" — meaning the patch only works for devices that haven't already run into the problem. For phones that have already completely lost signal, a software update or restore won't fix it. Apple says affected users will need to contact Apple Support or AT&T for a hardware replacement.

How to tell if your phone is affected

The signs are straightforward: an SOS symbol in the status bar, no ability to make calls or send texts, and no mobile data. Apple emphasizes that only a "small number" of AT&T iPhone 18 Pro Max users are affected — this isn't a widespread issue.

If you haven't seen any symptoms yet, the first step is updating to iOS 27.0.1 as soon as possible, via Settings > General > Software Update. Even if you've already updated your OS, it's worth double-checking that your carrier settings are current too — trigger the update prompt the same way, under Settings > General > About. If no pop-up appears, that usually means you're already on the latest version.

One notable detail: the iPhone 18 Pro Max is currently the only model sold in the US that uses a Qualcomm modem instead of Apple's own in-house modem. Apple hasn't said whether this hardware difference is directly tied to the bug, and so far there's no clear evidence linking the two.