Front-page Firmware  Updated

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.
Click to expand...

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

​

:arrow: Source
:arrow: GBAtemp thread
 
Last edited by RattletraPM,
  • Like
Reactions: DarthDub, mikymax972, Lightyose and 24 others
Click to expand...
axiomjunglist

axiomjunglist

Active Member
Newcomer
Level 4
Joined
Jan 7, 2019
Messages
37
Trophies
0
Age
45
XP
393
Country
United States
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?
 
Last edited by axiomjunglist,
R

RattletraPM

Well-Known Member
OP
Member
Level 19
Joined
Jan 18, 2017
Messages
897
Trophies
1
XP
8,341
Country
Italy
JokerD said:
My switch serial is warning are it safe to use auto-RCM. Is it non-patched? And thank's for your support.
Click to expand...
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)
 
Last edited by RattletraPM,
Zumoly

Zumoly

GBATemp Analyst
Member
Level 12
Joined
Apr 27, 2018
Messages
1,824
Trophies
0
Location
Yorosso
XP
3,170
Country
Mali
arjunpatel said:
is there any reason to keep on 6.2.0? (dont really care about warmboot fine with dongle) like homebrew wise
Click to expand...

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

ZanderX420

Well-Known Member
Newcomer
Level 3
Joined
May 8, 2018
Messages
85
Trophies
0
XP
268
Country
United States
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.
 
  • Like
Reactions: bomigoton and x65943
1NOOB

1NOOB

Well-Known Member
Member
Level 10
Joined
Sep 9, 2006
Messages
662
Trophies
1
Age
33
Location
Inside My Head...
XP
2,335
Country
Canada
axiomjunglist said:
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?
Click to expand...
tried the update and ended up with same result as you with the package . restoring lol.....
 
Snomannen_kalle

Snomannen_kalle

Well-Known Member
Member
Level 11
Joined
Sep 2, 2018
Messages
352
Trophies
0
Age
29
XP
2,425
Country
Norway
ssssss13 said:
This is a very dumb question but I cant have OFW on 4.1 and atmosphere on 8.0 , right?
Click to expand...
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
 
ZanderX420

ZanderX420

Well-Known Member
Newcomer
Level 3
Joined
May 8, 2018
Messages
85
Trophies
0
XP
268
Country
United States
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

DuveltjeDG

Well-Known Member
Member
Level 6
Joined
Apr 5, 2019
Messages
132
Trophies
0
Age
41
XP
854
Country
Netherlands
There is a quick fix somewhere for people with issues after updating. Does somebody know were to find this fix?
 
Essasetic

Essasetic

General Spectator
Member
Level 12
Joined
Jun 16, 2018
Messages
1,573
Trophies
1
XP
3,304
Country
United Kingdom
@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

hippy dave

BBMB
Member
Level 34
Joined
Apr 30, 2012
Messages
9,971
Trophies
2
XP
30,668
Country
United Kingdom
toxic9 said:
Does hekate still chainboot atmos on 8.0 ?
Click to expand...
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.

ssssss13 said:
This is a very dumb question but I cant have OFW on 4.1 and atmosphere on 8.0 , right?
Click to expand...
Not until emunand is released.

DuveltjeDG said:
There is a quick fix somewhere for people with issues after updating. Does somebody know were to find this fix?
Click to expand...
Atmosphere github release page, same place as the original release, the zip has been replaced with the fixed version.
 
JokerD

JokerD

Well-Known Member
Member
Level 7
Joined
Feb 3, 2016
Messages
122
Trophies
0
Location
Half Blood
XP
1,010
Country
Vietnam
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 :/
 
Last edited by JokerD,
Essasetic

Essasetic

General Spectator
Member
Level 12
Joined
Jun 16, 2018
Messages
1,573
Trophies
1
XP
3,304
Country
United Kingdom
JokerD said:
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 :/
Click to expand...
Did you update properly?

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

wurstpistole said:
Probably not long since nothing major has changed
Click to expand...
They'll have a harder time glitching Sept.

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

axiomjunglist said:
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?
Click to expand...
Hmm weird. Let me try it out.
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Majora’s Mask PC port 2Ship2Harkinian gets its first release

Mario Builder 64 is the N64's answer to Super Mario Maker

The founder of Oculus is releasing a $199 FPGA Game Boy system

Ubisoft reveals 'Assassin's Creed Shadows' which is set to launch later this year

Modders hint at potential kernel exploit hack for Xbox One consoles

RetroArch is now available in the Apple Store for iOS devices

The Kingdom Hearts games are coming to Steam

Nintendo takes down the Breath of the Wild randomizer mod from Gamebanana

General chit-chat
Help Users
  • Psionic Roshambo @ Psionic Roshambo:
    300 bucks hmmm lol
  • A @ ATEMVEGETA:
    @BigOnYa, Yes ofc we don't know how Nintendo bans work, but if there are situations where a lot of people have tried safely then we can at least assume that this path is pretty much safe. To say don't try anything homebrew relative just to be safe forever is the easiest thing to say to someone. What I am trying to figure out here is with which cases and what actions got most of the people their bans for.
  • A @ ATEMVEGETA:
    Most things I can find resulting to a ban is save-editing reasons, like Pokehex, etc, and going online afterwards.
  • K3Nv2 @ K3Nv2:
    I'm almost certain fucking Google fibers modems blocking out PPPoE signals
  • BigOnYa @ BigOnYa:
    @ATEMVEGETA
    https://gbatemp.net/threads/can-i-get-my-switch-banned-for-transfering-save.633923/post-10190451
  • K3Nv2 @ K3Nv2:
    Like the 6th time I had to reboot this router trying to get PPPoE active
  • Psionic Roshambo @ Psionic Roshambo:
    Lol
  • BigOnYa @ BigOnYa:
    Ken, your hamster inside it is hungry. Can't you turn POE on/off in your WiFi settings page? Or is it not staying on?
     +1
  • A @ ATEMVEGETA:
    @BigOnYa, Well, in that thread they say it's pretty much safe to manage save files back and forth to consoles as long as you don't go online with cheats activated or with a pirate game.
  • A @ ATEMVEGETA:
    I own every of my games legit with their own cartridges
  • A @ ATEMVEGETA:
    also, I'm not planning to use any cheats, etc, just continue the normal gameplay on the emulator
  • K3Nv2 @ K3Nv2:
    It only gives a internet settings option then it spazes out
     +1
  • BigOnYa @ BigOnYa:
    @ATEMVEGETA if you use save from other switch you may be ok, but using a save from emulator to switch will prob get you banned
  • K3Nv2 @ K3Nv2:
    Under ipv4/6
  • A @ ATEMVEGETA:
    The save file will be created and started normally on the Switch's OFW with a legit game. Then that save file will be transfered to the emulator and continue the gameplay there. Then send it back to the console.
  • K3Nv2 @ K3Nv2:
    I feel like I need to touch @Sicklyboy rack to make it work at this point
  • A @ ATEMVEGETA:
    The save file(s) would never be created first in an emulator
  • A @ ATEMVEGETA:
    Do you think continuing the story on the emulator would flag the save file as illegal? (Again no cheats, etc will take place, only normal story of the game progress)
  • BigOnYa @ BigOnYa:
    But still using the save on a emulator, then back to switch is shady
     +2
  • A @ ATEMVEGETA:
    Yea, that's the only thing I want to clarify actually. If someone has tried it with no problems.
     +1
  • A @ ATEMVEGETA:
    If using the save on the emulator flags the save file. :/
  • A @ ATEMVEGETA:
    Again, "using" I mean normal gameplay not modify it with other means like pokehex, etc
  • A @ ATEMVEGETA:
    @BigOnYa, Can you help me clarify this thing somehow? Do you know someone that may know or have tried it?
  • Psionic Roshambo @ Psionic Roshambo:
    Just play it on the emulation at home and portable use the normal save, I wouldn't risk anything if online is important to you
  • K3Nv2 @ K3Nv2:
    My psychiatrist tried to help me once said it was mine 9 months later
    K3Nv2 @ K3Nv2: My psychiatrist tried to help me once said it was mine 9 months later