Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[helvetinperkeles]

You probably delete those custom covers, as for the error 0100000000000F12 it points to Fireau.

No i did not.

Post automatically merged: Nov 22, 2023

holy shite i got all works finally! It was just one outdated file and signpatch issue i had. All works and now i can start look at the original issue the dying battery
Now all modules are removed that i dont use and all are updated. Well see of my battery drains in the morning

 

[SkullHex2]

it seems I can't properly update Atmosphere: I'm sure I'm on 1.6.2, but the system settings keep saying I'm on 1.5.5
Anything I can do to fix this?

it could be relevant that I usually boot via Hekate and package3

 

[Freeman93]

I need some help from you guys. After the 17 update I got the prodinfo error, so I set it to 0 in the config. Everything booted fine after, so I set it to 1 again with DNS MITM and everything. But still the games want to update, and atmosphere doesn't seem to care about the exopshere.ini and hostfiles, also icognito in Tinfoil doesn't show (my serial is still blanked, but atmosphere folder shows the backup). Before the firmware update I also had to delete the atmosphere folder to get the new version to boot, maybe that messed things up? I now tried to reinstall the 17 fw to no avail.

So what am I doing wrong here, I've always used this configuration, and it worked like a charm.
Any advice would be much appreciated, thanks!

 

[Hayato213]

I need some help from you guys. After the 17 update I got the prodinfo error, so I set it to 0 in the config. Everything booted fine after, so I set it to 1 again with DNS MITM and everything. But still the games want to update, and atmosphere doesn't seem to care about the exopshere.ini and hostfiles, also icognito in Tinfoil doesn't show (my serial is still blanked, but atmosphere folder shows the backup). Before the firmware update I also had to delete the atmosphere folder to get the new version to boot, maybe that messed things up? I now tried to reinstall the 17 fw to no avail.

So what am I doing wrong here, I've always used this configuration, and it worked like a charm.
Any advice would be much appreciated, thanks!

Did you used incognito to blank out your serial?

 

[Freeman93]

Did you used incognito to blank out your serial?

Yes I did with Tinfoil before the Update, and its still blanked, but doesn't show in Tinfoil anymore. I didn't know I should have restored it, I had no need to change anything with other updates...

 

[impeeza]

it seems I can't properly update Atmosphere: I'm sure I'm on 1.6.2, but the system settings keep saying I'm on 1.5.5
Anything I can do to fix this?

it could be relevant that I usually boot via Hekate and package3

Please show us your hekate_ipl.ini file

 

[Hayato213]

Yes I did before the Update, and its still blanked. I didn't know I should have restored it, I had no need to change anything with other updates...

Restore it and then use exosphere with DNSMitm.

 

[impeeza]

Yes I did with Tinfoil before the Update, and its still blanked, but doesn't show in Tinfoil anymore. I didn't know I should have restored it, I had no need to change anything with other updates...

Block n seevers DnsMITM

 

[Freeman93]

Restore it and then use exosphere with DNSMitm.

How do I restore it without Tinfoil showing it?

Block n seevers DnsMITM

I did, and even added the more extensive server list @Hayato213 posted earlier

 

[Hayato213]

How do I restore it without Tinfoil showing it?


I did, and even added the more extensive server list @Hayato213 posted earlier

Tinfoil should have an option to restore it, you should be able to see the message clean backup found if you have one. I never used Incognito through Tinfoil though, so can't help too much on that. Alternative is to get prodinfo from nand backup.

 

[Freeman93]

Tinfoil should have an option to restore it, you should be able to see the message clean backup found if you have one. I never used Incognito through Tinfoil though, so can't help too much on that. Alternative is to get prodinfo from nand backup.

Thats exactly what I can't do unfortunately since Tinfoil doesn't show it anymore, I'll try to do it with the backup then somehow, thanks anyways!

 

[SkullHex2]

Please show us your hekate_ipl.ini file

Of course. Not much to show I'm afraid

Spoiler

[config]
autoboot=0
autoboot_list=0
bootwait=0
backlight=30
noticker=0
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

{-- Custom Firmwares --}
[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

 

[impeeza]

Of course. Not much to show I'm afraid

Spoiler

[config]
autoboot=0
autoboot_list=0
bootwait=0
backlight=30
noticker=0
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

{-- Custom Firmwares --}
[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

Upgrade your atmosphere folder WITH A RECENT DOWNLOADED package from GitHub

ALSO BE SURE YOU UPDATE YOUR PAYLOAD.BIN, if you use a RCM Launcher on that device, if you have a ModChip upgrade the SDMC:/payload.bin file, with the latest hekate from GitHub.

Post automatically merged: Nov 29, 2023

# Nintendo Main Servers
127.0.0.1 *nintendo.*
127.0.0.1 *nintendoswitch.*
127.0.0.1 *.nintendo.com
127.0.0.1 *.nintendo.net
127.0.0.1 *.nintendo.jp
127.0.0.1 *.nintendo.co.jp
127.0.0.1 *.nintendo.co.uk
127.0.0.1 *.nintendo-europe.com
127.0.0.1 *.nintendowifi.net
127.0.0.1 *.nintendo.es
127.0.0.1 *.nintendo.co.kr
127.0.0.1 *.nintendo.tw
127.0.0.1 *.nintendo.com.hk
127.0.0.1 *.nintendo.com.au
127.0.0.1 *.nintendo.co.nz
127.0.0.1 *.nintendo.at
127.0.0.1 *.nintendo.be
127.0.0.1 *.nintendods.cz
127.0.0.1 *.nintendo.dk
127.0.0.1 *.nintendo.de
127.0.0.1 *.nintendo.fi
127.0.0.1 *.nintendo.fr
127.0.0.1 *.nintendo.gr
127.0.0.1 *.nintendo.hu
127.0.0.1 *.nintendo.it
127.0.0.1 *.nintendo.nl
127.0.0.1 *.nintendo.no
127.0.0.1 *.nintendo.pt
127.0.0.1 *.nintendo.ru
127.0.0.1 *.nintendo.co.za
127.0.0.1 *.nintendo.se
127.0.0.1 *.nintendo.ch
127.0.0.1 *.nintendoswitch.com
127.0.0.1 *.nintendoswitch.com.cn
127.0.0.1 *.nintendoswitch.cn

# Nintendo Telemetry Servers
127.0.0.1 receive-%.dg.srv.nintendo.net receive-%.er.srv.nintendo.net

# Nintendo CDN Servers
95.216.149.205 conntest.nintendowifi.net
95.216.149.205 ctest.cdn.nintendo.net

Use this list

I have almost the same content, but in mine the *.nintendo are *nintendo... which are better?

 

[SkullHex2]

Upgrade your atmosphere folder WITH A RECENT DOWNLOADED package from GitHub

ALSO BE SURE YOU UPDATE YOUR PAYLOAD.BIN, if you use a RCM Launcher on that device, if you have a ModChip upgrade the SDMC:/payload.bin file, with the latest hekate from GitHub.

Post automatically merged: Nov 29, 2023

I have almost the same content, but in mine the *.nintendo are *nintendo... which are better?

Okay, I tried to upgrade again and it seems to work now. This time I replaced everything after connecting the Switch to a computer via Hekate. Previously I was only replacing stratosphere and package3 through Hekate (because they cannot be deleted while Atmosphere is running I guess) and everything else through FTP. I'll remember this for the future, thanks.

About DNS MITM, I don't think one is better than the other: if they work like normal regular expressions, then the first line of Hayato's list also includes every domain from the third line to *.nintendo.ch (while the second line covers the three after *.nintendo.ch). By removing the dot before “nintendo,” yours could block more domains but they would still be a subset of what *nintendo.* covers

 

[Nephiel]

About DNS MITM, I don't think one is better than the other: if they work like normal regular expressions, then the first line of Hayato's list also includes every domain from the third line to *.nintendo.ch (while the second line covers the three after *.nintendo.ch). By removing the dot before “nintendo,” yours could block more domains but they would still be a subset of what *nintendo.* covers

According to the DNS MITM documentation, it does not use regular expressions, however, it treats the * as a wildcard matching 0 or more characters wherever it appears. If multiple entries match the same hostname, then the last one will be used.

So, assuming that wildcard also matches dots (does it?), then, shouldn't this cover the same cases?

# Nintendo Main Servers
127.0.0.1 *nintendo.*
127.0.0.1 *nintendoswitch.*
127.0.0.1 *.nintendo-europe.com
127.0.0.1 *.nintendowifi.net
127.0.0.1 *.nintendods.cz

# Nintendo Telemetry Servers
127.0.0.1 receive-%.dg.srv.nintendo.net receive-%.er.srv.nintendo.net

# Nintendo CDN Servers
95.216.149.205 conntest.nintendowifi.net
95.216.149.205 ctest.cdn.nintendo.net

 

[SkullHex2]

According to the DNS MITM documentation, it does not use regular expressions, however, it treats the * as a wildcard matching 0 or more characters wherever it appears. If multiple entries match the same hostname, then the last one will be used.

So, assuming that wildcard also matches dots (does it?), then, shouldn't this cover the same cases?

# Nintendo Main Servers
127.0.0.1 *nintendo.*
127.0.0.1 *nintendoswitch.*
127.0.0.1 *.nintendo-europe.com
127.0.0.1 *.nintendowifi.net
127.0.0.1 *.nintendods.cz

# Nintendo Telemetry Servers
127.0.0.1 receive-%.dg.srv.nintendo.net receive-%.er.srv.nintendo.net

# Nintendo CDN Servers
95.216.149.205 conntest.nintendowifi.net
95.216.149.205 ctest.cdn.nintendo.net

Yeah, you're right: it cannot use regular expressions since the dot is a special character. This is clearly a different syntax.
The wildcard should also match dots, after all they are a particular collection of zero or more characters.

Anyways, program ID 0100000000000045 is consistently crashing on me. To reproduce: start charging the console, enter sleep mode, wait (I normally wait an hour or so, but I don't think it makes a difference); stop charging the console, crash occurs after one minute more or less. The log is attached.
Here's a list of installed homebrews:

Spoiler

This happens both on my Erista and on my Mariko.

 

[impeeza]

Yeah, you're right: it cannot use regular expressions since the dot is a special character. This is clearly a different syntax.
The wildcard should also match dots, after all they are a particular collection of zero or more characters.

Anyways, program ID 0100000000000045 is consistently crashing on me. To reproduce: start charging the console, enter sleep mode, wait (I normally wait an hour or so, but I don't think it makes a difference); stop charging the console, crash occurs after one minute more or less. The log is attached.
Here's a list of installed homebrews:

Spoiler

View attachment 407209
View attachment 407210
View attachment 407211

This happens both on my Erista and on my Mariko.

you could try the post:
https://gbatemp.net/posts/10121629/

 

[SkullHex2]

you could try the post:
https://gbatemp.net/posts/10121629/

I'm already using OvlSysmodules and nx-ovlloader-zdm-v1.0.7 (thanks btw). I'm not using Tesla itself, because I have Ultrahand.
Crashes could have started after installing them, but I wouldn't bet on it. Given I've only installed two of them, I'll try going back (starting with nx-ovlloader-zdm-v1.0.7) and see if the bug persists.

 

[impeeza]

I'm already using OvlSysmodules and nx-ovlloader-zdm-v1.0.7 (thanks btw). I'm not using Tesla itself, because I have Ultrahand.
Crashes could have started after installing them, but I wouldn't bet on it. Given I've only installed two of them, I'll try going back (starting with nx-ovlloader-zdm-v1.0.7) and see if the bug persists.

Also can you go to the ultrahand ovl thread and report your problem, may be a bug on int.

 

[rave420]

What is "package3", and what does it do? I don't really have any problems, I'm just curious. Package3 gets used by tools such as IPS Patch Creator, I'm just trying to understand what it is used for (that would require patching).