Hacking How does SX OS Emunand work?

[RedHunter]

Make sure to unlink sysnand from emunand by either do factory restore sysnand or emunand(offline without Internet to unlink acc).

Oh it's like the 3ds emunand then, I remember. Ok then so I will factory reset the emunand.
Btw the procedure is super slow, it's still installing it.

 

[BionicGecko]

Anyone else experiencing random crashes on Emunand? My Switch keeps crashing with error 2011-0301. Problem takes a few hours to appear on a clean emunand with a reformatted SD, but slowly creeps in, and at some point the switch will crash within minutes of being powered on. Looks like some kind of weird memory leak issue that persists after system shutdown. I'm on OFW 6.0.0. Any ideas?

Same happened to me. I just removed the emunand will wait for 2.1.

For anyone experiencing this issue, I can confirm that SX OS 2.0.1 fixed the problem for me.

 

[thaikhoa]

Sysnand 6.0.1
Emunand 6.0.0
WORKS Perfectly.

The problem is when updating Sysnand, the firmware will patch BOOT0/1. Emunand signature is on BOOT1, after updating, SX OS won't recognize Emunand anymore.

Solution: Backup BOOT1 (unchanged after updating) when having Emunand setup.

Use Hekate to restore BOOT1 back after updating System to 6.0.1

 

[BionicGecko]

Sysnand 6.0.1
Emunand 6.0.0
WORKS Perfectly.

The problem is when updating Sysnand, the firmware will patch BOOT0/1. Emunand signature is on BOOT1, after updating, SX OS won't recognize Emunand anymore.

Solution: Backup BOOT1 (unchanged after updating) when having Emunand setup.

Use Hekate to restore BOOT1 back after updating System to 6.0.1

Are we sure that BOOT1 is identical on 6.0.0 and 6.0.1? Otherwise restoring the BOOT1 from 6.0.0 on 6.0.1 might cause problems down the road.

 

[thaikhoa]

Are we sure that BOOT1 is identical on 6.0.0 and 6.0.1? Otherwise restoring the BOOT1 from 6.0.0 on 6.0.1 might cause problems down the road.

YES 101%.

 

[loler55]

YES 101%.

View attachment 146098

Good to now

 

[sj33]

Wait, doesn’t updating the sysNAND defeat the point of having an enuNAND in the first place?

 

[Keylogger]

Sysnand 6.0.1
Emunand 6.0.0
WORKS Perfectly.

The problem is when updating Sysnand, the firmware will patch BOOT0/1. Emunand signature is on BOOT1, after updating, SX OS won't recognize Emunand anymore.

Solution: Backup BOOT1 (unchanged after updating) when having Emunand setup.

Use Hekate to restore BOOT1 back after updating System to 6.0.1

you mean i have to backup boot1 BEFORE updating right?

 

[BionicGecko]

you mean i have to backup boot1 BEFORE updating right?

Yes, you want to save a copy of your "hacked" BOOT1 (which contains the EMUNAND magic), so you can restore it after the OFW overwrites it.

I just did it, works fine. As a side note, I did both the backup and the restore from SX OS. No need for Hekate.

--------------------- MERGED ---------------------------

Wait, doesn’t updating the sysNAND defeat the point of having an enuNAND in the first place?

It depends on how you see it; there are two use cases.

1. You leave your sysnand at the lowest possible firmware to leave the door open for future exploits, and update your emunand to play the latest games
2. You update your sysnand to the latest firmware, but only do legit stuff on it, so you keep the possibility to play online, and you use your emunand for less legit stuff.

Thalkhoa's suggestion above is only relevant for the 2nd use case. Also the 2nd use case only makes sense if you have a clean NAND backup of your switch before any hacks, and you never went online after taking that backup.

 

[Chapi]

Sysnand 6.0.1
Emunand 6.0.0
WORKS Perfectly.

The problem is when updating Sysnand, the firmware will patch BOOT0/1. Emunand signature is on BOOT1, after updating, SX OS won't recognize Emunand anymore.

Solution: Backup BOOT1 (unchanged after updating) when having Emunand setup.

Use Hekate to restore BOOT1 back after updating System to 6.0.1

PM me if we have a real Emunand.

 

[thaikhoa]

PM me if we have a real Emunand.

You can PM the author of Atmosphere for "real" emunand. We're here for the emunand solution we love and take advantage of.

 

[GeraltOfRivia]

All your installed games on a nand will be archived completely when the other one doesn't have them in its ticketblob.
Because when linking, they're sharing the same Nintendo folder. Unlink them to separate Nintendo folder so when entering to your choice of nand with wrong Nintendo folder the system will ask you to delete rather than deleting without asking.

Just rename Nintendo folder to NintendoEmu after creating emunand (all your games on sysnand will be transfered to emunand). Enter sysnand and do factory restore settings (make sure your sysnand will be cleaned up before connecting to the Internet). When booting to emunand, rename Nintendo folder to NintendoSys and NintendoEmu to Nintendo and vise versa when booting to sysnand.

Use 2 sd to reduce headache.

Please could you explain me this procedure for the emunand? I will stay on 4.10 sysnand and update emunand to 6.00 to play latest games. I will stay offline, i don't have any games installed on my original nand cause I use xci and nsp update offline. So, once I setted up the emunand I have to factory restore the sysnand? I didn't understand very well this point, if you please could explain me how I unlink the Nintendo folder. Sorry didn't mean to bother you. Thanks

 

[stewacide]

The whole setup is finally working as advertized. I have sys and emunand both on 6.0.1+2.0.1. I'm using two SD's, one EXFAT for XCIs on sysnand and one FAT32 for NSPs/homebrew on emunand. I factory-reset the emunand so I don't accidentally wipe an SD by inserting it with the wrong nand loaded (if you don't do a reset on one or the other the /ninendo folders will collide and the Switch may wipe it without warning).

 

[GeraltOfRivia]

The whole setup is finally working as advertized. I have sys and emunand both on 6.0.1+2.0.1. I'm using two SD's, one EXFAT for XCIs on sysnand and one FAT32 for NSPs/homebrew on emunand. I factory-reset the emunand so I don't accidentally wipe an SD by inserting it with the wrong nand loaded (if you don't do a reset on one or the other the /ninendo folders will collide and the Switch may wipe it without warning).

Thank you for your reply. So after enabling emunand I must do factory reset the sysnand without sd inserted, right? Then I power off the console, boot emunand with the sd card in and so am i good to go? Sorry for my poor knowledge about it. Thanx

 

[stewacide]

You can reset either emunand or sysnand, with the SD removed and with wifi off. Then when you insert an SD it will be initialized to that nand. If you put the wrong SD in with the wrong nand it'll then give you an error message before wiping it (otherwise it'll wipe it without warning).

 

[newbcake]

For someone without an IQ as high as yours, would you say EmuNAND is "safe" to use for now? I'm already on the latest firmware on OFW, and just got my SX Dongle/Jig. In the midst of creating the NAND Backups and Boot backups now.

So I guess I'm asking, if I wanted to access things like the Homebrew Store (which would require internet access), RetroNX, and various other Homebrew apps, is that something EmuNAND would help me do with less risk?

Or is the better way just to go airplane mode and remove all networks and keep both OFW/CFW offline?

 

[guily6669]

You would be better off using OFW not hacked and fully clean for online and use emunand for the rest always offline.

Though this TX emunand solution is not good because even in OFW, emunand content is always there on the memory and any day in the future Nintendo could start just looking for a single simple part that they know they could detect if you have SX OS emunand and give a ban.

That's why M-SD emunand solution would be needed were you would just simply completely remove the emunand M-SD from your Switch having nothing for Nintendo to look for on a clean sysnand.

 

[insomniac45177]

Emunand does not change anything regarding autoRCM or non-autoRCM boot up. It's same as before, you either need the jig or have auto-RCM installed to your sysNAND.

Or remove your eMMC and boot. Remove it -> launch payload -> re seat it -> set autoRCM
Easy enough.

 

[Philourer]

Ok, so I was bored and tried to use a different switch's emunand. Causes an immediate power-off, doesn't get to any boot screen (other than the initial SX OS one). Has anyone gotten further than I have?

My notes so far (the names Switch #1 and Switch #3 are for my use, as I have one named Switch #2 that was not used for this experiment):

Switch #1 is on firmware 6.0.1, emunand created with SX OS 2.0.1. I chose to not backup user partition, and 10GB emunand size.

Switch #3 is on firmware 5.1.0, emunand created with SX OS 2.0.1. I chose to not backup user partition, and 10GB emunand size.

I verified that I could boot into emunand with each Switch.

I backed up nand00.bin, nand01.bin, and nand02.bin from both Switches.

I copied Switch #1's nand00.bin, nand01.bin, and nand02.bin files to Switch #3, overwriting the files already there.

I then tried to boot Switch #3 straight into emunand (SX OS does this if it detects emunand is present). Black screen after SX OS screen, appears to have fully powered off (inserting dongle and pressing power button will cause SX OS screen to appear again, so it doesn't appear to be hanging, just powering off). I then went into the SX OS menu (vol+ while pressing power), disabled emunand, was able to boot into CFW. Powered down, went into SX OS menu, left emunand enabled (the default) and tried to boot CFW, powered off as before.

I'm currently recopying the files, just in case something was messed up during that process.

If you have any ideas for me to test, I'm all ears. My guess is that the current emunand implementation does not support running an emunand from a different console. I thought that perhaps TX didn't implement it because of licensing (how would you support two license.dat files, one for the real nand and one for the emunand?), but it seems to be deeper than that.

 

[Halm]

@Philourer Sounds interesting...so what happens if you use different combinations of nand files? Like nand00 and nand01 of #1 and nand03 from #3?

I haven't used emunand yet, so not sure if nand0 and nand1 corresponds to boot0 boot1 while nand3 is the GPT....