This iOS time and date bug could permanently brick your iPhone, iPad or iPod touch

Software bugs occur all of the time, but some pose more of a threat to the security and general wellbeing of our devices than others. Fresh off the back of the error 53 story, which revealed that the Apple iPhone can be rendered completely useless if unofficial repairs to the Touch ID component have taken place, a video has surfaced online that apparently shows how a device can be bricked by means of a fairly innocuous software trick. 

As seen in the video below and noted by several others apparently affected by the bug, changing the date to January 1st 1970 and rebooting results in a non-functioning handset. After the reboot, the handset can be placed into DFU mode and recognized by iTunes. But even after a restore, it gets caught in a boot loop and cannot be used. 

Affected devices are said to be those running a 64-bit processor. Specifically, this includes the iPhone 5 and newer, iPad Air / iPad mini 2 and up, and the 6th-gen iPod touch. If your device is older than any of the above, then this bug will not affect your device. 

There's nothing to be too alarmed about here, for the bug apparently won't affect you unless you deliberately expose it. It's very likely that your device will cease to function, and you'll probably be forced to take a trip to the Apple Store. Presumably, Apple will be able to repair or replace devices affected by this bug, and above all, we'd expect a fix for this strange issue to manifest itself in the next software update. 

Check the video demo of the bug in action below, and let us know of your thoughts via the comments. 


source: 9to5Mac

FEATURED VIDEO

35 Comments

1. PHYCLOPSH

Posts: 652; Member since: Jun 28, 2014

I have tried this on Android and confirm that there is no such issue at this time.

3. AlikMalix unregistered

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 unregistered

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: 5029; Member since: Mar 30, 2015

No such issue on android searched for 30 min the web for anything about this and found nothing!

32. AlikMalix unregistered

My point went right over your head, apparently.

23. Finalflash

Posts: 4063; Member since: Jul 23, 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 unregistered

I just tried every date from 1940's to 1945's, so if someone else can do the next 5 years ;)

35. My1cent

Posts: 370; Member since: Jan 30, 2014

Have you ever tried to re-charge your phone using any microwave oven? It works on iPhone!

2. AlikMalix unregistered

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: 4063; Member since: Jul 23, 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 unregistered

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: 2278; Member since: Aug 06, 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

7. Subie

Posts: 2349; Member since: Aug 01, 2015

I'm guessing they forgot to add the "S"

14. Wiencon

Posts: 2278; Member since: Aug 06, 2014

But if you click on it it brings you to iP5 page so it's more than a typo :P

5. nepalisherpa

Posts: 338; Member since: Jul 17, 2015

I wonder what's significant about Jan 1, 1970.

9. matistight

Posts: 976; Member since: May 13, 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.

12. nepalisherpa

Posts: 338; Member since: Jul 17, 2015

Thank you.

25. Brewski

Posts: 671; Member since: Jun 05, 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: 435; Member since: Nov 15, 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: 854; Member since: Apr 22, 2013

Dead display units will start popping up at stopped all over the country.... Sigh.

11. SirYar

Posts: 351; Member since: Jul 02, 2014

Another quality piece of software from Apple.

13. MrElectrifyer

Posts: 3960; Member since: Oct 21, 2014

No, you're setting it wrong... Yet another proof of how iOS is considered the most vulnerable OS on the market. bit.ly/1FZM9C9

15. TechieXP1969

Posts: 14967; Member since: Sep 25, 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: 3960; Member since: Oct 21, 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: Sep 15, 2012

The iPhone is just there to remind us that almost nothing good emerged from the 1970s.

17. xondk

Posts: 1904; Member since: Mar 25, 2014

I don't know, RAM and Floppy disk were invented in 1970 amongst other things :P but yeah I get what you mean.

28. tedkord

Posts: 17295; Member since: Jun 17, 2009

But so was disco.

19. buccob

Posts: 2963; Member since: Jun 19, 2012

How long before malware apps change the date of users, or people fall for pranksters asking others to try it out...

24. Arch_Fiend

Posts: 3951; Member since: Oct 03, 2015

Why change the date to jan 1st 1970 and reboot anyway that's stupid.

26. darkkjedii

Posts: 30960; Member since: Feb 05, 2011

I thought this would be something to worry about...Mehhh.

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at https://www.parsintl.com/phonearena or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit https://www.parsintl.com/ for samples and additional information.