A quick update has been released for @SciresM 's Switch CFW, Atmosphère, bumping the version up to 0.9.1. Support for the latest available OFW (8.1.0) has been added and a few emuMMC-related bugs have been fixed. This, however, is not the general bugfix release the devs were talking about previously, so emuMMC should still be considered experimental for the time being.

The official changelog can be read below:

0.9.1 is Atmosphère's nineteenth official release.

fusee-primary was last updated in: 0.9.1.

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

The following was changed since the last release:

• Support was added for 8.1.0.
• Please note, emummc is still considered beta/experimental -- this is not the inevitable bugfix update for it, although some number of bugs have been fixed.
• 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.

On a last note, fusee-primary has also been changed with this version. Remember to update it too if you're using it!

UPDATE: If you were not being able to boot with this release, re-download it from the repo. A bug has been fixed which caused the system to hang if there was no emummc.ini file present on the microSD card.

Small logic error introduced in the last few days to fix an emummc bug would cause blackscreens on boot if emummc.ini didn't exist (even for non-emummc). Fixed, if this was affecting you re-download the 0.9.1 release (or create a blank emummc.ini, I guess? :))

Sorry about that!

— Michael (@SciresM) June 20, 2019

​

Source
GBAtemp thread

 

[fst312]

Can’t wait till emummc is ready, I know there is a tutorial on how to use the current version but I know I might make a mistake and ruin my other switch that I really want to use it on.

 

[Maq47]

Can’t wait till emummc is ready, I know there is a tutorial on how to use the current version but I know I might make a mistake and ruin my other switch that I really want to use it on.

Yes! A GBAtemp user with common sense! I thought those were all but extinct! You've restored my faith in this website!

 

[Chocola]

Can’t wait till emummc is ready, I know there is a tutorial on how to use the current version but I know I might make a mistake and ruin my other switch that I really want to use it on.

If your Switch are unpatched to fuseé geleé then just make a full nand backup with Hekate (BOOT0, BOOT1 and rawnand) before make any modification, you gona can comeback all time with this backup if you made some mistake.

 

[mrdude]

I've just updated to Atmosphere 0.9.1

Firmware on Emunand 8.1.0 - emunand freezes on Nintendo Logo.
Reinstalled firmware 8.0.1 - emunand works fine.

Seems there's an issue using emunand which has firmware 8.1.0 installed.

8.1.0 fimware on emunand - works fine with SXOS.

 

[Chocola]

I've just updated to Atmosphere 0.9.1

Firmware on Emunand 8.1.0 - emunand freezes on Nintendo Logo.
Reinstalled firmware 8.0.1 - emunand works fine.

Seems there's an issue using emunand which has firmware 8.1.0 installed.

8.1.0 fimware on emunand - works fine with SXOS.

There are a bugs to solve on emuMMC implementation, the 8.1.0 should work on sysnand atleast.

Please let a issue with all details possible on: https://github.com/Atmosphere-NX/Atmosphere/issues

 

[mrdude]

There are a bugs to solve on emuMMC implementation, the 8.1.0 should work on sysnand atleast.

Please let a issue with all details possible on: https://github.com/Atmosphere-NX/Atmosphere/issues

Done :-)

 

[Deleted User]

Getting black screen before switch logo

TX SX OS 2.8 loads ofw and cfw

Tried various brands of micro sd exfat and fat32

I think somethings up with this switch as it only loads ofw from tx sx boot option screen

This started from 8.1.0 system update

 

[Chocola]

Getting black screen before switch logo

TX SX OS 2.8 loads ofw and cfw

Tried various brands of micro sd exfat and fat32

I think somethings up with this switch as it only loads ofw from tx sx boot option screen

This started from 8.1.0 system update

On sysnand or emuMMC?

 

[goncalodoom]

Does it really support 8.1.0? Getting ""Failed to launch CFW" after updating through ChoiDujourNX to 8.1.0 and latest atmosphere...

 

[Deleted User]

On sysnand or emuMMC?

Sysnand black screens loading direct with no autorcm
Sysnand and TX CFW only currently load through tx sx options menu to load cfw/ofw - Tried loading atmo payload through tx menu and black screen
Atmo always black screens before switch logo
When in sysnand exfat and fat 32 cards are being detected

This all came about from an 8.1.0 update

 

[Owenge]

SXOS and Atmossphere: I aM sPeEd

 

[gizmomelb]

That TX fame did not last long.

it didn't have to - but it should show all the TX haters that TX did NOT use Sept, because the updated Sept wasn't even available before TX did their update.

So can we please stop with the usual shitbaggery between CFW? They both have their unique features, so let's be thankful there is a CHOICE.

 

[Chocola]

@SciresM: There are a some affected people that can't boot with the last release. Boot problems seems related with updates through ChoiDujourNX, so probably not related with a Atmosphére.

I've just updated to Atmosphere 0.9.1

Firmware on Emunand 8.1.0 - emunand freezes on Nintendo Logo.
Reinstalled firmware 8.0.1 - emunand works fine.

Seems there's an issue using emunand which has firmware 8.1.0 installed.

8.1.0 fimware on emunand - works fine with SXOS.

Getting black screen before switch logo

TX SX OS 2.8 loads ofw and cfw

Tried various brands of micro sd exfat and fat32

I think somethings up with this switch as it only loads ofw from tx sx boot option screen

This started from 8.1.0 system update

 

[Josshy0125]

@SciresM: There are a some affected people that can't boot with the last release.

Sounds to me like it wasnt... ready prior to its release

 

[Deleted User]

Sounds to me like it wasnt... ready prior to its release

Will have to wait then.

 

[Chocola]

Sounds to me like it wasnt... ready prior to its release

Probably a compile mistake or missed changes to git before compile, the public builds and the dev builds differ a bit.

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

Does it really support 8.1.0? Getting ""Failed to launch CFW" after updating through ChoiDujourNX to 8.1.0 and latest atmosphere...

Sysnand black screens loading direct with no autorcm
Sysnand and TX CFW only currently load through tx sx options menu to load cfw/ofw - Tried loading atmo payload through tx menu and black screen
Atmo always black screens before switch logo
When in sysnand exfat and fat 32 cards are being detected

This all came about from an 8.1.0 update

it didn't have to - but it should show all the TX haters that TX did NOT use Sept, because the updated Sept wasn't even available before TX did their update.

So can we please stop with the usual shitbaggery between CFW? They both have their unique features, so let's be thankful there is a CHOICE.

Sounds to me like it wasnt... ready prior to its release

Will have to wait then.

Disable all the kip patches and all modifications and try to boot with a fresh atmosphére release, I try it now and work, so seems some incompatibility or error with modules system.

 

[Deleted User]

Probably a compile mistake or missed changes to git before compile, the public builds and the dev builds differ a bit.

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











Disable all the kip patches and all modifications and try to boot with a fresh atmosphére release, I try it now and work, so seems some incompatibility or error with modules system.

Tried that and black screen.

 

[Darksabre72]

can't wait to try this when they get most of them bugs fixed

 

[Deleted User]

Fwiw, I updated from 8.0.1 to 8.1.0 via settings on emunand and didn't get a black screen on the Switch logo or anything. Just missing the sig patches to run stuff right now until they're updated. (so I've just downgraded back for the time being)

 

[Chocola]

Boot problems seems related with updates through ChoiDujourNX, so probably not related with a Atmosphére, users that update through oficial way (Settings menu > Console > Check for updates) we don't have any problem.

Probably @rajkosto need to update his homebrew for support the changes on 8.1.0