sprx decryption

imo, the best app for decryption/encryption is scetool. however, decryption is very basic, since the firmware needed is in the header. there are a lot of tools to do that. however, specific encryption is best with scetool.
 
pinky said:
imo, the best app for decryption/encryption is scetool. however, decryption is very basic, since the firmware needed is in the header. there are a lot of tools to do that. however, specific encryption is best with scetool.
Click to expand...

Could I use this for a PRX file? I'm trying to view the source code for a mod menu I downloaded.
 
Break 'n self.

You will not see any source code because they are already compiled. Only Sony have src for whole firmware, including PRX modules. You can try disassembling them for some reason.
 
Berion said:
Break 'n self.

You will not see any source code because they are already compiled. Only Sony have src for whole firmware, including PRX modules. You can try disassembling them for some reason.
Click to expand...

I'm not sure what you mean. I'm just trying to see the source for a mod menu someone wrote. Is there no way to decompile it?
 
Noxillio said:
I'm not sure what you mean. I'm just trying to see the source for a mod menu someone wrote. Is there no way to decompile it?
Click to expand...
No. You can not get the source from a compiled file. If you knew how to reverse engineer it using IDA and you knew how to code, you could rewrite the source or something close to it in theory, but it would be a lot of work.

The only way to get the actual source is from the original developer.
 
You mentioned about Rogero CFW so I assumed You are talking about build-in firmware modules. But it doesn't matter, from custom modules You also not get source code. :P At least not without laborious and time consuming decompiling. Differences between SPRX and PRX on PS3 is only encryption layer, but both are the same native binary compiled code.
 
Berion said:
You mentioned about Rogero CFW so I assumed You are talking about build-in firmware modules. But it doesn't matter, from custom modules You also not get source code. :P At least not without laborious and time consuming decompiling. Differences between SPRX and PRX on PS3 is only encryption layer, but both are the same native binary compiled code.
Click to expand...

I didn't mention Rogero, that was the OP.

Thanks for the quick answers, guys :)
 
Noxillio said:
I didn't mention Rogero, that was the OP.

Thanks for the quick answers, guys :)
Click to expand...

As the other members suggested SCETOOL is the recommended tool for decrypt/encrypt EBOOT/SELF/SPRX,

If you have my PS3 Tools Collection installed properly with the file associations, the encryption/decryption is a piece of cake:
1. Select the SPRX file and press SHIFT+ENTER to decrypt the file.
(You will get the decrypted PRX file. Do not touch the original SPRX file, it will be used in step 3)
2. Double click or just press ENTER on the decrypted PRX file to view/hex edit it with HxD
(You don't get the source code, but strings and binary values can be found and hex edited easily in the PRX)
3. Once you're done modding, save it and press CTRL+ENTER on the PRX the file.
(Your PRX will be encrypted again as SPRX using the same header parameters of your original SPRX.
The original SPRX will be renamed to .SPRX_ORIGINAL. You can leave it there for future mods or delete it if you don't need it.)

The same steps can be used on EBOOT.BIN, .SPRX and .SELF files.
 
aldostools said:
As the other members suggested SCETOOL is the recommended tool for decrypt/encrypt EBOOT/SELF/SPRX,

If you have my PS3 Tools Collection installed properly with the file associations, the encryption/decryption is a piece of cake:
1. Select the SPRX file and press SHIFT+ENTER to decrypt the file.
(You will get the decrypted PRX file. Do not touch the original SPRX file, it will be used in step 3)
2. Double click or just press ENTER on the decrypted PRX file to view/hex edit it with HxD
(You don't get the source code, but strings and binary values can be found and hex edited easily in the PRX)
3. Once you're done modding, save it and press CTRL+ENTER on the PRX the file.
(Your PRX will be encrypted again as SPRX using the same header parameters of your original SPRX.
The original SPRX will be renamed to .SPRX_ORIGINAL. You can leave it there for future mods or delete it if you don't need it.)

The same steps can be used on EBOOT.BIN, .SPRX and .SELF files.
Click to expand...

I actually did use your tool to decrypt the SPRX and get the PRX, then opened it in VSC and was able to see certain things. I was just curious if it was possible to do a full decompile, shame it's not possible.
 
Aius said:
Sorry aldostools, but DEX_Game_Mounter_GUI.exe contains the trojan Wacatac...
Click to expand...
the thread linked above by aldostools says that the ps3 tools collection may give a "false positive" from some scanners. IIRC the last update has been out for a while so it should have been noticed before now if it was infected.

if you are sure it is real then you should consider that the file may have been infected by something else on your pc.
 
If you are that worried that the application is infected, perhaps running in a virtual machine would alleviate your concerns.
I seriously doubt anything by aldostools has anything malicious in it. He has been around for a very long time, and contributed many amazing tools that are used everyday in the homebrew scene.

Another thing to note: Most antivirus will flag software that has zero infection, based off arbitrary code paths. Home based devs tend to learn online, the same way that some virus/trojan/etc writers learn online as well. So yes, there are coding similarities in the process, creating false positive flags. Windows Defender is one of the most notorious for this.
 
I know I know, you're right.
Sorry to question this respectable contributor !
Thank you for your excellent work, it's just that it is the only file that makes my antivirus panic with such precision.
A control costs nothing.
Thanks again !
 
aldostools said:
As the other members suggested SCETOOL is the recommended tool for decrypt/encrypt EBOOT/SELF/SPRX,

If you have my PS3 Tools Collection installed properly with the file associations, the encryption/decryption is a piece of cake:
1. Select the SPRX file and press SHIFT+ENTER to decrypt the file.
(You will get the decrypted PRX file. Do not touch the original SPRX file, it will be used in step 3)
2. Double click or just press ENTER on the decrypted PRX file to view/hex edit it with HxD
(You don't get the source code, but strings and binary values can be found and hex edited easily in the PRX)
3. Once you're done modding, save it and press CTRL+ENTER on the PRX the file.
(Your PRX will be encrypted again as SPRX using the same header parameters of your original SPRX.
The original SPRX will be renamed to .SPRX_ORIGINAL. You can leave it there for future mods or delete it if you don't need it.)

The same steps can be used on EBOOT.BIN, .SPRX and .SELF files.
Click to expand...

I tried running your installer with admin privs but my context menu doesnt have SELF tools :[
 
pinky said:
I think pkg_content_id may help. try having it run as administrator, then with compatibility with windows 7. see if you have self tools then. you may have to restart as well.
Click to expand...

Already tried that. The sprx's in question were intended to enable remote play for unsupported games, but I figured out how to toggle remote play and select compression method with aldos sfo editor. Besides, the sprx's were for 3.55 but I used them on the latest rebug and it broke remote play and I don't mind manually editing param.sfo for each app/game.
 
You must log in or register to reply here.

Similar threads

Back
Top