Pod2g Found New Untethered iOS Jailbreak Exploit! Most Probably Saved For iOS 4.3?


by casey on January 30, 2011

pod2g has found a new vulnerability in the iOS which is expected to bring an untethered iOS jailbreak solution for iPhone, iPad and iPod Touch. The new untethered exploit in iOS makes all registers controllable. Apparently its NOT an untethered iOS 4.2.1 jailbreak solution.

We are not sure when this untethered iOS solution discovered by pod2g is going to be released. Most probably the team is going to save it for iOS 4.3.

Here is an image posted by pod2g:


Image: via pod2g tweet

One of the reason we are expecting why pod2g’s solution will be saved for future is that the Chronic Dev Team is already working to release an untethered iOS 4.2.1 jailbreak solution. Joshu Hill has already posted a teaser video demonstrating iOS 4.2.1 untethered jailbreak. According to the developer the solution is almost ready and they are just fixing few bugs. That solution is expected to be GreenPois0n RC5. It will not require you to have iOS4.2b3 SHSH blobs. It will only require iOS 4.1 IPSW and will do an untethered jailbreak on iOS 4.2.1.

So Chronic Dev Team has now two untethered iOS jailbreak solutions. One is going to be released soon and the pod2g’s solution will be saved for future apparently.

pod2g’s jailbreak solutions seems to be too sophisticated. Thats why the team save it for the next version of iOS. We have a similar example from past. Back at the time when iOS 4.1 was released, pod2g developed SHAtter exploit by collaborating and taking help of p0sixninja who is Chronic Dev Team member. SHAtter was developed to jailbreak iOS 4.1 but GeoHot released Limer1n to jailbreak all iOS devices running iOS 4.1. SHAtter was preserved for next generation devices including iPhone 5 and iPad new version iPad 2.

Stay connected to VeryRite.com to get more news from jailbreak world.

You might also like to see:

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

We Write Very Rite

Previous post:

Next post: