Atmosphere CFW updated to version 1.9.4, now supports Switch OFW 20.4.0

atmo.png

Following on the heels of the Nintendo Switch firmware update for version 20.4.0 is a new update for Atmosphere CFW. SciresM has just released version 1.9.4, which adds support for the latest OFW, and even fixes a few minor bugs on top of that. As always, you can grab the latest version of Atmosphere from its official GitHub page, linked below.

The following was changed since the last release:

  • Basic support was added for 20.4.0.
    • An issue was fixed in exosphère's register accessilibity tables (thanks @CTCaer).
      • I believe this had no impact on official code, though it would have prevented some homebrew from interacting correctly with the MC0/MC1 registers.
  • An issue was fixed that could cause a deadlock when building multiple romfs images simultaneously (thanks @Ereza).
    • This fixes support for certain mods, e.g. system language translations overriding content for both overlayDisp and qlaunch.
  • General system stability improvements to enhance the user's experience.

:arrow: Source
 
I should really look at updating my consoles cfw but its been years since I've done anything and the last time I did I'm not sure if I did it wrong.

I have 2 consoles, launch one using donlge/jig and the other a Mariko using sx chip.

My launch one used to select payloads then fusee to boot but now when I accidently hit download on the AIO updater it doesnt boot it.

Silly mistake with drifting joycons made me select and download it.

So this one now I've to select different I think syscfw which i didnt ever use before.

My Mariko one with the sx chip boots how I used to boot my launch, but when selecting the fusee payload it takes absolutely ages for the console to actually boot to the nintendo logo then homescreen.

So I think its probably time to give both a fresh new clean cfw to hopefully fix them and possibly do a firmware update for newer games.

Which I also don't get, I never normally do console firmware updates, just the cfw and still played recentish games.

But with the like of Zelda BoTW which I have always been able to play as it came with my launch console, now prompts me to do a console firmware update in order to play it (same as on my switch 2 console).

My son wanted to play pokemon diamond remake which I bought to play on my switch 2.

It would prompt a firmware update for my switch 1 console which confuses me because I have pokemon pearl installed and running on my switch 1, so no idea why an original game won't play.

Instead I downloaded it as an nsp file and copied it onto my switch 1 consoles nsp folder.

Which I thought you had to install nsp games, rather than just copying it into a folder like you would xci rom dumps.

This is what I mean, its been years since I've done anything switch related or even making cheat codes and during the time I was, I was fighting cancer which its treatment has crippled me.

I moved to remastering PS2 games and now coming close to my 2nd release, Resident Evil Code Veronica X (including game FMVs I am remastering)..... this should be done and be releasing very soon.
 
  • Like
Reactions: iguanoPT
Hello I updated to the latest atmosphere and hekate version and have downloaded the latest syspatches but I am unable to launch my emummc as it says "failed to apply emummc" "failed to launch HOS"
I have also deleted kip1patch=nosigchk from my hekate_ipl.ini
 
Hello I updated to the latest atmosphere and hekate version and have downloaded the latest syspatches but I am unable to launch my emummc as it says "failed to apply emummc" "failed to launch HOS"
Are you launching Atmosphere with fusee.bin payload? Make sure that you update fusee.bin as well.
If that doesn't work, make a backup of your atmosphere and bootloader folder and delete it afterwards. After that, get the latest Atmosphere, Hekate and sys-patch and extract them to your SD card. That should fix the problem. After that, you can restore your Switch apps and modules one by one (update them while you're at it).
Post automatically merged:

My launch one used to select payloads then fusee to boot but now when I accidently hit download on the AIO updater it doesnt boot it.
Stay away from AIO updaters if you don't know what you're doing. Check this guide instead on how to update your setup.

Which I also don't get, I never normally do console firmware updates, just the cfw and still played recentish games.
I haven't updated my hacked consoles' stock system ever since i bought them, only emuMMC CFW and that's pretty much it.

Instead I downloaded it as an nsp file and copied it onto my switch 1 consoles nsp folder.

Which I thought you had to install nsp games, rather than just copying it into a folder like you would xci rom dumps.
I personally use DBI for installing my games. Latest English should work well for installing games, but I suggest getting familiar with where things are located in the latest Russian version. Alternatively, you can use TinWoo Installer (or sphaira? I think it has a built-in title installer of sorts).

If you want to setup your console from scratch, I'd suggest following this guide: https://switch.hacks.guide/user_guide/getting_started.html
A few things to consider:
1) If you don't plan on using clean stock system for legit games and you only plan on "playing backups", you don't have to update your stock firmware. You can download firmware updates from a few certain places (can't link to them here).
2) For "playing backups", you'll need sys-patch.
3) Make sure to block Nintendo servers with either 90DNS or DNS MITM (Exosphere).
 
Last edited by Blythe93,
Are you launching Atmosphere with fusee.bin payload? Make sure that you update fusee.bin as well. If that doesn't work, make a backup of your atmosphere and bootloader folder and delete it afterwards. After that, get the latest Atmosphere, Hekate and sys-patch and extract them to your SD card. That should fix the problem. After that, you can restore your Switch apps and modules one by one (update them while you're at it).
No I am booting it from the hekate menu directly and I have the latest fusee.bin
 
Sorry if this is the wrong thread. If I reboot to hekate and then use UMS to update all the HATS file will it be okay?
Or the console needs to be completely turned off?

Ty
 
No I am booting it from the hekate menu directly and I have the latest fusee.bin
Something might have gone wrong during the update process then. Did it work before you performed an update? Which firmware/Atmosphere were you on before that?

You should check in your emummc.ini whether your path and nintendo_path are correct i.e. set to the correct folders but, sadly, other than that nothing much I can do to help you out. Usually getting the fresh Atmosphere, Hekate and sys-patch fixes most of those issues but something else might have gone wrong along the way and I'm can't really see what without checking the console in person. :/

Sorry if this is the wrong thread. If I reboot to hekate and then use UMS to update all the HATS file will it be okay?
That's how I do it. Reboot to hekate, mount SD card via USB tools and update whatever needs to be updated. I can't say for sure if updating HATS pack that way won't break anything though as I'm not sure what else it has included. For example, I've set my reboot_payload.bin to hekate's one, not the Atmosphere's one and HATS would probably break that for me. But, if you've previously updated your HATS pack that way and nothing broke, you're probably good to go. Just make sure to backup any personal config you've created before.
 
  • Like
Reactions: SkyeS
Trying to think of the last time I played my Switch long enough to warrant updating...

I know I have a pile of games on the system I haven't gotten to but there's also the pile on my computer that I haven't played. My backlog is fairly sizable.
 
Trying to think of the last time I played my Switch long enough to warrant updating...

I know I have a pile of games on the system I haven't gotten to but there's also the pile on my computer that I haven't played. My backlog is fairly sizable.
I haven't had a reason to update so I'm on 16.0.3 but we'll see. I've just picked it up and played Sparks of Hope from start to finish and I'm in the middle of the first dlc. I honestly think they did a good job with the game and I'm very critical usually.
 
Something might have gone wrong during the update process then. Did it work before you performed an update? Which firmware/Atmosphere were you on before that?

You should check in your emummc.ini whether your path and nintendo_path are correct i.e. set to the correct folders but, sadly, other than that nothing much I can do to help you out. Usually getting the fresh Atmosphere, Hekate and sys-patch fixes most of those issues but something else might have gone wrong along the way and I'm can't really see what without checking the console in person. :/
Hi i managed to get it to work with a fresh install. However now I have another problem. All of my games except for Dave the diiver are unable to run. even with all the updated sigpatches. Even the latest version of tinfoil fail to work
 
Updated and now my mario 64decomp does not work anymore...fuck XD
Did you update sigpatches? Or better install Sys-patch sysmodule
Post automatically merged:

Hi i managed to get it to work with a fresh install. However now I have another problem. All of my games except for Dave the diiver are unable to run. even with all the updated sigpatches. Even the latest version of tinfoil fail to work
The same of the above
 

Did you update sigpatches? Or better install Sys-patch sysmodule
Post automatically merged:


The same of the above

Yes I have from the "sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/post-10692213" thread (I can't send this link because of spam protection) as well as the sys-patch sys module, I have everything on except the disablecaverifications
 
Yes I have from the "sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/post-10692213" thread (I can't send this link because of spam protection) as well as the sys-patch sys module, I have everything on except the disablecaverifications
Then your problem is not sigpatches, try removing any mod from the games and disable any unneded/outdated sysmodule like systweak
 

Site & Scene News

Popular threads in this forum