how do Patched Erista, Mariko, Aula boot into hekate/nyx with modchip?
Does the modchip unlock RCM Mode?
Does the modchip unlock RCM Mode?
When you started over, did you successfully format everything to one blank partition or did you overwrite /atmosphere and /bootloader when you unzipped the files?
I had format it to one blank partition, then add the files as per the guide. Also, it is a brand new Switch that I bought back in the old days, I didn't start using until this week.When you started over, did you successfully format everything to one blank partition or did you overwrite /atmosphere and /bootloader when you unzipped the files?

Before we even begin, understand that 'RCM Mode' is redundant; RCM stands for Recovery Mode so saying "RCM Mode" is like saying Recovery Mode Mode. You don't say PIN number or HIV virus do you? Anyway, RCM is already available on all consoles. Its an intended feature of the console. That's not the exploit used on unpatched consoles. The exploit is what you do after entering RCM which is obviously patched out on everything else.how do Patched Erista, Mariko, Aula boot into hekate/nyx with modchip?
Does the modchip unlock RCM Mode?
Perfect…so when you went to sdsetup.com, which options did you select? I’m going to grab the same setup.I had format it to one blank partition, then add the files as per the guide. Also, it is a brand new Switch that I bought back in the old days, I didn't start using until this week.
I had only select the recommended default one, but added the utilities : Checkpoint + JKSV.Perfect…so when you went to sdsetup.com, which options did you select? I’m going to grab the same setup.
There isn't a single person on this forum that would recommend downloading files. His installation videos may be helpful but there is very little reason to download files from a third-party when they are available to be downloaded from their official sources. I only recommended DeepSea so you wouldn't be confused when Atmosphere launches without Hekate hence the minimal version. Either way, the RCM Loader files shouldn't need to be changed.
Perfect…so when you went to sdsetup.com, which options did you select? I’m going to grab the same setup.
I don’t think so. Having your Sysnand on 4.0.1 shouldn’t be an issue. I’m assuming you’ll be updating your Emunand firmware with Daybreak at some point down the road.Hi Binkinator, do you think it is because of the OFW version is 4.0.1 and Atmosphere being not compatible?
I have found a similar problem post: https://gbatemp.net/threads/black-screen-after-launching-cfw-emummc.586933/
Hello, some time ago I bought a second hand switch (V1 I think) , the guy who sold me the console told me to never shut down the device otherwise i will lose the mod. It works this way? Since I've used the switch only for the few already installed games and knowing basically 0 about hacking and thus what mod I really have, reading the guide isn't helping me too much. So I'm here to ask what mod I could possibly have, how to update it (if I need) and every other basic stuff that I'm missing like the recommended homebrew. Basically I need to know where to watch or what file to find to understand what I have i guess. Correct me if I'm wrong. Thank you.
you're better off learning out to update manually instead of using pakages especially from a youtuber no matter how "famous" they are, it will pay off in the end.I found the solution to make it works everytime without the problem of random black screens at the boot or after the nintendo logo: I used the latest package from this youtuber posted yesterday which contains hekate 5.8.
Mine was 5.7.2, the same provided in your DeepSea package not up to date yet.
updated recently to 14.1.2 + Hekate 5.8 (sigpatches and atmosphere is up to date)
my problem is now:
Tinfoil and other Games (not all) will not start anymore when i boot with hekate (rcm loader)
if i boot with fusee all is working normal.
what did i wrong?
this is my CFG
[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1
backlight=100
[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp
[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp
any help?
to this[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
[CFW - emuMMC]
payload=/bootloader/payloads/fusee.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
yea it is working again. thanks my man!download the fusee.bin file from the official GitHub location where you picked up Atmosphere. Make sure you match the version number…you cannot mix and match. Place fusee.bin in /bootloader/payloads/ and then…
…change this
to this
and you should be good to go!
GFJ man. Enjoy your Switch!yea it is working again. thanks my man!

Hi Binkinator, yes I would like update via Daybreak if I can get through Atmosphere black screen. I still cannot find a breakthrough of the problem.I don’t think so. Having your Sysnand on 4.0.1 shouldn’t be an issue. I’m assuming you’ll be updating your Emunand firmware with Daybreak at some point down the road.
I’m reluctant to tell you to upgrade from 4.0.1 since it’s a relatively low firmware and there‘s an off chance of there being an undiscovered software hack.Hi Binkinator, yes I would like update via Daybreak if I can get through Atmosphere black screen. I still cannot find a breakthrough of the problem.![]()
What guide did you use to migrate?I made an attempt at upgrading my old sx to atmosphere, now I'm unable to boot either. If any gurus want to discord/team view in and look at it I'd be happy to gift 6months patron subscription