Hacking Atmosphere-NX - Custom Firmware in development by SciresM

bth · 2026-09-30T08:02:29+0100

Hpshout said:
I've now manually added 90dns to my internet config just to stop any Nintendo pings at all... perhaps as expected the 'Test Connection' function now fails, which suggests the hosts file is indeed non-functional for sysmodules? Regardless of DNS settings in HOS the browser in Sphaira refuses to connect to any Nintendo server, but does work for say Google.

On a side note... did 23.0.0 improve Joycon connectivity at all? I've now switched from HATS to just creating my own setup with Atmosphere+Hekate+the stuff I want manually, and since 23.0.0 I have a lot more reliable Joycon connectivity now (before it was very sensitive to interference as if the range was very short). The things that could have caused issues I used to remove like MissionControl... so either 23.0.0 changed something or HATS broke something (I've heard they modify Atmosphere/package3/kernel/etc)

turns out the sysmodules just used sfdnsres ipc commands not implemented into atmosphere (that were new in 23.0.0), and that some others used the old ones, dns.mitm worked for the ones who used the old ones, and not the new ones.

atmosphere 1.12.1 will address that

Bigdrago · 2026-09-30T14:27:20+0100

bth said:
turns out the sysmodules just used sfdnsres ipc commands not implemented into atmosphere (that were new in 23.0.0), and that some others used the old ones, dns.mitm worked for the ones who used the old ones, and not the new ones.

atmosphere 1.12.1 will address that

Ninjas will address this and release 23.0.1 so even more consoles gets banned

alfonsovin · 2026-09-30T19:11:40+0100

Bigdrago said:
The fss0 configuration key was deprecated in Hekate v6.3.0 and replaced by the pkg3 key

I have this for hekate_ipl.ini

Code:

[config] autoboot=1 autoboot_list=0 bootwait=1 backlight=100 noticker=0 autohosoff=0 autonogc=1 updater2p=1 bootprotect=0 [CFW - emuMMC] pkg3=atmosphere/package3 emummcforce=1 cal0blank=1 icon=bootloader/res/emu_boot.bmp [Stock - sysMMC] pkg3=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/stock_boot.bmp

And exosphere.ini

Code:

[exosphere] debugmode=1 debugmode_user=0 disable_user_exception_handlers=0 enable_user_pmu_access=0 enable_mem_mode=0 blank_prodinfo_sysmmc=0 blank_prodinfo_emummc=1 allow_writing_to_cal_sysmmc=0 log_port=0 log_baud_rate=115200 log_inverted=0

And use these DNS servers in network settings from 90dns/Lava team:
163.172.141.219
207.246.121.77

One Question:
pkg3 ... changed, understood
exosphere.ini ... I have blank both sys and info (file inside config folder or root?)
ca0blank ... this is new for me. I added but question is if necessary in sysMMC

DNS in settings, not sure to use, I have some "host" files to block domains. Is it the same?
I run 90dns and everything is blocked

So, I would link know more about "serial and dns block network" to know which is the best

Just to clarify I only use sysmmc to copy some save games and sync game control to be recognised in Emummc
My Emummc is with 19.0 firmware
Any way just to be safe, with last version of atmosphere I have a mess

Other question
I load emummc and sysmmc with new atmosphere, I erase Mission Control
I use hekate to payload
but if I use fusee.bin to launch atmosphere from hekate or form PC I got a yellow scree. The fusee.bin is the new one for sure

Bigdrago · 2026-09-30T22:17:57+0100

alfonsovin said:
One Question:
pkg3 ... changed, understood
exosphere.ini ... I have blank both sys and info (file inside config folder or root?)
ca0blank ... this is new for me. I added but question is if necessary in sysMMC

DNS in settings, not sure to use, I have some "host" files to block domains. Is it the same?
I run 90dns and everything is blocked

So, I would link know more about "serial and dns block network" to know which is the best

Just to clarify I only use sysmmc to copy some save games and sync game control to be recognised in Emummc
My Emummc is with 19.0 firmware
Any way just to be safe, with last version of atmosphere I have a mess

Other question
I load emummc and sysmmc with new atmosphere, I erase Mission Control
I use hekate to payload
but if I use fusee.bin to launch atmosphere from hekate or form PC I got a yellow scree. The fusee.bin is the new one for sure

exosphere.ini should be placed in root
Source: https://github.com/Atmosphere-NX/Atmosphere/blob/master/docs/features/configurations.md
This file is located in the root of your SD

hekate_ipl.ini must be placed in the folder bootloader.

Use 163.172.141.219 (France) and 207.246.121.77 (USA) as DNS servers on your switch network settings.
Source: https://gitlab.com/a/90dns

I dont use fusee etc. to launch hekate since I have modchipped switch oled. Cant answer that question. I have renamed hekate file to payload.bin.

alfonsovin · 2026-09-30T22:41:06+0100

Bigdrago said:
exosphere.ini should be placed in root
Source: https://github.com/Atmosphere-NX/Atmosphere/blob/master/docs/features/configurations.md
This file is located in the root of your SD

hekate_ipl.ini must be placed in the folder bootloader.

Use 163.172.141.219 (France) and 207.246.121.77 (USA) as DNS servers on your switch network settings.
Source: https://gitlab.com/a/90dns

I dont use fusee etc. to launch hekate since I have modchipped switch oled. Cant answer that question. I have renamed hekate file to payload.bin.

Exosphere.ini and 90DNS are not the same-similar measurement?
Ca0blank too?

Bigdrago · 2026-09-30T23:12:21+0100

alfonsovin said:
Exosphere.ini and 90DNS are not the same-similar measurement?
Ca0blank too?

Do it all above to be safe. They are three different things to keep safe.

https://search.brave.com/ask?q=What...9#WArfE61SjkCZBBQQx7jkFl0DbdOGPS93P9I-lbHOLYo

impeeza · 2026-10-01T00:24:56+0100

alfonsovin said:
Exosphere.ini and 90DNS are not the same-similar measurement?
Ca0blank too?

Exosphere.ini is a Atmosphère's configuration file. for some settings like debug mode, blank prodinfo allow writing to CAL and setup Log Serial port.
90DNS is a dns server configuration on network settings
Ca0blank is a procedure for remove data on your console, can be done editing your ROM, using a sysmodule or via atmosphère settings.

Post automatically merged: Today at 2:56 AM

firmware 23.0.1 RELEASED!!

RobZilla10001 · 2026-10-01T03:30:56+0100

Fixed an issue from system version 23.0.0 where software occasionally took a long time to start, pause, or close.

bth · 2026-10-01T08:12:31+0100

nothing changed in 23.0.1, atmosphere will support it without problems, as all that was changed was some background stuff inside of sdb

Tinkerbell · 2026-10-01T09:11:41+0100

A question not exactly related to the update but not sure where else to ask it. My switch (mariko with kamikaze pico mod) boots into hekate when I charge it in the dock. I power it off completely beforehand but this still happens. Is this normal?

proconsule54 · 2026-10-01T09:13:44+0100

Only mayor releases are scary, minor less scary, micro version is more or less harmless

Bigdrago · 2026-10-01T09:24:15+0100

Tinkerbell said:
A question not exactly related to the update but not sure where else to ask it. My switch (mariko with kamikaze pico mod) boots into hekate when I charge it in the dock. I power it off completely beforehand but this still happens. Is this normal?

Normal. When you power if off quickly inserted it i to docking. If u are to slow it will power on.

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

¡Kabito!

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum