The tutorial is more like

Setup EmuMMC, From SX to Atmosphere and keep using the both worlds.

If the moderator by any chance to come here, could you please change the title? Thanks.


YOU HAVE BEEN WARNED

There is always at least a risk to get you banned or unlikely to brick your Switch.
YOU'RE AT YOUR OWN RISK
I TAKE NO RESPONSIBILITY FOR ANY DAMAGES OR BAN.

You can use your current setup of SX's Emunand (hidden partition on the SD) to boot Atmosphere's Emummc using this tutorial. This will be considered as dual emunand booting. Take advantage of the both worlds.

CLEAN UP SYSNAND
> Skip this step if you're using SX's Emunand and being online on Sysnand.
> If you didn't have any previous clean nand backup before
You have no choice here to clean up a dirty nand without a clean nand backup but to believe in this method
> Stop here if you don't want to hurt yourself or even me
​

Spoiler: PRESS

Skip this step if your Switch is a brand new one or never ever been hacked.

​

Spoiler: PRESS

Access NAND using PC

What you will need
- biskeydump
https://files.sshnuke.net/biskeydumpv8.zip
Run the payload and write down (or scan QRCode) Bis Key 2
BIS KEY 2 (crypt): NUMBERS
BIS KEY 2 (tweak): NUMBERS

- memloader
https://files.sshnuke.net/memloaderv2.zip
Copy *.* in [sample] folder to SD and plug it in the Switch
Run the payload [memloader.bin]
Unplug any USB cable
> Choose emmc line
> Plug USB C <> USB A cable to the Switch and PC

- HacDiskMount
https://files.sshnuke.net/HacDiskMount1055.zip
Run the tool under Administrator permission
> Open Physical Disk > Choose Linux line
> Double click on SYSTEM and fill BisKeys2 in the small table on top
Crysto > BIS KEY 2 (crypt): NUMBERS
Tweak > BIS KEY 2 (tweak): NUMBERS
> Press on [Test] > you will get OK! Entropy
> From Drive Letter table > Choose a drive disk, N for example.
> Press on [Mount]
Install driver if needed.
Acess N drive from My Computer
> access save folder
> delete all files inside the save folder except 8000000000000120
> Press on [Unmount]

> Double click on USER and fill BisKeys3 in the small table on top
Crysto > BIS KEY 3 (crypt): NUMBERS
Tweak > BIS KEY 3 (tweak): NUMBERS
> Press on [Test] > you will get OK! Entropy
> From Drive Letter table > Choose a drive disk, N for example.
> Press on [Mount]
Install driver if needed.
Acess N drive from My Computer and Delete Everything
> Press on [Unmount] and unplug the USB cable

> Press on [Power] button for 15s or so to reboot the system​

> After rebooting, the system will be in initial setup stage.
​

CREATE EMUNAND AS HIDDEN PARTITION ON SD
> If you're SX Users and have been using their Emunand as hidden partition, just skip this step, go to COPY FILES
> Take advantage of SX Emunand creator (without valid license needed)
> Your SD will be formatted, backup your savedata and other data are needed.

Spoiler: PRESS

Before creating emunand > Ensure you did delete all WIFI connections and turned on Airplane / Flight mode

Go to SX website > download their latest boot.dat > copy to the root of your SD
Download payload.bin for activating payload via your chosen tools

SX OS Bootloader Menu
> Options
> EmuNAND
> Create EmuNAND
> Hidden Partition on microSD

You will get "successfully done"

COPY FILES

Spoiler: PRESS

Go to Atmosphere GitHub and download the latest release 0.9.0 and extract all files/ folders to the root of your SD

Create > emummc folder on the root of the SD

Create > emummc.ini file inside of emummc folder

Copy and paste this to emummc.ini

[emummc]
emummc_enabled = 1
emummc_sector = 0x2
emummc_nintendo_path = Emutendo <<< delete this line if you're not SX Users or don't want to keep using SX as your primary CFW

I got banned from ReSwitched discord because of Emutendo word. I'd like to help someone out but ended up in unexpected way. But it's okay.

Hope this will help out.
Enjoy!

 

[lordelan]

Ok thanks and once I do that would my seitch boot directly into atmos or would I still need the payload because I use sx

Did you create your emuNAND with SX OS? Partition based?
Then look at the end of the first post here to find what to put inside the emummc.ini in order to launch the SX OS emuNAND from hekate/Atmo as well:
https://gbatemp.net/threads/partition-based-emummc-and-l4t-ubuntu-on-the-same-sd-card.543956

And DON'T use the migrate feature in hekate.
Just create your emuNAND with SX OS, adjust the ini as said above and it will just work when booting into it from hekate.
I'm using mine from SX OS and Atmo and it's working just fine.

 

[Krayziezay13]

Did you create your emuNAND with SX OS? Partition based?
Then look at the end of the first post here to find what to put inside the emummc.ini in order to launch the SX OS emuNAND from hekate/Atmo as well:
https://gbatemp.net/threads/partition-based-emummc-and-l4t-ubuntu-on-the-same-sd-card.543956

Yes its created partitioned base

 

[lordelan]

Yes its created partitioned base

See my edit.

 

[Krayziezay13]

See my edit.

Ok about to look at it now

 

[Krayziezay13]

See my edit.

So All I have to do is just put that code into the .ini and then add the atmosphere files on my sd card and that's it Ill be able to run both with no issue sorry for acting like a dunce

 

[lordelan]

So All I have to do is just put that code into the .ini and then add the atmosphere files on my sd card and that's it Ill be able to run both with no issue sorry for acting like a dunce

Don't worry. Better ask twice.
Atmosphère alone won't be enough I guess. Go with KOSMOS. It includes Hekate 5.x + NYX which should already have a launch icon under the LAUNCH menu to get into eMMC with CFW (which would be Atmospère in this case).
If you want to add SX OS to hekate as well, download their payload.bin (here), rename it to sxos.bin and place it here:
sd:\bootloader\payloads\

Then add this section to your sd:\bootloader\hekate_ipl.ini:

[SX OS]
payload=bootloader/payloads/sxos.bin

 

[Krayziezay13]

Don't worry. Better ask twice.
Atmosphère alone won't be enough I guess. Go with KOSMOS. It includes Hekate 5.x + NYX which should already have a launch icon under the LAUNCH menu to get into eMMC with CFW (which would be Atmospère in this case).
If you want to add SX OS to hekate as well, download their payload.bin (here), rename it to sxos.bin and place it here:
sd:\bootloader\payloads\

Then add this section to your sd:\bootloader\hekate_ipl.ini:

[SX OS]
payload=bootloader/payloads/sxos.bin

Ok so let me make sure I did it correct I placed the atmos folder, switch, sept, and hbmenu.nro, emummc, and fuse primary bin all on the root of my sd card. Then do I turn on my switch which will go to the sx screen since Im running sx emmunand and the do I hit options or do I hit boot into custom FW? If I boot into custom FW do I click reboot to payload?

 

[lordelan]

Ok so let me make sure I did it correct I placed the atmos folder, switch, sept, and hbmenu.nro, emummc, and fuse primary bin all on the root of my sd card. Then do I turn on my switch which will go to the sx screen since Im running sx emmunand and the do I hit options or do I hit boot into custom FW? If I boot into custom FW do I click reboot to payload?

Did you use KOSMOS as I told you? There should be a bootloader folder as well. Also a hekate payload which you should use as your default payload as you can boot into SX OS from within hekate if you add it to the ini as I wrote above.

But in SX OS bootmenu (hold VOL+ on boot to get there while launching SX OS) you should make sure that it says "emuNAND enabled" at the top left.

Then you do what I wrote and basically use hekate to launch everything:
- sysNAND (with no CFW to play online)
- emuMMC CFW (emuNAND with Atmosphère)
- SX OS (emuNAND with SX OS to enjoy your external HDD)
- sysNAND CFW (in case you would want to backup some savegames with Checkpoint)

 

[Krayziezay13]

Did you use KOSMOS as I told you? There should be a bootloader folder as well. Also a hekate payload which you should use as your default payload as you can boot into SX OS from within hekate if you add it to the ini as I wrote above.

But in SX OS bootmenu (hold VOL+ on boot to get there while launching SX OS) you should make sure that it says "emuNAND enabled" at the top left.

Then you do what I wrote and basically use hekate to launch everything:
- sysNAND (with no CFW to play online)
- emuMMC CFW (emuNAND with Atmosphère)
- SX OS (emuNAND with SX OS to enjoy your external HDD)
- sysNAND CFW (in case you would want to backup some savegames with Checkpoint)

Nope Im missing the bootloader folder and where would I find KOSMOS

 

[lordelan]

Nope Im missing the bootloader folder and where would I find KOSMOS

https://github.com/AtlasNX/Kosmos/releases/tag/v13.0.3

Be sure to get the sig patches as well. Either from there or if you need the hbg shop as well, then take the acid patches from here:
https://gbatemp.net/threads/kosmos-patches-es-fs.542455/

 

[Krayziezay13]

https://github.com/AtlasNX/Kosmos/releases/tag/v13.0.3

Be sure to get the sig patches as well. Either from there or if you need the hbg shop as well, then take the acid patches from here:
https://gbatemp.net/threads/kosmos-patches-es-fs.542455/

Ok now I got the screen to where I can choose between anything with hekate now I just gotta add sx back so that I can boot into sx if I need to. If I boot into emuMMC will my games from sx automatically move over also if I boot into emuMMC how would it take to start. I hit emuMMC but nothing happened at all just a blank screen

 

[Krayziezay13]

Also if there is a way I can send you the folders that I have or a screenshot of what's in it maybe thatll help out as well

 

[Krayziezay13]

Ok I think I finally got it to work it had something to do with the emummc.ini I guess I opened the wrong text editor. I booted Atmos but how do I know for sure that its the emunand version of atmos

 

[switchalex]

https://github.com/AtlasNX/Kosmos/releases/tag/v13.0.3

Be sure to get the sig patches as well. Either from there or if you need the hbg shop as well, then take the acid patches from here:
https://gbatemp.net/threads/kosmos-patches-es-fs.542455/

Sorry to bother you, I’m looking to move from Sx to atmo, I’m only going to bring save files over and just use nsp’s and emmu of atmosphere , do I just need too :

1: Use Sx Os to delete current emmunand , then format sd after moving what im taking from it

2: follow this guide to install atmo https://gbatemp.net/threads/tutorial-from-sx-os-to-atmosphere.533337/

3: Create a new emmu with atmosphere

4: Happy times? I’m cautious about potential conflicts I may not know about so wanted to clarify this is how to cleanly transition

 

[lordelan]

Sorry to bother you, I’m looking to move from Sx to atmo, I’m only going to bring save files over and just use nsp’s and emmu of atmosphere , do I just need too :

1: Use Sx Os to delete current emmunand , then format sd after moving what im taking from it

2: follow this guide to install atmo https://gbatemp.net/threads/tutorial-from-sx-os-to-atmosphere.533337/

3: Create a new emmu with atmosphere

4: Happy times? I’m cautious about potential conflicts I may not know about so wanted to clarify this is how to cleanly transition

When "moving" over from SX OS to Atmo you literally just put KOSMOS and the patches I linked on the SD and use the included hekate hekate payload. Be sure to adjust the sd:\emuMMC\emummc.ini just as I wrote so it points to the emuNAND that SX OS created. You can use that one in Atmo and don't need to delete it.

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

Ok I think I finally got it to work it had something to do with the emummc.ini I guess I opened the wrong text editor. I booted Atmos but how do I know for sure that its the emunand version of atmos

Safest thing is to boot sysNAND (from hekate payload) and change theme to white. Then boot emuNAND and change theme to black so you know in which you are currently.

 

[Krayziezay13]

When "moving" over from SX OS to Atmo you literally just put KOSMOS and the patches I linked on the SD and use the included hekate hekate payload. Be sure to adjust the sd:\emuMMC\emummc.ini just as I wrote so it points to the emuNAND that SX OS created. You can use that one in Atmo and don't need to delete it.

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


Safest thing is to boot sysNAND (from hekate payload) and change theme to white. Then boot emuNAND and change theme to black so you know in which you are currently.

I hit boot Stock (SYSNAND) for hekate and the switch does nothing but cut off but when I choose the atmos emummc it boots and when I go to look for the serial information it doesn't show my serial number so I guess its still in incognito mode

 

[Powerful]

Don't worry. Better ask twice.
Atmosphère alone won't be enough I guess. Go with KOSMOS. It includes Hekate 5.x + NYX which should already have a launch icon under the LAUNCH menu to get into eMMC with CFW (which would be Atmospère in this case).
If you want to add SX OS to hekate as well, download their payload.bin (here), rename it to sxos.bin and place it here:
sd:\bootloader\payloads\

Then add this section to your sd:\bootloader\hekate_ipl.ini:

[SX OS]
payload=bootloader/payloads/sxos.bin

One question, I setup mine the exact same. Only thing is when I click launch then sx os it reboots to hekate. If I go to payloads it’ll boot proper though. Atmosphere launches through the launch menu, and so does emummc linked to Emutendo. Only thing that doesn’t work is sx os. How do I fix this?

 

[lordelan]

One question, I setup mine the exact same. Only thing is when I click launch then sx os it reboots to hekate. If I go to payloads it’ll boot proper though. Atmosphere launches through the launch menu, and so does emummc linked to Emutendo. Only thing that doesn’t work is sx os. How do I fix this?

You've got an SX OS licence, right?
Then basically all you do is download the most recent SX OS beta from here (which is a boot.dat) and the SX Loader (which is a payload.bin):
https://sx.xecuter.com
The boot.dat goes to your SD root, the payload.bin goes to sd:\bootloader\payloads\ and there renamed to sxos.bin

If it reboots to hekate, most likely your sxos.bin is not named correctly or it is spelled wrong in your hekate_ipl.ini so post that one here please so I can have a look if it's still not working.

 

[Powerful]

You've got an SX OS licence, right?
Then basically all you do is download the most recent SX OS beta from here (which is a boot.dat) and the SX Loader (which is a payload.bin):
https://sx.xecuter.com
The boot.dat goes to your SD root, the payload.bin goes to sd:\bootloader\payloads\ and there renamed to sxos.bin

If it reboots to hekate, most likely your sxos.bin is not named correctly or it is spelled wrong in your hekate_ipl.ini so post that one here please so I can have a look if it's still not working.

Yeah I have the license on the newest version. I have all that setup properly. Renamed it only in payloads. I copied your custom hekate.ini from your post, so I am not too sure on that.

 

[lordelan]

Yeah I have the license on the newest version. I have all that setup properly. Renamed it only in payloads. I copied your custom hekate.ini from your post, so I am not too sure on that.

Tell me the exact name of the sxos payload in sd:\bootloader\payloads\
and then post the content of the sd:\bootloader\hekate_ipl.ini here in SPOILER and CODE tags.