Today's the big day! Atmosphère, the Nintendo Switch CFW made by @SciresM and his team, has reached a new milestone, thus marking the release of version 0.9.0!

A few improvements were made to creport and dmnt's cheat virtual machine, adding more detailed output and 32-bit game support for the former and a new debug opcode for the latter, however, most users will be excited to know that a highly anticipated feature has finally been included: we're talking about emuMMC, of course! This has been possible thanks to a collaboration between @SciresM, @_hexkyz_, @m4xw and @CTCaer and it's the first publicly available free and open source implementation of NAND redirection for the Switch. Atmosphère's emuMMC can be enabled by editing the file emummc\emummc.ini and setting "emummc_enabled" under its relative section to 1. The feature is able to redirect reads and writes to either a separate partition on the card (recommended) or loose files in a directory with the archive bit set: in order to choose one of the two, you have to set either "emummc_sector" or "emummc_path" to a valid value (read the changelog for more information). By default, emuMMC will use a different Nintendo folder called "Nintendo_<emummc_id>", however, you can choose whichever directory you like by setting "emummc_nintendo_path" to your desired one.

While the current implementation is in a working state, the developers stress it should still be considered an experimental feature; as such, users who want to set emuMMC as their main boot option are advised to wait until any eventual bugs are fixed in the next update. Some planned features are also currently not included, for example having a separate atmosphere folder for each emuMMC.

The official changelog is as follows:

0.9.0 is Atmosphère's eighteenth official release.

fusee-primary was last updated in: 0.9.0.

With thanks to the @switchbrew team, Atmosphère 0.9.0 is bundled with hbl 2.1, and hbmenu 3.0.1.

The following was changed since the last release:

• Creport output was improved significantly.
  • Thread names are now dumped on crash in addition to 0x100 of TLS from each thread.
    • This significantly aids debugging efforts for crashes.
  • Support was added for 32-bit stackframes, so reports can now be generated for 32-bit games.
• dmnt's Cheat VM was extended to add a new debug opcode.
• With thanks to/collaboration with @m4xw and @CTCaer, support was added for redirecting NAND to the SD card (emummc).
  • Please note, this support is very much beta/experimental.
    • It is quite likely we have not identified all bugs -- those will be fixed as they are reported over the next few days/weeks.
    • In addition, some niceties (e.g. having a separate Atmosphere folder per emummc instance) still need some thought put in before they can be implemented in a way that makes everyone happy.
    • If you are not an advanced user, you may wish to think about waiting for the inevitable 0.9.1 bugfix update before using emummc as your default boot option.
      • You may especially wish to consider waiting if you are using Atmosphere on a unit with the RCM bug patched.
  • Emummc is managed by editing the emummc section of "emummc/emummc.ini".
    • To enable emummc, set emummc!emummc_enabled = 1.
  • Support is included for redirecting NAND to a partition on the SD card.
    • This can be done by setting emummc!emummc_sector to the start sector of your partition (e.g., emummc_sector = 0x1A010000).
  • Support is also included for redirecting NAND to a collection of loose files on the SD card.
    • This can be done by setting emummc!emummc_path to the folder (with archive bit set) containing the NAND boot partitions' files "boot0" and "boot1", and the raw NAND image files "00", "01", "02", etc. (single "00" file with the whole NAND image requires exFAT mode while multipart NAND can be used in both exFAT and FAT32 modes).
  • The Nintendo contents directory can be redirected arbitrarily.
    • By default, it will be redirected to emummc/Nintendo_XXXX, where XXXX is the hexadecimal representation of the emummc's ID.
      • The current emummc ID may be selected by changing emummc!emummc_id in emummc.ini.
    • This can be set to any arbitrary directory by setting emummc!emummc_nintendo_path.
  • To create a backup usable for emummc, users may use tools provided by the hekate project.
  • If, when using emummc, you encounter a bug, please be sure to report it -- that's the only way we can fix it.
• General system stability improvements to enhance the user's experience.

For information on the featureset supported by 0.9.0, please see the official release notes.

A reminder for people new to Switch hacking: emuNAND/emuMMC will not help if your console is banned, has been flagged by Nintendo or if your NAND has been "tainted" by running CFW/homebrew and you don't have a clean backup. All currently available implementations are preventive measures which let you have a clean system partition that you can use with your legit games online (no homebrew or game backups) and another separate one (the emuNAND/emuMMC itself) on which you can run everything else offline without fearing a ban. The latter is created from a copy of your Switch's internal memory: as such it will not let you evade a ban, nor clear any modifications or error logs made by homebrew apps.

For user support or bug reports, please use the GBAtemp thread linked below.

Source
GBAtemp thread

 

[Chocola]

What a complete load of garbage. All this post has done is made you look like one of those pathetic little fan boys that pop up on various forums spouting nonsense just because they prefer one product over another.

Both SX OS and Atmosphere are good and they both have their pros and cons.
Some people prefer XCI over NSP, it depends how the end user decides to setup their switch.

I am sorry that $35 is a lot of money for you so you cannot draw up a fair unbiased comparison but that doesn't excuse trying to derail a thread at the earliest opportunity. It's also pretty lame trying to argue one is better than the other because one uses illegal files and the other doesn't when your switch is undoubtedly full of illegal games which you didn't purchase.

10 years ago trolls like this weren't around on gbatemp, it was all about community. Nobody was really bothered about one solution over another instead they worked towards a common goal. Unfortunately over time a lot of communities have been filling up with trolls like this one and it's a shame

The 35$ isn't the cons for SX OS (it's cheap, they didn't should ask for money for this things but isn't the unic team that do this...), I have money to pay their crapy license, but didn't like closed source things from unknown teams or developers that didn't know that they do with my devices or data.

Both are good because SX OS it's based on Atmosphére, and have a bit features because they don't need to work on firmware compatibility, they let atmosphére work on these things and expend their time on they own mods.

When SX OS release the emunand feature the SX OS users talk about Atmosphere/ReiNX users because we don't have the emunand and they yes, the war of consoles / firmwares are pathetic but he just share his comparison and opinion without disrespect.

 

[MSearles]

I'm an SX OS user from when it was first released. How easy is atmosphere to use? With SX OS. You just plug in the dongle with a jig and hold two buttons to power on. As long as you keep it in sleep mode. It'll always be in CFW

 

[Chocola]

I'm an SX OS user from when it was first released. How easy is atmosphere to use? With SX OS. You just plug in the dongle with a jig and hold two buttons to power on. As long as you keep it in sleep mode. It'll always be in CFW

It's the same, just inject hekate or fuseé and enjoy, if you didn't turn your console off (only use sleep mode) you don't need do anything, I have mine more than 2 weeks without reboot with atmosphére.

 

[Adran_Marit]

Just a thought, since this emummc/emunand relies on a clean nand backup flashed to a partition to run the cfw on, even if it is emulated it still has your cert attached yea because it is part of the nand backup?

 

[Chocola]

Just a thought, since this emummc/emunand relies on a clean nand backup flashed to a partition to run the cfw on, even if it is emulated it still has your cert attached yea because it is part of the nand backup?

Yup, it's a 100% copy of your sysnand, so if you like trim some data (like cert or id's) you should do manually, there are a PR of prodinfo fake emulation on atmosphére but isn't merged for now and are WIP (need check more partitions when the Switch store identificable datas).

If you don't modify your emummc data, you have the same risk comming online and affect aswell to the online services of your sysnand too (it's a server ban).

 

[Ev1l0rd]

Just a thought, since this emummc/emunand relies on a clean nand backup flashed to a partition to run the cfw on, even if it is emulated it still has your cert attached yea because it is part of the nand backup?

Correct but there's an open PR that blanks PRODINFO through mitming it that I personally expect to be merged soon and that will probably be able to be enabled for emuMMC.

 

[spotanjo3]

Awesome. Now, how do you use emuMMC?

 

[Adran_Marit]

Yup, it's a 100% copy of your sysnand, so if you like trim some data (like cert or id's) you should do manually, there are a PR of prodinfo fake emulation on atmosphére but isn't merged for now and are WIP (need check more partitions when the Switch store identificable datas).

If you don't modify your emummc data, you have the same risk comming online and affect aswell to the online services of your sysnand too (it's a server ban).

Correct but there's an open PR that blanks PRODINFO through mitming it that I personally expect to be merged soon and that will probably be able to be enabled for emuMMC.

Meaning that the current build and online play is just as likely to get you banned as not. and if you blank your prod info you cant connect to servers iirc so whats the point?

 

[MSearles]

If I wanted to switch over my XCI's to NSP's, could I do so and still have my save files intact?

 

[Zumoly]

For this version its absolutely recommended to use partition based instead of file based (due to some unmounting/buffering issues).
Anyway, hekate (which will also be used as a setup utility), got delayed because of some other bugs of new features...
We spent the last 40+h on it, it's 7am now and we just have to call it a day, but we will soon release the setup utilities etc!

I can definitely say that the team outdid itself to deliver on June 15.

 

[Wednesday101]

Two questions:

1) Can an emummc be upgraded to a later firmware than your system nand? For being able to play cadence of Hyrule on a 5.1 system firmware for example.

2) Ideally the system nand should be updated and use the emummc for homebrew stuff. If I’m on 5.1 (fuses burned) and I upgrade my sysnand (prepatched unit) to the latest, does it break homebrew? If so, how would a switch boot into emummc?

 

[Idontknowwhattoputhere]

Awesome. Now, how do you use emuMMC?

If you would read its not 100% stable

 

[MSearles]

If you would read its not 100% stable

How am I supposed to believe you when whatever you say is bullshit?

 

[spotanjo3]

If you would read its not 100% stable

Seriously ? A proof?

 

[MSearles]

Seriously ? A proof?

Don't believe him. Whatever he says is bullshit

 

[Idontknowwhattoputhere]

Seriously ? A proof?

Quit with your damn bullshit

 

[spotanjo3]

Don't believe him. Whatever he says is bullshit

Yeah but... read below:

View attachment 169974 Quit with your damn bullshit

Thank you. It is still in beta, I see.

 

[Chocola]

Meaning that the current build and online play is just as likely to get you banned as not. and if you blank your prod info you cant connect to servers iirc so whats the point?

If you want play online, run homebrew stuff and you have unpatched unit, the point it's the next:

1. Make sure that your sysnand are clean of CFW or homebrew stuff, if not, you need to restore your last clean nand backup and disable autorcm.
2. Check that your clean backup work fine and your Switch still without ban, update the sysnand to last firmware version and put the Switch on Airplane mode (you can remove all wireless settings too for more safe).
3. Then make a copy of your current Sysnand for emuMMC, you need merge BOOT0, BOOT1 and rawnand.bin into one file, emummc.bin.
4. After this, for enter on OFW and play online you only should power on your console with power button, make sure that you remove the SD card with emuMMC and homebrew stuff before boot on OFW, you can enable wireless again, play online and do legal things.
5. To enter on CFW, you need a jig (or internal chipset) to inject hekate and boot on your emuMMC, you can do any CFW or homebrew things there, but always offline (if you trust on DNS solutions, incognito, etc etc... you can try to go online, but never to N services, only the rest of Internet)

This it's the same way of backup and restore nand between OFW and CFW, it work and I can trust that they didn't detect it, but take care with the emuMMC, the actions taked on emuMMC have the same risk of do it on sysnand, this just allow us to swap between OFW/CFW avoiding the backup and restore process, so if you do any thing that can ban your console, gona ban it, there is no protection against bans.

Please note that this steps are only for unpatched units, if your unit it's patched you didn't should update your sysnand, on this case the point is mantain the sysnand on lower version possible for run software exploits and the emuMMC on the last version updated with choi for run the lastest games, but these devices can't go online with or without emuMMC.

 

[OvOvOv]

RIP sxos.

 

[spotanjo3]

RIP sxos.

Good bye SXOS.. Hello atmosphere. A priceless!