If you burned fuses while updating to 7.X, then you will have to use AutoRCM to load your clean NAND dump. If you didn't, you can simply load your old NAND backup. You can check your fuse count with Hekate then compare that number with the ones from this list to see if they what firmware they match. You can also boot into Stock Mode with Hekate instead of CFW. As for risk, no one has been banned for only using AutoRCM and there is no evidence that Nintendo is actively checking users for AutoRCM so it is probably safe.
They charge when the switch's battery is over 50%It is so by design.
In order not to drain the main battery.
Why? Well, Nintendo though that was a good idea I guess.
But that is the normal behaviour.
It's possible, yes.can i haz melee yet on switch?
What's the difference/benefits between fusee-primary and hekate?
I'll use Hekate then, thanks.Fusee-Primary is the bootloader for Atmosphere, and Hekate is a multi function bootloader that you can use to create NAND backup/restore, create emunand, recalibrate battery. Hekate has way more function than Fusee-Primary.
I always use hekate, it can do the same as fusee-primary and more.I'll use Hekate then, thanks.
Stock used to be pretty clean before firmware version 7.0 but when sept was introduced, Stock required the usage of a custom secure monitor and warmboot which makes it slightly less clean but in the words of CTCaer, it is "pretty safe".wait so I can use autorcm to push hekate and then launch stock sysnand via hekate and still count as beingclean? Do I have to delete atmosphere from my sdcard for this to work? I thought having hekate installed instantly meant a switch was dirty? Because I'm not actually using any hacks, the only reason I'm using atmosphere is because I need autorcm to be on, which means I need hekate on to boot, which to me meant, I was dirty anyways, might as well choose CFW mode. Although I guess if I've ever booted into cfw then it's dirty? So what I should do is restore my clean nand backup, then setup an sdcard with only autorcm and hekate? I'm starting to get confused as to what exactly dirty means......
tl;dr I'd totally be willing to play fire emblem three houses online if I didn't have to burn more fuses to do it. I was under the impression I could only go online if I had the right number of fuses, or if I didn't care that I'd eventually be banned?
You can try finding DevMenu on the Internet (cannot link here because it is copyrighted material) and using the ResetRequiredVersion feature of the tool. If that doesn't work, you will have to install the game updates yourself.So I have a pretty nooby question. I've got kosmos/atmosphere/sept configured on my emuNAND and everything seems to be working smoothly. The problem is I have a few select games (ffix and cuphead are 2 examples) that ask me to update the game each time I run it. I can still start the game fine, but the prompt can get a little annoying and it only happens on a select few games. I haven't been able to find update files, or update files that seem to be completely up to date as I still get this prompt.
So my question: Is there a way to prevent this prompt from showing up? I do have the latest sigpatches, so I don't believe that would be it. I also tried converting my own xci to nsp using my prod keys, and it does the same thing. I've tried googling to no end, but I must be searching the wrong combination of words.
You can try finding DevMenu on the Internet (cannot link here because it is copyrighted material) and using the ResetRequiredVersion feature of the tool. If that doesn't work, you will have to install the game updates yourself.
Using a dirty emuNAND for hacks and a clean sysNAND for online play with legitimately purchased games is relatively safe, but the risk is yours to take.
I'm not entirely sure what you're asking. The system versions of the sysNAND and emuNAND are separate. What you do on one is separate from the other.If I installed a newer CFW (without burning fuses) and restored a clean sysNAND would I be detected?
So i'm asking like if I restore my original NAND and then created an emuNAND, is the FW versions separated?
I'm not entirely sure what you're asking. The system versions of the sysNAND and emuNAND are separate. What you do on one is separate from the other.
Stock used to be pretty clean before firmware version 7.0 but when sept was introduced, Stock required the usage of a custom secure monitor and warmboot which makes it slightly less clean but in the words of CTCaer, it is "pretty safe".
Also Hekate is never installed, only AutoRCM can be.
And keeping or deleting Atmosphere on your SD card would not make any difference as there is no evidence Nintendo scans the SD card for files. Even if they did, they run the risk of generating false positives and potential legal issues in the form of privacy violations. Not to mention that as stated earlier, you need some Atmosphere files on your SD card to boot Stock mode as of firmware 7.0.
The word "dirty" refers to a console that has ever booted CFW/homebrew. My NAND used to be clean but in order to not burn fuses while being on the latest firmware, I needed to make it a little bit dirty (plus the clean way of updating without burning fuses requires a jig with 100% efficiency). But since you've already booted online with your dirty NAND, there is no point in restoring a clean NAND anymore as that will create a mismatch on Nintendo's servers which can flag you for a ban.
You can try finding DevMenu on the Internet (cannot link here because it is copyrighted material) and using the ResetRequiredVersion feature of the tool. If that doesn't work, you will have to install the game updates yourself.
That is correct. 8.1.0 is required to play online. You have a few options:Oh I meant the FW versions. My switch was originally FW 4.1.0. If I want to play online games clean I would need to update my sysNAND FW to latest 8.1.0 right?
A controller update is done offline after your system version is updated. If you were using the PegaScape DNS, then you likely didn't connect to Nintendo's servers.I just realized I did go online with my dirty nand. Not on purpose (in fact I'm not even sure how you could tell exactly I had made this mistake, because even I didn't realize it...), but after I got everything running, about 1 second after I booted into atmo, I was given a nag for a controller update, then I remembered to turn airplane mode back on. Which is odd, I had my switch's DNS server configured as the pegascape DNS server, which I had assumed blocked nintendo's update url, but I guess it doesn't (even weirder though is my router firewall is setup to block nintendo update servers, although I added those url's to my router for 3ds/wiiu and maybe switch uses other urls). I guess since I connected to their servers while I was using atmosphere, you're right, there's probably no point in me restoring my nand backup. I guess I should just keep the switch in airplane mode forever, just in case anti-ban technology is improved in coming years and I can implement emu-updates then.
I guess what I should've done after hekate nand backup... was launch stock, turn airplane mode back on, then reset stock back into hekate, then launch CFW, and airplane mode would've been on already before my dirty nand appeared online. Or am I totally misunderstanding this? That's one thing that was missing from the instructions over at https://switch.homebrew.guide/hacking/caffeine/safetyprecautions they never bring up when to turn airplane mode back on (and I needed airplane mode off for some period of time at least in order to access the pegascape website, but it wasn't until I launched atmosphere for the first time that I think I was "online"). Although again, I might be totally misunderstanding everything!
That is correct. 8.1.0 is required to play online. You have a few options:
- Update your clean sysNAND to 8.1.0 for online play and burn your fuses.
- Update your clean sysNAND to 8.1.0 for online play while preserving your fuse count with AutoRCM.
- Keep your sysNAND low and use a clean emuNAND on 8.1.0 for online play.
--------------------- MERGED ---------------------------
A controller update is done offline after your system version is updated. If you were using the PegaScape DNS, then you likely didn't connect to Nintendo's servers.
First, it should be noted that controller updates are safe.Oh, yeah, I downloaded firmware from he who shall not be named (because I think you can't link to firmware downloads on gbatemp). I didn't realize the firmware update would include the controller update, but that's smart. Then if I've never been online, maybe I will try restoring my nand backup someday. Although I still don't entirely understand how I'll be able to autorcm into pushing hekate payload into launching stock firmware. Because the only steps I know of to install autorcm and a firmware update, are the ones I already went through. Although I guess there's probably a less user friendly way to do it that involves far fewer files with nice gui menus. Maybe in a year it'll be simpler/easier to do.
That is correct. 8.1.0 is required to play online. You have a few options:
- Update your clean sysNAND to 8.1.0 for online play and burn your fuses.
- Update your clean sysNAND to 8.1.0 for online play while preserving your fuse count with AutoRCM.
- Keep your sysNAND low and use a clean emuNAND on 8.1.0 for online play.
First, it should be noted that controller updates are safe.
Second, your post isn't clear. What is it you're wanting to accomplish?