68w ago - Following up on the
previous update, this weekend PlayStation 3 homebrew development group
DexL0ve have made available a PS3 patched DEX LV2_Kernel.Self for CEX consoles followed by a revision below that fixes PS3 crashing issues.
Download:
PS3 Patched DEX LV2_Kernel.Self for CEX Consoles /
PS3 Patched DEX LV2_Kernel.Self for CEX Consoles (Mirror) /
PS3 Patched DEX LV2_Kernel.Self for CEX Consoles (Fixed)
Essentially this PKG release is a patched LV2 DEX (Debug / Test) kernel for CEX (Retail) PS3 consoles based on the recent
LV2 Loader release.
To quote: From my limited understanding of PS3 coding and reading the NFO file, that by using the LV2_Loader released by Team Rebug earlier, and by QA flag'ing your CEX machine, this file is basically a patched LV2 DEX kernel that will load fully on your CEX machine and thereby give you some DEX (aka) TEST machine L0VE on your Jailbroken PS3 Console.
From
Cyberskunk: Syscall 8, 9, 10 are broken in this lv2_kernel.self. The patch for 3.55 CEX lv2 has been used which ends up point to the wrong offset. The kernel will still work but if an app calls those syscalls the PS3 will crash. Hopefully it was just a mistake and they will fix it..
Finally, from the included PS3 NFO File:
____ U _____ u __ __ _ ___ __ __ U _____ u
| _"\ \| ___"|/ \ \/"/ |"| / _"\ u\ \ /"/u\| ___"|/
/| | | | | _|" /\ /\U | | u | / U |/ \ \ / // | _|"
U| |_| |\| |___ U / \ u\| |/__| \// |,-./\ V /_,-.| |___
|____/ u|_____| /_/\_\ |_____|\___/(_/U \_/-(_/ |_____|
|||_ << >>,-,>> \\_ // \\ // // << >>
(__)_) (__) (__)\_) (__)_")("_)(__) (__) (__) (__)
`!` So you have a CEX, and wanted some c0ding l0ve .!.
.. D0n't You Miss -_-_- Peek and P0ke ? ...
Finally thanks t0 --> LV2_LOADER <-- you can n0w
If you want some c0ding l0ve on CEX, QA it first <0>
With thanks to Rebug, An0nymous, Dean, graf_chokolo
FIXED 2/6 - Sorry, first release had wrong offset <v>
Codemasters Community Manager Ben Walke has officially unveiled Grid 2 Mono Edition today, which he touts as the ultimate collector's item for ...
...
is too simple find a USB buffer overflow when a exploit is released and give to you access to the ENTIRE system and last question for YOU... WHO obtain the keys of the system ? something that everyone says is impossible is impossible is impossible... Santa Claus ?
My apologize AGAIN for the OT...
The first Jailbreak, exploited a bug in how the PS3 handles connected USB devices, after a precedure bugging/glitching, the Jailbreak device gets read and write access to the ram.
But I'll let the this explain (ps3devwiki.com/wiki/PSJailbreak_Exploit_Payload_Reverse_Engineering). The JIG just tells the PS3 to enter Factory Service Mode, there is no ".self" on a JIG which launches Factory Service Mode.
we got it and that's all that matters eh.
They used the master key and the method aka backdore that sony use with the JIG to inject a factory service mode self for injecting a payload to allow homebrew and all that stuff.
i love psn too much! i'd have to say i like ps3 news a lot more than the "scene"..