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

Apple Releases New Version of iOS 9.3 for Older Devices Affected by Activation Lock Bug

I don't understand ...

I already updated to 9.3 successfully on my iPhone 5s, and it correctly shows that I'm running it in the About screen. Yet, it's still showing me that I have an update to iOS 9.3 in the Software Update screen!?

If this is only fixing an installation bug, then why is it asking to install on my 5s AGAIN?

My iPad 3, on the other hand, currently shows that I am running iOS 9.3, and it is the current software version, no new updates.

Very odd.
 
  • Like
Reactions: Benjamin Frost
That is true, if for some reason I couldn't access 1Password on iOS, I do have the Mac app too so I'd be fine.
 
gpsouza said:
How is forgetting your password a "bug"? Only if in your brain i guess...
Click to expand...
If that's the only thing this update addresses, yes, it was a bug(s). That bug could be classified as a security issue, as well. @bsolar explained it well (#176) :

The question is not "why wouldn't I?", the question is "why are old login informations still relevant?". The old login informations might have been changed because they got somehow compromised: they should not be valid anymore anywhere, but actually they are.

The problem is not only that they need to be used to unlock the device (which could be counter-intuitive and potentially an hassle), the problem is that they can be used to do such a thing at all (which could be plain simply a security risk).
Click to expand...
https://forums.macrumors.com/thread...lder-ios-devices.1963446/page-8#post-22717394
 
Mac 128 said:
I don't understand ...

I already updated to 9.3 successfully on my iPhone 5s, and it correctly shows that I'm running it in the About screen. Yet, it's still showing me that I have an update to iOS 9.3 in the Software Update screen!?

If this is only fixing an installation bug, then why is it asking to install on my 5s AGAIN?

My iPad 3, on the other hand, currently shows that I am running iOS 9.3, and it is the current software version, no new updates.

Very odd.
Click to expand...

Well, my iPhone 5S is also showing 9.3 as an available update, even if it has been updated to 9.3 when it was released. My 5th Gen iPod Touch says it's up to date with 9.3. And I don't know about my iPad 2, I'll check it later.

The difference is... The 1st one was that usual OTA size (about 220 MB, if remember correctly..). This one is a full 1.4 GB download. And yes, it's OTA, since I'm at work and my iDevices only sync to the iTunes in my Early 2011 13" MBP at home.

I decided to take the risk again and check what happens now. I'll let you know when it's finished, although it might take a while. My work only offers 2 mbps bandwidth per WiFi connection...

Oh, and this is my very first post here. I've been a MacRumors reader since 2011, I think.
 
Mac 128 said:
I don't understand ...

I already updated to 9.3 successfully on my iPhone 5s, and it correctly shows that I'm running it in the About screen. Yet, it's still showing me that I have an update to iOS 9.3 in the Software Update screen!?

If this is only fixing an installation bug, then why is it asking to install on my 5s AGAIN?

My iPad 3, on the other hand, currently shows that I am running iOS 9.3, and it is the current software version, no new updates.

Very odd.
Click to expand...

Same on my Air, had the activation issue but luckily it got solved by plugging in to iTunes. I was told by the Apple support a few days ago that 'You shouldn't have to update'... Just DMed them and waiting for a response. On vacation with a unstable connection so I'd rather not update until I get green light by them...
 
lkrupp said:
Reading comprehension seems to be a serious issue for MacRumors commenters, as well as remembering the past.
Click to expand...

If the past would stop repeating itself things would be better. :) But yes, reading comprehension...it's lacking all over the place.
 
SMIDG3T said:
It's probably already mentioned but why not use a password manager? I use 1Password and I actually don't know ANY of my passwords off-by-heart so I can't accidentally give them out. I have a different password for every site I use. Some people might think that's a bit extreme but it's not an issue for me.
Click to expand...
Started off with 1 password, but didn't like it. I also have tons of passwords.

Between autofill and my brain, we get it together:)
[doublepost=1459189921][/doublepost]
Benjamin Frost said:
The major bug was known to Apple two days ago; they should have fixed it within 24 hours.

Sick and tired of Cook's lousy Apple quality control. Customer satisfaction, my arse.
Click to expand...

To fix a software bug, it requires analyzing.
Then find out what to do AND whether that fix will impact something else.

I am pretty sure it's more important to fix a bug, than doing it within 24 hours.
 
  • Like
Reactions: 69Mustang and macintoshmac
SMIDG3T said:
It's probably already mentioned but why not use a password manager? I use 1Password and I actually don't know ANY of my passwords off-by-heart so I can't accidentally give them out. I have a different password for every site I use. Some people might think that's a bit extreme but it's not an issue for me.
Click to expand...
tx4app said:
It might also be worth emphasizing to obtain a password-manager which not only runs on the iPhone/iPad/etc. (iOS) device, but also has a version that runs on their computer (OS X, Windows) AND which syncs the passwords between the different devices. Some people complained that they couldn't access their password manager, because it's an app on the unavailable iOS device. Well, if you make sure you get a product, as just previously mentioned, that also runs on your computer, then you'll have all your passwords there too (assuming you synchronize/update them regularly).
Click to expand...

This bug had nothing to do with remembering id/pw per se. The bug made the update ask for the original id/pw used to set up the phone. In some cases the current user wouldn't have that info (second hand phone, for instance). Also someone could have changed a compromised id/pw. There's no justifiable reason for an update to ignore the current id/pw and request the original.
Password managers wouldn't have helped in that instance, especially if there was an issue with the old info. You'd want that nowhere near your device.
 
  • Like
Reactions: chrismac2
I have a 9.3 update on my iPad 2 but never did update. It's been there for a while!

How do I know if its the one to fix the problem? Says it's 197MB. :confused:

Maybe I should wait a few days.
 
SMIDG3T said:
I doubt the Safari issue will be fixed in this build. It was only known to Apple today. Anyway, I'm on iOS 9.3 and I cannot update to this new build. (I've also had no issues regarding this Safari issue.)
Click to expand...

Definitely known before today based on existing Apple support forums, Twitter @applesupport, and my personal call to Apple on Friday -- they already had issue confirmed and were not even creating new tickets for it.

Hopefully they can turn around a fix very soon because none of the workarounds have been effective for me. Resorting to using Puffin.
 
69Mustang said:
This bug had nothing to do with remembering id/pw per se. The bug made the update ask for the original id/pw used to set up the phone. In some cases the current user wouldn't have that info (second hand phone, for instance). Also someone could have changed a compromised id/pw. There's no justifiable reason for an update to ignore the current id/pw and request the original.
Password managers wouldn't have helped in that instance, especially if there was an issue with the old info. You'd want that nowhere near your device.
Click to expand...


I agree with you. I comprehended the problem as first described. I understand entirely that the source of the 9.3 activation failure revolved around knowing the original id and password associated with the older devices. I'm only posting on the tangential topic of password management, and that there are very useful tools out there. And, on another tangent, out of convention I commonly store at least the previous (if not ALL previous) old passwords for some accounts, particularly for systems which don't allow you to re-use an old password. Again, I know this wouldn't have rescued anyone who purchased a second-hand/preowned device, but just adding another helpful tip for other scenarios.
 
gpsouza said:
How is forgetting your password a "bug"? Only if in your brain i guess...
Click to expand...
As I understand it - and I may be wrong - the bug is that it asked you to remember the first password used on the device and not the current password. For example, the iPad 2 came in March 2011. An early iPad 2 adopter could hace set a password the first time he used the iPAD changed the original password 6 months later and kept using that same new password for the next 4 and a half years. Is it reasonable to expect that person to remember that first password that he only used for 6 months 4 and a half years ago?
 
MacRumors said:



Just a few days after releasing the iOS 9.3 update, Apple stopped offering it to a selection of older devices including the iPad Air and earlier and the iPhone 5s and earlier due to an activation issue. When the update was pulled, Apple promised to release a new version of iOS 9.3 shortly.

Apple today made good on that promise and has released a new version of iOS 9.3, build 13E237, which is now available for all iOS 9 users with older devices as an over-the-air update or through iTunes. Customers with older devices who had not yet updated to iOS 9.3 will be able to do so now.

activateiphoneerror.jpg

With the first version of iOS 9.3, people with older iOS devices were required to input the Apple ID and password used when originally setting up the device. If the account information could not be recalled, the activation process could stall, rendering the devices inaccessible. To prevent users from installing iOS 9.3, Apple stopped signing the update for several older devices.

Following the release of the new build, Apple has resumed signing iOS 9.3 and the update now asks for current the Apple ID and password linked to the device instead of the original information.

On Thursday night, Apple issued an updated version of iOS 9.3 specifically for the GSM iPad 2, which was afflicted with a separate activation bug that prevented the device from communicating with Apple's activation servers.

Article Link: Apple Releases New Version of iOS 9.3 for Older Devices Affected by Activation Lock Bug
Click to expand...
 
ielessar said:
I hope the Safari freezing bug is fixed. Many people are facing this issue.
Click to expand...

Yes, this! I can barely do anything with my 6s in its current state because of this Safari bug. I can not open any links I get via e-mail, or even from Facebook or other 3rd party apps.

Anyone know if this update fixes that issue too?
 
This update IS STILL NOT WORKING for my ipad 2 GSM. Tried downloading and updating my iPad over 5 times through iTunes. I also unplugged and restarted iTunes every time. Has anyone got this to work on their iPad 2 GSM??
 
parisi2274 said:
Yes, this! I can barely do anything with my 6s in its current state because of this Safari bug. I can not open any links I get via e-mail, or even from Facebook or other 3rd party apps.

Anyone know if this update fixes that issue too?
Click to expand...


No, but a quick workaround would be turning off javascript in Safari settings.

Settings > Safari > Advanced > Javascript - Off

This is a temporary fix.
 
Startech2020 said:
This update IS STILL NOT WORKING for my ipad 2 GSM. Tried downloading and updating my iPad over 5 times through iTunes. I also unplugged and restarted iTunes every time. Has anyone got this to work on their iPad 2 GSM??
Click to expand...

Before Apple pulled the original 9.3, I did an OTA update to my iPad 2. I had the "can't contact servers and can't activate" error.. Tried again 5 or 6 times with my iPad 2 connected to my home WiFi with no success. 2 days later, restored it via iTunes, when Apple had probably replaced the 9.3 update for iPad 2. Nothing. Same error.

Then I turned off the WiFi and tried to do the activation thing via 3G. It finally worked.

Gotta wait until I get home to see if 9.3 is available again for iPad 2.
 
Last edited:
vlad_djkax said:
Before Apple pulled the original 9.3, I did an OTA update to my iPad 2. I had the "can't contact servers and can't activate" error.. Tried again 5 or 6 times with my iPad 2 connected to my home WiFi with no success. 2 days later, restored it via iTunes 2, when Apple had probably replaced the 9.3 update for iPad 2. Nothing. Same error.

Then I turned off the WiFi and tried to do the activation thing via 3G. It finally worked.

Gotta wait until I get home to see if 9.3 is available again for iPad 2.
Click to expand...


I had the cellular turned off on my Ipad. Update is still not working. Thanks for the info though.
 
Mac 128 said:
I don't understand ...

I already updated to 9.3 successfully on my iPhone 5s, and it correctly shows that I'm running it in the About screen. Yet, it's still showing me that I have an update to iOS 9.3 in the Software Update screen!?

If this is only fixing an installation bug, then why is it asking to install on my 5s AGAIN?

My iPad 3, on the other hand, currently shows that I am running iOS 9.3, and it is the current software version, no new updates.

Very odd.
Click to expand...
Because the build number is higher...xxx233 to xxx237
 
gpsouza said:
How is forgetting your password a "bug"? Only if in your brain i guess...
Click to expand...

How about this ... you had to change your password because your old one was compromised. The person(s) you changed your password to prevent accessing your device, learns of this exploit, and upgrades your iPad, accesses it with your old compromised password, and then has full access to your iPad. That's pretty much a bug.

dmnc said:
Because the build number is higher...xxx233 to xxx237
Click to expand...

Oh I understand that, but if I don't need the new build, why wouldn't there be a software check that determines I don't need the new build? Seems pointless. Now, I'm going to have to upgrade again, despite this doing nothing more for me, or face those annoying reminders I have to constantly dismiss.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back