v2.01 changed files

[jockyw2001]

I did a binary compare of 2.0 and 2.01 files after running psardumper2.
Following files are different:

OUT:
data0.bin
index.dat
README.txt
version.txt

OUTX:
libssl.prx
loadcore.prx
mebooter.prx
mebooter_umdvideo.prx
me_wrapper.prx
paf.prx
pspbtcnf.txt
pspbtcnf_game.txt
pspbtcnf_updater.txt
pspcnf_tbl.txt
sysmem.prx

Note: paf.prx is totally different and also different size, all other files differ only in a few bytes

Now it's up to the hackers to do a damage assessment :P

/JockyW

[Vampire]

actually only the following 3 files have changed:
vsh/etc/index.dat
vsh/etc/version.txt
vsh/module/paf.prx

[jockyw2001]

@Vampire: seems you have another 2.0 or 2.01
I downloaded 2.01 from pspupdates and 2.0 I downloaded on my PSP some days ago. My PSP is a 1000K.

I'll try again with a 2.01 downloaded on my PSP.

/JockyW

[Vampire]

Note: paf.prx is totally different and also different size, all other files differ only in a few bytes

this is due to a bug in psardumper2:
some decrypted prx files are a few bytes larger as they should.
it seems the problem is the return value of the MyDecryptPRX function.
it can be fixed by changing line 329 in main.c from
return cbTotal - 0x150; // size of actual data - may be a little off?
to
return *(u32*)&pbIn[0xB0]; // size of actual data

[jockyw2001]

Ah okay, in that case I'll save the hazzle of dl 2.01 again and will rebuild psardumper2.

It actually makes more sense now, sony just fixed the tiff exploit with 2.01 and are awaiting further instructions from the hackers :P

/JockyW

[edit]: perhaps vampire's bugfix can make mph's firmwareloader actually load 2.0 & 2.01 ??

[PspPet]

BTW: the files that have slightly larger sizes are those that aren't GZIP compressed (ie. text files and a few special prxs).

> perhaps vampire's bugfix can make mph's firmwareloader actually load 2.0 & 2.01 ??
Nope, not that easy.
FWIW: some may load, but not start. The problem is the existing system is already in RAM as discussed on other threads.