Appearance
photo 2 options
  • Logo

    Uploading…
    Photo Uploaded
    Error!
  • Footer Logo

    Uploading…
    Photo Uploaded
    Error!
color 6 options

Success!

Your settings have been saved.

PopWrapped | Technology

Apple Responds To 1970s Bug Hack

Roxanne Powell | PopWrapped Author

Roxanne Powell

Updated 02/19/2016 5:56pm
Apple Responds To 1970s Bug Hack | 1970
Media Courtesy of leganerd

In a previous article, we noted how Apple's latest phone hack takes you back in time to the 1970s.

You don't even need a TARDIS to do it!

Unfortunately, the "hack" makes your phone a shiny brick. In an updated article on February 16, 2016, Apple officially acknowledged the bug while promising their next software update will fix everything.

Everything, Apple?

Why anybody would want to set their system clock and calendar back to January 1970, effectively breaking their device for good, is beyond me.

After several customers have come in to seek AppleCare after attempting this "hack" for themselves, Apple finally made a post about it on their Support Forums. Basically, do not try this at home unless you feel comfortable dropping a few hundred dollars on a new phone.

“Manually changing the date to May 1970 or earlier can prevent your iOS device from turning on after a restart,” Apple said on their website.

On one hand, breaking your phone could be the kick in the pants you've been waiting for to finally get an Apple Watch.

Let's break it down by starting retail price:

Apple iPhone  5s: $450

Apple iPhone 6: $549

Apple iPhone 6 Plus: $649

Apple iPhone 6s: $649

Apple iPhone 6s Plus: $749

Apple Watch: $349-$1,049 (depending on bracelet style and casing, and that's not counting the gold or rose gold models)

Now, Apple is only acknowledging that this bug will crash an iPhone or iPad (yes, that includes Mini models) but hasn't said anything about the Apple Watch. One would assume (and you know what they say about those who assume) the whopping glitch would also affect the iWatch.

Then again, since the iWatch runs the brand new WatchOS, it may be clear of the impending explosion this bug will cause.

I for one will be staying clear of that particular setting for the foreseeable future. Too much could go wrong, and then where would we be?

We are a people reliant on technology. Let's make sure it doesn't die on us.

Share

Are you sure you want to delete this?

ConfirmCancel