s_king Wrote:Should I put a firmware selector instead of the 'dunno part' thingie? And when you choose 3.51 the 0x130 part will 0xA7CEA82D and when 3.52, the 0x130 part will 0xC37AED69.

Which files need to be compressed with this method? Because the 0x130 part is really firmware and prx specific. I would have to implement all possible values for 0x130 part? And let the program determines automatically from the selected header and set the right value?

The sad is I could test only the 3.52 related prxes because I'm on 3.52 M33.

hmm you need to consider if you do a firmware selector that you need to update your app everytime when a new M33 firmware comes. maybe let the app first read vshctrl.prx/systemctrl.prx and vshmain.prx and save it. well no clue how to do it without confusing the user too much :>

SchmilK Wrote:

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?

yea, i tested with M33 3.51 modules on M33 3.52. but really i don't think its too much work to do it more properly and just replace the whole header instead ;p

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.

default decrypted M33 3.52 (haven't updated to 2 though, they might have changed stuff) systemctrl.prx. just repacked.

(This post was last modified: 03/08/2007 04:37 PM by bstronga.)