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

[d0k3]

I don't mind the backup work and don't mind reformatting, but don't particularly want to make a new EmuNAND. Will it suffice to back up the EmuNAND and all the files, format the SD, then restore the existing EmuNAND?

I can't switch to RedNAND anyway because I do very occasionally use my Gateway.

Yes, of course, that's how it works.

 

[GBHAKC75]

Yes, of course, that's how it works.

Did you quoted my post by mistake ?

 

[d0k3]

Did you quoted my post by mistake ?

Yup, mistake . By the way, EmuNAND9 adds a proper entry for 'hidden' EmuNAND partition to the MBR, but no other tools takes advantage of that (afaik).

 

[GBHAKC75]

Yup, mistake . By the way, EmuNAND9 adds a proper entry for 'hidden' EmuNAND partition to the MBR, but no other tools takes advantage of that (afaik).

That's too bad, because it "should" be the way how it works x). But I guess it's way simpler to simply read NAND from/to hardcoded offsets than parsing MBR ^^.
However, I wonder : is there multiple MBR entries when using more than 1 emuNAND or are all they in the same partition ?

 

[d0k3]

That's too bad, because it "should" be the way how it works x). But I guess it's way simpler to simply read NAND from/to hardcoded offsets than parsing MBR ^^.
However, I wonder : is there multiple MBR entries when using more than 1 emuNAND or are all they in the same partition ?

That's a theoretical question, you know? Because EmuNAND9 is the only tool doing this and EmuNAND9 does not set up Multi EmuNAND. But, to do it right, each EmuNAND would have to be in a separate partition, which would also limit us to three EmuNANDs (if we don't use extended partitions, and we won't).

 

[GBHAKC75]

That's a theoretical question, you know? Because EmuNAND9 is the only tool doing this and EmuNAND9 does not set up Multi EmuNAND. But, to do it right, each EmuNAND would have to be in a separate partition, which would also limit us to three EmuNANDs (if we don't use extended partitions, and we won't).

EmuNAND MultiTool could also modify MBR, but I think it only uses one partition at the moment. However I don't think this will change one day, since every multi EmuNAND-compatible software is using this right now (which is pretty bad IMO, since partition table is here for a reason).
And three EmuNANDs should be more than enough for everyone, including multi emuNAND users ^^.

 

[leonmagnus99]

Yo guys, if i choose the convert option within emunand9 .

convert from emunand(gw emunand) to redNAND, will it just copy paste redNAND ontop of the current GW emuNAND that i have ?
it sounds simple but i guess i will make a backup of my current emuNAND and then i shall try converting it.

 

[d0k3]

Yo guys, if i choose the convert option within emunand9 .

convert from emunand(gw emunand) to redNAND, will it just copy paste redNAND ontop of the current GW emuNAND that i have ?
it sounds simple but i guess i will make a backup of my current emuNAND and then i shall try converting it.

Make a backup of your EmuNAND. It will leave everything else untouched. And EmuNAND9 warns you of possible consequence (and gives you the option to cancel) every step along the way, so no worries.

 

[leonmagnus99]

Make a backup of your EmuNAND. It will leave everything else untouched. And EmuNAND9 warns you of possible consequence (and gives you the option to cancel) every step along the way, so no worries.

yes my dude ! it does

and i was.. too.. hasty i am already converting it XDDD

because i didnt see any message stating "this can be potentially dangerous and will wipe your mSD" etc.

so since it is just a conversion i just pressed the buttons and it is converting it now !

btw. i am doing this on an OG and the MB size shows 954MB and i know the n3ds has like a 1.4gig i believe.

so does the redNAND actually also get smaller in size for the og 3ds ? i assume the 954 mb is off the GW emuNAND, and i know i would actually need to completely wipe the mSD for a fresh redNAND partition in order to get it to a smaller sized take of partition yep?

but other than the size issue, i hope it still takes affect? the redNAND partition !

i will check the emuNAND with emunand9 after it finishes conversion, and if it shows redNAND emunand then it means conversion was a success yes?

edit : alright it succeeded! it shows now emunand : rednand inside the emunand9.

one thing i would like to ask is, if i use my GW card on redNAND , it will not work yeah? (and even not if i used the firm90 sysNAND? and if i booted GW emuNAND from there would it not work with redNAND? so like if i dont have a GW emuNAND partition ,my gw card will not boot me into its emuNAND yes?)

so if i wanted a gateway emunand, i should first back it up and then convert it and then inject my gw emunand into mSD again yes? but this would also mean that my mSD would have 2 NAND partitions one red and other one gw emuNAND yep?

lastly ( it still says GATEWAYNAND when i push my mSD into my laptop, is this no biggie? it does say rednand when i launch emunand9, so i think i could just go ahead and rename my mSD into whatever i like? )
thanks in advance!

 

[d0k3]

yes my dude ! it does

and i was.. too.. hasty i am already converting it XDDD

because i didnt see any message stating "this can be potentially dangerous and will wipe your mSD" etc.

so since it is just a conversion i just pressed the buttons and it is converting it now !

btw. i am doing this on an OG and the MB size shows 954MB and i know the n3ds has like a 1.4gig i believe.

so does the redNAND actually also get smaller in size for the og 3ds ? i assume the 954 mb is off the GW emuNAND, and i know i would actually need to completely wipe the mSD for a fresh redNAND partition in order to get it to a smaller sized take of partition yep?

but other than the size issue, i hope it still takes affect? the redNAND partition !

i will check the emuNAND with emunand9 after it finishes conversion, and if it shows redNAND emunand then it means conversion was a success yes?

edit : alright it succeeded! it shows now emunand : rednand inside the emunand9.

one thing i would like to ask is, if i use my GW card on redNAND , it will not work yeah? (and even not if i used the firm90 sysNAND? and if i booted GW emuNAND from there would it not work with redNAND? so like if i dont have a GW emuNAND partition ,my gw card will not boot me into its emuNAND yes?)

so if i wanted a gateway emunand, i should first back it up and then convert it and then inject my gw emunand into mSD again yes? but this would also mean that my mSD would have 2 NAND partitions one red and other one gw emuNAND yep?

lastly ( it still says GATEWAYNAND when i push my mSD into my laptop, is this no biggie? it does say rednand when i launch emunand9, so i think i could just go ahead and rename my mSD into whatever i like? )
thanks in advance!

Oh well, is a forum post or is it an essay?

The conversion feature does exactly what it says, it converts your EmuNAND from GW format to RedNAND format or vice versa. No need to restore anything if it goes through, everything is in place. The backup is in case something unexpected happens, like your 3DS losing power or whatever. You won't get any much improvement in free space for O3DS, the big savings are only for N3DS (with 1.8GB chips). RedNANDs won't work in GW, and if you let GW create a new one, it will overwrite your existing one. You can also name your SD card anything you like, that's your choice.

Also, doing the conbversion too often is not good for your SD card lifetime, just saying in case you want to switch back and forth.

 

[Deleted member 373223]

You won't get any much improvement in free space for O3DS

not much, but you saved me 1 mb.

 

[leonmagnus99]

Oh well, is a forum post or is it an essay?

The conversion feature does exactly what it says, it converts your EmuNAND from GW format to RedNAND format or vice versa. No need to restore anything if it goes through, everything is in place. The backup is in case something unexpected happens, like your 3DS losing power or whatever. You won't get any much improvement in free space for O3DS, the big savings are only for N3DS (with 1.8GB chips). RedNANDs won't work in GW, and if you let GW create a new one, it will overwrite your existing one. You can also name your SD card anything you like, that's your choice.

Also, doing the conbversion too often is not good for your SD card lifetime, just saying in case you want to switch back and forth.

neat, thanks man .

 

[MegaBoyEXE]

That depends. I assume you used GW to do the format before? GW wastes a ton of space for N3DS EmuNANDs, and I'm pretty sure the placement of the data is off. The placement of the FAT is okay, though. If you want to know more about this, read here. In any case. you should use the official SD card formatter for SD cards (when formatting in Windows) and EmuNAND9 (when formatting on console). Now, should you make the switch? The performance difference between a perfectly formatted SD card vs one formatted in the worst possible way can be a lot. It most likely isn't though, you'd have to deliberately format the card in a bad way, but you can easily lower the lifetime of your SD card by ~50% with bad formatting. I'd recommend making the switch, if you can stomach all the backup work involved.

Well, since Emunand9 does not support multi-emunands, is it hard to add an option in 'Format SD' to just format the current FAT32 partition, without touching the reserved space for multi-nands?
Maybe something like 'Format FAT only', of course if there's no need to adjust nothing in MBR to allow high performance standards.

Both your program and the official SDFormatter wipes out the partition layout, so I can't have a 'multi-nand + awesome performance' right now.

 

[wurstpistole]

Quick question, how would I proceed to switch my sd card to a bigger one with Emunand9 - just make backup of Emunand with Emunand9, backup all the files with a sd reader, put all the files on the other card and the emunand dump, and then just write the emunand dump to SD with Emunand9? Or do I need to make a new emunand setup on the new card first, and then inject the backed up Emunand?

 

[DjoeN]

So i'm gonna use a new SD and setting it up with EmuNand9. (same sd brand, same size)

- When selecting complete setup, it copies starter.bin to memory and then i can swap the old sd with the new one and do the keycombo to start.
- Then it writes starter.bin/boot.3dsx to sd and setup *hax to finish autosetup and starts cloning sysnand to emunand

My question:
- My sysnand has A9LH on it to boot AuReiNand A9LH into emunand 10.7, will it also clone the A9LH hax to emunand? cause that would be an issue i suppose?

[EDIT]
Well it seems to work perfect
It booted into AuReiNand config and after setting that up it booted fine into emunand 9.2

 

[d0k3]

Well, since Emunand9 does not support multi-emunands, is it hard to add an option in 'Format SD' to just format the current FAT32 partition, without touching the reserved space for multi-nands?
Maybe something like 'Format FAT only', of course if there's no need to adjust nothing in MBR to allow high performance standards.

Both your program and the official SDFormatter wipes out the partition layout, so I can't have a 'multi-nand + awesome performance' right now.

There is no proper solution for this in EmuNAND9, cause formatting the SD according to the standard also requires a proper placement of the partition (in the MBR). You can do this, though: Backup everything from your SD, then format it with the official SD Formatter. Then use this to move the partition and make space for your Multi EmuNAND, but make sure it goes exactly to a multiple of 4MB (1MB = 1024*1024 byte) offset. 4GB, for 2 EmuNANDs, for example, would be okay.

Quick question, how would I proceed to switch my sd card to a bigger one with Emunand9 - just make backup of Emunand with Emunand9, backup all the files with a sd reader, put all the files on the other card and the emunand dump, and then just write the emunand dump to SD with Emunand9? Or do I need to make a new emunand setup on the new card first, and then inject the backed up Emunand?

You at least need to have that new card properly formatted for EmuNAND (via SD Format Options). Then you can go ahead.

P.S. Other than other things no April fools prank, guaranteed .

 

[wurstpistole]

If I format my SD with Emunand9, does it make a full wipe or quickformat?
Currently setting up a 64gb card, and it's been sitting at "formatting fat partition" for some minutes now

 

[d0k3]

If I format my SD with Emunand9, does it make a full wipe or quickformat?
Currently setting up a 64gb card, and it's been sitting at "formatting fat partition" for some minutes now

Quick format, if you chose the 'Complete Setup' it also transfers SysNAND to EmuNAND. The format itself taking for a bit can be perfectly normal, but if it doesn't continue after 10 minutes or more, just force shutdown and try again.

 

[wurstpistole]

Quick format, if you chose the 'Complete Setup' it also transfers SysNAND to EmuNAND. The format itself taking for a bit can be perfectly normal, but if it doesn't continue after 10 minutes or more, just force shutdown and try again.

It has finished now after around 10 minutes. Cloning of sysnand took around another 10 minutes. I recently had the problem that my emunand backup took over an hour (maybe you remember) and I reformatted my sd now to maybe get rid of fragmentation or something, seems it helped. Now I just need to restore all my files, and clone my old emunand in again and it's like before, but on a cleaned card.

 

[kesongputi]

hi dok3, i cant seem to run the latest version of emunand using the homebrew launcher. can you point me to the right direction, I'm new at this, many thanks!