Hacking Homebrew Error Code 2002-4373 (0x222a02) Switch crashing on startup

[Inkwell]

My Switch has been working fine up until I booted up Smash an hour ago, then it crashed and now everytime I try to boot into my emunand, I can make it to the homescreen but the Switch will then crash by itself about 5 seconds in. How do I fix this? Error Code: 2002-4737 (0x222x02) Program: 010000000000000C. I'll attach the crash report log that Atmosphere generated

 

[kenlee168]

Exfat formatted sdcard?
I experienced too many random file corruption using exfat, maybe it might be that in your case.

 

[kenlee168]

Did a google search and found similar error code
https://forums.warframe.com/topic/1278872-game-data-corrupted-error-2002-4373/

 

[Inkwell]

Hmm my SD Card is Fat32 Formatted

 

[Inkwell]

And Switchroot Android still works fine on the same SD Card too, which I find odd

 

[binkinator]

And Switchroot Android still works fine on the same SD Card too, which I find odd

Absolutely no other changes? No accidental updates or anything?

Try booting to Hekate and run Fix Archive bit. Long shot but it might fix.

next step would be to rename /atmosphere/contents to /atmosphere/contents.bak and reboot. Easy to put back if it doesn’t fix.

do yiu have another sd card we can test with? Would love to take this down to just stock atmosphere and Hekate on a different sd card.

 

[Inkwell]

Just tried both of those, and I still get the same error and crash :c. I do have two other SD Cards that I use and they're all Samsung Evo brand (a 64GB one for my phone and 256GB for my stock Switch, the one I use for this homebrewed Switch is 512GB)

 

[binkinator]

Just tried both of those, and I still get the same error and crash :c. I do have two other SD Cards that I use and they're all Samsung Evo brand (a 64GB one for my phone and 256GB for my stock Switch, the one I use for this homebrewed Switch is 512GB)

We just need a little one to test and then we can give it right back. Is there a ton of stuff on the 64G phone one?

What version of switch are you on?
RCM or Chipped?
Firmware version?
Version of Hekate/Atmosphere?

We can get this set up on the 64G sd card pretty easy just doing a default Deploy: https://rentry.org/SwitchHackingIsEasy

 

[Inkwell]

Ah, sorry for the late reply. My 64GB SD Card is half full so I should be able to use it. My homebrewed Switch uses RCM and is on FW 13.2.1 with Atmosphere 1.2.6

 

[binkinator]

Ah, sorry for the late reply. My 64GB SD Card is half full so I should be able to use it. My homebrewed Switch uses RCM and is on FW 13.2.1 with Atmosphere 1.2.6

You’ll have to back it up some where unless you have an idea for getting an emunand onto the card without formatting…

Here’s a decent guid on the topic to get yiu the basics: https://rentry.org/SwitchHackingIsEasy

 

[Inkwell]

Thanks! My files are backing up rn so I can format my phone's SD Card as Fat32. How will I be using this second emunand?

 

[binkinator]

Thanks! My files are backing up rn so I can format my phone's SD Card as Fat32. How will I be using this second emunand?

Emunand is for arrrr-ware. If you follow the guide it will blank out your prodinfo with 0000s (similar to Incognito_RCM but without changing your data on disk and risking losing it) and poison your local dns to prevent contact with Ninty (similar to 90DNS but without the external dependency.)

Sysnand should be completely clean at all times.

This prevents briics and reduces the likelihood of bans.

 

[Inkwell]

Is my 64GB SD Card replacing the 512GB one?
Also, I just found something out, while I waiting for the phone files to transfer I was curious and decided to see if I could peak at my emunand with nxnandmanager and I found out that its partition is formated as exfat, even though the rest of my SD Card was formatted as Fat32, even though I recall having created that emunand from Hekate itself haha

 

[binkinator]

Is my 64GB SD Card replacing the 512GB one?
Also, I just found something out, while I waiting for the phone files to transfer I was curious and decided to see if I could peak at my emunand with nxnandmanager and I found out that its partition is formated as exfat, even though the rest of my SD Card was formatted as Fat32, even though I recall having created that emunand from Hekate itself haha

Just temporarily. Want to see if it’s the main card + want to start from scratch on atmosphere + Hekate…everything default. Super simple, super clean…divide and conquer the problem so we can isolate it.

Emunand is exfat?!?! That’s kinda sketchy if true…could be our issue all along. We will come to know shortly…

 

[Inkwell]

Okay, I have the new emunand and it's working! (The Atmosphere CFW option is emunand right? I followed a different guide when I first did this XD) I don't have any extra homebrew stuff or files on it but what the guide said on it except for the tegraexplorer payload (so I could format it to fat32 before creating the emunand)

 

[binkinator]

Okay, I have the new emunand and it's working! (The Atmosphere CFW option is emunand right? I followed a different guide when I first did this XD) I don't have any extra homebrew stuff or files on it but what the guide said on it except for the tegraexplorer payload (so I could format it to fat32 before creating the emunand)

Correct. Atmosphere CFW is emunand.

So everything is working? 100%?

If so,
How much stuff so you have on the larger card?
Is it easily rebuildable from various sources around the web such that we can simply delete and rebuild or is it more like a highly unique set of games and configs that will make us want to preserve it?

 

[Inkwell]

My 512GB is a few GB shy of being completely filled up, if it's possible to preserve all the content I have on it I hope there's a way to

Hmmm...nxnandmanager says the emunand partition here is also exfat, while the rest of the sd card is Fat32 just like the original one. Is it supposed to be like that?

 

[Inkwell]

 

[Inkwell]

Correct. Atmosphere CFW is emunand.

So everything is working? 100%?

If so,
How much stuff so you have on the larger card?
Is it easily rebuildable from various sources around the web such that we can simply delete and rebuild or is it more like a highly unique set of games and configs that will make us want to preserve it?

After looking into it some more I think I found the main culprit. When going over that fatal report, the process that was involved in this error was "bcat" which I recall seeing in the past in JKSV, and this leads me to believe something got corrupted with the save files, which could be plausible seeing how this crash only began when booting up a game, particularly Smash, and nothing else. How that happened is still something I don't understand, since I've boot into Smash once on it before (but maybe it had something to do with save injection, which I did a few days ago so I could unlock all the characters to start modding the game and it did work at the time, the latter of which I never gone around to doing, but why it would work then and suddenly not now makes me question if that is the true cause, and I have another reason which I'll bring up later that that might not be the case). I've backed up this emunand (and saves) to my computer so I could start messing around with the files inside of its partition and so I mounted "User" from the "internal storage" of the emunand, and I've stumbled across this folder called "saveMeta," where there happens to be a stray file (000000001.meta) among all the folders and when I try to copy it to a separate folder on my computer, says that "This is no located in I:/saveMeta. Verify the item's location and try again." Unfourtently, because it was not found in its own folder I can not detect which game it could have belonged to, but I know this couldn't have been the Smash data because it was last modified on 3/16/22 at 2:38 PM, which is not when I did that save injection. Would you happen to know what "saveMeta" really is and would you know if this is supposed to be how the file structure works? Interestingly I can't delete it either, so I'm led to believe this is the particular file that was corrupted, but why that would crash the whole system rather than affect just a particular game is beyond me for now, and am curious to know if I can use a different program than Windows File Manager to do something about that one file. (Oh! Before I forget, I found out that my emunand is already Fat32, I was just looking somewhere that wasn't intended to indicate what format it was supposed to be. Selecting each partition of emunand manually in nxnandmanager shows they are Fat32)

 

[binkinator]

My 512GB is a few GB shy of being completely filled up, if it's possible to preserve all the content I have on it I hope there's a way to

Thats a ton of data…you might have to try to piece it back together in place.

After looking into it some more I think I found the main culprit. When going over that fatal report, the process that was involved in this error was "bcat" which I recall seeing in the past in JKSV, and this leads me to believe something got corrupted with the save files, which could be plausible seeing how this crash only began when booting up a game, particularly Smash, and nothing else. How that happened is still something I don't understand, since I've boot into Smash once on it before (but maybe it had something to do with save injection, which I did a few days ago so I could unlock all the characters to start modding the game and it did work at the time, the latter of which I never gone around to doing, but why it would work then and suddenly not now makes me question if that is the true cause, and I have another reason which I'll bring up later that that might not be the case).

this feels right though…fantastic sleuth work.

I've backed up this emunand (and saves) to my computer so I could start messing around with the files inside of its partition and so I mounted "User" from the "internal storage" of the emunand, and I've stumbled across this folder called "saveMeta," where there happens to be a stray file (000000001.meta) among all the folders and when I try to copy it to a separate folder on my computer, says that "This is no located in I:/saveMeta. Verify the item's location and try again." Unfourtently, because it was not found in its own folder I can not detect which game it could have belonged to, but I know this couldn't have been the Smash data because it was last modified on 3/16/22 at 2:38 PM, which is not when I did that save injection. Would you happen to know what "saveMeta" really is and would you know if this is supposed to be how the file structure works?

I’m just as curious as you are on this. i’ve not messed with the save files at this level so I don’t know what should/should not be there.

Interestingly I can't delete it either, so I'm led to believe this is the particular file that was corrupted, but why that would crash the whole system rather than affect just a particular game is beyond me for now, and am curious to know if I can use a different program than Windows File Manager to do something about that one file.

Possible, but have backups before yiu tear things up…this could be protected because it‘s important.

(Oh! Before I forget, I found out that my emunand is already Fat32, I was just looking somewhere that wasn't intended to indicate what format it was supposed to be. Selecting each partition of emunand manually in nxnandmanager shows they are Fat32)

Whew! That would have been really wild if it was exfat.