[luckyownz92]

This is from 2007! Read the date people!

[BobbyW]

I know it's old but i'd like to know what happened. It would be great if these people who start topics actually post again once their problem is fixed instead of keeping it to themselves has it been solved.

I have a similar case:

"Hello to all you mac gurus out there, this is my last resort. I had to restore my iPhone recently and it was at 2.0 unlocked etc. The problem is iTunes upgrade it to 2.0.1 at the same time. I had a locked phone after that but a working one none the less. I needed to unlock it again and i used Pwnage Tool i did a custom firmware of 2.0.1 i believe and it worked once BUT, when the phone restarted to load the bootloader it gave me an error. I was still able to use the phone at that point but not to make calls. I tried restoring the firmware again without success, it started giving me the dreaded 1604 error. I tried once more but did a wipe/new custom firmware and i think that might have put an incomplete firmware on my iPhone. Right now i tried all 3 different computers, plenty different USB ports, NVRAM reset, different itunes versions with different firmwares. I can't get past the apple logo with the spinning wheel at the bottom while in itunes it's saying "preparing iPhone for restore" then after maybe 3 minutes, sometimes less i get the damn 1604 error. I have used AppZap to remove all the itunes components and such before i install a different version still to no success. Also before anyone starts suggesting, it's not because of the DFU mode, i'm 100% sure it's in the right DFU mode and not recovery. Anyone have anymore ideas? One more thing, when i turn the iphone on, it starts with the pineapple logo and then stays on the russian steve jobs."

[feelx2210]

hey guys,
I've been trying everything for 2 days now.
And finally one thing helped me to get out of this endless restoring - getting 1604 or 1611 or whatever error pops up depending on itunes version and firmware version.

Now I simply tried the latest pwnage tool for mac and created a custom 2.0.1 ipsw and NOW IT WORKS!

It is really unbelievable for me, but after appr. 20min of restoring process I was patiently waiting for an error to come up, but nothing! It is now running on 2.0.1.

Try this!

[xboxaug04]

feelx2210,

Thanks for sharing your case. I followed the same steps, that is instead of following to troubleshoot 1604, when I opted for pwnage (winpwn for me, as I am Windows user), I was able to get my iphone un-bricked. I cannot forget those horrible 4 hrs when my lovely iphone was bricked.

now it's upgraded to ver 2 and loving using the activesync for emails
Thanks again

[scoggs]

okay so i have the same exact problem the OP has or had... who knows. but with a few minor differences. it originally started as a 1619 error in 7.7 then it went to a (1) error in 7.4.2/7.5 and nothing else. iTunes will also not recognize the phone when it has the connect to itunes screen up. only when i turn it off and put the phone into what i think is DFU.

And when i say i think, its mainly because it looks like its in DFU mode but iTunes just says recovery mode.

I also tried that winstaller or whatever, it doesnt detect the iphone, and crashes when the iphone is in 'DFU' mode.

and i did the whole sim card thing and that doesnt work... so what next?

EDIT

oh and i almost forgot... itunes is calling it an ipod for some reason...

[questioncom]

i had that happen a few days ago. after i reinstalled itunes, it worked like a charm from DFU mode.