This one's ncchinfo.bin generates a single xorpad, for some weird reason
Weird reason? that's how it's supposed to work.
This one's ncchinfo.bin generates a single xorpad, for some weird reason
Something looks wrong ith it.Weird reason? that's how it's supposed to work.
Something looks worong ith it.
I tried with the NCCH extracted from a DevMenu.cia and it generated 2 files named DevMenu (second overwrites the first one) and 1MB big, haha
It's encrypted.
I think you could just edit your ncchinfo.bin to reflect the new RomFS size and generate a new xorpad.
Couldn't you then you xor it back after having the hashes fixed and reinsert the encrypted romfs.bin with makerom?
I don't get the purpose of this NCCH ctrkeygen for romfs modding.
Any hints for recompressing code.bin? Cheers
it's in the 'Options' of the rsf fileAny hints for recompressing code.bin? Cheers
EnableCompress : true # Compresses exefs code
I don't even know how to load code.bin in a disassembler, let alone figure out the code... hahaHas anybody looked at a binary (as in CPU instructions) yet? If so any changes, even included strings or something.
Still multiple xorpads. Only it was weird for that devmenu content, generated exefs and exheader as 'devmenu' and both were 1MB big. Probably the file used a diferent encryption.OK, then according to you (because I haven't tried myself) the modified CTR_Keygen generates a single xorpad for a NCCH partition or is still divided in romfs, exefs and exheader; or both?