Ensure you have a pre-cfw CLEAN NAND backup if you want to use sysnand for online

File based EmuMMC is working but if you use FAT32 it is very limited and heavily bottlenecked, if you decide to use exFAT then it is very unstable and can corrupt your SD card easily; as of now use partition based as file based is very slow/unstable!!

Rewriting guide with NYX in mind alongside quad boot files for that.


Pre-Setup [Win/Linux]

Spoiler

• Dump your NAND via hekate or use a clean dumped nand(you need to dump BOOT0/BOOT1 and rawnand) ENSURE AUTORCM IS TURNED OFF!
• Merge these into one file using:
  
  Linux cmd:
  cat BOOT0 BOOT1 rawnand.bin.00 rawnand.bin.01 rawnand.bin.02 rawnand.bin.03 rawnand.bin.04 rawnand.bin.05 rawnand.bin.06 rawnand.bin.07 rawnand.bin.08 rawnand.bin.09 rawnand.bin.10 rawnand.bin.11 rawnand.bin.12 rawnand.bin.13 rawnand.bin.14 > emummc.bin
  
  Windows cmd:
  copy /b BOOT0+BOOT1+rawnand.bin.00+rawnand.bin.01+rawnand.bin.02+rawnand.bin.03+rawnand.bin.04+rawnand.bin.05+rawnand.bin.06+rawnand.bin.07+rawnand.bin.08+rawnand.bin.09+rawnand.bin.10+rawnand.bin.11+rawnand.bin.12+rawnand.bin.13+rawnand.bin.14 emummc.bin
• If you are using a single file dumped nand then:
  Linux cmd:
  cat BOOT0 BOOT1 rawnand.bin > emummc.bin

Windows cmd:
copy /b BOOT0+BOOT1+rawnand.bin emummc.bin

Setting up EmuMMC[Linux]

Spoiler

1. Format your SD, clear any partitions and etc.
2. Create your normal partition (MAKE SURE IT IS FAT32 AND 32K CLUSTER).
3. Leave enough space to fit the NAND image.
4. Make that last partition FAT32 aswell
   
5. Identify the partition address */dev/xxx
6. Use this command to write your complete emummc image to the EmuNand partition we made earlier:
   sudo dd if=<your_emummc_bin> bs=512M of=<Step 5, partition add> status=progress
7. Once this is done download the latest AMS and Hekate.
8. Download the EmuMMC config and create a folder named "emummc" then paste it there..
9. Use a tool like GParted to find the first sector of the partition holding the EmuNAND
10. Convert the value from step 8 to hexadecimal > just google <number> to hexadecimal ; it should give out a number such as 0x1039 and etc; IF on the case that it gives one like say 800 then it'll be 0x800.
11. SOMETIMES EmuMMC may not work fully with "0x" infront of the sector, it's hit & miss.
    
12. edit the config file in emummc with this value.

Setting up EmuMMC[Windows10]

Spoiler

Install tools:

• https://www.partitionwizard.com/partitionmanager/sd-partitions.html (Has freeware installer at the end, ensure you untick the box)
• https://uranus.chrysocome.net/linux/rawwrite/dd-0.4beta1.exe (Copy this into the folder where you made your complete EmuMMC image, rename it to dd)

Steps:

• Using the partition tool, delete all partitions on the sd (all data on the sd will be gone)
• Create the first partition at the start of the table, make this a Fat32 32K Cluster partition, leave 31GB at the end of the table.
• Format the end partition as FAT32 aswell, cluster size does not matter.
• 
• Using CMD cd into the folder where you have your emuMMC files and dd.
• Figure out what partition you will specificy to DD by using running the cmd dd --list
• 
• As you can see K: is my EmuMMC partition and it is linked to \\?\Device\HarddiskVolume19, this is the disk we will write to via DD.
• Using the CMD dd if=<your_emummc_bin_path> bs=512M of=<Disk we identified on previous step> --progress image your EmuMMC onto the last partition.
• Once the last partition has your EmuMMC, start setting up AMS and Hekate, download Atmosphere CFW and Hekate.
• Copy AMS + Hekate onto your SD
• Download the EmuMMC config and create a folder named "emummc" then paste it there.
• Find your first sector by using the disk tool, right click your EmuMMC partition > properties > partition info > first physical sector.
• Convert the number to hexadecimal by going on google and searching <Number> to hexadecimal ; a value such as 0x492A3900 or etc will show.
• SOMETIMES EmuMMC may not work fully with "0x" infront of the sector, it's hit & miss.
• Open emummc folder on your sd then open the config and paste the hexadecimal number over the existing one.
• Launch hekate then atmosphere, if it is all done right you should be in EmuMMC

Dual/Triple/Quad boot[L4T Ubuntu/Lakka, Stock-Sys, EmuNand]

Spoiler

Rewrite in progress

Notes:

• No I won't sit you through this, the process is already laid out there.
• If you decide to use exFAT I won't really help.
• You can do the partitioning and file merging on windows but I don't know any tool to write the image to a specific partition.
• There is NO such thing as *Cleaning* your NAND, if you don't have a clean backup then bad luck, you can maybe get away with clearing logs if you haven't been online for a long time but even then I wouldn't suggest it; should've made a clean NAND backup, I won't guide you through any of that.

CLICK HERE FOR EMUMMC CONFIG

DISCLAIMER: I am not resposible for you killing your switch, bricking it from the failure to make a NAND backup; I am in no way obliged to provide you personal support nor am I obliged to do anything else; I'm not resposible for you messing up your SD Card either.



Windows guide:

 

[hellogbatemp]

I get the following error when trying to write the emummc.bin onto my SD card

Error writing file: 87 The parameter is incorrect
0
1+0 records in
0+0 records out

Anyone know what the problem is?

same here ! help please

 

[RyanfromWork]

AMS just stands for Atmosphere, which means you are in AMS.
Doesnt matter if EmuNand or NAND

I though you asked how you can tell the difference between emuMMC and stock?

Stock, you clearly wont have atmosphere.

If you are in AMS you are in CFW... if you dont see ams you are on stock.

--------------------- MERGED ---------------------------

[QUOTE = "healthyboy, post: 8683146, member: 493770"] L'erreur suivante s'affiche lorsque j'essaie d'écrire emummc.bin sur ma carte SD.

Erreur d'écriture du fichier: 87 Le paramètre est incorrect
0
1 + 0 enregistrements dans
0 + 0 enregistrements

Quelqu'un sait quel est le problème? [/ QUOTE]
sam here. help please.

I cant read what you wrote, but i know what youre talking about

It is regarding the DD part, i accidentally used copy /b boot0+boo1+rawnand.bin.00+.... rawnand14 emuMMC.bin

When it should be “copy /b boot0+boot1+rawnand.bin emuMMC.bin”. Where i messed up was not creating the rawnand.bin file first, then using that along with the boot0/1 to make the emuMMC.bin file.

 

[Bl4ckeagle]

I though you asked how you can tell the difference between emuMMC and stock?

Stock, you clearly wont have atmosphere.

If you are in AMS you are in CFW... if you dont see ams you are on stock.

No I meant the difference between Emunand and Normal Nand...

2. Question
Is it possible to just copy the sigpatches or do i have to compile everything by my own?

 

[RyanfromWork]

No I meant the difference between Emunand and Normal Nand...

2. Question
Is it possible to just copy the sigpatches or do i have to compile everything by my own?

Ahh! In that case... BUMP! I have the same question...

I cant even get my 7.0.1 emunand fw to load. I can only get my switch to load into the restored via Hekate 4.0.1 FW (or CFW due to fuses, but it did allow verification of my 4.0.1 FW files arent corrupt)

I’m hoping the emunand is being used and not dirtying up my clean backup. (Which doesnt matter since it looks like I’m going to be repeating the process once i get things straighten out)

(Definitely not telling the Devs how to do anything) Where we find FW version then (ams x.x.x - emu) would be a nice hint.


2. Question

I honestly assume its similar to before. (I wish i knew how to compile anything beside “hello world”)

lets pretend you have everything setup exactly as you wanted it. I assume the patches would work as long as youre not on 8.1.0.....

 

[Cyan]

What about using hekate to boot to stock using autorcm?

unfortunately it's not possible to boot stock with hekate anymore since 7.x

Don't these two options pretty much result in the same thing?

for the 3, the result is the same yes, it's just how you do it which is different.

1. doing it manually and starting by writing the emu partition is the hardest, as you'll have to do all the math yourself (dd the bin starting sector 1 size=dump size, edit MBR to add a new partition after the emu position, (partition sector start+sector number), then you can format it.
2. create 1 partition that you move at the end if your tool allows it, leaving enough unallocated space in the front, then dd starting sector 1
3. the easiest, creating 2 partitions is faster and easier like the guide on first post, but then you replace the first one with the dump and you edit the MBR manually (or first delete the partition with a manager, it should only edit the MBR and not touch the actual partition content)

I don't have the command to type from memory for dd to start at 1 with the dump size, but I could deduce it if I have time. someone else will probably post it before me.

 

[nopo]

11 parts?, something's not right; redump it.

I cant redump because it's my dump from 6.0 and I'm on 8.0.1 now

 

[quincy uryuu]

I've tried running dd --list through command prompt and power shell, both give me errors about "dd" not being recognized as a function. Can anyone tell me what I'm doing wrong?

Edit- I think I figured it out.

 

[eyeliner]

Something odd has happened. I reinstalled a couple of nsps (Hello Kitty Kruisers and Lego Worlds).

THEY ARE FOR MY DAUGHTER!

Hello Kitty runsok, but oddly Lego Worlds does not. I have all the content installed as before, but it just throws an error telling that: The app couldn't start. Try again from the Home menu

Anyone seen this before? It's new for me.

Thanks

 

[quincy uryuu]

Okay, I got it to work, but now I just get this error every time. Reading the other pages of this thread, I can see that someone else had a similar problem that was fixed by closing things that are attempting to use the drive, but nothing is using the drive right now for me. I assume I just messed up something, so I'm including a screenshot.

Can anyone help me with this?

Edit- Figured it out again. Turns out my 31gb partition wasn't actually big enough. It worked after I upped the partition to 32gb.

 

[Purevideo]

I don't know what I'm doing wrong, every time atmosphere boots, it shows error 2011 0301. I followed the Windows guide and have trierd to boot Emunand with and without 0x. Any ideas?

 

[NA29]

finally got this working! thanks for the guide. so, both my sysNAND and my emuNAND both can see the SD Card (the partition that wasn't used for the emuMMC copying) in Data Management. Is that supposed to happen? i'm pretty sure it worked since i have different themes on emu and sysnand and I deleted a game on emu that didn't delete on sys. And of course, emu says Atmosphere. I'm just concerned that if I install a game on the SD card on the emuNAND that this could show up on the sysNAND and end with me getting banned...

Edit: Oh...if I install games on my emuNAND will it go in the EmuNand folder? and then if I install games on my sysNAND it will go into the Nintendo folder? (I didn't touch the config file apart from the hexadecimal or add any folders, but those seem to have been created on my SD card after booting emuNAND and sysNAND...). And they won't detect games installed in those folders on the opposite nand?

 

[Xw2X]

No only with "stock" and bought games!
With Emunand you can play the other games in flightmode.

What is the difference between Emunand and just using atmosphere in term of playing online ? couldn't you play stock and bought games without emmunand anyways?

 

[TariqSoftDev]

I cant redump because it's my dump from 6.0 and I'm on 8.0.1 now

Well NAND dumps should be a 15 part dump if done with a FAT32 card or single rawnand file with exFAT

Something odd has happened. I reinstalled a couple of nsps (Hello Kitty Kruisers and Lego Worlds).

THEY ARE FOR MY DAUGHTER!

Hello Kitty runsok, but oddly Lego Worlds does not. I have all the content installed as before, but it just throws an error telling that: The app couldn't start. Try again from the Home menu

Anyone seen this before? It's new for me.

Thanks

Sigpatches?

Okay, I got it to work, but now I just get this error every time. Reading the other pages of this thread, I can see that someone else had a similar problem that was fixed by closing things that are attempting to use the drive, but nothing is using the drive right now for me. I assume I just messed up something, so I'm including a screenshot.

Can anyone help me with this?

Edit- Figured it out again. Turns out my 31gb partition wasn't actually big enough. It worked after I upped the partition to 32gb.

Check your single emummc is there and nothing is accessing the drive.

finally got this working! thanks for the guide. so, both my sysNAND and my emuNAND both can see the SD Card (the partition that wasn't used for the emuMMC copying) in Data Management. Is that supposed to happen? i'm pretty sure it worked since i have different themes on emu and sysnand and I deleted a game on emu that didn't delete on sys. And of course, emu says Atmosphere. I'm just concerned that if I install a game on the SD card on the emuNAND that this could show up on the sysNAND and end with me getting banned...

Edit: Oh...if I install games on my emuNAND will it go in the EmuNand folder? and then if I install games on my sysNAND it will go into the Nintendo folder? (I didn't touch the config file apart from the hexadecimal or add any folders, but those seem to have been created on my SD card after booting emuNAND and sysNAND...). And they won't detect games installed in those folders on the opposite nand?

They use the same SD but different "Nintendo" folder so yes installs are seperate.

I don't know what I'm doing wrong, every time atmosphere boots, it shows error 2011 0301. I followed the Windows guide and have trierd to boot Emunand with and without 0x. Any ideas?

This is a issue with fw below 4.x.x I believe, use a fw above that; keep your clean nand but create a updated version for EmuMMC.

 

[cots]

Well

No one is mentioning the emummc.kip file from m4xw's repo. Every guide I read just says to download and use Atmopshere. So what is the kip used for? Does Atmopshere have the emuMMC code in it that requires the external kip, because I checked the latest version of Atmopshere and it doesn't come with a kip. If it does require you to download the kip then why doesn't anyone mention this in any of their guides?

 

[TariqSoftDev]

No one is mentioning the emummc.kip file from m4xw's repo. Every guide I read just says to download and use Atmopshere. So what is the kip used for? Does Atmopshere have the emuMMC code in it that requires the external kip, because I checked the latest version of Atmopshere and it doesn't come with a kip. If it does require you to download the kip then why doesn't anyone mention this in any of their guides?

Check SD Files, has them attached; updating it soon for 8.1.0 compat and loose file EmuMMC; I'm leaving out the need for people to compile them else it's a shit fest.

 

[cots]

Check SD Files, has them attached; updating it soon for 8.1.0 compat and loose file EmuMMC; I'm leaving out the need for people to compile them else it's a shit fest.

Okay, what if I want to install it manually aka myself?

 

[TariqSoftDev]

Okay, what if I want to install it manually aka myself?

Compile it from m4xw's git, place in atmos.

 

[cots]

Compile it from m4xw's git, place in atmos.

Okay. So it is required for emuMMC to work properly. That's all I needed to know. Thanks!

 

[TariqSoftDev]

Okay. So it is required for emuMMC to work properly. That's all I needed to know. Thanks!

You need the EmuMMC kip module in atmos, else it's just norm atmos

 

[tabzer]

Something odd has happened. I reinstalled a couple of nsps (Hello Kitty Kruisers and Lego Worlds).

THEY ARE FOR MY DAUGHTER!

Hello Kitty runsok, but oddly Lego Worlds does not. I have all the content installed as before, but it just throws an error telling that: The app couldn't start. Try again from the Home menu

Anyone seen this before? It's new for me.

Thanks

If you are re-installing nsps, it's best to delete the old record from the system/data management first, or else you'll run into these issues.