Hacking [QUESTION] Am I able to recover my old emuNAND from ReiNAND?

[Romruto]

Some backstory.... I formatted my sd card due to it freezing before all of this. During my wanting to play this 3DS again, I turned it on and loaded into Rei's emuNAND as normal. Then I downloaded the new update files for ReiNAND. After that, I turned on my 3DS as normal and proceeded to use Rei. I thought to update the CFW on Rei to today's Nintendo 3DS FW. After that, things acted up strange like not loading into the System Settings and stalling until I had to hard shut down. It happened again and again, so I decided to use a backup of my old files before I updated ReiNAND files and Rei's emuNAND CFW. At this point, it stopped loading into the emuNAND and gave a black screen. Then I tried to format the SD card and move the backup'd files onto the sd card once more and nothing still. And finally, I ended up here asking questions about what to do.

Question(s):
After installing everything from this https://3ds.guide/homebrew-launcher-(soundhax) GUIDE, from start to finish, and still having the folder that has my 3DS savedata & rei files, am I able to recover my emuNAND?

This may be too late, but when I tried to backup my rei's emuNAND, during the step about backing up the sysNAND from the 3ds guide page, everything listed in GODMODE was only sysNAND and there was no emuNAND present to select from. Also, I highly believe that my New3DS was unlinked from the sysNAND and rei's emuNAND.

So even if they were unlinked and nothing was showing emuNAND in the list in GODMODE, was it even possible to recover my ReiNAND's emuNAND?

 

[Clothahump]

Then I tried to format the SD card and move the backup'd files onto the sd card once more and nothing still.

This is where you killed your emuNAND. See, your 3DS' operating system has files both on its internal flash and the SD card (inside the folder named "Nintendo 3DS"). What emuNAND does is basically creating a new partition on your sd card equal the size of your 3DS' internal memory, and then copying all the files off that onto the new partition. CFWs can then choose to redirect all file operations going from and to NAND to your emuNAND partition on your SD card.

When you formatted your SD card, you more than likely killed that emuNAND partition (unless you specifically backed that up too), leaving you with the files from your visible data partition only. While it's true that most sava data for installed titles resides there, that stuff is encrypted using console-specific encryption, which (correct me if I'm wrong) even changes for your emuNAND when you unlink NANDs. If true, that would mean that you can't retrieve your emuNAND savedata at this point, even though you still have most of it backed up.

 

[Romruto]

This is where you killed your emuNAND. See, your 3DS' operating system has files both on its internal flash and the SD card (inside the folder named "Nintendo 3DS"). What emuNAND does is basically creating a new partition on your sd card equal the size of your 3DS' internal memory, and then copying all the files off that onto the new partition. CFWs can then choose to redirect all file operations going from and to NAND to your emuNAND partition on your SD card.

When you formatted your SD card, you more than likely killed that emuNAND partition (unless you specifically backed that up too), leaving you with the files from your visible data partition only. While it's true that most sava data for installed titles resides there, that stuff is encrypted using console-specific encryption, which (correct me if I'm wrong) even changes for your emuNAND when you unlink NANDs. If true, that would mean that you can't retrieve your emuNAND savedata at this point, even though you still have most of it backed up.

Oh okay, I figured that was the case. Thank you for the reply.