Difference between revisions of "Talk:Usb control msg(0xA1, 1) Exploit"

From The iPhone Wiki
Jump to: navigation, search
Line 26: Line 26:
   
 
But really, you could execute an unsigned ramdisk, have it patch the kernel at boot (so no recovery mode), and userland jailbreak. Untethered? --[[User:Palz|Palz]] 21:41, 30 September 2010 (UTC)
 
But really, you could execute an unsigned ramdisk, have it patch the kernel at boot (so no recovery mode), and userland jailbreak. Untethered? --[[User:Palz|Palz]] 21:41, 30 September 2010 (UTC)
  +
:Where would this ramdisk come from that patches the kernel at boot?? Ramdisks only come from Recovery/DFU mode which is what SHAtter is all about. But if this ramdisk's purpose is just to drop in a dynamic library / binary you can convince iOS to execute that uses another userland exploit in some framework, then you would have an untethered jailbreak.

Revision as of 21:46, 30 September 2010

Is this even suppose to be here? :S

iH8sn0w 00:31, 21 September 2010 (UTC)

Pod2g posted it himself so I don't see much of a problem for it as it doesn't sound like it will work on new devices. --OMEGA_RAZER

So would this exploit lead to a tethered jailbreak or would it be untethered? --JacobVengeance 01:50, 21 September 2010 (UTC)

Tethered. This just allows unsigned code execution to be performed regardless of SHSH or model revision at the DFU/bootrom level. This is useful for redsn0w or blackra1n type hacks as they provide a quick and unclosable exploit to perform the actual jailbreak. Functionally, this replaces the need for sending 2.1.1 iBSS + iBEC to use Arm7Go or the 3.1.2 iBSS/iBEC (if that can even be done?) for that other USB control msg exploit in 3.1.2 iBoot. Iemit737 02:37, 21 September 2010 (UTC)

the new bootrom ipod touch 2g where ipod touch 3g so will this exploit work on ipod3g and iphone 3gs --liamchat 14:51, 21 September 2010 (UTC)

I don't completely understand your question, but no, this exploit will work on nothing other than the 2nd generation iPod touch (and is not particularly big news, since we can already run unsigned code on the second gen touch). AriX 18:01, 21 September 2010 (UTC)

Pod2g : I released this one because it's old devices only (Apple engineers already found and fixed it). The good thing about it, is that it's a way to execute unsigned assembly code easily in the context of the bootrom. Researchers can use it to explore the bootrom, try things, etc. Also, maybe it could be useful for iDroid ?

palz2015 : So could it be untethered using the exploit to run code that patches the kernel, and preform a userland-only jailbreak, just from DFU?

no because the exploit will replace the rdisk with a pwnd one ( that will fail the check ) and cydia will need to know how to use the exploit but you can re inject apple's rdisk --liamchat 18:55, 27 September 2010 (UTC)

What are you talking about? Filesystem modification causes no problems, dropping in a dylib, adding a daemon for a userland jailbreak and changing FStab is a fully functional jailbreak. Also cydia does not have knowledge of how to use any exploit... Iemit737 21:19, 30 September 2010 (UTC)

What is classified as a 'New Device'. Would an iPod Touch 2G with the 2nd revision of the S5L8720 bootrom be classified as a new device? --ac3xx 17:44, 30 September 2010 (UTC)

The second revision of the touch 2G does have this exploit, but no devices after that. Iemit737 21:19, 30 September 2010 (UTC)

But really, you could execute an unsigned ramdisk, have it patch the kernel at boot (so no recovery mode), and userland jailbreak. Untethered? --Palz 21:41, 30 September 2010 (UTC)

Where would this ramdisk come from that patches the kernel at boot?? Ramdisks only come from Recovery/DFU mode which is what SHAtter is all about. But if this ramdisk's purpose is just to drop in a dynamic library / binary you can convince iOS to execute that uses another userland exploit in some framework, then you would have an untethered jailbreak.