The newest version of Pwnage has been released, just under an hour ago. It supports the new 2.0.2 firmeware, which fixes a lot of the edge/3G issues.
PwnageTool 2.0.3 is now available as a Sparkle update, or a direct download. This version provides support for iPhone/iPod firmware 2.0.2 5C1, it has an updated Installer.app beta (b6) and contains a new .de localization for our large amount of German friends. The application SHOULD ONLY be downloaded as a .tbz file from our servers and should NOT be decompressed using the very broken application called "the unarchiver" stick to the standard OS X built in "Archive Utility" to decompress. The SHA1 sum of PwnageTool_2.0.3.tbz is 91e670e0c623cd43f5e8cfbfaae6c23d98d8f31b
We will update our tutorials shortly.
Add Comment
Would you like to be notified when someone replies or adds a new comment?
Yes (All Threads)
Yes (This Thread Only)
No
Notifications
Would you like to be notified when we post a new Apple news article or tutorial?
When having a look at reviews of the 2.0.2 firmware in terms of fixing EDGE/3G reception issues, on many websites the general consensus among users seems to be that it makes no difference at all - some even report it makes reception worse, though I don't know if that is possible, or just paranoia...
Surely to affect radio antenna reception quality in a positive OR negative way you must let iTunes upgrade the baseband version by updating 'officially'? However when using Pwnage Tool, the baseband remains intact at the older version and so only system software based issues will be resolved as the baseband will not be updated.
I'm still going to update to firmware 2.0.2 with Pwnage Tool 2.0.3 because I can, but I doubt it will alter my signal reception as the baseband will not be upgraded.
P.S. The scam website www.iphoneunlockuk.com is STILL stealing the Dev Team's work and Nullriver's Installer.app , even though they probably realised they've been found out!! It makes me furious that they're continuing to get away with it. Can't anyone shut this website down for good or let the Trading Standards agency in the Dev Team's local geographical region know whats going on...?