It's here! @SciresM and the rest of his team have just released a new version of Atmosphère, their popular free and open-source Switch CFW.

Version 0.9.4's main highlight is full OFW 9.0.0 support, both for SysMMC and EmuMMC. However, if you plan on updating, there are a few important things to keep in mind. First off, Nintendo's latest firmware changed how HID works, which breaks libnx button input detection. This has been addressed in newer versions of the library, but will require homebrew to be recompiled in order for it to be fixed properly. As such, a temporary measure has been put in place to make old homebrew detect input properly while developers recompile their apps, but this will be removed in later releases as it could introduce further issues with HID MITM. Be sure to update everything you use when new versions pop up!

Secondly, the game card ASIC has also been updated in 9.0.0, which will cause the GC slot to stop working if you downgrade or run an earlier firmware in EmuMMC until you update. To prevent this, Atmosphère will now apply the nogc patch automatically if you boot into 9.0.0 on consoles with a lower fuse count. You can force disable this if you wish by setting nogc = 0 in BCT.ini.

Finally, USB cannot be IPS patched or MITM'd correctly due to some initialization changes, but a solution is currently being looked into.

There are also some general fixes and improvements, including correct BIS key generation for newer unpatched units and hbl 2.2 + hbmenu 3.1.1. You can read the full changelog below:

0.9.4 is Atmosphère's twenty-second official release.

fusee-primary was last updated in: 0.9.3.

With thanks to the @switchbrew team, Atmosphère 0.9.4 is bundled with hbl 2.2, and hbmenu 3.1.1.

The following was changed since the last release:

• Support was added for 9.0.0.
  • Please note: 9.0.0 made a number of changes that may cause some issues with homebrew. Details:
  • 9.0.0 changed HID in a way that causes libnx to be unable to detect button input.
    • Homebrew should be recompiled with newest libnx to fix this.
    • Atmosphere now provides a temporary hid-mitm that will cause homebrew to continue to work as expected.
      • This mitm will be removed in a future Atmosphere revision once homebrew has been updated, to allow users to use a custom hid mitm again if they desire.
  • 9.0.0 introduced an dependency in FS on the USB system module in order to launch the SD card.
    • This means the USB system module must now be launched before the SD card is initialized.
    • Correspondingly, the USB system module can no longer be IPS patched, and its settings cannot be reliably mitm'd.
    • We know this is frustrating, so we'll be looking into whether there is some way of addressing this in the future.
  • Please note: 9.0.0 updated the switch's gamecart controller ("lotus") firmware.
    • To prevent the burning of lotus fuses, Atmosphere now applies nogc patches when booting into 9.0.0 with fuses below 9.0.0.
    • If you wish to play gamecarts on 9.0.0 (but forever prevent yourself from playing them on < 9.0.0), set nogc = 0 in BCT.ini.
• An off-by-one error was fixed in boot system module's pinmux initialization.
  • This could theoretically have caused issues with HdmiCec communication.
  • No users reported issues, so it's unclear if this was a problem in practice.
• A bug was fixed that could cause webapplet launching homebrew to improperly set the accessible url whitelist.
• BIS key generation has been fixed for newer hardware.
  • Newer hardware uses new, per-firmware device key to generate BIS keys instead of the first device key, so previously the wrong keys were generated as backup.
  • This only affects units manufactured after ~5.0.0.
• General system stability improvements to enhance the user's experience.

@CTCaer's Hekate mod has also been updated, and full 9.0.0 support here is just the beginning! Version 5.0.2 adds a forced autoboot via ID key option, which will prove particularly useful with Android and Linux distros - and staying on topic, CPU/GPU warmboot reboot has been fixed for said OSes as well. A bug that made SaltyNX hang under 8.X.X EmuMMC has also been fixed, so apps and mods that depend on it (such as ReverseNX) will now work properly again. The nogc patch will be applied automatically when running pre-9.0.0 firmware in EmuMMC on a console with a higher fuse count: this is different than the previously described Atmosphère autonogc feature as this is an error prevention measure, while AMS' own tries to avoid game card slot ASIC updates.

Hekate Nyx has also some new goodies, such as archive bit support for EmuMMC folders and proper AutoRCM detection after restoring an eMMC backup. The version included in this release is 0.8.2.

Several other bugs and smaller issues have been fixed, all of which are listed in the changelog below:

This version supports booting ALL current OS/CS CFW, Linux chainloading and payload tools.
No more SD card removals

Latest HOS supported: 9.0.0

New in this version

• Full support for 9.0.0
• Fixed SaltyNX for emuMMC 8.x.x
  There was an issue with fs mitm patches where it caused hangs for SaltyNX.
• Add support for forced AutoBoot via id key - Android reboot
  You can now add id=max7char to your boot entries and hekate can be instructed to autoboot via only this.
  This will be helpfull especially with many Linux distros and Android (id=SWRANDR).
• AutoNOGC protection for fatal errors in emuMMC
  NOGC will now be applied automatically when fuses are >= 9.0.0 and emuMMC is less than that.
• Streamline power cycles for Sandisk U1 SDR104
  No more hangs because of this.
• Fix CPU/GPU on warmboot reboot from Linux/Android
• Allow critical info to be shown when a fatal error occurs while AutoBooting HOS
  Now, before booting Nyx right away, it will show the error message and wait for a button press.
• Add exosphere/kernel no user exceptions handler cfg
• And many other bugfixes

New in emuMMC

• 9.0.0 support

The binary is based on m4xw/emuMMC@4b5d9ae

Nyx v0.8.2

• 9.0.0 support for info and tools
• Fix AutoBoot list for inis (More configs)
  You can now select a cfg from ini folder for autobooting
• Update AutoRCM status when a eMMC restore occurs
• Add Fix Archive bit support for emuMMC folders
• Fix eMMC split restore when < 10 parts
  (FYI nyx supports splits that are 4MB aligned. Only last part is allowed to be unaligned.)
• Do not hide delay time option (for bootlogo) when AutoBoot is off
• And many other bugfixes

Check readme.md for more.

NOTE: You will need sept and a custom secmon and warmboot binary to boot 7.0.0-9.0.0 or stock emuMMC.

If you are a homebrew developer and wish to fix the broken button input issue found in 9.0.0, you can use dkp-pacman to update libnx to its latest version.

UPDATE: A bug affecting games with vibration support has been found and a hotfix has been released. Please redownload Atmosphère if this affects you.

Atmosphère: Source / GBAtemp Thread
Hekate CTCaer: Source / GBAtemp Thread

 

[Mythical]

Makes sense, though some of my games don't work now. Some do. What gives?

the ones that do work probably need older keys while the ones don't work need newer keys. You could also try redumping your keys to update them to the current firmware of your switch

 

[RandomUser]

First time Atmos beat SX OS in speed.

Couldn't be more wrong there bud. I cannot remember but I think it was firmware 7.0 or 7.1 when Atmos introduces SEPT or something like where the SXOS was going through a dry spell for a very long time, due to the SEPT uses Atmos splash screen.
I think keys were needed to compile a working SEPT in order to boot into the firmware.

 

[gbablackrain]

um what?s

Usually TX is the first to release new versions to support OFW and cool stuff.

 

[Mythical]

Usually TX is the first to release new versions to support OFW and cool stuff.

maybe for xci loading, but not much if anything else

 

[skydancer93]

So if I’m still on 8.0.1, stay on 0.9.3?

 

[smf]

Sucks. Here I thought keeping the lowest FirmWare was the way to go.

Some people always say that, but there are pros and cons. There is always emunand. If you cant use RCM then you shouldn't update.

What gives?

You lost me at what gives.

So if I’m still on 8.0.1, stay on 0.9.3?

Or update, your choice.

 

[maxpower49]

I was previously jailbroken on 8.x before accidentally (i know) updating to 9.0 a few days ago. Can someone give me a step by step of what I need to do to update the jailbreak without losing my installed NSPs and game saves?

 

[Ericthegreat]

Good news!..

By the way, where one can find fw 9.0.0 zip for the choidujournx?.. Or it's a copyrighted matter?..

Xbins probably, if you do xbins auto instead of using your own irc program, know that there will be false positives, and you anti virus/chrome will try to block it.

 

[RattletraPM]

The OP has been updated with more info about Hekate - even if they're two separate projects they both got updated almost at the same time, share similar new features while also having something unique to offer on their own and it just wasn't right to give the spotlight to only one of them

 

[Rahkeesh]

Trying to understand significance of the new android/linux options in hekate. Is this supposed to help us reboot to payload from those OSes?

 

[regnad]

Is everyone experiencing some games no longer working with FW9.0 and ATM, or is it just that one guy on the last page?

 

[phillyrider807]

Do we still have to update to 9.0 through choi so we don't burn fuses or can we update straight from the switch now with atmosphere?

 

[Rahkeesh]

Nothings changed in that regard, if you update firmware online and don't have a jig installed, it will bypass any payload, boot straight into OFW and burn fuses. They've added protection for gamecard fuses not the main ones.

 

[OneAngryGamer]

Is everyone experiencing some games no longer working with FW9.0 and ATM, or is it just that one guy on the last page?

Its not just me, on SciresMs twitter page lots of people are having the same issue.

 

[gizmomelb]

Quick work SciresM

I expect a new SXOS version any time now :9

oh look, a nice unbiased post from a moderator..

 

[goncalodoom]

Added the "nogc = 0" to BCT.ini but it's still throwing the error that the game card could not be read... -_-

 

[regnad]

Its not just me, on SciresMs twitter page lots of people are having the same issue.

Ugh. So I guess I won't be updating for a while.

I hope Goose Game, Zelda, DQ, etc won't require 9.0.

Looks like many are having trouble with Kosmos as well. Is anyone able to use the latest Kosmos with FW9.0?

Also RE Kosmos, what's this mean?

Firmware update 9.0 updated the gamecard reader firmware! If you want to use your gamecard reader but don't want to burn your fuses, you have to disable autonogc within the hekate GUI. THIS IS IRREVERSIBLE!​

If I don't do this I can't use carts, right? But if I do do it, what does that mean? How is it irreversable? What problems will this cause requiring an all caps warning?

 

[Deleted member 397813]

Les GOOOOOOOOOOOO

 

[OneAngryGamer]

Ugh. So I guess I won't be updating for a while.

I had to downgrade back to 810, could not install astral chains nor fire emblem using the latest stuff.

 

[Rahkeesh]

Also RE Kosmos, what's this mean?

Firmware update 9.0 updated the gamecard reader firmware! If you want to use your gamecard reader but don't want to burn your fuses, you have to disable autonogc within the hekate GUI. THIS IS IRREVERSIBLE!​

If I don't do this I can't use carts, right? But if I do do it, what does that mean? How is it irreversable? What problems will this cause requiring an all caps warning?

9.0 requires the gamecard reader firmware be updated. Once the update is made, it burns a fuse on the reader, so you can't go back to an earlier GC firmware. That's why it's irreversible.

If you block the update, your fuses will be safe but you won't be able to use gamecards on 9.0+ for the time being. If you let the update go through you can use on 9.0 but won't be able to use it on earlier versions like 8.1 and prior. This also applies to emunand and the like if you are running different versions of firmware, you only have one real GC reader so you have to choose which side of the 8.1/9.0 divide you want it to function on.