Hacking Atmosphere-NX - Custom Firmware in development by SciresM

Bigdrago · 2026-09-28T18:50:53+0100

Shaki123 said:
In plain English: with this Atmosphere updates the DNS blocking thing isn't working?

Yes.
https://github.com/Atmosphere-NX/Atmosphere/issues/2862
Enable prodinfo-blanker. Glad I have that as default on my configs

Nephiel · 2026-09-28T20:27:21+0100

Having a piHole or similar setup for the whole home is worth it any day, just for ads and malware. But on days like this, it pays off extra.

Bigdrago said:
Enable prodinfo-blanker. Glad I have that as default on my configs

Checking just in case. Having cal0blank=1 on all relevant boot entries in hekate_ipl.ini should blank it, right?

alfonsovin · 2026-09-28T20:28:19+0100

sure is a newbie question
update hekate and atmosphere
Boot Hekate 6.5.4 and boot Emummc working but not sys MMC, error

it could be Mission Control "content folder"

[Atmosphere (Emummc)]
fss0=atmosphere/package3
emummcforce=1
atmosphere=1
icon=bootloader/res/Atmoslogo.bmp
usb3force=1

[Atmosphere (sysMMC)]
fss0=atmosphere/package3
emummc_force_disable=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
usb3force=1

Shaki123 · 2026-09-28T20:30:10+0100

Nephiel said:
Having a piHole or similar setup for the whole home is worth it any day, just for ads and malware. But on days like this, it pays off extra.

Checking just in case. Having cal0blank=1 on all relevant boot entries in hekate_ipl.ini should blank it, right?

Just new to the whole thing but stuff like this makes my head spin. I'll just wait for the updates before I take the Switch out of Airplane Mode.

Bigdrago · 2026-09-28T20:32:13+0100

Nephiel said:
Having a piHole or similar setup for the whole home is worth it any day, just for ads and malware. But on days like this, it pays off extra.

Checking just in case. Having cal0blank=1 on all relevant boot entries in hekate_ipl.ini should blank it, right?

Yes, I have custom DNS as well

Removing malware and ads. But I feel sad for people not knowing this issue right now. Ninjas are celebrating.

In exosphere.ini
blank_prodinfo_emummc=1

and in hekate_ipl.ini :
[CFW - emuMMC]
pkg3=atmosphere/package3
emummcforce=1
cal0blank=1

Shaki123 · 2026-09-28T20:34:16+0100

Bigdrago said:
Yes, I have custom DNS as well Removing malware and ads. But I feel sad for people not knowing this issue right now. Ninjas are celebrating.

In exosphere.ini
blank_prodinfo_emummc=1

and in hekate_ipl.ini :
[CFW - emuMMC]
pkg3=atmosphere/package3
emummcforce=1
cal0blank=1

If I add these lines (or replace old ones) I'm good?

Don't wanna F things up.

Bigdrago · 2026-09-28T20:37:42+0100

alfonsovin said:
sure is a newbie question
update hekate and atmosphere
Boot Hekate 6.5.4 and boot Emummc working but not sys MMC, error

[Atmosphere (Emummc)]
fss0=atmosphere/package3
emummcforce=1
atmosphere=1
icon=bootloader/res/Atmoslogo.bmp
usb3force=1

[Atmosphere (sysMMC)]
fss0=atmosphere/package3
emummc_force_disable=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
usb3force=1

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

alfonsovin · 2026-09-28T22:06:25+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

Thank you I will review
I got working both system eliminate Mission Control that is not compatible with 23.0 firmware

PS: fusee.bin splash a yellow screen if try to use as payload (reboot payload.bin) or using in launcher PC. By now only use hekate payload to boot and reboot system

johw · 2026-09-28T22:51:15+0100

WuaZ said:
Trying to understand the sentence about the memory available for custom system modules, I looked at the previous release note and it is quite blurry for me. I hope someone can help me figuring it out.

Here is what I understood from changelog and discussions here:
- Prior to HOS 19.0.0 -> 40 MB available for custom modules (edited)
- HOS 19.0.0 -> 24 MB available (edited / thanks @Hayato213 for the correction)
- HOS 20.0.0 -> 14 MB available, but ams.mitm footprint reduced by 20 MB. Does this mean 14 MB or 34 MB available in the end?
- HOS 21.0.0 -> quantity available reduced by 10 MB, so @impeeza suggested 3.86 MB available and @SciresM answered the 19th of November 2025 that latest tests were given 16 MB
- HOS 23.0.0 -> quantity available reduced to 7 MB but Atmosphere team was able to "steal" 9 MB from Nintendo's modules, leading to 16 MB available back. Why the changeling mentioning "we can no longer launch browser applets (e.g.: eshop) without crashing."? Was 7 MB not enough for Atmosphere to run without any module installed by the user?

Is this summary correct? What happened with HOS 21.0.0? Is it recommended to upgrade to 23.0.0 or to remain on older HOS version?

How do I activate the 16MB?

impeeza · 2026-09-28T22:52:04+0100

johw said:
How do I activate the 16MB?

You do not need to do anything, atmosphère do it for you.

Blythe93 · 2026-09-28T23:19:05+0100

bth said:
it will however cause people who run nothing but dns.mitm, to send all and everything to nintendo, and have the people whom that happen to, end up being banned from dauth (eshop)
(my fork will now force enable the atmospheres prodinfo blanking option as consequence, and will keep it that way in the future)

Thanks for the info! I do remember hearing that blanking prodinfo is probably not enough and that SciresM added that feature just so that people would stop blanking their prodinfo and more often than not losing their prodinfo backup. Apparently DBI can get the right prodinfo while prodinfo is blanked and that makes me wonder if big N can do that as well? In any case, 90DNS or similar seems to be the go-to option for now.

Post automatically merged: 16 minutes ago

Nephiel said:
Having a piHole or similar setup for the whole home is worth it any day, just for ads and malware. But on days like this, it pays off extra.

I'll have to set up one one of these days.

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

Well-Known Member

Artificer

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

¡Kabito!

The Treasure Tracker

Similar threads

Popular threads in this forum