Argh!!! 1604 error!

Discussion in 'Jailbreaks and iOS Hacks' started by mdwsta4, Jul 20, 2008.

  1. mdwsta4 macrumors 65816

    Joined:
    Jul 23, 2007
    #1
    i tried following these steps:
    http://www.hackthatphone.com/20/pwnagetool_2_1st_gen_iphone.html

    yet every time it gets to the itunes restore part after the pinapple appears, i end up with an error in itunes stating 1604 and the iphone cannot be restored!!!

    so WTF?! i've tried repwning it 4 times. same error every time.
     
  2. gazzer82 macrumors regular

    Joined:
    Jul 8, 2008
    #2
    Did you do this?

    Note: many can not get into DFU mode. The solution appears to be ensuring that you have the following path on your Mac: ~/Library/iTunes/Device Support If you do not have the Device Support folder, then create one.

    It can also fix the 1604 error.
     
  3. mdwsta4 thread starter macrumors 65816

    Joined:
    Jul 23, 2007
    #3
    yes, i deleted the file that was in there. getting into DFU wasn't a problem.
     
  4. spinstorm macrumors 68000

    Joined:
    Sep 14, 2007
    #4
    PwnageTool 2.0.1 is out.

    Links are in my Pwnage FAQ below.

    This may fix the problems.

    1604 suggests you need to make a new custom firmware and try again!
     
  5. mdwsta4 thread starter macrumors 65816

    Joined:
    Jul 23, 2007
    #5
    downloading now. we'll see if that works.
    what do you mean custom firmware? i'm doing the simple step. i dont believe i'm making a firmware myself?
     
  6. mdwsta4 thread starter macrumors 65816

    Joined:
    Jul 23, 2007
    #6
    nope, STILL getting the 1604 error even with version 2.01
     
  7. jwmcgee1 macrumors newbie

    Joined:
    Jul 23, 2008
    #7
    I have re-downloaded the .ipw for 2.0, rebuilt my custom .ipw file and still get a 1604 or 1600 error.

    I can't seem to get the phone to do anything. Please tell me I have not trashed my 2g phone.
     
  8. mdwsta4 thread starter macrumors 65816

    Joined:
    Jul 23, 2007
    #8
    FWIW, i 'fixed' my problem. took my phone into an apple store and they gave me a brand new one. not the best fix, but hey, it worked! i was currently on ATT. just liked it unlocked/jailbroken for myself. i'm waiting until ziphone comes out with an updated app. i miss summerboard.
     
  9. adamerr macrumors 6502a

    adamerr

    Joined:
    Jun 7, 2008
    #9
    they just "gave" you one?
    wow.
    did you still have the jailbreak installed?
     
  10. mdwsta4 thread starter macrumors 65816

    Joined:
    Jul 23, 2007
    #10
    i told them i tried to upgrade to 2.0 and it didn't work. showed them the error, they tried to update using their computers and had the same problem. my phone wouldn't do anything so i don't think there was anything to even show it was ever jailbroken/unlocked. even on apple's support page it says that the 1604 errors can happen. just kind of played dumb and it all worked out.
    http://support.apple.com/kb/TS1275
     
  11. sonystyle macrumors newbie

    Joined:
    Aug 10, 2008
    #11
    Hey... Does anyone found any solution for this error?
    It's 3 days now that I stock in this error... I tried pwange 2.0 & 2.0.1 and created custom firmwares by using each one of them, but no luck to restore it with itunes.
    I have 2G iPhone which was working on 1.1.4 & yes I now how to put the iphone in DFU mode!! but I still get the 1604 error...

    tried more than 10 macs and 2PCs without any luck!!

    Plz... gimme a solution... :(
     
  12. adamerr macrumors 6502a

    adamerr

    Joined:
    Jun 7, 2008
    #12
    put your phone in DFU, then restore using iTunes (not custom firmware)

    then try and pwn it again.
     
  13. sonystyle macrumors newbie

    Joined:
    Aug 10, 2008
    #13
    Already tried it... many times... with 1.1.4 / 2.0 / 2.0.1 (all original firmwares)!! no luck at all! :(

    Any other idea?? :confused:
     
  14. illidian macrumors 6502

    Joined:
    Mar 27, 2008
    Location:
    Cincinnati, OH
    #15
  15. sonystyle macrumors newbie

    Joined:
    Aug 10, 2008
    #16
    WOOOOOOOOOOOOOOOOOOHOOOOOOOOOOOOOOOO!!
    It's recovered!! I can't believe my eyes!! :p
    A million thanx!! you're the man!! :eek:

    I tried to follow the instructions of the link, but i couldnt get it out of recovery mode! ziphone didnt work! it says successfully on normal mode, but the iPhone is still in recovery mode!
    Any advise?:rolleyes:





    p.s: THANX AGAIN! U SAVED MY LIFE!! :D
     
  16. Cattywampus_ macrumors 6502a

    Joined:
    Apr 19, 2006
    #17
    Er not sure.

    When I did followed it it kicked out of DFU after downgrading the bootloader into recovery mode then I could update the firmware using pwned 2.0
     
  17. sonystyle macrumors newbie

    Joined:
    Aug 10, 2008
    #18
    I used iLiberty+ too activate it, and it got me out of the restore mode also...
    I used Ziphone to Activate+JB+Unlock! :D

    Then I tired pwange tool again to make another custom 2.0.1 and this time it was successfull!! Now I have e 2.0.1 Unlock 2G iPhone! :D:D

    Thanx again man... I really owe you! ;)
     
  18. theevilone macrumors member

    Joined:
    Mar 12, 2008
    #19
    Problem: I am in DFU mode and I just get error 1604, 1602, 1601 (some 160x). I am pulling my hair out! What do I do?!
    Solution: This one sucks. There’s no single answer for it. Here are some possible suggestions:

    Validate you are using the correct firmware. You can get this if you are using an incompatible firmware (3g for 2g for example).
    Restart your computer and try again.
    Try another computer
    Try switching USB ports
    Uninstall and reinstall iTunes 7.7
     
  19. sonystyle macrumors newbie

    Joined:
    Aug 10, 2008
    #20
    If u have 2G iPhone, try to restore the original 1.1.4 with iTunes 7.5! (DFU Mode)
    It worked for me! ;)
     
  20. theevilone macrumors member

    Joined:
    Mar 12, 2008
    #21
    I am not having problems. That's a possible solution to the problem people have upgrading to 2.0.1.

    people upgrading sometimes use the wrong firmware and get the 1604 error.
     

Share This Page