Don't set the date on your iPhone (or other 64-bit iDevice) to January 1st, 1970

Welcome to our Community
Wanting to join the rest of our members? Feel free to sign up today.
Sign up

Rafagon

Genius
Gold
Dec 7, 2011
7,566
1,252
113
44
Miami, Florida
#3
The article calls this "an interesting bug"; I'm calling it a feature.

This is a security measure put in place by Apple in case someone maliciously sends your iPhone back in time (specifically to January 1st, 1970). When the phone arrives at that date, people there will be unable to access your bricked device, thus preventing access to information from the future which could have deadly results if used improperly.
 

Napoleon PhoneApart

Moderator
Senior Moderator
Jun 19, 2007
33,438
4,531
113
Upper Marlboro, MD
#4
The article calls this "an interesting bug"; I'm calling it a feature.

This is a security measure put in place by Apple in case someone maliciously sends your iPhone back in time (specifically to January 1st, 1970). When the phone arrives at that date, people there will be unable to access your bricked device, thus preventing access to information from the future which could have deadly results if used improperly.
You and a hundred other people have thought of this.
 

Rafagon

Genius
Gold
Dec 7, 2011
7,566
1,252
113
44
Miami, Florida
#5
If Napoleon and I were not clear and explicit enough, here is the take-away from this thread, according to OSXDaily, in clear and and simple English. I couldn't have worded this better myself.

"Do not try this yourself, you will ruin the iPhone. That can’t be made more clear, if you try this, you will ruin the iPhone. In other words, do not try this yourself with any iPhone that you care about, unless you don’t mind sending it back to Apple for repair. Doing this will destroy the iPhone and make it inoperable. That means you won’t be able to use the iPhone at all, it will be broken. So we repeat, again, do not try this yourself. Do not try this at home. Do not try this with your iPhone. Do not try this with your friends or anyone elses iPhone. And most importantly, don’t be fooled into trying this by someone else, as there are several ridiculous pranks in the form of various claims circulating on the internet as to what happens if you set the iPhone date far into the past – don’t do it, it breaks the iPhone. This is often referred to as a bricked phone, because the iPhone becomes as useful as brick."
 

Kadelic

Genius
Gold
Jan 4, 2010
4,935
1,645
113
Dallas, TX
#6
Do not, I repeat, do not be a numbskull and try this.
I'm sitting here reading this and thinking "yeah, right, there's no possible way this is legit. I'm going to prove it by setting my 6s to 1/1/1970 to show everyone this is a hoax." And then...something stops me from actually trying it. I don't want to be a numbskull after all. :D
 

Napoleon PhoneApart

Moderator
Senior Moderator
Jun 19, 2007
33,438
4,531
113
Upper Marlboro, MD
#7
I'm sitting here reading this and thinking "yeah, right, there's no possible way this is legit. I'm going to prove it by setting my 6s to 1/1/1970 to show everyone this is a hoax." And then...something stops me from actually trying it. I don't want to be a numbskull after all. :D
You don't want to wind up on my numbskull list. I have a few already. :D
 

iPutz

Zealot
Silver
Nov 20, 2012
941
184
43
71
US Midwest
#8
What possible reason would anyone have to reset their date that far back? The article in iClarified did say however that disconnecting and reconnecting the battery would "Un-Brick" the device. True or not I'm not going to try and prove or disprove any of it.
 

Napoleon PhoneApart

Moderator
Senior Moderator
Jun 19, 2007
33,438
4,531
113
Upper Marlboro, MD
#9
What possible reason would anyone have to reset their date that far back? The article in iClarified did say however that disconnecting and reconnecting the battery would "Un-Brick" the device. True or not I'm not going to try and prove or disprove any of it.
Some nerds play with their phones all day hoping to find stuff like this. I guess it gives them something to do until mom delivers their meals to the basement.
 

iPutz

Zealot
Silver
Nov 20, 2012
941
184
43
71
US Midwest
#10
And some nerds are really very long on brains and totally lacking in common sense. Butchya still gotta love 'em if for nothing else than the entertainment value.
 

Europa

Moderator
Senior Moderator
Dec 12, 2008
28,365
5,505
113
Utah
#11
I heard about this early this morning shortly after it was verified that a DFU restore would not fix it. It's not technically ruined or bricked because it can be fixed by Apple or by opening the device and disconnecting and reconnecting the battery. I imagine it will be a problem with demo units at Apple Stores this weekend. I bet we'll see an iOS update next week.
 

RBNetEngr

Contributor
Bronze
Jun 17, 2013
170
27
28
#12
I imagine it will be a problem with demo units at Apple Stores this weekend. I bet we'll see an iOS update next week.
It's interesting that you say this. Does Apple ever force updates out to iPhones? The reason I ask is that when I woke up on Saturday morning (2/13/16) and checked for the time on my iPhone, the screen to enter a pass or was displayed, indicating that I couldn't use TouchID to unlock it because it had been rebooted.

I thought there was something in Settings that indicates how long the device has been running since the last reboot, but I couldn't find it. And I don't make it a habit of memorizing version numbers, so I don't know if 9.2.1(13D15) is newer than the version running prior to Friday night. But looking in the Diagnostics and Usage files indicates that 9.2.1(13D15) has been the version reported for several items dated over the past few weeks, so that looks like it didn't change.

There are no Diagnostics and Usage events that are time stamped during the timeframe of 2300 hrs on 2/12/16 and 1000 hrs on 2/13/16.

Any ideas?
 

Rafagon

Genius
Gold
Dec 7, 2011
7,566
1,252
113
44
Miami, Florida
#13
It's interesting that you say this. Does Apple ever force updates out to iPhones? The reason I ask is that when I woke up on Saturday morning (2/13/16) and checked for the time on my iPhone, the screen to enter a pass or was displayed, indicating that I couldn't use TouchID to unlock it because it had been rebooted.

I thought there was something in Settings that indicates how long the device has been running since the last reboot, but I couldn't find it. And I don't make it a habit of memorizing version numbers, so I don't know if 9.2.1(13D15) is newer than the version running prior to Friday night. But looking in the Diagnostics and Usage files indicates that 9.2.1(13D15) has been the version reported for several items dated over the past few weeks, so that looks like it didn't change.

There are no Diagnostics and Usage events that are time stamped during the timeframe of 2300 hrs on 2/12/16 and 1000 hrs on 2/13/16.

Any ideas?
I've had that happen to me. Please check out this thread: http://forums.everythingicafe.com/t...-48-hours…-bug-makes-it-happen-sooner.108998/
 

Rafagon

Genius
Gold
Dec 7, 2011
7,566
1,252
113
44
Miami, Florida
#14
It's interesting that you say this. Does Apple ever force updates out to iPhones?
Never. You have to authorize every iOS software update manually.

FYI, you do have the option to schedule a pending update to occur automatically during the wee hours of the morning, when you're theoretically sleeping. But even if you select this option for a given update, the next update will not be pushed out to you automatically. You would have to again schedule it for nighttime.

I thought there was something in Settings that indicates how long the device has been running since the last reboot, but I couldn't find it.
This free app will show your device's uptime: https://appsto.re/us/S7Cty.i
 
Last edited:

Europa

Moderator
Senior Moderator
Dec 12, 2008
28,365
5,505
113
Utah
#15
It's interesting that you say this. Does Apple ever force updates out to iPhones? The reason I ask is that when I woke up on Saturday morning (2/13/16) and checked for the time on my iPhone, the screen to enter a pass or was displayed, indicating that I couldn't use TouchID to unlock it because it had been rebooted.

I thought there was something in Settings that indicates how long the device has been running since the last reboot, but I couldn't find it. And I don't make it a habit of memorizing version numbers, so I don't know if 9.2.1(13D15) is newer than the version running prior to Friday night. But looking in the Diagnostics and Usage files indicates that 9.2.1(13D15) has been the version reported for several items dated over the past few weeks, so that looks like it didn't change.

There are no Diagnostics and Usage events that are time stamped during the timeframe of 2300 hrs on 2/12/16 and 1000 hrs on 2/13/16.

Any ideas?
There hasn't been a firmware update yet. Mine does that quite often (requires a passcode even though it hasn't rebooted), but I'm still on 9.0.2.
 

Ledsteplin

Genius
Gold
Oct 29, 2013
4,791
979
113
65
Florence, AL
#16
If I check my lock screen and fool with my phone in the dark a bit, there's times touch ID won't work. But it's because of my actions. The phone thinks a thief is messing with it. So then I have to enter the passcode.
 

Europa

Moderator
Senior Moderator
Dec 12, 2008
28,365
5,505
113
Utah
#17
If I check my lock screen and fool with my phone in the dark a bit, there's times touch ID won't work. But it's because of my actions. The phone thinks a thief is messing with it. So then I have to enter the passcode.
Touch ID works perfectly fine in the dark.
 

Rafagon

Genius
Gold
Dec 7, 2011
7,566
1,252
113
44
Miami, Florida
#18
Getting back on topic, MacRumors tells us that "Apple has officially acknowledged the '1970' date bug affecting 64-bit iPhone, iPad, and iPod touch devices."

Apple's official statement on the subject is a rather terse one: "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."

Of course, "upcoming" is a rather vague term, but at least they've said something.

Hopefully, all of you who read this thread heeded Napoleon's and my warnings in the first few posts and your iDevice is still functioning swimmingly.
 

Ledsteplin

Genius
Gold
Oct 29, 2013
4,791
979
113
65
Florence, AL
#19
Touch ID works perfectly fine in the dark.
The dark had nothing to do with it. When I first wake in the morning, Touch ID does not work. I get a message to Enter the passcode instead. It's only been happening for the past 4 or 5 mornings. I had thought it was because I was checking my lock screen for the time and notifications a while earlier. But then I saw others saying the same. It's like the 48 hour thing but a different message. I'll skip the screen check in the morning and go straight to Touch ID and see what happens.
 

Europa

Moderator
Senior Moderator
Dec 12, 2008
28,365
5,505
113
Utah
#20
The dark had nothing to do with it. When I first wake in the morning, Touch ID does not work. I get a message to Enter the passcode instead. It's only been happening for the past 4 or 5 mornings. I had thought it was because I was checking my lock screen for the time and notifications a while earlier. But then I saw others saying the same. It's like the 48 hour thing but a different message. I'll skip the screen check in the morning and go straight to Touch ID and see what happens.
I was referring to your comment about it not working in the dark, not the bug that causes it to randomly require a passcode (when it hasn't been rebooted or 48 hours without usage). You said it sometimes doesn't work in the dark because of your actions.