This iOS time and date bug could permanently brick your iPhone, iPad or iPod touch
1. PHYCLOPSH (Posts: 123; Member since: 28 Jun 2014)
I have tried this on Android and confirm that there is no such issue at this time.
3. AlikMalix (Posts: 4839; Member since: 16 Jul 2014)
Android does have it, it's just another date you have to set it to. You gotta try every day possible starting from 1940's.
6. Unordinary (Posts: 1004; Member since: 04 Nov 2015)
Of course. It's just a matter of figuring it out. 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. This is triggered by having the time value less than zero
20. marorun (Posts: 2881; Member since: 30 Mar 2015)
No such issue on android searched for 30 min the web for anything about this and found nothing!
21. lyndon420 (Posts: 3716; Member since: 11 Jul 2012)
Google updated their clock app a few days ago and PA posted something I believe the following day. On a side note...what doesn't brick an iPhone lately???? Careful...don't breathe wrong or it'll brick on ya lol.
32. AlikMalix (Posts: 4839; Member since: 16 Jul 2014)
My point went right over your head, apparently.
23. Finalflash (Posts: 2725; Member since: 23 Jul 2013)
Lol Yea no, Android has no such bug because the internal system clock doesn't depend on the millisecond. There is a "long" primitive that tracks how long it has been since Jan 1970 and it can go negative. Once an app tries to use that number, if it doesn't have a check to handle a less than 0 value it might crash. Apps that depend on that might break but the system itself does not track the time using that method. Regardless, this issue will not happen with OSX, Windows or Android because none of the developers on that side of the pond were stupid enough to link system functions with the millisecond counter used by the front end of the system without a security check.
33. RebelwithoutaClue (Posts: 2633; Member since: 05 Apr 2013)
I just tried every date from 1940's to 1945's, so if someone else can do the next 5 years ;)
35. My1cent (Posts: 337; Member since: 30 Jan 2014)
Have you ever tried to re-charge your phone using any microwave oven?
It works on iPhone!
2. AlikMalix (Posts: 4839; Member since: 16 Jul 2014)
Wow, I'm trying to imagine how someone came across that bug... Maybe someone sold it as a time machine to a clueless user. Apple users will believe anything...
27. Finalflash (Posts: 2725; Member since: 23 Jul 2013)
It is a simple thing to set the clock back 50 years to fool around. See how far you can go, someone was bound to do it. Sad thing is, someone at the iOS development team with system level programming access decided not to do a
34. RebelwithoutaClue (Posts: 2633; Member since: 05 Apr 2013)
It is the date that is set when the phone completely runs out of battery and the phone is reset to factory settings. Had an iPhone 4s in storage once that was locked for 24 million minutes because of this.
4. Wiencon (Posts: 1713; Member since: 06 Aug 2014)
"Affected devices are said to be those running a 64-bit processor. Specifically, this includes the iPhone 5 and newer"
iP5 doesn't have 64 bit soc
14. Wiencon (Posts: 1713; Member since: 06 Aug 2014)
But if you click on it it brings you to iP5 page so it's more than a typo :P
5. nepalisherpa (Posts: 207; Member since: 17 Jul 2015)
I wonder what's significant about Jan 1, 1970.
9. matistight (Posts: 418; Member since: 13 May 2009)
The Unix epoch is the time 00:00:00 UTC on 1 January 1970. So setting it before that, the phone does not know what time it is, confuses the system, freaks out and bricks itself in confusion. Just like error 53, its another part of coding they simply need to change "true" to "false", or the reverse.
25. Brewski (Posts: 312; Member since: 05 Jun 2012)
^yes. I can confirm this. When setting the time on a machine running Unix it counts the seconds since then and so you set it to years/months after that date.
8. htcisthebest (Posts: 134; Member since: 15 Nov 2011)
It's alright. If this happens to me. I will just upgrade to the Galaxy S7 or the Surface Phone, whichever comes first.
10. tacarat (Posts: 722; Member since: 22 Apr 2013)
Dead display units will start popping up at stopped all over the country.... Sigh.
11. SirYar (Posts: 351; Member since: 02 Jul 2014)
Another quality piece of software from Apple.
13. MrElectrifyer (Posts: 1898; Member since: 21 Oct 2014)
No, you're setting it wrong...
Yet another proof of how iOS is considered the most vulnerable OS on the market.
15. TechieXP1969 (Posts: 7870; Member since: 25 Sep 2013)
What idiot would do this? Oh wait, the potential with iOS must really be high. Or you basically would have to be high.
The time and date is set by the network on the phone, so how would it ever be an issue?
Who would ever do this?
The idiot who even found this bug, needs a life. Get out the basement dude, and get some human interaction.
18. MrElectrifyer (Posts: 1898; Member since: 21 Oct 2014)
Simply security researchers exposing all the bugs and vulnerabilities apple just sweeps under the rug and calls it a day. Security by obscurity ain't security, and apple needs to fix that in all their software...
16. Baracus (Posts: 223; Member since: 15 Sep 2012)
The iPhone is just there to remind us that almost nothing good emerged from the 1970s.
17. xondk (Posts: 1132; Member since: 25 Mar 2014)
I don't know, RAM and Floppy disk were invented in 1970 amongst other things :P but yeah I get what you mean.
19. buccob (Posts: 2491; Member since: 19 Jun 2012)
How long before malware apps change the date of users, or people fall for pranksters asking others to try it out...
22. lyndon420 (Posts: 3716; Member since: 11 Jul 2012)
Doesn't anyone have their clocks automatically set to their carrier? Weird.
24. Arch_Fiend (Posts: 1938; Member since: 03 Oct 2015)
Why change the date to jan 1st 1970 and reboot anyway that's stupid.
26. darkkjedii (Posts: 19454; Member since: 05 Feb 2011)
I thought this would be something to worry about...Mehhh.
30. 47AlphaTango (Posts: 237; Member since: 27 Sep 2015)
What if the user doesn't register their fingerprint from the unlocking and apple id? You won't encounter error 53!
36. Lauticol (Posts: 313; Member since: 25 Jun 2011)
Nice way to get a replacement if your iPhone is having other issues
37. _PHug_ (Posts: 443; Member since: 11 Oct 2011)
Going to be funny when Apple charges people full price when they bring in phones that were bricked on purpose just to see if it works.