Homebrew Official [Download] Decrypt9 - Open Source Decryption Tools (WIP)

  • Thread starter Thread starter d0k3
  • Start date Start date
  • Views Views 935,303
  • Replies Replies 4,476
  • Likes Likes 71
For what it's worth, I had no problem decrypting on the 3-3-2016 compilation
Entrypoint - HBL CIA on 9.2.20-U sysNAND [booted from A9LH->AuRei SysNAND]

Firmware 4.5 (Monster 4x4 Cartridge Dump)

Opening /D9Game ...
Processing NCSD "Monster 4x4 3D.3ds"
Partition 0 (Executable)
Code / Crypto: CTR-P-AM4E / Standard
Decrypt ExHdr/ExeFS/RomFS (2kB/2505kB/40MB)
Verify ExHdr/ExeFS/RomFS: OK/OK/OK
Partition 7 (UpdateO3DS)
Code / Crypto: CTR-P-CTAP / Standard
Decrypt ExHdr/ExeFS/RomFS (0kB/0kB/16MB)
Verify ExHdr/ExeFS/RomFS: -/-/OK
Success!

1x processed / 0x failed
NCCH/NCSD Decryptor: succeeded!

Press B to return, START to reboot.

Firmware 9.9 [Megaman Collection 3DS Cartridge Dump = using 7x encryption]

Opening /D9Game ...
Processing NCSD "Megaman Legacy Collection.3ds"
Partition 0 (Executable)
Code / Crypto: CTR-P-BMME / 7x
Decrypt ExHdr/ExeFS/RomFS (2kB/1708kB/461MB)
Verify ExHdr/ExeFS/RomFS: OK/OK/OK
Partition 1 (Manual)
Code / Crypto: CTR-P-CTAP / Standard
Decrypt ExHdr/ExeFS/RomFS (0kB/0kB/0MB)
Verify ExHdr/ExeFS/RomFS: -/-/OK
Partition 6 (UpdateN3DS)
Code / Crypto: CTR-P-CTAP / Standard
Decrypt ExHdr/ExeFS/RomFS (0kB/0kB/5MB)
Verify ExHdr/ExeFS/RomFS: -/-/OK
Partition 7 (UpdateO3DS)
Code / Crypto: CTR-P-CTAP / Standard
Decrypt ExHdr/ExeFS/RomFS (0kB/0kB/34MB)
Verify ExHdr/ExeFS/RomFS: -/-/OK
Success!

1x processed / 0x failed
NCCH/NCSD Decryptor: succeeded!

Press B to return, START to reboot.

Perhaps he's on emuNAND?

My sysnand's my main nand as I've switched my emunand partitions over to it now and it's on 10.6.
 
Last edited by Svaethier,
Time for a new release: The 'a9lh' maintenance release with one big new/fixed feature (I mean Secure4 crypto, if that's not clear).

This is new:
  • This is now a9lh compatible (although a lot of stuff will not work - known issue)
  • Dumping seedsave.bin & updating seeddb from SysNAND (this is a thing with a9lh now)
  • Enabled Secure3 NCCH crypto / padgen on O3DS (need slot0x18KeyX.bin)
  • Enabled Secure4 NCCH crypto / padgen on O3DS / N3DS (need slot0x1BKeyX.bin)
  • Added a selftest feature
This is how the selftest feature works: (1) create the reference data on a known working entrypoint (= not a9lh!), (2) run the selftest on the entrypoint you want to test.

Now we can finally get behind on what cause some stuff on a9lh not to work. @Shadowtrance, and @Svaethier I'm burning to know your selftest result, and everyone elses (on a9lh).
 
Last edited by d0k3,
When you mention A9LH compatible (assuming just dumping emu/sys works as always) are you meaning cold booting straight into A9LH binary? Or do you mean booting a 9.0 nand and launching 3DSX via HBL?
 
When you mention A9LH compatible (assuming just dumping emu/sys works as always) are you meaning cold booting straight into A9LH binary? Or do you mean booting a 9.0 nand and launching 3DSX via HBL?
The former, the last one should have always worked.
 
Time for a new release: The 'a9lh' maintenance release with one big new/fixed feature (I mean Secure4 crypto, if that's not clear).

This is new:
  • This is now a9lh compatible (although a lot of stuff will not work - known issue)
  • Dumping seedsave.bin & updating seeddb from SysNAND (this is a thing with a9lh now)
  • Enabled Secure3 NCCH crypto / padgen on O3DS (need slot0x18KeyX.bin)
  • Enabled Secure4 NCCH crypto / padgen on O3DS / N3DS (need slot0x1BKeyX.bin)
  • Added a selftest feature
This is how the selftest feature works: (1) create the reference data on a known working entrypoint (= not a9lh!), (2) run the selftest on the entrypoint you want to test.

Now we can finally get behind on what cause some stuff on a9lh not to work. @Shadowtrance, and @Svaethier I'm burning to know your selftest result, and everyone elses (on a9lh).
Opening /D9Game ...
Processing NCSD "BOI.3ds"
Partition 0 (Executable)
Code / Crypto: KTR-N-GBAT / FixedKey
Decrypt ExHdr/ExeFS/RomFS (2kB/1768kB/317MB)
Verify ExHdr/ExeFS/RomFS: OK/OK/Fail
Failed!
NCCH/NCSD Decryptor: failed!

Press B to return, START to reboot.

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
nand_ctro_key
nand_ctrn_key
nand_agb_key
nand_frm_key
titlekey
12 of 15 tests passed

Failed tests:
nand_cid_mem
ncch_std_key
nand_twl_key
3 of 15 tests failed

Creating d9_selftest.lst ...
Run Selftest: succeeded!

Press B to return, START to reboot
trying the BOI 3ds right now again. will post results.

the self test succeeded with 0 fails :)
 
Last edited by Svaethier,
  • Like
Reactions: d0k3
Time for a new release: The 'a9lh' maintenance release with one big new/fixed feature (I mean Secure4 crypto, if that's not clear).

This is new:
  • This is now a9lh compatible (although a lot of stuff will not work - known issue)
  • Dumping seedsave.bin & updating seeddb from SysNAND (this is a thing with a9lh now)
  • Enabled Secure3 NCCH crypto / padgen on O3DS (need slot0x18KeyX.bin)
  • Enabled Secure4 NCCH crypto / padgen on O3DS / N3DS (need slot0x1BKeyX.bin)
  • Added a selftest feature
This is how the selftest feature works: (1) create the reference data on a known working entrypoint (= not a9lh!), (2) run the selftest on the entrypoint you want to test.

Now we can finally get behind on what cause some stuff on a9lh not to work. @Shadowtrance, and @Svaethier I'm burning to know your selftest result, and everyone elses (on a9lh).
Created reference from HBL version, ran test from a9lh... on my 9.0 sysnand n3ds. Haven't run it on my other n3ds (10.6 a9lh) yet.

Code:
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
nand_ctro_key
nand_agb_key
nand_frm_key
titlekey
11 of 15 tests passed

Failed tests:
nand_cid_mem
ncch_std_key
nand_twl_key
nand_ctrn_key
4 of 15 tests failed

Creating d9_selftest.lst ...
Run Selftest: succeeded!
 
  • Like
Reactions: d0k3
Ran self test on K9LH after genning on HBL
Code:
Running selftest…
opening d9_selftest.ref …

Passed test:
Nand_cid_hard
Nand_cid_mem
sha256
Sha1
Aes_cnt_ctr
Aes_cnt_twl
Aes_cnt_enc
Aes_ttk_enc
Aes_ttk_dec
Nand_twl_key
Nand_ctro_key
Nand_ctrn_key
Nand_agb_key
Nand_frm_key
Titlekey
14 out of 15 tests passed

Failed tests:
Ncch_std_key
1 of 15 test failed

Creating d9_selftest.lst …
Run selftest: Succeded!
 
Last edited by Toiry921,
Ran self test on K9LH after genning on HBL
Code:
Running selftest…
opening d9_selftest.ref …

Passed test:
Nand_cid_hard
Nand_cid_mem
sha256
Sha1
Aes_cnt_ctr
Aes_cnt_twl
Aes_cnt_enc
Aes_ttk_enc
Aes_ttk_dec
Nand_twl_key
Nand_ctro_key
Nand_ctrn_key
Nand_agb_key
Nand_frm_key
Titlekey
14 out of 15 tests passed

Failed tests:
Ncch_std_key
1 of 15 test failed

Creating d9_selftest.lst …
Run selftest: Succeded!
The failed one is a false alert. Everything works, great!
I can't find the keys that I need to insert into the 0x18 and 0x1B slots.
They should not be too hard to find. Google is your friend, or maybe some other forum.
 
  • Like
Reactions: hobbledehoy899
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!
 
  • Like
Reactions: Madridi
I'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?
 
@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.
 

Attachments

Site & Scene News

Popular threads in this forum