When rest of the world is enjoying on Sunday, iPhone Dev Team is hard at work to give out goodies to their jailbreak fans! The team has just released redsn0w 0.9.15b1 bringing support to restore to older firmware no longer being signed by Apple with testhed jailbreak support for Apple TV 2G on iOS 6.0. Which means that you can easily restore an iOS device between iOS 5.x if you have saved SHSH blobs on Cydia server or locally. If you have the correct SHSH blobs you can easily restore your device from iOS 5.1.1 to 5.0.1, iOS 5.0.1 to 5.1.1, iOS 5.1.1 to 5.1.1, and iOS 5.0.1 to 5.0.1. In addition, with Redsn0w 0.9.15b1, Cydia option is now included and you need not follow a complex route to install Cydia manually, which we did it while jailbreaking iOS 6 earlier.

Redsn0w 0.9.15b1 now allows you to choose “Just Boot” tethered option when your jailbroken iPhone, iPad or iPod touch connects in DFU mode. It also supports untethered hactivation on jailbroken iPhone 3GS or iPhone 4 running iOS 6.0 (10A403) firmware.

For Pre-A5 device owners (iPhone 4, iPhone 3GS, iPod touch 4G and iPad), iPhone Dev team has eased the process of downgrading the iOS mobile operating system. Users can now directly restore pre-A5 devices to earlier firmware without stitching the blobs, fixing awkward iTunes errors, and “hosts file” issues. We will be posting guide on how to downgrade iOS devices easily. Here’s what hacker @musclenerd suggests to all jailbreakers.

redsn0w 0.9.15b1

Redsn0w 0.9.15b1 high-level new Feature list:

  • restore from any 5.x iOS to any other (up, down or the same) 5.x iOS on all devices as long as you have the correct blobs (see more below)
  • Cydia now included in the tethered 6.0 jailbreak on A4 devices
  • automatically “Just Boot” tethered when qualifying A4 device connects in DFU mode
  • untethered 6.0 jailbreak on old-bootrom 3GS
  • untethered 6.0 hactivation on any 3GS or iPhone4
  • directly restore pre-A5 devices to earlier firmware – no more complicated 15-step how-to’s with stitching, iTunes errors, and “hosts file” concerns
  • fetch new signed blobs for any IPSW (present or future — no redsn0w update required) using Extras->SHSH Blobs->New
  • block the BB update for any 3GS or iPhone4 restore (past, present, or future - no redsn0w update required) using Extras->Even More->Restore
  • deactivate any iPhone, useful for testing your “official” unlock status through iTunes.  (Please only deactivate your own iPhone!)
  • activation status shown on “Even more” page
  • significantly more (very nerdy) info returned by “Identify” button when device is in Normal mode
  • Tethered jailbreak of ATV2 supported (but the only thing available for it is the SSH2 custom bundle available here - no Cydia yet.  Must use “Select IPSW” for tethered boot of ATV2 for now).
  • Auto-exit WTF mode for older devices with broken buttons
  • any time a set of blobs is fetched remotely (from Apple or Cydia), redsn0w also saves them locally (and will check there first if you click “Local”)
  • For your future restoring convenience, you should also submit all of your past and present TinyUmbrella blobs to Cydia if you haven’t done so yet.  Resubmitting is okay and won’t cause conflicts.

Here are more details on the iOS5-to-iOS5 restores for A5+ devices.  (Note: pre-A5 devices don’t have these restrictions – just follow the redsn0w prompts during the restore).

1. redsn0w now lets you restore an A5+ device from any iOS 5 to any other iOS 5 as long as you have correct 5.x blobs for the starting (current) and ending points of the restore

  • APtickets eliminated “higher-version only” comparison of firmware restores (just like BBtickets did for the baseband)
  • Example restores supported by redsn0w if you have the correct blobs: 5.1.1-to-5.0.1, 5.0.1-to-5.1.1, 5.1.1-to-5.1.1, 5.0.1-to-5.0.1
  • if you don’t have the blobs locally, let redsn0w try to fetch them remotely (redsn0w always tries both Apple and Cydia).  Any successful remote fetch also saves a local copy too.

2. You DO NOT QUALIFY for iOS5-to-iOS5 restores if you got to your current 5.x via an OTA update

iPhone Dev team further clarifies that those users who have updated their most current iOS 5.x via over the air update (OTA) doesn’t qualify. Hacker musclenerd said that the tickets saved by Cydia, redsn0w tool, or TinyUmbrella do not cover OTA update ramdisk images yet. Even the devices from fresh factory restore doesn’t qualify. Those users must simply stay away for downloading and using redsn0w 0.9.15b1.

  • The tickets saved by Cydia, redsn0w, and TinyUmbrella do not cover OTA update ramdisk images
  • Even if they did, it’s the “wrong kind” of ramdisk (you’d need to start at that earlier pre-OTA FW)
  • Devices fresh from factory or refurb may fall in the “does not qualify” category (your results will vary)
  • It’s okay if you previously got to 5.x via an OTA update, as long as your current 5.x was installed via a normal iTunes restore.  All that matters is how you got to your current 5.x most recently
  • Redsn0w detects an OTA/normal-restore APticket mismatch very early, so if you don’t know your status there should be no harm in trying.  Any device in recovery mode after such a mismatch can boot normally again just by going back to “Even More” screen from the “Restore” screen (or use “Recovery Fix” if you quit redsn0w before doing that).

3. Unlike the A4 devices, redsn0w can’t (usefully) prevent the baseband updates of A5+ iPhones and iPads.

  • Redsn0w automatically flashes the currently signed baseband when it does A5+ restores, even if those basebands didn’t come with the original firmware
  • Stay away from this if you have an unofficial unlock that isn’t supported by the newest baseband
  • The least-tested baseband update code in redsn0w is for iPad2,3 and iPad3,2.  Please give any feedback on those iOS5 restores in the comments section below.

4. iPad 2 owners (all three models) with saved 4.x blobs can use those instead, even from 6.x

The dev-blog re-iterated that it’s possible to downgrade from iOS 6.0 to iOS 5.x on iPad 2 provided that you have SHSH blobs on 4.x and 5.x. Interestingly, if you have SHSH blobs for only iOS 4.x but not for 5.x blobs, you can downgrade iPad 2 from iOS 6.x to iOS 4.x.

  • If you have both 4.x and 5.x iPad 2 blobs, you can always get to 5.x via the 4.x blobs, even if you’re currently on 6.x
  • You cannot get to 5.x from 6.x without the 4.x blobs (but you may still qualify for the iOS5-to-iOS5 restore described above)
  • If somehow you have 4.x blobs but no 5.x blobs, you can still go down to 4.x from 6.x
  • This only applies to iPad 2 owners (they’re the only A5+ devices that ever had a public 4.x FW)
  • Redsn0w still supports (but doesn’t require) jailbreaking A5+ devices at 5.0.1 and 5.1.1.  Just head back to the first page after re-restoring to 5.x.  It’s always much faster to jailbreak those FW versions with a freshly-restored device, before letting iTunes restore from a saved userland backup.

5. Ultrasn0w isn’t yet updated for 6.x

Most iPhone unlockers are waiting anxiously for the free Ultrasn0w unlock support for iOS 6.0, but unfrtunately, it is not updated yet. We would however, suggest to ask @chronic as he is currently unlocking AT&T iPhone 4,iPhone 4S and iPhone 5 for throwaway prices. Here’s what iPhone Dev Team has to say about Ultrasn0w iOS 6.x update

  • By now you probably should be taking advantage of the extremely cheap IMEI-based unlocks of iPhones sold by established online retailers like cutyoursim.com
  • still, IMEI-based unlocks don’t work in all cases.  We’ll announce when ultrasn0w is ported up to 6.x
  • redsn0w will still hactivate your 3GS or iPhone 4 if you run it before the device is activated.  Due to the current tethered 6.x JB status, redsn0w now hactivates 6.x without requiring subsequent tethered boots.  If you accidentally hactivate with redsn0w, use the “Deactivate” checkbox available from the Jailbreak screen, not the normal one in “Even more”

6. As always, redsn0w lets you “Fetch” the SHSH blobs currently flashed onto your pre-A5 device

  • Use this if you’re at 5.x or 4.x but without having saved your blobs when the window was open
  • This is only useful when Apple is no longer signing the firmware, otherwise Cydia/redsn0w “New”/TinyUmbrella blobs are superior (but you’re welcome to fetch your 6.0 blobs this way anyway)
  • Fetching blobs in this fashion will automatically forward them up to Cydia, as well as save a local copy

Download Redsn0w 0.9.15b1 Links

Stay tuned! We will update you along with full tutorial guides on downgrade iOS between iOS 5.x and re-jailbreak it. To get timely notification, follow Jailbreaks on Twitter or Facebook. If you have any other issue related to jailbreaking jump to jailbreak forum to seek help or post your queries under the comments section.

Tagged with →  

Like This Story? Please Share!

Like Our Site? Follow Us!

CydiaBlog on Google+
  • kevin

    i have a question what if my iphone 4s will downgrade to 5.1.1 from 6.0 is there a conflict or error? help please i want to go back to iOS 5.1.1

  • Frikki

    When iPad 3 5.1 or 6.0 jailbreak? New iPads from store have iOS 5.1 which has no jailbreak at this moment, and you promouted us in march to make iOS 5.1 ipad 3 jailbreak. Where it is now?????