Advertisements

Pod2g has been letting his fingers do the talking again, this time updating his official blog to let his followers know the direction he is taking in regards to his eagerly anticipated iOS 5 untethered jailbreak. First of all some background incase any of our readers stumble upon this article by chance or have missed previous reports relating to this.

iPhone-4S-21

In November, former Chronic Dev Team member pod2g tweeted for the attention of the jailbreak world, announcing that he had found a bug in iOS 5 which he believed could be useful in the pursuit of the elusive untethered jailbreak. Various follow up blog posts followed at the beginning of December informing readers that of the status of the development relating to individual devices. One stumbling block was the fact that pod2g did not own an A5 powered device (iPad2 or iPhone 4S) and therefore would find it extremely difficult to test his proposed jailbreak on these devices without needing to hand his code and exploit over to a third party. He implicitly expressed that he did not wish to do this through fear of it being leaked.

Various donators coming forward allowed the developer to purchase both devices for testing purposes and continue down the development route. On December 19th; an important blog update was posted, letting the world know that he was experiencing issues with the process on the iPhone 4S on iOS 5.0.1 due to memory cache issues relating to the Cortex-A9 cache management. To most this may sound like a showstopper but less than 24 hours later he announced that the cache management issues were no more, and that he had successfully overcome them.

Note, if you are a particular tech minded person, pod2g posted a link which explains the issues relating to self modifying code on the ARM platform.

The next update came in the form of a teaser video (which you can read about here), posted to show that the iPhone 4 untethered jailbreak for iOS 5.0.1 has been successful and is running on his device without issue. The post continued, informing readers that they can expect the same stability as is seen with Redsn0w as the jailbreak uses the same patches and that work on the A5 devices would continue.

Which takes us nicely to the present day, and the most recent blog post. After reading various comments on his own blog, pod2g has felt the need to reply to clarify one or two issues. One concern, which is always present when about to release a new jailbreak, is whether or not the release should be delayed until the next big release of iOS (version 5.1 in this case) to preserve the exploit. The issue comes from the fact that the jailbreak is being developed for a point release of iOS, meaning that the exploit could be closed by Apple come the release of iOS 5.1. Believing that the Chronic Dev Team have the experience and expertise necessary, pod2g has passed all of his research, work and information across to them to allow a speedy release of the A4 jailbreak.

Until then, you can follow our instructions posted here on how to jailbreak using Redsn0w, or here using Ac1dSn0w (instructions with Ac1dSn0w Beta 2 here), or here using Sn0wbreeze.

The hope is that he can now focus solely on progressing the jailbreak for both current A5 devices.

(via pod2g’s iOS blog)

You can follow us on Twitter, add us to your circle on Google+ or like our Facebook page to keep yourself updated on all the latest from Microsoft, Google, Apple and the web.

Advertisements