Hacking SWITCH NOOB PARADISE - Ask questions here

[Blythe93]

1. Is it possible to move back and forth from CFW to OFW?
I hear that it’s totally possible, and I do have some games that I’d like to continue using for online play (Pokémon Scarlet and Pokémon HOME being the biggest reasons), but I’m really not sure how to do it yet. I’ve come across a few guides for getting back to OFW, but even though I’m following the instructions, it never seems to boot back into it. When selecting OFW on Hekate, all it does is shut off my switch entirely. It boots into emuMMC just fine, though.

Can you paste the contents of your bootloader/hekate_ipl.ini?
For booting into OFW I believe you can hold volume down or something before you press power button?

Should I ever get back into OFW, can I still get my Pokémon out of HOME without getting banned?

In general, as long as you do not do anything you aren't able to do with an unmodded Switch, it should be okay. Use emuNAND for all CFW stuff.

Is my issue just that I need a bigger SD card, or is it something else?

From what I can see, you have 7.12GB free and the file you're trying to install is 11.33GB. I'd suggest getting a bigger SD card. I personally have SanDisk Extreme 256GB one and it works perfectly fine for my (or average user's) needs.

As someone that’s a complete newbie in this kind of thing and doesn’t really wanna risk accidentally banning/bricking it, I’d rather not take the guessing-game risk. Sorry for the long post, but I’m glad to provide anymore information regarding these issues if anyone needs them. Any help will be appreciated greatly!

Feel free to ask whichever question you may have about Switch! While I'm certainly not an expert when it comes to Switch troubleshooting, at the very least I can share stuff from my personal experience. There are a plenty of others that lurk around here that might be able to help you out. ^^

Best way to format new SD card 256gb? exfat or fat32?

FAT32.

If fat32, will doing so via diskpart be ok?

To be honest, I've been using Wii Backup Manger to format my SD cards to FAT32. guifromat should work fine as well, I don't see why diskpart wouldn't.

Having some issues with sleep mode and nintendo OFW saying SD card corrupted (even though I can play games just fine in CFW) and trying to figure out the cause

I'd suggest checking the integrity of your SD card with h2testw before using it in your Switch. Note that all the data on it will be removed so backup anything if necessary.

 

[Anth87]

Thanks very much, appreciated!

 

[Littlebluepoodle]

Can you paste the contents of your bootloader/hekate_ipl.ini?
For booting into OFW I believe you can hold volume down or something before you press power button?

Uh, you mean this, right?
Hope I didn't mess something up with this or anything like that!
The guide I was using to set up Hekate for my switch just said to copy/paste the code it had listed on it.

[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=2
autonogc=1
updater2p=1

[SEMI-STOCK (SYSMMC)]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp
usb3force=1
{}

[CFW (SYSMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
usb3force=1
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
usb3force=1
{}

 

[Lioner]

Hi, I recently bought a Picofly Core Version 2 (firmware 2.75) for my patched V2 Switch. I did the mod myself with a soldering iron and a ton of patience, but when I installed it the Switch was already on version 20.0.1. Hekate works fine, as do Atmosphere and the original firmware, but the only issue is that the Switch won’t go into sleep mode. Whenever I press the power button or the Home button on the Joy-Cons -whether I’m running Atmosphere or HOS- the system just freezes. No matter how many times I try pressing the buttons, the only way to turn the console back on is to hold the power button for 12 seconds, then press Volume + and Power once. On the SD card there’s a pack from Sthetix: HATS-1.9.0-Prerelease-1.1.

I followed these steps to try to solve the problem:
Followed the guide to prepare SD card, i've redone all the backups and prepared the emummc as well, both the OS works fine, but the sleep mode issue is still present.

Measured the resistance of the SP1 and SP2 to make sure that there are no bridges, in the SP1 the left is 0,07 Ohm, the right side is 18.3 Ohm, the SP2 is the same but L and R are mirrored, beetween the condensator there are 24,5 Ohm they are in line with the guides found online

Updated the firmware of the Picofly Core, from the 2.75 to 2.8, nothing has changed (just few seconds more to boot)

Maked sure that is not a warmboot issue that comes from the Mariko consoles, but the file has been created successfully from the stock firmware in the SD

Atmosphere, Hekate and the Sys-patch are all in the latest version possible

The SD card is a Sandisk extreme V30 128 GB and the switch is the 2019 edition, not game branded

Is there a way to dig up in the problem?

 

[Blythe93]

autohosoff=2

This might be the culprit.
Based on what it says on Hekate's Github page, autohosoff option can take the following values:

• 0: Disable,
• 1: If woke up from HOS via an RTC alarm, shows logo, then powers off completely,
• 2: No logo, immediately powers off.

And based on what you've said:

When selecting OFW on Hekate, all it does is shut off my switch entirely.

It does sound like the issue you're having. Now, since you have a modchip installed, I'm not sure if it's something necessary for patched units? All the guides I know of have autohosoff set to 0, even for patched units.

I usually suggest people to use NH Switch Guide for setting up their Switch CFWs. Additionally, since they do not cover running unsigned content on your Switch, make sure to get sys-patch as well (make sure to remove all kip1patch=nosigchk lines from the hekate_ipl.ini if you decide on using sys-patch).

As for the hekate_ipl.ini, I use a slightly modified version of it from sigpatches thread tailored to my needs.

 

[QWERTY_YTREWQ]

Hello, is it possible to add edited clips back to the Switch Album?


When I upload the MP4 file to emuMMC > Raw1 > Nintendo > Album > <number> > File.mp4, it doesn’t show up in the Album.

Does anyone have a clue?

 

[Littlebluepoodle]

This might be the culprit.

Hmm, well that’s new information for me!

Do you recommend that I wipe everything off my Switch and start from scratch with this guide specifically, or can I keep everything and make a few edits here and there where needed?

(Asking because the last guy to help me on Reddit suggested that I wipe everything off my Switch and start from scratch with the guide he provided. But the guide he provided seems to have caused THIS mess I'm in now.)

EDIT!: Also, do you recommend I do this only after I've gotten a bigger SD card?

 

[Blythe93]

Do you recommend that I wipe everything off my Switch and start from scratch with this guide specifically, or can I keep everything and make a few edits here and there where needed?

Since you've just hacked your Switch, it won't hurt to redo everything right back from scratch by following NH Switch Guide that I linked. I've used it in the past and it works perfectly fine for setting up the very least that you'll need to have on your Switch. Once you get the bare minimum stuff, you can expand the functionalities of your Switch to whatever you need. I'd advise against using all-in-one updaters as they often cause more issues than they fix. Update your CFW manually. Here's a decent guide for that.

Since you're using your OFW for online play and official stuff, I guess you're on 20.0.1? It would be great for you create a new, fresh emuNAND from your current sysNAND, therefore avoiding the wired "EULA not accepted" battery draining issue that few users had for some time (apparently, since firmware 18.0.0).

Since you'll be going through the NH Switch guide, I'll tell you few more things that you'll need to know:

• You don't need to dump your own sysNAND's firmware in order to update your emuNAND - you can download firmware files from a few websites that host them, one of which is the Github page. We aren't allowed to link to them since they include copyrighted content, but it's not hard to find them with a quick Google search-
• For running game backups, you'll need sys-patch. As I've previously mentioned, make sure to remove kip1patch=nosigchk lines from the hekate_ipl.ini. If you're using sys-patch, you don't need sigpatches (i.e. two things doing the same thing).
• Make sure to block Nintendo servers on your emuNAND by using either 90DNS or DNS MITM/Exosphere.

In case things go south, restoring NAND backups is only safe if you haven't connected to the Nintendo servers afterwards on your sysNAND/stock firmware. Quoted from this thread:

The correct process for trying to avoid a ban are as follows:

1. Make a clean NAND backup before doing any other hacks/CFW/homebrew using Hekate including boot0/boot1 and raw eMMC GPP (which will become a rawnand.bin)
2. Perform any and all hacking offline with the Wi-Fi settings deleted and Airplane Mode to prevent accidental connection to Nintendo Hotspots (think 3DS Spotpass)
3. Restore the clean NAND backup as well as boot0/boot1 prior to going online
4. Make another NAND backup as well as boot0/boot1 at this point since your NAND has made permanent changes while connected to Nintendo's servers that are not present in your original NAND backup
5. Repeat steps 2-4

This is more important for users that are using sysNAND CFW.

EDIT!: Also, do you recommend I do this only after I've gotten a bigger SD card?

You can always move the stuff to the bigger SD card when you get to it, but if you're patient enough, buy the bigger SD card and hack your Switch then. Make sure to check your microSD card with h2testw before you use it.

Let me know if you have any other question (or homebrew recommendation?). ^^ Good luck.

Does anyone have a clue?

Last time I've checked, it's not possible. Can't really help you much, I'm afraid. :/

 

[Littlebluepoodle]

Let me know if you have any other question (or homebrew recommendation?). ^^ Good luck.

Oof... I'm really not sure where I went wrong here, but I've followed the guide the best I could, yet upon reaching the part where I'm supposed to launch Atmosphere PKG3 emuMMC, all I get is the blue screen of death now.

Is there a way to fix this, or am I totally done for?

I had this same issue last night, and afterward, I realized I accidentally missed a step.
This time, I tried to start over and reread everything slowly and carefully, but I still got the blue screen.

 

[Blythe93]

Oof... I'm really not sure where I went wrong here, but I've followed the guide the best I could, yet upon reaching the part where I'm supposed to launch Atmosphere PKG3 emuMMC, all I get is the blue screen of death now.

Is there a way to fix this, or am I totally done for?

I had this same issue last night, and afterward, I realized I accidentally missed a step.
This time, I tried to start over and reread everything slowly and carefully, but I still got the blue screen.

Kernel panic code. Sadly, my knowledge about that is limited and only time I've encountered it was on Hekate 6.2.x, not sure which. A certain firmware update was released and launching Atmosphere's package3 via Hekate's FS00 didn't work on Erista units. Thankfully, it was fixed rather quickly.

Other than backing up and removing atmosphere and bootloader folders on your SD cards and getting fresh Atmosphere and Hekate builds from their Github pages and trying to boot into emuMMC again, I don't know what else you could try.

You can, however, since you're using sys-patch, just push the latest fusee.bin payload and see if that will work. You don't have to boot into Atmosphere from Hekate (although it would be nice to fix the blue screen issue).

@impeeza, @Hayato213, any solution that you could suggest?

 

[Tubesy]

So, I went and followed the full guide on switch.hacks.guide to install Atmosphere via sysMMC and got it working, but the moment I try to boot basically any of the apps recommended in the SD card prep (like JKSV and Goldleaf) I get an immediate crash. I even went and switched to Atmosphere 18 (I'd been on the pre-release initially), but I'm getting the exact same error. I'm attaching the log. Hopefully someone can help me out, because I feel like a total idiot right now and have been dealing with this issue for over a week now, lol.

 

[impeeza]

So, I went and followed the full guide on switch.hacks.guide to install Atmosphere via sysMMC and got it working, but the moment I try to boot basically any of the apps recommended in the SD card prep (like JKSV and Goldleaf) I get an immediate crash. I even went and switched to Atmosphere 18 (I'd been on the pre-release initially), but I'm getting the exact same error. I'm attaching the log. Hopefully someone can help me out, because I feel like a total idiot right now and have been dealing with this issue for over a week now, lol.

DO NOT RUN HOMEBREW THROUGH ALBUM APPLET, PRESS R AND KEEP IT PRESSED WHILE RUN A TITLE ON THE HOS.

IF YOU RUN HOMEBREW ON APPLET MODE THE MEMORY IS REDUCED AND MOST HOMEBREW WILL FAIL.

 

[Tubesy]

DO NOT RUN HOMEBREW THROUGH ALBUM APPLET, PRESS R AND KEEP IT PRESSED WHILE RUN A TITLE ON THE HOS.

IF YOU RUN HOMEBREW ON APPLET MODE THE MEMORY IS REDUCED AND MOST HOMEBREW WILL FAIL.

TBH I could have sworn that was how I was doing it in the first place, but since I haven't touched this in over a week I guess not. It feels like the little warning about launching via the album on the site isn't worded strongly enough, since it implies it's not THAT handicapped compared to launching with R. Either way, thanks for the help!

 

[Lioner]

So, I went and followed the full guide on switch.hacks.guide to install Atmosphere via sysMMC and got it working, but the moment I try to boot basically any of the apps recommended in the SD card prep (like JKSV and Goldleaf) I get an immediate crash. I even went and switched to Atmosphere 18 (I'd been on the pre-release initially), but I'm getting the exact same error. I'm attaching the log. Hopefully someone can help me out, because I feel like a total idiot right now and have been dealing with this issue for over a week now, lol.

for me worked better the SHISE guide from Gitlab

 

[Blythe93]

TBH I could have sworn that was how I was doing it in the first place, but since I haven't touched this in over a week I guess not. It feels like the little warning about launching via the album on the site isn't worded strongly enough, since it implies it's not THAT handicapped compared to launching with R. Either way, thanks for the help!

To be honest, I can't remember the last time I've run an app on my Switch in full RAM mode and it's definitely been a while since I run into a crash. Iguess it depends on what kind of CFW setup you have on your Switch. Removing atmosphere and bootloader folders and downloading fresh copies of Atmosphere and Hekate usually fixes most of the issues I run into. After that, I just add whatever else I usually need (e.g. sys-modules, apps and stuff). However, I do wonder if recent changes that firmware 20.0.0 introduced made running apps in applet mode even worse than it used to be?

for me worked better the SHISE guide from Gitlab

I like that one but I haven't run through it completely yet. It reminds me of Rentry guide as it's probably based on it as well, slightly modified to be more straightforward.

 

[Hayato213]

Oof... I'm really not sure where I went wrong here, but I've followed the guide the best I could, yet upon reaching the part where I'm supposed to launch Atmosphere PKG3 emuMMC, all I get is the blue screen of death now.

Is there a way to fix this, or am I totally done for?

I had this same issue last night, and afterward, I realized I accidentally missed a step.
This time, I tried to start over and reread everything slowly and carefully, but I still got the blue screen.

If you don't mind me asking it is solid blue screen or it is one of the Atmosphere crash screen?

 

[gotcubed]

Hello all, I have 2 modded switches, 1 Oled, 1 Lite. I just updated both to 20.0.1, and used the Hats Pack to attempt to update atmosphere. I have no issues booting into Hekate, or into OFW, but when I try to boot into my CFW on EMUMMC both of the systems hang on the switch logo, no errors or anything. Any help would be really appreciated. Thanks in advance!

Post automatically merged: May 23, 2025

Hello all, I have 2 modded switches, 1 Oled, 1 Lite. I just updated both to 20.0.1, and used the Hats Pack to attempt to update atmosphere. I have no issues booting into Hekate, or into OFW, but when I try to boot into my CFW on EMUMMC both of the systems hang on the switch logo, no errors or anything. Any help would be really appreciated. Thanks in advance!

Also probably worth noting that it only seems to hang when trying to load Emummc, when I load cfw on sysnand it loads.

 

[Hayato213]

Hello all, I have 2 modded switches, 1 Oled, 1 Lite. I just updated both to 20.0.1, and used the Hats Pack to attempt to update atmosphere. I have no issues booting into Hekate, or into OFW, but when I try to boot into my CFW on EMUMMC both of the systems hang on the switch logo, no errors or anything. Any help would be really appreciated. Thanks in advance!

Post automatically merged: May 23, 2025

Also probably worth noting that it only seems to hang when trying to load Emummc, when I load cfw on sysnand it loads.

your emunand on fat32 or exfat? Did you select correctly when updating?

 

[gotcubed]

your emunand on fat32 or exfat? Did you select correctly when updating?

I usually leave it as fat32, although I haven't been able to get that far to update my emummc firmware with daybreak as I can't even get into my emummc.

Post automatically merged: May 23, 2025

I usually leave it as fat32, although I haven't been able to get that far to update my emummc firmware with daybreak as I can't even get into my emummc.

Ok, I don't know what I did, but I enabled logs when selecting EMUMMC in Hekate and the both booted fine. Very strange.
Edit nevermind it's still doing it. I was able to update the firmware in the EMUMMC, but it seems to be happening again.

Post automatically merged: May 23, 2025

I usually leave it as fat32, although I haven't been able to get that far to update my emummc firmware with daybreak as I can't even get into my emummc.

Post automatically merged: May 23, 2025

Ok, I don't know what I did, but I enabled logs when selecting EMUMMC in Hekate and the both booted fine. Very strange.
Edit nevermind it's still doing it. I was able to update the firmware in the EMUMMC, but it seems to be happening again.

I’m wondering if it’s possible this is happening because my SD Cards are garbage? I would imagine if my emummc was corrupt it would work at all, it seems to boot sometimes, but mostly locks up at the switch logo. I’m using SP 1 Tb sd cards I got from Amazon maybe last year. They have been fairly slow, but haven’t given me any serious issues.

 

[QWERTY_YTREWQ]

Hello,

I asked the question in the sys-screenuploader thread too, but i don't think it gets viewed often so i want to ask it here too, i hope that is okay.


Is it possible to upload a specific game’s screenshots to a specific Discord chat channel?
I tried modifying the config file, but I can't seem to figure it out.


For example:

• Screenshots for Let’s Go should go to the Let’s Go Screenshots channel.
• Screenshots for Legends Arceus should go to the Legends Arceus Screenshots channel.

See the attached screenshot. All the in-game screenshots I take now go to the "General" channel instead of the designated channel I created for them. What am I doing wrong?

Thanks!

I still haven’t managed to get this working. When someone has the time, could you please take a look at the config file?


What I’m trying to achieve is for the uploaded screenshots and videos to be automatically separated and posted in their respective game channels on Discord.