Something looks wrong 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
The tool behaves awkwardly with stuff encrypted with zero keys, however they can simply be extracted without xorpads with ctrtool.
Yeah I thought there would be something like that. But I guessed it would simply be wrong xorpads, not entirely glitched results.
So, summarising, these are the steps to edit dumps of retail games:
1. Create a xorpad of the original 3DS ROM with the modified CTR_Keygen.
2. Decrypt the whole rom, then extract the contents of romfs.
3. Edit whatever you want in the folder that contains the extracted files of romfs.
4. Recompile a whole (temporary) ROM with makerom doing the proper modifications to a rsf file in order to rebuild the romfs folder.
5. Extract romfs of this new temporary ROM.
6. Replace the romfs of the decrypted ROM with the one extracted in step 5.
7. Rexor with original xorpad.
What about that rexoring part? What if the new romfs is bigger than the original?
1. Create a xorpad of the original 3DS ROM with the modified CTR_Keygen.
2. Decrypt the whole rom, then extract the contents of romfs.
3. Edit whatever you want in the folder that contains the extracted files of romfs.
4. Recompile a whole (temporary) ROM with makerom doing the proper modifications to a rsf file in order to rebuild the romfs folder.
5. Extract romfs of this new temporary ROM.
6. Replace the romfs of the decrypted ROM with the one extracted in step 5.
7. Rexor with original xorpad.
What about that rexoring part? What if the new romfs is bigger than the original?
With zero keys. Also, I don't think this works with cia files, you have to use the actual cci.
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.
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.
The purpose is to get a single xorpad as I can understand, instead of one for every partition contained in the NCSD
The modded keygen still generates multiple xorpads, only it uses a NCCH container (CXI, CFA, or content extracted from NCSD) instead of a NCSD (CCI, CSU, 3DS rom).
Any hints for recompressing code.bin? Cheers
Rebuild the whole ncch: makerom.exe -f ncch -target d -rsf gw.rsf -o "%filename%.cxi" -exheader exh.bin -code code.bin -icon icon.bin -banner banner.bin -alignwr
it's in the 'Options' of the rsf fileAny hints for recompressing code.bin? Cheers
Code:
EnableCompress : true # Compresses exefs code
I don't even know how to load code.bin in a disassembler, let alone figure out the code... haha
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?
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.
-
AncientBoi
-
Xdqwerty
what are you looking at? -
The Real Jdbye
*is birb* -
NinStar
-
K3Nv2
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
The Real Jdbye:
they bought their own game on a key site and checked where they came from and it turned out they were review copies he had given out by email to someone
-
-
@
NinStar:
no storefront I'm aware of (at least on pc) requires the devs to pay for the keys they generate
-
-
@
The Real Jdbye:
so that seems to be a pretty common thing, i kinda blame the dev for that one though as they were giving out like 5 keys to someone just because they asked for multiple copies for review for whatever reason and there were multiple people doing this. he should've seen the red flags
-
-
-
