Apple Officially Acknowledges 1970 Date Bug That Can Brick Your iPhone, Promises Fix [Video]

Apple Officially Acknowledges 1970 Date Bug That Can Brick Your iPhone, Promises Fix [Video]

Posted by · 10416 views · Translate

Apple has officially acknowledged the 1970 date bug that we demonstrated last week and promised a software update to fix it.

Manually changing the date to May 1970 or earlier can prevent your iOS device from turning on after a restart.

An upcoming software update will prevent this issue from affecting iOS devices. If you have this issue, contact Apple Support.

Click here or take a look at the video below to learn more about the bug and how to fix it.

Read More

Big daddy - February 15, 2016 at 6:43pm
Who really f with the dates anyway? And why would anyone back date to 1970? I don't think it's a big deal.
sandeewhispers - February 17, 2016 at 12:42pm
I'm actually surprised this is the only comment like this. That was my thought as well. LOL!
SGreene - February 20, 2016 at 1:36am
Good question, except it has happened to me twice without my touching the date. The first time It was accompanied by the phone getting extremely hot. I would change to the correct date and soon again it would switch back. Interestingly the date displayed was correct but I noticed because my emails and imessage started showing strange dates sent and received. After it ran out of battery it showed stuck on apple a few times and then would not come back on at all. I tried to tell Apple and they gave me the impression they didn't quite believe me. The second time it happened was in the apple store as they were replacing the phone under warranty and when the backup was restored onto the new phone date showed 1/1/70. The genius took that phone and gave me another new one- said they'd never seen it before. That was over a year ago.
Andy - February 15, 2016 at 4:15pm
Yep for people who know how open iphone whitout damaging home button is easy to fix it. But if you dont openet iphone yet you can easy damage you home bitton and in future get erro 53 becouse you never get your touch id to original state.
Huracandriver82 - February 15, 2016 at 3:18pm
Never had this many bugs or patch fixes when Jobs here.
6 More Comments