After releasing PwnageTool 2.2.5 and QuickPwn 2.2.5 for iPhone firmware 2.2.1 for Mac users earlier in the day, the iPhone Dev team has just released QuickPwn 2.2.5-2 for Windows users.
The QuickPwn tool can be used to jailbreak and unlock 1st Gen iPhone and only jailbreak iPhone 3G. But using QuickPwn or the upgrading to iPhone Firmware 2.2.1 from iTunes will re-lock your iPhone 3G. So iPhone 3G users should use QuickPwn 2.2.5-2 if you DON'T care about unlocking and want to ONLY jailbreak your iPhone 3G.
Before you use QuickPwn 2.2.5 for Windows, its very important that you read the following points highlighted by the Dev team (till you are absolutely clear):
- GOLDEN RULE: If you have a 3G iPhone running 2.2 firmware and you want to keep your ability to use yellowns0w (or the option to use it in the future) do NOT use QuickPwn, and do not use the official ipsw or the iTunes update process without using PwnageTool.
- Yellowsn0w will NOT work with the baseband version (02.30.03) that is present in the recent 2.2.1 update. If you want to use Yellownsn0w you will need to create and restore using a custom .ipsw that will allow you to update safely to 2.2.1 without applying the 02.30.03 baseband update. You’ll then have a 3G iPhone running 2.2.1 with an older baseband version that is still vulnerable to yellowsn0w, following these steps ensures that yellowsn0w will still operate.
- The Yellowsn0w version has been updated to 0.9.7. Yellowsn0w is available from Cydia or Installer – this version allows compatibility with pwned 2.2.1 system (not baseband). Again remember 0.9.7 yellowsn0w DOES NOT WORK WITH 2.2.1 (02.30.03) directly – you need to be running a ‘pwned’ version of 2.2.1 which didn’t upgrade the baseband during the restore/upgrade.
Here are some more instructions based on the type of iPhone user:
This applies if you bought your iPhone 3G for $$$$$$$. This
model of iPhone 3G doesn’t have an Service Provider lock (aka factory
unlocked) and you are able to put any SIM card into the phone and get
service. Your phone is already unlocked so you do not need to worry
about baseband updates, simply upgrade to 2.2.1 using iTunes and then
use QuickPwn to Pwn and Jailbreak. This will add Cydia and Installer
Locked iPhone 3G – Preserve Baseband
applies if you have a locked iPhone 3G and you wish to update to 2.2.1
but preserve the iPhone’s current baseband software. Preserving the
baseband will ensure that you can still use “yellowsn0w” the iPhone 3G
unlock application. To upgrade your phone to 2.2.1 and preserve the
state of the baseband you need to create a custom .ipsw with
PwnageTool. This custom .ipsw will not contain the baseband update but
of course will still give you any new stuff from 2.2.1. However PwnageTool is only available for Mac, so you will need to get the custom iPhone firmware created by your friend or you should use your friends Mac to create the custom firmware.
Please DO not use QuickPwn if you want to unlock your iPhone 3G.
Locked iPhone 3G
If you are using your iPhone with one carrier and have no interest
in the possibility of an iPhone 3G unlock in the near future then just
restore or upgrade to 2.2.1 using iTunes and use QuickPwn to Jailbreak
and add Cydia and Installer.
iPhone 2G (1st Generation)
Update or Restore your iPhone 2G with iTunes then run QuickPwn to do
the magic, ‘nuff said, you don’t need to worry about anything.
Please remember that hacking your iPhone could void its warranty, so proceed with caution and at your own risk.
If you DON'T want to unlock your iPhone 3G (now or anytime in the future) but just want to jailbreak it then you can download QuickPwn 2.2.5-2 for Windows using this Bittorrent link.
If you have the 1st Gen iPhone running firmware 2.2.1 then you can download QuickPwn 2.2.5-2 to jailbreak and unlock it using the Bittorrent link mentioned above.
Update (Feb 1, 2009):
Dev Team has published some more direct download links which you can use in case you are having trouble with the Bittorrent link.
As always, please let us know how it goes in the comments.
Thanks Dr Puttingham and chris for the tip!
[via Dev Team's blog]