Error Code 2123-0011 (0x167b)

[jamfrancisc0]

Bug Report

[ If any section does not apply, replace its contents with "N/A". ]
[ Lines between [ ] (square brackets) should be removed before posting. ]

[ * ]
[ Note: If the bug or crash you encountered is related to; ]
[ - software used to make "backups", ]
[ - software explicitly distributed for piracy, etc ]
[ then contributors will not provide support for your issue and your issue will be closed. ]

What's the issue you encountered?

Once updating atmosphere and booting up an existing emunand it crashes withing a few seconds with error code 2123-0011, ive tried twice now it happened the same both times

How can the issue be reproduced?

[ * ]
boot into hekate and click on emummc then just wait

Crash Report

(https://gist.github.com/jamfrancisc0/8fc6b70846a23df3035b0f40ea4e2f85)

System Firmware Version

19.0.0

Environment?

used hekate to load a partition based emummc

Additional context?

[borntohonk]

@jamfrancisc0 see https://github.com/Atmosphere-NX/Atmosphere/issues/2225 The solution is for you to either reverse engineer NIM and create patch that removes the fatal condition, or...

edit exosphere.ini like this, to whichever line you have set to 1. (this is not new in 19.0.0, this has been like this since 17.0.0) blank_prodinfo_sysmmc=0 blank_prodinfo_emummc=0

"cal0blank=0" if hekate_ipl.ini

[jamfrancisc0]

@borntohonk both are already at 0 in exosphere.ini, cant find cal0blank in hekate_ipl should i create it?

[borntohonk]

@borntohonk both are already at 0 in exosphere.ini, cant find cal0blank in hekate_ipl should i create it?

You probably used "incognito" at some point then, which is irreversible without a backup of your prodinfo

[wakoyname]

if both are already at 0 in exosphere.ini:

1. try to check if theres another exosphere.ini in root folder and delete it
2. go to atmosphere > config > system_settings find: enable_dns_mitm = u8!0x1 and change it to: ; enable_dns_mitm = u8!0x1

find: add_defaults_to_dns_hosts = u8!0x1 and change it to: ; add_defaults_to_dns_hosts = u8!0x1

3. go to atmosphere > config_templates > system_settings find: enable_dns_mitm = u8!0x1 and change it to: ; enable_dns_mitm = u8!0x1

find: add_defaults_to_dns_hosts = u8!0x1 and change it to: ; add_defaults_to_dns_hosts = u8!0x1

[wakoyname]

also delete atmosphere > hosts > default.txt

[jamfrancisc0]

@borntohonk @wakoyname nothing seems to work, theres nothing even in atmosphere>config and ive deleted default.txt but no joy, any ideas to fix the problem thats not above my pay grade as im no expert? if i wipe the sd and start a new emunand will it have the same fault?

[borntohonk]

@borntohonk @wakoyname nothing seems to work, theres nothing even in atmosphere>config and ive deleted default.txt but no joy, any ideas to fix the problem thats not above my pay grade as im no expert? if i wipe the sd and start a new emunand will it have the same fault?

I've already responded to you and provided you your realistic options.

No need to tag me further, do with the options you have.

Undo incognito/incognito_rcm, or, alternatively, reverse engineer a patch for NIM to remove the fatal (repeated for every firmware version released)

a new emunand would have the same occur if your "sysnand" is where you applied "incognito".

[jamfrancisc0]

@borntohonk sorry i wont bother you anymore i just have no idea how to even begin reverse engineering a patch so i was hoping for another solution. thanks for the help anyway :)

[wakoyname]

then downgrade is your only option. you can still play games on fw version 18.1.0 using atmos 1.7.1, why update?