Yes, and always OTA from the time I started to use iphone, which never has these issues
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.
Roll back to 10.3.3
- Thread starter twdawson
- Start date
- Sort by reaction score
Yes, and always OTA from the time I started to use iphone, which never has these issues
That's not what's being reported: other devices are showing up as signed as well. Edit: the posts I saw were from a single person, so I'm going to backtrack on that until there's more. I may need to try going back to 10.3.3 on my iPhone 7 later today so I may find out personally.
[doublepost=1507378374][/doublepost]
That is supposed to work, but when I restored two different devices last week 'update' didn't work, I had to use 'restore.'
Last edited:
I just did some searching and I'm backtracking on that, the reports are from a single user and they might be mistaken.
You should be more worried about the unknown security holes in your devices as they might already be being exploited without your knowledge. I recommend you turn off all your Apple devices to be safe.
I think it's time you do an install through itunes. It's fact that OTA updating is more prone to issues as well as the iTunes software has better error checking. I think an itunes install whenever a new OS is released makes a big difference for the rest of the year. If my iPhone is running fine and yours isn't, it's because of some software install issue.
Yes. One way you can do that is by holding the key while pressing update in iTunes and you can choose which firmware file to install. Then you don't have to restore. But you still have to reset the device from Settings after.
Ah, I see. Will be more playing around tonight. Turns out the problem may have originated in 11.0.1 - will do some more testing tonight (on 10.3.3 at the moment and everything's working as it should).
You don't have a 6s then?
I just did another rollback to 10.3.3 this morning (been trying to rid my device of any pesky data remnants) - this last wipe seemed to take.
I had to upgrade to the 11.1 beta in order to not get an error 65 when I was doing it previously though (wouldn't let me downgrade from 11.0.2).
Just upgraded to 11.0.1 from 10.3.3, now to test if this latest update has the problem with my car connection or not.
Oh, btw - proof that Apple is playing games with their iCloud backups - they wouldn't allow me to backup to iCloud once I had rolled back to 10.3.3.
Edit: Deleted the last part - for some reason I thought iTunes could do iCloud backups.
Should be able to - be a nice feature!
Last edited:
I can now confirm that it also won't allow you to on 11.0.1 when you've previously been running 11.0.2.
Edit: Aha! New error message (rather than just failing)
"The last backup could not be completed because iCloud contains a backup from a newer iOS version"
So, at least they're admitting that they're evil now.
Edit2: Staying on 10.3.3 now. The problems I experiences on 11.0.2 started happening on 11.0.1 - so something is changing the configuration after the initial installation. Possibly carrier settings being pushed? No idea - wasn't prompted for any data updates that would have caused the issues to return.
Hopefully they fix the USB and Bluetooth Car issues people are experiencing....
So, not considering new Watch or iPhoneX so long as the problem persists.
(not replacing my car this year).
Last edited:
Probably because you did an iCloud backup on ios11 which made it incompatible with iOS 10.3.3. Delete iCloud backup and start over, it works
That's a political decision, not a technical one. I get not allowing people to restore an iOS 11.x backup onto 10.3.3, but to disable any future backups because you've downgraded?
Your backups are listed - as are the versions of iOS that they were backed up with. The part I'm taking issue with is that none of my iOS 11.0.1 backups were visible after updating to 11.0.2.
It's a one-way street. They're enforcing their no rollbacks policy everywhere that they can. (regardless of whether its a disservice to their customers or not).
Broken, but controlled.
My point is, control the rollback. Build a policy around it - have a mechanism in iOS (or iTunes) to support it. This "no rollbacks allowed" policy will only reduce the number of people willing to update. When basic functionality is broken, how long should you be expected to wait?
It's not realistic to expect customers to wait 6-12 months for functionality that they had previously (and could have been broken by a minor update).
There needs to be a balance between the risks and the benefits. Doing otherwise is irresponsible.
And, yes, I get it. I managed engineering teams. Many, many, software releases. We always had a rollback strategy....and it was always tested before implementation.
If we're ever going to get the vast majority of people to upgrade to the current release, we need to mitigate the risk.
I really believe this has been a thing with iCloud backups since they started, isn't it?
Ok, I'll grant you that, but what about the older backups? It's pretty convenient that when you roll your device back, the older iCloud backups are no longer available. Provided you have space, why shouldn't they be?