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

[laharl22]

Its a dual emunand created older time

 

[urherenow]

It's even useful to GW users, as they don't need to format the whole SD card to make an emuNAND anymore (with pre existing emuNAND that is) it's funny when people outdo gateway in every way

With an emunand partition already created you never did need to format the SD card. You just needed to use your PC (emunandtool)

and they can't be known before the 3Ds generates them.

I'm pretty sure the number will change after the format. If not, you can just add your Ironfall install to your personal starter.bin (read the readme!).

No... the number only changes when you format from system settings within the 3ds. The numbers are already in the NAND (There are folders in the nand.fat16 partition with the same numbers) and the way they are created is a function of movable.sed. When you format your nand in system settings, it deletes the ID0 and ID1 folders from your SD card (if you didn't remove it... which you can't if using emunand) and also deletes those folders from nand. They are regenerated via movable.sed and some random seed.

When you clone your sysnand into emunand, nothing changes. That's why they are "linked" until you format sysnand afterwards.

I did a manual system transfer for reasons I'll not get into here, but I'll just say that my o3ds emunand and N3ds emunand both use the same numbers and can read each other's files. I'm also stuck with the same friend code on both of them :/ (I haven't bothered digging in there and deleting it from one of the nands yet, so I can generate a new one).

 

[d0k3]

No... the number only changes when you format from system settings within the 3ds. The numbers are already in the NAND (There are folders in the nand.fat16 partition with the same numbers) and the way they are created is a function of movable.sed. When you format your nand in system settings, it deletes the ID0 and ID1 folders from your SD card (if you didn't remove it... which you can't if using emunand) and also deletes those folders from nand. They are regenerated via movable.sed and some random seed.

When you clone your sysnand into emunand, nothing changes. That's why they are "linked" until you format sysnand afterwards.

I did a manual system transfer for reasons I'll not get into here, but I'll just say that my o3ds emunand and N3ds emunand both use the same numbers and can read each other's files. I'm also stuck with the same friend code on both of them :/ (I haven't bothered digging in there and deleting it from one of the nands yet, so I can generate a new one).

Yup, guess I was wrong with that. @MassExplosion213 if you try it let me know if it worked. Setting up a personal starter.bin is easy and maybe even fun, promised.

 

[MassExplosion213]

Yup, guess I was wrong with that. @MassExplosion213 if you try it let me know if it worked. Setting up a personal starter.bin is easy and maybe even fun, promised.

It did. I've done that already. And you're right. Kinda fun. Just needs a GUI now.

 

[dark_samus3]

The problem was in main.c. I already fixed it, can you take a look again?

@dark_samus3 maybe you can help! In the EmuNAND9Tool 'starter' subdir is a Windows batch script. A pretty simple one, and I see no reason why using this should be limited to Windows users. I also had to include 7za (EXE). I'd very much like to use GZip, but I'm unsure how to get the same result with it (don't compress .hidden files and use ./starter/extstarterpack/ as the root dir of the ZIP archive). Any idea how to handle this in GZip without actually moving files around?

I'd think you'd need to do something like "gzip ./starter/extstarterpack/*" which, at least on Linux, doesn't include any .hidden files. Mainly because the wildcard excludes . as the first character so files like file.ext will show up along with directories (you may need a gzip option for directories) but not .hidden files I'd say just try it out. Not sure how to do it with 7zip CLI version but I'm sure it won't be too hard

EDIT: based on the make file it's extremely easy to port over to linux it looks like my only problem is how to handle the 7zip stuff... it's easier to include it for users but harder to support for us, like for example handling different OSes... maybe if you have the user install it so that it's in their $PATH already (it seems to assume that you have something like msys or cygwin already installed so that could easily be handled by the Makefile) which would make it fairly easy to support... It's up to you, I'm working on gzip right now and those were the few problems I saw going forward with a linux port so I figured I'd mention it

 

[Deleted member 356526]

@d0k3 Can I just mention, you are amazing. You are helpful and rock.

 

[muskieratboi]

Great tool so far, D0k3.

As for a feature request, could you add a fat16 Xorpad generator and a SysNAND Flasher? (Yes, I'm aware how dangerous that is, feel free to put it behind, like 10 screens of warning text!)

As i'm on 4.5, I have to flash a modified SysNAND because standard FBI injection isn't working right.

 

[dark_samus3]

Great tool so far, D0k3.

as for a feature request, could you add a fat16 Xorpad generator and a SysNAND Flasher? (Yes, I'm aware how dangerous that is, feel free to put it behind, like 10 screens of warning text!)

As i'm on 4.5, I have to flash a modified SysNAND because standard FBI injection isn't working right.

Just use Decypt9 for that

 

[muskieratboi]

Just use Decypt9 for that

You can Flash SysNAND in Decrypt9?

 

[dark_samus3]

You can Flash SysNAND in Decrypt9?

Yep

 

[d0k3]

You can Flash SysNAND in Decrypt9?

Yup, I added this feature a while ago. Use the link from my signature.

 

[muskieratboi]

EDIT 2: Got it! Big thanks to @dark_samus3 who led me to the experimental Decrypt9. dumped h&s and injected FBI perfectly, no xorpads required. Thanks a whole bunch for these tools, @d0k3!

 

[MelonGx]

Two questions:
1) Does it work on 64-512GB SD/MicroSD?
2) There is a rare type of 2DS, whose emuNAND formatted by GW is 2GB and it doesn't work, unless the user inject that 2GB emuNAND into a 1GB emuNAND partition. Is this tool compatible with this type of 2DS?

 

[d0k3]

Two questions:
1) Does it work on 64-512GB SD/MicroSD?
2) There is a rare type of 2DS, whose emuNAND formatted by GW is 2GB and it doesn't work, unless the user inject that 2GB emuNAND into a 1GB emuNAND partition. Is this tool compatible with this type of 2DS?

1.) I tried it successfully on a 64GB SD and there is no reason why it should not work on a larger one. In fact, if the 3DS can handle the SD card, this tool can, too!
2.) That needs a tester. I'm pretty sure that problem doesn't exist here, but I can't say for sure.

 

[AileenLumina]

Well, this makes it almost unnecessary to code a Java 3DS CFW Installation Assistant xD Damn...

Whatever, it's an awesome piece of software that makes things a lot easier. Thank you for all your efforts!

 

[kidasquid]

You, sir d0k3, are a treasure to this community! Is that a kd ratio or doke, btw? Not sure how to pronounce that when I name my first child.

 

[djalmafreestyler]

Does it have FBI to install CIAs after format emuNAND? Any way to no need to inject fbi in S&H?

 

[mid-kid]

About time someone did this. Great work @d0k3.
EDIT: Is there an option to create a redNAND?

 

[dark_samus3]

Does it have FBI to install CIAs after format emuNAND? Any way to no need to inject fbi in S&H?

I believe the default start.bin does have FBI included in it for hax, but I think you'd be better off installing it to H&S

 

[d0k3]

Does it have FBI to install CIAs after format emuNAND? Any way to no need to inject fbi in S&H?

The answer is, as many times before, in my signature . Use Decrypt9 and Universal Inject Generator (both links in my signature) to inject anything into H&S.