iOS 3.1 probably bricked - need help

Discussion in 'iOS Jailbreak & Cydia' started by mnk1, Jun 1, 2010.

  1. mnk1

    mnk1 New Member

    Joined:
    Jun 1, 2010
    Messages:
    10
    Likes Received:
    0
    so, i've had my iPhone 3GS (on 3.1.2) for about a month now, and jailbroke it with blackra1n the day i purchased it.

    while walking to school i pressed pause on my headphones to listen to someone talking to me.
    pressed play 2 minutes later and nothing happened...
    pulled the iPhone out my pocket to find that all the buttons were unresponsive - bar the power/lock button which switched on my iPhone leaving it on the recovery mode screen (usb cable -> iTunes logo)

    iTunes restore won't restore my iPhone - error 1603
    iTunes DFU restore won't restore my iPhone - error 1604
    blackra1n make it ra1n won't restore my iPhone

    and i'm hesitant to bring it to the Apple store considering that it's jailbroken (and hence out of warranty? correct me if i'm wrong), becaue i'm worried they won't fix it because it's jailbroken

    any help would be much appreciated

    Please Register or Log in to view images



    ta

    edit: using blackra1n will put the iPhone on the boy's face screen, but it won't reboot after this, just switch off...
  2. Nburnes

    Nburnes Well-Known Member

    Joined:
    Jan 3, 2009
    Messages:
    9,022
    Likes Received:
    767
    Device:
    OnePlus One
    Positive you are doing DFU correctly?
  3. b-mac 39

    b-mac 39 Well-Known Member

    Joined:
    Dec 15, 2009
    Messages:
    5,809
    Likes Received:
    60
    Device:
    iPhone 4S (White)
    When you get the 1604 error in iTunes, run iRecovery to boot. Your firmware is on the iPod, iTunes just isn't letting you use it. If you run iRecovery, you will boot as normal. After that, restore and use Spirit so you can automatically reboot.
  4. mnk1

    mnk1 New Member

    Joined:
    Jun 1, 2010
    Messages:
    10
    Likes Received:
    0
    positive i'm doing DFU correctly.. i had some trouble entering DFU mode but i succesfully did it about 20 minutes ago and that's when i first encountered error 1604
    before that i only got error 1603

    i'll try iRecovery now
  5. b-mac 39

    b-mac 39 Well-Known Member

    Joined:
    Dec 15, 2009
    Messages:
    5,809
    Likes Received:
    60
    Device:
    iPhone 4S (White)
    DFU didn't matter in this case. He can just use iRecovery to boot and he is done. Since he is on blackra1n and not Spirit, he might have to boot with iRecovery and then reboot with blackra1n.
  6. mnk1

    mnk1 New Member

    Joined:
    Jun 1, 2010
    Messages:
    10
    Likes Received:
    0
    all the tutorials for running iRecovery say you type

    iRecovery -s

    to execute the program
    i just get

    iRecovery is not recognised as...

    running windows 7 64 bit.

    edit: double clicking the file iRecovery opens it for a fraction of a second, much like opening other things in cmd
  7. xXrkidXx

    xXrkidXx Well-Known Member

    Joined:
    Mar 27, 2009
    Messages:
    4,594
    Likes Received:
    129
    Device:
    iPhone 5 (Black)
    Get iREB and use Recovery Mode Fixer. It will make you install LIBUSB but it will do the same thing iRecovery does, just a GUI.
  8. mnk1

    mnk1 New Member

    Joined:
    Jun 1, 2010
    Messages:
    10
    Likes Received:
    0
    okay, iREB appeared to do nothing..

    after fiddling with iREB and DFU mode

    blackra1n'ing still results in turning the phone off
    restore comes back with a 1603 error
    and DFU restore comes back with a 1604 error
  9. Jarlath

    Jarlath Retired Moderator

    Joined:
    Mar 21, 2008
    Messages:
    2,321
    Likes Received:
    0
    Try another computer - 1604 means the computer can't talk with the device for some reason, which usually means driver issues (that involve a reinstall of AppleMobileDeviceDriver). Sometimes even just restarting the computer fixes it.
  10. mnk1

    mnk1 New Member

    Joined:
    Jun 1, 2010
    Messages:
    10
    Likes Received:
    0
    i tried it on my brother's PC and got the same error..

    tried both normal restore and DFU mode

Share This Page