Toggle sidebar

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,815,584
  • Replies Replies 9,434
  • Likes Likes 93
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:)
Click to expand...
Checking just in case. Having cal0blank=1 on all relevant boot entries in hekate_ipl.ini should blank it, right?
 
  • Like
Reactions: Tyvar1, Blythe93, impeeza and 2 others
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
 
Last edited by alfonsovin,
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?
Click to expand...
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.
 
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?
Click to expand...
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
 
  • Like
Reactions: Nephiel
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
Click to expand...
If I add these lines (or replace old ones) I'm good?

Don't wanna F things up.
 
  • Like
Reactions: Bigdrago
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
Click to expand...

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
 
Last edited by Bigdrago,
  • Like
Reactions: Tyvar1, johw, impeeza and 1 other person
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
Click to expand...
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
 
  • Like
Reactions: impeeza
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?
Click to expand...
How do I activate the 16MB?
 
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)
Click to expand...
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:

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.
Click to expand...
I'll have to set up one one of these days. :D
 
  • Like
Reactions: Tyvar1, Nephiel and impeeza
Blythe93 said:
Apparently DBI can get the right prodinfo while prodinfo is blanked
Click to expand...
I'm assuming this is fetching the backup file(s) atmosphere makes automatically on the sd card, not that there are many legitimate reasons for a homebrew to touch your console unique certificate.

the intent with blanking your console unique ssl certificate (thats whats in your prodinfo), is to make it so ssl communication (https) cannot be established, even if nintendos domains resolve correctly, for whatever reason.

also the feature being implemented into atmosphere had to do with the fork i ran for tinfoil back then, which became a big enough stink that he caved in and added it, alongside a setting to be able to read cal0 (and defaults being able to read it under emummc), also to counter the incognito / rcm / 2.0 variants that literally edited the prodinfo incorrectly
 
  • Love
  • Like
Reactions: Blythe93, Tyvar1, johw and 2 others
bth said:
We was at the "we are doomed" point right now, we only "stole back" 9MB in 23.0.0 by trimming down reserved memory pool 3 official applets use by using convoluted patches.

or well, the only people doomed are the ones who insist on running unecessary sysmodules
Post automatically merged:

supposedly dns.mitm isn't functional in 23.0.0 with atmosphere 1.12.0;

doesn't impact people who are banned from nintendos domains, or people who use third-party DNS servers / have prodinfo-blankers (such as the exosphere option).

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)
Click to expand...
When you say "my fork" do you mean Atmosphere being forked, or just the current one? Forgive my ignorance here!

I am unsure how some people's Switch seems to be downloading eShop updates for games though... mine does not connect to anything even nintendo.com via the browser
 
Last edited by Hpshout,
Hpshout said:
When you say "my fork" do you mean Atmosphere being forked, or just the current one? Forgive my ignorance here!
Click to expand...
He meant his fork with built in patches: https://github.com/borntohonk/Atmosphere/releases
Hpshout said:
I am unsure how some people's Switch seems to be downloading eShop updates for games though... mine does not connect to anything even nintendo.com via the browser
Click to expand...
Either banned, have prodinfo blanked already or 90DNS (or similar) doing its job? Most of the users just had DNS MITM set up and therefore it connected to the Nintendo servers when they went online after the firmware update.
 
Hpshout said:
When you say "my fork" do you mean Atmosphere being forked, or just the current one? Forgive my ignorance here!

I am unsure how some people's Switch seems to be downloading eShop updates for games though... mine does not connect to anything even nintendo.com via the browser
Click to expand...
"the browser" -> no such thing as an official browser provided by Nintendo or atmosphere.

theres a probability whatever homebrew you're referencing respects the hosts file (placebo), and doesn't actually query through sfdnsres ( nn::socket::resolver::IResolver ) which dns.mitm routes the queries through.
 

Site & Scene News

Go to forum More news

Popular threads in this forum