Help Pod2G Find Another 5.1 Untethered Jailbreak

Pod2g is already starting to look for exploits to use for the untethered jailbreak for iOS 5.1 and he can use your help.  He is asking to keep an eye out for anything hat makes your iPhone crash.  “You can help if you can crash either a core application (Safari, Mail, etc…) or the kernel in a repeatable way. A kernel crash is easy to recognize : it reboots the device.”

Please only email pod2g if you can explain how the crash happened and if you can duplicate the crash.  Also, don’t email him if the crash was from an app from the app-store or any other non stock application.

Read more from Pod2G’s Blog:

To jailbreak a device, hackers need a set of exploitable vulnerabilities :

• a code injection vector : a vulnerability in the core components of iOS that leads to custom, unsigned code execution.
• a privilege escalation vulnerability : it’s usualy not enough to have unsigned code execution. Nearly all iOS applications and services are sandboxed, so one often need to escape from the jail to trigger the kernel exploit.

• a kernel vulnerability : the kernel is the real target of the jailbreak payload. The jailbreak has to patch it to remove the signed code enforcement. Only the kernel can patch the kernel, that’s why a code execution vulnerability in the context of the kernel is needed.
• an untethering vulnerability : when the device boots, it is unpatched, thus cannot run unsigned code. Thus, to start the jailbreak payload at boot time, a code execution vector either in the services bootstrap or in the loading of binaries is mandatory.

You can help if you can crash either a core application (Safari, Mail, etc…) or the kernel in a repeatable way. A kernel crash is easy to recognize : it reboots the device.

Important facts :

• Always test on the latest iOS version before reporting a crash (at the time of writing, iOS 5.1)
• Be sure to not report crashes to Apple : on your iOS device, go to Settings / General / About / Diagnostics & Usage,  and verify that “Don’t Send” is checked.
• Not all crashes are interesting : aborts, timeouts or out-of-memory kind of crashes are useless. Verify the crash dump in Settings / General / About / Diagnostics & Usage / Diagnostic & Usage Data that the crash report you created is of Exception Type SIGILL, SIGBUS or SIGSEGV.
• The crash should be repeatable, which means you should know what exact steps produced it and how to reproduce it on another device.

How and where to report :

• Send an email to ios.pod2g@gmail.com detailing the steps to produce the crash and the associated crash report.

Thank you very much for reading & helping !

~pod2g

If you found this post useful, hit the +1 (recommend) button ?

Waiting for an untethered jailbreak for iOS 6? Join our Newsletter and receive an email when the jailbreak is public! (click here)

You can follow us on Twitter, join our Facebook fanpage and add us on Google+ to keep yourself updated on the latest jailbreak and unlock news.

-