Update #5: Unlockers have been reporting mixed results about GPS functionality at 06.15.00. Until we can track down what differentiates those who retain GPS vs. those who lose it, be conservative and assume you’ll lose GPS at 06.15.00. As we work on finding the cause (and possibly a fix), please report your personal findings in our comments section. (Update: early indications are that while 06.15.00 is capable of GPS, it will require some further hacks. But please still be conservative and assume you will lose GPS at 06.15, in case the hacks don’t work).

Update #3: For those Mac users with an old-bootrom 3GS who really know what they’re doing, here’s a minimal 3GS 4.2.1 bundle that will get you to 4.2.1 without updating your baseband. Be sure to uncheck “Activate the iPhone” using Expert mode. To actually jailbreak after you’ve restored with the help of that bundle, please use redsn0w. If you don’t know how to drop a bundle into PwnageTool.app, please hold off on 4.2.1 until it’s untethered for everyone

See the Dev-Team’s full post HERE.

SIMPLIFIED VERSION (Updated):
1. Read and fully understand the warning below.
2. If you have an old-bootrom 3GS and are already unlockable but want to get to 4.2.1, please wait til we release an “unofficial” bundle for you. Read no further.
3. Read update #1 for an updated 3GS bundle.
4. Download this IPSW
5. Run PwnageTool to create a custom 4.1 IPSW. Tell it you want to use the iPad baseband you just downloaded. Restore to this custom IPSW.
6. Install ultrasn0w through Cydia
7. Enjoy!
8. If you don’t have a Mac, redsn0w will be released within a few hours to handle this.

Below is the full post from the Dev-Team’s blog… you will want to read it before using ultrasn0w.

Today we’re pleased to announce our free carrier unlock for iPhone3G/3GS owners with a baseband later than 05.13.04. The unlock for that baseband exploited the AT+XAPP command, thanks to a crash initially discovered by @sherif_hashim (@Oranav also found this crash). So what hole are we exploiting today, since Apple closed that AT+XAPP hole? Well, we’re exploiting the exact same hole!

It turns out that the very first iPad firmware 3.2.2 has baseband version 06.15.00 still vulnerable to AT+XAPP. The iPad baseband is built for the exact same baseband chip as the iPhone3G/3GS — they’re fully compatible! Some of us have been running 06.15 for weeks now on our iPhones in preparation for this release.

SIMPLIFIED VERSION:

1. Read and fully understand the warning below.
2. If you have an old-bootrom 3GS and are already unlockable but want to get to 4.2.1, please wait til we release an “unofficial” bundle for you. Read no further.
3. Read update #1 for an updated 3GS bundle.
4. Download this IPSW
5. Run PwnageTool to create a custom 4.1 IPSW. Tell it you want to use the iPad baseband you just downloaded. Restore to this custom IPSW.
6. Install ultrasn0w through Cydia
7. Enjoy!
8. If you don’t have a Mac, redsn0w will be released within a few hours to handle this.

FULL VERSION:

Since 06.15 is a higher version than 05.14 or 05.15 (where AT+XAPP is gone), anyone stuck at those versions can simply upgrade to 06.15 to unlock again! Luckily for us, Apple *still* provides the iPad FW 3.2.2 with this vulnerable baseband right from their own servers. (Grab it now, before they take it down!)

We’ve been busy updating both PwnageTool and redsn0w to make the baseband update as seamless as possible.

1. First up is “PwnageTool 4.1.3 Unlock Edition”. It has a special dialog box which will ask you if you want to update to the iPad baseband. You must already have the iPad 3.2.2 IPSW on your computer (see the above link)….so just point PwnageTool at it (or let it find it on its own if you’re in “simple” mode).

2. Directly after PwnageTool 4.1.3 is available, the official ultrasn0w repo http://repo666.ultrasn0w.com will be updated with ultrasn0w 1.2, which covers iPhone 4 baseband 01.59.00 and iPhone 3G/3GS basebands 04.26.08, 05.11.07, 05.12.01, 05.13.04 and now 06.15.00.

3. Finally, we’ll release an update to redsn0w today for those without Macs and can’t run PwnageTool. The new redsn0w will give you the option to update your baseband to 06.15 too.

WARNING — YOU DO THIS AT YOUR OWN RISK! PLEASE UNDERSTAND THE CONSEQUENCES OF UPDATING TO 06.15.

1. There is no way to come back down from 06.15, and there’s no hiding the baseband version from Apple. You’ll be voiding your warranty in a very obvious way.

2. If some future baseband comes out with a critical fix, you won’t be able to update to it if it remains down in the 05.xx sequence (then again, you wouldn’t update to it if you wanted to keep your unlock anyway).

3. Starting with FW 4.2.1 if you have 06.15 on your iPhone you won’t ever be able to restore to stock firmware (it will fail). You’ll need to only restore to custom IPSWs (then again, if you’re unlocker you should already be doing that).

Certainly don’t update to 06.15 if you don’t need to! Only do this if you need the unlock and you’re stuck on 05.14 or 05.15, and you’re willing to assume the above risks.

This PwnageTool also contains a 4.2.1 bundle for iPhone3G owners…for all else, it’s still only 4.1. If you have an iPhone3GS with an old bootrom, the new redsn0w will handle 4.2.1 for you (in fact it covers 4.2.1 for all devices, even though some of them are still tethered at 4.2.1 until @comex can work some untethering magic). iPhone3GS users with old bootroms who want to go to 4.2.1 should not use this PwnageTool! Update to stock 4.2.1 first, then use the upcoming redsn0w to update your baseband.

Please feel free to use our comments section for questions. We have some very knowledgeable and helpful moderators: angiepangie, Confucious, dhlizard, and Frank55!

Update #1: There’s an error in the bundle for the iPhone 3GS 4.1 that prevents the new baseband from being used. If you know your way around OSX, please download the fixed bundle, and unzip it if Safari hasn’t already done so. Then “Show Package Contents” of PwnageTool.app, navigate to Contents->Resources->FirmwareBundles and drop it there. Otherwise, please wait for the updated PwnageTool, or the OSX version of redsn0w coming soon.

Check out the Dev-Team’s post for the download links.

Today we’re pleased to announce our free carrier unlock for iPhone3G/3GS owners with a baseband later than 05.13.04. The unlock for that baseband exploited the AT+XAPP command, thanks to a crash initially discovered by @sherif_hashim (@Oranav also found this crash). So what hole are we exploiting today, since Apple closed that AT+XAPP hole? Well, we’re exploiting the exact same hole!

It turns out that the very first iPad firmware 3.2.2 has baseband version 06.15.00 still vulnerable to AT+XAPP. The iPad baseband is built for the exact same baseband chip as the iPhone3G/3GS — they’re fully compatible! Some of us have been running 06.15 for weeks now on our iPhones in preparation for this release.

FULL VERSION

Since 06.15 is a higher version than 05.14 or 05.15 (where AT+XAPP is gone), anyone stuck at those versions can simply upgrade to 06.15 to unlock again! Luckily for us, Apple *still* provides the iPad FW 3.2.2 with this vulnerable baseband right from their own servers. (Grab it now, before they take it down!)

We’ve been busy updating both PwnageTool and redsn0w to make the baseband update as seamless as possible.

1. First up is “PwnageTool 4.1.3 Unlock Edition”. It has a special dialog box which will ask you if you want to update to the iPad baseband. You must already have the iPad 3.2.2 IPSW on your computer (see the above link)….so just point PwnageTool at it (or let it find it on its own if you’re in “simple” mode).

2. Directly after PwnageTool 4.1.3 is available, the official ultrasn0w repo http://repo666.ultrasn0w.com will be updated with ultrasn0w 1.2, which covers iPhone 4 baseband 01.59.00 and iPhone 3G/3GS basebands 04.26.08, 05.11.07, 05.12.01, 05.13.04 and now 06.15.00.

3. Finally, we’ll release an update to redsn0w today for those without Macs and can’t run PwnageTool. The new redsn0w will give you the option to update your baseband to 06.15 too.

WARNING — YOU DO THIS AT YOUR OWN RISK! PLEASE UNDERSTAND THE CONSEQUENCES OF UPDATING TO 06.15.

1. There is no way to come back down from 06.15, and there’s no hiding the baseband version from Apple. You’ll be voiding your warranty in a very obvious way.

2. If some future baseband comes out with a critical fix, you won’t be able to update to it if it remains down in the 05.xx sequence (then again, you wouldn’t update to it if you wanted to keep your unlock anyway).

3. Starting with FW 4.2.1 if you have 06.15 on your iPhone you won’t ever be able to restore to stock firmware (it will fail). You’ll need to only restore to custom IPSWs (then again, if you’re unlocker you should already be doing that).

Certainly don’t update to 06.15 if you don’t need to! Only do this if you need the unlock and you’re stuck on 05.14 or 05.15, and you’re willing to assume the above risks.

This PwnageTool also contains a 4.2.1 bundle for iPhone3G owners…for all else, it’s still only 4.1. If you have an iPhone3GS with an old bootrom, the new redsn0w will handle 4.2.1 for you (in fact it covers 4.2.1 for all devices, even though some of them are still tethered at 4.2.1 until @comex can work some untethering magic). iPhone3GS users with old bootroms who want to go to 4.2.1 should not use this PwnageTool! Update to stock 4.2.1 first, then use the upcoming redsn0w to update your baseband.

Please feel free to use our comments section for questions. We have some very knowledgeable and helpful moderators: angiepangie, Confucious, dhlizard, and Frank55!

Check out the ef="http://blog.iphone-dev.org/post/1718400992/ultra-recycle">Dev-Team’s post for the download links.

    • The update will still not include the iPhone 4
    • It will cover the 4.2.1, 3G/3GS iPhones, baseband (05.15.04)
    • The best config for unlockers will be: old-bootrom 3GS, FW 4.2.1, untethered redsn0w JB, ultrasn0wed

Question: What about new-bootroom devices? is it gonna cover them is well?
Answer: The unlock will cover 3GS devices that are currently tethered JB at 4.2.1, but you’d still need to tether JB them for now

Question: So will it work on new-bootrom 3GS 4.1/05.14.02? Or does it need 4.2.1?
Answer: Nope it doesn’t need 4.2.1…but we needed to make it to work on 4.2.1. For new-bootrom 3GS, 4.1 is best for now

Question: What about new-bootroom devices? is it gonna cover them is well?
Answer : I’d stay at 4.1 if I were on a new-bootrom 3GS, until the untether JB 4.2.1 comes out

QuestIon: ultrasn0w 4.2.1 working for iPhone 4?
Answer: Yes…but only just as of tonight: but to reiterate, on iPhone 4 that’s only on BB 01.59.00

As we mentioned, the updated ultrasn0w unlock should be available by Sunday. We’ll keep you posted.

With Turkey Day a few days off, today Apple publicly released FW version 4.2.1. As always, ultrasn0w unlockers please stay far far away from this official firmware (and all official firmware). Wait for the ability to create custom 4.2.1. IPSWs that don’t update your baseband! If you’re not an unlocker, read on!

The best news of all is for owners of iPhone3G, older iPhone3GS, and non-MC iPod touch 2G. Due to a combination of our original pwnage2 exploit, the arm7_go exploit, 24kpwn, and limera1n, your device is “just as jailbreakable as ever.” You reap the full benefit of an untethered 4.2.1 jailbreak.

Next are the owners of all the more recent devices. The good news there is that due to geohot’s limera1n exploit, all recent devices can be jailbroken (this will be true until Apple released new hardware that fixes geohot’s limerain exploit in the bootrom). The bad news is that right now, the 4.2.1 jailbreak is *tethered* on all of these recent devices. A tethered jailbreak means that each time your device loses battery power or needs to be rebooted, you must attach it to a PC or Mac to boot into the jailbroken state. @comex is working hard on a method that may untether the 4.2.1 jailbreak, but it will require you to have your 4.1 SHSH blobs in order to use it. No word on how much more effort it will take though (please don’t bug @comex about it!). (We also have an alternative method that may work, but @comex’s method is much more elegant.)

So when does all this 4.2.1 jailbreak action happen? Well if you’re a JB developer or tinkerer, you’ve already probably used the redsn0w mentioned in our last post to jailbreak 4.2.1 and at least get SSH working. But beyond that, there are still some last minute issues with MobileSubstrate and comex’s kernel patches that are being fixed. We’ll tweet and post a blog update when it’s all available (we hate to give ETAs, but barring any unforeseen problems, probably later today). It happens “now’…see Update #1.

In the meantime, please make sure you have your 4.1 SHSH blobs for all your devices. These will be important even for firmware beyond 4.1 (using both comex’s method and our alternative, depending on how each of them turn out.)

ultrasn0w unlock: After redsn0w is officially released with the new Cydia and kernel patches, we’ll be able to assess the unlock situation. It’s already looking very promising though, so expect the unlock for the 3G and 3GS to be coming this week. The i4 unlock is taking more effort though, and no further concrete info is available about that yet.

Feel free to ask questions in our comments section below, where we’ve got some awesome new additional moderators — sherif_hashim, dhlizard, and Frank55!

Update #1: redsn0w version 0.9.6b4 is now available for your 4.2.1 jailbreaking pleasure. Please read all the above to understand what this jailbreak currently entails.

Check out the Dev-Team’s blog post for the download links for both Mac and PC.

ultrasn0w 1.0-1 is compatible with iPhone4 on baseband 01.59 and 3G/3GS basebands 04.26.08, 05.11.07, 05.12.01 and 05.13.04.

Video

Sherif Hashim’s Tweets:
(Feb 10th)

))))))))))))))))))))))))))))))))))))))))))))))))))))))) i just crashed the 5.12.01 baseband ))))))))))))))))))

(Feb 14th)

“Your Apple ID was banned for security reasons”, that’s what i get when i try to go to the app store, they must be really angry ))))

and guess what my apple ID was, “sherif_hashim@yahoo.com”, what a fool was me not to notice )), can’t help laughing, they are babies ))

at least they should have wait after the release ) about 15 hours ago from Twitterrific in reply to goobot

ScreenShot

Firstly, complete the unlocking form – it will take up to 14 days for the iPhone to be unlocked and we’ll text you to confirm the unlock request. Then place a non-O2 sim into the iPhone and connect to iTunes via a USB cable. iTunes will confirm that the iPhone has been successfully unlocked.