A tool named Absinthe and developed by the Chronic Dev Team will install the untether on your device. Also the iPhone Dev Team will release a CLI (command line) tool to help diagnose issues and repair things if it goes wrong.
This is a little scary I know, but the chance you break something is really small, since we made lots of tests to verify the process on different devices. But it is the first time we use the backup / restore functions of iTunes to install software, and there are maybe things we are not aware of.
For more detailed information ahead of the jailbreak please read the information from iPhone Dev-Team.
The iPhone 4S and iPad 2 jailbreak utilities are undergoing testing and polishing before the public release. According to ‘Dream Team’ member planetbeing:
We’re testing & fixing problems with the jb app (that @pimskeks finished the majority of at incredible speed). Still needs to be polished.
P0sixninja also tweeted it should not be much longer before the jailbreak gets released.
iPhone Dev Team has posted a blog entry about upcoming public release. If you have iPad 2 or iPhone 4S go ahead and read it:
But we’re now near the final stages of testing the public version of the jailbreak. Please allow time to clean up any remaining bugs in the jailbreak clients.Jailbreak programs:
To be as flexible as possible, the A5 version of the corona jailbreak will take multiple forms:
Chronic Dev have incorporated the overall flow into a GUI that runs on your Mac or PC. The goal is for the GUI to be enough for most cases.
iPhone Dev have also incorporated the exact same flow into an alternative command-line interface (CLI). This will allow us to help users through individual steps of the jailbreak manually, to both help the user and help improve the overall flow. Although the CLI will also allow the user to perform the entire jailbreak from beginning to end, we anticipate it will be more useful in debugging the occasional errors. The CLI currently has over 20 individual options (in addition to the single “jailbreak” option) that should be useful during debug after the GUI release.
Once all the bugs in the flow are worked out, we’ll also incorporate it into the redsn0w GUI (but still leave the CLI freely available too). In order to maximize the chances of the jailbreak working for everyone, the redsn0w GUI will use native Apple iTunes libraries — this technique is slightly different than how the Chronic Dev GUI handles communications, and should provide nice combined coverage for all the odd computer configurations out there.
iPhone4S: 5.0 (9A334), 5.0.1 (9A405) and the “other” 5.0.1 (9A406)
iPad2: 5.0.1 (9A405)
iPhone4S owners looking to maximize their chances of achieving an eventual software-based carrier unlock should be staying at 5.0. Everyone else should be at 5.0.1. If you’re an iPhone4S owner who already updated to 5.0.1, it’s too late to go back down to 5.0, but if you’re on 9A406 it is possible to downgrade the BB by going to the 9A405 version of 5.0.1 while the window is still open.
Support:
The overall flow used by the GUI and CLI to inject the A5 corona jailbreak has never been done before, and there may be unforeseen problems once it’s released to the public. It’s very important for you to sync your data, photos, and music before attempting any version of this jailbreak. We’ll be watching the comments section below for signs of any widespread problems, but please be aware that you jailbreak at your own risk!
When:
As mentioned at the start of this post: when testing has shown most of the bugs have been fixed!
Popular jailbreak utility Sn0wbreeze was updated to version 2.9.1. Several issues were fixed, including iPad Baseband for iPhone 3G and several PAM issues.
New version 2.9 adds support for untethered iOS 5.0.1 jailbreak as well as support for all firmwares supported by previous versions of sn0wbreeze. You can read more about version 2.9 here.
iH8sn0w has released new version of popular jailbreak utility Sn0wBreeze 2.9. Sn0wbreeze is used to create a custom firmware with jailbreak and preserve iPhone modem (baseband) version for unlock. New version 2.9 adds support for untethered iOS 5.0.1 jailbreak as well as support for all firmwares supported by previous versions of sn0wbreeze.
The update fixes issues for iBooks and launchd and it’s recommended that users who previously jailbroke their A4 devices install the Corona package from Cydia.
Corona (5.0.1 untether) 1.0-4 is now out: users of redsn0w or the older packages should install. This fixes both iBooks and launchd (again).
As many users don’t realize that untethers only affects boot, I just released 1.0-5 of the Corona package, which forces a reboot on upgrade.
You can find instructions on how to install Corona here.
iPhone Dev Team have just released a new version of RedSn0w 0.9.10b4. It includes a fixes for iBooks and launchctl. As always, you can simply run the new redns0w over your current jailbreak, just make sure to uncheck Cydia. To fix iBooks and launchctl errors you can also simply install new version of Corona from Cydia.
Update #4: The b4 version of redsn0w incorporates the 5.0.1 fix for iBooks, and also for sporadic problems with launchctl. Thanks to @xvolks for merging the iBooks (sandbox) fix from @comex’s github into the overall corona untether from @pod2g! As usual, you can choose to install the fix either by re-running redsn0w over your existing jailbreak (de-select Cydia if you do that), or by installing the corona package from Cydia (it’s the same set of files no matter which way you choose).
You can download the new version of RedSn0w from here.
@planetbeing escaped from the sandbox with the help of @saurik. Thanks to their awesome work, there should be nothing left blocking for the A5 jailbreak. Now it should be a matter of days. Still no precise ETA of course.
Now that the team has been successful in breaking out of Apple’s sandbox (which lets them run unsigned code) they’ll focus their attention on writing the Mac OS X and Windows software utilities.
“Now it should be a matter of days” means that jailbreak utilities will be released very soon, maybe next week.