iOS developer and discoverer of exploits pod2g has updated jailbreaking enthusiasts on the latest status of his untethered jailbreak for iPhone 4S. Details after the jump!
News of the status update comes straight from pod2g’s official blog in the form of a short post in which he briefly discusses his weekend with testing the iPhone 4S with his untethered jailbreak.
Pod2g states that his untethered jailbreak, which works on iOS 5.0.1 on older iOS devices, as of now fails on the iPhone 4S due to “processor cache issues” related to multicore cache management. Still he is, apparently, close to getting it to work but feels that it is all a “matter of chance”.
The untether fails right now because I’m having processor cache issues.
I’m close, but I can’t figure out what happens. It certainly has something to do with the multicore cache management.
I could sort it out quick, it’s a matter of chance.
Pod2G’s jailbreak is likely based on software-based (userland or kernel) exploit which means that a. there are relatively high chances of it working on iPhone 4S and iPad 2 and b. Apple will patch the exploit by releasing a software update (iOS 5.0.2 or iOS 5.1).
He seems quite optimistic to us, so we’re hoping that he’ll manage to get the iPhone 4S untethered jailbreak working very soon! Keep in mind that since the iPhone 4S and iPad 2 are based on the same A5 chip, once a jailbreak works on one device, it should be relatively easy to make it work on the other.
In a previous blog post, pod2g did confirm that coding and testing for his untethered jailbreak is complete for devices like the iPod touch 3G, iPhone 4 (GSM), original iPad and iPhone 3GS on iOS 5.0.1. The only thing that remains between this jailbreak and jailbreaking enthusiasts is packaging the code for public release and actually releasing it.
We will, of course, keep you updated about the latest on the iOS 5.0.1 jailbreak, so stay tuned to Redmond Pie!
Update: Pod2g has just posted another update on his blog regarding iPhone 4S untethered jailbreak. The processor cache issues that he was having earlier has now been resolved.
OK, figured it out, the A5 cache is not a problem anymore. I sorted it out by doing the untether in a single thread and by flushing all the dcache then all the icache in a row at a strategical point of the process. It took me like a hundred of tests to find the key. Hard for the nerves.
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.