Currently Being ModeratedFeb 23, 2013 7:24 PM (in response to Michael Crabb)
Error -1 is most often a very bad hardware error of the Baseband Chip. Apple recomendation is to try to Restore your iPhone on a different computer. To get iPhone into Recovery Mode. Open iTunes on computer. Connect iPhone to computer with USB Cable. Hold both Home and Power buttons for about 20 seconds until iTunes on computer recognizes iPhone in Recovery Mode. Click the Restore button of iTunes.
Currently Being ModeratedFeb 24, 2013 7:02 AM (in response to brad805)
Thanks, that helped and that's what I did. Then after restoring on another computer, which wiped all my apps and data, I went back to the iMac that the phone is linked to and did a restore from back up. Now everything is back to where it was prior except the iOS is now current.
I wonder if the Apple servers were getting overloaded with updaes yesterday...I forgot to mention the other error I got repeatedly was "loss of network connection". And I got that message twice while trying ro restore on another machine as well. Both machines are hard wired, no wifi.
Currently Being ModeratedFeb 25, 2013 7:36 AM (in response to brad805)
I have had this happen as well on an iPhone4, both with 6.2 IOS update, and the 6.2.1 update. Both failed with 'unknown error' and then did a restore (on the same Mac Air), and required a restore of the backup and a sync to get the apps backs (on the same Mac Air). My iPhone5 upgraded just fine though. Other than the two IOS update failures, the iPhone4 works perfectly and sync's fine etc. I rather suspect it is an IOS update issue as I've heard of this same problem on other iPhones, but just iPhone4. Very odd that after the restored backup etc the IOS itself is indeed updated. Perhaps Apple is 'phasing' the iPhone4 and pushing it out with IOS updates that frustrate iPhone4 users, or it's just another example of some MS Windows programmer now working for Apple!
I had this error also on my iPad2, which I initally thought might have just been out of space, but just got the same failure on my iPhone5. Going through the restore now.
Both devices updating from 6.0.2 to 6.1.2