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

  • Thread starter Thread starter d0k3
  • Start date Start date
  • Views Views 935,357
  • Replies Replies 4,476
  • Likes Likes 71
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

It should work fine once you format using E9 and copy everything back, it did for me.
 
Emunand9 also said there was an emunand on my SD and that I had corrupt filesystem 0-0
Basically me and burnout same problem

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

Emunand9 format fixed it though
 
  • Like
Reactions: d0k3
Now for something completely different... Alternative D9 logos:
d9logo_alt0.png d9logo_alt1.png d9logo_alt2.png d9logo_alt3.png d9logo_alt4.png

Somebody had to do it! :) To use, just rename the .bin of your choice to d9logo.bin, and place it into either the SD card root or /Decrypt9/ (replace your d9logo.bin, if existing).
 

Attachments

Last edited by Asia81,
So the 3 key files are still needed for this to work?
Define 'work'. Depending on the entrypoint you are running this from, you need certain keyfiles to decrypt certain NCCHs (which are inside of .3DS and .CIA and .APP files). On A9LH + a recent FW version, you need only one. Everything else is explained in the readme.
 
Useless question, just for curiosity:
What about encrypt a .3ds and then play it on Sky3DS+ ?

Same thing, will not work?
If you encrypt it in the exact same way it was encrypted before. Otherwise the signature will not match. The signature is the reason why you can't play everything on Sky3DS. WIth newer CFWs things may have changed, though
 
  • Like
Reactions: hobbledehoy899
Define 'work'. Depending on the entrypoint you are running this from, you need certain keyfiles to decrypt certain NCCHs (which are inside of .3DS and .CIA and .APP files). On A9LH + a recent FW version, you need only one. Everything else is explained in the readme.
Which file do i need for just a9lh? Because when you boot as a payload it says file missing if you dont have it right?
 
  • Like
Reactions: hobbledehoy899
@d0k3
Re-tested Decrypt9 entrypoints on 4.4.0-4J.
CakeHax MSET - OK
CakeHax Browser - NG
GW Browser - OK

(I'll also post this issue to CakeHax)

So is this a reason to keep GW entrypoint for frankenfirmwares which have -4 Browser (v1024)?
 
Last edited by MelonGx,
Is there any chance we could get an in-app import.db modification to prevent System Update nags? I recall you saying something about leaving it out a year ago, but I wonder if A9LH has changed your mind on the topic?

(In any case, I tried using it on an 11.0U N3DSXL and importfix.exe failed to modify the decrypted/extracted import.db (directly from D9) properly. Is this related to the various changes Nintendo made in the latest firm update?)
 
@d0k3
Re-tested Decrypt9 entrypoints on 4.4.0-4J.
CakeHax MSET - OK
CakeHax Browser - NG
GW Browser - OK

(I'll also post this issue to CakeHax)

So is this a reason to keep GW entrypoint for frankenfirmwares which have -4 Browser (v1024)?
Alright, the Launcher.dat will be included in the next release archive. It is still deprecated, meaning that some stuff (nothing critical or dangerous) will not work.

Is there any chance we could get an in-app import.db modification to prevent System Update nags? I recall you saying something about leaving it out a year ago, but I wonder if A9LH has changed your mind on the topic?

(In any case, I tried using it on an 11.0U N3DSXL and importfix.exe failed to modify the decrypted/extracted import.db (directly from D9) properly. Is this related to the various changes Nintendo made in the latest firm update?)
Not possible. As you see, no one has the import.db format actually fully figured out. The importfix.exe working is somewhat based on luck. Also, this modification is not a cleanup but rather it just suppresses the nag.

You could ask CFW devs to write protect the import.db (for EmuNAND?). This might also break game updates, though. Also, if you read up on that thread, there is a (not tested enough) way to prevent updates being downloaded in the first place.
 
@d0k3

When building Decrypt9 with 'make release' you get the version also for the hombrew launcher.
When launching the hombrew aluncher under latest Cakes and run Decrypt9WIP, it doesn't work:
- Top black screen/bottom red screen, followed by 2x black screen, followed by Top black screen/bottom red screen and then it returns to the hombrew launcher.

Ow and to let you know, it's the same for EmuNand9/GodMode9/OTPHelper
CTRXplorer works fine :)
 
@d0k3

When building Decrypt9 with 'make release' you get the version also for the hombrew launcher.
When launching the hombrew aluncher under latest Cakes and run Decrypt9WIP, it doesn't work:
- Top black screen/bottom red screen, followed by 2x black screen, followed by Top black screen/bottom red screen and then it returns to the hombrew launcher.

Ow and to let you know, it's the same for EmuNand9/GodMode9/OTPHelper
CTRXplorer works fine :)
System version needs to be <= 9.2 for this to work and you need to use the firm90.bin in Cakes. Does that solve it?
 
Hi, I can't make D9 launching.

With an o3ds, sysnand 9.2 / RxTools 11.0, I'm trying to get a9lh, following plailect guide.
Part 4, it says
  1. Copy the Decrypt9WIP folder from the Decrypt9 zip to the /3ds/ folder on your SD card
I did it, that's on my SD, in the 3DS folder. Then I go to my SysNand - Homebrew Launcher when said, and it keep like crashing when I try to start D9, returning into Homebrew Channel after 2 red screens. (tried like 50 times...)

I saw, in the Decrypt9 zip, a scripts folder and some other files, first I didn't copy them since I follow carefully the guide, but maybe that's the issue ? Am I suppose to put them somewhere on my SD card ?
Or maybe the issue is somewhere else ?

Thanks;
 
First some context:
I made a romhack of Pokemon Omega Ruby and before installing the cia I figured I would test it in Citra since installing the cia takes quite a lot of time, even on new3DS.

Reading through citra's guide I noticed the majority of getting the .cci from a .3ds is nigh similar to getting a .cia with Simple 3DS to CIA converter, the only difference being that Archshift's xorer also requires a romfs xorpad along with the exefs and exheader.

For the world of me I cannot figure out how I am to get the romfs xorpad. The way it is explained on Citra's website it should be right there along with the exefs and exheader xorpads when doing a NCCHPadgen with the NCCHInfo generated by ncchinfo_gen.py.

TLDR: Want to test a freshly (with 3ds builder) made .3ds in Citra before converting to and installing cia on 3DS but lacking the romfs xorpad to decrypt it.

So for my question:
Is the romfs xorpad generating a feature taken out of Decrypt9WIP and something I would have to use Archshift's Decrypt9 for it or am I missing something in the process?




p.s. a9lh new3ds 11.0 updated sysnand

p.p.s. I know Citra's website says it is not yet compatible with Pokemon but last I heard it is with the hardware render but even if it's not consider that irrelevant to the question and consider OR as just a "context example"
 
Last edited by Favna,

Site & Scene News

Popular threads in this forum