It should be possible, yes.It's possible to make multiple xorpad with drag&drop 2 or 3 .3ds on ctrkeygen.py ?
Should just be able to select however many .3ds files at the same time and drag n drop on the script.
It should be possible, yes.It's possible to make multiple xorpad with drag&drop 2 or 3 .3ds on ctrkeygen.py ?
Indeed it is.The new decrypt9 is very fast oO
Thanks a lot
Yes, that should be possible. Just try it!It's possible to make multiple xorpad with drag&drop 2 or 3 .3ds on ctrkeygen.py ?
A couple of options for new icon... ignore the grey background, icon starts at the purple edges. Thoughts?
I also got Uncart added but sadly something goes horribly wrong after it finishes dumping and you press B to exit back to the menu, where you should have control of the menu again but you don't.
It doesn't load the top image after exiting and bottom images don't change if you move left/right, sd space is messed up too.
I think both are good options, but the left one fits better with the general theme.
That might be some of uncart's ASM not playing nice with Decrypt9's. Or maybe, it is not. I'm pretty sure you compared the source files in WinMerge (or similar). Are there differences in the .S files? If so, I doubt we can fix it. If not, we might be able to find the reason.
Another possibility would be that uncart does something 'temporarily irreversable', meaning something that can only be reversed by restarting the console, same as f.e. Brahma, which doesn't allow you to return once the payload is executed.
@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.
I'm thinking about making the work directory an option. I do prefer having all out of the way and so do you, but it's almost sure that this will lead to confusion. Plus, every other software out there wants the "slot..." file, "ncchinfo.bin" file and others in the root directory.No problem. I like the Decrypt9 directory instead of everything on root. It makes my filesystem cleaner. I was able to get the xropads working once I found out the correct folder.
Yeah the work dir is a good idea, got enough crap on the root of my sd card as it is haha Just something people have to get used to it i guess.I'm thinking about making the work directory an option. I do prefer having all out of the way and so do you, but it's almost sure that this will lead to confusion. Plus, every other software out there wants the "slot..." file, "ncchinfo.bin" file and others in the root directory.
I still think that how the restore NAND option is accessed in the menu is too dangerous. If there is a chance something bad happens, it will happen, and just having to press an additional button is not a good layer of security. Picture an user accidentially triggering that option, who panics and force shutdowns their 3DS. Even Roxas75 gets criticism from time to time for including the NAND restore and inject options in a submenu. Also, the NAND restore option (in my opinion) should not be used by someone who doesn't have a hardmod at all. As of now, the restore NAND option is the only really dangerous option in Decrypt9, for all others basically nothing bad can happen, even with bad input files, force shutdowns and otehr stuff users might come up with.
I'd suggest you make it 'more impossible' to trigger that option by accident. For example, by starting Decrypt9 in a 'safe mode', which the user has to actively switch to even get the NAND restore option in the menu. Or, put a disclaimer, with visual clues about danger (f.e. exclamation mark, red letters...) between the menu and the execution of the NAND restore option. Then require the user to input a key combination to continue. Or do two versions of Decrypt9, one with, one without the option.
I put some work into the ncchinfo_gen.py scripts. And, yup, ncchinfo v4 is not backwards compatible because the entries are 8 bit longer and include the titleId. It would be pretty easy to write a ncchinfo v3 -> v4 converter though. But, does that make sense? Do people really have old ncchinfo.bin files lying around that they still use to generate XORpads? Also, keep in mind that the CTRdecryptor option (once I finish that) will lead to people using the ncchinfo.bin format less anyways.
The seeddb mystery... I posted here hoping to get some people onboard for solving that (I don't think Archshift will reply on Github). I really think it should be possible to generate the seeddb.bin from nand:\data\<id>\sysdata\0001000f\00000000, but you'd have to be on a recent FW version (which I can't do) to even get that. Also, I'd like to know if that file is identical for every 3DS or if it is unique. Not a pressing issue, but knowing that you've got three 3DSs with hardmods lying around, you are one of the few persons who can find out on their own .
Last point - decryption (and encryption, of course) of TWL - I'm at it. Can't say much about yet, cause I'm still trying to figure out how to handle the different endianness of the TWL partitions. Check out the last few posts here if interested.
Cool to see you're getting somewhere (sort of) with TWL stuff. Hopefully it can all be decrypted and we'll have full nand decryption (i think, not missing anything am i?)
Ah yeah, knew there was one i was missing, but yeah probably not much use adding it really. Could add it for completeness sake but that's about it i suppose.
edit: @d0k3 the nand backup / restore option is now safer. Check latest commit.
Here is some info on getting the seeddb.bin from another forum.
Where are you getting the external seed value? The game you've posted is successfully cryptofixed, yes, but it makes no sense that a "converter" would be able to remove encryption that requires sha256 + the 3ds's hardware aes engine to decrypt.
I can do the cryptofix dumping the seeddb.bin from the NAND.
Do you know where the seeddb.bin is located? I searched in my decrypted emunand backup and i can't find it
It's in NAND\data\(console exclusive)\sysdata\0001000f, the 00000000 file is the seeddb.bin
Yeah I found that file, I tried to rename it seeddb.bin and it doesn't seem to work with the last decrypt9 version. Did I miss something?
There aren't the steps. You need to use ctrKeyGen.py with the seeddb.bin renamed as 00000000.sav, after you will need to generate the xorpads via Multi Decryptor, after use xorer for decrypt the ROM and finally do cryptofix with mergerom. Despite this, I use a method envolving converting to cia.
I haven't done a release yet with the latest changes, still got some UI stuff i want to make changes to. But i also got assignments to finish so that will have to wait for now.I've seen it - much better that way! The additional input won't matter to those who actually want to use that option, and accidental triggerers will thank you for that. Do you want me to put a link into the first post to your release?
That makes sense, somehow. Thank you! I can't test, but I'm pretty sure that puts us a step nearer to the solution.
No problem, that can still wait . Just let me know when to put up a link! Progress for me also has been a bit slow these last few days. Damn TWL decryption :/. I guess I'll make NCCH padgen routines backward compatible with NCCH v3, by the way. It is just a few lines of code, and perhaps a lot of people will be happier with that than with the current solution.I haven't done a release yet with the latest changes, still got some UI stuff i want to make changes to. But i also got assignments to finish so that will have to wait for now.
I think that sums it up pretty good:Yeah would be handy to have it backward compatible (if possible). Might not get used a lot but still handy.
How's the TWL stuff going anyway?
Thanks for the bug report! So... you tried all possible options, correct?I have a New 3DS (9.2), I tried to dump my title keys but with all the options, I always lack some of them for my legit DSiWare games. It just finds 8, but I have 17 or 18... I used the SDK Devmenu to check which games are missing (from their titleIDs), and it's completely random.