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

[Shadowtrance]

emunand: the NCSD header (first 0x200 bytes of nand) is moved to about 1 GB (3BA00000 old3ds physical offset) in the sdmc card.
the rest of the nand (offset 0x200 and beyond) starts at sdmc physical offset 0x200 and continues uninterrupted to the end of the nand

With rednand, the entire nand is contiguous, essentially idenical to the sysnand image. It is placed anywhere in the unallocated sdmc region.

Ahh there you go then, was hoping someone would clear that up because i couldn't really remember. haha

 

[zoogie]

Ahh there you go then, was hoping someone would clear that up because i couldn't really remember. haha

I would just add that the NCSD offset in emunand can sometimes be at 3AF00000, which is likely the source of some of the emunand detection problems I hear about. The offset is also different for n3ds of course, but the same general structure applies.

 

[Shadowtrance]

Alright, finally a new release.
And, for the tinkerers:
As for the hidden NAND_SWITCH feature - that enables switching between EmuNAND and SysNAND. According to previous tests, EmuNAND access is unreliable and needs more testing. As long as you don't write to EmuNAND, nothing bad will happen though. Also, be careful with stuff dumped from EmuNAND and don't use anything on EmuNAND if you don't have an EmuNAND installed on your SD card.

In short: NAND_SWITCH is not dangerous in itself, but accessing EmuNAND is unreliable, while DANGER_ZONE (on SysNAND) is reliable, but dangerous if the user makes an error. Hope that makes sense.

@Shadowtrance :
If you want to include NAND_SWITCH in the GUI version, you hace some work ahead of you. You'll need to edit DrawSplashLogo() to also display the current NAND, and you have to make the new SetNand() function work in the menu. Maybe it's better to wait until it is better tested? I will come up with a cleaner implementation later.

Cool. Got that partly done already as seen in the pic below, think i got the placement alright.
And I'll look at the rest when it isn't 4am, unless you beat me to it. haha

Spoiler: [B]CLICK ME!![/B]

 

[d0k3]

emunand: the NCSD header (first 0x200 bytes of nand) is moved to about 1 GB (3BA00000 old3ds physical offset) in the sdmc card.
the rest of the nand (offset 0x200 and beyond) starts at sdmc physical offset 0x200 and continues uninterrupted to the end of the nand, stopping just short of the NCSD header.

With rednand, the entire nand is contiguous, essentially idenical to the sysnand image. It is placed anywhere in the unallocated sdmc region.

Alright, didn't know that. Everyone enabling the NAND_SWITCH option hast to be careful. What @zoogie wrote means that NAND backup and NAND restore will not work properly for EmuNAND yet. There won't be any trouble with anything else, though.

--------------------- MERGED ---------------------------

I would just add that the NCSD offset in emunand can sometimes be at 3AF00000, which is likely the source of some of the emunand detection problems I hear about. The offset is also different for n3ds of course, but the same general structure applies.

So, any way to detect where the NCSD offset actually is at?

 

[Shadowtrance]

Well i give up... i can't get the switching to work cause I'm a noob. lol

Also, not sure how you got your latest version to compile without including fatfs/sdmmc.h in decryptor.c because it errors out and fails if it isn't included.

 

[d0k3]

Well i give up... i can't get the switching to work cause I'm a noob. lol

Also, not sure how you got your latest version to compile without including fatfs/sdmmc.h in decryptor.c because it errors out and fails if it isn't included.

I'll take a look later, alright? Keep in mind that it doesn't work properly yet (no NAND backup / restore, and everything else unreliable according to the last round of tests).

 

[Shadowtrance]

I'll take a look later, alright? Keep in mind that it doesn't work properly yet (no NAND backup / restore, and everything else unreliable according to the last round of tests).

Yeah cool. I was just trying to add it myself, but clearly I'm missing something (as I've said many times, I'm not the code guy lol still figuring things out as i go), I'm the graphics and hardware guy.

 

[KashiToxicBlood]

decrypt9 screenshot from new 3ds capture card

 

[KashiToxicBlood]

screenshot without decrypt9 UI

 

[d0k3]

Thank you! I'll use both of them on the op with your permission.

 

[KashiToxicBlood]

Thank you! I'll use both of them on the op with your permission.

yeah you can use them lol, i generally don't care if people use it, in fact it's mainly for educational purposes for people who want to know what it looks like

 

[Shadowtrance]

hah! nice pics Wish i could get my hands on capture card that doesn't cost what a new console does...

@d0k3 Messing with minimizing the drawstring text on main menu top screen.... most of it is actually in the image.

Thoughts? not the best pic (camera flat, phone camera not great).

Spoiler: CLICK ME!

 

[d0k3]

hah! nice pics Wish i could get my hands on capture card that doesn't cost what a new console does...

@d0k3 Messing with minimizing the drawstring text on main menu top screen.... most of it is actually in the image.

Thoughts? not the best pic (camera flat, phone camera not great).

Spoiler: CLICK ME!

The placement and the mix of fonts looks a little... off. If the placement was better, it could work, though. The (X) should be in the "current NAND" font, btw. I think there is little use in mimizing the DrawString text, though. And the UI will be less flexible this way.

 

[Shadowtrance]

The placement and the mix of fonts looks a little... off. If the placement was better, it could work, though. The (X) should be in the "current NAND" font, btw. I think there is little use in mimizing the DrawString text, though. And the UI will be less flexible this way.

Yeah true, was just an idea i was toying with that isn't that great anyway lol and yeah i guess it would make it less flexible too.
I'll just find a nice spot for the nand switch and maybe use the new font color that matches the image text.


Edit: Anyway, new version(s) here with current changes (nand switch gone) but there is 2 separate versions and they display which version you're using on the top screen and also for the emunand version i made a change so that when you dump your ticket.db it will be called ticket_emu.db. Most people only want that part emunand compatible anyway, so thought I'd add that.

READ THE README.txt!

https://mega.nz/#!PZIygJiZ!1NCnQ6aOWQCyBxgh24-OO4RGHlwRQG63p4Iprql5pQY

 

[pakrett]

I really want to know the way to decrypt an encrypted native-firm.bin or .cia like rxTools (2.6 & 3.0) does in the "installation data suite".
I tried the "dump system titles" option in the rxtools menu and after that it asked me if I want to decrypt them but the result files are not in the same format that the files into rxTools\data\ ...
I don't really undertand, so I need help. Can I do it with decrypt9 ?
I already posted my question here : https://gbatemp.net/threads/how-can...s-and-more-specifically-a-native-firm.395880/

 

[hashcheck1]

Is there anyway to run this on n3ds xl 9.0 yet? Via oot or gateway

 

[Shadowtrance]

Is there anyway to run this on n3ds xl 9.0 yet? Via oot or gateway

Yes it can be run on n3ds xl 9.0, no it can't be run from oot or gateway.

Download the zip from the link above and read the README.txt (there's an mset, profile exploit version for those who don't have cubic ninja)..

 

[k8099]

Yeah true, was just an idea i was toying with that isn't that great anyway lol and yeah i guess it would make it less flexible too.
I'll just find a nice spot for the nand switch and maybe use the new font color that matches the image text.


Edit: Anyway, new version(s) here with current changes (nand switch gone) but there is 2 separate versions and they display which version you're using on the top screen and also for the emunand version i made a change so that when you dump your ticket.db it will be called ticket_emu.db. Most people only want that part emunand compatible anyway, so thought I'd add that.

READ THE README.txt!

https://mega.nz/#!PZIygJiZ!1NCnQ6aOWQCyBxgh24-OO4RGHlwRQG63p4Iprql5pQY

i want to know,is this version can backup&restore eumnand?(i mean if i use the emunand version)

when i try to backup eumnand,i get the nand.bin,i do not sure it is right thing.if it is eumnand backup,can you rename it with "emu" when decrypt9 creat it.

 

[Shadowtrance]

i want to know,is this version can backup&restore eumnand?(i mean if i use the emunand version)

when i try to backup eumnand,i get the nand.bin,i do not sure it is right thing.if it is eumnand backup,can you rename it with "emu" when decrypt9 creat it.

The emunand version is mainly for ticket.db dumping that people wanted.
For emunand backup/restore you're better off using the pc tool for that at the moment.

 

[Ninoh-FOX]

i has a nand backup from my death old new3ds, i was buy a new3ds again, now... Can i decripter my old nand backup and flash in my new new3ds?