About the ncch..thanks I havnt noticed that...i'll fix it next version...
Do you extract the files with a key? or just extracting encrypted files?
I'm extracting without a key (leaving the box blank)
Quick way to check is to do this:
- click NCCH0 in the upper tree view then extract RomFS0 to a file. (e.g Test0.bin)
- click NCCH1 in the upper tree view then extract RomFS0 to a file. (e.g Test1.bin)
- click NCCH2 in the upper tree view then extract RomFS0 to a file. (e.g Test2.bin)
Then open all three files in a hex-editor, or get the CRC32 / MD5 checksums of the files
the files you get will all be different because the starting offset is wrong.
You need to get the same CRC/MD5 for file no matter which page you are viewing when extracting.
"cxt.currentNcch" needs to be changed to use the number at the end of the file. e.g:
When extracting Exe/RomFS0, the program should see the 0 at the end of the name and use "cxt.cci.FirstNCCHOffset"
When extracting Exe/RomFS1, the program should see the 1 at the end of the name and use "cxt.cci.SecondNCCHOffset"
When extracting Exe/RomFS2, the program should see the 2 at the end of the name and use "cxt.cci.ThirdNCCHOffset"
Not too sure how to do that in code as I'm not a programmer (but I can read and understand some code)
I've added some details in my post above.