166w ago - Today KaKaRoTo has introduced a common repository of payloads that can be used by any PS3 JailBreak implementation called PL3, and also said he is making progress with PSFreedom ports for PS3 Firmware 3.01, 3.10 and 3.15.
To quote: "I'll announce two things, first, let's talk about PL3.. PL3 is a new project I started in order to have a common repository of payloads that can be used by any 'jailbreak' implementation. I got tired of copying payloads from PSGroove, and I had some nice changes in mine that I thought the PSGroove project could benefit from, so I thought I'd create a single repository that both projects, PSFreedom and PSGroove (or any other similar projects) could use.
You can find it in github, so don't hesitate to submodule it and use it.
Second important news... I've bought a new PS3 just for homebrew. Thanks to all who donated money so I can buy it (I didn't get enough donations to pay for it, but enough to help me). I bought this PS3 used and it came with firmware 3.01! This is good and bad news : I can't use PSFreedom to jailbreak it, so i've put on hold any improvements for it, however, it will allow me to actually port PSFreedom to older firmwares! My plan is to get the jailbreak working on 3.01, then move on to 3.10 and 3.15 (depending on how hard it is, i might skip 3.10).
Another good news is that after 4 days of work, I was finally able to dump the LV2 memory from the 3.01 firmware, and now all that remains is to find the right offsets to patch, and port PSFreedom to 3.01, so all those who are still using this firmware version, you will soon be able to jailbreak it! Once I'm done with that, I'll try to do the same with the 3.10/3.15 firmware versions!
To dump LV2, I used a trick and algorithms found by marcan42, so big thanks goes to him, as well as many other people who helped me out, RichDevX and Aaron in particular. I used RichDevX's idea of ignoring the JIG and bruteforcing the address in which the port1 descriptor gets stored until I get a hit, then use that payload to dump lv2, then find the right JIG offset for that particular firmware from the dump. Marcan's trick was to send the data through the ethernet cable by using LV1 only hypercalls, and it worked!
Now the latest git version of PL3 has a new 'dump_lv2′ payload which you can use, it is firmware independent, and only uses LV1 hypercalls, so it should just work... It will dump all the lv2 memory through ethernet, so fire up wireshark, save the dump to a .pcap file, and use the tool in PL3/tools to extract the memory dump from the .pcap file.
In other news, I will soon upload to Ps3utils an .idc script that will search and find the syscall table, and correctly resolve all of its functions and name them properly.. maybe even have it automatically find all functions of a dump in order to save time creating procs in IDA. I'll let you know once I'm done with it."
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Ermm - because that's what his newly acquired "dev" PS3 is currently on and - as I've mentioned above - the more various FWs you can get fully dumped / look at the more details about internal functionality we can all obtain. It's also a good practise for the FUTURE updates as locating of the correct entry points to patch the FW on the fly would be in principle quite similar And - maybe just for FUN!
It is really that simple to just check and compare files and see what they are. then to compare it to info that $ony has given us that details waht the changelog is and the new features and then slowly implent them into anew "CFW" and load them via the usb loader. i myself have been looking into this and have made a lot of progress. just taking my time.
It is easier to go from older versions and up and see how this have progressed instead of taking a shot in the dark and going through everything on newer versions.
The concerns i have are:
1. Original JB was supposed to be updateable.
2. What is exactly different in this payload that makes it work on 3.15 and 3.42?
3. Do they have this up and running?
4. When will it be out and will the scene get to it faster before a paid version?
5. Is this just another ploy for get money and run?
6. IS there a new loader/CFW to make this happen?
7. Is this still Team JB working on it?
PS - i should have a payload working and released by next week. wink
This is more important indeed but not as easy (if even possible) to do as Sony obviously PATCHED this exploit from 3.42 onwards so I doubt it would be possible to use it in the same way just by "relocating" the payload's absolute addressing.
So - on other side - JB-ing the multiply FW versions downwards from 3.41 will not only help to get more devs on board as some of them are holding from upgrading above 3.15 for obvious reason but by giving us multiply dumps from various FW version it will give us a good idea how the FW devevelops and vary from version to version.