iOS update 9.2.1 to 9.2.1

[cynics]

Anyone else getting these?

I updated my iPhone from iOS 9.2.1 to 9.2.1 thinking it was 9.3 because I didn't read the update only to realize it didn't actually update anything. Now its asking to update my iPad Air 2....



Just another bug?

 

[lagwagon]

Anyone else getting these?

I updated my iPhone from iOS 9.2.1 to 9.2.1 thinking it was 9.3 because I didn't read the update only to realize it didn't actually update anything. Now its asking to update my iPad Air 2....

View attachment 617329

Just another bug?

They re-released 9.2.1 with a fix to "error 53" and I believe it also fixes the Jan 1st, 1970 bug as well. Only available via iTunes though and not OTA.

 

[C DM]

They re-released 9.2.1 with a fix to "error 53" and I believe it also fixes the Jan 1st, 1970 bug as well. Only available via iTunes though and not OTA.

I can't say I've heard that it fixes the date issue (and I'd imagine they would bump up the version if it had something like that or anything else outside of a removed factory check that was responsible for "error 53" causing devices to no longer work).

 

[lagwagon]

I can't say I've heard that it fixes the date issue (and I'd imagine they would bump up the version if it had something like that or anything else outside of a removed factory check that was responsible for "error 53" causing devices to no longer work).

They didn't bump the version number but the build did go from ending with 15d to 20d.

There was a video by EverythingApplePro on YouTube that for him he was able to get past the boot loop without issue with the 9.2.1 (version 2) re-release.

They also didn't remove the factory check that caused error 53. They just made it so it didn't brick. The new version just disables all Touch ID and anything related to Touch ID. It allows them to use their phone again but they still have to get it properly fixed at an Apple Store to re-enable everything Touch ID.

*EDIT to add video link*

 

[C DM]

They didn't bump the version number but the build did go from ending with 15d to 20d.

There was a video by EverythingApplePro on YouTube that for him he was able to get past the boot loop without issue with the 9.2.1 (version 2) re-release.

They also didn't remove the factory check that caused error 53. They just made it so it didn't brick. The new version just disables all Touch ID and anything related to Touch ID. It allows them to use their phone again but they still have to get it properly fixed at an Apple Store to re-enable everything Touch ID.

You are saying someone that didn't have the "error 53" issue, but just had the issue because of the date change was able to restore using the updated 9.2.1 version (and once restored no longer were abel to reproduce the date issue)?

As fro the factory test, it seems like there was one that would actually disable the device it seems vs. one that simply disables TouchID (which has been around for some time now), and it's the version that disables the whole device that slipped into the original 9.2.1 update and was pulled out of or modified back to the previous one (that simply disables TouchID) in the updated 9.2.1 update.

 

[lagwagon]

You are saying someone that didn't have the "error 53" issue, but just had the issue because of the date change was able to restore using the updated 9.2.1 version (and once restored no longer were abel to reproduce the date issue)?

Edited my post to include the video link that explains the update. (And shows him testing to see if the date bug was fixed by setting the date and rebooting and it successfully rebooting while on Jan 1, 1970 date.)

 

[cynics]

Interesting.

Strange to me that the build number was changed without a revision but nice of Apple to fix those issues so promptly. I'm even more pleased just to find out this isn't another bug.

I imagine iOS 9.3 is just around the corner and Apple wanted to push the Error 53 fix to fix peoples devices that are suffering from that bug. Kind of like a "there if you need it" patch...

 

[lagwagon]

Interesting.

Strange to me that the build number was changed without a revision but nice of Apple to fix those issues so promptly. I'm even more pleased just to find out this isn't another bug.

I imagine iOS 9.3 is just around the corner and Apple wanted to push the Error 53 fix to fix peoples devices that are suffering from that bug. Kind of like a "there if you need it" patch...

No version change (9.2.2) I would assume because the main focus of it was to un-brick devices stuck in "error 53". It wasn't needed for everyone so didn't require a number change and force everyone to update. (Which is why it also isn't available OTA)

9.3 isn't until next month still. (Eddie Cue and Craig Federighi mentioned OS X 10.11.4 releasing next month. 9.3 and 10.11.4 will be released same day as usual.)

 

[C DM]

Edited my post to include the video link that explains the update. (And shows him testing to see if the date bug was fixed by setting the date and rebooting and it successfully rebooting while on Jan 1, 1970 date.)

No version change (9.2.2) I would assume because the main focus of it was to un-brick devices stuck in "error 53". It wasn't needed for everyone so didn't require a number change and force everyone to update. (Which is why it also isn't available OTA)

9.3 isn't until next month still. (Eddie Cue and Craig Federighi mentioned OS X 10.11.4 releasing next month. 9.3 and 10.11.4 will be released same day as usual.)

I can understand no version change to address the "error 53" issue that only happens during an update/restore process, but if the date bug was fixed I can't quite imagine why they wouldn't bump up the version and release it as a regular update as basically anyone and everyone would benefit from having that bug fixed (whether or not they would run into it, intentionally or not).

 

[lagwagon]

I can understand no version change to address the "error 53" issue that only happens during an update/restore process, but if the date bug was fixed I can't quite imagine why they wouldn't bump up the version and release it as a regular update as basically anyone and everyone would benefit from having that bug fixed (whether or not they would run into it, intentionally or not).

Apple made a statement earlier this week that the date fix would be in the next update (most likely meaning 9.3)

They probably just tacked it on to 9.2.1 (version 2) just because they had the fix ready. I have no doubt 9.3 beta 4 will include the same date fix this coming week.

Wether it's right or wrong to not just release it as 9.2.2 and force everyone to update, it's rare enough to not force an upgrade to all when the fix is going to hit everyone soon enough and the main intention of the update was to un-brick "error 53" phones.

 

[C DM]

Apple made a statement earlier this week that the date fix would be in the next update (most likely meaning 9.3)

They probably just tacked it on to 9.2.1 (version 2) just because they had the fix ready. I have no doubt 9.3 beta 4 will include the same date fix this coming week.

Wether it's right or wrong to not just release it as 9.2.2 and force everyone to update, it's rare enough to not force an upgrade to all when the fix is going to hit everyone soon enough and the main intention of the update was to un-brick "error 53" phones.

Strange that they would stick it into the 9.2 branch of code and not just 9.3 unless they were contemplating on pushing out an earlier 9.2.2 update for it for some reason and still included it in the latest re-release of 9.2.1. Also strange that there hasn't been much mention of the fix somewhere here and basically just a YouTube video from a single user.

 

[lagwagon]

Strange that they would stick it into the 9.2 branch of code and not just 9.3 unless they were contemplating on pushing out an earlier 9.2.2 update for it for some reason and still included it in the latest re-release of 9.2.1. Also strange that there hasn't been much mention of the fix somewhere here and basically just a YouTube video from a single user.

Well I don't know for a fact if the new 9.2.1 build also fixes the date issue. I only said "I believe it also fixes" purely based on only what I saw in the video. I also haven't seen much of it mentioned anywhere. Maybe it doesn't include the date fix yet, (I'm not willing to try) which would just further point to not doing it as a 9.2.2 forced to everyone and just a download from iTunes for people stuck with error 53.

Here is the document Apple saying the date bug will be fixed in an upcoming update. https://support.apple.com/en-us/HT205248

 

[C DM]

Well I don't know for a fact if the new 9.2.1 build also fixes the date issue. I only said "I believe it also fixes" purely based on only what I saw in the video. I also haven't seen much of it mentioned anywhere. Maybe it doesn't include the date fix yet, (I'm not willing to try) which would just further point to not doing it as a 9.2.2 forced to everyone and just a download from iTunes for people stuck with error 53.

Here is the document Apple saying the date bug will be fixed in an upcoming update. https://support.apple.com/en-us/HT205248

Right, I recall Apple saying they will address it in an upcoming update (which I read basically as the next update, and in my mind that would be either 9.3 when it's released or possibly something like 9.2.2 if they wanted to release it earlier for some reason, but basically to everyone). Seeing that their support document still mentions that it will be addressed in an upcoming update (rather than saying that the latest version of 9.2.1 update addresses it) I would probably assume that the fix is likely not part of the updated 9.2.1 update after all. Not quite sure what would explain the experience of that YouTube user in particular, but perhaps there's something else in play, like maybe the battery actually running down at some point before the restore which got it back into working order, or something like that.

 

[Paddle1]

This update is not available on iPhone 5s or iPod Touch 6, or available over the air on any device, if it was to fix the date bug, wouldn't it have been more readily available?

 

[lagwagon]

This update is not available on iPhone 5s or iPod Touch 6, or available over the air on any device, if it was to fix the date bug, wouldn't it have been more readily available?

The fix is pretty much 100% only to address "error 53" so that phones bricked by that can update and get past the error. It "is" possible they could have added the fix for the date bug in it. Since they do have a fix ready but said it wasn't going to release until the upcoming update (presumably they meant 9.3) The video linked "claims" to show him setting it to Jan 1, 1970, reboot and it booted up just fine. But the puzzler is no one this site or any other site have confirmed If it's actually true. I'm not willing to test and find out either.

 

[iapplelove]

I passed on the update, really no reason to. 9.3 will come soon enough.

 

[Umbrarian]

I take all the updates, not sure why anyone would not.

 

[lagwagon]

I take all the updates, not sure why anyone would not.

If you're phone or device isn't bricked by "error" 53 you have no reason to update to the newer 9.2.1 build. That's all the update does.

 

[iapplelove]

I take all the updates, not sure why anyone would not.

lol you do realize there is no point updating to this one unless needed right? Why take the chance of updating and having unnecessary issues?

 

[wlossw]

This is a very annoying "feature."

 

[C DM]

This is a very annoying "feature."

Which one?

 

[wlossw]

Which one?

itunes prompting top install 9.2.1 on my phone when I already have it.... IE: not changing the release number.

 

[C DM]

itunes prompting top install 9.2.1 on my phone when I already have it.... IE: not changing the release number.

Well, the build number changed, so that's basically why it's prompting that, but, as mentioned before, it's essentially actually useful for the purposes of those with phones that need to be restored.