emuNAND will not be affected by this. Remember that resoring your sysNAND to a clean state requires you to restore a clean NAND backup.ok, thanks
--------------------- MERGED ---------------------------
how does partition between NAND and emuNAND work? let's say I create emuNAND with all the hack stuff on 8.1.0. Then I want to downgrade sysNAND to a clean state, initialize sysNAND and then update it to 8.1.0 for online. will emuNAND be affected because of that downgrade and/or initialization?
--------------------- MERGED ---------------------------
If your Switch is unpatched, 8.1.0 is the latest version, and it's compatible with CFW. When future system versions are released, you will likely need to wait at least a few days for CFW to be updated to support the new system versions.I'm trying to update firmware from 6.2.0 custom to whatever Latest Firmware is-(not sure what latest hackable firmware is)-while keeping custom firmware.
If your Switch is ipatched, you will need to keep your sysNAND on 4.1.0, and you can update your emuNAND to 8.1.0.
There are only two big reasons to use an emuNAND:emuMMC thing or whatever it called?..-(and also don't know much about it other than what i seen about it-which is
it being some kind of emuNAND-(i feel this is going to be a major headache for me
- If you plan on using online play with legitimately purchased games
- If your Switch is ipatched and you want to play newer games
If you're saying here that you're struggling to install a game, I would need more information to help you.said this is required for newer*-games-titles-(which i'm guessing is for the one i'm trying to play
and install at the moment-(Fire Emblem Three Houses*) but keeps failing for some odd reason?).. hmm , i wonder..
is it possible just because it's not named with a shorter name* and Capitalized , like example:
Fire emblem three houses .XXX instead of something like : feth.xxx?? could be messing it up?..
i had issues with this same problem in the past and finally got one working long ago..??
- Which system version are you on?
- Which installer are you using?
- Which CFW are you using?
- Do you have the correct signature patches installed?
Atmosphere is compatible with 8.1.0. However, if your Switch is ipatched, your sysNAND must stay on 4.1.0 forever, and you will have to update an emuNAND to 8.1.0 instead.side note!: just in-case anyone wondering about this , i wouldn't mind at all to be on Firmware Version latest that i know of-(8.1.0)- ONLY EXCEPTION THOUGH!**-(has to be hackable while keeping Custom Firmware)-if not then ,
what is latest firmware that supports everything-while Keeping Custom Firmware? , like Atmosphere Glaeee' or what it called..
You must manually create an emuNAND in order to be able to boot into an emuNAND, and that requires partitioning your SD card properly with your computer. However, as I said above, you might not need to use an emuNAND.and also i believe i possibly clicked right thing-(it gave me a few options to choose from at on menu*-from Atlas Kosmos and or Atmos-NX main Menu the latest one-
it said CFW-sysNAND and then another option said CFW-emuNAND.. i know difference between the two , but my problem is when i click the emuNAND option
it doesn't really show and or do anything that even shows that its working correctly and or even on emuNAND like the 3ds ones did long ago..-(plus i didnt even create an emuNAND that i know of??)