Atmosphere CFW v0.9.0 Released

Atmosphere CFW v0.9.0 Released

SciresM has released a new version of Atmosphere which is a "custom firmware" that allows you to run homebrew and access other features of the Nintendo Switch console. Atmosphere CFW v0.9.0 introduces emuMMC (emuNAND) support brought to you by mx4w and CTCaer which allows you to have one or more virtual NAND along with enhanced error reporting features.

In one usage scenario emuMMC allows you to use your original NAND on a stock firmware version with no hacks to go online with and then use a emuMMC NAND to install homebrew and do not go online with which should result in your account not being flagged and banned by Nintendo and lose access to their online services (in theory it should protect you, but nothing is guaranteed).

The emuMMC was mainly contributed by m4xw who had been working on and giving progress reports about for some time now and decided instead of a stand alone solution to integrate it into Atmosphere. The author of the hekate payload CTCaer is also working on a version of hekate that will allow you to easily create and boot into your emuMMC NAND image(s). It is advised that normal end users wait until the release of Atmosphere v0.9.1 and the new hekate before attempting to create or use an emuMMC, but if you want to go ahead now you should use the partition based solution instead of the file based solution as the latter has some bugs that need to be worked out.

The general process for creating a emuMMC is to make a backup of the boot partitions of the NAND along with a full NAND backup using hekate, join the files together and it is then suggested to make a dedicated partition on your micro sd card and write the raw joined data to it. Once this is done configure Atmosphere to use the partition. I'll be creating a guide in the coming days that will deal with the entire process in detail so stay tuned.

What's New?

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.

links & downloads

Post a Comment


  1. Genial!! Estaré atento por la guía para crear EmuNand