PwnageTool 4.3.3 will allow iPhone users to safely restore to a pre-jailbroken iOS 4.3.3 firmware and retain their current baseband so that they can use Ultrasn0w to unlock their GSM iPhone, which is only useful for users with older baseband.
Dev Team has provided the following information on their blog:
… three in a row! Apple released iOS 4.3.3 on Wednesday, and once again the untethered jailbreak exploit that@i0n1c created for 4.3.1 still works. That makes it an unprecedented three firmwares where the same userland exploit works. We’re not exactly sure why Apple hasn’t fixed the hole yet, but we’re not complaining!
Today’s PwnageTool and redsn0w incorporate @i0n1c’s port to 4.3.3 (it’s ironic that such a long-lasting untether doesn’t even have an official name!). It also of course uses geohot’s limera1n bootrom exploit to inject the jailbreak.
Some things to note:
- ultrasn0w unlockers must stay away from redsn0w! Use only a custom IPSW to update to 4.3.3, to avoid updating your baseband.
- ultrasn0w has been updated to v1.2.3 to be compatible with iOS 4.3.3 and earlier (the ultrasn0w update does not include any new baseband support!). Please reboot your iPhone using the normal “slide to power off” swipe after installing ultrasn0w 1.2.3.
- By popular demand, redsn0w now allows you to enable multitasking gestures (although most will find it useful only on iPads).
PwnageTool 4.3.3 and Redsn0w 0.9.6rc15 supports the following iOS devices for iOS 4.3.3:
PwnageTool 4.3.3 and Redsn0w 0.9.6rc15 does not support iPad 2 or iOS 4.2.8. Dev Team has also provided the following update for iPad 2 users:
The iPad2 jailbreak remains under development. As you may know, the original exploit @comex developed in the first week of the iPad2 release was mysteriously fixed by Apple within days of its development. Partly because of this, don’t expect much public discussion of the iPad2 jailbreak until it’s actually finished and ready for release (and please avoid asking about it). In all liklihood, it will be a userland exploit like the first (unreleased) one, not dependent on bootrom dumps. The first one can’t be released even for those with the original 4.3 firmware due to legal (distribution) reasons.
iPad, iPod Touch and iPhone users who don’t care about unlocking are better off using Redsn0w as one doesn’t need to preserve baseband like iPhone users.
Please note that jailbreaking your iDevice may void its warranty so proceed at your own risk. Please don’t forget to backup your iPhone before you proceed. You can refer to this post for instructions on how to backup your iPhone.
Redns0w 0.9.6rc15 can be downloaded from the following link:
PwnageTool 4.3.3 is available only for Mac users and you can download it from one of the mirror sites:
Ultrasn0w v1.2.3 can be installed on a jailbroken iPhone 4 (baseband 01.59.00) or iPhone 3GS (baseband 04.26.08, 05.11.07, 05.12.01, 05.13.04 and 06.15.00) on iOS 4.3.3. Note: You can find your iPhone’s baseband by going to Settings –> About –> Modem Firmware
Ultrasn0w v1.2.3 can’t unlock iPhone 4 basebands – 02.10.04 (bundled with iOS 4.1), 03.10.01 (bundled with iOS 4.2.1), 04.10.01 (bundled with iOS 4.3) or iPhone 3GS basebands – 05.14.02 (bundled with iOS 4.1), baseband 05.15.04 (bundled with iOS 4.2.1), baseband 05.16.01 (bundled with iOS 4.3) and baseband 05.16.02 (bundled with iOS 4.3.1, iOS 4.3.2).
iPhone users who don’t care about unlocking but want to fix the signal bar issue also need to install Ultrasn0w 1.2.3.
If you meet the baseband requirements then you can follow these steps to unlock your jailbroken iPhone or fix the signal bar issue (T-Mobile USA users should disable 3G before using Ultrasn0w):
Launch Cydia from the homescreen.
Tap on the Search tab and search for ‘ultrasn0w’. That last “o” is actually the number zero “0”. If you use the letter “o” you’ll get an error.
Select ultrasn0w from the search results.
Then tap on the Install button.
Tap on the Confirm button.
You will be prompted to Restart SpringBoard, tap on it.
Reboot your iPhone, your iPhone should now be successfully unlocked or the signal bar issue should be fixed.
As always, let us know how it goes.
[via Dev Team’s blog]