redsn0w allows owners of A4+earlier devices to install rocky-racoon two different ways:
backup/restore method similar to Absinthe and cinject
its traditional limera1n-based ramdisk install. If you have a lot of media on your A4 device (music, movies, TV shows, etc), then the ramdisk method is preferrred because it avoids any possibility of later problems related to syncing to iCloud (including Photo Stream and Music Match). The ramdisk method is not available for A5 devices or later because limera1n can’t be used. If you’d like to use redsn0w’s ramdisk method, just be sure to put the A4 device in DFU or Recovery mode before starting redsn0w (otherwise it will immediately start to use the backup/restore method).
We’ve also added a new redsn0w feature specifically for those who got in on the SAM unlock: you can now include your SAM tickets as part of your initial ramdisk jailbreak of iPhone4 or earlier, or alternatively you can upload your SAM tickets to any device after its been jailbroken. redsn0w accepts either the individual SAM activation ticket plist file, or the entire zip file created by redsn0w’s “Backup” button. As usual, redsn0w continues to cover all of its previous jailbreaks and untethers (so redsn0w-0.9.12b1 covers everything from 5.1.1 all the way back to 4.1).
PwnageTool also avoids any possible sync issues, but again it applies only to A4+earlier devices. If you unlock your iPhone with ultrasn0w or a commercial method, you must use PwnageTool to avoid updating your baseband otherwise you’ll lose the unlock. PwnageTool will also jailbreak+untether the AppleTV2,1 5.0_2B206f (unless you customize the IPSW further, you’ll have just basic SSH access to the device).
Just like version 2.9.4 the new 2.9.5 version supports untethered jailbreak of A4 devices on iOS 5.1.1. Sn0wbreeze can be used to create a custom firmware with jailbreak and preserve iPhone modem (baseband) version for unlock.
Sn0wbreeze 2.9.5 supports iPhone 3GS, iPhone 4, iPad 1, iPod Touch 3G, iPod Touch 4G and Apple TV 2G. It does not work with A5 devices, like iPad 2, iPad 3 and iPhone 4S.
All info below is tentative and subject to last minute refinements
@pod2g’s 5.1.1 jailbreak+untether is working out great. All devices are covered except for AppleTV3,1, which currently has no path for jailbreaking.
- the initial 5.1.1 plan used a kernel exploit from @westbaer which unfortunately precluded use in iPod3,1 and iPhone2,1
- @planetbeing stepped up and provided a kernel exploit that covers both of those. Those two JBers are the bomb!
The 5.1.1 A5 JB is very similar to the A5 5.0.1 JB. @pimskeks has done a tremendous job supporting both 5.0.1 and 5.1.1 in absinthe
Similar to 5.0.1, there will also be a 5.1.1 CLI “cinject” binary and redsn0w version of the 5.1.1 JB+untether. Absinthe, cinject, and redsn0w will all provide the same JB in different fashions.
- timing is indeterminate. Plans are for this week, but a number of factors can influence that.
For those wishing to donate, we’ve set up a new 5.1.1 paypal URL: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=4U6DQGJ2NRVUN
Please don’t pirate AppStore apps (seriously, please do not).
Version 0.9.10b7 of redsn0w adds a collection of useful features: It finally implements the corona-A5 jailbreak for iPhone4S and iPad2 devices still at 5.0.1. It can also re-install that jailbreak for those who accidentally uninstalled the untether. When stitching an IPSW, it can now grab your blobs directly from Cydia. It now shows a lot more info about your device (for instance, whether your iPhone3G has the vulnerable baseband boot loader, or whether your iPhone3GS has the old exploitable bootrom. (And the next new feature to be added will be built-in restore support, to provide an alternative to iTunes restores.)
Previously you needed to use Absinthe to jailbreak the iPhone 4S and iPad 2.
Using saved SHSH blobs, iH8sn0w was able to downgrade his A5 iPad 2 from iOS 5.1 to iOS 5.0.1. He says his method will also work with the A5X processor once firmware updates are released for the new iPad. That means that it’s possible to restore to any firmware you want on A5 devices, as long as you have the SHSH blobs saved.
This is great news for those with the iPhone 4S and newer iPads. As it stands now, if you have to restore for any reason, you will be forced to upgrade to the latest firmware. This could leave you without the ability to jailbreak for some time.
Found a loophole in Apple’s apticket system. Restored my iPad 2 to 5.0.1 from 5.1. Works on all A5 devices.
A5X devices will work too once Apple pushes a new firmware for it.
Hope we will see update to current utilities soon.
The Chronic Dev-Team has released an update to their Absinthejailbreak utility for iPhone 4S and iPad 2. So users who failed to jailbreak can try with new version Absinthe 0.3. Chronic Dev-Team also released a version for Linux users.
@pimskeks announced the release over Twitter:
Linux version (x86/x86_64) of #Absinthe #A5 #jailbreak is done!
Also version 0.3 of #Absinthe #A5 #jailbreak is available for OSX and Windows. Nothing really new, so no need to re-apply
#Absinthe 0.3 only has some cosmetic changes, and a potential bug fix for win32 (only really few people seem affected)
You can download Absinthe for Windows, Mac OS X and Linux from here.
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.
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!
As mentioned at the start of this post: when testing has shown most of the bugs have been fixed!