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

  • Thread starter Thread starter d0k3
  • Start date Start date
  • Views Views 935,380
  • Replies Replies 4,476
  • Likes Likes 71
Processing NCSD "SDK09_CiaoIllustClub.3ds"
Partition 0 (Executable)
Code / Crypto: CTR-P-BMDJ / 7x
Decrypt ExHdr/ExeFS/RomFS (2kB/1134kB/63MB)
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/3MB)
Verify ExHdr/ExeFS/RomFS: -/-/OK
Partition 7 (UpdateO3DS)
Code / Crypto: CTR-P-CTAP / Standard
Decrypt ExHdr/ExeFS/RomFS (0kB/0kB/31MB)
Verify ExHdr/ExeFS/RomFS: -/-/OK
Success!

Why Decrypt9 is saying SDK7?
AFAIK, it's SDK11, and the game have an AP flag detected
 
lol no. It allows deleting/restoring it. For example, you can do a system format after removing NNID first so you can format emunand without breaking NNID
The feature is useful, but formatting with tinyformat prevents the NNID from getting unlinked from your console, right? In that case, simply logging in with the NNID should work :unsure:
 
Processing NCSD "SDK09_CiaoIllustClub.3ds"
Partition 0 (Executable)
Code / Crypto: CTR-P-BMDJ / 7x
Decrypt ExHdr/ExeFS/RomFS (2kB/1134kB/63MB)
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/3MB)
Verify ExHdr/ExeFS/RomFS: -/-/OK
Partition 7 (UpdateO3DS)
Code / Crypto: CTR-P-CTAP / Standard
Decrypt ExHdr/ExeFS/RomFS (0kB/0kB/31MB)
Verify ExHdr/ExeFS/RomFS: -/-/OK
Success!

Why Decrypt9 is saying SDK7?
AFAIK, it's SDK11, and the game have an AP flag detected
Why, the output is completely okay (all verifications passed)? I don't see any SDK7 there.

The feature is useful, but formatting with tinyformat prevents the NNID from getting unlinked from your console, right? In that case, simply logging in with the NNID should work :unsure:
That feature is for getting rid of the NNID. In my case I lost both, the password and access to the email I used to set it up and without that feature the only other possibility would have been losing all my stuff. You can try using that feature to port a NNID to another console, but make a backup in any case.
 
Why, the output is completely okay (all verifications passed)? I don't see any SDK7 there.


That feature is for getting rid of the NNID. In my case I lost both, the password and access to the email I used to set it up and without that feature the only other possibility would have been losing all my stuff. You can try using that feature to port a NNID to another console, but make a backup in any case.

Yeah, the Output is completly OK.
I'm just wondering why Decrypt9 show SDK7 since it's SDK11:
http://image.noelshack.com/fichiers/2016/05/1454368292-sdk11.png
 
Okay. Well, I think I know how to add it to the Makefile with an additional build goal, but it will be some work. Plus, the UI version will still need external files, so no one step install. Do you think it would be worth it?
Probably not worth it. We even have to use pasta mode for the CIA to work...

Now we have menuhax and CtrBootManager / BootCtr só we can boot the Homebrew Channel very easily.
 
  • Like
Reactions: d0k3
Probably not worth it. We even have to use pasta mode for the CIA to work...

Now we have menuhax and CtrBootManager / BootCtr só we can boot the Homebrew Channel very easily.
I agree. Not worth it, no point to it and no need to give in to all the whiners who keep asking for a cia version. :P haha

You're trying to make things EASIER on yourself right @d0k3 and you want to throw a cia version into the already messy mix? :P
 
  • Like
Reactions: d0k3
You can try using that feature to port a NNID to another console, but make a backup in any case.
No... That's not how it works. The nnid is attached to a specific console on the server side. You must format your nand through system settings so that Nintendo's servers remove the link, before you can use the nnid on a different system.

What this IS useful for, is to restore your nnid to sysnand, after you've used tinyformat to unlink your nands. Believe me, this is a nice feature, and I hope the million "setting up cfw" guides floating around get updated to mention both tinyformat and this particular feature, when talking about unlinking the nands.

Probably not worth it. We even have to use pasta mode for the CIA to work...

Now we have menuhax and CtrBootManager / BootCtr só we can boot the Homebrew Channel very easily.
Don't forget hblauncher_loader :P
 
Last edited by urherenow,
  • Like
Reactions: klear
good day @d0k3, i just want to ask some few noob question...

i have a N3DS. we all know that if we format a NAND (either sys or emu, lets make the example emuNAND) it will create a new SD-ID...
what i mean is the folder of ID1 and ID2 in "X:/Nintendo 3DS/ID1/ID2" where the cia are being installed...

i backed up the X:/Nintendo 3DS/OLD-ID1/OLD-ID2 and formated the emuNAND using system settings...
upon finishing initial setup (name/date/time/region) it created a X:/Nintendo 3DS/NEW-ID1/NEW-ID2

i tried to put the contents of X:/Nintendo 3DS/OLD-ID1/OLD-ID2 that i backed up inside the the X:/Nintendo 3DS/NEW-ID1/NEW-ID2
but when i started the new emuNAND, it doesnt detect the games i installed on the old emuNAND even i put the contents of old emunand SD-ID to new emunand SD-ID...

i believe that there should be something to backed up first inside the nand before doing the formating thing and restore it inside the new nand, so we doesnt need to re install each game over and over again...

the question is what part of NAND should i back up first before formating the nand so that the new nand will detect the old contents without reinstaling each game/app again? thanks and have a nice day...
 
good day @d0k3

the question is what part of NAND should i back up first before formating the nand so that the new nand will detect the old contents without reinstaling each game/app again? thanks and have a nice day...
You shouldn't format emunand. You should format sysnand, and you should use tinyformat to do it, not system settings.

Search for eshopmovingtools and have a good long read, if you really want to do things the way you are going. It's so much faster to just restore your emunand to the way it was (you did make a backup, didn't you?) and format sysnand instead (with the SD card removed).

Edit: Dunno why I ended with that. Use tinyformat on sysnand, not format with card removed.
 
Last edited by urherenow,
good day @d0k3, i just want to ask some few noob question...

i have a N3DS. we all know that if we format a NAND (either sys or emu, lets make the example emuNAND) it will create a new SD-ID...
what i mean is the folder of ID1 and ID2 in "X:/Nintendo 3DS/ID1/ID2" where the cia are being installed...

i backed up the X:/Nintendo 3DS/OLD-ID1/OLD-ID2 and formated the emuNAND using system settings...
upon finishing initial setup (name/date/time/region) it created a X:/Nintendo 3DS/NEW-ID1/NEW-ID2

i tried to put the contents of X:/Nintendo 3DS/OLD-ID1/OLD-ID2 that i backed up inside the the X:/Nintendo 3DS/NEW-ID1/NEW-ID2
but when i started the new emuNAND, it doesnt detect the games i installed on the old emuNAND even i put the contents of old emunand SD-ID to new emunand SD-ID...

i believe that there should be something to backed up first inside the nand before doing the formating thing and restore it inside the new nand, so we doesnt need to re install each game over and over again...

the question is what part of NAND should i back up first before formating the nand so that the new nand will detect the old contents without reinstaling each game/app again? thanks and have a nice day...
I can add to this, this does not work because the encryption is different for that stuff inside the OLD-ID1 folder (vs the NEW-ID1 folder). eshopmovingtools is the way to go, but you'd really be better off formatting SysNAND for the unlink insterad of EmuNAND. If you haven't made a backup of your EmuNAND... you might still be able to transfer the SysNAND over.
 
Last edited by d0k3,
  • Like
Reactions: noctis90210
@d0k3
Here's one for you, could not access eshop after unlinking Nands by formatting sysnand.

Tiny format was not out when I first made my emunand.

Well with your new backup nnid option I was able to fix this.

Backup emunand, use tiny format on emunand, go through setup to get nnid setup. Dump nnid with decrypt9, restore emunand backup and then finally restore nnid backup on emunand.

Things looked bad for a few moments but it all worked out.

Kudos to you for the new features!!!
 
  • Like
Reactions: d0k3
Yeah, the Output is completly OK.
I'm just wondering why Decrypt9 show SDK7 since it's SDK11:
http://image.noelshack.com/fichiers/2016/05/1454368292-sdk11.png
Pretty sure the crypto used is different than the SDK version... (i could be totally wrong though).
I think Shadowtrance is right. I also checked in the source code. If it says '7x crypto', that also means 7x crypto and nothing else. 7x is just the type of crypto that was introduced with 3DS FW 7.x and is by now used by basically everything.
 
Opening slot0x25KeyX.bin ...
Opening seeddb.bin ...
Opening ncchinfo.bin ...
Number of entries: 2
0: /0004000000030700.Main.exheader.xorpad (1MB)
Using keyslot: 2C
1: /0004000000030700.Main.exefs_norm.xorpad (4MB)
Using keyslot: 2C
NCCH Padgen: succeeded!

Press B to return, START to reboot.
http://image.noelshack.com/fichiers/2016/05/1454423212-d9ui.png

Fine in the output file, but there is something hidden in the UI.
I guess it's because the filename is too long.
 
Opening slot0x25KeyX.bin ...
Opening seeddb.bin ...
Opening ncchinfo.bin ...
Number of entries: 2
0: /0004000000030700.Main.exheader.xorpad (1MB)
Using keyslot: 2C
1: /0004000000030700.Main.exefs_norm.xorpad (4MB)
Using keyslot: 2C
NCCH Padgen: succeeded!

Press B to return, START to reboot.
http://image.noelshack.com/fichiers/2016/05/1454423212-d9ui.png

Fine in the output file, but there is something hidden in the UI.
I guess it's because the filename is too long.
Yeah it does that. haha No line wrapping in place...
 
Opening slot0x25KeyX.bin ...
Opening seeddb.bin ...
Opening ncchinfo.bin ...
Number of entries: 2
0: /0004000000030700.Main.exheader.xorpad (1MB)
Using keyslot: 2C
1: /0004000000030700.Main.exefs_norm.xorpad (4MB)
Using keyslot: 2C
NCCH Padgen: succeeded!

Press B to return, START to reboot.
http://image.noelshack.com/fichiers/2016/05/1454423212-d9ui.png

Fine in the output file, but there is something hidden in the UI.
I guess it's because the filename is too long.
Yup, nothing much that can be done there. That is only the filesize, though. BTW, @Shadowtrance, looking great! Tbh I haven't had a look in a while.
 

Site & Scene News

Popular threads in this forum