Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hes 9, And I think Apple should be fixing this free of charge. The shouldn't have an option in the standard setting menu that basically says 'Brick phone here' and 'Pay Apple ransom to fix'! IMO

Apple does fix this free of charge, the fix includes unplugging the battery for ten seconds and reconnecting it, after doing so, performing a hard reset. Date will automatically set to current date, and all that needs to be done is turn Set Automatically back on.

Also, if there wasn't a fix, I feel as though it is not a multi billion dollar companies responsibility to cover replacement units for people doing something they shouldn't be doing. That's like saying BMW should replace vehicles because someone decided to drive around without oil in the motor.
 
Why exactly should there even be an option to set your date/time in 1970?!

I honestly dont get it and would love some kind of explanation.
 
Apple should prevent idiots from doing idiotic things with their hardware?
What possible reason is there to set any clock back that far?

Exactly the point. Nobody did this for years and years until some OCD wack job stumbled upon it. Now the stupid ones are doing it to themselves on purpose and think Apple should replace their iPhones. The teen script kitties who think they are intelligent are mobbing Apple stores and setting the dates back on display devices. Then they stand in the corner and giggle while they take pictures with their unsafe, security issue riddled Android phones. But then these are the same idiots who drive cars with open recalls for safety issues.
 
image.jpeg


..and that's why this has been trending.
 
Are you saying there's not a problem with iOS being bugged filled lately?

So it does mess up you phone...

I looked it up on Snopes and it said FALSE, but it turns out it mean for the retro boot screen and not the bricking.

My point of Snoping it was wondering about the bricking so False made me think it was safe, I guess I needed to read it more. Oops....
http://www.snopes.com/apples-blast-from-the-past/

Gary
 
Apple should prevent idiots from doing idiotic things with their hardware?
They actually did. If you watch the original video of the guy resetting his iPhone, it took him several attempts before iOS would register all the way back to 1970. There's no reason for anyone to set their device to that date, and the OS makes it difficult to do that, so I don't understand all the outrage at Apple over this bug. It seems like people are latching on to any excuse to slam the company these days.

And it should be obvious that your iDevice would brick if you set it to 1970; Apple didn't exist back then!
 
Are you saying there's not a problem with iOS being bugged filled lately?


You mean like any other software that's out today? Constantly looking for and patching bugs? For what iOS is and does, I would have expected a lot more bugs than it has. I am honestly ok and impressed with the minor few that are found.

This time thing to me, isn't really a bug. Anyone who sets their time/date to 1970 on purpose, deserves whatever they get. Especially knowing full well what it does.
 
They actually did. If you watch the original video of the guy resetting his iPhone, it took him several attempts before iOS would register all the way back to 1970. There's no reason for anyone to set their device to that date, and the OS makes it difficult to do that, so I don't understand all the outrage at Apple over this bug. It seems like people are latching on to any excuse to slam the company these days.

And it should be obvious that your iDevice would brick if you set it to 1970; Apple didn't exist back then!

It's because those that engage in this don't have a life and are living in their grandma's basement on a diet of soda and Cheetos. When they should actually be attending high school.
 
That's like saying BMW should replace vehicles because someone decided to drive around without oil in the motor.

Except my BMW comes with a very thick manual that explains every last menu option, switch and knob, as well as how to maintain it etc.

Under the bonnet are all sorts of warning labels and stickers reminding me to read the manual. So you could argue BMW took all reasonable precautions to educate and warn the user.

It tells me when it needs more oil, so to drive without it would be directly ignoring all of BMW's efforts.

Apple, however, give no real manual (although I'm told there's an online one) and have no such warnings as the phone allows you to wind the time back to 1970. It's Apple's fault for not educating the user and/or allowing the bug to be present.
 
What reason would Apple even have for letting users set their clocks back that far? I don't even understand any situation in which a user would ever need to set their iPhone date to 1970. Or before the current date. Ever. Or at least before the date of the first iPhone if it's needed for troubleshooting something weird and obscure.

This seems like it might be a good way to get a new iPhone for whatever weird reason (people wanting the slightly more power efficient A9, people with scratched glass or casing, etc) if it's still under warranty. Hopefully it's not abused. And anyone who just does this to your iPhone should be held liable just like if they took it and smashed it. But honestly who doesn't use a pass code or Touch ID these days?
 
  • Like
Reactions: Sea Bass
This image is circulating through Twitter about this bug. Hahaha for people believing it actually works. I'm on mobile btw.
 

Attachments

  • image.jpeg
    image.jpeg
    137.1 KB · Views: 470
Just out of curiosity, why should the system even allow you to change the clock to a date in the past? I can't think of any reason someone might want to do this, other than to screw with someone and cause a headache, or purposely temporarily brick a device in this case.

Moving across the date line; accidentally putting the wrong year when setting the date (and thus being able to fix it going back).

Every user input should have it's boundary checked, seems this one has not (and for many years this big lay dormant since setting it back that far is pretty unusual).
 
  • Like
Reactions: BulkSlash
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.