Guys, just a note, I've been hanging out on the OSX86 IRC channel for quite sometime now, and it looks like NO ONE there is even coming close to recommending the use of the current WinPwn release, as far as reliability and bugs are concerned. The creator by the name of cmw is currently asleep in his timezone and will get to work on the bugfixes in a couple of hours time.

Until then, it has been highly advised to not try the current release of WinPwn just yet. For Windows users, fret not, instead of WinPwn, I'd suggest trying xPwn 0.9.3 or xWinPwn 0.3 for the time being. I just used xPwn on mine and it worked out great. But beware, it's more command-line than GUI, so be prepared

Guys, the latest release of WinPwn, 2.0.0.3 has been said to fix many of the 160x errors you guys have been facing, as well as iPwner's problem getting into iTunes. If anyone here still has problems getting WinPwn to work, I would strongly advise trying xPwn 0.9.5 by geeb > DOWNLOAD HERE <.

It's a little more of a cross-platform command line utility compared to WinPwn and PwnageTool, but overall it doesn't have all the bugs and probems which still plague WinPwn, as I have personally experienced under a week ago, especially for those who are having problems packaging the custom IPSW. Remember to read both the HTML guide and README.txt before attempting anything.

Mind you, not necessarily In the first 2 releases, iPwner was bugged in the sense that it would either crash the app without getting into iTunes, or it wouldn't be able to copy the Pwn file into the iTunes AppData directory to allow the restoration of unsigned IPSW packages. Without these steps, errors 1601 and 1604 would strike during the restoring process which would mean that iTunes rejected the custom IPSW.

The whole definition of Pwning here is to not only package a custom firmware IPSW containing all the pre-packaged unlocks and exploits, but to also'Pwn' iTunes in order to get it to accept the custom IPSWs.

This post has been edited by Samanoske Akechi: Jul 26 2008, 05:39 PM

Sorry, Mike. I oversaw the question. Correct, Hussain. There would only be one reason that step is required there, but only if you've accidentally updated to the STOCK 2.0 firmware. Basically, the 2.0 firmware installs a new baseband, AKA 05.05.04_G. On 1.1.4, it was 04.04.05_G. Anyhow, bear in mind that this baseband has been successfully unlocked, which is why calls work on 2G iPhones already using this firmware unlike how it was with 1.1.2 where we had to retain the 1.1.1 baseband just to get it unlocked for calls. Basically, this all comes down to the way iTunes does a restore. During an upgrade from one firmware to another, iTunes first checks the baseband currently on the phone to see whether it's already been updated, and if the numbering matches the new baseband contained in the new IPSW whether or not it has been unlocked, iTunes will skip the baseband upgrade and jump straight into the software update. During a downgrade, iTunes will retain the newer baseband if it finds that the baseband in the IPSW being used is older.

What this means is, your iPhone's baseband is not restored or overwritten everytime you perform a Restore in iTunes, which is why in the days of AnySIM, we were only required to unlock our phone once, and wouldn't have to do it again even after restores of the SAME firmware. In the current scenario, PWNING requires the baseband along with the firmware to be PRE-unlocked and patched prior to restoring the phone. This means the stock 2.0 baseband (04.05.04_G) cannot be unlocked once installed, but instead has to be 'uninstalled' and reinstalled using the unlocked version. As fore mentioned, downgrading to 1.1.4 will NOT downgrade the baseband, but instead it will allow you to use Bootneuter to 'Neuter' your phone and downgrade the baseband for you back to 04.04.05_G. After doing that, restoring your phone using the custom package will allow iTunes to install the new, patched and unlocked 04.05.04_G baseband. And only then will your phone be unlocked.

Phew, I believe I've just spewed out more than a mouthful. If you're like me and were still on 1.1.4 without having accidentally upgraded to the stock 2.0 prior to the upgrade to 2.0, then you can just get straight to the Pwning and restoring using the custom package. Just include BootNeuter and the Neutering process in your custom package, no Neutering required before Pwning, I assure you Hopefully that clarifies things for you, Mike. All the best!

It depends on whether or not you've accidentally upgraded to the stock 2.0 firmware prior to this. If you have, then read my explanation above to understand why it's required. If not, just get straight to the Pwning and restoring too, mate! It's actually quite simple using PwnageTool/WinPwn, don't worry.

3rd party apps? Installer 4.0 is still on it's way, for now App Store has some pretty good games. Most of the good ones are paid apps, including Super Monkey Ball, Enigmo, Scrabble, Crash Team Racing etc. The free ones are not to be ashamed of either, like the all-new Tap Tap Revenge. Cydia hasn't quite made the cut with games yet, but you can rest assured that tonnes of 'em are on their way, just waiting to be ported over to 2.0 and released along with Installer 4.0 very soon!

Correction, the constant lag when browsing through stuff and especially tapping through menus is also a known bug in 2.0. Only occurs noticeably in certain areas like tapping on tabs and contacts for me, about 2 seconds delay. Keyboard on 2G iPhone is still fairing fine, so the lags are tolerable thus far. Hopefully 2.1 will fix this, fingers crossed!

This post has been edited by Samanoske Akechi: Jul 26 2008, 08:09 PM

Typical. Almost all apps crash on first run after install in 2.0. Try a reboot and resync. Just another 2.0 dilemma.

The length of the 1.1.4 restoration procedure depends on whether or not you've accidentally updated to the stock 2.0 firmware prior to this. Assuming you've only updated to the Pwned 2.0 package and want to revert to 1.1.4, your first step would be to either Pwn iTunes again to allow the 1.1.4 restore without having to downgrade back to iTunes 7.5, or to uninstall iTunes 7.7 and reinstall iTunes 7.5 manually. This is due to the fact that iTunes 7.7 doesn't allow the restoring of 1.1.4 and below firmwares, and Pwning iTunes would basically trick iTunes into accepting unsigned IPSW packages including 1.1.4 on iTunes 7.7 in this case After that, you will need to use BootNeuter to restore the baseband 04.04.04_G (1.1.4) because your iPhone would still be running the Pwned 04.05.04_G, which wouldn't work on 1.1.4. That's about it

The procedure using WinPwn requires nearly NO explanations whatsoever. Build custom IPSW, iPwner to Pwn iTunes, DFU your phone and restore away! Simple as that. And yes, the current firmware itself is the culprit behind all the crashes and lags we're experiencing thus far. Installer 4.0 will be out soon according to RIP DEV, screenies have already been released of the actual thing, which look pretty promising right now. The 2.1 firmware update which is claimed to bring turn-by-turn navigation in Maps on the iPhone 3G is also in Beta as we speak. Your time to update may come sooner than you think, mate

Relax, Uncle Back then I was in the 1.1.3 mess too, but back then it was the jailbreaking and unlocking which caused all the problems. Pwning the 2.0 firmware now is a breeze, it's just the 2.0 firmware itself that's messed up and buggy. But yeah, if you have the patience, might as well wait it out till the soon-to-come 2.1 update. Personally, Super Monkey ball was just too tempting to resist

In Cydia under the 'Utilities' category, you will find the same MakeItMine.app Install it and do as you please. Simpler to use now, with additional ability to change your banner where the time is displayed.

---

Added on July 27, 2008, 10:52 amRelax, it's completely normal. I would assume that iTunes currently displays the message "Preparing iPhone software for restore"? This particular process takes up to 10-15 minutes for some reason, but rest assured that what you're experiencing is not a cause for panic

This post has been edited by Samanoske Akechi: Jul 27 2008, 10:52 AM

Don't mix the usage of WinPwn's iPwner and xPwn, you might have missed a step or two. I assume, after running iPwner, you didn't perform the "dfu-util" procedure?

Yes, BossTool will be of no use to you on a regular basis.

Haha. Don't mention it, mate. Congrats to you for making the journey and coming out alive and well kai5814, I've already replied to your PM. To the rest of you guys, WinPwn's almost near perfection, with a lot lesser bugs and problems now than compared to the first release I tried, 2.0. Version 2.0.0.4's coming out soon to address more errors like error 6, 13 etc.

P.S. Mike, get on MSN. I have the 'goods'

No worries, mate. It's a good thing. What this means is that the DFU exploit has already been patched into your phone, AKA your phone has already been Pwned prior to the restore. Basically, if your phone has been Pwned before, future restores will no longer require that you put your phone into DFU mode, or even Pwning iTunes. Recovery Mode, as you have experienced, will work perfectly fine. However, this will only apply is you ONLY restore using Pwned IPSWs. Once you've restored using a stock firmware file, the Pwn will revert, and you'll have to do the DFU procedure again.

Hope that helps!

As mentioned a couple of times earlier, the lagging is completely normal The culprit behind isn't the apps installed, but the actual buggy 2.0 firmware itself. We'll have to bear with it until the 2.1 update is released, which'll hopefully address the lag and crashing issues.