Atmosphère version 0.8.4 has been released

37918415.png

Happy June 15! @SciresM has released a new update for his Atmosphère Switch CFW, which is now able to boot on firmware 7.0.1 and 7.0.0 without the need for end-users to provide any keys.

For those out of the loop, initial 7.0.0 support was already added some time ago (31st of January) but it did not include a key derivation algorithm for said firmware, relying on a bring-your-own-keys (BYOK) approach instead. Said keys were private and only a few individuals had access to them, meaning the average user was not able to make use of this feature. Some time later a minor firmware revision was released, 7.0.1. The update contained very few changes and the TSEC was left untouched, meaning whatever key derivation algorithm was being made for the previous firmware would work painlessly on the newest one aswell.

Now, said algorithm is finally complete and has been included in the aforementioned release. The new approach relies on a payload called "sept" (which is french for "seven") which gets automatically executed by fusee-primary if the CFW detects it needs to get the 7.0.X keys from the TSEC. It only adds around a second to the total boot time without the need of any user interaction. It comes pre-signed on release builds, thus making it a full non-BYOK solution for regular users, however if you're a developer or power user who likes to compile unofficial builds directly from the source you will still need the appropriate keys to sign it.

The new release also comes with other improvements and changes, some of which were already pushed to the repository sometime ago (for example, the improved reboot to payload function). The full changelog is as follows:
0.8.4 is Atmosphère's tenth official release.

fusee-primary was last updated in: 0.8.4.

The following was changed since the last release:

  • Support for 7.0.0/7.0.1 was added.
    • This is facilitated through a new payload, sept, which can be signed, encrypted, and then loaded by Nintendo's TSEC firmware.
    • sept will derive the keys needed to boot new firmware, and then load sept/payload.bin off the SD card and jump to it.
  • Recognition of applications for override/mitm has been improved.
    • Nintendo's official Title ID range (0x0100000000000000-0x01FFFFFFFFFFFFFF) is now enforced.
  • A deadlock condition was fixed involving libstratosphere mitm sysmodules.
  • Kernel patches for JIT support were added (Thanks, @m4xw!).
    • These loosen restrictions on caller process in svcControlCodeMemory.
  • set.mitm and fs.mitm were merged into a single ams_mitm sysmodule.
    • This saves a process ID, allowing users to run one additional process up to the 0x40 process limit.
  • A bpc.mitm component was added, performing custom behavior on shutdown/reboot requests from am or applications.
    • Performing a reboot from the reboot menu now reboots to atmosphere. This can be configured via system_settings.ini.
    • Performing a shutdown from the reboot menu now works properly with AutoRCM, and does a real shutdown.
  • General system stability improvements to enhance the user's experience.

This version can be downloaded from Atmosphère's releases page on its GitHub repository (link in the sources below).

:arrow: Source
:arrow: GBAtemp thread
 
Last edited by RattletraPM,
gonna answer my own q for any fellow noobs. this sept payload does not seem to run from hekate and when i tried running fusee it didnt run either what i needed to do was use TegraRcmGUI_v2.5 connect via usb to my pc then install driver then inject fusee and i was golden bravo all those involved thanks so much! my 7.0 switch is free once more hurray!
 
Can you elaborate on this for a noob. thanks

If you are on 7.0.0 or 7.0.1, use the latest release of atmosphere to run the homebrew application called choidujourNX which allows you to install any firmware, in this case, going back to 6.2.

You do need to find the firmware files yourself though to install
 
If you are on 7.0.0 or 7.0.1, use the latest release of atmosphere to run the homebrew application called choidujourNX which allows you to install any firmware, in this case, going back to 6.2.

You do need to find the firmware files yourself though to install
You mean to downgrade firmware to 6.2?
 
Is there a way to use this to boot 7.0.1 stock with not enough burnt fuses?

Or do I have to wait for 7.0.1 support on Hekate?

I just want to preserve my fuses while playing online.
 
hold power button for 15-20 seconds

yes this

also just want to post that i was able to downgrade from 7.0 to 6.2 slight issue atmosphere would not boot (?) it might be because i swapped argon.bin with the reboot payload bin? not sure but rolling back to latest kosmos had me sorted out can this version of atmosphere boot on 6.2?
 
yes this

also just want to post that i was able to downgrade from 7.0 to 6.2 slight issue atmosphere would not boot (?) it might be because i swapped argon.bin with the reboot payload bin? not sure but rolling back to latest kosmos had me sorted out can this version of atmosphere boot on 6.2?

should do


Thanks, it works again
What payload should I use?

for 7.0.x the new atmosphere, for 6.2 and lower whatever you want
 
should do




for 7.0.x the new atmosphere, for 6.2 and lower whatever you want

for 7.0.x - exactly what payload file, because when I choose launch/payload in RCM, it says no payload, I guess I have to copy needed file ? to bootloader/payload on SD card? Sorry for noob questions
 
for 7.0.x - exactly what payload file, because when I choose launch/payload in RCM, it says no payload, I guess I have to copy needed file ? to bootloader/payload on SD card? Sorry for noob questions

yep, copy the new fusee-primary to the payloads folder on the sd :)
 
yep, copy the new fusee-primary to the payloads folder on the sd :)
Thanks, I was able to launch payload, but after blue atmosphere logo appeared, then nintendo logo, then 2nd time nintendo logo and it just go back to normal nintendo home. I thought it is straight forward :))
 
So I updated the SD files but now my game data is curropt. Is there a way to fix this??
are they games you legitimately own? or are they games you "acquired" and can only run with a CFW?
If it's the later and you're a sailor of the seven seas then you'll either have to wait on sigpatches to support the new OFW version, or downgrade using Atmosphere.
 

Site & Scene News

Popular threads in this forum