Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[bth]

From my emummc (with fw 21.0) I accidentally launched a homebrew not updated to properly work on fw21+ and when I closed it I got an atmosphere error.
Now every time I try to boot on emummc I get this same error (program: 010000000000001E).
I tried to clean the micro SD card with a minimal atmosphere + hekate config but still the same error.
How screwed am I ?

0x4E4EC is a svc (0x21, https://switchbrew.org/wiki/SVC#SendSyncRequest) that is sent a 0x100 value from (in this case from 0x38ed0), which 0x38ed0.

as to what exactly is failing to sync to what, im not sure. which homebrew did you launch?

 

[its-my-right]

0x4E4EC is a svc (0x21, https://switchbrew.org/wiki/SVC#SendSyncRequest) that is sent a 0x100 value from (in this case from 0x38ed0), which 0x38ed0.

as to what exactly is failing to sync to what, im not sure. which homebrew did you launch?

Thanks for the detailed inputs.
I launched totk unexplored (https://github.com/lud99/totk-unexplored), it worked as intended and then I closed it with "+" and from there I get this error

 

[bth]

Thanks for the detailed inputs.
I launched totk unexplored (https://github.com/lud99/totk-unexplored), it worked as intended and then I closed it with "+" and from there I get this error

https://github.com/lud99/totk-unexplored/blob/main/source/Main.cpp#L273

seems normal to me, not sure why that would/should crash your console so hard your account data bricks

 

[its-my-right]

https://github.com/lud99/totk-unexplored/blob/main/source/Main.cpp#L273

seems normal to me, not sure why that would/should crash your console so hard your account data bricks

totk-unexplored requires user selection upon opening to read the totk game save, so the connection to the user account is probably there.

Since the homebrew wasn't recompiled with libnx >=4.10.0, I imagine memory corruption or something similar has occurred.
Now I wonder whether this is fixable in some way, or if I have to recreate an emummc.

 

[impeeza]

From my emummc (with fw 21.0) I accidentally launched a homebrew not updated to properly work on fw21+ and when I closed it I got an atmosphere error.
Now every time I try to boot on emummc I get this same error (program: 010000000000001E).
I tried to clean the micro SD card with a minimal atmosphere + hekate config but still the same error.
How screwed am I ?

You have your prodinfo blanked? Try to restore your original prodinfo, or use sys-patch

 

[its-my-right]

You have your prodinfo blanked? Try to restore your original prodinfo, or use sys-patch

Thanks for your help. I tried putting back blank_prodinfo_emummc to 0 in exosphere.ini, also tried without exosphere.ini, and made sure all sigpatches have been removed, but still have this same error. My micro SD now is with a very minimal setup (latest hekate + atmosphere only) and no luck so I guess I'll have to make a new emummc

 

[impeeza]

Thanks for your help. I tried putting back blank_prodinfo_emummc to 0 in exosphere.ini, also tried without exosphere.ini, and made sure all sigpatches have been removed, but still have this same error. My micro SD now is with a very minimal setup (latest hekate + atmosphere only) and no luck so I guess I'll have to make a new emummc

Put sys-patch sysmodule

 

[its-my-right]

Put sys-patch sysmodule

Thanks, I tried that also (latest version 1.5.8-v5) but still the same error

 

[impeeza]

sorry for the mistake, 010000000000001E is account service.

Yo may be your acconts got corrupted, try to star the emunand on recovery mode.

 

[john87]

I have PRODINFO completely blanked using Incognito through NxNANDManager (I prefer it over Exosphere since Russian malware like DBI can read your Serial even if you use Exosphere) and I don’t have any issues. In fact, I don’t have Exosphere at all (I don’t have an exosphere.ini in the root of the MicroSD).

On my console, the serial number doesn’t appear when I try to check it, not even all zeros. And I don’t have any problems; that said, I do use sys-patch.

 

[NeoGranzon]

Guys have a request:you could create a thread with all the updated homebrews for OFW 21.0.0&CFW 1.10.0,so you can find them right away like @impeeza did for the sys-patches?

 

[Asia81]

Guys have a request:you could create a thread with all the updated homebrews for OFW 21.0.0&CFW 1.10.0,so you can find them right away like @impeeza did for the sys-patches?

literally the first thread on the forum https://gbatemp.net/threads/prelimi...0-ams-1-10-0-please-add-your-findings.677217/

 

[NeoGranzon]

literally the first thread on the forum https://gbatemp.net/threads/prelimi...0-ams-1-10-0-please-add-your-findings.677217/

@Asia81 thank you so much,i hadn't seen it.

 

[its-my-right]

sorry for the mistake, 010000000000001E is account service.

Yo may be your acconts got corrupted, try to star the emunand on recovery mode.

I'm not sure what you mean by trying to start the emunand on recovery mode.
I start it via Hekate as I always do and I'm not sure how to start it in a different way

 

[impeeza]

I'm not sure what you mean by trying to start the emunand on recovery mode.
I start it via Hekate as I always do and I'm not sure how to start it in a different way

launch the emunand on hekate, but press and keept pressed the VOL + and VOL - buttons

 

[NeoGranzon]

I'm not sure what you mean by trying to start the emunand on recovery mode.
I start it via Hekate as I always do and I'm not sure how to start it in a different way

@its-my-right i also got that error during installation with NS USBloader from my smartphone.
Now if itry with Awoo Installer from my smartphone with games larger than 3GB,i get the error 010000000000012 with the Poco X7 Pro (Android 15),while with the Galaxy Note 9 (Android 10) i can install games of the same size and even larger without problems.
I still haven't figured out what causes this error: the low RAM of the Switch or the smartphones.

 

[its-my-right]

launch the emunand on hekate, but press and keept pressed the VOL + and VOL - buttons

Thanks, I just tried that too (reset without erasing saves data) but then I still have an atmosphere error at emummc boot.
But the error is different now: error code 2002-4686 with program ID 010000000000001f

 

[impeeza]

Thanks, I just tried that too (reset without erasing saves data) but then I still have an atmosphere error at emummc boot.
But the error is different now: error code 2002-4686 with program ID 010000000000001f

May be the firmware of the Cartdrige reader is newer than your EmuNAND, remove the cartdrige and if the emunand boot, you should upgrade it.

Post automatically merged: Nov 20, 2025

also look on this atmosphere issue

https://github.com/Atmosphere-NX/Atmosphere/issues/1437

 

[its-my-right]

May be the firmware of the Cartdrige reader is newer than your EmuNAND, remove the cartdrige and if the emunand boot, you should upgrade it.

Post automatically merged: Nov 20, 2025

also look on this atmosphere issue

https://github.com/Atmosphere-NX/Atmosphere/issues/1437

Thanks for you help, but nothing worked. Fresh Emunand it is. But be very careful of what homebrew you launch on cfw 21.0+ !!!

 

[hexdec1a4]

Has PPSSPP been updated? If not, would someone mind fixing it? please haha