Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I always restart after an update as well.
I don't understand why people are getting defensive about this.

All I said was that it was not necessary to manually restart unless you're actually having issues like battery drain or stuttering. I leave it plugged in for half hour after the update so it can finish with any background processing, and rarely do I experience any issue.
If you believe that's helping your experience, then by all means. But it's not necessary as a reboot is part of the update process itself.
 
Updated 16 PM without any issue a few minutes ago
I also did update my 17 Pro without issues but they mixed IPSW files for 17P and 16P.
When I click on 17P it starts downloading IPSW for 16P.

Zrzut ekranu 2026-05-8 o 21.36.08.png
Zrzut ekranu 2026-05-8 o 21.36.24.png


iPhone18,1 - iPhone 17 Pro
iPhone17,1 - iPhone 16 Pro
 
I don't understand why people are getting defensive about this.

All I said was that it was not necessary to manually restart unless you're actually having issues like battery drain or stuttering. I leave it plugged in for half hour after the update so it can finish with any background processing, and rarely do I experience any issue.
If you believe that's helping your experience, then by all means. But it's not necessary as a reboot is part of the update process itself.
It seems like you are the one getting defensive about your statement, right? All I did was state that I also typically do a restart after an upgrade. (Obviously we know that the upgrade process restarts the device during the process.)

Why is simply making a statement defined as “becoming defensive?”
 
It seems like you are the one getting defensive about your statement, right? All I did was state that I also typically do a restart after an upgrade. (Obviously we know that the upgrade process restarts the device during the process.)

Why is simply making a statement defined as “becoming defensive?”
You felt the need to respond to my response to someone else unprompted. I wasn't looking for data points with that. So yes, I'm the one getting defensive.

Let's move on to the bugs on RC2 now.
 
Wouldn’t doubt it if this release was just the 205 safari fixes posted yesterday:

Update: apparently RC2 is “laser-focused on Apple Watch 🔬

UserNotificationsCore gets a file data-protection fix for Watch notification forwarding — classic BFU bug

WatchFacesWallpaperSupport snapshot renderer refactored: per-look progress tracking replaces the old orientation→MTLBuffer map

Kernel/iBoot untouched — purely a Watch reliability patch”
 
Last edited:
  • Like
Reactions: souko and f12003_ga
I’ve wondered if the phone restarting as part of an update is the same as a forced restart. I’ve noticed that after a software update restart, the phone stays connected to WiFi, the a forced restart does not retain the WiFi connection and only shows cellular for a phone.
It’s only slightly different.
It connects to the WiFi since you’re authenticating with a passcode before the update begins.
While on a hard restart you’re not.
Only difference being the authentication. Everything else is the same.
 
Apple needs to find a way to fix bugs in specific apps without having to wait and then push an entire iOS update.

I say *need*, but they've never done it so I suspect it's more a "want" on my side 😁
Well no I found bugs in RC 1 that doesn’t require apps. Apple needs to find a way to fix bugs without releasing multiple updates on my iPhone 17.
 
  • Like
Reactions: Hans300
It’s only slightly different.
It connects to the WiFi since you’re authenticating with a passcode before the update begins.
While on a hard restart you’re not.
Only difference being the authentication. Everything else is the same.
If the secure enclave is still open (or unlocked, whatever the correct word is) and the credentials still cached, then this could mean that other caches aren't flushed during the OS reload.

I do a hard reboot (when I remember to do so!), usually a few minutes after the upgrade. It's most likely achieving nothing, but I do it anyway.
 
Went to an Apple Premium Reseller (iStores Czechia) today to see if iOS is still a buggy mess.

The sales guy asks which model I used to have, I say "17 Pro Max." Then he asks where I bought it.

I told him I got it at a local electronics chain (Datart), and this man literally says: "Well, if you'd bought it from us..."

Like they have a special holy version of iOS that doesn't have any bugs?? I just died laughing and walked straight out.
 
If the secure enclave is still open (or unlocked, whatever the correct word is) and the credentials still cached, then this could mean that other caches aren't flushed during the OS reload.

I do a hard reboot (when I remember to do so!), usually a few minutes after the upgrade. It's most likely achieving nothing, but I do it anyway.
Slightly more technical answer.
When you manually restart, the device enters the Before First Unlock (BFU) state which means everything’s fully secured.

In case of a software update, a token is set that allows the device to (not completely) bypass the fully secure BFU state to connect to WiFi. This is on purpose to verify the update hasn’t been tampered with among other things. The bypass is only possible since you’re already prompted for a passcode before the update begins.

The changes in state are minimal and with practically no difference between the two otherwise.

Personally, I wouldn’t suggest hard reboots without an issue. While we’ve come a long way from “It’s now safe to turn off your computer” days, you’re still abruptly killing active processes with a hard restart.
 
The ipsw file available for download for iOS 26.5 RC and RC 2 for iPhone 17 Pro are not correct. The file that is getting downloaded upon clicking link for the ipsw file for iPhone 17 Pro on the page https://developer.apple.com/download/os/ are -

For RC: https://updates.cdn-apple.com/2026S...1951E4AE07/iPhone17,1_26.5_23F75_Restore.ipsw

For RC 2: https://updates.cdn-apple.com/2026S...3C2005AF64/iPhone17,1_26.5_23F77_Restore.ipsw

This downloaded files from above links are not compatible with iPhone 17 Pro.
When we try to update the iPhone 17 Pro using the above mentioned ipsw files, it gives error "The iPhone "xxxxxx" could not be updated because the firmware file is not compatible."
 
The ipsw file available for download for iOS 26.5 RC and RC 2 for iPhone 17 Pro are not correct. The file that is getting downloaded upon clicking link for the ipsw file for iPhone 17 Pro on the page https://developer.apple.com/download/os/ are -

For RC: https://updates.cdn-apple.com/2026S...1951E4AE07/iPhone17,1_26.5_23F75_Restore.ipsw

For RC 2: https://updates.cdn-apple.com/2026S...3C2005AF64/iPhone17,1_26.5_23F77_Restore.ipsw

This downloaded files from above links are not compatible with iPhone 17 Pro.
When we try to update the iPhone 17 Pro using the above mentioned ipsw files, it gives error "The iPhone "xxxxxx" could not be updated because the firmware file is not compatible."
As mentioned above they mixed up 16 Pro and 17 Pro update files. If you have 17 Pro you must choose 16 Pro.
 
  • Like
Reactions: NBKindaGirl
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.