Share:

1.1.2 OTB Unlock Update

Share:

For those who have been following the online forums about the iPhone software unlock, you may have heard some conflicting reports. Recently, a video has been released showing a jailbreaked 1.1.3 iPod Touch! That means 1.1.3 has been in fact jailbreaked! Haven’t read about the 1.1.3 hardware unlock? Read it here.

However, one notable hacker, Geohots, posted on his blog stating that a 1.1.2 software unlock will most likely not happen. This news probably has scared a bunch of you out there that are patiently waiting with your 1.1.2 OTB iPhones! There seems to be some sort of drama going on right now within the Dev Team itself.

pspsully posted on the Hackint0sh forums a brief update for us, explaining the current situation. In a nutshell, a couple members of the Dev Team spent money and sacrificed six ($2400US!! Not donation funds) iPhones a few days ago attempting to get access to the 1.1.3 secpack–until word came out that other Dev Team members had the secpack for over a week but did not share it! IMTH and TA_MOBILE worked together with Geohots to release the 1.1.2/1.1.3 hardware unlock that I posted about previously. So basically, pspsully believes a 1.1.2 OTB software solution is indeed possible, but it will take everybody working together, to stay ahead of the “cat and mouse” game.

Here’s the video of the jailbreaked 1.1.3 iPod Touch…as you can see Installer icon on the Springboard, plus the new feature from 1.1.3:

So there you have it…let’s be patient and wait to see what happens over the next few weeks. Using your iPhone with Rogers or Fido could come sooner than you think! Make sure you subscribe to my RSS feed so you can find out the latest! Thanks to everyone for sending in the tips and posting awesome updates in the comments! 🙂

PS – Thanks for the beer, Raz! =)

PPS – Notice I have a new header image! Can somebody help me with the CSS on how to push the menu bar down? Thanks! 🙂

If you enjoyed this post, please subscribe to my RSS feed, so you won’t miss any updates!

Share:

  • Pingback: 1.1.2 OTB Unlock Update()

  • Dusty

    Nice video, I have seen many of them and I just don’t know how real or fake they are lol Until the time comes of a release 1.1.3jailbreak, then well… that would be awesome haha
    Thanks

  • Dusty

    Nice video, I have seen many of them and I just don’t know how real or fake they are lol Until the time comes of a release 1.1.3jailbreak, then well… that would be awesome haha
    Thanks

  • Dusty

    Here is some news about the 1.1.3FW Jailbreak….

    About Jailbreak

    The reason we are delaying the release of the jailbreak is that we don’t want (you know who) to know how we did it.We can’t and we won’t release a full decrypted image of 113 because that would constitute a copyright infringement and we DO NOT support piracy.
    So, concentrate on the 1.1.3 ramdisks. Get them by hardware, bruteforcing or whatever method you come up with.
    We’d like to keep the vulnerability open so that whatever the current version is at the time the SDK is released will be breakable.

    I hope you understand.

    Well I guess we still have a while before we see a release… 🙁

  • Dusty

    Here is some news about the 1.1.3FW Jailbreak….

    About Jailbreak

    The reason we are delaying the release of the jailbreak is that we don’t want (you know who) to know how we did it.We can’t and we won’t release a full decrypted image of 113 because that would constitute a copyright infringement and we DO NOT support piracy.
    So, concentrate on the 1.1.3 ramdisks. Get them by hardware, bruteforcing or whatever method you come up with.
    We’d like to keep the vulnerability open so that whatever the current version is at the time the SDK is released will be breakable.

    I hope you understand.

    Well I guess we still have a while before we see a release… 🙁

  • Dusty

    Here is some news about the 1.1.3FW Jailbreak….

    About Jailbreak

    The reason we are delaying the release of the jailbreak is that we don’t want (you know who) to know how we did it.We can’t and we won’t release a full decrypted image of 113 because that would constitute a copyright infringement and we DO NOT support piracy.
    So, concentrate on the 1.1.3 ramdisks. Get them by hardware, bruteforcing or whatever method you come up with.
    We’d like to keep the vulnerability open so that whatever the current version is at the time the SDK is released will be breakable.

    I hope you understand.

    Well I guess we still have a while before we see a release… 🙁

Deals