Hacking SWITCH NOOB PARADISE - Ask questions here

Sparky076 · Jun 23, 2020

Yo guys. So I have a Switch that is fusee gelee exploitable. Updated to 10.0.4 on the sysNAND, made a 29.2 GB partition for emuMMC, and the rest in FAT32. Created emuMMC, boot into emuMMC, and was able to get in. I was able to launch homebrew. The keyword is "was".

Now I can't boot into emuMMC. I send the hekate payload (v5.3.0), choose "Launch", select "CFW - emuMMC" to launch Atmosphere (0.13.0), Atmosphere logo pops up, Nintendo Switch logo pops up, then a blank screen with backlight.

I went back into hekate, made a new emuMMC, tried again, and no difference. Any suggestions? I have a sysNAND backup of when it was 4.1.0, before updating the sysNAND to 10.0.4, and another sysNAND backup after I updated the sysNAND to 10.0.4.

I don't think the sysNAND backup of 4.1.0 is any good, as I've burnt fuses updating the sysNAND through the official servers.

Draxzelex · Jun 23, 2020

cook99 said:
Thanks, was referring to the stickied thread on firmware status.
"WARNING !!! if you have a console with 4.1.0 firmware DO NOT UPDATE YET."
Seems to be pretty old advice though?
Seems I should just follow steps from the switch homebrew guide and use fusee gelee?

The exploit for firmware versions 4.1 and below has already been released. The only advantage it offers over Fusee Gelee is that it requires no jig in order to be utilized. However Fusee Gelee is still better in every other instance. That does not mean another exploit can still be released for lower firmware versions. As I have stated before, you can still use Fusee Gelee while keeping a path open for other exploits whether its updating without burning fuses or using emuMMC.

Sparky076 said:
Yo guys. So I have a Switch that is fusee gelee exploitable. Updated to 10.0.4 on the sysNAND, made a 29.2 GB partition for emuMMC, and the rest in FAT32. Created emuMMC, boot into emuMMC, and was able to get in. I was able to launch homebrew. The keyword is "was".

Now I can't boot into emuMMC. I send the hekate payload (v5.3.0), choose "Launch", select "CFW - emuMMC" to launch Atmosphere (0.13.0), Atmosphere logo pops up, Nintendo Switch logo pops up, then a blank screen with backlight.

I went back into hekate, made a new emuMMC, tried again, and no difference. Any suggestions? I have a sysNAND backup of when it was 4.1.0, before updating the sysNAND to 10.0.4, and another sysNAND backup after I updated the sysNAND to 10.0.4.

I don't think the sysNAND backup of 4.1.0 is any good, as I've burnt fuses updating the sysNAND through the official servers.

Where did you download Hekate and Atmosphere from?

DrROBschiz · Jun 23, 2020

Hey GBAtemp Gurus

Made my first attempt at hacking a launch day switch. Currently its on 9.2.0 Firmware and I was easily able to get into RCM and launch various payloads

Was using the Switch Homebrew guide https://switch.homebrew.guide/ and got all way past the Safety Precaution back up steps and moved on to trying to finally load Atmosphere and thats where I am hitting snags

Its flashes the atmosphere logos then goes into fatal error bootloops so I always have to put it back into RCM

I think my issue may be tied to the newer requirements for Atmosphere 13? I am unsure and kind of out of my depth at this point so any help for this newbie would be greatly appreciated.

NoAds · Jun 23, 2020

emuMMC is forced but not enabled!
Failed to launch HOS!
Press any key..

Does anyone know how to fix this issue? And before you ask, I did try the methods on the previous thread about this topic. However, it just sends me back to the hekate menu. So I decided to undo that when it didn't work. So I still got the same error

emuMMC is forced but not enabled!
Failed to launch HOS!
Press any key..

Lacius · Jun 23, 2020

DrROBschiz said:
Hey GBAtemp Gurus

Made my first attempt at hacking a launch day switch. Currently its on 9.2.0 Firmware and I was easily able to get into RCM and launch various payloads

Was using the Switch Homebrew guide https://switch.homebrew.guide/ and got all way past the Safety Precaution back up steps and moved on to trying to finally load Atmosphere and thats where I am hitting snags

Its flashes the atmosphere logos then goes into fatal error bootloops so I always have to put it back into RCM

I think my issue may be tied to the newer requirements for Atmosphere 13? I am unsure and kind of out of my depth at this point so any help for this newbie would be greatly appreciated.

Make sure the SD card is FAT32.
Remove all CFW files/folders from your SD card (that would be folders like /sept/ and /atmosphere/)
Download the latest Atmosphere
Download the latest fusee-primary (next to Atmosphere)
Download these signature patches
Put Atmosphere and the signature patches onto your SD card
Put the SD into your Switch
Enter RCM
Launch Atmosphere using fusee-primary

NoAds said:
emuMMC is forced but not enabled!
Failed to launch HOS!
Press any key..

Does anyone know how to fix this issue? And before you ask, I did try the methods on the previous thread about this topic. However, it just sends me back to the hekate menu. So I decided to undo that when it didn't work. So I still got the same error

emuMMC is forced but not enabled!
Failed to launch HOS!
Press any key..

Did you manually setup an emuNAND?

DrROBschiz · Jun 23, 2020

Lacius said:
Make sure the SD card is FAT32.

Remove all CFW files/folders from your SD card (that would be folders like /sept/ and /atmosphere/)

Download the latest Atmosphere

Download the latest fusee-primary (next to Atmosphere)

Download these signature patches

Put Atmosphere and the signature patches onto your SD card

Put the SD into your Switch

Enter RCM

Launch Atmosphere using fusee-primary

Did you manually setup an emuNAND?

Is it recommended that I update the main firmware to 10.0.4 or is it best to stay on 9.2.0? This will mostly just be used for homebrew

Lacius · Jun 23, 2020

DrROBschiz said:
Is it recommended that I update the main firmware to 10.0.4 or is it best to stay on 9.2.0? This will mostly just be used for homebrew

There is no reason not to update to 10.0.4. To play newer games in the future, you'll have to update eventually.
If you don't care about games at all, there is probably no reason to update.

Sparky076 · Jun 23, 2020

Draxzelex said:
The exploit for firmware versions 4.1 and below has already been released. The only advantage it offers over Fusee Gelee is that it requires no jig in order to be utilized. However Fusee Gelee is still better in every other instance. That does not mean another exploit can still be released for lower firmware versions. As I have stated before, you can still use Fusee Gelee while keeping a path open for other exploits whether its updating without burning fuses or using emuMMC.

Where did you download Hekate and Atmosphere from?

From their respective githubs.

Draxzelex · Jun 23, 2020

Sparky076 said:
From their respective githubs.

If you downloaded Hekate straight from its GitHub page, it wouldn't come with a "CFW - emuMMC" option. In fact, it wouldn't come with any launch options.

Sparky076 · Jun 23, 2020

Draxzelex said:
If you downloaded Hekate straight from its GitHub page, it wouldn't come with a "CFW - emuMMC" option. In fact, it wouldn't come with any launch options.

I followed this guide here: https://switch.homebrew.guide/emummc/windows

Draxzelex · Jun 23, 2020

Sparky076 said:
I followed this guide here: https://switch.homebrew.guide/emummc/windows

Unfortunately that guide was written before Hekate could partition the SD card itself so it is now considered outdated. It might be best to format your SD card and start fresh by letting Hekate partition the SD card instead of following the guide.

Sparky076 · Jun 23, 2020

Draxzelex said:
Unfortunately that guide was written before Hekate could partition the SD card itself so it is now considered outdated. It might be best to format your SD card and start fresh by letting Hekate partition the SD card instead of following the guide.

Alright. Backing up my SD card again. What folders should I keep if I'm completely starting over? Is there a guide anywhere specifically for setting up emuMMC through Hekate, and everything else alongside it?

Draxzelex · Jun 23, 2020

Sparky076 said:
Alright. Backing up my SD card again. What folders should I keep if I'm completely starting over? Is there a guide anywhere specifically for setting up emuMMC through Hekate, and everything else alongside it?

Your Nintendo folder stores your games and any game mods you have are kept in the /atmosphere folder. There is also no guide for setting up emuMMC within Hekate as all of the steps within Hekate are pretty self-explanatory.

Sparky076 · Jun 23, 2020

Draxzelex said:
Your Nintendo folder stores your games and any game mods you have are kept in the /atmosphere folder. There is also no guide for setting up emuMMC within Hekate as all of the steps within Hekate are pretty self-explanatory.

Do I place all the Atmosphere and Hekate files, including the hekate_ipl.ini file in the root of the microSD file structure, or should I place it in emuMMC/RAW1/ file structure?

Nokocchi52 · Jun 23, 2020

and custom firmware and normal firmware updates do I need to be able to have a fully updated copy of Pokemon Sword(the update that adds the Isle of Armor Pokemon to the coding) on a hacked switch have the capability to interact with Sword/Shield on a non-hacked, fully updated switch via local wireless?

Also, has there been any better save backing programs(or updates to older ones) that have come out since the Sword/Shield update that added Galarian Slowpoke as a IoA teaser?

Lacius · Jun 23, 2020

Nokocchi52 said:
and custom firmware and normal firmware updates do I need to be able to have a fully updated copy of Pokemon Sword(the update that adds the Isle of Armor Pokemon to the coding) on a hacked switch have the capability to interact with Sword/Shield on a non-hacked, fully updated switch via local wireless?

Also, has there been any better save backing programs(or updates to older ones) that have come out since the Sword/Shield update that added Galarian Slowpoke as a IoA teaser?

For local play, both games need to have the same updates installed.

Nokocchi52 · Jun 23, 2020

Lacius said:
For local play, both games need to have the same updates installed.

I know about the game updates needed, but does the latest patch of Sword/Shield need newer firmware from the last one(IIRC 8.1) and if so what do I need to update to make my CFW compatible with it

Nokocchi52 · Jun 23, 2020

How can I play Pokemon Sword and use a a save state program without corrupting the game constantly? I used that one program that allows you to move games from carts to the system itself, and a downloaded(from my computer) 1.2.0 patch(not the DLC, just the patch). I have the latest atmosphere, 10.0.0 firmware, the latest hetake and all of that stuff, yet I seem to be the only one that has this problem. What am I doing wrong? I am getting tired of having to go back to a firmware that can read carts, and re-download the game , re-add the patches, and re-add the save constantly whenever I want to edit save files. It is getting stupid. Let's Go Eevee is also used on the system and it never has had this problem.

It was like this back when I had 9.1.0 and when the patch that added Galarian Slowpoke came out as well.

What am I doing wrong?

For the record, I am using Check Point and JKSV simply does not work(there is no .sav file, just an empty folder named after what I named the save that isn't there)

EDIT: Now that I think of it, if I'd have to pinpoint the beginning of this problem, it was when CFW stopped being able to support physical game carts on newer firmware. Before that I had no problems at all with this

Final Edit: Problem is solved, at least for now. Updated Sigpatches and everything works again.

DrROBschiz · Jun 24, 2020

Lacius said:
Make sure the SD card is FAT32.

Remove all CFW files/folders from your SD card (that would be folders like /sept/ and /atmosphere/)

Download the latest Atmosphere

Download the latest fusee-primary (next to Atmosphere)

Download these signature patches

Put Atmosphere and the signature patches onto your SD card

Put the SD into your Switch

Enter RCM

Launch Atmosphere using fusee-primary

Did you manually setup an emuNAND?

Well I am making no progress. I may try to partition this 64GB MicroSD into fat 32 (unless there is some way to boot on an exFAT device)

I tried with a spare 1GB one i had and followed that steps and that failed too... Im curious if its all just bad luck with the SD cards i am working with

Seems like it should be much simpler to get into atmosphere otherwise.

Lacius · Jun 24, 2020

DrROBschiz said:
Well I am making no progress. I may try to partition this 64GB MicroSD into fat 32 (unless there is some way to boot on an exFAT device)

I tried with a spare 1GB one i had and followed that steps and that failed too... Im curious if its all just bad luck with the SD cards i am working with

Seems like it should be much simpler to get into atmosphere otherwise.

FAT32 is highly recommended, and your Switch might not even have exFAT support installed. Use guiformat to reformat your SD card as FAT32.

Hacking SWITCH NOOB PARADISE - Ask questions here

Well-Known Member

Well-Known Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum