How to setup Atmosphere EmuMMC

Krayziezay13 · Aug 3, 2019

lordelan said:
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.

Any reason why I click boot into normal CFW and it doesnt boot but if I boot normal CFW is sx it does it
Also when I boot into atmos emummc the serial number is gone does that mean jts cfw and not normal

lordelan · Aug 3, 2019

Krayziezay13 said:
Any reason why I click boot into normal CFW and it doesnt boot but if I boot normal CFW is sx it does it
Also when I boot into atmos emummc the serial number is gone does that mean jts cfw and not normal

Sounds strange to me. You can always look in system settings at your firmware version and if it's Atmosphère it should stand there next to it.

Krayziezay13 · Aug 3, 2019

lordelan said:
Sounds strange to me. You can always look in system settings at your firmware version and if it's Atmosphère it should stand there next to it.

Ok yea it does AMS next to the firmware version

Powerful · Aug 4, 2019

lordelan said:
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.

I fixed it, the hekate.ini didn’t match as you had SX_OS and mine was just sxos. I changed mine to match, so problem solved.

Krayziezay13 · Aug 12, 2019

Well im back and I just found out that Im not running emummc its just regular atmosphere any ideas on how to fix it. Does it supposed to have the letter E at the end of it

Krayziezay13 · Aug 13, 2019

Powerful said:
I fixed it, the hekate.ini didn’t match as you had SX_OS and mine was just sxos. I changed mine to match, so problem solved.

Does your atmosphere have an E and the end or does it just say the regular build under system information

stick267 · Aug 13, 2019

Krayziezay13 said:
Well im back and I just found out that Im not running emummc its just regular atmosphere any ideas on how to fix it. Does it supposed to have the letter E at the end of it

The letter E at the end of your version means that you are currently in emummc.

Krayziezay13 · Aug 13, 2019

stick267 said:
The letter E at the end of your version means that you are currently in emummc.

But doesn't this tutorial allow you to run both sx emunand and atmos emummc

lordelan · Aug 13, 2019

Krayziezay13 said:
But doesn't this tutorial allow you to run both sx emunand and atmos emummc

Yes.
Atmo + emuMMC -> E at version end
SX + emuMMC -> SX rommenu shows up by accessing album applet

Krayziezay13 · Aug 13, 2019

lordelan said:
Yes.
Atmo + emuMMC -> E at version end
SX + emuMMC -> SX rommenu shows up by accessing album applet

Ok well I mustve done something wrong again because when i boot into whats supposed to be atmos emummc it boots into regular atmos

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

Is there anything I can upload that you can take a look at to see where I mightve messed up at

lordelan · Aug 13, 2019

Krayziezay13 said:
Ok well I mustve done something wrong again because when i boot into whats supposed to be atmos emummc it boots into regular atmos

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

Is there anything I can upload that you can take a look at to see where I mightve messed up at

Did not follow your discussion here but to have one emuNAND working in both custom firmwares, you have to create it with SX OS (emuNAND partition based) and create this file:

sd:\emuMMC\emummc.ini

with the following content:

Code:

[emummc]
enabled = 1
sector = 0x2
nintendo_path = Emutendo

Given the fact that you use most recent Atmos and hekate (KOSMOS) of course.
If you want to use your installed sysNAND games in the newly created emuNAND, rename
sd:\Nintendo
to
sd:\Emutendo before your first emuMMC boot.

You can also have a look at my guide. Although it covers Ubuntu as well, it's good nevertheless to get to know how to setup an emuMMC for both CFWs:
https://gbatemp.net/threads/partition-based-emummc-and-l4t-ubuntu-on-the-same-sd-card.543956/
Also take a loot into my hekate_ipl.ini there.

Krayziezay13 · Aug 13, 2019

lordelan said:
Did not follow your discussion here but to have one emuNAND working in both custom firmwares, you have to create it with SX OS (emuNAND partition based) and create this file:

sd:\emuMMC\emummc.ini

with the following content:

Code:

[emummc] enabled = 1 sector = 0x2 nintendo_path = Emutendo

Given the fact that you use most recent Atmos and hekate (KOSMOS) of course.
If you want to use your installed sysNAND games in the newly created emuNAND, rename
sd:\Nintendo
to
sd:\Emutendo before your first emuMMC boot.

You can also have a look at my guide. Although it covers Ubuntu as well, it's good nevertheless to get to know how to setup an emuMMC for both CFWs:
https://gbatemp.net/threads/partition-based-emummc-and-l4t-ubuntu-on-the-same-sd-card.543956/
Also take a loot into my hekate_ipl.ini there.

well I already have emmunand partition based set up using sx os that's my main CFW as I started out with SX but I think it may have something to do with the emummc.ini file as when I saved the file the name I put it under was emummc.ini and once I boot into atmos Emmu the screen just goes black and that's it

lordelan · Aug 13, 2019

Krayziezay13 said:
well I already have emmunand partition based set up using sx os that's my main CFW as I started out with SX but I think it may have something to do with the emummc.ini file as when I saved the file the name I put it under was emummc.ini and once I boot into atmos Emmu the screen just goes black and that's it

So you never succeeded in booting into your emuNAND with Atmos?
If so and if you can already use it with SX OS, just delete your sd:\emuMMC\ folder.
Then create it freshly, put in a emummc.ini with the content I posted above and be sure to have such an entry somewhere in your sd:\bootloader\hekate_ipl.ini:

Code:

[CFW (EMUMMC)]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

Krayziezay13 · Aug 13, 2019

lordelan said:
So you never succeeded in booting into your emuNAND with Atmos?
If so and if you can already use it with SX OS, just delete your sd:\emuMMC\ folder.
Then create it freshly, put in a emummc.ini with the content I posted above and be sure to have such an entry somewhere in your sd:\bootloader\hekate_ipl.ini:

Code:

[CFW (EMUMMC)] fss0=atmosphere/fusee-secondary.bin kip1patch=nosigchk atmosphere=1 logopath=bootloader/bootlogo.bmp icon=bootloader/res/icon_payload.bmp {}

Ok Ill try that and correct I can boot into emmunand with sx fine but when I try to boot into emmuNAND with Atmos it just boots into regular Atmos without the E at the end

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

this is what I have and its still not working

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

this is what I have and its still not working

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

https://i.imgur.com/HzEQ4cA_d.jpg?maxwidth=640&shape=thumb&fidelity=medium

lordelan · Aug 14, 2019

Krayziezay13 said:
Ok Ill try that and correct I can boot into emmunand with sx fine but when I try to boot into emmuNAND with Atmos it just boots into regular Atmos without the E at the end

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

this is what I have and its still not working

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

this is what I have and its still not working

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

https://i.imgur.com/HzEQ4cA_d.jpg?maxwidth=640&shape=thumb&fidelity=medium

Umm, are you sure that it's not the emuNAND? Never looked for that "E" at the end tbh.
Try changing the menu theme from black to white in SX emuNAND, then boot into Atmos emuNAND and see if it's white or black to be complete sure.

If you put the card in your PC, hit WINDOWS+R and enter diskmgmt.msc, what does it show you?
Should be 29.1 GB unallocated space and a FAT32 partition afterwards, correct?

Krayziezay13 · Aug 14, 2019

lordelan said:
Umm, are you sure that it's not the emuNAND? Never looked for that "E" at the end tbh.
Try changing the menu theme from black to white in SX emuNAND, then boot into Atmos emuNAND and see if it's white or black to be complete sure.

If you put the card in your PC, hit WINDOWS+R and enter diskmgmt.msc, what does it show you?
Should be 29.1 GB unallocated space and a FAT32 partition afterwards, correct?

Yes it does say 29.1 unallocated and when I changed the theme from black to white on sx emunand atmosphere also changed from black to white. I thought I read somewhere that you should see an E at the end for the emuMMC with atmos maybe its only when your using atmosphere emuMMC by itself

ColinMacLaren · Aug 15, 2019

I have SXOS on hidden partition. I installed AtlasNX alongside, following this guide.
Everything is working fine, except my games.

I dumped my games in SX OS with SX dumper to XCI, then installed them to the SD Card with SX Installer. When trying to run the games in atmosphere I recieve "An error has occured" a couple of seconds after starting the game.

wikdclown · Aug 22, 2019

If using emunand can I boot into ofw and download purchased games and restore saves with minimal risk of being banned? Or do you have to reflash the clean nand back?
It's a virgin switch that has never had hacks on it and has clean nand.

lordelan · Aug 23, 2019

wikdclown said:
It's a virgin switch that has never had hacks on it and has clean nand.

On a virgin Switch:
Make a NAND backup (just in case). Create emuNAND. Use hekate to boot into stock sysNAND or CFW emuNAND.
Use sysNAND to play online with legit games. Use emuNAND for anything else.

Edit: Obviously keep emuNAND offline or use 90DNS or incognito.

wasney · Sep 12, 2019

Hey there, wondering if you can pass on some advice. Following your posts I've gotten it to the point I can open my SXOS emunand in Atmosphere, but like Colin above I can't open stuff. I also noticed the replacer shortcuts aren't working either, so I can't get into any Homebrew, which is the whole reason I wanted atmosphere since I want to backup my saves to switch to a larger SD card.

Any tips?

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Attachments

Well-Known Member

Well-Known Member

Member

Active Member

Well-Known Member

New Member

Similar threads

Popular threads in this forum