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

  • Thread starter Thread starter d0k3
  • Start date Start date
  • Views Views 935,174
  • Replies Replies 4,476
  • Likes Likes 71
Would it be able to detect which nand was in use or would the switch need to be selected manually?
If you should run Decrypt9 from EmuNAND, it can't get access to SysNAND at all :). Doesn't matter much, though, as most EmuNANDs should be well beyound 9.2 anyways. I meant, running Decrypt9 from SysNAND and processing EmuNAND.

As for how to implement it... if they users say they will need all of the features I named above, then I'll have to somehow implement a switch option (to switch between processing EmuNAND and SysNAND). If they only need a subset, I'll add EmuNAND features alongside SysNAND features ("Dump ticket.db" and "dump ticket_emu.db" would be two separate options then).
 
If you should run Decrypt9 from EmuNAND, it can't get access to SysNAND at all :). Doesn't matter much, though, as most EmuNANDs should be well beyound 9.2 anyways. I meant, running Decrypt9 from SysNAND and processing EmuNAND.

As for how to implement it... if they users say they will need all of the features I named above, then I'll have to somehow implement a switch option (to switch between processing EmuNAND and SysNAND). If they only need a subset, I'll add EmuNAND features alongside SysNAND features ("Dump ticket.db" and "dump ticket_emu.db" would be two separate options then).

Ha oh duh I should have realized that. I haven't put emunand on my N3DS yet since there isn't much of a benefit to it.
 
New release coming up soon, but, in the meantime, I had a short discussion with Archshift about EmuNAND features... In short, I think rather than releasing two different builds, or implementing a malfunctioning NAND switch feature, I decided it would be best to have EmuNAND functionality in the main build, via additional menu entries.

These features are eligible for EmuNAND:
  • Dump ticket_emu.db
  • Decrypt Titlekeys (EmuNAND)
  • Dump EmuNAND partitions
  • EmuNAND backup
  • Inject EmuNAND partitions
  • EmuNAND restore
I'm unsure if all would be needed, so I ask the users: Which features would you want for EmuNAND, and which will you actually use?

Dump ticket_emu.db is needed for downloading eshop games.

Decrypt Titlekeys (EmuNAND) is neeeded for downloding eshop games in .3ds format for cryptofixing.

EmuNAND backup + EmuNAND restore is not needed.It is held back on speed by the 3ds.You can backup + restore with emuNANDTool in a fraction of the time.

Dump EmuNAND partitions + Inject EmuNAND partitions i can't see a need for them.Maybe someone else might need them.

For more features i would like to be able to dump the seeddb.bin.If you can't dump the seeddb.bin just the 00000000 file would be fine.

So all you would need is one more menu entrie with dump ticket_emu.db,dump decTitleKeys_emu.bin and dump seeddb.bin.
 
Dump ticket_emu.db is needed for downloading eshop games.

Decrypt Titlekeys (EmuNAND) is neeeded for downloding eshop games in .3ds format for cryptofixing.

EmuNAND backup + EmuNAND restore is not needed.It is held back on speed by the 3ds.You can backup + restore with emuNANDTool in a fraction of the time.

Dump EmuNAND partitions + Inject EmuNAND partitions i can't see a need for them.Maybe someone else might need them.

For more features i would like to be able to dump the seeddb.bin.If you can't dump the seeddb.bin just the 00000000 file would be fine.

So all you would need is one more menu entrie with dump ticket_emu.db,dump decTitleKeys_emu.bin and dump seeddb.bin.
Thank you! The 00000000 file (or the seeddb.bin) can only be dumped with a hardmod ;). You need to be on 9.6x to even have that file in your NAND, so there's nothing we can do with the exploits for NAND reading only working up to 9.2. As for dumping ticket_emu.db and EmuNAND titlekey decrypt - yeah that's how I see it, too at the moment. I do hope other people will give their opinion, too, though.
 
Thank you! The 00000000 file (or the seeddb.bin) can only be dumped with a hardmod ;). You need to be on 9.6x to even have that file in your NAND, so there's nothing we can do with the exploits for NAND reading only working up to 9.2. As for dumping ticket_emu.db and EmuNAND titlekey decrypt - yeah that's how I see it, too at the moment. I do hope other people will give their opinion, too, though.

You don't need a hard mod for o3ds it has 10.1 emunand to dump the file from.

And for n3ds with a hard mod use emuNANDTool to inject nand dump and you can dump the file.
 
  • Like
Reactions: d0k3
You don't need a hard mod for o3ds it has 10.1 emunand to dump the file from.

And for n3ds with a hard mod use emuNANDTool to inject nand dump and you can dump the file.
Good point! Alright, dumping seeddb.bin will go there as well.

EDIT: But, you'll have to test it, as I have an N3DS and can't do that ;).
 
Last edited by d0k3,
  • Like
Reactions: key1340
New release, this is what's new:
  • Universal ncchinfo.bin support. Meaning: whatever you use to generate the ncchinfo.bin file, Decrypt9 will take it and generate your xorpads.
  • A warning message and a simple unlock feature for dangerous features (still needs DANGER_ZONE enabled).
  • Reorganized NAND partition dump / inject feature. You can now dump CTRNAND and TWLN separately.
  • Further improved error handling for Secure3 and Secure4 crypto.
Especially for the first one, a lot of people will be happy about. Decrypt9 will now also correctly process the ncchinfo.bin generated by Riku's 3DS Simple CIA Converter. If you should find any ncchinfo.bin file Decrypt9 doesn't work with (or generates wrong results), just write in thread and I'll see what I can do.
 
New release, this is what's new:
  • Universal ncchinfo.bin support. Meaning: whatever you use to generate the ncchinfo.bin file, Decrypt9 will take it and generate your xorpads.
  • A warning message and a simple unlock feature for dangerous features (still needs DANGER_ZONE enabled).
  • Reorganized NAND partition dump / inject feature. You can now dump CTRNAND and TWLN separately.
  • Further improved error handling for Secure3 and Secure4 crypto.
Especially for the first one, a lot of people will be happy about. Decrypt9 will now also correctly process the ncchinfo.bin generated by Riku's 3DS Simple CIA Converter. If you should find any ncchinfo.bin file Decrypt9 doesn't work with (or generates wrong results), just write in thread and I'll see what I can do.

Thanks for the Universal ncchinfo.bin support was getting annoying having to swap to an old Decrypt9 to use Riku's cia converter.Will test out later today.
 
  • Like
Reactions: d0k3
New release, this is what's new:
  • Universal ncchinfo.bin support. Meaning: whatever you use to generate the ncchinfo.bin file, Decrypt9 will take it and generate your xorpads.
  • A warning message and a simple unlock feature for dangerous features (still needs DANGER_ZONE enabled).
  • Reorganized NAND partition dump / inject feature. You can now dump CTRNAND and TWLN separately.
  • Further improved error handling for Secure3 and Secure4 crypto.
Especially for the first one, a lot of people will be happy about. Decrypt9 will now also correctly process the ncchinfo.bin generated by Riku's 3DS Simple CIA Converter. If you should find any ncchinfo.bin file Decrypt9 doesn't work with (or generates wrong results), just write in thread and I'll see what I can do.
Thanks a lot mate! This is an amazing update. :)
 
  • Like
Reactions: d0k3
Could you make the .cia version? Launcher.dat not is very useful for the emuNAND...
Not possible.
Well I've tried just about everything i can think of to get it to work as a cia and it doesn't.
That will never work, 100% guaranteed. CIAs don't have ARM9 access. I will implement some EmuNAND features in the following days, though.
 
Little request: can you add CakeHax like archshift's repo? So we can use Decrypt9.dat in combination with ropCustom, using MSET exploit? Thank youuuuu. :) :)
 
  • Like
Reactions: d0k3
You can already do that with mine, but it isn't up to date with d0k3's version yet.
If you're updating now, there's still a lot of stuff coming... EmuNAND access and seeddb updater meaning tons of new menu entry points and work for you. You may also just update what you can now (f.e. the universal ncchinfo.bin support, without changing anything in your menu) and wait until the more recent features are finished.
 
If you're updating now, there's still a lot of stuff coming... EmuNAND access and seeddb updater meaning tons of new menu entry points and work for you. You may also just update what you can now (f.e. the universal ncchinfo.bin support, without changing anything in your menu) and wait until the more recent features are finished.
Yeah I've held off updating because i knew there was more coming, plus I've been busy working on my mobile game / assignments etc.
 
  • Like
Reactions: d0k3
I've got something new to test for people with hardmods... not ready yet, but I found a newer implementation of Normatts sdmmc.h and the FATFS file io routines. In theory, we'd have faster file operations with this, but this is also some pretty low level stuff and possibly somewhat dangerous. I can't and I won't test this, as I still don't have a hardmod.

We'd need to test reading and writing, with several features (NAND backup / restore, partitions inject, also small stuff such as ticket dumping). The results of each operation have to be verified (check if the dumped files are still the same as with the earlier version).

So, anyone willing to give a helping hand? As I said, I still need some time to implement this, and I won't code it if no one will test it.
 
Alright, new release, and a big one this time:
  • Includes the CakeHax ROP launcher.dat (same as Archshifts & Shadowtrances build)
  • Includes EmuNAND features (dumping ticket_emu.db and decrypting titlekeys from EmuNAND)
  • Also includes a strictly-limited-to-EmuNAND seedsave dumper

Seedsave is the file required for generating the seeddb.bin, also known as the "00000000" file. Proper seeddb.bin generator still coming up. Also, all EmuNAND features untested - the only critical part is the EmuNAND checker, though, which may give a false negative (meaning the feature won't be executed, so no damage done). Menu structure is subject to change with coming features.

Have fun testing and give me feedback! Also, read what I wrote above if you have a hardmod.
 
Last edited by d0k3,
I wish there was a way to use decrypt9 on Ninjhax2.0/Ironhax/Tubehax/ :(
Yeah sadly that is to do with how Brahma (the loader Decrypt9 is built into) and Ninjhax 2 work (or don't work) together. Something drastic changed in the way ninjhax works (pretty different exploit setup) between 1.1 and 2.0 making ANY homebrew that relies on brahma to work, not work. :(
So if you're on 9.2 or below and want to use anything that relies on brahma, ninjhax 1.1 is your only option (or the MSET or spider version in Decrypt9's case).
Above 9.2, you're out of luck at the moment. :(
 
Last edited by Shadowtrance,

Site & Scene News

Popular threads in this forum