iphone cannot be restored...

Discussion in 'iPhone Tips, Help and Troubleshooting' started by pokemon1111, Oct 6, 2010.

  1. pokemon1111 macrumors newbie

    Joined:
    Oct 6, 2010
    #1
    i was using iphone 3G 4.1 with snowbreeze 2.0.2 jailbreak
    suddenly it cannot be switched on...
    it just shows few seconds of snow icon when it was connected to the power supply. in other occasions it did not give me any response.
    i tried to connect it to the computer and entered dfu mode (i suppose) itunes said it is in recovery mode though...
    when i try to recover. it got a timeout error when up to the process "preparing iphone to be restored"
    error code 1601

    the following is the log..


    2010-10-06 18:32:39.816 [5164:1754]: restore library built Aug 6 2010 at 11:14:46
    2010-10-06 18:32:39.816 [5164:1754]: iTunes: iTunes 10.0.1.22
    2010-10-06 18:32:39.816 [5164:1754]: iTunes: Software payload version: 8B117
    2010-10-06 18:33:08.756 [5164:968]: iTunes: Specifying UOI boot image
    2010-10-06 18:33:08.759 [5164:968]: requested restore behavior: Erase
    2010-10-06 18:33:08.823 [5164:968]: amai: AMAuthInstallPlatformCreateDataFromFileURL: can't resolve file
    2010-10-06 18:33:08.837 [5164:968]: amai: AMAuthInstallDebugWriteObject: debug object written: C:\Users\User\AppData\Local\Temp\Per67C9.tmp\amai\debug\tss-request.plist
    2010-10-06 18:33:35.582 [5164:968]: amai: AMAuthInstallRequestSendSync: received tss response (server version: 0.6.30-b2)
    2010-10-06 18:33:35.583 [5164:968]: amai: AMAuthInstallDebugWriteObject: debug object written: C:\Users\User\AppData\Local\Temp\Per67C9.tmp\amai\debug\tss-response.plist
    2010-10-06 18:33:36.025 [5164:98c]: <DFU Device 10607118>: production fused device
    2010-10-06 18:33:36.025 [5164:98c]: unable to open device_map.txt: No such file or directory
    2010-10-06 18:33:36.026 [5164:98c]: WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#5d574ad2
    2010-10-06 18:33:36.026 [5164:98c]: WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#5d574ad2
    2010-10-06 18:33:36.031 [5164:98c]: <DFU Device 10607118>: operation 0 progress 1
    2010-10-06 18:33:36.035 [5164:98c]: <DFU Device 10607118>: operation 0 progress 3
    2010-10-06 18:33:36.039 [5164:98c]: <DFU Device 10607118>: operation 0 progress 5
    2010-10-06 18:33:36.043 [5164:98c]: <DFU Device 10607118>: operation 0 progress 7
    2010-10-06 18:33:36.047 [5164:98c]: <DFU Device 10607118>: operation 0 progress 9
    2010-10-06 18:33:36.054 [5164:98c]: <DFU Device 10607118>: operation 0 progress 11
    2010-10-06 18:33:36.058 [5164:98c]: <DFU Device 10607118>: operation 0 progress 13
    2010-10-06 18:33:36.062 [5164:98c]: <DFU Device 10607118>: operation 0 progress 15
    2010-10-06 18:33:36.067 [5164:98c]: <DFU Device 10607118>: operation 0 progress 17
    2010-10-06 18:33:36.071 [5164:98c]: <DFU Device 10607118>: operation 0 progress 19
    2010-10-06 18:33:36.075 [5164:98c]: <DFU Device 10607118>: operation 0 progress 21
    2010-10-06 18:33:36.079 [5164:98c]: <DFU Device 10607118>: operation 0 progress 23
    2010-10-06 18:33:36.083 [5164:98c]: <DFU Device 10607118>: operation 0 progress 25
    2010-10-06 18:33:36.087 [5164:98c]: <DFU Device 10607118>: operation 0 progress 27
    2010-10-06 18:33:36.091 [5164:98c]: <DFU Device 10607118>: operation 0 progress 29
    2010-10-06 18:33:36.095 [5164:98c]: <DFU Device 10607118>: operation 0 progress 31
    2010-10-06 18:33:36.099 [5164:98c]: <DFU Device 10607118>: operation 0 progress 33
    2010-10-06 18:33:36.103 [5164:98c]: <DFU Device 10607118>: operation 0 progress 35
    2010-10-06 18:33:36.107 [5164:98c]: <DFU Device 10607118>: operation 0 progress 37
    2010-10-06 18:33:36.111 [5164:98c]: <DFU Device 10607118>: operation 0 progress 39
    2010-10-06 18:33:36.115 [5164:98c]: <DFU Device 10607118>: operation 0 progress 41
    2010-10-06 18:33:36.119 [5164:98c]: <DFU Device 10607118>: operation 0 progress 43
    2010-10-06 18:33:36.123 [5164:98c]: <DFU Device 10607118>: operation 0 progress 44
    2010-10-06 18:33:36.127 [5164:98c]: <DFU Device 10607118>: operation 0 progress 46
    2010-10-06 18:33:36.131 [5164:98c]: <DFU Device 10607118>: operation 0 progress 48
    2010-10-06 18:33:36.135 [5164:98c]: <DFU Device 10607118>: operation 0 progress 50
    2010-10-06 18:33:36.139 [5164:98c]: <DFU Device 10607118>: operation 0 progress 52
    2010-10-06 18:33:36.143 [5164:98c]: <DFU Device 10607118>: operation 0 progress 54
    2010-10-06 18:33:36.147 [5164:98c]: <DFU Device 10607118>: operation 0 progress 56
    2010-10-06 18:33:36.151 [5164:98c]: <DFU Device 10607118>: operation 0 progress 58
    2010-10-06 18:33:36.155 [5164:98c]: <DFU Device 10607118>: operation 0 progress 60
    2010-10-06 18:33:36.159 [5164:98c]: <DFU Device 10607118>: operation 0 progress 62
    2010-10-06 18:33:36.163 [5164:98c]: <DFU Device 10607118>: operation 0 progress 64
    2010-10-06 18:33:36.168 [5164:98c]: <DFU Device 10607118>: operation 0 progress 66
    2010-10-06 18:33:36.172 [5164:98c]: <DFU Device 10607118>: operation 0 progress 68
    2010-10-06 18:33:36.176 [5164:98c]: <DFU Device 10607118>: operation 0 progress 70
    2010-10-06 18:33:36.181 [5164:98c]: <DFU Device 10607118>: operation 0 progress 72
    2010-10-06 18:33:36.185 [5164:98c]: <DFU Device 10607118>: operation 0 progress 74
    2010-10-06 18:33:36.189 [5164:98c]: <DFU Device 10607118>: operation 0 progress 76
    2010-10-06 18:33:36.193 [5164:98c]: <DFU Device 10607118>: operation 0 progress 78
    2010-10-06 18:33:36.197 [5164:98c]: <DFU Device 10607118>: operation 0 progress 80
    2010-10-06 18:33:36.201 [5164:98c]: <DFU Device 10607118>: operation 0 progress 82
    2010-10-06 18:33:36.205 [5164:98c]: <DFU Device 10607118>: operation 0 progress 84
    2010-10-06 18:33:36.209 [5164:98c]: <DFU Device 10607118>: operation 0 progress 86
    2010-10-06 18:33:36.213 [5164:98c]: <DFU Device 10607118>: operation 0 progress 87
    2010-10-06 18:33:36.217 [5164:98c]: <DFU Device 10607118>: operation 0 progress 89
    2010-10-06 18:33:36.221 [5164:98c]: <DFU Device 10607118>: operation 0 progress 91
    2010-10-06 18:33:36.225 [5164:98c]: <DFU Device 10607118>: operation 0 progress 93
    2010-10-06 18:33:36.229 [5164:98c]: <DFU Device 10607118>: operation 0 progress 95
    2010-10-06 18:33:36.233 [5164:98c]: <DFU Device 10607118>: operation 0 progress 97
    2010-10-06 18:33:36.237 [5164:98c]: <DFU Device 10607118>: operation 0 progress 99
    2010-10-06 18:33:36.237 [5164:98c]: WinDFU::UploadData: EOF, cbRead: 296
    2010-10-06 18:33:36.239 [5164:98c]: <DFU Device 10607118>: operation 0 progress 100
    2010-10-06 18:33:36.239 [5164:98c]: WinDFU::UploadData: ZLP
    2010-10-06 18:33:36.240 [5164:98c]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
    2010-10-06 18:33:36.240 [5164:98c]: WinDFU::processUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
    2010-10-06 18:33:36.240 [5164:98c]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
    2010-10-06 18:33:36.240 [5164:98c]: WinDFU::processUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
    2010-10-06 18:33:39.240 [5164:98c]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
    2010-10-06 18:33:39.240 [5164:98c]: WinDFU::processUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
    2010-10-06 18:33:39.240 [5164:98c]: WinDFU::ResetDevice: resetting...
    2010-10-06 18:33:39.306 [5164:98c]: WinDFU::FinalizeDfuUpdate: success
    2010-10-06 18:33:39.306 [5164:98c]: <DFU Device 10607118>: DFU succeeded
    2010-10-06 18:33:39.348 [5164:1540]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#5d574ad2
    2010-10-06 18:33:39.351 [5164:1540]: WinAMRestore::processDevNodesChanges: device: 0x077d03e8, notify: 2, connected: 0
    2010-10-06 18:33:39.351 [5164:1540]: WinAMRestore::processDevNodesChanges: device: 0x077d0a28, notify: 2, connected: 1
    2010-10-06 18:33:39.351 [5164:1540]: AppleDevice::NotifyDisconnect: DFU \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#5d574ad2, inst: 0x77d0a28
    2010-10-06 18:33:39.351 [5164:1540]: _AMDFUModeDeviceFinalize: 10607118
    2010-10-06 18:37:39.484 [5164:1754]: iTunes: Restore error 1601

    is that a hardware problem?
     
  2. aquaben1988 macrumors newbie

    aquaben1988

    Joined:
    Oct 5, 2010
    #2
    first thing, migth seem stupid but ive had it work for a freind of mine

    take out sim card try to recover that way (whats to recover you might say? but just try it) this should recover the cash on your phone/restore original settings (you can reinstal jailbreak after if you want)
    another thing you could try first if you want is to recover it again while having no apps on your computer on at all. no internet no nothing.

    Another thing try updating firmware on your phone (throught the usb) and see if that helps any. if it doesn t work throught normal update try it through DFU and update the firmware again.

    Or last thing you could do is

    Step 1 for Mac users) Navigate to the folder ~Library/iTunes/Device Support ... For the new Mac users among us, remember that the "~" designates that you start in your home (i.e., yourname) folder on your Mac rather than the several other places where a "Library" folder exists.
    Alternate Step 1 for Windows users) Navigate to this subdirectory:
    CDocuments and Settings\All Users\Application Data\Apple Computer\iTunes\
    2) Delete this file: x12220000_4_Recovery.ipsw
    3) Run the PwnageTool application. (I used PwnageTool 2.0.2 on the Mac.) Yes, I already had a usable custom firmware file I had made before, but I was doing it again because the process also dutifully recreates the file I deleted in Step 2 when it can't find it there.
    4) This is important: In my case, when Pwnage asked me at the end whether I had ever pwn'd my iPhone before (whether I'd seen the pineapple, etc.), rather than click "YES," I clicked "NO." In other words, click "NO" as if this was the first time you've pwn'd your phone.
    5) Finish out the pwn'ing by following the prompts in PwnageTool to put your phone in recovery mode, etc.. Then within iTunes, option-restore with the new custom firmware you created.

    The phone should be restored without the dreaded error. I hope this works for you as well.

    if this doesn t help sorry
     
  3. pokemon1111 thread starter macrumors newbie

    Joined:
    Oct 6, 2010
    #3
    thanks for your help
    what if i am using windows 7..?
    and actually i simply don't want any jb now..i just want my phone to be usable again
    i have no phone to use for 2 days already....
     
  4. aquaben1988 macrumors newbie

    aquaben1988

    Joined:
    Oct 5, 2010
    #4
    first option can be done the same way you tried before just remove the sim card, doesn t matter if you have windows 7.

    2nd option same thing, just make sure your computer is not runnign anything else but what you are using to restore your phone (i use task manager to find out)

    3rd option

    the folder should still be there so you should be able to look at it. If it is not reinstall your itunes and try step 1 then step 2 then see if you can locate the folder C: Documents and Settings\All Users\Application Data\Apple Computer\iTunes\

    it should not matter if your running windows ME or windows 7 it should work and if it does not I apolgise it is all i could think of
     

Share This Page