Btw has anyone updated from iOS 26.2.1 to 26.3 without getting stuck on the Apple logo? We have a case still got stuck when updating from iOS 26.2 to 26.3 for now.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Getting stuck on Apple screen with progress bar every time I do an update
- Thread starter jfiggy77
- Start date
- Sort by reaction score
It got stuck for how long? I guess it’s taking a long time to clean the system cache.
Just want to update that my update to iOS 26.3 went fast and smooth.
Mine was stuck for both 26.2 and 26.2.1, both times I restored from backup, a procedure that took all night and most of the next day. Also, because I had WhatsApp still up on my computer, I was able to continue conversations during that time. HOWEVER, after that, once I logged into WhatsApp on the restored iPhone, as it was considered a new device, I had to re-sync my Mac and as a result I lost all conversations since my last backup (about 2 days worth!).
This time I decided to do the update over the weekend and close WhatsApp on my Mac as well so that all new messages would just wait in line until I'm back online on both devices. But, as I wrote above, this update completed very quickly.
I thought that maybe Apple fixed something and from now on everything will be fine again. But then I read niltonhc 's post above and saw that his update to 26.3 failed. So either there's something else at play, like seaweed_coast 's idea that it relates to the size of your System Data, or maybe it's just the update after 26.2 that will fail or something else altogether.
Mine was stuck for both 26.2 and 26.2.1, both times I restored from backup, a procedure that took all night and most of the next day. Also, because I had WhatsApp still up on my computer, I was able to continue conversations during that time. HOWEVER, after that, once I logged into WhatsApp on the restored iPhone, as it was considered a new device, I had to re-sync my Mac and as a result I lost all conversations since my last backup (about 2 days worth!).
This time I decided to do the update over the weekend and close WhatsApp on my Mac as well so that all new messages would just wait in line until I'm back online on both devices. But, as I wrote above, this update completed very quickly.
I thought that maybe Apple fixed something and from now on everything will be fine again. But then I read niltonhc 's post above and saw that his update to 26.3 failed. So either there's something else at play, like seaweed_coast 's idea that it relates to the size of your System Data, or maybe it's just the update after 26.2 that will fail or something else altogether.
Can anyone actually explain what the issue is here?
Does it happen with OTA or via IPSW?
Does it boot into recovery screen or something else?
Does it happen with OTA or via IPSW?
Does it boot into recovery screen or something else?
macguy167
macrumors member
I have an iphone 13 PM that updates fine to ios 26.3, an iphone 17 PM that also updates fine, but one iphone 17 PM that always crashes at the apple logo with the progress bar almost done. The last several updates I had to go into DFU mode and update then restore (takes a long time due to apps), but now on ios 26.3 it states that after rebooting it will show up in the finder window on the MBP, but now I am still looking at a stuck on apple logo and ready to buy a Samsung Phone!
Why does this always happen? I F***cking hate ios 26, yes apple you suck!!!!!
Would anyone be willing to open a support ticket on Apple’s website? I’ve already submitted one, but I’m concerned this issue may not get addressed if only a small number of tickets are filed. More reports could help get Apple Support’s attention.
macguy167
macrumors member
Stuck the same!
Will I update to 26.3.x, NO!
I will wait on 26.4 at least.
Every update is a 15 hour restore…
Same thing is happening to me. iPhone 17 Pro Max. 2TB. It’s destroying my battery health each time I have to restore.
No, I did not experience this issue with the 26.4 update, but I have encountered it thrice before with one most definitely being the 26.3.1 update. Unfortunately, I can’t recall which updates the other two were. Based on what some users have shared, I just realized that this problem only occurs every other update, regardless of its size?!?! Initially, when I visited the Apple Store, the store associate informed me that I needed to use a computer to update the software, and that the issue was caused by an over-the-air update. However, when I attempted the 26.3.1 update on a computer, it froze. Therefore, this is definitely not the cause of the problem. I am extremely frustrated with this situation and am at a loss for what to do next.
This is like Final Destination. There's no escaping it. You think it will just skip over you by not doing the most current update... and then you wake up the next morning realizing you didn't turn off Automatic Updates. 💀
Hi everyone. I hadn’t checked this forum in a while so I’m glad to see that I wasn’t the only one experiencing this problem. I had the issue several times since my original post. I most recently had it with the first RC last week. Took me about 17 hours to restore from a backup. I have an iPhone 17 Pro Max 2 TB. However, I didn’t have the issue with the official release I installed yesterday OTA. I’ve had the issue with OTA and computer updates so it hasn’t mattered how I’ve done it. In the past, the update usually right after a restore has not failed for me but updates afterwards have so I’m not entirely surprised yesterday’s update installed fine. I’m afraid though that the next update will fail if history repeats itself. I read in one post above that someone believes it may be related to the size of your system data cache right before you do the update. Currently, mine is at 55.48GB. Before I installed yesterday’s update, it was at 157GB. One thing I did differently yesterday is that I rebooted my phone to try and reduce the system data cache first and after my reboot, it had gone done to 112 GB so I then installed the update and it actually installed quickly so perhaps it may in fact be related to the size of the system cache when you do the update. Wish there was a manual way to clear it but there isn’t unfortunately.