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

[Asia81]

No. Not 128GB cards in general. I have a 128GB card and have no problems out of D9 at all.



If you are worried about clutter you can make a folder on the root of the SD card called Decrypt9 and put all the key files there. This will also make any files made with D9 appear in this folder.

Or you could use the Maintenance options -> Build Key Database and it will build a single file for the keys.

It's not D9Game?

 

[Xenosaiga]

It's not D9Game?

You can have that folder too, But that folder is mainly used for when you are Decrypting CIA files.

 

[Asia81]

Good to know, thanks

 

[d0k3]

"Removed ability to dump / inject rand_seed (this has no practical use)"

Was dump/inject rand_seed going to be something useful? Or was it just something random that was created?

If you find a practical use for it, I'll put it back in (no one has found one so far). Other than that, this is just a bunch of random data, which is most likely not used by the 3DS console at all.

ok

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

same problem

Alright. @runetoonxx2 & @Mthodmn101 - could you try this build and show me the output of it?
https://up1.ca/#t5vlqJX27i6P1T9XImjlrg
I'm still somewhat clueless about what may cause this, but with some testing we should find the issue.

EDIT: replaced the link, the last test build had a small problem.

EDIT2: While you're at it, also provide me with some more info... what did you use to format these SD cards, and how did you format them? Is there an EmuNAND on these SD cards? Are there any other known problems with these cards (you could, f.e. run Windows chkdsk over them).

EDIT3: Also, you don't see anything of the menu, right? It freezes rigth after initialization: success?

@d0k3

Is something like that possible? :
- Build ourselves Decrypt9WIP, with all the keys inside, instead have multiples .bin files at the root.

If yes, how we can do it?

Seconding @Xenosaiga here - the slot0x05keyY.bin file is already no more required. KeyX 0x25 / 0x18 / 0x1B are only required for NCCH decryption. NCCHs might also need the seeddb.bin, which will never be complete. So, including those keys doesn't really make sense.

 

[runetoonxx2]

If you find a practical use for it, I'll put it back in (no one has found one so far). Other than that, this is just a bunch of random data, which is most likely not used by the 3DS console at all.


Alright. @runetoonxx2 & @Mthodmn101 - could you try this build and show me the output of it?
https://up1.ca/#t5vlqJX27i6P1T9XImjlrg
I'm still somewhat clueless about what may cause this, but with some testing we should find the issue.

EDIT: replaced the link, the last test build had a small problem.

EDIT2: While you're at it, also provide me with some more info... what did you use to format these SD cards, and how did you format them? Is there an EmuNAND on these SD cards? Are there any other known problems with these cards (you could, f.e. run Windows chkdsk over them).

EDIT3: Also, you don't see anything of the menu, right? It freezes rigth after initialization: success?


Seconding @Xenosaiga here - the slot0x05keyY.bin file is already no more required. KeyX 0x25 / 0x18 / 0x1B are only required for NCCH decryption. NCCHs might also need the seeddb.bin, which will never be complete. So, including those keys doesn't really make sense.

Formatted using easeus portion manager
64kb clutter size no emunand sysnand very 10.7 USA 3ds

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

Formatted using easeus portion manager
64kb clutter size no emunand sysnand very 10.7 USA 3ds

It freezes after initialization success
Sandisk SD and I made sure my SD wasn't fake as well with h2testw

 

[Xenosaiga]

@runetoonxx2 use Emunand9 right on the 3DS to format.

It will format it the right way every time.

Just load up Emunand9. Push select to dismount the SD card. Put the SD card you want back into the system. And then follow through on formatting.

https://gbatemp.net/threads/release-emunand9-open-source-emunand-formatter-manager.405921/

 

[OLineGuy]

If you find a practical use for it, I'll put it back in (no one has found one so far). Other than that, this is just a bunch of random data, which is most likely not used by the 3DS console at all.


Alright. @runetoonxx2 & @Mthodmn101 - could you try this build and show me the output of it?
https://up1.ca/#t5vlqJX27i6P1T9XImjlrg
I'm still somewhat clueless about what may cause this, but with some testing we should find the issue.

EDIT: replaced the link, the last test build had a small problem.

EDIT2: While you're at it, also provide me with some more info... what did you use to format these SD cards, and how did you format them? Is there an EmuNAND on these SD cards? Are there any other known problems with these cards (you could, f.e. run Windows chkdsk over them).

EDIT3: Also, you don't see anything of the menu, right? It freezes rigth after initialization: success?


Seconding @Xenosaiga here - the slot0x05keyY.bin file is already no more required. KeyX 0x25 / 0x18 / 0x1B are only required for NCCH decryption. NCCHs might also need the seeddb.bin, which will never be complete. So, including those keys doesn't really make sense.

Was able to fix by reformatting and copying all sd card data back over.

 

[runetoonxx2]

Was able to fix by reformatting and copying all sd card data back over.

OK I'll do the same when I get home then

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

But 70 gigs of games gunna be hell

 

[Xenosaiga]

OK I'll do the same when I get home then

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

But 70 gigs of games gunna be hell

Just do like I said. Format it with Emunand9.

 

[d0k3]

OK I'll do the same when I get home then

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

But 70 gigs of games gunna be hell

The E9 format will most likely work, and you may actually have advantages in boot times from it. Still, I'd rather know what's going wrong here. At the moment I'm clueless. I think the only way for me to find out would be if I had a full image of your SD. 128GB of data, including some private data, which I sure as hell won't ask you to upload or even want to download myself.

I'm keeping an eye on this issue, though, maybe something will come up later.

 

[Xenosaiga]

The E9 format will most likely work, and you may actually have advantages in boot times from it. Still, I'd rather know what's going wrong here. At the moment I'm clueless. I think the only way for me to find out would be if I had a full image of your SD. 128GB of data, including some private data, which I sure as hell won't ask you to upload or even want to download myself.

I'm keeping an eye on this issue, though, maybe something will come up later.

I've suggested the E9 format several times now. Keep getting ignored by them though so who knows?

 

[d0k3]

OK I'll do the same when I get home then

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

But 70 gigs of games gunna be hell

One thing that I ask of you, if you haven't already reformatted... try this test build of D9 first:
https://up1.ca/#886wAfGtNQoriNaKdtGS_A

Hold L+R when initializing and tell me what the last few lines before the crash say (or, provide me with the Decrypt9.log).

 

[pbanj]

Formatted using easeus portion manager
64kb clutter size no emunand sysnand very 10.7 USA 3ds

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


It freezes after initialization success
Sandisk SD and I made sure my SD wasn't fake as well with h2testw

Try this http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm

I had issues with easeus formatted cards and 3ds

 

[runetoonxx2]

One thing that I ask of you, if you haven't already reformatted... try this test build of D9 first:
https://up1.ca/#886wAfGtNQoriNaKdtGS_A

Hold L+R when initializing and tell me what the last few lines before the crash say (or, provide me with the Decrypt9.log).

One thing that I ask of you, if you haven't already reformatted... try this test build of D9 first:
https://up1.ca/#886wAfGtNQoriNaKdtGS_A

Hold L+R when initializing and tell me what the last few lines before the crash say (or, provide me with the Decrypt9.log).

Kk I'll try tmrw can't ATM was busy today

 

[Burnout600]

One thing that I ask of you, if you haven't already reformatted... try this test build of D9 first:
https://up1.ca/#886wAfGtNQoriNaKdtGS_A

Hold L+R when initializing and tell me what the last few lines before the crash say (or, provide me with the Decrypt9.log).

I'm also having the issue with it freezing after Initialization: success! on a 128GB SD. I figured I would try this test build of D9 before backing up my SD and reformatting with E9 format. No emunand, SD was formatted using GuiFormat. The last build I was using of D9 dated back in March worked fine with A9LH / Luma3DS. Holding L+R while initializing, the last few lines are this

Finalizing Initialization...
SD card: 28493MB / 121912MB

Initialization: success!
(A to continue)

Then it locks up, doesn't do anything even after pressing buttons. The Decrypt9.log file is completely empty, so there's nothing to provide from there.

-Edit-

SD backed up, formatted with E9. E9 said that there was an unknown or corrupt filesystem and it was formatted for Emunand. Of course, I removed Emunand when I went to A9LH. Formatted through E9, went to format a second time to see what it said, and there was no corrupted message and said it wasn't currently setup for Emunand. Now restoring SD backup, which is going to take some time and I'll check to see how D9 reacts now.

So yeah, definitely seems like there's something that newer builds of D9 really doesn't like about how other programs format SD cards. I originally formatted through Panasonic SD formatter to remove Emunand when I first setup A9LH weeks ago (as I read someone saying to use Panasonic SD formatter with the size adjust option to remove emunand completely) then used GuiFormatter to format to Fat32.

Just to note, there was no other issue with the SD card. Windows didn't return any errors, all games and 3DS software ran fine. Boot time was about 13 seconds, but I've read that is normal on 128GB microsd cards.

 

[d0k3]

I'm also having the issue with it freezing after Initialization: success! on a 128GB SD. I figured I would try this test build of D9 before backing up my SD and reformatting with E9 format. No emunand, SD was formatted using GuiFormat. The last build I was using of D9 dated back in March worked fine with A9LH / Luma3DS. Holding L+R while initializing, the last few lines are this

Finalizing Initialization...
SD card: 28493MB / 121912MB

Initialization: success!
(A to continue)

Then it locks up, doesn't do anything even after pressing buttons. The Decrypt9.log file is completely empty, so there's nothing to provide from there.

-Edit-

SD backed up, formatted with E9. E9 said that there was an unknown or corrupt filesystem and it was formatted for Emunand. Of course, I removed Emunand when I went to A9LH. Formatted through E9, went to format a second time to see what it said, and there was no corrupted message and said it wasn't currently setup for Emunand. Now restoring SD backup, which is going to take some time and I'll check to see how D9 reacts now.

So yeah, definitely seems like there's something that newer builds of D9 really doesn't like about how other programs format SD cards. I originally formatted through Panasonic SD formatter to remove Emunand when I first setup A9LH weeks ago (as I read someone saying to use Panasonic SD formatter with the size adjust option to remove emunand completely) then used GuiFormatter to format to Fat32.

Just to note, there was no other issue with the SD card. Windows didn't return any errors, all games and 3DS software ran fine. Boot time was about 13 seconds, but I've read that is normal on 128GB microsd cards.

Alright, thanks for the detailed explanation! Does it work now?

@runetoonxx2 if you haven't already tried it, here's another test build that may or may not fix this issue:
https://up1.ca/#cHtvvfL54IfqX7Es0Jp0BA

 

[Burnout600]

Alright, thanks for the detailed explanation! Does it work now?

Working fine now! Starts right up, no problem at all once I formatted with E9.

 

[RacsoSakuraba]

@d0k3 you can create a glossary for "validate nand dump" in the first post? for different cases (with or without A9LH)

 

[d0k3]

@d0k3 you can create a glossary for "validate nand dump" in the first post? for different cases (with or without A9LH)

A glossary? If you have A9LH installed, there is a note about it. If the dump validator fails, it is not safe to restore (also: not possible with the standard restore). If it succeeds, there are at least no detectable problems (meaning: problems are very improbable).

 

[runetoonxx2]

Alright, thanks for the detailed explanation! Does it work now?

@runetoonxx2 if you haven't already tried it, here's another test build that may or may not fix this issue:
https://up1.ca/#cHtvvfL54IfqX7Es0Jp0BA

To my surprise the decrypt9 log was empty 0-0
still freezes at initialization success

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

will format using emunand9 now ty for the help either way guys

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

rip have to copy 62.7 gigs of stuff :l i cri everyteim