Homebrew Official [Release] EmuNAND9 - Open Source EmuNAND Formatter & Manager

[dark_samus3]

@d0k3 have you seen this? http://hackinformer.com/2016/01/05/3ds-emunand9tool-open-source-sd-manager-releases/

found it while browsing google images for 3ds NAND mods haha

 

[Drak0rex]

Ok, so regarding the H&S app injection, can I inject an app into it and someone else install it onto their emunand, or is it tied to the system? I know they are different between old and new 3DS, but between the same model, are they interchangeable?

 

[dark_samus3]

Ok, so regarding the H&S app injection, can I inject an app into it and someone else install it onto their emunand, or is it tied to the system? I know they are different between old and new 3DS, but between the same model, are they interchangeable?

they are interchangeable between systems as long as the region and version of the application matches

 

[Deathscreton]

My friends copy of this program keeps crashing. He's used both Menuhax and Browserhax to boot it, and it crashes either way. Any idea why it'd do this?

(He just downgraded to 9.2).

 

[dark_samus3]

My friends copy of this program keeps crashing. He's used both Menuhax and Browserhax to boot it, and it crashes either way. Any idea why it'd do this?

(He just downgraded to 9.2).

He probably got an incomplete downgrade

 

[Deathscreton]

He probably got an incomplete downgrade

How do we go about fixing that? Using sysupdater again and reinstalling the same CIAs?

 

[dark_samus3]

How do we go about fixing that? Using sysupdater again and reinstalling the same CIAs?

Yep, you may also want to clear the update nag (google on how to do that)

 

[Deathscreton]

Alright. I'll get him to attempt that. Thanks.

 

[4ur0r]

Hi, I've (hopefully) successfully downgrade my N3DS to 9.2 but when I go to EmuNAND9 Manager Options > Dump SysNAND to NAND.bin after a while it sayd "Dumping SysNAND (1240MB) to file...", and then "Creating NAND.bin..." and then "COuld not create NAND.bin!". Obiviously dumping sysNAND to NAND.bin has failed, and can't understand why. I'm using a 32gb samsung class 10 micro sd. Tried many times, but the results are the same and I would like to have a dump of my NAND in case I brick bad.

 

[Shadowtrance]

Hi, I've (hopefully) successfully downgrade my N3DS to 9.2 but when I go to EmuNAND9 Manager Options > Dump SysNAND to NAND.bin after a while it sayd "Dumping SysNAND (1240MB) to file...", and then "Creating NAND.bin..." and then "COuld not create NAND.bin!". Obiviously dumping sysNAND to NAND.bin has failed, and can't understand why. I'm using a 32gb samsung class 10 micro sd. Tried many times, but the results are the same and I would like to have a dump of my NAND in case I brick bad.

Seems you're not the only one running into this issue, try Decrypt9 nand backup and see how that goes.
https://github.com/Shadowtrance/Decrypt9/releases/tag/v2.3

 

[4ur0r]

Seems you're not the only one running into this issue, try Decrypt9 nand backup and see how that goes.
https://github.com/Shadowtrance/Decrypt9/releases/tag/v2.3

Thank you, apparently dumping the NAND with Decrypt9 has been successfull. GONNA DUMP EVERYTHING
EDIT: I used the textual version, guess it's the same?

 

[saxon48]

Many thanks for this tool. Was instrumental in getting me all setup on 9.2 with my N3DS.

Out of curiosity, is this the recommended tool for going to back to stock firmware, reverting any and all OS modifications while still keeping game data intact?

 

[d0k3]

Maybe we should have a separate version for N3DS (no intention to discriminate O3DS)? Developer should ultilise all the power of the hardware, right? It's Nintendo fault for being cheap and make a less powerful 3DS model in the first place.

I understand that. What I meant is that's would help creating an easier method that creating EMUNAND with CIA installer in 1 go for N3DS (no other app & preinstalled game inside the 3DS folder to make > 20MB (screw you, auto correction)) . Many new Tempers just keep forget to back up the Nintendo 3DS folder after installing CIA installer, before creating EMUNAND.Many new Tempers just ask the same questions of how to install CIa installer on N3DS EMUNAND, which at the moment there is no other noob-friendly way is install in SYSNAND and back up NIntendo 3DS folder before creating EMUNAND (I don't trust new Tempters to Inject stuff to NAND).

As of now starter.bin, 16MB limit in EMUNAND9Tool kinda hinder because there is not enough room if I put other nesscesary homebrew apps (which helps installing RxTools CFW, menuhax, ftbony, file explorer, Hans, Pasta CFW... In a sense, 1-go RxTools CFW installation method via EMUANAND9Tool without having to connect to PC again.

A separate version is not needed, but I'll see about including a hidden way of disabling that 16MB limit. As I wrote, it would be in the users responsibility to make sure their starter pack actually works (can't test everything). Taking over the Nintendo 3DS folder, on the other hand - I don't say never, but as of now this is just too complex, and this could never be tested enough for me to say that it works reliable enough. Including a zipping tool into EmuNAND9 (to make it auto-create / add to the starter.bin) is out of question, too, cause the zipping code would result in an executable too big (in ARM9, executable memory is limited).

Many thanks for this tool. Was instrumental in getting me all setup on 9.2 with my N3DS.

Out of curiosity, is this the recommended tool for going to back to stock firmware, reverting any and all OS modifications while still keeping game data intact?

You mean setting it back in case you need to send it in for warranty? The general advice here is to keep SysNAND as untouched as possible. You can make a backup of your SysNAND, but only Decrypt9 (my signature) can write it back, and for users without a NANDmod, writing to SysNAND should be done as little as possible.

 

[d0k3]

Emunand9UI!

@d0k3 Ran into a few issues with this in regards to doing a UI version...
Pretty sure we've encountered similar issues before with D9 (i think).

Basically if i select Complete emunand setup, press B to cancel it,
1. It complains it can't find failed.bin (all images do exist)
2. It doesn't reload the menu (progress image is stuck on bottom screen, debug_bg + previous text is on top screen, if i press B again the "Emunand and SD Storage" strings show up, Work dir string doesn't. SD Storage "space" is totally messed up, for example: 17592186044415MB / 28124MB.

That's the only issues I've encountered so far as i don't have any spare sd cards to test everything fully.

I just wanted to take a look, but you haven't updated your Github yet... Can you send me your work in progress project so that I can have a look?

 

[Shadowtrance]

I just wanted to take a look, but you haven't updated your Github yet... Can you send me your work in progress project so that I can have a look?

Yeah can do.
Only difference between my repo and yours (besides small changes i've made) is you've pushed the update for ctrulib 1.0.0 and i haven't. I've manually updated my local "work" copy though.
Check your PM's.

 

[3xkrazy]

@d0k3

Hi d0k3,

I'm not sure how the Complete EmuNAND Setup option works because I haven't tried it, but I assume it clones the current SysNAND into EmuNAND, correct? Would it be possible to add an option to initiate the starter.bin under EmunNAND Manager Options, so it operates independently from Complete EmuNAND Setup?

I assume it would also make unlinking NANDs much less of a chore, as one would have to format sysNAND after EmuNAND setup.

So my ideal protocol when setting up fresh would be:
1) Run EmuNAND9
2) Format SD
3) Format EmuNAND
4) Unmount SD, and copy unlinked Sys/Emu NAND.BIN and starter.bin from PC into EMUNAND9 SD folder
5) Mount SD and clone NAND.BIN to EmuNAND
*6) Initiate starter.bin setup

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

@d0k3

Hi d0k3,

I'm not sure how the Complete EmuNAND Setup option works because I haven't tried it, but I assume it clones the current SysNAND into EmuNAND, correct? Would it be possible to add an option to initiate the starter.bin under EmunNAND Manager Options, so it operates independently from Complete EmuNAND Setup?

I assume it would also make unlinking NANDs much less of a chore, as one would have to format sysNAND after EmuNAND setup.

So my ideal protocol when setting up fresh would be:
1) Run EmuNAND9
2) Format SD
3) Format EmuNAND
4) Unmount SD, and copy unlinked Sys/Emu NAND.BIN and starter.bin from PC into EMUNAND9 SD folder
5) Mount SD and clone NAND.BIN to EmuNAND
*6) Initiate starter.bin setup

Wait..could you also please clarify what Format EmuNAND (auto) does? Does it initiate the starter.bin after formating the EmuNAND?

 

[d0k3]

@d0k3

Hi d0k3,

I'm not sure how the Complete EmuNAND Setup option works because I haven't tried it, but I assume it clones the current SysNAND into EmuNAND, correct? Would it be possible to add an option to initiate the starter.bin under EmunNAND Manager Options, so it operates independently from Complete EmuNAND Setup?

I assume it would also make unlinking NANDs much less of a chore, as one would have to format sysNAND after EmuNAND setup.

So my ideal protocol when setting up fresh would be:
1) Run EmuNAND9
2) Format SD
3) Format EmuNAND
4) Unmount SD, and copy unlinked Sys/Emu NAND.BIN and starter.bin from PC into EMUNAND9 SD folder
5) Mount SD and clone NAND.BIN to EmuNAND
*6) Initiate starter.bin setup

Well, I don't see much reason at the moment why the starter.bin should not be copied in step 2) (which that option totally does, you just have to select the "auto" version).

... and in response to your merged post - yup that's what it does. Guess I should make that more clear.

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

Oh well, I guess i see more of a misunderstanding here... there are four options in the format sd menu... and each of them is self contained. You don't have to do a standard format before you do a EmuNAND format. Or maybe I got that wrong? What do you mean by step 3)?

 

[3xkrazy]

Well, I usually do the steps manually. I assume that format SD (step 2) destroys the current partition table and formats it to recommented standards. Format EmuNAND (step 3) rewrites the MBR, creates the EmuNAND partition, and FAT 32 partiton.

But you recommend that starter.bin should be copied to the SD at step 2?

 

[d0k3]

Well, I usually do the steps manually. I assume that format SD (step 2) destroys the current partition table and formats it to recommented standards. Format EmuNAND (step 3) rewrites the MBR, creates the EmuNAND partition, and FAT 32 partiton.

But you recommend that starter.bin should be copied to the SD at step 2?

You only need to run "Format SD (EmuNAND / auto)", that does everything (format SD for EmuNAND & set up starter.bin) in one step. I'll try to make that more clear in the next release.

 

[3xkrazy]

You only need to run "Format SD (EmuNAND / auto)", that does everything (format SD for EmuNAND & set up starter.bin) in one step. I'll try to make that more clear in the next release.

Sweet. Thank you!

 

[d0k3]

@tivu100
The attached intermediate release is for you - this does not justify a full new release yet, but it already allows the user (at his own responsibility) to skip the warning because of a too big starter.bin. RAM boundaries are still checked, so little bad can happen with this.

@Shadowtrance
Guess what? You found a bug that was also in the "vanilla" version of EmuNAND9 . Take a look at my GitHub. I also reorganized some theme stuff - I want to limit the stuff a theme designer has to change to the bare minimum and also "contain" any changes to theme.c / theme.h as much as possible. You also don't need to change anything in DrawMenu() (if that change was intentional), that function is never called in the themed version.

Also, we need another graphic. A feature cancelled by the user is not the same as a failed feature . I guess you'll see once you take a look at the last commit.

@MelonGx
Well, I looked into the EmuNAND sizes issue. Annoying as hell as I said... Anyways, I'll add a third (fifth & sixth if you count the 'auto' variants) format option, that will create a bigger / more compatible EmuNAND partition. The other two format options will stay as they are.

Now, what sizes should I choose for best compatibility? I only have one N3DS to test (~1,8GB NAND), so I can't fully decide. Should I just reserve 1GB (for O3DS) / 2GB (for N3DS). Also, will EmuNAND Tool really not work with 'small' EmuNAND partitions? Can you give me the exact error message?