Hacking [RELEASE] 3DS Multi EmuNAND Creator

[Real.96]

@DarkMatterCore
I'm using v1.61 but seem to run in to a issue regarding multiple emunands.
I injected one (JPN)emunand to "nand number1", then I went on to inject the second (USA)emunand into "nand number2". The program seems to work as intended, showing me a progress bar and letting me know the operation is complete.

When I put it back into my N3DS it only seems to find enunand1(JPN). Going to Luma settings and telling it to boot emunand2(USA) results in it booting into emunand1(JPN).
I tried injecting a EUR nanddump into "nand number2", still, it will only boot nand number1(JPN).

Edit: I don't know how I did it, but after 3-4 new tries of cleaning my SD and reformating it suddenly worked (seemingly) like a charm.

I'm having the same issue...emuNAND 1 works, emuNAND 2 doens't...

 

[Real.96]

@DarkMatterCore
I'm using v1.61 but seem to run in to a issue regarding multiple emunands.
I injected one (JPN)emunand to "nand number1", then I went on to inject the second (USA)emunand into "nand number2". The program seems to work as intended, showing me a progress bar and letting me know the operation is complete.

When I put it back into my N3DS it only seems to find enunand1(JPN). Going to Luma settings and telling it to boot emunand2(USA) results in it booting into emunand1(JPN).
I tried injecting a EUR nanddump into "nand number2", still, it will only boot nand number1(JPN).

Edit: I don't know how I did it, but after 3-4 new tries of cleaning my SD and reformating it suddenly worked (seemingly) like a charm.

How did you do it? Which Luma version did you use? (also, i can help you get the kor emuNAND xP)

 

[zaqqaz00]

Use latest Luma 6.6
LUMA supports 4 emunands

The emunands have to be created on the same console ie cannot come from another console.


To boot into emunands
(note gateway emunand will only boot with the payload method and occupies slot for emunand 1)

to boot into (non gw) emunand 1 hold Left camera Key = L and up bar
thus
L+ up = emu1
L+ right = emu2
L+ down = emu3
L+ left= emu4

 

[Real.96]

Use latest Luma 6.6
LUMA supports 4 emunands

The emunands have to be created on the same console ie cannot come from another console.


To boot into emunands
(note gateway emunand will only boot with the payload method and occupies slot for emunand 1)

to boot into (non gw) emunand 1 hold Left camera Key = L and up bar
thus
L+ up = emu1
L+ right = emu2
L+ down = emu3
L+ left= emu4

I'm using latest luma version and i know all the comands

 

[zaqqaz00]

I'm using latest luma version and i know all the comands

My reply was in refernce to this

How did you do it? Which Luma version did you use? (also, i can help you get the kor emuNAND xP)

 

[Natsuru]

I would love to see the app able to format a new SD card with the correct partition size (if that's possible) and select how many emuNANDs you would like to have.

 

[Zaphod77]

To make emunands of different regions work on same console, i think you have to change your console's region to get the nand dump.

 

[zaqqaz00]

I would love to see the app able to format a new SD card with the correct partition size (if that's possible) and select how many emuNANDs you would like to have.

This program does just that

 

[CrazyMaxx]

What shoud i do now?

The tool let me only inject emunands... How make new one?

 

[bandar]

So I keep getting invalid 3ds nand dump. Filesize (1979711488 Bytes) is invalid.
Also tried the trimmed one but got the same error but (1300234240 Bytes).
The dumps are verified in Decrypt9 and no errors so they are fine.
My device is New 3DS XL the first black colored edition (not special).
I also tried 9.2 ctrtransfer but no luck.
Is there a way to fix such issue? Thanks

Forgot to say my device runs on 11.3 and I have back up for both 11.3 and 11.2. Just thought you may ask

 

[Doeetright]

Use latest Luma 6.6
LUMA supports 4 emunands

The emunands have to be created on the same console ie cannot come from another console.


To boot into emunands
(note gateway emunand will only boot with the payload method and occupies slot for emunand 1)

to boot into (non gw) emunand 1 hold Left camera Key = L and up bar
thus
L+ up = emu1
L+ right = emu2
L+ down = emu3
L+ left= emu4

Sir, would you kindly be willing to help me? I am having one heck of a time doing just what you listed here. I have tried using this tool to no avail and I'm not sure if it's a user error or...? Is there some kind of guide for it that I could use? I've tried starting with a blank card and copying my SD contents over. I've tried with a previous EmuNAND via EmuNAND9.

I think my problem comes when extracting/injecting. I'm not sure if I'm extracting/injecting the right things. I've used everything from current NAND dumps to Original NAND dumps. Anyway, think you can help me figure this out?

TL;DR In case it wasn't clear, I need instructions on how to achieve this function:
L+ up = emu1
L+ right = emu2
L+ down = emu3
L+ left= emu4

 

[zaqqaz00]

Sir, would you kindly be willing to help me? I am having one heck of a time doing just what you listed here. I have tried using this tool to no avail and I'm not sure if it's a user error or...? Is there some kind of guide for it that I could use? I've tried starting with a blank card and copying my SD contents over. I've tried with a previous EmuNAND via EmuNAND9.

I think my problem comes when extracting/injecting. I'm not sure if I'm extracting/injecting the right things. I've used everything from current NAND dumps to Original NAND dumps. Anyway, think you can help me figure this out?

TL;DR In case it wasn't clear, I need instructions on how to achieve this function:
L+ up = emu1
L+ right = emu2
L+ down = emu3
L+ left= emu4

My method: First of all you must have a custom firmware with Luma, A9LH and Hourglass

Then follow the instructions posted by member the MCDO
if you still have problems PM me

L+ up = emu1
L+ right = emu2
L+ down = emu3
L+ left= emu4[

Once you create the multi emunands, you boot into emunand 1(if it is not a gatewway emunand) by holding the UP key and the Left camera key(on back of console) and then while holding these 2 keys hit the power button, let go after 4or 5 seconds, this will boot into Emu1

 

[Doeetright]

My method: First of all you must have a custom firmware with Luma, A9LH and Hourglass

Then follow the instructions posted by member the MCDO
if you still have problems PM me

Is this the post you are referring to?

https://gbatemp.net/threads/release-3ds-multi-emunand-creator.381603/page-16#post-7143288

And I'm not entirely sure how to PM on this site, is it the "Start a conversation" button? if not I may not be able to PM due to low post count.

 

[zaqqaz00]

Is this the post you are referring to?

https://gbatemp.net/threads/release-3ds-multi-emunand-creator.381603/page-16#post-7143288

And I'm not entirely sure how to PM on this site, is it the "Start a conversation" button? if not I may not be able to PM due to low post count.

Yes that is the post by member MCDO I was referring to

 

[DarkMatterCore]

Here's a quite *unexpected* update, I suppose.

v1.7:
* Completely revamped the EmuNAND parsing code.
* Added compatibility with multiple NAND layouts in the same SD card. The program is now able to detect, read and write EmuNANDs that don't share the same layout as the first one.
* Every NAND inject operation now defaults to the minimum size possible, including the format procedure. This should fix some compatibility problems with Luma3DS.
* If a new NAND is injected and the size of the previous NAND was greater than the minimum size possible, and if it wasn't stored as a RedNAND, its NCSD header will be wiped from the SD card to avoid problems.

I hope you still find this tool useful.

 

[Arithmatics]

Here's a quite *unexpected* update, I suppose.



I hope you still find this tool useful.

always. Thanks for this

 

[MassExplosion213]

Here's a quite *unexpected* update, I suppose.



I hope you still find this tool useful.

Thanks for the update.

 

[DarkMatterCore]

Here's yet another update:

v1.71:
* Updated program manifest to target at more Windows versions.
* Added a proper Windows version check. The program won't run under a Windows version older than XP SP2.
* Fixed a bug where the DRIVE_INFO struct pointer could be freed twice, leading to a crash when trying to refresh the drives lists.
* Simplified the code for checking if the program is running under admin mode.

I have also created a GitHub repository for this project; check it out if you want.

 

[Kazuma77]

Here's yet another update:



I have also created a GitHub repository for this project; check it out if you want.

I'm finding this release completely unusable (at least in Windows 7 x64, haven't tried XP or WINE yet, and as for 10, I'm really not wanting to try this in a VM). Sometimes there is an error at the very end of the write process (I've even got it writing to the first EmuNAND -- it gave the error, then worked the second time). If this happens when trying to create a 2nd or higher EmuNAND, trying to create it again eats more space. Even worse, sometimes it says it succeeded, but neither the EmuNAND shows up, nor is the FAT32 partition accessible. It's like it's trying to make another EmuNAND each time, instead of writing to the one I selected. The only way to fix it seems to be to remove the previous EmuNAND. But I can't get anywhere moving backwards. I was going for one legacy EmuNAND and two minimum RedNANDs on my N3DS, but apparently it wasn't meant to be. Because the next highest version I have is 1.2.

Oh yeah, sometimes it also says the wrong disk is in the drive. But that one's purely cosmetic. I'd focus on the others first.

Anyway, thanks for trying. I've always loved the concept. That it would break when I finally got around to using it is just par for the course.

EDIT: I managed to find a copy of 1.61 and that worked (though it didn't save me any space, since they all have to be the same length). It seems like where things really go to Hell is when you try to create EmuNAND #3. Most people probably use two or less (one for GW, and one for homebrew) and would therefore never encounter the card corruption issue, but I decided to merge my old eShop cards so I can use them for music (not that getting update tickets/keys has been a problem recently, but I might as well keep them around if I have the space). Anyway, I'll upload it in case anyone needs it in the meantime.

 

[DarkMatterCore]

Sometimes there is an error at the very end of the write process (I've even got it writing to the first EmuNAND -- it gave the error, then worked the second time). If this happens when trying to create a 2nd or higher EmuNAND, trying to create it again eats more space. Even worse, sometimes it says it succeeded, but neither the EmuNAND shows up, nor is the FAT32 partition accessible. It's like it's trying to make another EmuNAND each time, instead of writing to the one I selected. The only way to fix it seems to be to remove the previous EmuNAND. But I can't get anywhere moving backwards. I was going for one legacy EmuNAND and two minimum RedNANDs on my N3DS, but apparently it wasn't meant to be. Because the next highest version I have is 1.2.

Oh yeah, sometimes it also says the wrong disk is in the drive. But that one's purely cosmetic. I'd focus on the others first.

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