Toggle sidebar

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,818,310
  • Replies Replies 9,442
  • Likes Likes 93
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)
Click to expand...
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
 
  • Like
  • Love
Reactions: impeeza, Bigdrago, Hpshout and 5 others
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
Click to expand...

Ninjas will address this and release 23.0.1 so even more consoles gets banned😭
 
  • Haha
Reactions: impeeza
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
Click to expand...
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
 

Site & Scene News

New Hot Discussed User Submitted

Go to forum More news

Popular threads in this forum