Great news for jailbreakers this morning, with the release of the long awaited new version of redns0w, including restoration options for iPad2 and iPad3 owners on 5.x firmwares looking to re-install 5.1.1 and re-jailbreak! redsn0w version 0.9.15b1 is available from the dev-team blog - Dev-Team Blog You can find our tutorial on re-restoring IOS 5.x here - http://www.ipadforums.net/jailbreak...5-x-ipad2-ipad3-using-redsn0w-shsh-blobs.html Here are the (iPad specific) features of the new tool in the meantime... The tool also includes the official public tethered jailbreak for A4 devices on IOS6 (including Cydia installation), but this is of course nothing to do with the iPad, since the iPad1 cannot run 6.0. Here are more details on the iOS5-to-iOS5 restores for A5+ devices. 1. redsn0w now lets you restore an A5+ device from any iOS5 to any other iOS5 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 succesful 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 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. and so, 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. iPad2 owners (all three models) with saved 4.x blobs can use those instead, even from 6.x if you have both 4.x and 5.x iPad2 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 iPad2 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.