Hacking [RELEASE] 3DS Multi EmuNAND Creator

[Kazuma77]

I'll look into these issues. Would you please try out a debug build? I'd like to see the debug messages.

I've got some spare microSD cards laying around I could test with. So, sure, put up a debug build. I'll see if I can get you some useful information with it.

 

[Kyrara]

i become an error if i want Inject a Second Emunand:

---------------------------
Error
---------------------------
Error writing dummy data.
---------------------------
OK
---------------------------

Anyone know what i can do?

I have test to Format the SD card again and have no problem to inject the first Emunand but the Second have all time this Error.

 

[Kazuma77]

i become an error if i want Inject a Second Emunand:

---------------------------
Error
---------------------------
Error writing dummy data.
---------------------------
OK
---------------------------

Anyone know what i can do?

I have test to Format the SD card again and have no problem to inject the first Emunand but the Second have all time this Error.

I was testing debug versions for the author but I haven't heard back from him in a while. He did send me a debug build that fixed most of the problems I was having before he disappeared. Though you may need a couple of other versions if you want maximum compatibility. Since it's been almost two weeks, I'll just post the method I'm currently using. Hope it helps.

 

[SirNapkin1334]

Is there a way to do this without this program? I'm on Mac. I tried using Wine, but it always says, "No valid drives availible." I want to create a second emunand without erasing the contents of the first.

 

[senkunmusashi]

I was testing debug versions for the author but I haven't heard back from him in a while...

I do hope that this very useful program is still being developed. I just used the version linked in the first post to prep a new sdcard and transferred emunand from my old card without a hitch, made the job so quick and easy.

 

[DarkMatterCore]

New year, new release. As always, you can find the download in the first post.

v1.72:
* The program now always forces the creation of a new, 4 MiB aligned offset for the FAT partition when injecting a new NAND. This fixes a bug where the first sector from the new FAT partition would have been overwritten with a dummy footer if the generated offset for the partition was already aligned to a 4 MiB boundary. Thanks to Kazuma77 for testing.
* If a new NAND is injected and the size of the previous NAND was greater than the size of the new NAND, the stored NAND dump will be zero padded to match the previous NAND size right after the injection process is finished.
* Now, only the format procedure defaults to the minimum NAND size possible. The rest of the NAND inject operations use the default NAND size layout to avoid problems.

 

[bendevnull]

New year, new release. As always, you can find the download in the first post.

No offense to anyone on this thread, and also, amazing work on this @DarkMatterCore (I used this a few times back when EmuNAND was almost a MUST (I had a 10.7 SysNAND, 10.7 EmuNAND, and a 9.2 EmuNAND)), but is EmuNAND even relevant anymore with Boot9strap and NTRBootHax? Even if you can't afford a card for NTRBootHax, you still have Boot9Strap which, unless you REALLY fuck something up, it's almost impossible to brick with!

 

[DarkMatterCore]

No offense to anyone on this thread, and also, amazing work on this @DarkMatterCore (I used this a few times back when EmuNAND was almost a MUST (I had a 10.7 SysNAND, 10.7 EmuNAND, and a 9.2 EmuNAND)), but is EmuNAND even relevant anymore with Boot9strap and NTRBootHax? Even if you can't afford a card for NTRBootHax, you still have Boot9Strap which, unless you REALLY fuck something up, it's almost impossible to brick with!

I'm more than aware of the fact that EmuNANDs are not really necessary anymore. It's just me wanting to "polish" the program as much as possible, or so to say. In the end, it's better to have, and don't need.

 

[bendevnull]

I'm more than aware of the fact that EmuNANDs are not really necessary anymore. It's just me wanting to "polish" the program as much as possible, or so to say. In the end, it's better to have, and don't need.

I understand wanting to polish a program. In my opinion, the program was really good when I used it, and that was YEARS ago!

 

[SirNapkin1334]

I understand wanting to polish a program. In my opinion, the program was really good when I used it, and that was YEARS ago!

EmuNand is still useful—you can region change an EmuNand but have a regular NAND. Then you can switch back and forth.

 

[senkunmusashi]

EmuNand is still useful—you can region change an EmuNand but have a regular NAND. Then you can switch back and forth.

Exactly! It's almost like having 2 consoles (or 3, or more), very useful when you have to share one device and everyone can have their own settings and games.

In the end, it's better to have, and don't need.

No truer words hath been spoken. Thank you for making and maintaining this great app.

 

[Cuphat]

No offense to anyone on this thread, and also, amazing work on this @DarkMatterCore (I used this a few times back when EmuNAND was almost a MUST (I had a 10.7 SysNAND, 10.7 EmuNAND, and a 9.2 EmuNAND)), but is EmuNAND even relevant anymore with Boot9strap and NTRBootHax? Even if you can't afford a card for NTRBootHax, you still have Boot9Strap which, unless you REALLY fuck something up, it's almost impossible to brick with!

Just because EmuNAND is not required and shouldn't be your default choice doesn't mean EmuNANDs are irrelevant. There's a reason Luma can still launch EmuNANDs (and multiple EmuNANDs at that) when it has removed other legacy stuff.

 

[SirNapkin1334]

Just because EmuNAND is not required and shouldn't be your default choice doesn't mean EmuNANDs are irrelevant. There's a reason Luma can still launch EmuNANDs (and multiple EmuNANDs at that) when it has removed other legacy stuff.

And the reason GM9 has support for EmuNand, as well as multi-EmuNand setups.

 

[d0k3]

Okay, here's a GM9 / Multi EmuNAND Creator related issue:
https://github.com/d0k3/GodMode9/issues/391

Okay, just so that we have this documented. With the exact same settings, Multi EmuNAND Creator created the second RedNAND...
... on a 128GB SD card at 0x3B000000
... on a 64GB SD card at 0x3BC00000

From all that I know, the first offset should be correct - I have no explanation for the second one, and no idea why Multi EmuNAND Creator should treat these two SD cards differently. Still hoping that @DarkMatterCore can shed some light.

 

[DarkMatterCore]

Okay, here's a GM9 / Multi EmuNAND Creator related issue:
https://github.com/d0k3/GodMode9/issues/391

Thanks for reporting it, I just commented on the GitHub issue.

 

[deSSy2724]

Im on luma3ds 11.8 (only sysnand, no emunands), can I use this to create an emunand and inject a backup of my 9.0 - 11.2 emunand over it with this tool?

 

[TurdPooCharger]

Im on luma3ds 11.8 (only sysnand, no emunands), can I use this to create an emunand and inject a backup of my 9.0 - 11.2 emunand over it with this tool?

Yes, this desktop program can create an EmuNAND or RedNAND on your SD card.

I'm presuming this is for a Gateway 3DS flashcart, jah?

 

[deSSy2724]

Yes, this desktop program can create an EmuNAND or RedNAND on your SD card.

I'm presuming this is for a Gateway 3DS flashcart, jah?

Exactly, dual boot (Luma and GW).

 

[emuashui]

a (emu)nand question so small that i ask it here instead of making a new thread,
is there method to know the version of a nand's version without restoring it to the console?
i tried to restore nands to emunand #0 but always met with error "not enough space to restore" alike; restoring to emunand #1 is fine:
why cant i use emunand #0 ?

 

[emuashui]

anyone successfully created 4 emunands?
i used the format card option, then injected in order #1 , #2 , #3 , #4 NAND using this tool ver 1.72,
but booting up the console (new type 3ds small version JP ) to check and found only 1 emu was created, no matter which default emunand ( #1/2/3/4 ) i setup in luma config.