"Unknown error (6)" with itunes, when restoring an iPhone 4 to 4.2.1 --what is this?
Hello fam, I've been having this little issue for the past few days... I tried to update my already jb iPhone 4 (from 4.1) to 4.2.1 using iClarified's tutorial and have been getting a crazy error that doesn't seem to be an issue when googling. I don't really know what the issue is.
I checked the log and see that the TSS is started. I tried restoring while in DFU mode. I know that similar errors were with itunes not being updated, so I updated to the new itunes. I saw that some error codes where because for whatever reason, itunes had signed out--so I checked and resigned in just to be sure. Then I noticed that error code 6 a few years ago had to do with something in the host file, sooooo I went and removed those lines as advised-- but I still get the error code.
Now my phone is stuck in a recovery loop. I tried to use a saved 4.1 restore, and that still gives me the error.
Does anyone have any experience with this?
Edit: it was my attempt to update without upgrading my baseband --even tho the current baseband is unlockable. I didn't specify earlier that I do have the requisite SHSH files stored both with cydia and locally.
Last edited by thunderhawki; 02-11-2011 at 07:00 AM.
Reason: Automerged Doublepost
Thanks! I looked at the error code listings, and assuming that "unknown error (6)" is the same as error 6, then it isn't liking the USB port. Well, I tried changing to each of my 3 other usb ports (restarting after each change) and still getting the same error when restoring.
Last edited by thunderhawki; 02-11-2011 at 08:25 AM.
Just an update, you are amazing! Trying another computer did the trick!! I'm not real clear on why I needed another computer, tho. Any after I got the good error code (letting me know that the baseband wasn't updated), then I moved back to my computer and tried to move everything back.
Then I had a new problem. My device kept timing out when syncing the contact/pic/media/apps! I used WINscp to log into my i4 and remove the database files, which I read would resolve the issue, buuut no. So I'm now looking online some more before I bother this forum again just yet... :wink: