Atmosphere v1.11.0 released, adds support for Switch firmware 22.0.0

atmos.png

The wait is over! 18 days after the release of Switch firmware 22.0.0, the latest version of Atmosphere is available to download. This update brings support for the latest Switch firmware, with special thanks given to alula for handling a lot of the heavy lifting around the kernel, loader, and erpt changes. This update doesn't come without some downsides however, with changes to how applications and applets' lifespans are managed apparently breaking the homebrew ecosystem. You can read more about this below:

Changelog said:
Please note: A change in how applications/applets' lifespan is managed broke the homebrew ecosystem.
  • All applications and applets are expected to perform a clean exit by calling the relevant IPC commands.
  • Homebrew compiled with libnx and hbmenu itself explicitly avoid exiting so it can keep using the same process.
    • Properly fixing this would require a re-design of how homebrew is launched and terminated.
  • As a temporary solution, patches to the am sysmodule are now included which allow restoring the previous behavior and regain homebrew compatibility without any further changes.
  • Nonetheless, please report any issues you may face when testing homebrew to ensure no edge cases have been missed.

Though a temporary solution has been implemented, users should be aware and report any issues that arise from previously-working homebrew.

Atmpshere v1.11.0 is available now directly from the project's GitHub repo.

:arrow: Atmosphere Latest Release
 
Well, tried it out before updating the rest... bad idea for me. Utterly broke my ability to launch homebrew by holding R button for a game. Which has also made being able to install a game nigh impossible.

AUGH, it's even worse. stupid thing forced me to uninstall Z-A and won't even launch the games that were working just fine before. How do I fix this?
 
Last edited by codezer0,
Is there any reason so many people on here use fusee instead of just launching with hekate package3? Like pretty much any guide tells you too?
which guide? the guide I followed back then years and years ago tell me to use fusee. It works fine so why should I change it now using this new package3 method?
 
I need help.

I tried this new build and it broke everything. Tried overwriting with the prior release of atmosphere and while I can boot up the console now, things are still broken.

I cant launch any installed game. The "hold r" to launch homebrew doesnt work at all. How do i fix this?
 
I need help.

I tried this new build and it broke everything. Tried overwriting with the prior release of atmosphere and while I can boot up the console now, things are still broken.

I cant launch any installed game. The "hold r" to launch homebrew doesnt work at all. How do i fix this?
Are you sure your SD card isn't dying or something? The new cfw works fine. I'm using it. But if you rolled back to the last version (I'm assuming you're still on a lower firmware version and not 22) and it's still not working that seems like there's corruption or something on your SD. It's also possible it's just file system corruption and not the actual SD dying. If you have another SD to test try copying Hekate and Atmosphere to it and see if it works correctly. Also are you using exFAT? That's known to cause corruption.
 
Are you sure your SD card isn't dying or something? The new cfw works fine. I'm using it. But if you rolled back to the last version (I'm assuming you're still on a lower firmware version and not 22) and it's still not working that seems like there's corruption or something on your SD. It's also possible it's just file system corruption and not the actual SD dying. If you have another SD to test try copying Hekate and Atmosphere to it and see if it works correctly. Also are you using exFAT? That's known to cause corruption.
It's a 1tb sd card... So safe to say, i definitely cant afford to replace it #EffAI 💀

Has to be fat32, since i HAVE to use network install in Awoo to install most anything. Ever since dbi english stopped being updated, its the only installer that functions for me anymore. And how i cant do the hold R thing for it to resolve properly.
 
My goldfish ratted my pet giraffe for tax evasion and drug trafficking, when the feds arrived and broke down the door, one of them stepped on the update button 😩
 
  • Like
Reactions: sermuns
any real advantages to upgrading? IIRC I'm still on a much older firmware version 20.5 IIRC
 
any real advantages to upgrading? IIRC I'm still on a much older firmware version 20.5 IIRC
Unless there's a game, update or dlc that won't work for you, there's no need to update.
Or for people that updated to the latest firmware by mistake.

Some upcoming games like Tomodashi Life, or Digimon Story Time Stanger might need higher firmware versions.
 
  • Like
Reactions: Blythe93 and Psd99
Back to business, thanks a lot: Hexkyz / Alula / CTCaer, and all Others, I now have access to the eMuMMC again. I'll be more careful next time I update; I'll read more and investigate more. It happened because I was playing Fortnite; it asked me to update the system, and I thought it was just the game. But it's very satisfying to know that there are people like you, a true hero, that we're not helpless. Thank you so much.
Fortnite , heh ?

If you want to avoid future issues , I recommend setting up a emummc

You can update your sysnand, while keeping you emunand at the desired firmware 😀

Read up about it beforehand but it works
 
Unless there's a game, update or dlc that won't work for you, there's no need to update.
Or for people that updated to the latest firmware by mistake.

Some upcoming games like Tomodashi Life, or Digimon Story Time Stanger might need higher firmware versions.
I can confirm that the new MARVEL MaXimum Collection won't even install without being on 22.0.0. That's the main reason I updated, and it works fine.
 
There is some weird problem when installing with DBI now, it stops almost at the end of process and show some weird message like" Skipping file to secure partition ..."
Hope it's just DBI that need a update of some sort now...Any idea of an alternative which still work with 22.0;0?

PS: Oh wait! It seems there is one already in my package called cyberfoil....let's test and see!

PS2: It works! I managed to install Octopath Traveler 0 which was problematic with DBI...
And The Homebrew is really complete, many easy way to install things, so for people having issues with DBI now, you can try this Cyberfoil...
 
Last edited by rudras,
There is some weird problem when installing with DBI now, it stops almost at the end of process and show some weird message like" Skipping file to secure partition ..."
Hope it's just DBI that need a update of some sort now...Any idea of an alternative which still work with 22.0;0?

PS: Oh wait! It seems there is one already in my package called cyberfoil....let's test and see!

PS2: It works! I managed to install Octopath Traveler 0 which was problematic with DBI...
And The Homebrew is really complete, many easy way to install things, so for people having issues with DBI now, you can try this Cyberfoil...
Why are you insisting on using DBI?
Awoo does the same job.

First, download and install the USB driver (Libusbk) according to your operating system:
https://sourceforge.net/projects/libusbk/

Then download and install Java 19. NS USB Loader doesn't work in newer versions. https://www.oracle.com/java/technologies/javase/jdk19-archive-downloads.html

Download NS USB Loader from this page:

https://github.com/developersu/ns-usbloader/releases/tag/v7.3
When Awoo 1.36 or higher is released, download it from this address and extract it to the Awoo-installer folder located in the switch folder on your Nintendo Switch SD card.
Post automatically merged:

In order to use dbi without error

just Run Hekate's fix archive bit on the sd card Thanks @impeeza

There you download: https://github.com/Kofysh/Lockpick_RCM/releases/download/v1.9.19/Lockpick_RCM-v1.9.19.zip Unzip it to "bootloader\payloads" folder
You will need it in order to overcome 2002-1002 error in loading games and DBI prod.keys, title.keys error
Then you can update programs in switch folder such as Awoo installer 1.36
https://github.com/yeoyck/switch-prodkeys
https://github.com/Abdess/retrobios/tree/main/bios/Nintendo/Switch
Good luck.
 
Last edited by savagewarrior,
Why are you insisting on using DBI?
Awoo does the same job.

First, download and install the USB driver (Libusbk) according to your operating system:
https://sourceforge.net/projects/libusbk/

Then download and install Java 19. NS USB Loader doesn't work in newer versions. https://www.oracle.com/java/technologies/javase/jdk19-archive-downloads.html

Download NS USB Loader from this page:

https://github.com/developersu/ns-usbloader/releases/tag/v7.3
I would like to cheekily promote my own alternative to NS-USBloader which requires no dependencies, no Java. It's called ironfoil. Both available as a command-line tool and a graphical interface.



https://github.com/sermuns/ironfoil
 
Last edited by sermuns,

Site & Scene News

Popular threads in this forum