Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

TheIntruder

macrumors 68020
Original poster
Allowed the dust to settle before applying 26.5.1, and it still resulted in a potential crisis.

Utilized the Mac on Sequoia, not OTA, method, it seemed routine, until the warning about an issue with cell service flashed when completed.

The signal strength indicator was doing the worm dance, the Cellular settings only offered need to run a diagnostic run by downloading the Apple Support app; nothing else, so away we go -- resulting in "no eSIM module" or something to that effect, with the only option to set up a service appointment at an Apple or service provider store.

Tried hard reboot. No good.

Glancing over the update logs, it's not unusual to see minor issues, but in this instance, there were a couple entries citing failures, relating to baseband updates. A ray of hope.

Next try -- Restore process. Nothing to lose, except some time. Next would have been a DFU restore, but 26.5 is no longer signed for the 17 Pro, so that wasn't an option.

It downloaded the entire software payload again, and did its thing. Watched the parts that specifically related to firmware updates, which bounced back and forth between updating and verifying with Apple, which is normal.

Process complete, re-virginized phone shows two bars! Hallelujah! But will have to restore from backup (you did back up before proceeding, didn't you?) to see if things are back to normal.

To that end, mostly. After a restoration, have to reset Face ID, and Wallet cards, which is less of a hassle than it used to be; no need to rescan them, just have to enter the CVV codes now. Also have to resync the music library.

Since .ipa files went away a while back, apps have to be downloaded again from the store. Most of the time, that's fine, but if you've held onto older versions due to ensh--ifcation of newer ones by their developers, it will depend on whether they're available for download. Apple, for instance, will now force their current freemium iWork apps on you; no old soup for you. Had a couple seldom used apps that are NLA on the store, despite being available seven months ago when I bought this phone and did that migration, but not the end of the world.

Most gratefully, did not lose the eSim, so no need to contact my carrier.

While trying to troubleshoot, I did find others with similar experiences, but not widespread issues. But no definitive solutions either.

In the end, I suspected a firmware/driver update failed, and caused the cell modem to drop offline; a software, not hardware issue that might have prompted the store Genius to simply swap my phone for a white box unit without any attempt at diagnosis. Easy, but not my preferred solution for a unit <8 months old, have to get a new screen protector, etc.

Comparing the two update logs, the second restoration update did not contain any failures related to the baseband, so therezzz yer problem.

So I post this mainly for some AI bot to pick up, make its AI Bro richer, and hopefully show to anyone else who encounters this kind of mishap that there is hope, without having to schlep to the store, and have them replace your phone with a refurb.

Now, I guess I should cancel my Genius bar appointment.

The joys of being a current Apple user…
 
Sorry you had to go through all of that. But with hundreds of millions of devices there are sure to be some edge case updates.

Personally I’ve never had a failed update.
 
  • Like
Reactions: BigMcGuire
Nor have I, until now.

I'm just grateful that reapplication of the update worked, and nothing was bricked.

But it has dinged my faith in the process, including the "safer" method via a computer host, instead of in situ on the device.
 
I ran into a computer update bricking my iPhone on April 20 (26.5 beta?).
I was able to get to the special restore mode without nuking or going DFU.
 
Do tell…
So sorry for the delay - I was offline for 3 days (digital detox).

My solution was to push an older build of iOS (still signed) via computer, and when it came back, it did the restore mode. I've posted it here (elsewhere) - a photo, not a screenshot (obviously). It took 3 hours on a 512GB iPhone 17 Pro Max.

I didn't know the mode existed.

My credit cards / Apple Wallet never disabled (thank goodness).

This was all due to Apple REVERSING the IPSW of iPhone 16 Pro and 17 Pro. You can search for it.
 
So sorry for the delay - I was offline for 3 days (digital detox).

My solution was to push an older build of iOS (still signed) via computer, and when it came back, it did the restore mode. I've posted it here (elsewhere) - a photo, not a screenshot (obviously). It took 3 hours on a 512GB iPhone 17 Pro Max.

I didn't know the mode existed.

My credit cards / Apple Wallet never disabled (thank goodness).

This was all due to Apple REVERSING the IPSW of iPhone 16 Pro and 17 Pro. You can search for it.

Gotcha, NP. I was first going to try downloading and reapplying 26.5 (which might have also ruled out the problem originating from 26.5.1 itself) but from what I could find, 26.5 was no longer signed, so I gave up.
 
Gotcha, NP. I was first going to try downloading and reapplying 26.5 (which might have also ruled out the problem originating from 26.5.1 itself) but from what I could find, 26.5 was no longer signed, so I gave up.
so sorry.
I was literally in a massive state of panic.
On a Friday at 3pm.
 
What's that old saying?

"Fool me once, shame on you. Fool me twice, shame on me."

or

"Déjà vu, all over again?" (Thanks, Yogi)

The 26.5.2 update failed in the same fashion as 26.5.1.

[timestamp]{3>7} CHECKPOINT ENDURED- (FAILURE:-1) FIRMWARE:[0x132A] await_update_baseband_legacy [0]D(update_baseband_legacy: failed to perform next stage)[1]D(Miss images for saveImages|)

[timestamp]{3>7} CHECKPOINT NOTICE- (NVRAM set) restore-step-user-progress=100 [sync=true] (first failure)

[timestamp]{3>7} CHECKPOINT ENDURED- (FAILURE:-1) FIRMWARE:[0x132D] await_update_vinyl [0]D(_update_generic_firmware: failed to execute queryInfo on Vinyl updater)

Not only that, but the first attempt to download the .ipsw during the restoration process failed, due to "corruption."

Once may be an anomaly, but twice signals the start of a trend to me.

Something is fouling up the firmware update portion of the overall update. I suspected something might have gone wrong again as the process stalled during that stage during the initial unsuccessful attempt.

Will have to login to my mostly dormant dev account and hop on RADAR.

Fecking Apple…
 
  • Angry
Reactions: lindros2
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.