Iphone, ipad bug causes infinite bootloop when date is changed back to 1 january 1970_

If an “unlucky” iOS user does try to set the dates back, the device would be bricked. After setting the date, it would still run normal. Once it reboots, it will be stuck in the booting up screen until the battery dies. Some have tried to boot it up again after the battery died. Others were lucky enough to get it to boot and set the date back to the current year, but others were not so fortunate. Apple (NASDAQ: AAPL) has another nasty bug to deal with. iPhone and iPad users who set their dates manually back to 1 January 1970 will have their phones bricked once it reboots. In order to try and fix the bug,

one user tried to set the date back to January 1, 1970. After rebooting, the iPhone was then stuck in a bootloop.

The user posted the experience on the Internet, which soon got others to try and replicate the bug, thinking that it would not affect them. Users who tried out the bug and ended up with a bricked phone had their iPhones replaced for free. Some reddit users have already suggested that they should just do the bug in order to get a new phone especially if they have Apple Care Plus. Best Choice of Actions is Replacement iPhone, iPad from Apple Interestingly, some Reddit users managed to try and do the bug but still survived. One user explained that the reason behind it is because of time zones. Pranksters have already tried to dupe others into changing their dates. 4chan users have posted a LifeHack ad campaign, which trick unsuspecting users into changing the dates to seemingly activate a Macintosh theme on their iPhones. Others simply try and trick their friends through social engineering.

There could be some instances where someone could just try and borrow the phone to simply change the date. If somebody had their iPhone’s date changed to 1 January 1970, it would be wise not to turn it off. The bug happens when it is rebooted so it is advised to just change the date back to year 2016. iPhone Apple One reddit user by the name of Ziph0n shared his jailbreak tweak to prevent other users from trying to replicate the bug manually. The tweak is called BrickingDate and it changes the time and settings tab into a blank slate, which means that the date can’t be manually set. Naturally, the first step that iPhone users tried is to restore the phone through iTunes on their computers. Unfortunately, restoring it does not even work. The best option to fix the iPhone is to have it replaced through an authorized Apple dealer. Of course, this would need the original receipt to validate the warranty of the phone.

The origin of the bug was from another bug in the iOS 9.3 Beta 3 version. Time was being prevented from being displayed in the status bar of the version. Remote Attack to Replicate Bug Possible Even the desktop browsers were not safe. Visiting the site on a desktop browser also caused the browser to hang and crash. Users who were working on another tab were unfortunate to lose their progress. The bug is one of the more unusual ones. There isn’t really much of a valid reason why somebody would set their dates that far back. For average users, such bugs would be a big problem.

However, users who are nearing the end of their warranty period are considering to do the bug in order to have a replacement. Other bugs that were encountered in the past include the iMessage that caused problems and a prank site that caused several browsers to crash and iPhones to suddenly reboot. In the case of the latter, it was not as harmful as the 1970 bug. “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. Best guess is that this is triggered by having the time value less than zero,” said redlion1992 on the r/jailbreak thread.

When users try to visit crashsafari. com, the browser is overloaded by a string of text. iPhones were then forced to reboot because of the problem, but the bug was not exclusive to the iOS platform. 1970 Bug as a Way for Replacement?

The January 1, 1970 iOS Bug Explained Apple iPhone users also had a different, yet difficult bug last year. When users tried to update to iOS 9, some of them got stuck at the Slide to Upgrade screen. The 1970 date bug affects all iPhones, iPads and even iPod touches that are powered by 64-bit processors that currently run the iOS 8 or iOS 9 versions. They also include the iPhone 5S and newer models, according to Guardian. While users who are sane enough not to try and do the bug are safe, there is still a chance that someone else could do it remotely. A skilled hacker could connect into a public Wi-Fi hotspot and set off a malicious NTP (Network Time Protocol) request to try and adjust the time settings of every connected iPhone.

Once the connected devices automatically update their time through the Wi-Fi connection, they will end up in a bootloop once it reboots. Backing up the phone data is a must if a user wants to replicate the bug. Since the iPhone would be replaced, it would be wise to wipe it first before trying to change the date. The only way to restore the device into a working state was to wipe it. It meant that users had to delete all of their files and start over again. One YouTube video even showed how to do it and it took almost a minute to scroll back to the said date. After rebooting, the iPhone got stuck in a bootloop with no end in sight. Android phones that visited the site would still have problems.

The browsers would lag so much that it became unresponsive. Even the iPad mini 2, iPad Air and the sixth generation of the iPod touches are vulnerable to the bug. Apple already said that they are working on the problem and could release a small update to protect the users from the bug soon. Users who would like to try for whatever reason would still have a hard time doing so. Setting it that far back manually to January 1, 1970 requires a lot of scrolling. Other iOS Bugs