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

Ternary

macrumors regular
Original poster
Jul 4, 2015
168
162
Curious about this, since starting with iOS 9.3, you can't set the system time earlier than 1/1/2001 anymore.

Anyone daring enough to try?
 
You mean if you are hit by the bug with a phone that isn't working because of it...what happens if/when you upgrade to iOS 9.3?
 
You mean if you are hit by the bug with a phone that isn't working because of it...what happens if/when you upgrade to iOS 9.3?
I mean if you set your system time to January 1, 1970 on iOS 9.2.1 and then start the iOS 9.3 update OTA.
 
Pretty sure 9.2.1 re-release fixed this already. I believe you just had to DFU restore to that version and it fixed the issue even if they device didn't boot beforehand.
 
Depends on how updates occur. Is it booting the full kernel and starting the write process? Or is it only booting something temporary to actually do the install? I'd bet that you'd get stuck and have to restore the phone with iTunes.
 
Let me tell you what happens. A customer changed the date on an iPhone to 1/1/1970 and rebooted the phone which threw it into the booting loop. We were able to put the phone into recovery mode, connect it in to iTunes and update its software to 9.3. The phone booted up normally with its date set to 1/1/1970 and everything was back to normal.
 
  • Like
Reactions: Ternary
Let me tell you what happens. A customer changed the date on an iPhone to 1/1/1970 and rebooted the phone which threw it into the booting loop. We were able to put the phone into recovery mode, connect it in to iTunes and update its software to 9.3. The phone booted up normally with its date set to 1/1/1970 and everything was back to normal.
I was thinking more along the lines of an OTA update. What would happen if you changed the date to 1/1/1970 on a phone running 9.2.1 and then proceeded to start the 9.3 OTA update? Would it not work, since the wrong time prevents proper communication with the server for verifying? Or would it start and fail? Or maybe just go normal?
 
I was thinking more along the lines of an OTA update. What would happen if you changed the date to 1/1/1970 on a phone running 9.2.1 and then proceeded to start the 9.3 OTA update? Would it not work, since the wrong time prevents proper communication with the server for verifying? Or would it start and fail? Or maybe just go normal?

Can't help you with that.
 
Let me tell you what happens. A customer changed the date on an iPhone to 1/1/1970 and rebooted the phone which threw it into the booting loop. We were able to put the phone into recovery mode, connect it in to iTunes and update its software to 9.3. The phone booted up normally with its date set to 1/1/1970 and everything was back to normal.
Interesting. I thought that part of the "fix" for this was that it was more of a workaround in the sense that dates simply couldn't be set that far back (basically to where they would cause an issue).
 
Interesting. I thought that part of the "fix" for this was that it was more of a workaround in the sense that dates simply couldn't be set that far back (basically to where they would cause an issue).

I don't know how that "fix" would work with calendar events. If if Ios restricts you from setting date as far back, you could receive a calendar event of that date/time, with an alert. Wonder what happens then.
 
I don't know how that "fix" would work with calendar events. If if Ios restricts you from setting date as far back, you could receive a calendar event of that date/time, with an alert. Wonder what happens then.
That wouldn't set the system time to that date though.
 
That wouldn't set the system time to that date though.

I know. But the bug may trigger some underlying problem with events on that date as well. Since they haven't published the underlying bug within Linux itself (at least I don't know in detail what it is), it's possible that an event like this may also trigger it.
 
I know. But the bug may trigger some underlying problem with events on that date as well. Since they haven't published the underlying bug within Linux itself (at least I don't know in detail what it is), it's possible that an event like this may also trigger it.
Possible perhaps, although in this case it seems that the bug was with system time and in the context of the boot process.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.