How to downgrade iPhone4S iPad2 and The New iPad using Redsn0w 0.9.11b1
0
How to downgrade iPhone4S iPad2 and The New iPad using Redsn0w 0.9.11b1
The new Redsn0w 0.9.11b2 has been released now which will allow A5+ device users who have saved their SHSH blobs previously to be able to downgrade their firmware. This was not previously possible since the previous downgrade method required the limera1n exploit which does not exist on A5+ devices. Remember that you must have saved the SHSH for the firmware you wish to downgrade to while that firmware was being signe for this to work. If you did not save your SHSH this will not work(and no, you cannot use an SHSH from a different device).Now there is one major downside to this method so please take caution if you are a Gevey unlocker. A more detailed release log can be found at the bottom of the post:
- The A5 downgrade method actually updates to the latest firmware before downgrading to the earlier one.This process updates your baseband to whatever is newest. DO NOT USE THIS METHOD IF YOU RELY ON UNOFFICIAL UNLOCKS of your iPhone4S. Those who used the temporary SAM technique to unlock their iPhones to specific SIMs shouldn’t be affected by this baseband update.
Redsn0w 0.9.11b2 - OSX
Redsn0w 0.9.11b2 - WIN
iOS Firmware - You will need both the firmware you wish to downgrade to and the most current firmware(5.1.1)
Step 1: Download Redsn0w 0.9.11b1 from above. Also download the iOS5 firmware file you wish to downgrade to and ALSO download the latest iPhone firmware available(5.1.1 currently).
Step 2: Now open Redsn0w(run as administrator if you're on Windows) and go to and select the new Restore utility which can be found under Extras -> Even More -> Restore
Step 3: Now click the
"IPSW" button and Redsn0w will ask you to browse for the IPSW you want
to restore. The first IPSW you need to select is the one you ultimately
want to end up on. In my case I will be restoring to 5.0.1 so I can
jailbreak my 4S so I will select the 5.0.1 firmware first. Immediately
after selecting the 5.0.1 firmware, I will then select the 5.1.1(most
current firmware) that I downloaded earlier. As soon as you select the
5.1.1 firmware, a large warning will pop-up explaining to you the
baseband update and how users with an unlocked iPhone using Ultrasn0w or
Gevey will lose the ability to unlock, click "Yes" to proceed.
If you have any questions, as always, don't hesitate to ask in the comments section! Below is an entire list of the Redsn0w 0.9.11b1 changelog:
- The new feature is at Extras->Even More->Restore
- You cannot downgrade without the personalized SHSH blobs for your device at that lower firmware. You need to have fetched those blobs while the signing window was open, using either Cydia’s built-in TSS@Home feature, or with TinyUmbrella. The new Restore screen of redsn0w lets you choose either the remote blobs or local ones (for the earlier firmware). If you don’t know where TinyUmbrella put your blobs, TinyUmbrella has a button that will show you (copy them out of that folder and feed them to redsn0w).
- The A5 downgrade method actually updates to the latest firmware before downgrading to the earlier one.This process updates your baseband to whatever is newest. DO NOT USE THIS METHOD IF YOU RELY ON UNOFFICIAL UNLOCKS of your iPhone4S. Those who used the temporary SAM technique to unlock their iPhones to specific SIMs shouldn’t be affected by this baseband update.
- This method can be fixed by Apple with a firmware update. It’s a (pleasant) mystery why they haven’t fixed it yet, because reverse-engineering of the restore ramdisk indicates they do know about it. It’s possibly too niche to bother to fix right now.
- The least-tested devices with this method are the iPad2,3 and iPad3,2 (because we don’t have those models). If you do and you feel like experimenting, please let us know how it turns out in the comment section below!
- This update involves a bunch of new redsn0w code. We recommend sticking to the previous version 0.9.10b8b unless you’re specifically using this new feature, until all the bugs are worked out! (Note: If redsn0w gets stuck at the “Waiting for device” stage for more than 30 seconds, you’ve hit a pesky GUI bug…that will be fixed in an upcoming version!)