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
New redsn0w is.gd/6eek4Y explicitly supports iOS5b7 (no need to point at b6 IPSW). Also brings back old-bootrom 3GS goodies.
This is great news for both developers and owners of old bootrom iPhone 3GS’s who accidentally updated to iOS 4.3.5.
About 12 hours after we released redsn0w 0.9.8b7 with some improvements for iOS5b6, Apple went and released iOS5b7 (what are the odds of that?!?). Even though that redsn0w could still jailbreak iOS5b7, you needed to point it at the iOS5b6 IPSW to do so. Today’s redsn0w 0.9.8b7b lets you point redsn0w directly at the iOS5b7 IPSW instead.
We’ve also added some overall improvements for old-bootrom 3GS owners (where the 24kpwn exploit applies): on those devices, you can tell redsn0w to untether 4.3.5 and lower, or iOS5b7. Old-bootrom 3GS owners can once again choose custom logos, and/or verbose booting (for the really nerdy iPhone3GS fans out there!). And it allows 4.3.4 or 4.3.5 users to use ultrasn0w again (if they have a compatible baseband).
Last but not least, we fixed some lingering Verizon iPhone4 4.2.10 JB issues.
The iPhone Dev-Team recently released RedSn0w 0.9.8b7 which brings explicit support for a tethered 4.3.5 jailbreak as well as new iOS 5.0b6 iPad 1 jailbreak:
Apple updated the iPad1 iOS5b6 IPSW without changing its version number or filename, so we’re releasing redsn0w 0.9.8b7 to handle both the original and changed IPSW. We’ve also added explicit support for a tethered 4.3.5/4.2.10 jailbreak (instead of pointing at the 4.3.4/4.2.9 IPSWs) and fixed a 4.2.10 problem.
We’ve released redsn0w 0.9.8b6 to jailbreak iOS5 beta6 (point it directly at the beta6 IPSW).
Two important notes about this version:
(1) Please let your device boot normally to IOS5b6 and do a clean shutdown (slide to power off) before jailbreaking.
(2) Boot logos have intentionally been disabled for now, so you’ll see a black screen on tethered boots (you can re-enable logos or verbose boot with command-line options if you really want them back).
Due increased sensitivity to abrupt filesystem shutdowns in IOS5b6, it’s very important that you do a clean shutdown before running redsn0w.
redsn0w has been updated to 0.9.8b5, adding support for Apple’s new iOS5 beta5 (point it directly at the beta5 IPSW). Please use this only if you’re a jailbreak app developer with a legit Apple dev account, and remember it’s a tethered jailbreak for now!
You can download RedSn0w 0.9.8b5 for Windows and Mac OS here.
The iPhone Dev-Team has released RedSn0w 0.9.8b3 which can perform a tethered jailbreak on iOS 4.3.4. This means that you will have to connect your device to a computer and run redsn0w each time you restart.
For the convenience of kernel hackers like @comex and @i0n1c, we have a new redsn0w 0.9.8b3 that supports a TETHERED jailbreak for iOS 4.3.4 on all devices that have 4.3.4 except the iPad2. The vast majority of people will want to stay back at 4.3.3 because that’s where the untethered jailbreak is! There are no new features in 4.3.4 – only fixes for jailbreak exploits.
Also, this is a good time to remind everyone (since we’re still seeing confusion about this): iPad2 owners with a baseband (3G or CDMA) cannot currently use saved blobs to go back to 4.3.3 once the signing window is closed. This is unlike every other device, so don’t be confused! iPad2 owners with basebands should stay away from all updates to maintain your jailbreak!
This jailbreak works with iPhone 3GS, iPhone 4, iPad 1, iPod Touch 3G and iPod Touch 4G. It does not work with iPad 2.
You can download RedSn0w 0.9.8b3 from here: (Mac, Windows)