Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[PKM190]

I think you misread the changelog, these are about the changes made in 1.10.0, not 1.10.1:

View attachment 544372

Basic support was added for 21.0.0.

• The console should boot and atmosphère should be fully functional.
• Please note: As a result of changes made to nintendo's software in 21.0.0, there is again roughly 10MB less memory available for custom system modules.

That is the part I am confused about, in green. Seems like with 21.0.0, there is less memory available yet again. 21.1.0 was released two days ago. So look it looks like 21.1.0 might require a re-compile of more apps. Or maybe I am just misreading.

 

[XenoFredo]

That is the part I am confused about, in green. Seems like with 21.0.0, there is less memory available yet again. 21.1.0 was released two days ago. So look it looks like 21.1.0 might require a re-compile of more apps. Or maybe I am just misreading.

I installed the update yesterday on my EmuNAND and everything appears to run the same, no issues. SciresM has addressed the memory concerns and there was even slightly more (a few MB's) memory available on firmware 21 than on 20. Besides, available memory has nothing to do with whether homebrews need recompiling or not, it's a matter of one the libraries used that lost compatibility, and there's been no change on the latest firmware that would require another update of the homebrews.

Post automatically merged: Dec 11, 2025

After updating to HOS 21.0.0 and doing a fresh install of Atmosphere 1.10.1 and Hekate 6.4.2 I installed Sphaira 1.0.0 and at first launch in applet mode it ran fine.
After exiting and launching with title override it gets stuck on "Checking" forever (30 minutes tested).
Using applet mode I installed the forwarder for it and tried launching it again with the same results.
Rebooted my Switch and it launched using the forwarder. Exit and relaunched it via forwarder again and got stuck at "Checking". Same happens when using title override, it launched fine first time, but gets stuck at "Checking" on next launch. Only way to fix is a reboot.

Post automatically merged: Dec 10, 2025

Edit: I also installed sys-patch and sigpatches for AMS 1.10.1
Edit 2: Also every game does this. A window saying "Please Wait" flashes infinitely

You need to install the latest modded version of Linkalho, unlink your account and relink it, or just link it if it had never been done.

Homebrew Homebrew app  Post in thread 'sys-patch - sysmod that patches on boot'

Nov 19, 2025

too bad then, the .dat the actual information is read from is read from a system savefile .dat (as you can turn off upload/download of savegames through official settings) while most other olsc functions have their values read from the exefs itself.

Don't worry about it!!! We still can edit the config.ini




Here's the linkalho MOD from mrdude:

• josete2k

• 
• 

 

[PKM190]

I installed the update yesterday on my EmuNAND and everything appears to run the same, no issues. SciresM has addressed the memory concerns and there was even slightly more (a few MB's) memory available on firmware 21 than on 20. Besides, available memory has nothing to do with whether homebrews need recompiling or not, it's a matter of one the libraries used that lost compatibility, and there's been no change on the latest firmware that would require another update of the homebrews.

Okay thank you. Sounds like if the homebrew apps were updated 2 or so weeks back they should all run fine now.

 

[Naxster]

Sorry for this, stupid question if I want to update to the latest stable Atmosphere, what's the easiest way to do it?

 

[XenoFredo]

Sorry for this, stupid question if I want to update to the latest stable Atmosphere, what's the easiest way to do it?

You download the latest release on github, copy the files to your SD card in Hekate, make sure you add the latest release of MissionControl if you have that, download the latest firmware, put it on your SD card, then go to Daybreak and update.

 

[Naxster]

You download the latest release on github, copy the files to your SD card in Hekate, make sure you add the latest release of MissionControl if you have that, download the latest firmware, put it on your SD card, then go to Daybreak and update.

I’m not sure what MissionControl is. Is it required for updating?
Also, should I simply replace the existing atmosphere folder, or do I need to delete the old one before adding the new version?

Do I need to add other files, such as newer Hekate etc?

Sorry for these stupid questions, it has been a looooong time ago since I updated Atmosphere

 

[NeoGranzon]

I’m not sure what MissionControl is. Is it required for updating?
Also, should I simply replace the existing atmosphere folder, or do I need to delete the old one before adding the new version?

Do I need to add other files, such as newer Hekate etc?

Sorry for these stupid questions, it has been a looooong time ago since I updated Atmosphere

@Naxster follow this step:
1 download last Atmosphere,fusee,Hekate from GitHub and sys-patch in this site(use search function)
2 extract and Copy on sdcard root
3 reboot on OFW
4 go to setting/system update and update firmware
5 power off and inject Hekate(Power&vol+)with jig or rcmloader.
6 from Hekate push launch e choice CFW
If everything went well you now have the latest Atmosphere.

 

[Naxster]

@Naxster follow this step:
1 download last Atmosphere,fusee,Hekate from GitHub and sys-patch in this site(use search function)
2 extract and Copy on sdcard root
3 reboot on OFW
4 go to setting/system update and update firmware
5 power off and inject Hekate(Power&vol+)with jig or rcmloader.
6 from Hekate push launch e choice CFW
If everything went well you now have the latest Atmosphere.

But I don’t want to update the firmware, I just want to use the latest Atmosphere version.
My EmuNAND is already on 21.0.1.

The Atmosphere build I’m using now is last week’s pre-release (the one right before the current stable release). And I modded my switch literally last week.

 

[Earthshine]

Sorry @Earthshine ,i already had the first file you attached and when i tried to connect to the Nintendo server it didn't give me the error,as it gives me now if i try with the primary and secondary DNS set like this 163.172.141.219(primary)207.246.121.077(secondary)and which i use together with Switch 90dns tester.

Not sure exactly what you're trying to do or accomplish. What error? I don't see you mention any error. Also, when you showed images of your files they were not the same as the ones I attached. named the same, yes, but they did not have the same contents as the ones I posted. You had it set up for sysmmc.txt, then the next one you showed was an altered default.txt.

 

[NeoGranzon]

But I don’t want to update the firmware, I just want to use the latest Atmosphere version.
My EmuNAND is already on 21.0.1.

The Atmosphere build I’m using now is last week’s pre-release (the one right before the current stable release). And I modded my switch literally last week.

@Naxster if you want update only Atmosphere,follow step 1&2.

 

[Naxster]

@Naxster if you want update only Atmosphere,follow step 1&2.

Ahhh it's that easy?!
Thank you!

 

[NeoGranzon]

Not sure exactly what you're trying to do or accomplish. What error? I don't see you mention any error. Also, when you showed images of your files they were not the same as the ones I attached. named the same, yes, but they did not have the same contents as the ones I posted. You had it set up for sysmmc.txt, then the next one you showed was an altered default.txt.

@Earthshine i was referring to this error

when you try to connect to Nintendo server with DNS are blocked.

 

[Hayato213]

@Earthshine i was referring to this error
View attachment 544652
when you try to connect to Nintendo server with DNS are blocked.

You can't go online when you block server communication that why you get 2137-8007

 

[NeoGranzon]

You can't go online when you block server communication that why you get 2137-8007

@Hayato213 i know,this is what i'm trying to convey to the user i replied above.
Since i had a problem with downgrade to 20.5.0 and was advised to restore everything while keeping the saves,i hadn't set the primary and secondary DNS and when i used FTP to transfer files and screenshots to my smartphone, the Switch updated automatically even though i had disabled automatic updates.

 

[Earthshine]

@Earthshine i was referring to this error
View attachment 544652
when you try to connect to Nintendo server with DNS are blocked.

As hayato213 said, that's supposed to happen. That's the point of blocking.

 

[NeoGranzon]

As hayato213 said, that's supposed to happen. That's the point of blocking.

@Earthshine this is what i'm trying to convey to you in some of my posts.

 

[Chicken0895]

Edit: Was user error. Doesn't look like I can delete this post though.

 

[phillyrider807]

Hey looking for some help here. I've been using my v1 switch online with cfw sysnand for years now as i do online pokemon giveaways and i use Livehex all the time. Never had any issues.

I recently updated my switch to 21.1.0 and since then i have not been able to connect online while using cfw sysnand (it works when using normal sysnand so i know my system is not banned)

I'm pretty sure this has something to do with exosphere/dns mitm but im not sure what im missing/what i have to add. Im using the latest HATS pack if that matters.

Any help?

 

[impeeza]

I'm pretty sure this has something to do with exosphere/dns mitm but im not sure what im missing/what i have to add. Im using the latest HATS pack if that matters.

Yes is because HATS package.

you must to know what is inside each package you install and be able to enable/disable each tinny thing you have on your system. by example the atmosphère settings and how they block some services if you like.

So if you do not know what are you doing stay away from prepackaged packages, and install everything by yourself.

in this case you need to setup your console to allow the communication, BUT BE AWARE if you run EmuNAND and SYSNAND and you let booth connect to ninja servers YOU WILL BE BANNED.

 

[phillyrider807]

Yes is because HATS package.

you must to know what is inside each package you install and be able to enable/disable each tinny thing you have on your system. by example the atmosphère settings and how they block some services if you like.

So if you do not know what are you doing stay away from prepackaged packages, and install everything by yourself.

in this case you need to setup your console to allow the communication, BUT BE AWARE if you run EmuNAND and SYSNAND and you let booth connect to ninja servers YOU WILL BE BANNED.

Yup i fixed it thanks.