171w ago - We are happy to report that the PS3 Hypervisor LV1 and Bootloader LV0 are dumped from the PlayStation 3's RAM after getting our
SX28 Hardware a few days ago, utilizing code for glitching and mashing buttons for hours - the
exploit eventually will get triggered!
We tried a few different ways to dump out the real memory - the biggest "problem" was the fact that you can't just simply use File I/O code in a kernel module. Furthermore, you can't call the
lv1_peek function from user mode either.
Luckily, resident DEV
kakarotoks was up to the challenge. After some trial and error (and too many PS3 crashes!) he made a
kernel module which maps the "real" PS3 memory to a device in
/proc. The
/proc area lets the kernel and userland interact some.
Basically, the device
/proc/ps3_hv_mem is created when the kernel module is inserted. Once it is inserted, you can use
dd to read the device. By doing this, the device gets passed arguments, which is passed along to
lv1_peek - which in turns reads out the real memory.
Be advised, don't go beyond the PS3's upper memory limit. At around 260MB, the PS3 tends to crash - it does not like trying to read beyond RAM limits! So, for usage:
First, run the exploit, and get it triggered and working - that's the hard part!
Next, download the
attached file, inside are three files, a
Makefile, the
ps3_hv_mem.c and a pre-compiled version. Stick these in a folder, and run make. It will then compile a kernel module for you (
ps3_hv_mem.ko, or use the pre-compiled one). Then simply type:
sudo insmod ps3_hv_mem.ko
Enter your password and check
/proc for a
ps3_hv_mem entry, or your dmesg. If it is there - let the dumping begin!
You can dump out the PS3 Hypervisor and Bootloader (and the rest of the real memory) via
dd. You can use the command:
dd if=/proc/ps3_hv_mem of=PS3_Memory_Dump.bin bs=1024 count=10K
That command will dump out 10485760 bytes, or about 10MB - which nicely includes the goodies like LV0 and LV1. Finally, you can also increase the count, which will increase the amount dumped (multiply by blocksize).
No it won't....
...
Not really, The #1 reason people want a game is to play online. scea knows this. I'm pretty sure they will implement disc ID's once again. the technology has been there since PS2, look at the Socom series, no matter what you did, you could not get online with a backup copy of it, even if you injected an ID into the file. so i think a lot of people will be disappointed. But then again thats just a opinion also...
LOL you know my view of it.
One has been sent in to be fixed at 187 US dollars because as sony says "with the economy being down they were forced to implement their new 29 dollar shipping charge. Now honestly, i have the resources and brains to fix my lasers on my lonesome, but we are talking 3 60 gigs that i would rather have fixed by sony rather than me tearing the seal off only to wait another 3 months and have an unfixable ps3 on my hands that i wouldnt be able to send in to get fixed.
These guys are doing more than just allowing the mass to become "pirates", they are actually turning the tide and putting the consumer in control. With that rant said and done, i commend these guys for the incredible drive to even still be working on this machine for as long as they did and if they can save me money i am more than happy to help and do my part "however small that may be" by HV review, donations or whatever.
I was honestly thinking of buying a FGPA and somehow contacting cjpc to mail it to him. So thanks to the people involved and i will say the pressure you are under from the "people" wanting a miracle overnight must be ridiculous, so take your time, and do what you do best, and if there is anything i can do donation-wise im more than up to it. If your gonna save my hard earned cash from being pocketed by sony, i'm sure i can find some laying around to help out with the cause!