iPhone not working after 17.2.1 update

After updating my iPhone last night to 17.2.1 I can no longer connect to my network provider. Tried the resets and still it does not work!

very frustrating.

Trusted Apple and iPhone for years, now not so sure

Posted on Dec 21, 2023 8:24 AM

Reply
Question marked as Top-ranking reply

Posted on Dec 28, 2023 10:22 AM

Solved my problem after 8 hours of troubleshooting! After the 17.2.1 update, my iPhone 14 Pro Max would not send or receive calls and got hot from accelerated battery drain. First AppleCare walked me through hardware diagnostics, network resets, backups and restores but the problem persisted. Next, Verizon helped me with a new eSIM, but the problem continued. Next, I focused on my company's corporate software, because I was intrigued by the VPN discussion in this forum. While I don't use a VPN, my iPhone is managed by my company's installation of Microsoft InTune, which I noticed (Settings:General:VPN & Device Mgmt) had a signing certificate (IOSProfileSigning.manage.microsoft.us) that had expired December 12, 2023. To test this theory, I removed this Management software and my phone's cellular calls worked perfectly again! So for the final steps, I worked with my company's IT department to reinstall the Management software, which has an updated IOS signing certificate, and the phone is now back to normal. Sharing in case others find my painful tech journey useful.

370 replies

Mar 9, 2024 8:56 AM in response to Hedgehog64

After updating my iPhone to the 17.2.1, I’ve had endless problems. Went to Apple, they found no problem. They wanted to reset my phone. Then, they sent us to Verizon. They switched out my SIM for an eSIM. Still having problem. Called Verizon customer service. They sent me a new phone. Updated automatically. Same problem. No one can hear me. I may as well not have a phone. When is the fix coming? I can’t stand this!?!

Feb 22, 2024 11:02 PM in response to Hedgehog64

This workaround seems to get tethering to work via a usb cable on the Mac for me.

The issue seems to be related to IPv4 DHCP address negotiation that arbitrarily fails between the iPhone and the Mac. When it fails, the Mac self-assignes a 169.254.x.x address, which is useless for tethering.


  1. On the Mac, open System Settings and search for Network.
  2. In the Network panel, click on the ellipsis (...) at the bottom right.
  3. Under Locations, choose 'edit locations'.
  4. Click + to add a new location. The name you choose is arbitrary. I just leave it as 'untitled'.
  5. Click 'Done'
  6. Now click on the ellipsis again, choose locations, and select the new location's profile as the active location. Everything should start working again at this point - for awhile.
  7. When it stops working, repeat the process and add a second location ('untitled2') and select that one as the active location profile.
  8. After that, each time it quits working, just toggle back and forth between the two locations and like magic it all starts working again.


Hope this helps. Your mileage may vary.


Feb 17, 2024 10:55 PM in response to Hedgehog64

I installed the 17.2.1 update on my 12 Pro right after it was released before Christmas. Now, after more than three weeks while traveling to family during the holidays without a working cellular connection, and more than 20 hours on the phone with both Apple and T-Mobile Support, and a couple trips to Apple Stores, I finally have a working phone after Apple gave me a new one. However, the problem was never identified or fixed - they finally just gave me a new phone. I am writing this sad saga in hopes that it helps many of you who have the same problem.


After many hours in a half dozen sessions with Apple technical support downloading diagnostics on my phone, the person that I was dealing with said that it was clearly a software issue, and specifically that my phone hardware was fine. In fact, the cellular connection started working at one point while they were collecting diagnostics, and then stopped again for no apparent reason. Luckily this was all documented, because she then recommended that I take it to an Apple Store. They wiped my phone clean, but before restoring ran their own diagnostics, and said that it was a hardware issue, so refused to restore it. They then offered to repair the phone for about $600, basically the price of a refurbished 12 Pro. At this point my phone was a brick.


I refused to pay them because I knew that there was no problem with my phone until their update destroyed my ability to make a cellular connection. It was as if someone at Apple said, "Give me your phone, I'll make it better for you," and then hit it with a big hammer and handed it back. And when I complained that it wasn't working, they say that it was my problem, and that I'd have to pay to have them fix it.


I re-connected with my Apple Technical Support person, and told her that I was unwilling to wait for Apple to figure out their software problem - that I needed a working phone now. She spoke with a supervisor in Customer Service, to whom she connected me. That person asked me a bunch of questions, and after initially saying that it was a hardware problem, relented and authorized a replacement 12 Pro for me at no cost. I found one at a local Apple Store, went in, and traded in my non-working phone for the "new" one which is probably refurbished.


I then had to take the new phone to get a new sim card from T-Mobile, because they had told me to destroy my old one when my phone stopped working. T-Mobile had remotely installed several eSims on my old phone which had worked temporarily, but all eventually ended up not connecting to cellular.


After installing the new sim card, I went back to the Apple Store to have them watch while l restored the new phone in case there was a problem. I didn't want them claiming that I'd damaged the new hardware if it didn't work. The backup that I restored from was done after the 17.2.1 update, which they said shouldn't be a problem, but had me concerned.


It took a while but the restoration process worked fine. Now a month later my phone is still working and connecting to the cellular network. No explanation of why my other phone stopped working, or why this new one with the same 17.2.1 update is working. So the lesson is, don't let them tell you it's a hardware issue - insist that they replace your phone which they damaged with their update.


Makes me wonder if their software somehow causes a change in the phone that shows on diagnostics as hardware damage. And there is nothing from Apple explaining what happened, or even admitting that they caused this issue with so many of their users. Hopefully someday they come out with a new update that fixes the cellular connectivity issue, as well as the many other problems apparently caused by this update, which appears to have been rushed and not adequately tested.


Just don't pay Apple more money to fix the problem that they have caused. Assuming that there isn't a software fix soon, find someone at Apple who can get you a new phone to replace the one that no longer works because of their defective update.


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

iPhone not working after 17.2.1 update

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.