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:

 

[thaikhoa]

If anyone has programming ability and compile this tool, it'd help a lot for unexperienced users.

https://github.com/dimok789/sdio_nand_manager

 

[TariqSoftDev]

If anyone has programming ability and compile this tool, it'd help a lot for unexperienced users.

https://github.com/dimok789/sdio_nand_manager

Releases > Already compiled.

 

[thaikhoa]

Releases > Already compiled.

It's for Wii U Rednand. Sectors should be modified and removed some unused parts to work on EmuMMC partition.

 

[RyanfromWork]

I got it to start working. Unfortunately, I have no idea how. Could be the 0.9.1 update?

Regardless, its running "my" 7.0.1 (ams 0.9.1) with all games working.

Thank You for your excellent guide and the Genius's who made this guide possible.


But side question, since my clean backup was from 4.0.1.... I have 7 burnt fuses. What do I do??

 

[tabzer]

I update my emummc FW and now it doesn't work

 

[RyanfromWork]

I update my emummc FW and now it doesn't work

Its a benefit of emunand. As in rinse and repeat the process like if u picked up a new SD card

 

[eyeliner]

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.

Thanks friend. I believe I did that already. But I can redo those steps.

 

[tabzer]

How is emummc breaking on a fw update a benefit? I can do what you said anyway.

My concern is that when I want to update emummc, I'll have to reclone my NAND, rewrite tht into my emu space, and then redo all the things I had customized for the previous emummc.

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

Its a benefit of emunand. As in rinse and repeat the process like if u picked up a new SD card

See above.

 

[thaikhoa]

emummc shouldn't be any issue on the latest fixed build of Atm 0.9.1 on firmware 8.1 (updated using choinx on the emummc itself). Don't do Switch memory card format or windows format function by default. You guys should use Mini Tool Partition to format the SD.

 

[tabzer]

emummc shouldn't be any issue on the latest fixed build of Atm 0.9.1 on firmware 8.1 (updated using choinx on the emummc itself). Don't do Switch memory card format or windows format function by default. You guys should use Mini Tool Partition to format the SD.

I updated the emummc with choinx and it prevented emummc from booting. Black screen no switch logo after atmo logo disappeared. I was already updated to atmo 0.9.1 so I don't know what could have went wrong.

 

[Purevideo]

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.

Well my firmware is 4.0.1, the weird thing is that I have used atmosphere before (8.10 I think it was) without a problem, maybe there was an error while creating emunand?

 

[thaikhoa]

I updated the emummc with choinx and it prevented emummc from booting. Black screen no switch logo after atmo logo disappeared. I was already updated to atmo 0.9.1 so I don't know what could have went wrong.

Open your SD drive using HxD (run it under Administrator) Tools > Open disk. Check on the boot0 sector (the starting sector when you set it in emummc_sector) and compare to the actual boot0 if it's there in the partition.

 

[tabzer]

I can't check now, but would the difference be caused by enabling fuse-protection when upgrading?

 

[thaikhoa]

I can't check now, but would the difference be caused by enabling fuse-protection when upgrading?

Idk. I'm using SX Emunand to run Atm Emummc and updated fw on Atm Emummc.
Next time, you should turn off the fuse-protection when updating firnware on Emunand. It doesn't affect to the Sysnand (the OFW) but the Emunand itself.

fyi, reinject boot0 and boot1 to the emummc partition if it will work (boot0 and boot1 of firmware 8.1) or you just disable all the custom sysmodule kips in atmosphere/titles folder. emuiibo causes the issue for me, at least.

 

[RyanfromWork]

How is emummc breaking on a fw update a benefit? I can do what you said anyway.

My concern is that when I want to update emummc, I'll have to reclone my NAND, rewrite tht into my emu space, and then redo all the things I had customized for the previous emummc.

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



See above.

Never said it’s a benefit for anything to be “updated” and break. I mean really?? Breaking = benefit. Nope.

the benefit im referring to is that emunand can be recreated over and over and over again.

I’d rather mess around and screw up in emunand than in sysnand.


atmosphere released 0.9.1 which covers Nintendo’s 8.1.0. I would say the only option you have is to rinse and repeat....

 

[alimao]

https://github.com/exelix11/MakeEmu simple tool

 

[TariqSoftDev]

Well my firmware is 4.0.1, the weird thing is that I have used atmosphere before (8.10 I think it was) without a problem, maybe there was an error while creating emunand?

EmuMMC driver, offsets are different when programming for different FW, this is still FS redirection approach not EL2 so the fw has to be supported via EmuMMC

I can't check now, but would the difference be caused by enabling fuse-protection when upgrading?

Update the EmuMMC driver, I updated the SD files for it, it's not atmosphere rather the EmuMMC driver but it's been updated alongside the threads SD Files.

 

[Purevideo]

EmuMMC driver, offsets are different when programming for different FW, this is still FS redirection approach not EL2 so the fw has to be supported via EmuMMC

So the only thing that I could do is to update without burning fuses (I saw a guide here) to say, 7.xx and run emunand from there, right?

 

[TariqSoftDev]

So the only thing that I could do is to update without burning fuses (I saw a guide here) to say, 7.xx and run emunand from there, right?

Backup stock clean nand, using atmos on Sys update to 7.xx via ChoiNX in Atmos CFW, dump that nand and use it for EmuMMC then restore your sys to the stock clean; that way you won't burn any fuses.

 

[thaikhoa]

Backup stock clean nand, using atmos on Sys update to 7.xx via ChoiNX in Atmos CFW, dump that nand and use it for EmuMMC then restore your sys to the stock clean; that way you won't burn any fuses.

Might I ask, what's exact purpose of the emummc driver? Emummc 8.1 works out of the box with Atmosphere 0.9.1 without an issue for me.