Jailbreakers And Unlockers Are Advised To Stay Away From iOS 5.1 Update


by cM Boy on March 8, 2012

iPhone Dev Team has updated a blog post to warn jailbreakers and people who care for unlock of their device to stay away from iOS 5.1 update.

Apple has just shown their new device, the new iPad and iOS 5.1 will be rolling out soon for the new device along with other supported devices.

Its a good time to warn people not to update to iOS 5.1 because a lot of users specially the new ones to the jailbreaking world upgrade their device and end up loosing the jailbreak or an updated baseband which results in a locked device.

ios 5.1

This is what the dev team has posted:

In all likelihood we’ll see the GM “gold master” version of 5.1 this week. DO NOT UPDATE TO 5.1, because you may lose your jailbreak! The rest of this post details the subtleties with this rule, but if there’s only one message to take home, it’s the overall “do not update” message! Now for the nitty gritty exceptions:

  • Soon after 5.1 appears on Apple’s public servers (i.e. iTunes starts to offer it), Apple will stop signing 5.0.1 SHSH blobs.
  • If you have an iPhone4S, the basic rule above is really the only rule: you cannot restore back to 5.0.1 once the 5.0.1 signing window is closed, no matter what (even if you saved your SHSH blobs).
  • If you have an iPad2 with saved 4.x hashes, you can in fact downgrade to that 4.x but you won’t be able to get to 5.0.1 once the 5.0.1 signing window is closed (even if you saved your 5.0.1 SHSH blobs).
  • If you have a device earlier than the iPad2, you can downgrade to whatever version you want, as long as you have saved SHSH blobs for that version. You’ll need the assistance of geohot’s limera1n exploit with tools like redsn0w to get into “pwned DFU mode” and bypass the downgrade restriction.

We cover all jailbreak and unlock news. Proof is our homepage VeryRite.com. Make sure you follow us.

Follow us on TWITTER or Like Facebook Page to stay connected to get daily Internet News.

We Write Very Rite

Previous post:

Next post: