Newly-revealed date glitch may render some iOS devices unusable
Though people have to go out of their way to trigger it, a time-related glitch discovered in iOS 8 and 9 will let users potentially "brick" many Apple devices, rendering them non-functional.
Users must go into the Date & Time menu under Settings, disable the "Set Automatically" option, and then manually roll the date back to Jan. 1, 1970, according to a YouTube video published on Thursday. This requires jumping in and out of the menu, since the date won't initially rewind that far.
Once the new date is set, rebooting a device may leave it stuck at the Apple logo, and even the full range of restore options may not work. In that circumstance there's likely no option but to get a Genius Bar repair or a replacement device (possibly free under warranty), though some people have reported that a device might spontaneously recover several hours later -- albeit with extremely slow performance. That may allow users to change date settings and recover.
A Reddit thread suggests that the bug may be related to timezones, since rolling the date back as far as it will go could be setting the clock to a value less than zero. One person said they only bricked their phone after changing timezones from Beijing to New York.
In addition to requiring iOS 8, the bug is also limited to Apple devices with 64-bit processors, from the iPhone 5s onwards. Older products like the iPhone 5 or iPad 2 should be immune.
Users must go into the Date & Time menu under Settings, disable the "Set Automatically" option, and then manually roll the date back to Jan. 1, 1970, according to a YouTube video published on Thursday. This requires jumping in and out of the menu, since the date won't initially rewind that far.
Once the new date is set, rebooting a device may leave it stuck at the Apple logo, and even the full range of restore options may not work. In that circumstance there's likely no option but to get a Genius Bar repair or a replacement device (possibly free under warranty), though some people have reported that a device might spontaneously recover several hours later -- albeit with extremely slow performance. That may allow users to change date settings and recover.
A Reddit thread suggests that the bug may be related to timezones, since rolling the date back as far as it will go could be setting the clock to a value less than zero. One person said they only bricked their phone after changing timezones from Beijing to New York.
In addition to requiring iOS 8, the bug is also limited to Apple devices with 64-bit processors, from the iPhone 5s onwards. Older products like the iPhone 5 or iPad 2 should be immune.
Comments
European Union probe into whether it is possible to entirely prevent iOS to be set back to 1970 to commence; initiative underway to erase 1970 from the space-time continuum, sources say.
Shares tumble in the wake of Dategate. Tim Cook deletes blurry photo of his fishing trip. Apple iPhone guidance now in question.
More at 11.
Sorry, with Apple Configurator 2 you can recover it for sure.
The problem is, this really does have to be fixed. Some moron will see your phone unlocked and "prank" you. It's like the olden days when Hey Siri could be set to run actively when your phone was docked to power, so guys would come up and say "Hey Siri, from now on call me Butthead."
queue the Seattle law firm...
I guess I need to warn my kids not to let anyone play with the calendar, I can see kids pranking each other with this gem. I know my kids friends you to keep trying to unlock each other phones until you could not get into the phone for an hour or so.
Some systems that work with future dates could run into the problem even sooner than 2038.
I have hundreds of files on my Mac right now that somehow have the date of Feb 5, 2040. You can fix in terminal but it is a real pain.
That sounds like bricking to me.
And you can get a brand new one at any Apple Store for what, $129?
But only if you bought AppleCare+ when your smashed phone was new.