So, I, like many others got the dreaded 1013 when I tried to update to 4.2 on my iphone 4. Restoring didn't work, no posted fixes worked. So, I decided I was going it wing it. I downloaded the latest redsn0w beta and did exactly what every guide told me not to do, tried to jailbreak straight from 4.2.1 firmware and not 4.1. It got to "Installing Application Bundles" and Springboard crashed and the phone locked up essentially. After giving up on that I hard restarted the phone and it was back to the restore screen. I went to iTunes and clicked restore one last time. Viola! Worked like a charm! No errors or anything. So that is my suggestion to you all should you encounter the error on your device. It's probably dangerous, but it worked for me.
Alternatively, you could try using a recovery program like iRecovery to get it to boot then try updating from there. Usually it will work in the case of a failed update. iTunes puts your device in the "connect to iTunes hurr" state but the OS on there is fully functional and everything.
Anyway, if anyone else is getting this error, please try the iRecovery method and tell me how it works.
[QUOTE=SA Spyder;26248369]Alternatively, you could try using a recovery program like iRecovery to get it to boot then try updating from there. Usually it will work in the case of a failed update. iTunes puts your device in the "connect to iTunes hurr" state but the OS on there is fully functional and everything.
Anyway, if anyone else is getting this error, please try the iRecovery method and tell me how it works.[/QUOTE]
I'd like to see how this goes as well, its probably a lot safer than my method.
Only issue now is the fact that Safari crashes on launch.
Sorry, you need to Log In to post a reply to this thread.
