answered Unsure how I'm supposed to install EmuNAND

[coltonsmogon]

So how exactly am I supposed to get the EmuNAND ready on my 3DS? I would certainly like to test out my new Omega Ruby hack with legendary E4 teams. I'm getting rather anxious...

[Sabresite]

Following plailect tutorial, I believe.

[coltonsmogon]

30 minutes ago, Sabresite said:

Following plailect tutorial, I believe.

Can't find it. Site doesn't have it anymore

[Poke J]

@coltonsmogon try using this tutorial it sounds similar to what I did when I set mine up.  I can't give you the tutorial I used since it doesn't exist anymore.  https://gbatemp.net/threads/tutorial-setting-up-9-0-9-2-n3ds-xl-for-cfw-including-emunand-coldboot-cia-installer.405589/ .  As myself haven't actually used this tutorial I probably will not be able to lend assistance if you get stuck so read it over and understand the procedure before beginning.

[suloku]

STOP EVERYONE!

I feel like I know more about this topic, and the guide Poke J linked is quite outdated. Why do you want an Emunand exactly? That should be the first question since what suits you best depends on that.

The recommended method is to install A9LH and don't use EMUNand at all. For that follow this guide: https://3ds.guide/
Some notes about current A9LH installation:
- You do a full nand backup before the process starts. You should keep at least 2 copies of that somewhere safe (different hard disks) since this nand backup can be used to restore your 3DS to exactly how it was before you installed A9LH, used CFW or anything.
- A9LH allows you to directly boot into CFW EMUNand way faster than other methods.
- A9LH can be uninstalled without restoring a nand backup, so you might install A9LH to use an emunand and leave your SYSNand untouched (except for A9LH installation) and remove it anytime you want. If you don't use EMUNand and install a crapload of things to your sysnand over the months and at some point you want to "unmodify" your 3DS, the best way is to restore your Nand backup, since that gets you back where you started.

IMPORTANT: if you suspend (close the lid) of your console during A9LH installation you will brick it. This is the only significant danger in A9LH installation, since the programs have many safety checks to ensure everything goes fine.

Boot process on A9LH + Luma CFW (the recommended cfw):
- Power ON (and that's all, you can now access everything)

If you want EMUNand because you have a 9.0<->11.3 firmware console and you want to leave your SYSNand untouched, you can run EMUNand from homebrew launcher and you never have to install anyhting on your 3DS, but the boot process is tedious and longer, but valid if you are afraid of messing up A9LH installation. I don't have link for a guide for this method, but it is possible to do it this way. On firmwares that have menuhax you can speed up the boot process, menuhax sometimes fails.

The boot process for Emunand on untouched sysnand would be:
- Power ON
- Use entrypoint to get on homebrew launcher (depends on firmware)
- Run fasthax (or the alternative for 11.3 that came out recently)
- Run the kernel exploit (safehax I believe)
- Run the EMUNand launcher (I believe just Luma CFW launcher at this point)
- Wait until EMUNand boots.

To setup an emunand you just need to use Emunand9 under kernel access, (BACKUP YOUR SD CARD FIRST! CONTENTS GET ERASED AND YOU HAVE TO COPY THEM OVER AFTER SETUP!): https://gbatemp.net/threads/release-emunand9-open-source-emunand-formatter-manager.405921/
Emunand9 basically formats your SD card, makes the emunand partition and copies your sysnand over to the emunand partition ready to be boot with a CFW like Luma. Afterwars you just need to copy the contents you backed up from your SD card again onto the SD card.

ps: all homebrew in the most updated version have many safety checks to ensure nothing goes wrong, but doing things with kernel access always means there's a chance something goes wrong (normally due to the user doing something wrong/skipping some steps) and bricking your 3DS.

[coltonsmogon]

I'm trying to get custom ROM hacks onto my system, & the only way I know how I could do that is install an EmuNAND first... If you've got any other suggestions, that'd be welcome...

EDIT: It seems .NET 3DS Toolkit builds CIAs for them already, just they have the .3ds extension. I'll try renaming it to .cia before I install it... Thanks for your help though!

Edited April 15, 2017 by coltonsmogon

[evandixon]

Emunand is no longer a requirement for hacks, and with A9LH it's easier to not have it.

3 hours ago, coltonsmogon said:

It seems .NET 3DS Toolkit builds CIAs for them already, just they have the .3ds extension. I'll try renaming it to .cia before I install it... Thanks for your help though!

Unless you specifically tell it to make a CIA, you need to tell it to save with a .cia file extension.  Using auto-detect and a .3ds extension will generate an unencrypted CCI.

 

5 hours ago, suloku said:

- Run fasthax (or the alternative for 11.3 that came out recently)

- Run the kernel exploit (safehax I believe)

AFAIK the thing that was released for 11.3 was an ARM11 kernal exploit.  An ARM9 kernal exploit is needed for booting CFW, and I don't remember seeing anything about one for 11.3.

[coltonsmogon]

Yes, I told it to make an unencrypted CIA. Came out as a .3ds file, rename to .cia, install in FBI, & done! Playing the hack right now. Can't wait to see the newfound power of the E4!

[suloku]

If you could already install cia files why did you want to setup emunand? It seems you already have a CFW running.

2 hours ago, evandixon said:

AFAIK the thing that was released for 11.3 was an ARM11 kernal exploit.  An ARM9 kernal exploit is needed for booting CFW, and I don't remember seeing anything about one for 11.3.

I wasn't aware of that, I read the new exploit was a workaround for the same exploit on 11.3, so I assumed it would work the same as in 11.2, but seem I was wrong (or read it wrong)

[evandixon]

1 minute ago, suloku said:

If you could already install cia files why did you want to setup emunand? It seems you already have a CFW running.

I wasn't aware of that, I read the new exploit was a workaround for the same exploit on 11.3, so I assumed it would work the same as in 11.2, but seem I was wrong (or read it wrong)

Sorry, looks like I was wrong.  Safehax was updated for 11.3, so I guess I just didn't see it.