after it builds custom ipsw it crashes and leaves a 1kb file.
then when you try to pwn,it says "your itunes is being pwned" and crashes again.
any help? am I the only one?

If you can, try another computer

I had the same problems - winpwn crashing several times when I was trying to build the custom ipsw. I was running winpwn on a WindowsXP Home system, 500MB memory, with Microsoft .NET framework 2.0 service pack 1.

I was able to get this working after several attempts by turning off my antivirus software (Avira Antivir Personal), shutting down ALL other applications, and freeing up about 3 GB of space on the C: drive (up from only 1GB free when winpwn was crashing.

I'm not sure that the anti-virus software had anything to do with the problems I was having. I'm pretty sure that going from 1 GB to 3 GB of free disk was what allowed winpwn to successfully build the customer ipsw file.

I also had problems getting one of the two ("classic") iPhones that I pwn'ed on this system into DFU mode. Several times, I found that even with a black screen, the phone was only in recovery mode, and not DFU mode.

To be sure that the iPhone is really in DFU mode, I had to look in Control Panel ==> System ==> Hardware ==> Device Manager ==> Universal Serial Bus controllers. If you see your Apple device with "DFU" mentioned, then you are good to start your custom ipsw restore. When it said "Recovery mode" my restore attempts always ended with a 160* error message failure...

Good luck!

tom

The problem is that the program needs 300Mb of ram, which is very difficult to get with XP and a whole bunch of programms/services running in the backgroud. Shutting down some programs might just work, but the best way to do it is on a computer with atleast 1GB of RAM. It worked for me as soon as I increased the RAM memory. hope that helps

alright , mate.Gonna try soon