PwnageTool 2.0.2 To Be Released Today
by Eric March on August 7, 2008 at 9:19 am
For those of you who have been holding off on updating to the latest 2.0.1 firmware due to the lack of a jailbreak — or even for those of you who have updated and don’t mind doing it again for a proper jailbreal — prepare to get your download on. According to the Dev Team, “PwnageTool 2.0.2 is undergoing final checks and will be packaged,
signed and should be uploaded within the next few hours, so count on it
being released sometime on Thursday. This will be available via the
PwnageTool software updater that is built in and checked when you start
PwnageTool, we’ll also publish a link here for direct downloads.”
Naturally we’ll also provide the direct link here for those of you who don’t already have previous versions of Pwnage to update, or who simply want the full installation package. Two things to note: First, this is not an unlock for the 3G. They’re still working on that, so for now PwnageTool is still strictly for jailbreaking 3Gs. First-gen iPhone users, including those who have upated to 2.0 can still unlock, but first-gen iPhone owners who have upgraded to firmware 2.0.1 will no longer be able to unlock, because Apple have updated the baseband again; not even a restore back to 2.0 will help, because you’ll still have the newer baseband.
Second, and as usual this is only for Mac; we Windows users still have to wait for cmw to finish WinPwn 2.5, which will presumably incorporate PwnageTool 2.0.2 when it does finally get released; the last WinPwn blog entry is dated July 31st, which means he hasn’t posted daily build screenies like he wanted to — but could also mean he’s been hard at work and hopefully close to a release. We can plz has WinPwn soon?
(via iPhone Dev blog)

Posted in 











August 7th, 2008 at 7:27 pm
I want to jailbreak, but for me Winpwn has failed to create the new firmware across MULTIPLE systems. I just cannot build a firmware, which means I’m screwed for jailbreaking:(
August 7th, 2008 at 9:51 pm
It took me a while to figure it out too. Turns out the problem was that I just wasn’t entering DFU mode properly. Once I did that, everything went smooth as silk.