A tool named Absinthe was developped by the Chronic Dev Team to install the untethered jailbreak on your iPad 2 and iPhone 4S. 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 quite 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.
A unified PayPal account was opened so that everyone who worked on the A5 exploits will receive a fair split of your contributions. Here is the link to contribute!
Be sure to donate the A5 jailbreak team a few bones, planning to donate $100 once the jailbreak is made available. These guys have worked hard for the past couple weeks to get the iPhone 4S jailbroken for the first time, the iPad 2 has only had one other jailbreak.
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.