Skip to content
View in the app

A better way to browse. Learn more.
ResHax

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Help us keep the site running.

Katamari Damacy/We Love Katamari (PS2) .BIN

ZenHAX
in Zenhax

Featured Replies

  • Author
  • Localization

aluigi, posted Wed Feb 03, 2016 10:54 pm (11200)

They are just raw data without information about the contained files.
For example FILE_00.BIN starts immediately with an mpeg while 01 with a VAG and there are no info at the end.

Can you check if there are smaller files? There should be some index files.
  • Author
  • Localization

AnonBaiter, posted Wed Feb 03, 2016 11:04 pm (11202)

This file, uploaded as an attachment, is the only smaller file I could find. The rest are just ELF and .CNF files at this point.
  • Author
  • Localization

aluigi, posted Fri Feb 05, 2016 8:55 am (11215)

Maybe the index is the executable (ELF) like it happens with some rare games.
I don't know what should be contained in the CNF files.
Maybe upload the ELF and one CFN.
  • Author
  • Localization

AnonBaiter, posted Fri Feb 05, 2016 2:26 pm (11220)

Here are the rest of the files in the game.

https://mega.nz/#!JB9m3AII!S-JwMMOIG49KibGpJc9JhO6afDJBYr314aF5AcZWixc

aluigi wrote:
I don't know what should be contained in the CNF files..

The CNF usually contains the information of the game: the file needed to boot it, the version, and the video region(such as NTSC, PAL, etc.).
  • Author
  • Localization

aluigi, posted Fri Feb 05, 2016 3:35 pm (11224)

I don't see references in the executable.
I just searched for "mpg" and "vag" because I don't have more information to search.
There are not even references to the names of the bin archives.

Maybe someone else as more information to share.
  • Author
  • Localization

AnonBaiter, posted Fri Feb 05, 2016 5:25 pm (11227)

Then I might as well just document the BIN files out of the offsets. I'll see what I can find out of these archives.

EDIT: Well, I think I know where the PS2 videos are from the offsets. Here they are:
Code:
FILE_00 Movie(PSS) Directory Offsets:
000000(000007 - TMPGEnc header)
273080(273087 - TMPGEnc header)
3BF500(3BF507 - TMPGEnc header)
4BAD80(4BAD87 - TMPGEnc header)
5B6600(5B6607 - TMPGEnc header)
6F0680(6F0687 - TMPGEnc header)
7EBF00(7EBF07 - TMPGEnc header)
901380(901387 - TMPGEnc header)
A11C00(A11C07 - TMPGEnc header)
B27080(B27087 - TMPGEnc header)
C37900(C37907 - TMPGEnc header)
CF5180(CF5187 - TMPGEnc header)
DB2A00(DB2A07 - TMPGEnc header)
E70280(E70287 - TMPGEnc header)
F2DB00(F2DB07 - TMPGEnc header)
FEB380(FEB387 - TMPGEnc header)
10A8C00(10A8C07 - TMPGEnc header)
1166480(1166487 - TMPGEnc header)
1223D00(1223D07 - TMPGEnc header)
12E1580(12E1587 - TMPGEnc header)
1410200(1410207 - TMPGEnc header)
1687E80(1687E8B - TMPGEnc header)
170A700(170A707 - TMPGEnc header)
1753B80(1753B87 - TMPGEnc header)
17C6C00(17C6C0B - TMPGEnc header)
1839C80(1839C8B - TMPGEnc header)
18ACD00(18ACD0B - TMPGEnc header)
18F0D80(18F0D87 - TMPGEnc header)
193F600(193F60B - TMPGEnc header)
198DE80(198DE8B - TMPGEnc header)
19DC700(19DC707 - TMPGEnc header)
1B7EF80(1B7EF87 - TMPGEnc header)
1BC3000(1BC3007 - TMPGEnc header)
1C07080(1C07087 - TMPGEnc header)
1C4B100(1C4B107 - TMPGEnc header)
1C8F180(1C8F187 - TMPGEnc header)
1CD3200(1CD3207 - TMPGEnc header)
1D17280(1D1728B - TMPGEnc header)
1D5B300(1D5B307 - TMPGEnc header)
1D9F380(1D9F38B - TMPGEnc header)
1DE3400(1DE3407 - TMPGEnc header)
1E27480(1E27487 - TMPGEnc header)
1E6B500(1E6B507 - TMPGEnc header)
1EAF580(1EAF587 - TMPGEnc header)
1EF3600(1EF3607 - TMPGEnc header)
1F37680(1F37687 - TMPGEnc header)
1F7B700(1F7B70B - TMPGEnc header)
1FF3B80(1FF3B87 - TMPGEnc header)

If I'm not mistaken, the .PSS files end with the end of the FILE_00.BIN file itself. As aluigi said, they are just raw data with no information about them. Now off to documenting FILE.01.BIN files...
  • Author
  • Localization

aluigi, posted Sat Feb 06, 2016 1:05 am (11235)

No references about 00 27 30 80 or 80 30 27 00 in SLUS_210.08, and those about ?? 30 27 00 are unrelated.
  • Author
  • Localization

AnonBaiter, posted Sat Feb 06, 2016 3:38 am (11237)

I actually meant "offset addresses" instead of just "offsets", but you get the idea.
Actually there are no references to these files in the ELF file, since said file is a combination of logs that were generated during the creation of the ISO, unused debug texts, and other bits.
  • Author
  • Localization

aluigi, posted Sat Feb 06, 2016 9:44 am (11239)

Let's do the following, upload the first 10 or more megabytes of file_00.bin.
  • Author
  • Localization

AnonBaiter, posted Sat Feb 06, 2016 5:08 pm (11254)

aluigi wrote:
Let's do the following, upload the first 10 or more megabytes of file_00.bin.

I'm uploading it, but that might take a little longer since I'm instead uploading the whole file divided into 4 parts instead of the first 10MB. I'll PM you with the link when it's done uploading.
  • Author
  • Localization

aluigi, posted Sat Feb 06, 2016 11:23 pm (11264)

The offsets you listed are correct when multiplied by 16.
Anyway, also in this case, there are absolutely no references of those offsets (for example 0x3bf5000 or 0x2730800) or the file sizes (for example 0x014c4800) even if divided by 0x800 (usually used on PS2). And yeah, both the IMG and the ELF file.
That's enough for me. Sorry.
  • Author
  • Localization

AnonBaiter, posted Sun Feb 07, 2016 3:17 am (11278)

aluigi wrote:
The offsets you listed are correct when multiplied by 16.
Anyway, also in this case, there are absolutely no references of those offsets (for example 0x3bf5000 or 0x2730800) or the file sizes (for example 0x014c4800) even if divided by 0x800 (usually used on PS2). And yeah, both the IMG and the ELF file.
That's enough for me. Sorry.

That's okay. Thanks for your help.

EDIT: I might upload the rest of the .BIN files(DUMMY.BIN, FILE_01.BIN, FILE_02.BIN) someday.
  • Author
  • Localization

AnonBaiter, posted Wed Mar 09, 2016 10:00 am (11865)

Looks like I found something on the FILE_00.BIN file.

I extracted the files manually using 010 Editor, and the last .PSS file is located at "1FF3B000" offset, right through the end of the file.

Well, that wasn't easy.

EDIT: Okay, let's see what are these archive files:
DUMMY.BIN - sounds(?)
FILE_00.BIN - mostly movies
FILE_01.BIN - sound data
FILE_02.BIN - unknown

It's mostly a breakdown of what I found so far. I might take a look into these files, if I have the time to.

EDIT2: Now that I think about it, I should take the task of writing a BMS script despite having no reverse-engineering skills whatsoever. But for now I'd just rather think about it.
  • Author
  • Localization

AnonBaiter, posted Tue Apr 19, 2016 12:34 am (12688)

I found the same type of archive on the game We Love Katamari, which is a sequel of the game that you're seeing on the title of this thread.

EDIT: Here are the samples(IMG, CNF and ELF files included):
https://mega.nz/#!MIMCRQbT!RifrMvK2MF8gwbtjtgCqPrr6WbKMYsfs9Rc_7b0gHXo

And here are the file locations for FILE_00.BIN:
Code:
FILE_00.BIN File Directory Offsets:
13E840h - .PSS file(TMPGEnc header)
2B0F0B3h - .PSS file(TMPGEnc header)
49C3840h - .PSS file(TMPGEnc header)
6878040h - .PSS file(TMPGEnc header)
872C840h - .PSS file(TMPGEnc header)
A5E1040h - .PSS file(TMPGEnc header)
C51D840h - .PSS file(TMPGEnc header)
E45A040h - .PSS file(TMPGEnc header)
10396840h - .PSS file(TMPGEnc header)
122D3040h - .PSS file(TMPGEnc header)
14703840h - .PSS file(TMPGEnc header)
16B34040h - .PSS file(TMPGEnc header)
18F64840h - .PSS file(TMPGEnc header)
1B395040h - .PSS file(TMPGEnc header)
1CDE5840h - .PSS file(TMPGEnc header)
1E836040h - .PSS file(TMPGEnc header)
20286840h - .PSS file(TMPGEnc header)
21CD7040h - .PSS file(TMPGEnc header)
2397B840h - .PSS file(TMPGEnc header)
25620040h - .PSS file(TMPGEnc header)
272C4840h - .PSS file(TMPGEnc header)
28F69040h - .PSS file(TMPGEnc header)
2ACA1840h - .PSS file(TMPGEnc header)
2C9DA040h - .PSS file(TMPGEnc header)
2E712840h - .PSS file(TMPGEnc header)
3044B040h - .PSS file(TMPGEnc header)
32217840h - .PSS file(TMPGEnc header)
33FE4040h - .PSS file(TMPGEnc header)
35DB0840h - .PSS file(TMPGEnc header)
37B7D040h - .PSS file(TMPGEnc header)
39B75840h - .PSS file(TMPGEnc header)
3BB6E040h - .PSS file(TMPGEnc header)
3DB66840h - .PSS file(TMPGEnc header)
3FB5F040h - .PSS file(TMPGEnc header)
41577840h - .PSS file(TMPGEnc header)
42F90040h - .PSS file(TMPGEnc header)
449A8840h - .PSS file(TMPGEnc header)
463C1040h - .PSS file(TMPGEnc header)
4822D840h - .PSS file(TMPGEnc header)
4A09A040h - .PSS file(TMPGEnc header)
4BF06840h - .PSS file(TMPGEnc header)
4DD73040h - .PSS file(TMPGEnc header)
4EDC3840h - .PSS file(TMPGEnc header)
56D8C040h - .PSS file(TMPGEnc header)
5ED54840h - .PSS file(TMPGEnc header)
66D1D040h - .PSS file(TMPGEnc header)
6ECE1840h - .PSS file(TMPGEnc header)
6FD32040h - .PSS file(TMPGEnc header)
7147A840h - .PSS file(TMPGEnc header)
724CB040h - .PSS file(TMPGEnc header)
7351B840h - .PSS file(TMPGEnc header)
7456C040h - .PSS file(TMPGEnc header)
755BC840h - .PSS file(TMPGEnc header)
7660D040h - .PSS file(TMPGEnc header)
7765D840h - .PSS file(TMPGEnc header)
786AE040h - .PSS file(TMPGEnc header)
796FE840h - .PSS file(TMPGEnc header)
7A74F040h - .PSS file(TMPGEnc header)
7B79F840h - .PSS file(TMPGEnc header)
7E5E0040h - .PSS file(TMPGEnc header)
888E4000h - ???(looks like encyption/compression/obfuscation data)
888E5000h - file ends here


What's interesting to note is that each of the .BIN files ends with what looks like a hash or a encryption key:
Code:
xa37dd45ffe100bfffcc9753aabac325f07cb3fa231144fe2e33ae4783feead2b8a73ff021fac326df0ef9753ab9cdf6573ddff0312fab0b0ff39779eaff312x
Guest
This topic is now closed to further replies.
Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.