Download Redsn0w 0.9.9b1

Redsn0w 0.9.9b1 Released - Tons of New Features


Jailbreaking on the iOS 5 beta is down at your own risk. Note the consequences and possible issues you may run into when using redsn0w on the iOS 5 beta

With iOS 5 on the heels of release, it would make sense that the iPhone hackers are vigorously working hard. Their goal is to ensure that the tools necessary for jailbreaking are ready for the upcoming iOS public release (in this case, iOS 5). Plus they are looking to improve the process and experience in any way possible. This update round with redsn0w certainly made its goal and brought on a ton of new features. MuscleNerd (@MuscleNerd) alerted us yesterday that redsn0w 0.9.9b1 was released and that it houses a ton of new improvements and features. Instead of elaborating in full detail on each component myself, the iPhone Dev-Team Blog prepared a nice summary to what is new with this redsn0w release. The information is below:

Quote Originally Posted by iPhone Dev-Team Blog;
Update #9: A bunch of new features!
  • 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 second 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
  1. Stitching is NOT yet supported on iPhones! Need to work out the baseband part of the restore process.
  2. 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)
  3. 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.
  4. 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.
  5. Will eventually support fetching the blobs directly from Cydia instead of a file on your computer


One thing you may realize from the new update is that after using redsn0w with the IPSW file for the first time, you will never have to pick the IPSW file again. According to MuscleNerd, redsn0w now caches the information from Apple so that you no longer have to choose the IPSW every time you need to reboot tethered (for instance). This is quite handy and is a great addition to redsn0w.

Download redsn0w 0.9.9b1 for your respective system via the following links:

redsn0w 0.9.9b1 for Mac
redsn0w 0.9.9b1 for Windows

Note: The iOS 5 beta firmwares, along with iOS 4.3.4-4.3.5 (and for Verizon 4.2.9-4.2.10), are still tethered jailbreaks. Also, this version of redsn0w is not applicable for the iPad 2

Source(s): MuscleNerd, iPhone Dev-Team Blog

No comments:

Post a Comment