https://github.com/ITotalJustice/patches/releases merge the atmosphere folder from the download here with the one on your sd root. Use the fusee download for fusee primary directly or fusee primary through hekate. Use the hekate download for hekate without fusee primary.
You can check your hekate_ipl.ini file, find the specific boot entry you use, and if it says payload=fusee_primary.bin then fusee, and if it says fss0=fusee_secondary.bin then hekate. Alternatively, you can just add both and assume one of them will work.
Honestly, I tried to figure that out, but I came up short. This is the guide I used to put cfw on my switch
https://nh-server.github.io/switch-guide/user_guide/getting_started/
I have to say thank you so much though. Been a big help in keeping sanity.
EDIT: I put both of them on there and I still have a spinning icon.
EDIT V2: I'm reading that tinfoil does not work with Hekate. Is there any way to use a different payload?
Last edited by Tinoator,
I think I realized the issue. Youre using the NH guide which is strictly anti piracy and therefore doesnt include any support for sigpatches. Youre booting with hekate which requires you specifically enable sigpatches, which of course NH doesnt tell you. To enable sigpatches, either add kip1patch=nosigchk to your boot option in hekate_ipl.ini or push fusee primary instead of hekate.
I think I downloaded the wrong sigpatches using AIO, downloading pure Atmosphere instead of Fusee-gelee and then rebooted like an idiot, and now I'm stuck on my emuNAND, can't even reboot into Hekate anymore because it just boots into my emuNAND. I downloaded a new Hekate payload into my RCM loader, but no dice. Hitting reboot to payload in the HB Menu just reboots to my emuNAND, too. Do I have to nuke everything and start over?
EDIT: Actually, looking through my hekate_ipl.ini, it just looks like I moronically set a profile so that this emuNAND will boot up by default... at least, I hope that's the case.
EDIT: Actually, looking through my hekate_ipl.ini, it just looks like I moronically set a profile so that this emuNAND will boot up by default... at least, I hope that's the case.
Last edited by Steel-Winged_Pegasus,
I'm using AMS quite a while now and I'm totally satisfied so far. I don't care about playing backups, or online cheating. AMS is primarily used for savegame management, ftp and some offline cheating in games like hyrule warrios to shorten the massive grinding. But I'm interested in emuMMC. Does it have any advantages? What can be done in emuMMC what cannot be done in sysnand?
So you want to boot into Hekate menu instead of autoboot into your EmuMMC? in hekate_ipl.ini change autoboot=0. That should do it. Alternatively you can press COL- when you boot to go to the menu (bypasses autoboot one time). I haven't done it myself so I don't know exactly when to do that. I guess while the Hekate logo appears.
EmuMMC is basically a copy of your SysMMC so nothing can be done in EmuMMC that cannot be done in SysMMC. However the advantage with EmuMMC is that you can stay offline in EmuMMC or block Nntendo servers and then safely play online in SysMMC (legit games) without getting banned. Another advantage is that if you make a mistake with CFW and brick then you only brick EmuMMC and not the console itself. EmuMMC is highly recommended.
Then just one last question. Does EmuMMC use the same savegames as sysnand (exept device savegames like ACNH I think) and are legit bought games available on sysnand and EmuMMC?
SysMMC and EmuMMC are completely separated. When you create EmuMMC it will be a copy of SysMMC at the time of creation but after that if you progress in a game in for instance EmuMMC it will not show in SysMMC. Legit games that are installed in SysMMC at the time where you create EmuMMC will also be available in EmuMMC (if you copy the Nintendo folder too) but if you purchase a game after that it won't be available in EmuMMC. Generally it's recommended to us SysMMC for legit games and EmuMMC for backup games.
As I don't care about playing backup games, for me EmuMMC would just be for playing around. Maybe testing any Switch Updates before installing them on sysnand. For legit usage and some homebrew there seems not to be a high advantage of using only AMS instead of Hekate and emuMMC.
Just trying out some Fusee Gelee payload stuff.
On Windows machines, sending fusee_test.bin using TegraRcmGUI works just fine.
But on my OnePlus 3T, I've installed Rekado 4.1.3 and enabled OTG. It gets as far as sending the fusee_test.bin payload but it doesn't seem to work. This is using the same USB-cable as with my Windows machines.
Any idea why it might not be working with my Android device? It detects the Switch in RCM mode no problem.
On Windows machines, sending fusee_test.bin using TegraRcmGUI works just fine.
But on my OnePlus 3T, I've installed Rekado 4.1.3 and enabled OTG. It gets as far as sending the fusee_test.bin payload but it doesn't seem to work. This is using the same USB-cable as with my Windows machines.
Any idea why it might not be working with my Android device? It detects the Switch in RCM mode no problem.
I know this question might have been asked before but I like to be 100% sure, so I'd rather state my situation even though it repeats with what already has been posted by others before.
I own a Mariko unit, FW on sysNAND is still 10.2.0 and I haven't touched it since I installed my chip in September last year.
Due to several reasons I now want to boot into sysNAND again, but have the fear of a ban.
I did not go online with my Switch on emuNAND for a long time at all, and if so later I used the new DNS blocking module by Atmosphère (previously Stealth Mode on SXOS), but as I said this rarely occured and was not used for "naughty" activities, maybe homebrew related. Then again, I also use exosphere since I switched from SXOS to Atmosphère.
I currently run a 11.0.1 emuMMC with Atmosphère (chainloaded fusee-secondary with hekate) but still have my SX license just in case, what would be the smartest or best or safest or whatever-you-wanna-call-it way to boot into sysNAND now so I can safely update my system software and access the eShop for example?
Would I need to update my emuMMC aswell or will it still run on 11.0.1 even with sysNAND FW on 12.0.1?
Thanks in advance and if you need more information I will gladly provide them.
I own a Mariko unit, FW on sysNAND is still 10.2.0 and I haven't touched it since I installed my chip in September last year.
Due to several reasons I now want to boot into sysNAND again, but have the fear of a ban.
I did not go online with my Switch on emuNAND for a long time at all, and if so later I used the new DNS blocking module by Atmosphère (previously Stealth Mode on SXOS), but as I said this rarely occured and was not used for "naughty" activities, maybe homebrew related. Then again, I also use exosphere since I switched from SXOS to Atmosphère.
I currently run a 11.0.1 emuMMC with Atmosphère (chainloaded fusee-secondary with hekate) but still have my SX license just in case, what would be the smartest or best or safest or whatever-you-wanna-call-it way to boot into sysNAND now so I can safely update my system software and access the eShop for example?
Would I need to update my emuMMC aswell or will it still run on 11.0.1 even with sysNAND FW on 12.0.1?
Thanks in advance and if you need more information I will gladly provide them.
Last edited by HalfScoper,
You need a clean eMMC backup that was made before running homebrew and/or CFW. Without that, you risk getting banned if you go online.
The first thing I did after installing the chip was making a NAND backup within the SX boot menu, would that be sufficient?
Edit: And I still got that original backup stored on an external drive.
Last edited by HalfScoper,
Assuming SX OS does not make corrupted dumps, it should be fine although there was one person I remember being banned even restoring a clean eMMC backup. The only factor I could not remove was the fact that he made it through SX OS. Now I'm not saying you share the same chances of getting banned as he did but what I am saying is that there is a very small possibility that the backups SX OS makes are not clean enough to go online with. If you are still willing to take the chance, you should also perform the cleanup option in the SX boot menu after restoring the clean eMMC backup.
-
Xdqwerty
what are you looking at?
