Descrambler has sniffed the code right off PS JailBreak and it could lead to some future possibilities. Here are some quotes taken.
GregoryRasputin takes on this:
The first 8 bytes are from the usb protocol left [09 02 … ]
The code Will be pushed four times onto ps3 usb stack:
Quoted from PS3Exploits:
Just in from RichdevX and Disane. Disane has shared the shell code you can check it out below. Apparently the shell code repeats 32 times and patches lvl2. The code may only run on a certain firmware which explains why the dongle only works on firmware 3.41
This is the disassembled PPC code more like the shell code that is being injected. The best way would be to use the lv2 dump and this to figure out how the stack overflow exploit works in the USB buffer of the PS3 after that it can be reproduced on any FW. On both slim and fat PS3s.
The JIG ID is probably passed to trigger some code pathern which the Configuration Descriptor overflows and injects the shell code after that the code gets executed. The shell code patches lv2 to run fselfs and all kinds of interesting flags which I haven’t noticed yet…
Links to the code below:
Part 1: https://dukio.com/code1
part 2: https://dukio.com/code2
Alternative ASCII binary version: https://dukio.com/cascii
Links provided by: xCoder
Microcontrollers USB Stick Tool are the likely USB candidates for developing the code with(once we find the replicable code exploit) rather than dumping it on your ordinary USB flash drive.
UPDATE: 2 versions of disassembly of what looks like the overflow part for the PPC code.
UPDATE 3: You could also browse our TUTORIALS section to get an idea to create your own PS3 JailBreak.