46w ago - Following up on his previous release, this weekend PlayStation 3 homebrew developer PsDev has updated PS3Tools GUI Edition to version 2.5 which now includes a new PS3 GUI and features as outlined below.
To quote: To jump right into it, I have added a lot into this version. RCO dumper SFO reader and a whole new GUI form and GUI improvements.
When the program first loads, you're going to be opted to choose the GUI, well remember the original GUI for the main screen? Well I added a new one that took out the Command prompt emulator, made the form smaller and sleeker.
Once you choose the GUI you want it will take you too the specific form, but wait, you want to use the other GUI after your done with your first selection? Well I though of that and instead of having it close after selection it stay's alive until you're done!
Added loading bar on both GUI
Added dialogs to see completion
Add messageboxes for errors and PUP completion
Fixed minor bugs
Fixed Core_os image reader tool
Side Note: All RCO's that are dumped will be shown in the RCO folder.
If you repack any .PKG with they will install on 4.11 DEX. I have had a great deal of fun learning TCL TK and some python to try and make this tool as easy to use as possible for those who don't want to install Macports. Read README and how to use included.
PS3Tools v2 for OSX:
New: no more X11 needed all GUI is written in tcl tk.
Edit Read and Create PARAM.SFO files.
Fail0verFlow make self tool
As of now you can:
unself : F0F unself
unself2 : F0F unself2 See README.txt for mallory instructions.
readself : F0F readself and readself2<
make_self : This is geohot's make_self.
make_self_F0F : F0F make self tool<
make_self_npdrm : This is geohot's make_self_npdrm tool.
package_finalize : This is geohot's tool to make any .pkg installable on WutangrzaCFW.
norunpack : F0F to unpack NOR.BIN.
pupunpack : This will unpack any PS3UPDAT.PUP
pupexplode : This will unarchive all the files from the PS3UPDAT.PUP
ungpkg : This is for unpkg npdrm pkg (works on some .pkg not on others)
unpkg : This is for unpkg of regular pkg (works on some .pkg not on others)
unpack_devflash : it's a simple dev_flash extractor for 3.56+ PUPs --thanks Wargio
make_pkg : This is HACKERSCHANNEL-PS3Py's python script that will make a npdrm .pkg that will install on your PS3.
Extract CoreOs : it's a simple CoreOs extractor for 3.56+ PUPs --thanks Wargio
Edit PARAM.SFO : Edit or read a Game PARAM.SFO file. <
New PARAM.SFO : create a New PARAM.SFO file for your homebrew. <
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!
The Appldr from 3.60 + firmware has been encapsulated in lv0. So we must first access the lv0 (not yet decrypted). In firmware 3.60-instead appldr is independent of other processes. If you change the system so that the install package files installs games appldr using of the firmware 3.55 (which we know keys), so installing a backup managers, which mounts the boot path of the games and then uses the appldr of the firmware 4.00.
That system uses 2 processes appldr, the 3.55, which installs the homebrew, and appldr (that of the Sony OFW) who starts the game 4.00.
A CFW obtained with a scrum of the various self of the core_os (4.00 and 3.55) but with a bit of reprogramming, so that uses two processes, depending on the function
Can unpack any "PS3" Firmware up to date. Gets really fast after first or second use.
A console is built into the program showing you the exact log a cmd would.
Can Decrypt PS3/PSP retail PKG files (Signed by sony installable via OFW).
Can readself of, Appldr, lv0, lv1ldr, lv2ldr, isoldr, EBOOT.BIN or if any of the things that you want to read are not listed on a button you can run a custom command to do it, for example: aim_spu_module.self just type that in where it says input and it will read it. So any file that is possible to use via readself, can be done in a fast manor 1-2 sec.
A full featured .Conf editor. view .Conf files edit them then hit save button when finished.
A awesome Core_os_package tool that can decrypt, extract and encrypt the Core_os_package.pkg all in about 1-2 sec.
Sign pkg for 3.55 or 3.41
UnSELF a file.
Build SELF a file.
Whenever a tar file is modified, it's permissions need to be set, this tool can do that for you. fix the tar file for the following FW. retail fw up to 3.72, debug fw up to 3.72 and retail and debug fw 4.0.
Lets use a example: If you want to unpack a ps3 update just get the PS3UPDAT.PUP
(Don't change the name of any file in ps3 FW keep original) and put in tool folder, run my program click unpack and it will unpack it.
So like if you want to fix tar make sure the update_files.tar stays the same name and put in the main folder where program is located. same for anyfile keep the original name. So it's pretty simple just drag the file that you want the tool to do something with and keep the original name.
Here is a video I made (I am pretty bad a videos) to help it' a tutorial that covers everything. If some one else could make a better one that would be awesome.
Notes: PS3Tools GUI Edition will create two new files for the Core_os_package. "decrypted_core_os" and "CORE_OS_PACKAGE_ENCRYPTED.pkg" don't change the name of the decrypted one or else you won't be able to encrypt it
BETA Tester Thoughts: Tested by jhax78
All those command line tools that takes loads of time and sometimes commands that you need to understand will be replaced by this 1 click tool, even a trained monkey could extract repack sign with this now.. it's taking literally 3 seconds to extract a pup resign or whatever you need to do.
I'm no dev but like to poke around in stuff and i think more ppl think like this with this tool all that is just peanuts now.
Developer PsDev is back again today with another article (psx-scene.com/forums/content/possible-1885/) for everyone to read and enjoy. This time, the topic revolves around a possible PS3 4.0 exploit, and the theory around it. This is information that he would like to share with the scene, in hopes of change and overcoming the current barriers to jailbreaking the PS3 console. Feedback welcomed, as PsDev has put a lot of thought and time into this theory.
OK so lets get right to it. This is a theory, nothing more.
There has been information available for quite some time. and I took it, thought about it, researched and experimented and I come out with my theory below to exploit 4.00 part of the way. This is not a random theory to, this is logical stuff and true facts. I'm providing this info for other devs to look at and lets see if this can work. I don't keep my work to my self, I like to share in give other people chances in discovering stuff. It always makes me happy when someone finds something out using my work, it just tells me I did a good job in describing and helping and they did a good job in listening and learning the material in order to trigger the exploit or whatever it might be.
So the lv2ldr verifys decrypts the lv2_kernal.self. we can get the address of this happening. inside Parameters Layout there are arguments, they are used as commands basically to load a function you want to use. they start in the lv2 @ 0x3E800(seems to be same for other ldrs) that address. There is a argument that is called lv2_in and lv2_out (we have know about these) basically we can use lv2_in to map out the address and lv2_out to map out the address for where the lv2ldr decryptes the self file.
We can make a program like readself basically and get the offset, u8* means read one byte from the address. use that and we can actually be get the exact offset where it all happens at. once we have the location grabbing this decrypted self should be the easy task. Like I said some info we had and some we did not know about can be obtained like this and used to get keys.
exploiting 4.00 with this method would work most likely because I doubt sony changed all the locations where the loaders do there thing, sure there encapsulated in the bootloader but they still pass over into the ram at one point before being fed over to the metldr which loads ldrs and if all that is still happening then Sony didn't change nothing.. some where along these lines:
void *buf; //