Hacking Some questions about (unlinking) emunand

TinyBilbo · Dec 6, 2018

Hi,

I've just backed up a virgin fw3.01 nand with nothing on it other than the account created to check it's firmware.
It's never even been connected to wifi.
It's sysnand has been upgraded to fw6.10 with ChoixDuJourNX and only 4 fuses have been burnt.
I then created a fw6.10 emunand
I have a 4 xci games and I installed the nsp updates and some DLC to those games in the emunand

I'm not really intending to use this switch online... I have another (unmodded) for that.
I've only ever run SXOS, Hekate, ChoixDuJourNX, & Checkpoint.

Whilst it probably doesn't matter if I get banned or not because I may never go online with this switch,
I wouldn't mind keeping my options open for a later date.

1) Have I made any mistakes so far that might get flagged? and would a sysnand downgrade fix that?

2) Do I need to unlink the sysnand? and if so so how do I do that? (do I just reset the sysnand like on the 3DS)

3) What are the advantages/disadvantages of unlinking the emunand and sysnand?

4) If I boot my switch directly to fw6.10 without using the SXOS bootloader - Do any fuses burn (i.e must I always boot to SXOS first?)

5) If I (eventually when fixed) upgrade to fw6.20, can I go online with the sysnand firmware through SXOS menu or can I only go online If I don't use OSOX?

Thanks

JJTapia19 · Dec 6, 2018

You don't need to unlink nands. Sd installs on on emunand will be redirected to the emutendo folder and on sysnand the it will use the normal nintendo folder. That way the nands don't conflict with each other without the need of unlinking. If you boot to a higher firmware without sx os or any other cfw it will burn fuses to match the version. About #5 I'm not sure but I wouldn't risk booting stock firmware through sx os if I plan to play online. I would just burn fuses and keep sysnand as stock as possible and keep emunand for hacks offline usage.

TinyBilbo · Dec 6, 2018

JJTapia19 said:
You don't need to unlink nands. Sd installs on on emunand will be redirected to the emutendo folder and on sysnand the it will use the normal nintendo folder. That way the nands don't conflict with each other without the need of unlinking. If you boot to a higher firmware without sx os or any other cfw it will burn fuses to match the version. About #5 I'm not sure but I wouldn't risk booting stock firmware through sx os if I plan to play online. I would just burn fuses and keep sysnand as stock as possible and keep emunand for hacks offline usage.

Many thanks for the reply, it clears up a few things...

The only reason I asked about unlinking is because I remember that on the 3DS the settings would carry through from the emunand to the sysnand which was sometimes a pain....

It's noted that I'll burn fuses if I boot an unmodded sysnand, it makes sense really.... So if I wish to play online with an updated umodded firmware I will HAVE to burn fuses...
I was hoping to keep the fuse count down so that if a dongle-less solution came up I might be able to revert to that firmware.. I'll worry about this if I ever feel that I wish to use this switch online.
At the moment I'm happy playing the emunand offline...

It also makes sense that I can't take a modded sysnand online, however I just wanted to clarify that point :-)

Hacking Some questions about (unlinking) emunand

Well-Known Member

I fight for my friends.

Well-Known Member

Similar threads

Popular threads in this forum