To quote: Hi everybody, here to release my new update.
PS3Tools GUI Edition v2.6 Changes:
Added CEX 2 DEX
Fixed PKG decryptor button
Fixed EDAT Tool button
Removed second GUI form
Minor bug fixes and code changes to perform better
I have been asked a lot recently to add in a debug PKG decryptor because all I had is a Retail decryptor & extractor. Well I did, but last minute checks, I noticed it was not performing the way I wanted it too.
So instead of releasing faulty code/tool on my program and say it works half way, I'd rather withdraw the feature until a further update when I can have it working properly to my standards and what should be most.
PlayStation 3 CEX to DEX:
This whole CEX to DEX is going around, I felt like adding it to GUI form had to be done so, I jumped on band wagon and did it. When going to use this Make sure you have a CEX Nor flashed named "CEXFLASH.bin" and the eid_root_key.bin in the program folder.
Run the tool and it will output a DEXFLASH.bin... easy as pie. Note* opensll required!!
Thanks to naehrwert, KaKaRoToKS, andbey0nd Math, HsRiena, geohot, eussNL, zecoxao and ofcourse the MAIN team I cannot forgot. Fail0verFlow also tthousand for always helping with everything, you're awesome buddy I never give you enough appreciation and thanks!!
Finally, from Sony PS3 hacker evilsperm:
I will not be going into detail on how to compile the metldrpwn or how to compile and use libeeid. Oh and if you don't know what scp is go google it because im not gonna be getting into all that, this isnt a spoon feeding tut
1. dump nor (from xmb, hardware flasher, or petitboot) if from petitboot you will need a flash drive or external hdd. make sure you hold on to this backup or your FUCT if something goes wrong.
2. extract nor (f0f tools or the windows nor unpack)
3. install rebug otheros++
4. install rebug otheros++ preptools
5. boot into petitboot
Now this is where it will start to get tricky because you will need to either scp files or use a flashdrive/external hdd, I use scp because its fast and easy
6. READ eEID : dd if=/dev/ps3nflasha skip=$((0x2F000)) of=/cex_eid.bin bs=1 count=$((0x10000))
7. scp cex_eid.bin to your computer
8. cd / rm cex_eid.bin
8. scp your metldr to the PS3 from your computer
9. run the metldrpwn on your metldr and dump the eid_root_key
10. scp your eid_root_key from your PS3 to your computer
11. use libeeid or whatever that other cex>dex tool is and convert your eid to dex (using the cex_eid.bin > dex_eid.bin)
12. scp your new dex_eid.bin to the PS3
13. WRITE eEID: dd if=dex_eid.bin of=/dev/ps3nflasha bs=1 seek=$((0x2F000)) count=$((0x10000))
15. if you're not bricked you will still be in cex FW just install DEX fw and poof your done
LAST WORDS OF WARNING:
If you brick its 100% you're fault and you didn't follow the instructions the the letter, or you just did something wrong all together. Don't ask me what went wrong cuz I won't have a clue nor do I care if you brick seeing I warned you to have a hardware flasher just in case.
Sorry if that sounds harsh but if you don't think you can do this then you shouldn't be trying to mess with your nor in the first place because YOU CAN PERM BRICK!
Rename the .bin's for use with this gui...
Note: After booting to gameOS from petitboot (just after writing the nor, which only a very small section is actually changed) it is still booting the cex firmware that is installed. It isn't on debug fw yet, so there are no debug options. All this does is allow you to install a debug firmware.
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; //