YesI'm feeling extremely dumb, but I have to ask it.
Is it normal to get different md5 numbers from my NAND backup when I use Decrypt9 after rebooting my 3DS?
YesI'm feeling extremely dumb, but I have to ask it.
Is it normal to get different md5 numbers from my NAND backup when I use Decrypt9 after rebooting my 3DS?
#r3Tools pic.twitter.com/Hcrdntn8yT
— 173210 (@173210) March 5, 2016
I saw this and my reaction was basically "you wot mate?"
@173210 was one of the critics of rxtools so hopefully he didn't import any of the bad parts.Could have at least merged a decent CFW with it. lmao
Then again i guess rx isn't too bad now that all the broken tools are gone. haha
That's strange... Although it is stupid to ask, you used the proper firmware90.bin file? Maybe somethign else special with that 3DS?So did i...
I did the same, ran from hbl first for reference then ran the "test" from a9lh.
Sorry, there was a bug in yesterdays release. Just download the newest release (see below) and it should be fine).I'm trying to decrypt my VC SNES mario world eur .cia (build with groovycia) but...
decrypt9log: Code / Crypto: KTR-N-UAEE / Secure4 Seed Loading slot0x01KeyX.bin: not found Failed!
Maybe, if it is useful. What are those BOSS files used for?@d0k3 Any chance you could add boss file decryption in the future?
Keyslot 0x38 is involved in decrypting them. I'm working on a new tool and until now it has been a pain to get decrypted files... >_<
Attached is a sample boss file for testing.
So someone made this into a CFW.
https://github.com/173210/r3tools
lol
https://twitter.com/173210/status/706041377889452032
I actually like this, and it's coming coming from @173210, too! Tbh, I never tried rxMode, but I personally think that it isn't that bad at all. The rxTools part was the bad part of this, and this seems to be gone now. I also still think that the better solution to this would be a (ARM9 based9?) frontend loader for CFW, Decrypt9 and EmuNAND9. GodMode9, too, once that is usable enough. And yup, that other problem is that it gives people possibilities they can't handle.
IIRC, CtrBootManager9 works on Brahma2 too, not only on A9LH.I also still think that the better solution to this would be a (ARM9 based9?) frontend loader for CFW, Decrypt9 and EmuNAND9. GodMode9, too, once that is usable enough. And yup, that other problem is that it gives people possibilities they can't handle.
Probably does but who else but the author can actually compile it? lol damn cmake....IIRC, CtrBootManager9 works on Brahma2 too, not only on A9LH.
Used the new build. I got 2 failed tests with self test this time. Updates ref from hbl.That's strange... Although it is stupid to ask, you used the proper firmware90.bin file? Maybe somethign else special with that 3DS?
Sorry, there was a bug in yesterdays release. Just download the newest release (see below) and it should be fine).
Maybe, if it is useful. What are those BOSS files used for?
I actually like this, and it's coming coming from @173210, too! Tbh, I never tried rxMode, but I personally think that it isn't that bad at all. The rxTools part was the bad part of this, and this seems to be gone now. I also still think that the better solution to this would be a (ARM9 based9?) frontend loader for CFW, Decrypt9 and EmuNAND9. GodMode9, too, once that is usable enough. And yup, that other problem is that it gives people possibilities they can't handle.
Also, new release. Yesterdays release had a bug in the NCCH Decryptor Secure4 crypto feature and also a smaller one in the selftest feature. Nobody is perfect . This is now fixed.
New in this relase:
The readme now again provides descriptions for everything that is in Decrypt9. Oh, and you need to update your selftest reference data.
- Fixed the NCCH decryptor Secure4 bug
- Fixed and extended the selftest feature
- Updated the readme for the new features
Which two failed?Used the new build. I got 2 failed tests with self test this time. Updates ref from hbl.
Not console unique. The file is called slot0x05KeyY.bin.@d0k3 with your latest commit you require the slot 0x05 keyY to be present to mount N3DS ctrNand on a9lh, any help about how to dump that as it's supposedly console unique ? (according to @Reisyukaku 's pastebin)
Which two failed?
Not console unique. The file is called slot0x05KeyY.bin.
On O3DS A9LH? Both are normal and expected. ncch_7x_key / ncch_sec3_key / ncch_sec4_key should have also failed but if they don't, whatever.Running selftest...
Opening d9_selftest.ref ...
Passed tests:
nand_cid_hard
sha256
sha1
aes_cnt_ctr
aes_cnt_twl
aes_ttk_enc
aes_ttk_dec
ncch_std_key
ncch_7x_key
ncch_sec3_key
ncch_sec4_key
nand_ctro_key
nand_ctrn_key
nand_agb_key
nand_frm_key
titlekey
16 of 18 tests passed
Failed tests:
nand_cid_mem
nand_twl_key
2 of 18 tests failed
Creating d9_selftest.lst ...
Run Selftest: succeeded!
interesting, i ran the test on my N3DS A9LH and failed both of the same tests with nand_7x_key and nand_ctrn_key, i have slots 0x25,0x1B,0x18 keyXs and 0x05keyY on the rootRunning selftest...
Opening d9_selftest.ref ...
Passed tests:
nand_cid_hard
sha256
sha1
aes_cnt_ctr
aes_cnt_twl
aes_ttk_enc
aes_ttk_dec
ncch_std_key
ncch_7x_key
ncch_sec3_key
ncch_sec4_key
nand_ctro_key
nand_ctrn_key
nand_agb_key
nand_frm_key
titlekey
16 of 18 tests passed
Failed tests:
nand_cid_mem
nand_twl_key
2 of 18 tests failed
Creating d9_selftest.lst ...
Run Selftest: succeeded!
Also, expected results. The slot files are not loaded for that test - otherwise it would be pointless, we're checking if the keys are correctly set from the start .interesting, i ran the test on my N3DS and failed both of the same tests with nand_cid_test and nand_ctrn_key, i have slots 0x25,0x1B,0x18 keyXs and 0x05keyY on the root