220w ago - Update: This method ended up failing because the LV2 address range is protected by Sony on PS3 with Firmware v3.55, so Netkas and flukes1 are now working on a patch for LV1 instead.

Today Netkas and flukes1 have successfully managed to patch the PS3 lv2_kernel in v3.55 Firmware to allow peek and poke syscalls, meaning PlayStation 3 backup managers and Custom Firmware (CFW) will also be able to make use of them!

From the ReadMe file:Patch to add peek and poke syscalls to PS3 firmware v3.55 by flukes1 and netkas (irc.efnet.net #ps3test)

To create the patched PS3UPDAT.PUP:

1. Use bspatch to apply PS3UPDAT.PUP.bsdiff to Sony's official 3.55 PUP, which is available from their website.
2. Run this from command line: "bspatch PS3UPDAT.PUP PS3UPDAT-NEW.PUP PS3UPDAT.PUP.bsdiff"
2. Ensure that the md5sum of the resulting PS3UPDAT.PUP is: 337831fac6a9b05074f73710c4bb7c86

Geohot didn't put anything IN lv2, everyone is misunderstanding what he said. He was talking about it being dangerous to patch lv2 on 3.55 because SONY put a check in there which is what's causing the issue.

We already have people sitting around messing with eboots to make them boot up. The problem is it is not really a simple setup. We have to wait for someone else to do the work, or figure out how to do it ourselves.

If we can get a system that allows us to drop unmodified files somewhere then I think it is better. At the end of the day I would love to have the games just show up in XMB like on PSP. That way we can just run them right from there. For now though I will not be picky.

Geohot, did not put any "crap" in Lv2. He actually was warning people not to patch Lv2 because he knew of the security that Sony placed in Lv2 with firmware 3.52. Hence the reason he states OMG do not patch Lv2.