ROM Hack [Release] 3DS_CTR_Decryptor-VOiD

  • Thread starter Thread starter Relys
  • Start date Start date
  • Views Views 649,172
  • Replies Replies 2,226
  • Likes Likes 30
you can tell if the files are right because the start of the files should have a lot in common because the header contains a lot of 0's when decrypted.
 
Yeah definitely the right xor pad.
When I extract the encrypted RomFS using ctrtool (compiled from 3dshax) it gives me different contents than when I extract it using 3dsExplorer or manually. It states the same offset & length tho. None of them give a working output once xor'd anyway tho.
 
Yeah definitely the right xor pad.
When I extract the encrypted RomFS using ctrtool (compiled from 3dshax) it gives me different contents than when I extract it using 3dsExplorer or manually. It states the same offset & length tho. None of them give a working output once xor'd anyway tho.

Oh wait, are you using the '-p' switch on ctrtool when extracting the encrypted romfs? I forgot about that.
 
Ok, using the -p switch gives the same extracted encrypted RomFS.bin as I get with the other methods. The xor'd result still isn't recognised by ctrtool tho.

So I guess it's either the xor'ing process going wrong (not looking likely as different tools give the same output) or the xorpads are wrong - which must mean there's still something up with the ncchinfo.bin? Ugh.
 
  • Like
Reactions: Tikvah
Ok, using the -p switch gives the same extracted encrypted RomFS.bin as I get with the other methods. The xor'd result still isn't recognised by ctrtool tho.

So I guess it's either the xor'ing process going wrong (not looking likely as different tools give the same output) or the xorpads are wrong - which must mean there's still something up with the ncchinfo.bin? Ugh.

I just tested Sonic 2 Game Gear with the instructions I posted above, it decrypted and extracted fine.

Is your romfs.bin.out from padxorer the same size as your extracted romfs.bin from ctrtool?
 
Unless GW decides to implement this rom decryption feature in their GW menu

Try to send them the source code of the decryptor via email and see what happens. Anyway, it must be launched within the 3DS menu because it requires to have emuNAND initialized on 8.1, so adding it in the GW Menu would be useless.
 
Ok, using the -p switch gives the same extracted encrypted RomFS.bin as I get with the other methods. The xor'd result still isn't recognised by ctrtool tho.

So I guess it's either the xor'ing process going wrong (not looking likely as different tools give the same output) or the xorpads are wrong - which must mean there's still something up with the ncchinfo.bin? Ugh.



Thank you SO much! This really helped me! All I had to do was decrypt using the -p switch. :lol:
 
Nailed it. It was still my build of ctrKeyGen that was causing problems and giving me a faulty ncchinfo.bin. Somehow the first byte of the KeyY was overwritten for two of the three pad files, must be an overflow somewhere due to some other random difference compiling on a Mac. Rather than finding that, I added some padding bytes before the KeyY data in the info structure, and now it works, gotta love a botch job :D
Have successfully unpacked the romfs from those three roms I mentioned, that's enough testing for one night! Thanks a lot guys for the tools and the patient assistance :)

Edit: for the record, all the audio in the VVVVVV eshop dump is in regular .wav or .ogg - sweet.
 
  • Like
Reactions: Celice
Have you had any luck?
I started writing my own program to decipher the file, but I can't figure out how the colors work. They are obviously 16bpp and they have transparency.
I've never programmed before, so this was already a task for me to get to.
lXDlsiF.png


If anyone knows how I can figure out the colors and transparency, It would be appreciated. Some kind of documentation or something would be great. Thank you.

Here it is converted properly (I believe):

RPzv3xD.png


It uses ARGB4444. I'll probably post more on how the format works once I figure it out instead of macgyvering my BCLIM code to (kind of) support it.

EDIT: There are actually like five images in this file, and they're all different.

Here's a second, will work on the rest later:
4auUOLP.png
 
Here it is converted properly (I believe):

RPzv3xD.png


It uses ARGB4444. I'll probably post more on how the format works once I figure it out instead of macgyvering my BCLIM code to (kind of) support it.

EDIT: There are actually like five images in this file, and they're all different.

Here's a second, will work on the rest later:
4auUOLP.png



Thats really cool :D Have you by any chance figured out how to extract the models from Pokemon X/Y?
 
New and interesting graphic formats I see.
If you are all looking for fairly extensible graphics viewers, be they in general or in code you can tweak a bit, and crystaltile2 is not cutting it then you might also like
http://code.google.com/p/tiledggd/
and
https://github.com/marco-calautti/Rainbow

You might also look into SUSIE plugins, it seems to be bigger in Japan but it has a fairly long history in game hacking.
 

Site & Scene News

Popular threads in this forum