18.0.1 crash - Atmosphere

[Ideal_]

Hello, I am having a persistent crash issue after updating my system to 18.0.1. Generally after about 10 seconds of being on the system will crash to the Atmosphere error screen.

Atmosphere is updated to the latest version. Methods tried for fixing the problem - deleting "Contents" folder under Atmosphere as suggested elsewhere, booting through Hekate, booting Hekate with fss0 (fss0=sept), deleting atmosphere folder and replacing it on the Sd card.

Any advice or guide appreciated.

 

[Badablek]

Hi,

you should post the error screen, because it can be a lot of things :

• an old sysmodule, not compatible 18.0.0+
• an hidden/deleted prodinfo without dns_mitm or 90DNS (since firmware 17.0.0+)
• a theme
• ...

BTW it seems to be a missing/hidden PRODINFO, as Atmosphere boots correctly, then crashes. Since firmware 17.0.0+, atmosphere will crash the second you try to use WIFI without 90DNS or dns_mitm enabled

ps : it should be fss0=atmosphere\package3 in hekate_ipl.ini, no ?

 

[Ideal_]

Hi,

you should post the error screen, because it can be a lot of things :

• an old sysmodule, not compatible 18.0.0+
• an hidden/deleted prodinfo without dns_mitm or 90DNS (since firmware 17.0.0+)
• a theme
• ...

BTW it seems to be a missing/hidden PRODINFO, as Atmosphere boots correctly, then crashes. Since firmware 17.0.0+, atmosphere will crash the second you try to use WIFI without 90DNS or dns_mitm enabled

ps : it should be fss0=atmosphere\package3 in hekate_ipl.ini, no ?

Thanks! Very helpful.

Edit: I installed incognito forever ago and never had a problem. Did an update (system or atmosphere) change how this worked?

 

[Badablek]

Did an update (system or atmosphere) change how this worked?

yes, since firmware 17.0.0, if your PRODINFO is erased (incognito) or hidden (exosphere), HorizonOS will crash when trying to reach Nintendo servers.
Reason why you absolutely need to block it (by using 90DNS or dns_mitm) or unhide/restore your PRODINFO

https://github.com/Atmosphere-NX/Atmosphere/issues/2215
https://github.com/Atmosphere-NX/Atmosphere/issues/2208
https://github.com/Atmosphere-NX/Atmosphere/issues/2231

and as "it's not a bug, it's a feature", this behavior will not be patched in any way by SciresM (if I understood correctly)

 

[4d1xlaan]

just patch out the check

https://github.com/fruityloops1/nim-prodinfo-blank-fix

 

[Badablek]

just patch out the check

https://github.com/fruityloops1/nim-prodinfo-blank-fix

nice finding
(but as IPS patching was removed in fusee, this must be used with Hekate + fss0 boot method)

 

[xawak67952]

Well im not getting any crash on my console but instead a lot of this files are generated in erpt_report folder.
Are you guys also have them? No idea if i should disable exosphere blanking or look for other solution.
This started happening on 18.0.0+, never had any problem on 17.0.0

strings d4be6ad9-f854-c94c-5fd9-a18b1d7de0dd
............
OsVersion
18.0.1
PrivateOsVersion
1NintendoSDK Firmware for NX 18.0.1-1.0 (8cf56436)
SerialNumber
XAW00000000000
ReportIdentifier
$d96abed4-54f8-4cc9-5fd9-dde07d1d8ba1 <-- filename
OccurrenceTimestamp
OccurrenceTimestampNet
ReportVisibilityFlag
OccurrenceTick
SteadyClockInternalOffset
 SteadyClockCurrentTimePointValue
ElapsedTimeSincePowerOn
ElapsedTimeSinceLastAwake
RegionSetting
Europe
VideoOutputSetting
ProductModel
AbortFlag
ErrorCode
2123-0011
ThreadName
nn.olsc.EventHandler
CipherKey

 

[4d1xlaan]

nice finding
(but as IPS patching was removed in fusee, this must be used with Hekate + fss0 boot method)

this is an exefs patch, not a kip patch

 

[Badablek]

this is an exefs patch, not a kip patch

great news !

(I thought every IPS patching was removed, but now I realize it would be dumb because it won't allow any cheat codes if it was the case...)

 

[4d1xlaan]

great news !

(I thought every IPS patching was removed, but now I realize it would be dumb because it won't allow any cheat codes if it was the case...)

yeah, that and stuff like missioncontrol

it's just kip patches because the only kip patches were for piracy, but exefs patches have a lot of other uses so far