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.
Installed. Let’s see. Overall I was happy with Beta 4.
Regarding the strange iOS 26 cycle so far I would also expect a newer build as the final next week.
 
Last edited:
  • Like
Reactions: luipaard and ikir
How? Elaborate please.
I did Apple Devices shift-click update of the IPSW, it appeared to run and process the update for about 7 or 8 minutes with progress bars on both my monitor and my phone screen, but before it was complete I received a long error message (which could not be photographed due to iphone being inoperable) and progress was halted with the progress bar stuck about 75% of the way complete. Doing a force restart of the phone only puts me in recovery mode. It may have ruined my existing installation of iOS which would result in the need for a full restore and/or the loss of important data. This is an update that should be stayed far away from, it seems it is nothing but trouble
 
Interesting to read so many different opinions. So far for me on the Air, this is a regression over even 26.0.1. Runs worse, more bugs, feels unpolished. But YMMV as they say.

I see over on Reddit lots of users reporting this RC is a dumpster fire too. Glad it’s not just a few of us. Apple has to do a new build before public release.
 
Last edited:
I did Apple Devices shift-click update of the IPSW, it appeared to run and process the update for about 7 or 8 minutes with progress bars on both my monitor and my phone screen, but before it was complete I received a long error message (which could not be photographed due to iphone being inoperable) and progress was halted with the progress bar stuck about 75% of the way complete. Doing a force restart of the phone only puts me in recovery mode. It may have ruined my existing installation of iOS which would result in the need for a full restore and/or the loss of important data. This is an update that should be stayed far away from, it seems it is nothing but trouble
I’ve had issues with IPSW update using my Mac before with my iPhone getting stuck in data recovery mode. Once it’s finished though the data is fully intact. This is the reason I only do OTAs these days.

Now if you’re using a genuine cable to update then it could be something else that terminated the connection before the update is finished. Another possibility could be a corrupted config which I always suspected in your case.

Now for some reason you’re obsessed with that stupid Apple Devices app but you should’ve at least made an encrypted backup before you updated. Hopefully, now you can start from scratch and your issues will go away. If you’d been cautious enough to make an encrypted or iCloud backup, you could restore using either of those and get most, if not all, of your data back and still be able to resolve some of your persistent issues.
 
I’ve had issues with IPSW update using my Mac before with my iPhone getting stuck in data recovery mode. Once it’s finished though the data is fully intact. This is the reason I only do OTAs these days.

Now if you’re using a genuine cable to update then it could be something else that terminated the connection before the update is finished. Another possibility could be a corrupted config which I always suspected in your case.

Now for some reason you’re obsessed with that stupid Apple Devices app but you should’ve at least made an encrypted backup before you updated. Hopefully, now you can start from scratch and your issues will go away. If you’d been cautious enough to make an encrypted or iCloud backup, you could restore using either of those and get most, if not all, of your data back and still be able to resolve some of your persistent issues.
Yes, I always complete an encrypted backup and this will save most, however not all of my data. There will be considerable time and effort required in restoring and setting up again and so I still consider this a major, major issue. The update process should NEVER fail once it is initiated.


I use an OEM Apple lightning to USB-C cable (came out of one of the iPhone boxes) which is dedicated only for use with PC for Apple Devices device management. I also do not pick up or touch the iPhone/cable during any procedure.


Apple Devices is the current software that Apple developed and provides for such purposes however it is unstable and unpredictable. What procedure works fine one day may not work well the next. I use it because this is what Apple officially suggests and provides in 2025 for this exact purpose
 
  • Haha
Reactions: Newton1701
Interesting to read so many different opinions. So far for me on the Air, this is a regression over even 26.0.1. Runs worse, more bugs, feels unpolished. But YMMV as they say.

I see over on Reddit lots of users reporting this RC is a dumpster fire too. Glad it’s not just a few of us. Apple has to do a new build before public release.
As always, and you know it as a member of this forum, let it settle for a moment. Charge it, leave it rest a bit, probably do a restart and judge about the update 1-2 days later.
 
  • Like
Reactions: Maloney~888
Yes, I always complete an encrypted backup and this will save most, however not all of my data. There will be considerable time and effort required in restoring and setting up again and so I still consider this a major, major issue. The update process should NEVER fail once it is initiated.
If you have an iCloud backup I’d suggest going that route instead of encrypted. Less chance of ending up with your old corrupted config.
Encrypted backup saves all your data but your phone may not be exactly like before and you might need to login to some apps, especially ones secured with Face ID.
It is sophisticated software and it’s not perfect. How many times have you actually had a failed install? And I could actually argue it’s a Windows problem and not Apple’s as well. We can’t be certain why the connection got terminated until we go through the logs.

I’m not going to bother getting into a debate about Apple Devices for many reasons. But if you can afford to set it up as new and live with the data you can’t recover, you might as well do yourself a favor and do that. Might save you a lot of time and anguish in the long run.
 
I did Apple Devices shift-click update of the IPSW, it appeared to run and process the update for about 7 or 8 minutes with progress bars on both my monitor and my phone screen, but before it was complete I received a long error message (which could not be photographed due to iphone being inoperable) and progress was halted with the progress bar stuck about 75% of the way complete. Doing a force restart of the phone only puts me in recovery mode. It may have ruined my existing installation of iOS which would result in the need for a full restore and/or the loss of important data. This is an update that should be stayed far away from, it seems it is nothing but trouble
Same as @Artemiz this too happened to me on my MBA when updating from 18.6.2 to 26.0.0 RC, even worse that I had no backup - what I did was unplug the phone, reboot my MBA, then restart the process and it eventually went through no data loss. Good luck

Fwiw, updates on my PC to 26.0.1 and 26.1 RC via iTunes and both were fine.
 
Interesting to read so many different opinions. So far for me on the Air, this is a regression over even 26.0.1. Runs worse, more bugs, feels unpolished. But YMMV as they say.

I see over on Reddit lots of users reporting this RC is a dumpster fire too. Glad it’s not just a few of us. Apple has to do a new build before public release.
Definitely YMMV as on my Air it’s great. B4 was already running pretty smooth and this is an improvement over that two hours post-update. I updated via IPSW this time rather than OTA. No stuttering at all on Home Screen swiping which was still an occasional problem on B4.
 
  • Like
Reactions: NBKindaGirl
Still getting massive stutters moving between pages on the springboard. Animations throughout seem to be a bit quicker though so that helps ever so slightly.

17 Pro
 
I did Apple Devices shift-click update of the IPSW, it appeared to run and process the update for about 7 or 8 minutes with progress bars on both my monitor and my phone screen, but before it was complete I received a long error message (which could not be photographed due to iphone being inoperable) and progress was halted with the progress bar stuck about 75% of the way complete. Doing a force restart of the phone only puts me in recovery mode. It may have ruined my existing installation of iOS which would result in the need for a full restore and/or the loss of important data. This is an update that should be stayed far away from, it seems it is nothing but trouble
You couldn’t take a picture with your iPhone, but don’t you know how to take a screenshot with your computer? I can find you some support articles if you’d like.
 
  • Like
Reactions: NBKindaGirl
Updated to RC on an 13 Pro.

Apart from some unfixed bugs like inability to create stacked widgets in the Today View & stutters when swiping from Today View to Homescreen (specifically), the os itself runs much smoother and fluid compared to 26.0.1. I finally don’t feel the need to upgrade my device this year (but perhaps a battery change).

Can’t really speak on battery life itself since I’m at around 81% health and it’s only been a few hours.
 
keyboard still bugged.

Stuttering galore swiping through Home Screen pages. Lol and why did the keyboard just capitalise “Home Screen” 😂

What a joke.
 
  • Haha
Reactions: NBKindaGirl
keyboard still bugged.

Stuttering galore swiping through Home Screen pages. Lol and why did the keyboard just capitalise “Home Screen” 😂

What a joke.
Because of this👇🏻
 

Attachments

  • IMG_0739.jpeg
    IMG_0739.jpeg
    119.6 KB · Views: 48
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.