iOS 8/9 will get bricked if you set your date back too far. If someone could explain how exactly this happens, I would love to know.

closed as too broad by fsb, Ɱark Ƭ, Allan, IconDaemon, Monomeeth Jul 14 '17 at 22:32

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 2
    Why would you ever want or need to set the current date to 1970? – Solar Mike Jul 14 '17 at 15:22

In some time zones, setting the date to 1 Jan 1970 will set the internal clock to a number less than zero, as the time is stored in GMT (as the number of seconds since midnight on that date) and then the offset is applied before display. In other time zones, setting the clock will result in a positive time value. Best guess is that this is triggered by having the time value less than zero.

This behaviour can be replicated by creating an NPT server on a network and injecting it to multiples devices. If the time returned to the device is negative, the device will crash.

  • 1
    That sounds a very plausible explanation. Still I don't see any good reason why someone would want to do that - unless they are hitchhiking in time... – Solar Mike Jul 14 '17 at 16:14
  • 1
    No idea why, but just Google 'iOS 9 1970 bug' for a slew of related results. – Tetsujin Jul 14 '17 at 19:20
  • I fell for this because someone on reddit (never trust the internet) said that resetting it back to 1970 would give a classic macintosh theme. i.imgur.com/mnfsKzF.png – noodles Jul 14 '17 at 19:27

Not the answer you're looking for? Browse other questions tagged .