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

[Shadowtrance]

I put all my slot***Key*.bin files inside a folder named Decrypt9. Should they be in the root?

It can be either. SD root or Decrypt9 folder. Personal choice.

 

[pbanj]

I put all my slot***Key*.bin files inside a folder named Decrypt9. Should they be in the root?

That's how I have mine and it works just fine

 

[d0k3]

I put all my slot***Key*.bin files inside a folder named Decrypt9. Should they be in the root?

Not sure myself, so I just put it on root.

Both is okay.

Couldn't you encrypt and hardcode them in like ReiNand did with the 9.6 keys

I'll think about it. I don't know if that is really a legit workaround.

 

[Serphirot]

I was using that before for that sole purpose, but AuReinand has a new feature added to let you boot a payload bypassing the cfw launch, it's pretty nice and makes things simple but seems I'll need to make a custom build of Decrypt9 to take advantage of it >.< thanks to me being set on a no-screen-init a9lh

You can load bootctr with AuReinand and then load d9 or all the other stuff that can be loaded with a9lh. It is just a bit tricky to use the button you want if you have something on other buttons than r or l because if you aren´t fast enough he will load what is on that or the dafault way if you don´t have anything on l or r if you hold them to long.

 

[Sniffynose]

You can load bootctr with AuReinand and then load d9 or all the other stuff that can be loaded with a9lh. It is just a bit tricky to use the button you want if you have something on other buttons than r or l because if you aren´t fast enough he will load what is on that or the dafault way if you don´t have anything on l or r if you hold them to long.

That's true, as long as Decrypt9 is set as the default under the boot config file it would load without a problem. This also initializes the screen so any build could be used easily.

 

[Spoober]

Using the latest release, I'm still getting "file too small." Kind of at my wits end here, would really appreciate a helping hand. It's a fresh (and full sized..) backup of an Emunand just after a system transfer. Without fail, every time, at 17-19% it says the file is too small, which obviously cannot be.

edit:
Backup was made using Emunand9 and is the correct size down to the byte.

The percent also ranges from 17~19, perhaps more. I am still trying.

 

[d0k3]

Using the latest release, I'm still getting "file too small." Kind of at my wits end here, would really appreciate a helping hand. It's a fresh (and full sized..) backup of an Emunand just after a system transfer. Without fail, every time, at 19% it says the file is too small, which obviously cannot be.

edit:
Backup was made using Emunand9 and is the correct size down to the byte.

You mean it loads up to 19%, then says file too small? Could you check your SD card integrity? Maybe using something like Windows chkdsk (from command line, on your SD card drive, "chkdsk /f /x").

EDIT, and you get the "Restoring ???NAND. Size (MB): ???" message first, right?

 

[Spoober]

You mean it loads up to 19%, then says file too small? Could you check your SD card integrity? Maybe using something like Windows chkdsk (from command line, on your SD card drive, "chkdsk /f /x").

EDIT, and you get the "Restoring ???NAND. Size (MB): ???" message first, right?

Yes, it says

"Restoring EmuNAND. Size (MB): 1888" (this time it got to 21%...)

Here is my chkdsk results.

Spoiler

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

chkdsk f: /f /x
The type of the file system is FAT32.
Volume EMUNAND9SD created 2/1/2015 12:00 AM
Volume Serial Number is 4641-0000
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.
28,434,432 KB total disk space.
2,016 KB in 63 folders.
2,259,232 KB in 452 files.
26,173,152 KB are available.

32,768 bytes in each allocation unit.
888,576 total allocation units on disk.
817,911 allocation units available on disk.

 

[JuanmaHL]

Only need to copy Decrypt9.bin (rename it) on the sd and i can do backups and restore or i need to copy other files, What versión i need to have to do backups and restore (i have a9lh 10.6 NATIVE 9.0)

 

[d0k3]

Yes, it says

"Restoring EmuNAND. Size (MB): 1888" (this time it got to 21%...)

Here is my chkdsk results.

Spoiler

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

chkdsk f: /f /x
The type of the file system is FAT32.
Volume EMUNAND9SD created 2/1/2015 12:00 AM
Volume Serial Number is 4641-0000
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.
28,434,432 KB total disk space.
2,016 KB in 63 folders.
2,259,232 KB in 452 files.
26,173,152 KB are available.

32,768 bytes in each allocation unit.
888,576 total allocation units on disk.
817,911 allocation units available on disk.

There is something on your SD card that causes it to fail midway. It's not the data that is wrong (D9WIP has quite a few safety clamps in place). We can try something, though, I'll need a minute or two... Will be right back.

 

[Spoober]

There is something on your SD card that causes it to fail midway. It's not the data that is wrong (D9WIP has quite a few safety clamps in place). We can try something, though, I'll need a minute or two... Will be right back.

Oh that is interesting, Also, I discovered this though I have no idea if it could be helpful.

if I go back into Emunand Restore menu after that I see something weird, or not I dont know but, it displays this:

Use arrow keys and <A> to choose EmuNAND
EmuNAND #0: EmuNAND ready

After that if I press A it says it fails to retrieve the file names list and I need to unmount/remount the SD card to avoid seeing it again.

Thanks for looking into it for me.

 

[d0k3]

Oh that is interesting, Also, I discovered this though I have no idea if it could be helpful.

if I go back into Emunand Restore menu after that I see something weird, or not I dont know but, it displays this:



After that if I press A it says it fails to retrieve the file names list and I need to unmount/remount the SD card to avoid seeing it again.

Thanks for looking into it for me.

Reporting back... looking into this will take me a little bit longer. For some unknown reason, your SD card seems be unmounted mid process, and the reasons for that can be a lot. The most probable one is a defective SD card (chkdsk doesn't do a full surface test), but that's not the only possible cause. Will come back about this, alright?

EDIT: Adding to this... What you can do now is check your SD card more thoroughly. Know of any tools to check this? Also, maybe try it with another SD card, just to make sure it is not your console that is at fault.

 

[Spoober]

Reporting back... looking into this will take me a little bit longer. For some unknown reason, you're SD card seems be unmounted mid process, and the reasons for that can be a lot. The most probable one is a defective SD card (chkdsk doesn't do a full surface test), but that's npt the only possible cause. Will come back about this, alright?

A defective SD would be a strange thing as I was using it flawlessly with an o3ds, but understood and appreciated. I'll put it to the side for now as I've been banging my head against it for probably 10 hours now.

For the record this is a reputable brand (Sony) purchased at a big name retail outlet and not from a shady online dealer. I performed a surface scan to verify the SD card is not (immediately) faulty, result here.

Spoiler

Thanks again and, whatever it is should be interesting.



EDIT:

I'm in the process of experimenting with my SD card(s). I formatted a 16 gig on my computer, and then partitioned it using EmuNAND9 (launched from my 32 gig), and then did the same with Decrypt9. The SD card was empty but the partition folder and the emunand backup. it successfully restored the backup. I am now going to test the same procedure but with the 32gig card. (Empty/fresh card with no other files than the NAND.bin)

EDIT 2:

AAaaannd... It failed at the same point. That is bizarre. And unfortunate. If the SD card has no errors on a surface scan? What could the problem be? If it is just a fault card, I apologize for wasting your time, but..

 

[Sev501]

quick question, those slot key files are like the ones used by rxtools ? and they're the ones you can make from some google spreadsheet?

Edit: NVM. Just did the backread and yeah answered my questions.
Will be compiling again! Thanks for all the hardwork guys!

P.s.
Is the main git the same deal for a9lh?

 

[The Crane Game]

Just to be clear, if I've backed up my original SysNAND with EmuNAND9 before creating EmuNAND and using TinyFormat, I can restore that NAND with Decrypt9 right? And then redo the EmuNAND and use TinyFormat to wipe the SysNAND once again?
Using this guide, hopefully that makes sense. I accidentally skipped a step and used TinyFormat before and now I'm concerned about losing my save data for games like Animal Crossing (plus having to redownload about 18 GB of games on the eShop would suck.)

 

[pbanj]

Just to be clear, if I've backed up my original SysNAND with EmuNAND9 before creating EmuNAND and using TinyFormat, I can restore that NAND with Decrypt9 right? And then redo the EmuNAND and use TinyFormat to wipe the SysNAND once again?
Using this guide, hopefully that makes sense. I accidentally skipped a step and used TinyFormat before and now I'm concerned about losing my save data for games like Animal Crossing (plus having to redownload about 18 GB of games on the eShop would suck.)

if your system nand/backup still contains all the stuff you want your emunand to have yes that will work

 

[The Crane Game]

if your system nand/backup still contains all the stuff you want your emunand to have yes that will work

Solid! So I can just restore the backup, then rerun EmuNAND9 as instructed in that tutorial, then TinyFormat, etc. etc. and all will be kosher?

 

[pbanj]

should be yes. as long as the nand u are using to create the emunand has the games/saves you want they will transfer over. just make sure you back up your nintendo 3ds folder before hand as creating the eminand will format the card. once that folders gone if you dont have a back up your stuff is gone forever.

 

[The Crane Game]

should be yes. as long as the nand u are using to create the emunand has the games/saves you want they will transfer over. just make sure you back up your nintendo 3ds folder before hand as creating the eminand will format the card. once that folders gone if you dont have a back up your stuff is gone forever.

Sounds pretty foolproof! I've still got everything backed up from yesterday and haven't gotten to make changes so that's what I'll do. Thanks again!

EDIT: One last question, I'm sure it's obvious but do I need to go through Homebrew Launcher on SysNAND to do the restore and delete Menuhax all over again? Or can I keep that setup.

 

[d0k3]

A defective SD would be a strange thing as I was using it flawlessly with an o3ds, but understood and appreciated. I'll put it to the side for now as I've been banging my head against it for probably 10 hours now.

For the record this is a reputable brand (Sony) purchased at a big name retail outlet and not from a shady online dealer. I performed a surface scan to verify the SD card is not (immediately) faulty, result here.

Spoiler

Thanks again and, whatever it is should be interesting.



EDIT:

I'm in the process of experimenting with my SD card(s). I formatted a 16 gig on my computer, and then partitioned it using EmuNAND9 (launched from my 32 gig), and then did the same with Decrypt9. The SD card was empty but the partition folder and the emunand backup. it successfully restored the backup. I am now going to test the same procedure but with the 32gig card. (Empty/fresh card with no other files than the NAND.bin)

EDIT 2:

AAaaannd... It failed at the same point. That is bizarre. And unfortunate. If the SD card has no errors on a surface scan? What could the problem be? If it is just a fault card, I apologize for wasting your time, but..

Just writing to let you know I've seen your edits. Well, I see you know how to test and verify this, and this stays a very bizarre error. Even if the SD card had (undetected) surface errors, it would be rather improbable the file would be on the same physical space again. And, this working with a 16GB format only serves to makes this even more strange. I have an idea what you could try though. Check what cluster size the FAT formating of this 32GB SD card uses, and format it with a different cluster size. Then see if it keeps on happening and tell me.

In any way, thanks for this information!