Hacking A question about EmuNAND

Lord-Farquaad

New Member
OP
Newbie
Joined
Feb 15, 2021
Messages
2
Trophies
0
Age
24
XP
4
Country
United Kingdom
Hello

Sorry if i have put this thread in the wrong place!!!

I am not new to the Switch CFW scene and have been doing it since V6 (well that's what my fuzes allow me to downgrade to anyway) but i am no pro at it in any way. I am new however to emuNAND and have successfully jumped on the train but i have a few sanity questions

So from what i see it is like a carbon copy of the sysNAND that lives on the SD card and you make that copy "Dirty" in order to save the sysNAND or OFW. From what i have seen the benefit is for going online, you have a clean OFW NAND that helps prevent a ban. My question is why would you do this? Surely you will always go online via the emuNAND anyway otherwise you will burn your fuzes the moment you boot into the OFW? or have i missed something here?

Online, this is something i intend on doing (Yes i know the risks) - I use Incognito, now surely Incognito will strip the information from the emuNAND only? This means if all goes wrong and i can't ever get that info back, i can just remove the SD card volume and re-create the emuNAND? - I can imagine this applies to other things as well

Bricking - Beyond pure stupidity or playing around with the clean OFW sysNAND, would this help prevent accidental bricking following the same idea from the last question?

Updates - I have seen a lot of threads concerning this and from what i see you now only ever update your emuNAND. So currently my switch can be downgraded to FW 6 - My actual installed FW is 11.0.1..... From what i have read there is no actual real reason to keep them on different versions like the sys being on V11 and emu on V10 or whatever way you want to see it. Is this true? The only benefit i see is having the sys on the lower version removes the possibility of burning your fuzes

Last one i promise: Again with updates - If i were to downgrade my sysnand again I guess i need to remove the emuNAND completely?

sorry for any spelling/technical mistakes. I am no pro and have typed this on a phone

Thank you in advanced!!!!!
 
Joined
Mar 17, 2010
Messages
21,260
Trophies
3
Location
Space
XP
10,070
Country
Norway
Hello

Sorry if i have put this thread in the wrong place!!!

I am not new to the Switch CFW scene and have been doing it since V6 (well that's what my fuzes allow me to downgrade to anyway) but i am no pro at it in any way. I am new however to emuNAND and have successfully jumped on the train but i have a few sanity questions

So from what i see it is like a carbon copy of the sysNAND that lives on the SD card and you make that copy "Dirty" in order to save the sysNAND or OFW. From what i have seen the benefit is for going online, you have a clean OFW NAND that helps prevent a ban. My question is why would you do this? Surely you will always go online via the emuNAND anyway otherwise you will burn your fuzes the moment you boot into the OFW? or have i missed something here?

Online, this is something i intend on doing (Yes i know the risks) - I use Incognito, now surely Incognito will strip the information from the emuNAND only? This means if all goes wrong and i can't ever get that info back, i can just remove the SD card volume and re-create the emuNAND? - I can imagine this applies to other things as well

Bricking - Beyond pure stupidity or playing around with the clean OFW sysNAND, would this help prevent accidental bricking following the same idea from the last question?

Updates - I have seen a lot of threads concerning this and from what i see you now only ever update your emuNAND. So currently my switch can be downgraded to FW 6 - My actual installed FW is 11.0.1..... From what i have read there is no actual real reason to keep them on different versions like the sys being on V11 and emu on V10 or whatever way you want to see it. Is this true? The only benefit i see is having the sys on the lower version removes the possibility of burning your fuzes

Last one i promise: Again with updates - If i were to downgrade my sysnand again I guess i need to remove the emuNAND completely?

sorry for any spelling/technical mistakes. I am no pro and have typed this on a phone

Thank you in advanced!!!!!
Yes, you will burn fuses, but that's not a huge concern. RCM exploitable consoles are forever hackable anyways.
Going online on emuNAND would be a bad idea as that would pretty much guarantee you a ban.

You can apply Incognito to emuNAND or sysNAND but it's not recommended to apply it to sysNAND nor is there much point to. Some people though don't bother with emuNAND and they go ahead and apply Incognito to their sysNAND and then lose their PRODINFO backup, then they are screwed.

You don't need to worry about bricking as long as you have a sysNAND backup (including boot0/boot1)

If you downgrade your sysNAND you run into issues with fuses and you won't be able to boot stock OFW and will have to boot "stock" sysNAND through Hekate which is not as safe for online. It doesn't affect your emuNAND at all. Why would it? emuNAND is completely isolated from sysNAND.
 
Last edited by The Real Jdbye,

Lord-Farquaad

New Member
OP
Newbie
Joined
Feb 15, 2021
Messages
2
Trophies
0
Age
24
XP
4
Country
United Kingdom
Yes, you will burn fuses, but that's not a huge concern. RCM exploitable consoles are forever hackable anyways.
Going online on emuNAND would be a bad idea as that would pretty much guarantee you a ban.

You can apply Incognito to emuNAND or sysNAND but it's not recommended to apply it to sysNAND nor is there much point to. Some people though don't bother with emuNAND and they go ahead and apply Incognito to their sysNAND and then lose their PRODINFO backup, then they are screwed.

You don't need to worry about bricking as long as you have a sysNAND backup (including boot0/boot1)

If you downgrade your sysNAND you run into issues with fuses and you won't be able to boot stock OFW and will have to boot "stock" sysNAND through Hekate which is not as safe for online. It doesn't affect your emuNAND at all. Why would it? emuNAND is completely isolated from sysNAND.


I see so the idea is you just stop caring about Fuzes and use the OFW as, well, an OFW. You then use the emuNAND for all your homebrew ect... That makes more sense

Currently i do not play games online and i probably should of said in the og post, by online i mean just having a network connection. I have enabled incognito for the emuNAND and use the DNS servers (90's DNS? cant remember the name). I am not very bothered about being banned to be fair. I have another non-hackable switch which i use for multiplayer games. This one is for everything i don't take online and for tinkering

That is a good thing, having an almost safety net on your switch being if you mess the emuNAND up, just make it again!!! I think i won't bother making the OFW a lower version and just update both when needed. I tend to make a NAND backup every time I update just in case. I can then downgrade via homebrew or via backup

I don't think i am quite ready to give up the Fuzes yet:rofl:

Thank you for your answers, appreciate it
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
16,219
Trophies
1
Age
27
Location
New York City
XP
11,076
Country
United States
I see so the idea is you just stop caring about Fuzes and use the OFW as, well, an OFW. You then use the emuNAND for all your homebrew ect... That makes more sense

Currently i do not play games online and i probably should of said in the og post, by online i mean just having a network connection. I have enabled incognito for the emuNAND and use the DNS servers (90's DNS? cant remember the name). I am not very bothered about being banned to be fair. I have another non-hackable switch which i use for multiplayer games. This one is for everything i don't take online and for tinkering

That is a good thing, having an almost safety net on your switch being if you mess the emuNAND up, just make it again!!! I think i won't bother making the OFW a lower version and just update both when needed. I tend to make a NAND backup every time I update just in case. I can then downgrade via homebrew or via backup

I don't think i am quite ready to give up the Fuzes yet:rofl:

Thank you for your answers, appreciate it
You know, you do not need both Incognito and 90DNS; one alone is sufficient.
 

CanIHazWarez

Well-Known Member
Member
Joined
Jan 21, 2016
Messages
337
Trophies
0
Age
30
XP
866
Country
United States
I don't think i am quite ready to give up the Fuzes yet:rofl:

I'm not sure no one told you this yet, but you can very easily keep your fuses by using autoRCM. You can then choose to boot emunand or sysnand via 3rd party boot loader (SX OS's bootloader, Hekate, etc.). This will bypass the fuse check and will thus not burn fuses. Be aware that updating using the official method will remove autoRCM and will thus burn your fuses upon reboot (as it will use the official bootloader to boot into Horizon). However, you can update your firmware with the homebrew ChoidujourNX and it will not burn fuses. There is theoretically a ban-risk in doing this because you'll have to use CFW on sysnand, but if you turn on airplane mode beforehand and cross your fingers, you'll be fine. Plus, you said that a ban-risk is not a big deal to you. Also I'll note, you can technically update via the official Nintendo servers without burning fuses if go into recovery mode upon reboot (via jig and Vol+) and inject a payload without booting into Horizon. Too ballsy of a move for me, but it's possible.
 
General chit-chat
Help Users
    CORE @ CORE: He Who Controls The Spice Controls The Universe...