While not required, update CAB identity to 4392.
Makecab /D CompressionType=LZX /D CompressionMemory=15 /D ReservePerCabinetSize=8 ar.dat cab.cab Re-pack scenario/script CAB files with the following: dat file is a PAK3 file that can be extracted with pakcomposer. Furthermore, after extract chat file, the resulting. bin extension but can be extracted like a CAB file. Just find the font name in the exe, hash it and get the font from the big file with its offset and sizeĭecode the gim and that's it Hacker Note 5įiles with MSCF in the header are Microsoft CAB Files and can be extracted in Windows with EXPAND file.cab -F and packed with MAKECAB. You can't find them using the GE debugger though. Other aspects of the game are somewhat easy to hack, like the font the hashes could be all recovered Hacker Note 4 Meaning that a small change in the source string, causes a small change in the resulting hash There is also the fact that the hash is a partially reversible function Hash all, and take the ones existing in the entry table Those are easy to get, just run strings on the exe. Some system files, like the font, have file names directly stored in the execuable So theoretically if you know all the folders you can brute force faster Then it would hash "levels/5/enemy/bat/model.dat" The game engine statically links something like libc, so it uses sprintf to generate in runtime file names.įor instance sprintf('levels/%d/enemy/%s/model.dat", 7, "bat") If you want to extract the right file names, you need to bruteforce the hashes from the index table with the function above (Hacker Note 1) Then hashes the generated names and looks it up in the index table to find offset and size. Now the game doesn't store names anywhere, but rather generates them at runtime.Then search both offsets and sector in the exe. Just identify the padding in the big file to know where a subfile starts.Are the "sub-files" padded to start at an LBA? I think so, try searching for both (should take 2 minutes).So each entry should be 12-bytes, given each member 32-bits Indices are in the executable, offset + size + name hash.Besides the executable, all.dat is the only file of the game.The game's engine simply reloads the menu if you still try to access it. Then alpha-out the Phantasia X logo from the menu.and voila! It's just another ELF inside the game ( top.prx?) Those numbers are not random, they are the hash of the filename string, as per the above hash function.įor example, it's actually pretty trivial to "detach" this game, from Phantasia X, resulting in 2 independent ISO's. Some system files do have their names in the ELF ( all.dat). Except that they don't appear enywhere in the.
0 kommentar(er)
