I guess it must be hard for you to see anything behind those fangirl glasses you're wearing but here in the real world it is reasonable to expect a company making cellphones not to do something as stupid as what Apple and AT&T just did. This isn't an act of god or something unforeseen, they could have and should have done their own stress testing to see what would happen and realize that allowing people to brick their phones is something that needs to be worked around. If I made a decision at my job that resulted in a situation like this, I'd be fired on the spot, and rightfully so, IMO.
As I said before, this isn't the end of the world, but it IS a big deal, and people whose iPhones are now iBricks have every right to be pissed off about it.
Look the difference between:
iPhone1,1_2.0_5A347_Restore.ipsw = iPhone First Generation
and
iPhone1,2_2.0_5A347_Restore.ipsw = iPhone 3G
This is the reason why "iPhone1,2_2.0_5A347_Restore.ipsw" link was up yesterday because some countries were already selling 3G and it had to be there in case someone with 3G needed to restore, we never saw it on iTunes because it can only be seen as a 3G update
I guess it must be hard for you to see anything behind those fangirl glasses you're wearing but here in the real world it is reasonable to expect a company making cellphones not to do something as stupid as what Apple and AT&T just did. This isn't an act of god or something unforeseen, they could have and should have done their own stress testing to see what would happen and realize that allowing people to brick their phones is something that needs to be worked around. If I made a decision at my job that resulted in a situation like this, I'd be fired on the spot, and rightfully so, IMO.
As I said before, this isn't the end of the world, but it IS a big deal, and people whose iPhones are now iBricks have every right to be pissed off about it.
ok i am terrified, i just started to update my mums iPhone to 2.0 and then read about the issues. What are the chances of it not working correctly? Can it be fixed later?
Oh no! I tried to warn you, but…OK, now it is stuck in that endless loop, does anyone know how to fix this?
Apple should have let 1st gen iPhone owners to download 2.0 earlier this week. Both as a 'thank you' and to prevent this very thing from happening.
Again - read what i wrote (and quit calling me names! I am NOT a 'fangirl')
It is STUPID to do ANYTHING ON THE FIRST DAY OF A SIGNIFICANT RELEASE if you REQUIRE 100% usage of that device. The smart thing to do is WAIT.
You can argue all you want, but if you needed your phone today, you should have waited PERIOD END OF DISCUSSION.
It isn't just Apple - it is true of any new software, new product, new gaming device etc.
Just broke through the damn iTunes Berlin Wall
I've been pretty silent up until now but I firmly disagree with this. While this sadly may be the norm, its certainly not something that companies or users should be comfortable with. It is never the consumers fault if they choose to upgrade on day one. I'm a software developer. If i release crappy software on day one then it's not the user's fault. It is my own. It's a testament to the lack of proper testing and capacity planning that goes with things like this that has jaded users into thinking they have to wait, because it can't ever possibly work, but that's just a sad mentality. Software developers and engineers all need to do better. Imagine if the car industry was like that and we said, "well you bought your car on day one. It's your freaking fault dude that your car now has a problem."
I'd say it's risky to upgrade on day one, but it's never the user's fault if things don't work, and users who upgrade and that don't have success have a right to be angry. I can guarantee Apple is pissed as hell right now with themselves and their performance, so why shouldn't we be?
Perhaps the difference is due to Tiger versus Leopard? There is no red record button. Is this what you get with your Automator?It was my first time using it too. When you open up Automator, click the red record button in the upper right hand corner. It will hide automator and show your applications underneath. Just go through the motion in iTunes. Click on say "Purchased" then click on your phone, then click on the "OK" button when the error comes up. Then stop recording.
This will appear in automator. You can press play and make sure everything works. Once you verify it's working, click on the whole thing, cmd+c to copy, cmd+v to paste, and you can keep pasting several times. once you have a good set, just press play and let it do it's thing.
The bad thing is that you can't do anything else while it's running...
i'm gonna say hours, this is a huge PR disaster if they don't get these phones activated within the next 8 hours
http://www.macworld.com/article/134442/2008/07/iphone_launch.htmlTechRepublic editor Jason Hiner reports that in his line in Louisville, Kentucky, an Apple representative just said, "We're looking at considerable delays," indicating that it might be a three or four hour wait for a phone. Hiner went on to report that an Apple representative had indicated that all activations had stopped temporarily and might not resume for some time. And indeed, our Jonathan Seff has also heard that it's down again.