03/08/2007, 09:03 AM
vodkkaa {who took my name} Wrote:bstronga Wrote:@vodkkaa working fine here.
can you please pm the decrypted systemctrl and the M33 header you used please.
u can get it by prxdecrypter.
03/08/2007, 09:03 AM
03/08/2007, 09:08 AM
Is this gui for 3.52 m33 only? or is it also for 3.51 m33?
If it is also for 3.51 m33 then what do i need to do to get
it to work?
I use original paf.prx straight from Flash0 vsh/nodule as my
header file, and my modded 2.11mb paf.prx as decrypted file, set
compression to 6(end up with 803kb file). But when I flash it gives
a semi-brick:@
What am I doing wrong?
If it is also for 3.51 m33 then what do i need to do to get
it to work?
I use original paf.prx straight from Flash0 vsh/nodule as my
header file, and my modded 2.11mb paf.prx as decrypted file, set
compression to 6(end up with 803kb file). But when I flash it gives
a semi-brick:@
What am I doing wrong?
03/08/2007, 09:26 AM
bstronga Wrote:http://endlessparadigm.com/forum/showthr...8#pid39048
yep, for M33 3.51 it would be for vsh modules 0xA7CEA82D, firmware kernel modules 0x462FD0F5.
From the few that I've done using the vshmain.prx and paf.prx straight from the freshly flashed 3.52m33 those two files have that data already in there and I have not had to change them.
So, I am now assuming that I can take my recompressed vshmain.prx and paf.prx that work on 3.52 and just change those keys to make it work in 3.51?
03/08/2007, 10:55 AM
s_king Wrote:Some infos about my PRX compressor project.
What you can do with the program now:
- load an original compressed 3.5x M33 prx to use as header (0x0 - 0x150). That means no need for frmware selector, you get the final prx for the same M33 firmware as your original prx was.
- load a decompressed prx (elf) to use as the data
- select gzip compression level
- compress the data part with the selected level
- the program keeps all of your original files, doesn't overwrite anything (gzip normally deletes the original file after the compression)
Things that surely will implemented in the first release (to do list):
- merge the header and the compressed part to the final prx
- 'Force dunno part' option: force to use the 4 bytes from vshmain.prx (0x130 - 0x132) "dunno" name from bstronga ;)
- filename difference checking: if you load paf.prx as header and a 'vsh.prx' named file as data, the program will warn you, but let you use the selected files
- maybe compression rate infos: original data x bytes, compressed data y bytes, gained z bytes or w% or something like that
And in the second version I will implement a decompressor. I believe it's not so important in the first release.
Release date? Tomorrow. Any ideas, suggestions are welcome.
S_King im waiting to see your App , i got only one suggestion ; Can u please make it works for every PRX .
03/08/2007, 11:03 AM
he said he stopped development on it because that other takeshi(sp?) dude is making one
03/08/2007, 12:17 PM
Yes, I truly said stopped developing, but some of you asked and... okay, why not? I'm continue working on it. Currently I'm making 'Force vshmain dunno part' option, all other functions are ready. After finishing I'll start the tests to see if the created prxes are working or not... :)
@Gsmoke: What prxes you want create and what's the difference between them (if you know it)?
@Gsmoke: What prxes you want create and what's the difference between them (if you know it)?
03/08/2007, 12:34 PM
s_king Wrote:Yes, I truly said stopped developing, but some of you asked and... okay, why not? I'm continue working on it. Currently I'm making 'Force vshmain dunno part' option, all other functions are ready. After finishing I'll start the tests to see if the created prxes are working or not... :)
@Gsmoke: What prxes you want create and what's the difference between them (if you know it)?
oops you got me ... I don't know the differences , well i was talking about for your opening_plugin.prx file , lol is not much 72 KB , so no need to be compressed . By the way , im really thankful that you keep on making your gui , Let it be how it is . Don't listening to me ;P
03/08/2007, 02:20 PM
Did somebody try to recreate paf.prx with takeshi's tool? I didn't get a working paf in any way. Tried with 3.51 M33 and 3.52 M33 original prxes as a header and the decompressed pafs as the data and none of them worked. Somehow the paf.prx I created with takeshi's tool was always 4 bytes longer than a paf created with my program. And the gzipped content in the file is completely different. The good news is, my paf creations are working. I'm on 3.52 M33 and tested with both FW versions recreated pafs on my PSP and if the 'Force dunno part' option is on, it's working.
03/08/2007, 02:24 PM
wauw thanks ..!!
03/08/2007, 02:42 PM
@S_king maybe he is using the Dunno too , but i don't know why the paf size is diferent ...
Did you saw that :
cool.
however it does always use 0xC37AED69 which is fine for vsh modules
but not for modules like vshctrl.prx or third party plugins you may want to compress. which would need 0x33D63A71.
also its important to know that 0xC37AED69, 0x33D63A71 are for M33 3.52 exclusivly
and won't work on M33 3.51 or any other upcoming M33 firmware with different kernel.
Maybe that's the reason ... I know is a dumb idea , because they talking about VSHCTRL ...
Did you saw that :
cool.
however it does always use 0xC37AED69 which is fine for vsh modules
but not for modules like vshctrl.prx or third party plugins you may want to compress. which would need 0x33D63A71.
also its important to know that 0xC37AED69, 0x33D63A71 are for M33 3.52 exclusivly
and won't work on M33 3.51 or any other upcoming M33 firmware with different kernel.
Maybe that's the reason ... I know is a dumb idea , because they talking about VSHCTRL ...