We've seen it time and time again: an OFW update drops by, CFW gets broken, the devs start working and everything gets fixed eventually. However, looks like this time it's sooner rather than later for the Switch scene, as Atmosphère 0.8.8 has just been released thanks to the efforts of @SciresM and his team!

The key feature this time around is, of course, firmware 8.0.0 support, which was released by Nintendo earlier this month. While it's still recommended for patched units to avoid updating, as the new OFW fully fixed the vulnerabilities used by the upcoming dejà vu exploit chain, unpatched units can now install it and enjoy CFW safely. Some bugfixes are also included, as well as custom exception handlers for Stratosphère modules.

One last important detail to keep in mind is that fusee-primary was updated with this version: you'll need to update it in case you're using it, otherwise Atmosphère may not boot properly.

As usual, you can find the full changelog below:

0.8.8 is Atmosphère's fifteenth official release.

fusee-primary was last updated in: 0.8.8.

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

The following was changed since the last release:

• Support was added for firmware version 8.0.0.
• Custom exception handlers were added to stratosphere modules.
  • If a crash happens in a core atmosphere module now, instead of silently failing a reboot will occur to log the information to the SD card.
• A bug was fixed in creport that caused games to hang when crashing under certain circumstances.
• A bug was fixed that prevented maintenance mode from booting on 7.0.0+.
• General system stability improvements to enhance the user's experience.

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

UPDATE: A hotfix was released for people having issues with the CFW.

Just swapped out the 0.8.8 Atmosphere release build to hotfix a bug -- a service ("apm:p") was removed in 8.0.0, and Atmosphere's attempt to support this caused older games that might access it to fail to launch. If you saw that issue, try re-downloading ams...sorry about that!

— Michael (@SciresM) April 21, 2019

​

Source
GBAtemp thread

 

[axiomjunglist]

Not sure what I'm doing wrong here. Using Hekate 4.9.1, with 8.0.0 firmware installed via ChoiNX, on Atmo 0.8.8 (SD folders/files replaced correctly (twice now)). Downloaded and ran LockpickRCM.bin 1.1.1 in Hekate as well just to see if that would help (did not change anything below)

I get "Unknown pkg1 version. Failed to launch firmware." for all launch options in hekate.ini except Fusee-Primary (using the latest one from the atmo 0.8.8 folder), which gets all the way to Switch logo and then fatal crashes (error code: 2168-0008) every time.

[Atmosphere]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1

[Fusee-Primary]
payload=atmosphere/fusee-primary.bin

[Stock-Old]
[Stock-7+]
secmon=modules/required/exosphere.bin
warmboot=modules/required/lp0fw.bin
atmosphere=1

Anybody else running into this or seen this before with older CFW release?

 

[arjunpatel]

is there any reason to keep on 6.2.0? (dont really care about warmboot fine with dongle) like homebrew wise

 

[ssssss13]

This is a very dumb question but I cant have OFW on 4.1 and atmosphere on 8.0 , right?

 

[RattletraPM]

My switch serial is warning are it safe to use auto-RCM. Is it non-patched? And thank's for your support.

I honestly didn't quite get that (sorry!) but if you can boot any RCM payload (fusee-primary, hekate,etc.) then it's also safe to install AutoRCM.

If you want a more in-depth explaination:
The problem here stems from the fact that AutoRCM is designed intentionally to brick your console as doing so will automatically send it to RCM when powered on. On non-patched units this is safe, as you can send a payload via USB and boot it thanks to Fusèe Gelèe. On the other hand, while patched units can still get into RCM, booting a payload via USB is impossible as Fusèe Gelèe no longer works - so you'll be stuck in RCM unless you use a hardware method to unbrick your console (restoring a previously made RAW backup via an eMMC reader, for example)

 

[Zumoly]

is there any reason to keep on 6.2.0? (dont really care about warmboot fine with dongle) like homebrew wise

As long as latest has cfw support why stay behind? Eventually features will appear you won't be able to enjoy. I say always go for latest whenever you can. Besides with nand backups of your previous fw versions you can revert back anytime no?
Now I'm off to update to 8 after a nand back up.

 

[ZanderX420]

Omg im so freaking happy right now not even a week has gone by and already we got 8.0 cfw. From the bottom of my heart i want to thank sciresM and the reswitched team for there hard work bringing us cfw for each new release. Again ty.

 

[1NOOB]

Not sure what I'm doing wrong here. Using Hekate 4.9.1, with 8.0.0 firmware installed via ChoiNX, on Atmo 0.8.8 (SD folders/files replaced correctly (twice now)). Downloaded and ran LockpickRCM.bin 1.1.1 in Hekate as well just to see if that would help (did not change anything below)

I get "Unknown pkg1 version. Failed to launch firmware." for all launch options in hekate.ini except Fusee-Primary (using the latest one from the atmo 0.8.8 folder), which gets all the way to Switch logo and then fatal crashes (error code: 2168-0008) every time.

[Atmosphere]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1

[Fusee-Primary]
payload=atmosphere/fusee-primary.bin

[Stock-Old]
[Stock-7+]
secmon=modules/required/exosphere.bin
warmboot=modules/required/lp0fw.bin
atmosphere=1

Anybody else running into this or seen this before with older CFW release?

tried the update and ended up with same result as you with the package . restoring lol.....

 

[Snomannen_kalle]

This is a very dumb question but I cant have OFW on 4.1 and atmosphere on 8.0 , right?

No you can't, emuNAND isn't implemented in Atmosphere yet, so OFW and CFW must be on the same version. What you can do, however, is to upgrade from 4.1.0 to 8.0.0 with ChoiDujourNX without burning fuses; that way, you can always downgrade back to 4.1.0 if you want at a later time

 

[stitchxd]

Damn, some themes are broken :/ shit.

 

[ZanderX420]

I was successfully able to downgrade back from 8.0 to 7.0.1 using choidujourNX i freaking love this program im so happy right now. Now i can use deja vu when it releases for 7.0.1

 

[DuveltjeDG]

There is a quick fix somewhere for people with issues after updating. Does somebody know were to find this fix?

 

[Essasetic]

@Switch_Maniac Well... Time did certainly tell.

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

(for reference he said that SX OS might get the update for 8.0.0 first due to the masterkey not changing).

 

[hippy dave]

Does hekate still chainboot atmos on 8.0 ?

Yes, chainloading the new fusee-primary will work. It's the only way to load atmosphere on 8.0 from hekate until hekate is updated.

This is a very dumb question but I cant have OFW on 4.1 and atmosphere on 8.0 , right?

Not until emunand is released.

There is a quick fix somewhere for people with issues after updating. Does somebody know were to find this fix?

Atmosphere github release page, same place as the original release, the zip has been replaced with the fixed version.

 

[Essasetic]

• A bug was fixed in creport that caused games to hang when crashing under certain circumstances.

Ayy. Hopefully this will fix emuiibo hanging on SSBU when checking the Amiibo info.

 

[wurstpistole]

SXOS 3.0 INCOMING IN 3.....2......

Probably not long since nothing major has changed

 

[JokerD]

I have update 8.0 and used atmos 0.8.8 Now i go boot payload , and it error 2000-0000 in atmos. Im try back to boot in ofw and it fine, but go in atmos and boot logo Switch it error :/

 

[Essasetic]

I have update 8.0 and used atmos 0.8.8 Now i go boot payload , and it error 2000.0000 in atmos. Im try back to boot in ofw and it fine, but go in atmos and boot logo Switch it error :/

Did you update properly?

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

Probably not long since nothing major has changed

They'll have a harder time glitching Sept.

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

Not sure what I'm doing wrong here. Using Hekate 4.9.1, with 8.0.0 firmware installed via ChoiNX, on Atmo 0.8.8 (SD folders/files replaced correctly (twice now)). Downloaded and ran LockpickRCM.bin 1.1.1 in Hekate as well just to see if that would help (did not change anything below)

I get "Unknown pkg1 version. Failed to launch firmware." for all launch options in hekate.ini except Fusee-Primary (using the latest one from the atmo 0.8.8 folder), which gets all the way to Switch logo and then fatal crashes (error code: 2168-0008) every time.

[Atmosphere]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1

[Fusee-Primary]
payload=atmosphere/fusee-primary.bin

[Stock-Old]
[Stock-7+]
secmon=modules/required/exosphere.bin
warmboot=modules/required/lp0fw.bin
atmosphere=1

Anybody else running into this or seen this before with older CFW release?

Hmm weird. Let me try it out.

 

[JokerD]

Did you update properly?

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


They'll have a harder time glitching Sept.

im update on ChoiDujoirNX, and download fw 8.0

 

[Essasetic]

im update on ChoiDujoirNX, and download fw 8.0 in this site : -snip-

I'll download it from there and see if I can reproduce it.

 

[Zumoly]

im update on ChoiDujoirNX, and download fw 8.0 in this site :/QUOTE]

You should not link this here.