@atkfromabove:
Thanks a ton for all the testing! Also for doing the risky stuff
. So, the current state is, everything works, but there is some trouble with ncchinfo.bin XORpad generation, correct? To be honest, I never tested that, cause I haven't changed anything except the working dir.
As for that (the working directory) - well, I already suspected that would lead to confusion. I'd like to have the Decrypt9 stuff out of sight, and that is badly needed especially when it's about hundreds of dumped system titles. Or, for the (planned) CTR decryptor - that should not process roms across the SD (as rxTools does) or even in the root folder. I think I should only use the working directory for these two options. Should be less confusing that way.
@Shadowtrance:
Thanks to you for testing the titlekey decryption and the risky stuff, too! I'll give your version a quick test later, then put a link on the first post. Is that okay? I just wonder, with the menu.bin files - that won't work with the Launcher.dat version, correct?
@Asia81 and everyone:
Well, the seeddb. No idea how to get that. If it is in the NAND, we can extract it, but as I said, no idea yet. I'll look into it.
There also is something on 3Dbrew. With the wording there that might even mean that you need a specific seeddb.bin for each (9.6 crypto) game. Also, if that file is on the SYSNAND FAT16 partition, it is not on mine obviously, as I'm on 9.0.0.
The ncchinfo.bin XORpad generator would in theory be downwards compatible, at least with ncchinfo.bin v3 (that's the previous version), but the version check prevents that now.
But, what's the trouble with the seeddb right now? As I understand it, if it is not found you'll get a short error message and the XORpad generator should work regardless (except for the new crypto, of course). Shadowtrance, did you just replace the ncchinfo.bin XORpad generator with an older version?