As one knows few days ago Apple released an update to iOS 4.3.3 which solve the location tracking issue.
As I mentioned before apple did not fix the bug founded by @i0nic, which brings untether jailbreak to iOS 4.3.3. As I predicted Dev-Team and iH8sn0w update their jailbreaking tools (redsn0w, pwnageTool, and sn0wbreeze) to support this version.
redsn0w 0.9.6 rc15 , pwnageTool 4.3.3, sn0wbreeze 2.7 are the tools you can use for jailbreaking all iDevices (expect iPad2) running iOS 4.3.3 (4.2.8 for Verizon iPhone 4). Download links could be found under our download section.
Ultrasn0w also updated to support this version. You can find it in Cydia.
As before I just put the links to the instructions from other sites instead of duplicating the world. I think it is much more environmental friendly!
The iPhone DevTeam has update PwnageTool to ver 4.3.2 which support iOS 4.3.2 (Untethered). They recently update redsn0w to support iOS 4.3.2 but redsn0w can’t prevent baseband upgrade. Unfortunately iPad2 not supported in this version.
Ultrasn0w also update to version 1.2.2. You can install it via Cydia.
Only a few weeks after the 4.3.1 untether created by @i0n1c was released, Apple pushed out firmware 4.3.2. Thankfully, it appears Apple didn’t have a chance to fix the hole used by @i0n1c’s untether, so he ported his code over to 4.3.2’s kernel. Today’s redsn0w has been updated to include it. The 4.3.2 untether works on all devices that actually support 4.3.2 except for the iPad2: iPhone 3GS iPhone4 (GSM) iPod touch 3G iPod touch 4G iPad1
Only a few weeks after the 4.3.1 untether created by @i0n1c was released, Apple pushed out firmware 4.3.2. Thankfully, it appears Apple didn’t have a chance to fix the hole used by @i0n1c’s untether, so he ported his code over to 4.3.2’s kernel. Today’s redsn0w has been updated to include it.
The 4.3.2 untether works on all devices that actually support 4.3.2 except for the iPad2:
How to Jailbreak Your iPhone 4 Using PwnageTool (Mac) [4.3.2] Via iClarified
iPhone Dev-Team today release a new version of PwnageTool (MAC only) wich brings untethered jailbreak to all 4.2.1 devices. As you know the major difference between PwnageTool and other jailbreaking solution is that with PwnageTool you can create a custom pre-jailbroken firmware file (.iPSW) and then restore it to your iDevice using iTunes instead of jailbreaking device on the fly. You can also prevent baseband upgrade using PwnageTool, it’s a good news for iPhone unlockers (iPhone 4 [Verizon] & 3GS) because they can safely restore to a custom iOS 4.2.1 pre-jailbroken iPSW and retain their current baseband and unlock.
as the Chronic Dev Team revealed last week with an untether for the 4.2.1 jailbreak, which had previously been a tethered JB for most recent devices since 4.2.1’s release in November. With their permission, we’ve incorporated their 4.2.1 “feedface” untether into today’s PwnageTool 4.2.
This version of pwnagetool also contain iBook fix and also solve AppleTV 2G Wi-Fi problem.
PwnageTool also includes two very recent improvements to the 4.2.1 JB: iBooks was just fixed by @comex and @pushfix last night so that it works as intended on DRMed books, and the wifi problem on AppleTV 2G was fixed by @nitotv, @DHowett, and @saurik. Both of these fixes will also be available in upcoming Cydia package updates, so if you’re already jailbroken you can wait for those updates rather than restore and jailbreak again.
Here is a list of supported devices in PwnageTool 4.2
Feel free to ask for help in comments section.
The iPhone Dev-Team has announced that there will be no unlock -More About Unlocking- released until after iOS 4.2.5 or 4.3 is released.
From Dev-Team blog
This time of year there are lots of new iPhone owners, and not everybody knows that accepting new iOS updates is the surest way to lose your jailbreak and/or unlock. While those of you who have Cydia or TinyUmbrella backups of your FW hashes will always be able to get back to 4.0.1 if you make this mistake, this doesn’t hold for unlockers. There’s currently no known way to revert your baseband — if you update your baseband you’ll lose the ultrasn0w unlock, possible forever. Please stay away from this 4.1 release until a safe jailbreak procedure (which also preserves ultrasn0w) is developed and released. P.S. There are a tiny number of iPhone3G owners who can revert their basebands due to a flaw in very early bootloaders…you will already know if you fit in this category!
This time of year there are lots of new iPhone owners, and not everybody knows that accepting new iOS updates is the surest way to lose your jailbreak and/or unlock. While those of you who have Cydia or TinyUmbrella backups of your FW hashes will always be able to get back to 4.0.1 if you make this mistake, this doesn’t hold for unlockers. There’s currently no known way to revert your baseband — if you update your baseband you’ll lose the ultrasn0w unlock, possible forever.
Please stay away from this 4.1 release until a safe jailbreak procedure (which also preserves ultrasn0w) is developed and released.
P.S. There are a tiny number of iPhone3G owners who can revert their basebands due to a flaw in very early bootloaders…you will already know if you fit in this category!
Apple today released a new version of iPhone OS. This update contains 3GS baseband upgrade (05.12.01) so BE WARNED. DON’T UPDATE YOUR iPHONE 3GS.
There is not any notable change in this firmware.
iPhone 2G users : Can use redsn0w (download here) in order to jailbreak it. Please note that you should have firmware 3.1.2 file and you must point redsn0w to that files after updating (or restoring) to 3.1.3.
iPhone 3G users : If you need to unlock your iPhone baseband (using ultrasn0w, etc) DON’T UPDATE TO 3.1.3. otherwise use the above method.
iPhone 3GS users: BE WARNED. DON’T UPDATE YOUR iPHONE AT THIS TIME.
iPod Touch 1G users : Same as iPhone 2G.
iPod Touch 2G users : Do not update to 3.1.3
iPod Touch 3G users : Do not update to 3.1.3
The above information maintained from Dev-Team blog
Few minutes ago, Dev-Team released their new PwnageTool for jailbreaking iPhone OS 3.1
iPhone 2G (1st Generation) Use PwnageTool to do the magic and then restore with iTunes using your newly created .ipsw ‘nuff said, you don’t need to worry about anything, the baseband will be unlocked, the phone jailbroken. iPod Touch 1G (Original iPod Touch) Use PwnageTool to create a firmware image and restore with that .ipsw using iTunes. iPod Touch 2G (New iPod Touch) Sorry, no support at this time within PwnageTool, use Redsn0w for an earlier (pre 3.1) firmware release instead.
iPhone 2G (1st Generation) Use PwnageTool to do the magic and then restore with iTunes using your newly created .ipsw ‘nuff said, you don’t need to worry about anything, the baseband will be unlocked, the phone jailbroken.
iPod Touch 1G (Original iPod Touch)
Use PwnageTool to create a firmware image and restore with that .ipsw using iTunes.
iPod Touch 2G (New iPod Touch)
Sorry, no support at this time within PwnageTool, use Redsn0w for an earlier (pre 3.1) firmware release instead.
Torrent Link:
According to the latest news from DevTeam members :
DONT UPDATE TO OS 3.1, WAIT for the new version of pwning tools.
Stay Tuned.
Today Apple announce iTunes 9 along with iPhone OS 3.1 (Build 7C144). As DevTeam said, iPhone users who wants to unlock their iPhones with Ultrasn0w should not update their iPhone to 3.1 and have to wait for new version of Redsn0w and PwnageTool.
Below you can find direct download link for iPhone OS 3.1
iPhone 2G – iPhone1,1_3.1_7C144_Restore.ipsw iPhone 3G – iPhone1,2_3.1_7C144_Restore.ipsw iPhone 3GS – iPhone2,1_3.1_7C144_Restore.ipsw
Some tips from Dev Team :
Unusual battery depletion is almost always caused by people choosing to “Restore from backup” instead of “Setup as new iPhone” when iTunes asks you. This isn’t caused by either the jailbreak or the unlock, but it’s a common 3.0 snafu. The fix is to just re-run the official 3.0 restore and choose “Setup as new” this time. Your music and apps and all that will still be synced, but you’ll get rid of any conflicting wifi, bluetooth, or carrier settings. Then just re-run redsn0w and install ultrasn0w. Remember, ultrasn0w works with hacktivated phones too, but don’t outsmart redsn0w into thinking you don’t need hacktivation! If you don’t plan on using an official sim, don’t activate via iTunes with such a sim. Just keep your unofficial sim at all times and let redsn0w and ultrasn0w handle hacktivation T-Mobile in the USA doesn’t use the 3G frequencies that the iPhones support, so turn off 3G in Settings->General->Network. (Some T-Mobile territories gracefully hand down to Edge mode, but most do not). Certain unofficial plans have limitations on whether you can make calls and use data at the same time. That’s not unlock-related. Some people have installed previous versions of ultrasn0w using non-standard techniques. While the ultrasn0w 0.9 update should have removed all previous versions of ultrasn0w, these users may have outsmarted our removal. So make sure you don’t still see /usr/bin/ultrasn0w present if you’re at ultrasn0w 0.9 (which doesn’t have such a binary anymore). If you don’t need or plan to update to ultrasn0w 0.9 from a previous version, you can avoid having that red badge over Cydia by removing repo666 as a Cydia source. Don’t worry, you can always add it back later If you follow us on twitter you’ll be advised of any new updates anyway.
