Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

OFFICIAL: iPhone Pwnage 2.0 ---> Brickage 2.0 Thread

A

Altimeter88

macrumors member
Original poster
Jul 17, 2006
99
0
This thread is ONLY for people who (most likely due to user error) have bricked their iphones using the new Pwnage utility and hopefully we can get them working again. It is NOT for instructions on how to use the app.

Please follow this format as in my case:

BEFORE Pwnage 2.0:
-iPhone 1Gen
-1.1.4 Jailbroken (not unlocked) w/iLiberty
-upgraded to 2.0 via iTunes
-iPhone not Activated

Pwnage 2.0 (what steps you took to get into the bricked state your in now):
-Simple mode, went smooth, jailbroken but not unlocked (no boot neuter)
-Everything appeared fine but I realized the phone was NOT unlocked, needed it unlocked to sell, so I ran again in 'Expert Mode', I think I UNchecked 'Disable partition wipe-out', not exactly sure on the bootneauter options.

WHAT HAPPENED:
-Everything seemed to update fine until bootloader started running, it said it would take about 2min but after about 15 I figured it was frozen so I rebooted. Now I just get the icon of the guy speaking russian telling me my phone needs to be restored.

I have tried using iTunes to restore new pwnage packages I made in both simple and expert modes, I have also tried using the default iTunes 2.0 firmware to "restore and update" but during the restore process iTunes always comes up with the "Preparing to Restore" window, and after about 3-4 min I get the unknown error 1604.

I think my problem was rebooting during the partition wipe-out. So if anyone has any solutions or things to try let me know. Also if you have similar stories to share please do.
 
My story:
- Jailbroken & unlocked iPhone 1.1.2 (BL 3.9), using Leopard 10.5.4

- Had some trouble with pwnagetool DFU-stuff (just said 'U FAIL' without DFU instructions) so went to DFU myself
- Tried to update to pwnaged 2.0 firmware, failed (iTunes 1600)
- Tried to restore 1.1.2, got iTunes 1601
- Now the iPhone won't show up in iTunes, iNdependence or ziphone.

It's like it's stuck with DFU on but the USB-stuff is somehow crooked. Since it won't respond to any input or show up as a device, I could say it's properly bricked :D

EDIT: somehow pressing power and home randomly while plugging/unplugging the cable kicked it out of the mode. All is well now.
 
I got stuck in DFU as well. :[
I have an iPhone first gen, Mac is running Leopard 10.6.1, PC is XP Tablet Version.

Steps taken:
(On my Mac) Started Pwnage 2.0, everything went well.
Then I use my PC because the USB ports for my Mac don't work. Dragged the .ipsw file on my network from Mac to PC. Successfully saved.
(On my PC) Recovery Mode: Installation went all smooth. Expect to reboot and load up.

Then when it reboots, the apple logo shows up for a few seconds, then reboots itself again and again and again.

So I turned it back to Recovery Mode, restored it again, same results.
Then I switched it off and went into DFU mode, and I tried to restore it, it loads in "Preparing for an iPhone restore..." for a few minutes. Then 1601 pops up. (Sometimes it's 1602 or 1604 when I switched to another port)

Any ideas? Please help me :[
 
tabakishinado said:
I got stuck in DFU as well. :[
I have an iPhone first gen, Mac is running Leopard 10.6.1, PC is XP Tablet Version.

Steps taken:
(On my Mac) Started Pwnage 2.0, everything went well.
Then I use my PC because the USB ports for my Mac don't work. Dragged the .ipsw file on my network from Mac to PC. Successfully saved.
(On my PC) Recovery Mode: Installation went all smooth. Expect to reboot and load up.

Then when it reboots, the apple logo shows up for a few seconds, then reboots itself again and again and again.

So I turned it back to Recovery Mode, restored it again, same results.
Then I switched it off and went into DFU mode, and I tried to restore it, it loads in "Preparing for an iPhone restore..." for a few minutes. Then 1601 pops up. (Sometimes it's 1602 or 1604 when I switched to another port)

Any ideas? Please help me :[
Click to expand...

Well... You might wanna put the iPhone on DFU mode and then connect it to iTunes. Then hit the restore button. That should work. Otherwise I have no idea.. Just glad mine turn out good :)
 
Altimeter88 said:
This thread is ONLY for people who (most likely due to user error) have bricked their iphones using the new Pwnage utility and hopefully we can get them working again. It is NOT for instructions on how to use the app.

Please follow this format as in my case:

BEFORE Pwnage 2.0:
-iPhone 1Gen
-1.1.4 Jailbroken (not unlocked) w/iLiberty
-upgraded to 2.0 via iTunes
-iPhone not Activated

Pwnage 2.0 (what steps you took to get into the bricked state your in now):
-Simple mode, went smooth, jailbroken but not unlocked (no boot neuter)
-Everything appeared fine but I realized the phone was NOT unlocked, needed it unlocked to sell, so I ran again in 'Expert Mode', I think I UNchecked 'Disable partition wipe-out', not exactly sure on the bootneauter options.

WHAT HAPPENED:
-Everything seemed to update fine until bootloader started running, it said it would take about 2min but after about 15 I figured it was frozen so I rebooted. Now I just get the icon of the guy speaking russian telling me my phone needs to be restored.

I have tried using iTunes to restore new pwnage packages I made in both simple and expert modes, I have also tried using the default iTunes 2.0 firmware to "restore and update" but during the restore process iTunes always comes up with the "Preparing to Restore" window, and after about 3-4 min I get the unknown error 1604.

I think my problem was rebooting during the partition wipe-out. So if anyone has any solutions or things to try let me know. Also if you have similar stories to share please do.
Click to expand...

Always stay away from expert mode if you don't know what ya doing!
 
iBookfan said:
Well... You might wanna put the iPhone on DFU mode and then connect it to iTunes. Then hit the restore button. That should work. Otherwise I have no idea.. Just glad mine turn out good :)
Click to expand...

I did made it into DFU mode, and then when I tried to restore it, it kept on staying in "Preparing iPhone for restore" for a few minutes, then an error (usually 1601, sometimes 1602 or 1604) pops up. :(
 
tabakishinado said:
I did made it into DFU mode, and then when I tried to restore it, it kept on staying in "Preparing iPhone for restore" for a few minutes, then an error (usually 1601, sometimes 1602 or 1604) pops up. :(
Click to expand...

Do you select the custom firmware or the one from Apple?
 
lol well i was trying to update to 2.0 clicked the wrong firware and now im unlocked and bricked or w.e on 2.0 ,iphone telling me to connect to itunes, cannot get into dfu mode uh oh
 
I have a 2G iphone that was unlocked until I (stupidly) tried to upgrade to 2.0 last week. I could not downgrade (2.0 to 1.1.4) using the standard tutorials online, nor could i use the new pnwage 2.0.

I have discovered ht reason why is that i cannot get into DFU mode. I think that my sleep/wake button is messed, because when I start the restore with iTunes 7.7 and the phone is in 'emergency call' mode i cannot turn it off.

Is there any other way i can enter DFU or turn this thing off!!!

Thanks in advance,
cez
 
tabakishinado said:
I did made it into DFU mode, and then when I tried to restore it, it kept on staying in "Preparing iPhone for restore" for a few minutes, then an error (usually 1601, sometimes 1602 or 1604) pops up. :(
Click to expand...

Did you try upgrading to official firmware 2.0 first and then using the pwned version?
 
tabakishinado said:
yes. i did.
it still went on the "preparing iphone for restore" thing for a few minutes then comes up with 1601 error.
Click to expand...

tabakishinado said:
I did made it into DFU mode, and then when I tried to restore it, it kept on staying in "Preparing iPhone for restore" for a few minutes, then an error (usually 1601, sometimes 1602 or 1604) pops up. :(
Click to expand...

tabakishinado said:
I got stuck in DFU as well. :[
....
Then I switched it off and went into DFU mode, and I tried to restore it, it loads in "Preparing for an iPhone restore..." for a few minutes. Then 1601 pops up. (Sometimes it's 1602 or 1604 when I switched to another port)

Any ideas? Please help me :[
Click to expand...

designed said:
My story:
- Jailbroken & unlocked iPhone 1.1.2 (BL 3.9), using Leopard 10.5.4

- Had some trouble with pwnagetool DFU-stuff (just said 'U FAIL' without DFU instructions) so went to DFU myself
- Tried to update to pwnaged 2.0 firmware, failed (iTunes 1600)
- Tried to restore 1.1.2, got iTunes 1601
- Now the iPhone won't show up in iTunes, iNdependence or ziphone.

....
Click to expand...

I haven't tried this, so no promises....

Apparently, if you get Error 16## from iTunes try creating a brand new ~/Library/iTunes/Device Support

If that directory already exists, remove it and any files in it first. Then re-run PwnageTool.

A few people elsewhere have reported success with this. Then, the following instructions workd for me to go back to 1.1.4

https://forums.macrumors.com/showthread.php?p=5790279#post5790279

Andy
 
Mine was on 1.1.4 Pwned, unlocked and Jailbroken.

Created a custom firmware using the new tool and went into iTunes and done a restore, took ages and when it finally rebooted it now says "Invalid Sim" in iTunes.

Dave
 
andyhargreaves said:
I haven't tried this, so no promises....

Apparently, if you get Error 16## from iTunes try creating a brand new ~/Library/iTunes/Device Support

If that directory already exists, remove it and any files in it first. Then re-run PwnageTool.

A few people elsewhere have reported success with this. Then, the following instructions workd for me to go back to 1.1.4

https://forums.macrumors.com/showthread.php?p=5790279#post5790279

Andy
Click to expand...

Well... I tried your method, and now it showed some progress! w00t.
so yeah. I did what you said, strictly follow the steps PwnageTool said, and then yays! It has iphone 2.0 in it but it went back to the "keep on restarting" thing. Not so a big success but at least it went back to step 1 lol.

so that's my current status (i think)
iphone 2.0 installed successfully, but kept on restarting when boots up. the apple logo shows for approx 7-8 seconds before it restarts and appears again.
 
Think my problem is am not restoring the right firmware, trouble is I can not get Itunes to prompt me to pick a file during restore. I have tried all sorts of key combinations when clicking Restore (incl Shift).

Dave
 
Dave B said:
Think my problem is am not restoring the right firmware, trouble is I can not get Itunes to prompt me to pick a file during restore. I have tried all sorts of key combinations when clicking Restore (incl Shift).

Dave
Click to expand...

if you have Mac, it's option/command+click
osx86 is the alt key
windows is shift
 
Have any of you tried the downgrade instructions to go from 2.0 to 1.1.4? I think that might solve some of your problems...it's almost like some of you had bad bootloaders.
 
Updates on my phone:
After the restarting incident happen again, I booted into Recover Mode and restored it with the original 2.0 firmwire and voila! a fully functional iphone 2.0, but not unlocked, possibly (or definitely) not jailbroken. So right now I'm stuck. Any advice?
 
I unlocked my phone using Pwnage 2.0. Worked sucessfully too. Tested with my t-mobile sim card and it works.

Too bad the AIM client is still crap.
 
Jailbroke my 3G iPhone successfully and now I have no service whatsoever. Help please.
 
I have updated the pwnage tool guide and FAQ for 2.0.

Please direct any questions into that thread and I will answer and help anyone I can.

Hopefully it will be re-pinned so its easy to find at the top of the thread.

I have updated the intructions and I still have to include advanced instructions and add solutions to problems to the thread.
 
Just an update, I got my phone unbricked.

I used a windows laptop I had to downgrade itunes to 7.5, put it in DFU mode and put 1.1.4 back on it.
Then I used winpwn to pwn it.
Then I hooked it to my Mac Pro and ran Pwnage 2.0 (simple mode) and everything came back OK.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back