Tomb Raider Trilogy working PKG [1st post]

[deank]

I managed to snap a shot of the cmd window before it went away. This is what happened when I drag and dropped. Crysis 2 does have 2 compressed headers btw in the original eboot.bin
(part of my problem could be the space in my username, i dont know how to change this without making a new account)

Your target path string should not contain spaces.

Yep... extract the folder to a location without spaces in the path like:

d:\multiMAN_eboot_fix\

or

e:\blabla\1234\multiMAN_eboot_fix\

[PatrickBatman]

HAHAHAHHA I knew it was that easy! Lack of sleep and Henderson-Hasselbalch equation cycles in my head due to the last pH meter broken. This is my fun time! Anyway, I checked the code on Crysis 2 (wont try to run game until tommorrow) looks perfect .sys_proc_param was visible in EBOOT.BIN near end of code, 40 was at start of control flags, etc etc etc (the 2 things i couldnt get to work yet)

So bodacious job, if dean or belmondo could tell me how they got the sys_proc _param visible in .BIN and 40 at start of control flags ill greatly appreciate it because I'll try and figure it out anyway because there's something wrong with me.

[dan74cold]

worked great so far. loaded all 3 games fine, changed options in all 3 and they were accepted, played underworld about 5 mins, saved, quit, and reloaded the save fine. Only oddity i noticed was quting game to launcher sent you back to XMB, non issue really.

sound the alarms! TRT from internal with 3.55 KMEAW!

How its working while its not ? Maybe I'm missing something, but according to instruction from package:
"-Replace PS3_GAME from this pack, overwrite everything when asked
-Rename PS3_GAME to BES01195 and transfer to your Ps3 dev_hdd0:\
-Install the PKG and run TRT from XMB"

So I've backuped my TRT bd to dev_hdd0:\GAMES\
Then overwritten dev_hdd0:\GAMES\<TRT_folder>\PS3_GAME with PS3_GAME from mote's archive.
Next I've renamed PS3_GAME from mote's archive and putted it as def_hdd0:\BES01195
As last part I've installed pkg and tried run game from xmb but got blackscreen and game went back to XMB.

What about that making shadow copy with mm ? Is that no longer necessary ?
I'm little confused about def_hdd0:\BES01195 folder ? I've put there contents of PS3_GAME folder from mote's archive, but maybe I should put there full content of TRT\PS3_GAME ?

[mote]

How its working while its not ? Maybe I'm missing something, but according to instruction from package:
"-Replace PS3_GAME from this pack, overwrite everything when asked
-Rename PS3_GAME to BES01195 and transfer to your Ps3 dev_hdd0:\
-Install the PKG and run TRT from XMB"

So I've backuped my TRT bd to dev_hdd0:\GAMES\
Then overwritten dev_hdd0:\GAMES\<TRT_folder>\PS3_GAME with PS3_GAME from mote's archive.
Next I've renamed PS3_GAME from mote's archive and putted it as def_hdd0:\BES01195
As last part I've installed pkg and tried run game from xmb but got blackscreen and game went back to XMB.

What about that making shadow copy with mm ? Is that no longer necessary ?
I'm little confused about def_hdd0:\BES01195 folder ? I've put there contents of PS3_GAME folder from mote's archive, but maybe I should put there full content of TRT\PS3_GAME ?

You doing it wrong, after overwrite PS3_GAME with my archive, rename PS3_GAME of the game to BES01195 and move it to the root of hdd0, install the pkg and you're good to go, no shadow copy needed.

[deank]

HAHAHAHHA I knew it was that easy! Lack of sleep and Henderson-Hasselbalch equation cycles in my head due to the last pH meter broken. This is my fun time! Anyway, I checked the code on Crysis 2 (wont try to run game until tommorrow) looks perfect .sys_proc_param was visible in EBOOT.BIN near end of code, 40 was at start of control flags, etc etc etc (the 2 things i couldnt get to work yet)

So bodacious job, if dean or belmondo could tell me how they got the sys_proc _param visible in .BIN and 40 at start of control flags ill greatly appreciate it because I'll try and figure it out anyway because there's something wrong with me.

UPDATED FINAL#5: Here is an updated version of the tools. They now handle properly SPRX files. (thanks to belmondo for the hints!)

There are few important fixes (about path with spaces and wrong byte change which may cause crashes and also fixed PARAM.SFO in RETAIL to be DG type). Don't use previous versions I posted. This package also includes multiMAN 01.16.11 (TEST UPDATE#5) which handles properly SPRX files during SHADOW COPY.

ebootFIX now produces TWO separate folders:

One is [NPDRM] - to be used as PSN-styled game to launch from XMB (to be used with multiMAN's shadow copy)
The other one is [RETAIL] - it will generate the full game structure with all subfolders + all EBOOT.BIN / *.self / *.sprx files.

[NPDRM] has a PKG file to be used with multiMAN's shadow copy.
[RETAIL] can be used to directly replace the files in your original game BACKUP.

Let me know if it works properly for you.

************************************************************************************
Short readme for ebootMOD and ebootFIX:
************************************************************************************
ebootFIX:

Drag and drop a PS3 game folder to ebootFIX.exe.

For example drag&drop 

	X:\GAMES\MY_GAME\PS3_GAME

	or

	X:\GAMES\MY_GAME\PS3_GAME\USRDIR

	or

	X:\GAMES\MY_GAME


to ebootFIX.exe.

ebootFIX processes whole game folders and produces two output folders:

--> [NPDRM] - folder - content ready to be installed as PSN-style XMB game:
You will find two PKG files in the folder. The tool will decrypt and sign
all executables (EBOOT.BIN and other .self / .sprx files) to make them compatible
with lower firmware versions. Follow the generated INSTRUCTIONS in
[NPDRM] folder.

--> [RETAIL] - folder - all files which you can replace in your original
backup copy to play the game via a Game Manager.

************************************************************************************
ebootMOD:

Drag & drop a file (EBOOT.BIN, .self or .sprx) to ebootMOD.exe. It will decrypt and
sign the file to make it compatible with lower firmware versions. The generated file
will be saved in the same folder with the original, prefixed with "MODIFIED_".

More options available via command-line.
************************************************************************************

Thanks to: Belmondo, Rogero, mote and all other developers for the ideas, help and that great set of tools!

[PatrickBatman]

Sorry also how do i get it to run in a command line, i used cygwin and put eboot in home/username directory (no spaces) and put ebootMOD in bin folder but get an error:

$ ebootMOD EBOOT.BIN

unself [EBOOT.BIN]...
open EBOOT.BIN
perror: No such file or directory

Searching for sys_proc_param data...
0% Processing...
fRead: (RT) The handle is invalid.
- Line 116

I want to read what ebootMOD does exactly after finding sys_proc_param data

[deank]

Please make sure that you use the package from the previous post. And I think you can't use the tool in cygwin. Use it in windows command prompt.

[simmeon1]

Good job guys, the scene's developing better thanks to you (bow).

[y2kinder]

TRT WORKS!!!
Can't tell you how happy I am to have this game working!
The skills you have and time you put into the scene is unmatched!
Thank you so much!

[enragedg0ldfish]

UPDATED: Here is an updated version of the tools. They now handle properly SPRX files. (thanks to belmondo for the hints!)

There are few important fixes (about path with spaces and wrong byte change which may cause crashes). Don't use previous versions I posted.

ebootFIX now produces TWO separate folders:

One is [NPDRM] - to be used as PSN-styled game to launch from XMB (to be used with multiMAN's shadow copy)
The other one is [RETAIL] - it will generate the full game structure with all subfolders + all EBOOT.BIN / *.self / *.sprx files.

[NPDRM] has a PKG file to be used with multiMAN's shadow copy.
[RETAIL] can be used to directly replace the files in your original game BACKUP.

Let me know if it works properly for you.

Ermm.. no link was provided in this, did you mean the link provided in your previous, previous post?

NVM, saw post updated with link now.