It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Some features of ATS will be disabled while you continue to use an ad-blocker.
Your iPhone really hates the date January 1, 1970. It hates it so much that it will permanently crash if you change your iPhone's time settings to that date.
January 1, 1970 is the earliest date you can set your iPhone to. If you turn your date and time settings to manual (please don't do this), and scroll the calendar back as far as you can go (seriously, don't do this), you can only go as far back as January 1, 1970.
Now, why would scrolling all the way back to January 1, 1970 (00:00:00 in Unix time) turn your iPhone into a brick? If your time zone isn't GMT, your iPhone might think you're in a time before January 1, 1970 -- or before zero. Though Unix time can be negative, it's possible that something about that makes your iPhone go haywire.
This bug affects any iOS device that uses a 64-bit processor and is running iOS 8 or newer, including iPhones, iPads, and iPod touches. For those unsure, 64 bit processors are the A7, A8, A8X, A9, and A9X (iPhone 5s or later, for instance). If you use a 32 bit device, you’re in the clear.
A Reddit thread offers a handful of possible causes of the issue. The most reasonable appears to be that it all comes down to time zones and that setting the date to January 1st, 1970 causes the internal clock to be set to less than zero, which confuses the device and crashes it.
Another user claims that he inadvertently suffered this bug when he changed the time zone on his iPhone from Bejing back to New York, experiencing the same issue.
One Twitter user says that the device could come back on after 5 hours, while another notes that changing the SIM card could fix the issue, as well.
originally posted by: James99
If you let the phone run completely dead on the battery and then recharge it it'll bring it back to life