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.
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!
Semi-tethered jailbreak is already available for some devices for both iOS 5 and iOS 5.0.1. But we all want untethered jailbreak and we want jailbreak for iPad 2 and iPhone 4S. So why not help hackers to find new exploits and vulnerabilities?
The Chronic Dev-Team has a released a tool to collect crash reports from iOS devices in order to find vulnerabilities that could lead to an untethered jailbreak.
The idea is very simple. When your iPhone, iPad or iPod Touch crashes it sends data to Apple (you can turn it this off though). Apple uses these reports to update iOS in the future. By the way, it also uses them to fix exploits found by jailbreakers. P0sixninja says that Apple closed several exploits they have found in IOS 5 beta before the final version of the software was released.
In order to find more vulnerabilities as fast as possible, the team has developed a tool which will copy the crash reports from your device and analyze them to locate potential exploits. The tool will also remove the crash reports from your device and modify your iTunes installation to prevent uploading of that diagnostic information to Apple.
The iPhone Dev-Team has released RedSn0w 0.9.9b5 – an official tethered jailbreak for iOS 5. Users don’t have to point to downloaded iOS 5 ipws any more. Just run and jailbreak.
Currently only the Mac version has been made available. Windows version is coming soon. However Windows users can still jailbreak iOS 5 with Redsn0w 0.9.9.b4, – just go to “Extras” -> “Select IPWS” and select your iOS 5 ipsw file (can download here).
Good news for users who need carrier unlock (ultrasn0w or Gevey Sim). With RedSn0w 0.9.9b5 you can update to iOS 5 and preserve the baseband (modem) version for unlock:
The new “Custom IPSW” button on the Extras screen will create a custom IPSW without the baseband update for 4.3.3 or 5.0gm (iPhone3GS and iPhone4 only, for now). Remember not to accidentally restore to the stock IPSW after you create the custom one! The custom one begins with NO_BB_ (for “no baseband”).
You must enter “Pwned DFU” mode before trying to use the NO_BB_ IPSW with iTunes (and your hosts file cannot be pointing to Cydia’s servers due to the new blob nonce mechanism they’re using in iOS5).
We will update our step-by-step tutorials soon.
You can download RedSn0w 0.9.9b5 (Mac) and RedSn0w 0.9.9b4 (Windows) here.
PS: RedSn0w 0.9.9 is a bit different from 0.9.8 version. You can learn more about other new redsn0w 0.9.9 features here. UPDATE: redsn0w 0.9.9b6 released, download here
Here are links to our RedSn0w 0.9.9 iOS 5 jailbreak tutorials:
uses DFU mode to try to automatically determine which device and FW you have
fetches pieces of public IPSWs from Apple (once). Non-public IPSWs must be provided manually (once). It then caches those pieces for future use.
“Just boot” is a tethered boot. Uses whatever “Preferences” you’ve set for boot logo and kernel boot-args
“Pwned DFU” puts your device in a pwned DFU state for some of the iTunes stuff detailed below
“Recovery fix” gets past 1015 types of errors (when baseband portion of restore fails). Should work on iOS5 beta too
“Select IPSW” is for picking non-public IPSWs, or overriding auto-detection
“SHSH blobs” has a bunch of options…
“Fetch” – fetch current PARTIAL blobs on device. Should complete in under 10 or 15 seconds. Puts the set of PARTIAL of blobs on your computer as a plist. Checks if Cydia already has a full set for this device and build. If not, it submits this PARTIAL set and returns Cydia’s acknowledgement or rejection
“Verify” – cryptographically verifies existing blob files from either redsn0w, TinyUmbrella, or Cydia server. You can select a whole bunch of blobs to verify at once if you want (like the TinyUmbrella directory)
“Submit” – both verifies and submits one or more blob files to Cydia. This lets you copy your entire TinyUmbrella cache of blobs up to the Cydia server
“Query” - queries the Cydia server for all available FULL or PARTIAL blobs for a given set of ECIDs
“Stitch” – stitches either FULL or PARTIAL blobs to a STOCK or CUSTOM IPSW
Stitching is NOT yet supported on iPhones! Need to work out the baseband part of the restore process.
FULL blobs stitched to a STOCK IPSW gives you a completely self-contained signed IPSW that iTunes will accept without any tricks (no need to go into pwned DFU mode, no need to start TinyUmbrella TSS server, no need to redirect to Cydia server for blobs)
PARTIAL blobs stitched to any IPSW requires you to go into pwned DFU mode before running iTunes. No need to start TU or use Cydia though.
Stitching either FULL or PARTIAL blobs to a CUSTOM IPSW also requires a pwned DFU start before iTunes restores. No need to start TU or use Cydia though./li>
Will eventually support fetching the blobs directly from Cydia instead of a file on your computer
iH8Sn0w has released a new version of Sn0wBreeze 2.8 b4 with iOS 5.0 beta 3 jailbreak support. Sn0wBreeze is a so-called PwnageTool for Windows, an application that creates a custom ipsw with jailbreak preserving old baseband.
sn0wbreeze v2.8b4 -- For iOS 5.0 b3(9A5259f)
* Intended only for developers (as usual).
* Hacktivation is disabled (again).
* MAKE SURE YOU UPDATE TO iTunes 10.5 BETA 3!
iPhone 3G[S] (old bootrom) [UNTETHERED]
iPhone 3G[S] (new bootrom) [TETHERED]
iPhone 4 (GSM) [TETHERED]
iPhone 4 (CDMA) [TETHERED]
iPod Touch 3G [TETHERED]
iPod Touch 4 [TETHERED]
iPad 1G [TETHERED]
Those wondering, the jailbreakme exploit
cannot be integrated into applications
such as PwnageTool/redsn0w/sn0wbreeze.
redsn0w seems to be having sandbox errors
due to it using the old b1 kernel.
I and many others have not seen any issues
with sn0wbreeze related to AppStore apps.
If you prefer to use redsn0w, I am sure
@MuscleNerd is working on a fix.
Download --> http://is.gd/sb28b4
MuscleNerd recently Tweeted that iOS 5 beta 1 jailbreak is already available. DevTeam released Redsn0w 0.9.8 b1.
For now the jailbreak is tethered (you have to run redsn0w each time you reboot) and available for Mac OS X only. It will not activate your device, so you need have registered UDID. iPhone 3GS users with 06.15 baseband: redsn0w will get you past the iTunes restore error. This redsn0w will probably work on future versions of iOS 5.
Apple recently released iOS 5 beta and iTues 10.5 beta. It is available only for Apple registered developers. But you can try it too. Remember that you do it at your own risk. Below you will find iOS 5 download links for iPhone 3GS, iPhone 4, iPod Touch 3G, iPod Touch 4G, iPad 1, iPad 2, Apple TV 2G and download links to iTunes 10.5 Mac and Windows.
Keep in mind that your iDevice will need to be activated, your UUID needs to be registered in Apple. Installing iOS beta on a non-activated device will render it useless. If you need help with registering UUID – write us, we will try to help..
Remember that currently there is no jailbreak for iOS 5 released.
You can download iOS 5.0 beta 1 and iTunes 10.5 beta here.