iPhone's date to January 1, 1970 will stuck your 64bit-phone at apple logo - GSM-Forum

***mihut*** · 02-14-2016, 15:54

A number of those individuals who fell foul of the mysterious date issue were under the impression that a simple DFU mode restore via iTunes would rectify the issue. The device can be placed into DFU mode, and subsequently restored via iTunes, but even then it simply gets stuck on the Apple logo boot-up screen, and refuses to go past that. Interestingly, this bug seems to be haunting iOS devices with a 64-bit CPUs only, so in essence, any iPhone, iPad, or iPod touch device with the A7, A8, A8X, A9, or A9X chipset is prone to being permanently bricked. More so, it does not matter what version of iOS you’re running either.

See Video:

There are a number of theories behind why this is actually an issue. The popular consensus appears to be that, setting the time and date to January 1st, 1970 causes the internal time clock to be less than zero, and therefore confuses the device forcing it to freak out. The bottom line is that programming and handling date and times is incredibly complex, and we can best speculate for now.

You’d expect Apple to get it right and not put our hard-earned money at risk with such a ridiculous bug that can be exploited for any ill-intentions by anyone. For now, we also expect this to be fixed sooner rather than later with Apple rolling out a quick software update fix to this huge flaw in the iOS code.

02-14-2016, 15:54	#1 (permalink)
*mihut* Super Moderator Join Date: Dec 1999 Location: In EveryOne's Heart Posts: 8,275 Member: 824 Status: Offline Thanks Meter: 25,151	iPhone's date to January 1, 1970 will stuck your 64bit-phone at apple logo A number of those individuals who fell foul of the mysterious date issue were under the impression that a simple DFU mode restore via iTunes would rectify the issue. The device can be placed into DFU mode, and subsequently restored via iTunes, but even then it simply gets stuck on the Apple logo boot-up screen, and refuses to go past that. Interestingly, this bug seems to be haunting iOS devices with a 64-bit CPUs only, so in essence, any iPhone, iPad, or iPod touch device with the A7, A8, A8X, A9, or A9X chipset is prone to being permanently bricked. More so, it does not matter what version of iOS you’re running either. See Video: There are a number of theories behind why this is actually an issue. The popular consensus appears to be that, setting the time and date to January 1st, 1970 causes the internal time clock to be less than zero, and therefore confuses the device forcing it to freak out. The bottom line is that programming and handling date and times is incredibly complex, and we can best speculate for now. You’d expect Apple to get it right and not put our hard-earned money at risk with such a ridiculous bug that can be exploited for any ill-intentions by anyone. For now, we also expect this to be fixed sooner rather than later with Apple rolling out a quick software update fix to this huge flaw in the iOS code.