Gizmodo 
Enter your username and password.
-
posts about #iphone30bricking more → 
iPhone 3.0 Upgrade Process Deactivating Some Phones From AT&T (Update: Working Now)
Tip your editors:
Editorial Director:
Brian Lam | | Twitter
Editor:
Jason Chen
| AIM | Twitter
Features Editor:
Wilson Rothman
| Twitter
Senior Contributing Editors:
Jesus Diaz
| AIM | Twitter
Mark Wilson, Reviews
| AIM | Twitter
Contributing Editors:
Matt Buchanan
| AIM | Twitter
Adam Frucci
| Twitter
Sean Fallon
| Twitter
Jack Loftus
| Twitter
John Herrman
| Twitter
Dan Nosowitz
Chris Mascari
Danny Allen
| Twitter
Rosa Golijan
| Twitter
Chris Jacob
Columnist:
Brendan I. Koerner
Interns:
Don Nguyen
Kyle VanHemert
Comment Account Questions:
| posts about #iphone30bricking more → |
iPhone 3.0 Upgrade Process Deactivating Some Phones From AT&T (Update: Working Now) |
Original material is licensed under a Creative Commons License permitting non-commercial sharing with attribution.
06/17/09
06/17/09
Be patient, wait an hour or so, and try again; don't be such a complaining bitch about it.
06/17/09
06/17/09
See, you are right that it shouldn't happen, but horribly, undeniably wrong in that you did the right thing. There is NOTHING about 3.0 that you need to have today for your "enterprise" needs. NOT A DAMN THING. Why do you think most IT places still use XP even with it being almost 10 years old? Give up? Its because in a business environment where downtime matters, things have to be as compatible as possible.
If you were worried about lost sales, and had any knowledge of the way the world works, you would have waited a week before upgrading. It doesn't matter if its Apple, MS, whoever, there are limitations to servers and hardware. Windows Mobile updates sure as hell can bring your phone down for awhile since you usually have to wipe the damn thing for any significant update, and they don't have the built in backup features of iTunes.
The point is, any even remotely smart "enterprise" user or IT person would ALWAYS say not to upgrade on day 1 unless its an update that resolves an issue that has been costing the company money (security updates, etc).
You are just as much at fault for using your work phone like a personal phone as Apple would be for a minor activation problem that may not even be their fault (look at the solution posted about IE possibly being the issue).
Man you have a big problem with jumping the gun. Call me a fan boy or whatever you want to try and push my comments aside, I am not defending Apple, just pointing out your awful logic.
06/17/09
06/17/09
If MS servers went down for a huge release like this... the internet would be ablaze with talk about how it was just another MS failure.
When Apple screws the pooch it's the user's fault? REALLY?
06/17/09
His complain is NOT valid, at least in the world of business. I don't understand how anyone could see anything the way he does, from the standpoint he's using. It's completely unfounded. Updates like this ALWAYS break something, no matter how many server strain tests companies do, something can't be addressed until a real-life scenario occurs.
In his case - he REALLY should not have bothered updating, knowing the likelyhood that something wrong COULD occur, and COULD impair business.
It doesn't matter how much Apple hypes something... perhaps they did beef up the auth servers, you DON'T know that. There are a shitload more users than there were last time there was an update that broke on update day.
Get over it, there will be problems.
I haven't updated yet for that very reason.
I have patience.
06/17/09
06/17/09
You don't even own an iPhone. Who are you to talk?
06/17/09
Wow, I sure generated a lot of replies here. If you can read, you will read that I used my phone as a test so there was no damage, I'm just saying this should not happen, it's a bad design to lock a phone this way.
06/17/09
iTunes.. and every single thing having to do with iTunes... is a huge, stinky, steaming pile of SHIT!
06/17/09
06/17/09