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

[d0k3]

Just got finished doing my homework, @d0k3

In all cases I've been using the 3dsx entrypoint through Homebrew Launcher through Menuhax. (also tried through Browserhax a couple of times)

N3DS with, naturally, SysNAND 9.2u, Emunand 10.6 (though it happens as well with EmuNAND 9.2). If reading the SysNAND and writing it to the EmuNAND partition is a problem though I don't see how it could be copied successfully to a fresh EmuNAND in the first place, though.. Making dumps of the NANDs fails at 7-~15%, and injecting a NAND dump .bin into EmuNAND fails at 14-22%. On both Decrypt9 and EmuNAND9. (only on the 32gb card, even with the same dumps.)

My SysNAND dump fails as well, at the same point using EmuNAND9 and the 32gb SD card.

Copying the same NAND.bin using GodMode9 failed. (From Root of 32gb SD to a folder within the same partition)(was I supposed to copy it directly from my NAND?). The resulting file was 0 bytes (to windows anyhow), though from rough estimation the progress bar showed about the same as I can expect with the other apps. The SD card is, once again, unmounted after the fail, so obviously that's what's causing the failure.

And, much to my dismay. The Decrypt9 work folder trick does not work either. Dumping SysNAND to it stopped at 20%. The file was 395mb. I tried to dump EmuNAND twice. The first failure was almost instant and stopped at 4mb. The second went to 10% and stopped at 202mb. The points at which it unmounts seem totally arbitrary.

To summarize:
Writing SysNAND to EmuNAND using EmuNAND9 initial setup works fine.
Dumping SysNAND or EmuNAND regardless of app fails at arbitrary points anywhere from (4mb?!)170mb to 395mb.
Entrypoint is 3dsx in all cases.
N3ds XL with 9.2u SysNAND, 10.6 EmuNAND, and 9.2 EmuNAND.
Earlier versions were not tested.
Godmode9 fails as well, by visual estimation, at the same percentages.

Edit:
I'm going to try filling the SD card up with a bunch of files to approximately 50% capacity and try this again.
Edit 2:
After loading up the card with a bunch of files (over 50% capacity) the dumps still fail within the same frame. (215mb EmuNAND dump and a 121mb SysNAND dump)
GodMode9 failed very quickly when attempting to copy any large files (tested with a complete dump and a 2gb mkv file) after loading the card up.
Dumps will also occasionally fail nearly instantly but if they don't they reach the lower end of the average size stated above. (9-13%) So there's some part of my SD card (or rather, the partition?) that either these apps or my n3ds do not like.

important note: cloning SysNAND to EmuNAND still works fine even after filling the SD card up.

So if it is really a failed card, why haven't any of the intensive tests shown it? Why doesn't windows have the same write errors?

I'd hate to think that the problem could be my 3ds's hardware.. (brand new as of 3 days ago..)

p.s. sorry for the massive posts all the time

Exact model of card:
Sony SR-32UY2A

No worries about the massive post, it is good to get some insight about this. We can try to update the FATFS library (this handles all file io), maybe that helps. Will have a testing version for you within an hour or two. Some background info: When you're cloning your SysNAND directly to EmuNAND, you write to the SD at the low, hardware level, without any other libraries involved. If that works, we have reason to believe that my FAT32 routines or somehow at fault.

Hi d0k3,

Thanks for answering.
No, i'm not using multiple emunands. In the attach is the info when injecting the app.

Regards

Alright. I see this is a O3DS, but what region and what FW version is it? Also, is there a chance you have downgraded this system to 4.x with GW in the past?

 

[bakterio]

No worries about the massive post, it is good to get some insight about this. We can try to update the FATFS library (this handles all file io), maybe that helps. Will have a testing version for you within an hour or two. Some background info: When you're cloning your SysNAND directly to EmuNAND, you write to the SD at the low, hardware level, without any other libraries involved. If that works, we have reason to believe that my FAT32 routines or somehow at fault.


Alright. I see this is a O3DS, but what region and what FW version is it? Also, is there a chance you have downgraded this system to 4.x with GW in the past?

Hi,

Yes, i downgraded it from 7.x to 4.5 and now i'm un 9.2. It's EUR región.

Regards.

 

[d0k3]

Hi,

Yes, i downgraded it from 7.x to 4.5 and now i'm un 9.2. It's EUR región.

Regards.

Okay, I can tell you what happened here...
The GW downgrade left your system a mess, leaving multiple versions of app files lying around. Normally, D9 handles this pretty well and is still able to find the correct one to inject to, not in your case, though. There is a fix for that, but that involves dumping your CTRNAND partition, editing it and writing it back, possibly multiple times. If you want to do it, I can give you instructions, let me know. There may also be a quicker way.

 

[bakterio]

Okay, I can tell you what happened here...
The GW downgrade left your system a mess, leaving multiple versions of app files lying around. Normally, D9 handles this pretty well and is still able to find the correct one to inject to, not in your case, though. There is a fix for that, but that involves dumping your CTRNAND partition, editing it and writing it back, possibly multiple times. If you want to do it, I can give you instructions, let me know. There may also be a quicker way.

You're talking about doing it to the emunand or the sysnand? Could have upgradring to 9.2 solved the problem, so that if i make a new emunand it won't have the issue?

 

[d0k3]

You're talking about doing it to the emunand or the sysnand? Could have upgradring to 9.2 solved the problem, so that if i make a new emunand it won't have the issue?

No, you downgraded via GW in the past, unless you have a backup from before, that issue will never go way. And I'm talking about doing it on EmuNAND.

 

[bakterio]

No, you downgraded via GW in the past, unless you have a backup from before, that issue will never go way. And I'm talking about doing it on EmuNAND.

Ok. I have my 7.x nand backup. Can i inject it directly un emunand with the otphelper to start with a clean emunand? All this was to downgrade to 2.1 so i suppose it will be riskier to do it with my current emunand even if somehow the hs injection had worked by chance.

 

[d0k3]

@Spoober: You can try this build and see if it makes a difference. This has updated low level routines:
http://workupload.com/file/i1w5hv6R
And yes, your hardware beeing at fault is one possibility, although the SysNAND -> EmuNAND clone fully working makes this look like it is not.

@bakterio:
I'll give you an explanation on what to do. In the meantime, make a backup of your EmuNAND and keep it in a safe place.

 

[d0k3]

Okay, @bakterio, here is what you do:

Grab my alpha build of GodMode9 from here:
http://workupload.com/file/lqZrdozu
(Don't write anything to or delete anything from your SysNAND!)

Enter this folder in EmuNAND CTRNAND (4:
4:/title/00040010/00022300

In this folder, delete the first .tmd file you find. Now reboot to your EmuNAND. Does H&S still work? If not, restore your EmuNAND backup and try again with the second, then with the third and so on. In the end, you should have deleted all tmds that have no effect on the system, meaning only one tmd will stay.

After you have done this, inject H&S -> working!

 

[Zeriel]

@d0k3
Hello I have Homebrew Launcher but it's on Emunand, I'm trying to find an access point on Sysnand but
when you say build this with brahna what does that mean? Is there any tutorial I could follow?

I'm on new 3DS 9.2 sysnand and Reinand 9.5

 

[d0k3]

@d0k3
Hello I have Homebrew Launcher but it's on Emunand, I'm trying to find an access point on Sysnand but
when you say build this with brahna what does that mean? Is there any tutorial I could follow?

I'm on new 3DS 9.2 sysnand and Reinand 9.5

Use the 3DSX and start it from SysNAND.

 

[Zeriel]

Use the 3DSX and start it from SysNAND.

But how do I run the 3dsx from Sysnand? I have Homebrew tools but it's on Emunand, I have no
launchers on Sysnand and that's what I'm trying to figure out. Also I'm scared of installing anything
into Sysnand, what's the safest thing to do in this case?

 

[d0k3]

But how do I run the 3dsx from Sysnand? I have Homebrew tools but it's on Emunand, I have no
launchers on Sysnand and that's what I'm trying to figure out. Also I'm scared of installing anything
into Sysnand, what's the safest thing to do in this case?

Read the readme and check if another entrypoint works for you. You may also get Ninjhax installed on SysNAND.

 

[bakterio]

Okay, @bakterio, here is what you do:

Grab my alpha build of GodMode9 from here:
http://workupload.com/file/lqZrdozu
(Don't write anything to or delete anything from your SysNAND!)

Enter this folder in EmuNAND CTRNAND (4:
4:/title/00040010/00022300

In this folder, delete the first .tmd file you find. Now reboot to your EmuNAND. Does H&S still work? If not, restore your EmuNAND backup and try again with the second, then with the third and so on. In the end, you should have deleted all tmds that have no effect on the system, meaning only one tmd will stay.

After you have done this, inject H&S -> working!

Ok. I'll try this weekend and let you know.

Thanks and regards.

 

[Ekaitz]

I did not have time to try it yet so I'm asking, do the keys have to be in the root directory or we can use a subfolder such as /Decrypt9 ?

 

[Zeriel]

It would have been nice to actually have some instructions, maybe this thread wouldn't be 140 pages long

 

[Shadowtrance]

It would have been nice to actually have some instructions, maybe this thread wouldn't be 140 pages long

It would be nice to not have to spoon feed everyone all the time too with this stuff but you don't see me bitching... oh wait, i am now.

A little investigation and reading of your own won't hurt you y'know...

 

[pbanj]

It would be nice to not have to spoon feed everyone all the time too with this stuff but you don't see me bitching... oh wait, i am now.

A little investigation and reading of your own won't hurt you y'know...

But people don't read. Hell the info could be in the first post and they would still ask how to use it. People here don't like to read the first post so they are deff not going to look through a thread.

 

[Shadowtrance]

But people don't read. Hell the info could be in the first post and they would still ask how to use it. People here don't like to read the first post so they are deff not going to look through a thread.

Well that's their problem then isn't it?
Not to hard to glance at the fist post and click the link to github where there's a giant README that answers probably most of the damn questions asked here...

 

[d0k3]

I did not have time to try it yet so I'm asking, do the keys have to be in the root directory or we can use a subfolder such as /Decrypt9 ?

It would have been nice to actually have some instructions, maybe this thread wouldn't be 140 pages long

We actually have a pretty good readme, which isn't even that long. Specific information about the key files is still missing from it, but if you would have read the part about work folders, you would know as well. I'll add info about those keyfiles, but once that is in, I expect from everyone to do their homework for themselves.

Just for now: you can use both, root and work folder.

 

[pbanj]

Well that's their problem then isn't it?[emoji14]Not to hard to glance at the fist post and click the link to github where there's a giant README that answers probably most of the damn questions asked here...

I think a big part of the issue is people get the dl from a guide that doesn't link them to the github