iPhone 3G with ERROR 1604 -- Will not restore...AT ALL.

Quote:

---

Originally Posted by duffrageous

How do you kill iTunes.exe, restart iTunes, and then restore again? All I see is a normal iTunes window. Do you have to wait another 10 minutes for your device to exit the spinning wheel and restart in recovery mode? My understanding is iTunes instantly detects recovery mode even though it's already at the Preparing to Restore part of the process.

---

I finally fixed the issue after 100 restore attempts over 15 hours. I did all the uninstall iTunes and even formatted the hard drive as suggested on YouTube. I simply needed to put the iPhone in DFU and then run sn0wbreeze to get to the last step where it assists you to get into DFU. Apparently, this is a special DFU mode that cannot be entered without the assisted DFU step in pwnagetool or sn0wbreeze. I'd like to thank the person's blog who I can no longer find who suggested to use sn0wbeeze with the cooked pwnagetool firmware.

The new sn0wbreeze 2.1 that was released today as a port of pwnagetool for 4.1 has a new iReb built-in that supposedly overrrides the 160x errors. I'm not sure if the previous versions do as well.

I only lost 1 iPhone in the process by updating to stock 4.1 baseband 5.14.02 out of 10.

Quote:

---

Originally Posted by duffrageous

I simply needed to put the iPhone in DFU and then run sn0wbreeze to get to the last step where it assists you to get into DFU. Apparently, this is a special DFU mode that cannot be entered without the assisted DFU step in pwnagetool or sn0wbreeze. I'd like to thank the person's blog who I can no longer find who suggested to use sn0wbeeze with the cooked pwnagetool firmware.

The new sn0wbreeze 2.1 that was released today as a port of pwnagetool for 4.1 has a new iReb built-in that supposedly overrrides the 160x errors. I'm not sure if the previous versions do as well.

---

To be clear - sn0wbreeze is NOT a port of pwnagetool. It never has been.

Sn0wbreeze is a GUI on top of an open source cross-platform utility called xpwntool (which was originally written by a member of the iPhone Dev Team)

Redsn0w 0.9.6b2 on windows also includes the pwned dfu mode. This pwned dfu mode comes originally from geohot's limera1n.

We don't recommend or encourage sn0wbreeze here, I'm unsure about 2.1 - the word is that for once, it uses the same patches as other tools (one of the big problems historically with sn0wbreeze)

iREB has been built into to sn0wbreeze for a while now (at least since 2.0). I'm somewhat against this as some of these errors are informative and simply suppressing them can be counter-productive.

im not clear on if a solution has been found or not, i have the 1604 error im trying to update to 4.1 from a jailbroken/unlocked 3.2.1 3G
i have tried iReb dosnt work, and the restart method of killing the process did not work for me either i killed itunes and mobildevice, am i missing something? is there a step by step method someone can explain? to fix a 16xx error

Quote:

---

Originally Posted by STAYCOLD

im not clear on if a solution has been found or not, i have the 1604 error im trying to update to 4.1 from a jailbroken/unlocked 3.2.1 3G
i have tried iReb dosnt work, and the restart method of killing the process did not work for me either i killed itunes and mobildevice, am i missing something? is there a step by step method someone can explain? to fix a 16xx error

---

You ask about how to fix a 16xx error, there are at least 10 different error codes that fall under 16xx and are commonly encountered. The solutions for each specific error can vary.

Please publish your restore log and a clear description of what you were trying to do. That is the FIRST step in finding a solution.

http://www.hackint0sh.org/f137/130802.htm

iREB is NOT a solution it is a workaround.

Are you using a custom IPSW (that you made yourself with pwnagetool 4.1 or 4.1.2), or an original IPSW (downloaded direct from Apple)

We won't support custom IPSW you "found" on the net. They are often the problem.
We won't support custom IPSW made by any version of sn0wbreeze. These *might* work for you, or they might not.

You speak about trying to "update" to 4.1, I do hope that you are not shift-clicking the "update" button in iTunes and then browsing to a custom IPSW. That simply won't work with a custom IPSW, it will only work with an original IPSW (which will also upgrade your baseband)

The most common non-custom IPSW cause for 1604 is problems with USB, the solution for this is explained on the Apple troubleshooting page. Update and restore alert messages on iPhone, iPad, iPod touch and Apple TV (2nd generation)

1604 is usually caused by being in DFU mode with an already pwned device when you don't need to be.

Quote:

---

Originally Posted by Olethros

You ask about how to fix a 16xx error, there are at least 10 different error codes that fall under 16xx and are commonly encountered. The solutions for each specific error can vary.

Please publish your restore log and a clear description of what you were trying to do. That is the FIRST step in finding a solution.

http://www.hackint0sh.org/f137/130802.htm

iREB is NOT a solution it is a workaround.

Are you using a custom IPSW (that you made yourself with pwnagetool 4.1 or 4.1.2), or an original IPSW (downloaded direct from Apple)

We won't support custom IPSW you "found" on the net. They are often the problem.
We won't support custom IPSW made by any version of sn0wbreeze. These *might* work for you, or they might not.

You speak about trying to "update" to 4.1, I do hope that you are not shift-clicking the "update" button in iTunes and then browsing to a custom IPSW. That simply won't work with a custom IPSW, it will only work with an original IPSW (which will also upgrade your baseband)

The most common non-custom IPSW cause for 1604 is problems with USB, the solution for this is explained on the Apple troubleshooting page. Update and restore alert messages on iPhone, iPad, iPod touch and Apple TV (2nd generation)

---

i was running a jailbroken/unlocked 3G firmware 3.2.1 my phone was stuck on the boot screen, if there is a way to fix that problem let me know, i proceeded to try and restore it to 3.2.1 (original IPSW file not custom) got a 1604 when trying to do so, then i tried with 4.1 restore and update i think i got a 1603 or 1604 that time, good thing because the 5.14 baseband isnt unlocked yet, SO i tried ireb for the hell of it, didnt work, then snowbreezze got a 1604, then tried 4.0 and closing itunes after the 1604 and reopending it also didnt work then tried with 3.2.1 close and open, that didnt work,

all i am wanting to do is upgrade to a 4.1 and keep my baseband a 4.26 or atlease a unloackable baseband, and not get this 1604 or 1603 error,

HOW DO I DO THAT?

i cant get apast boot logo my phone has to be in dfu for itunes to pick it up

# iTunes version 10.1.0.54)
# iPhone OS version (before restore/update) (e.g. 3.2.1)
# OS Version ( Windows 7)
# Detailed Instructions to Reproduce the Problem (The more specific the better.)
# FULL iTunes restore Log (dont know how to get this info)

trying to update to 4.1 from a jailbroken unlocked 3.2.1 and be able to unlock agian and not upgrade the baseband just the firmware and jailbreak? how do i do this without getting a 1603 or 1604 error

trying to use apple's 4.0.2 gives a 3194 error

3194 is no blobs

1604 is wrong mode - if you do a normal restore try restore mode, if that doesn't work try DFU.

If your phone is working, wait a few days until 4.2....

Quote:

---

Originally Posted by Confucious

3194 is no blobs

1604 is wrong mode - if you do a normal restore try restore mode, if that doesn't work try DFU.

If your phone is working, wait a few days until 4.2....

---

my phone will not power on apast the boot seen so itunes only sees it in dfu
the unlock isnt going to come out till th 26th probably and i need my phone. so its like what do i do i just tried to restore it on another computer to 4.0.2 and got 3194 abd i dont know how to update to 4.1 and keep my baseband under 5.14? custom 4.1 file made with sn0w 1603ed or 1604d