Atmosphère 0.8.8 released, now compatible with firmware 8.0.0

atmosphere-png.162000

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.


:arrow: Source
:arrow: GBAtemp thread
 
Last edited by RattletraPM,

Wario

Well-Known Member
Newcomer
Joined
Mar 11, 2019
Messages
46
Trophies
0
Age
24
XP
273
Country
United States
If someone has an unpatched "nVidia Tegra" Switch and chooses to update to OFW 8.0 and run Atmosphere 0.8.8 it will forever be through a hardware dongle. Super slim chance of soft mod only via something like Deja Vu because that's been patch by Nintendo in 8.0. Decisions. Decisions.
 

Chocola

GBAtemp Meowgular
Member
Joined
Sep 18, 2018
Messages
379
Trophies
0
Age
32
Location
Neko Paradise
XP
723
Country
Korea, South
If someone has an unpatched "nVidia Tegra" Switch and chooses to update to OFW 8.0 and run Atmosphere 0.8.8 it will forever be through a hardware dongle. Super slim chance of soft mod only via something like Deja Vu because that's been patch by Nintendo in 8.0. Decisions. Decisions.

The unpatched units can downgrade when you like, so isn't decisions at all xD
 
  • Like
Reactions: phonz

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
If someone has an unpatched "nVidia Tegra" Switch and chooses to update to OFW 8.0 and run Atmosphere 0.8.8 it will forever be through a hardware dongle. Super slim chance of soft mod only via something like Deja Vu because that's been patch by Nintendo in 8.0. Decisions. Decisions.
Also not really a decision when you can update without burning fuses in the first place.

Scratch updating without burning fuses, 8.0 has the same fuse count of 7.X so you can downgrade as long as you don't burn any more fuses in the future.
 

JACMAN

Well-Known Member
Newcomer
Joined
May 30, 2018
Messages
50
Trophies
0
Age
26
XP
178
Country
United States
Is it correct that using Hekate 4.9.1 with Kosmos V12 autoboot profile and changed Atmosphere 0.8.8 files gives the "unknown pkg1" error? Because when chainloading only fusee-primary it works fine. Does Hekate needs to be update for this to use autoboot profile?

I got it working but because that ES patches aren't quite ready yet I downgraded back to 7.0.1 and using Atmosphere 0.8.8. Downgraded back in 7.0.1. loading profile of Kosmos V12 and Atmosphere 0.8.8 works perfect.

ChoiDuJourNX is one heck of a homebrew. Perfect flawless up and downgrade functions.

Great work SciresM for delivering this quick, awesome project.
i keep getting the same issue and I've tried everything.any idea?
 

garco

Well-Known Member
Member
Joined
Jun 28, 2006
Messages
141
Trophies
1
XP
1,619
Country
Italy
Is it correct that using Hekate 4.9.1 with Kosmos V12 autoboot profile and changed Atmosphere 0.8.8 files gives the "unknown pkg1" error? Because when chainloading only fusee-primary it works fine. Does Hekate needs to be update for this to use autoboot profile?

I got it working but because that ES patches aren't quite ready yet I downgraded back to 7.0.1 and using Atmosphere 0.8.8. Downgraded back in 7.0.1. loading profile of Kosmos V12 and Atmosphere 0.8.8 works perfect.

ChoiDuJourNX is one heck of a homebrew. Perfect flawless up and downgrade functions.

Great work SciresM for delivering this quick, awesome project.
So is it possible to downgrade? How? Now I'm on 8.0 don't risk the brick for the fuse?
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
So is it possible to downgrade? How? Now I'm on 8.0 don't risk the brick for the fuse?
Its always been possible to downgrade. Burnt fuses make downgrading a bit more of a hassle but as long as your console is vulnerable to Fusee Gelee, you can technically boot any firmware. This is because all of the bootloaders aka the payloads that boot CFW bypass the fuse check automatically allowing CFW to load any firmware regardless of the fuse count. This doesn't mean you can downgrade if an untethered coldboot exploit is released on a lower firmware as you would need to use Fusee Gelee to bypass the fuse check in order to use the untethered coldboot exploit meaning you would need to use double the exploits to use one (under the assumption the untethered coldboot exploit doesn't bypass the fuse check). And you still risk bricking if you try booting a firmware lower than the fuse count since the fuses are a hardware feature meaning they cannot be permanently disabled. The simple workaround is enabling AutoRCM on a firmware lower than the fuse count. For reference, you can find a list of fuses and their respective firmwares here.
 

axiomjunglist

Active Member
Newcomer
Joined
Jan 7, 2019
Messages
37
Trophies
0
Age
45
XP
393
Country
United States
I just downloaded the new (exists at the same Pg. 1 source link) Atmo package & Fusee-Primary bin file. Fusee-Primary is the only launch option currently working in Hekate 4.9.1. Reportedly Sys-Clk isn't working in Atmo 8.0.0 either so I skipped copying its Title folder over this time and finally booted all the way successfully.

Big thanks to all the posters helping myself & others along the way!
 
Last edited by axiomjunglist,

Chocola

GBAtemp Meowgular
Member
Joined
Sep 18, 2018
Messages
379
Trophies
0
Age
32
Location
Neko Paradise
XP
723
Country
Korea, South
Downgrading to an older OFW providing you made a backup of it or downgrading to any OFW from anyone/anywhere.

Always that you use a custom bootloader or prevent the fuse burn on update, he are asking about fuse bricks (the kernel throw error at boot if you have more fuses burnt that expected)
 

rick191

Well-Known Member
Newcomer
Joined
Dec 4, 2015
Messages
53
Trophies
0
XP
233
Country
United States
My switch is unpatched but after reading some posts in this thread I'm guessing I messed up by updating to 8.0 and trying to run atmosphere 0.8.8 because I keep getting error 2168-0002 however it boots fine with OFW?

I made a backup back in september and in the backup folder I have my rawnand.bin and a few other files so what is the best option for me?
 

Zumoly

GBATemp Analyst
Member
Joined
Apr 27, 2018
Messages
1,817
Trophies
0
Location
Yorosso
XP
3,063
Country
Mali
My switch is unpatched but after reading some posts in this thread I'm guessing I messed up by updating to 8.0 and trying to run atmosphere 0.8.8 because I keep getting error 2168-0002 however it boots fine with OFW?

I made a backup back in september and in the backup folder I have my rawnand.bin and a few other files so what is the best option for me?

What else arw you running alonside atmosphere? Did you overwrite your previous setup? If so try deleting cfw files and copy only the release files. You could try addind your mods/patches one by one after you boot successfully and see which one is causing the issue.
 

rick191

Well-Known Member
Newcomer
Joined
Dec 4, 2015
Messages
53
Trophies
0
XP
233
Country
United States
What else arw you running alonside atmosphere? Did you overwrite your previous setup? If so try deleting cfw files and copy only the release files. You could try addind your mods/patches one by one after you boot successfully and see which one is causing the issue.
I was on 7.0.1 and I used the sdsetup site to download the zip file and copy the contents to the SD cards, could you please confirm if updating to 8.0 actually breaks the exploit did I make a mistake?

I'm going to try adding mods and patches one by one.
 
Last edited by rick191,

Zumoly

GBATemp Analyst
Member
Joined
Apr 27, 2018
Messages
1,817
Trophies
0
Location
Yorosso
XP
3,063
Country
Mali
I was on 7.0.1 and I used the sdsetup site to download the zip file and copy the contents to the SD cards, could you please confirm if updating to 0.8.8 actually breaks the exploit did I make a mistake?

I'm going to try adding mods and patches one by one.

You are mostly using Kosmos which has not been updated yet for fw 8. Atmosphere recently got updated and you should use it for now before Kosmos gets support for 8.
For the release files, check the first post.
 
  • Like
Reactions: rick191

Clockdryve

Well-Known Member
Newcomer
Joined
Mar 10, 2019
Messages
74
Trophies
0
Age
61
XP
177
Country
United States
So I update fusee-primary and atmosphere 0.8.8 (I'm on 0.8.4), and this does nothing negative to anything running now on my 254Gb ExFat SD card? If I choose to stay on 6.2.0 AutoRCM after 4.2.0 "no fuse burn" update......and I'll be all good? EXCEPT if I choose to update CFW - I need to rework my keys again I suppose? An update to 8.0 would also alter my NSP compatibility, so they must be reconfigured again for my switch with these "new" keys in FW 8.0??
 
Last edited by Clockdryve,

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
So I update fusee-primary and atmosphere 0.8.8 (I'm on 0.8.4) and this does nothing negative to anything running now on my 254Gb ExFat SD card. If I choose to stay on 6.2.0 AutoRCM after 4.2.0 "no fuse burn" update......and I be all good? EXCEPT if I choose to update CFW - I need to rework my keys again I suppose? An update to 8.0 would also alter my CIA's so they must to reconfigured again for my switch with these "new" keys??
I think you've confused yourself so much you're confusing me.

Not sure what you mean by "4.2" but Atmosphere should work on all firmwares including this latest release. The issue is most likely trying to boot CFW on an exFAT formatted SD card. Reformat the SD card to FAT32. Since your SD card is larger than 32 GB, you will have to format without the Windows formatter. Use something like GUIFormat.

And I cannot fathom any reason why your currently installed content would need the new keys when the keys are already on the console. Its not like whenever you update your firmware normally, suddenly your eShop purchases no longer work. Keys only need to be redumped if you are trying to convert or extract a game on your computer that is encrypted with a newer masterkey found only on the later firmwares. This is correlated to the firmware requirements of the game, not so much the release date (e.g. Smash works on 5.1 despite being released around the time 6.2 was out).

Lastly, Switch doesn't use .CIA files.
 

Ali3n90

Well-Known Member
Newcomer
Joined
Feb 17, 2019
Messages
97
Trophies
0
Age
37
XP
660
Country
United States
My switch is unpatched but after reading some posts in this thread I'm guessing I messed up by updating to 8.0 and trying to run atmosphere 0.8.8 because I keep getting error 2168-0002 however it boots fine with OFW?

I made a backup back in september and in the backup folder I have my rawnand.bin and a few other files so what is the best option for me?
Your error might be caused by a theme. Try to delete the themes.
 
  • Like
Reactions: Liv2MsTrb8T

Site & Scene News

Popular threads in this forum

Recent Content

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: Sorry for accidentally bending over