Hacking SX-OS emuNAND got corrupted. Error: 2002-4373

Phenj · Dec 5, 2018

Alright, today i just made my SD emuNAND offered by >TeamXecuter, at first it worked like charm, than troubles came.
First of all, my sysNAND is on 6.2 (online gaming, etc) and my emuNAND is on 6.1. Everything worked fine until i restarted my console, like normal, and SX-OS doesn't work anymore with emuNAND, after the Switch logo, a black screen with the error 2002-4373. sysNAND works fine. Why is this? What can i do? I do have a 6.1 NAND backup (boot01 included) just in case.
Thank you.

ZachyCatGames · Dec 5, 2018

The description of that error is "Error: Save data is corrupted". Idk if that helps at all

JJTapia19 · Dec 5, 2018

Not sure what caused your problem but if you're going to try creating emunand again format your sd card fat32 next time. It's better against random corruption like this one. Cons are that files larger than 4gb can't be moved to it but there are xci and nsp splitters and also installing nsp via external usb devices is really fast. Faster than using the sd card.

thaikhoa · Dec 5, 2018

Use HacDiskMount to open the first file of emunand in [sd:]\sxos\emunand\ if it can read. Then restore partitions from your previous backup (except USER because of splitted emunand, you can use copy /b cmd line to merge them in, give it a try then). exFAT won't easily corrupt just because of restart the system. Are you using trusted brand?

Always backup a copy of emunand ([sd:]\sxos\emunand\) just in case.

Zaide · Dec 5, 2018

Forgetting about the whole FAT32 vs exFAT thing, you should format your sd card and (while it's empty) run a full Write/Verify test with H2testw. If the scan finds bad sectors then your card is corrupting random data.

I had this happen. Took a couple times rebuilding my emuNAND before I finally narrowed down the culprit.

ssssss13 · Dec 5, 2018

Zaide said:
Forgetting about the whole FAT32 vs exFAT thing, you should format your sd card and (while it's empty) run a full Write/Verify test with H2testw. If the scan finds bad sectors then your card is corrupting random data.

I had this happen. Took a couple times rebuilding my emuNAND before I finally narrowed down the culprit.

So exfat corruption is that usual?

Phenj · Dec 5, 2018

thaikhoa said:
Use HacDiskMount to open the first file of emunand in [sd:]\sxos\emunand\ if it can read. Then restore partitions from your previous backup (except USER because of splitted emunand, you can use copy /b cmd line to merge them in, give it a try then). exFAT won't easily corrupt just because of restart the system. Are you using trusted brand?

Always backup a copy of emunand ([sd:]\sxos\emunand\) just in case.

I'll try this, thank you. Btw i am using FAT32, original Samsung SD bought from Amazon.

EDIT:
IT WORKED! Restoring files from a previous 6.1 NAND backup fixed my emuNAND.
Any way to restore my USER partition on FAT32? Nothing really important, just wondering.
EDIT 2:
Found the issue, sleep mode doesn't work on emuNAND, doesn't matter if AutoRCM is on or off. Just don't go in sleep mode.

llee8820 · Aug 1, 2019

Phenj said:
I'll try this, thank you. Btw i am using FAT32, original Samsung SD bought from Amazon.

EDIT:
IT WORKED! Restoring files from a previous 6.1 NAND backup fixed my emuNAND.
Any way to restore my USER partition on FAT32? Nothing really important, just wondering.
EDIT 2:
Found the issue, sleep mode doesn't work on emuNAND, doesn't matter if AutoRCM is on or off. Just don't go in sleep mode.

Yes I'm resurrecting an old thread, but I want to say googling this answer solved the same problem I had.
Twice I had my emunand put out an error 2002-4373. After the first time, I reformatted my card to fat32 instead thinking maybe exFAT corruption was the cause. Nope, the same thing happened a few days later.
I'm using a Samsung 256gb select EVO, I'm pretty sure it's official.

Each time this happens was when I powered on my switch from sleep mode. So you may be right that sleep mode is the culprit. But I don't know how to disable sleep mode nor do I want my switch to always be on if I do disable it.

Hopefully, this will help someone else that may experience this error in the future.

Blackguedes · Jan 20, 2020

I already had the "on files SD" emunand corrupted 4 times (2 in exFat and 2 in FAT32). The biggest concern, by far, is the saves, as the rest is easily reinstalled. I followed tutorial "Retrieving game saves from SX OS EmuNAND files after accidental 6.2.0 update using Wi-Fi OTA" from here, gbatemp , Which takes a lot of work, but it is possible to restore the emunand saves.

However, this last time, when the system even starts up, but it presents an SX OS error screen a few seconds later, it is not even possible to open Checkpoint to copy the saves, I found a way to fix the corrupted emunand, with all saves intact, since that you have some prior backup (or not*) .

- You will need to have Bis Key on your console (biskeydump);
- HacDiskMount;
- Corrupt file "full.00.bin" and previous backup "full.00.bin" (or doing another *).

1- In HacDiskMount, open the corrupted full.00.bin file, directly from your SD, then double-click on SYSTEM and mount the partition with the respective BIS KEYS (Drive letter: Y);
2- Do the same with the file full.00.bin from your previous backup (Drive letter: Z);
3- Now you will have two virtual drives (Y and Z), as if they were HDs. Just delete all files from drive Y and copy everything from drive Z to Y. It takes about 5 minutes;
4- Unmount both virtual drives and try to use the SD on the switch normally.

* If you have not backed up the emunand in the firmware that was installed, just take any backup of the previous emunand, or make a totally new one, and update to exactly the same version, then use the full.00.bin of this "healthy" emunand .

uriel831 · Nov 2, 2020

Blackguedes said:
I already had the "on files SD" emunand corrupted 4 times (2 in exFat and 2 in FAT32). The biggest concern, by far, is the saves, as the rest is easily reinstalled. I followed tutorial "Retrieving game saves from SX OS EmuNAND files after accidental 6.2.0 update using Wi-Fi OTA" from here, gbatemp , Which takes a lot of work, but it is possible to restore the emunand saves.

However, this last time, when the system even starts up, but it presents an SX OS error screen a few seconds later, it is not even possible to open Checkpoint to copy the saves, I found a way to fix the corrupted emunand, with all saves intact, since that you have some prior backup (or not*) .

- You will need to have Bis Key on your console (biskeydump);
- HacDiskMount;
- Corrupt file "full.00.bin" and previous backup "full.00.bin" (or doing another *).

1- In HacDiskMount, open the corrupted full.00.bin file, directly from your SD, then double-click on SYSTEM and mount the partition with the respective BIS KEYS (Drive letter: Y);
2- Do the same with the file full.00.bin from your previous backup (Drive letter: Z);
3- Now you will have two virtual drives (Y and Z), as if they were HDs. Just delete all files from drive Y and copy everything from drive Z to Y. It takes about 5 minutes;
4- Unmount both virtual drives and try to use the SD on the switch normally.

* If you have not backed up the emunand in the firmware that was installed, just take any backup of the previous emunand, or make a totally new one, and update to exactly the same version, then use the full.00.bin of this "healthy" emunand .

For step 3, do you actually mean to delete all files from drive Z(Healthy Emunand) and then transfer all file from corrupt bin (drive Y) to Z?

Draxzelex · Nov 10, 2020

uriel831 said:
For step 3, do you actually mean to delete all files from drive Z(Healthy Emunand) and then transfer all file from corrupt bin (drive Y) to Z?

That user hasn't logged on in months and this thread is even older than that but based on what he said, basically yes. You can have another backup of Z in case you're paranoid.

Gabsbroni · Dec 4, 2020

He said:
"...or make a totally new one, and update to exactly the same version, then use the full.00.bin of this 'healthy' emunand"

Anybody knows how could I see in which firmware my emunand is in that case of corrupting?
I just can't remmember the firmware since I didn't toke the Switch to play in like 4 months and choosed to don't update it regularly.
Please somebody help me revive my Switch

Draxzelex · Dec 11, 2020

Gabsbroni said:
He said:
"...or make a totally new one, and update to exactly the same version, then use the full.00.bin of this 'healthy' emunand"

Anybody knows how could I see in which firmware my emunand is in that case of corrupting?
I just can't remmember the firmware since I didn't toke the Switch to play in like 4 months and choosed to don't update it regularly.
Please somebody help me revive my Switch

Use NX-NAND Manager.

Hacking SX-OS emuNAND got corrupted. Error: 2002-4373

Well-Known Member

Well-Known Member

I fight for my friends.

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

New Member

Member

Well-Known Member

Member

Well-Known Member

Similar threads

Popular threads in this forum