Hacking SWITCH NOOB PARADISE - Ask questions here

[MortalWombat89]

does the PPSSPP emulator no longer work on the latest atmosphere and 20.2 update?

 

[SaGer27]

hey tthanks for replying but id assume if i stated the versions that would be clear? Sigpatches are the latest and the message just states it cant start the game.

Its weird because all the other games like latest octopath traveler 0 and pokemon legends za work fine. I use the latest hekate_ctcaer_6.5.1.bin but do i need to use also hekate_ctcaer_6.5.1_Nyx_1.9.1.zip ?

I use this one hekate_ctcaer_6.5.1_Nyx_1.9.1.zip

On reddit there are some user who have the same issue. Problem is you need a offline patch for D2 without that it would not start.
post on reddit

 

[Headblast]

I use this one hekate_ctcaer_6.5.1_Nyx_1.9.1.zip

On reddit there are some user who have the same issue. Problem is you need a offline patch for D2 without that it would not start.
post on reddit

Yep, thank you. Found the offline patch. Had to use the Russian DBI instead of the old english native one too. The russian one for some reason worked but the english one didnt.

 

[SwayStation]

Is it possible to run stock ofw off of emunand instead of sysnand?

I've searched through the forums and threads and only found one thread concerning it. One person had mentioned that it was possible but never replied with how to do it. Another person said that it still isn't possible.

 

[SaGer27]

You cannot truly run clean stock OFW from emuNAND as a safe replacement for sysNAND. The Nintendo Switch boot chain and Horizon OS were never designed for that separation. emuNAND (or emuMMC) is fundamentally a redirected, modified environment, even when it looks stock on the surface.

You can boot an emuNAND that:​

runs without Atmosphère patches, has no homebrew installed, behaves very close to stock


But and this is the important shadow in the corner, it is still not equivalent to real sysNAND OFW.

I think, I'm not to 100% sure

 

[Jean-Charles]

I have a question. I never installed any pirated games (nsp or xci etc) and never installed anything to the home menu. Only used stuffs in album and specifically only jksv, Edison se, checkpoint, usb connector. Will I get banned if I open Tesla menu/ultrahand overlay on Sysnand with cfw while connecting to WiFi? Can I update/download legitimately bought games from eshop? I always enable airplane mode while doing this though.

 

[lee_1689]

Someone please instruct me how to properly install this sound mod/ sound mods in general on my sd card?

https://gamebanana.com/mods/444173

The World Time Stop (Slow Mo SFX) Mod for The Legend of Zelda: Tear...
A The Legend of Zelda: Tears of the Kingdom (TOTK) Mod in the Sounds category, submitted by NyuB

 

[Gorkensnorkel]

Hey guys, I just updated my switch oled to FW 21.0.0 and AMS 1.10.2 and found that Breeze and the PPSSPP emulator no longer work. I get the PPSSPP emulator from HERE and the version hasn't changed since Sept 9th, 2024.

Has anyone else had any success with either of these two apps? Any feedback would be greatly appreciated, thanks!

 

[OoT4Ever]

Hi everyone, I have an oled with modchip and I've been using sysnand to play online and emunand to play my modded games for a few years.

However, I messed up with nxnandmanager and restored an emunand backup on my sysnand.

My Sysnand backup is more than 2 years old and I think restoring it might trigger a ban since Nintendo would see a difference in their log, so I was wondering if factory reset the dirty sysnand would be enough to clean it ?

My goal being to keep my emunand as it is and getting back a sysnand that clean to go online.

Thanks in advance

 

[OrGoN3]

Hi everyone, I have an oled with modchip and I've been using sysnand to play online and emunand to play my modded games for a few years.

However, I messed up with nxnandmanager and restored an emunand backup on my sysnand.

My Sysnand backup is more than 2 years old and I think restoring it might trigger a ban since Nintendo would see a difference in their log, so I was wondering if factory reset the dirty sysnand would be enough to clean it ?

My goal being to keep my emunand as it is and getting back a sysnand that clean to go online.

Thanks in advance

No, it is not if logs were created. You can try the system wipe script in tegraexplorer 4.2.0. you can then update under syscfw. I can't guarantee this will prevent a ban as I don't know what your console has recorded log wise and or sent to Nintendo. But a factory reset does not wipe logs.

 

[OoT4Ever]

Thanks a lot for the response, I'll look into the script you mentioned.

In terms of log sent to Nintendo, I'm 100% sure I've only been online with a clean system and never been online after my restore mistake, I'm hoping once the system wipe is done my system could safely go online.

 

[Littlebluepoodle]

Welp. After 3 days of trying to figure this out on my own, I'm finally at the end of my rope here and am 100% out of ideas on how to fix my problem with my Switch...Mind you, I'm in this whole mess purely because I waited way too late to jump on the 'Don't update your firmware' train from last year and because I wanted to play the new Pokemon LeafGreen ports.

Main issue; I can't access ofw OR emunand AT ALL anymore.

Trying to access either one just gets me the dreaded black screen of death. Somehow, though, Semi-Stock (Sysnand, I believe) gives me no problems and shows every game I had available before falling into this horrible mess I'm currently in. Of course, clicking on any of the game icons will get me nothing, as they'll just say 'Install virtual key cards' or 'insert game cartridge'.

Before all this mess, I was on Firmware 21.1.0 (I got the memo to avoid this too late last year) and tried to play Leafgreen on emunand, but couldn't get it open up at all. I heard from others that the game played just fine on Firmware 20.5.0, so I tried backing up all my game saves and my EMMC/EMUMMC. I still have all of these backup saves stored away safely, too.

Once I tried switching to the 20.5.0 firmware, I then tried to see if I could somehow restore all my backups, only for me to keep getting confused and mixing up steps.

Ever have it when you're playing a game that has loads of sidequests and you keep getting so distracted or mixed up with different quests that you forget where you even started?

That's the scenario I'm currently in right now with my Switch Lite.
Fell down the deepest rabbit hole of my life watching various Youtube videos trying to solve burnt fuse issues and restoring everything, just to pretty much end up with nothing in the end.

I'm all out of options on what I can possibly do to fix any of this, so any help will be GREATLY appreaciated.

Also, I'm unsure of where to really start when it comes to listing what particular specs or details to include,
so if there's details you want to know, ask away and I'll do my best to provide any information you may need!
Thank you so much!

 

[Blythe93]

@Littlebluepoodle I can try to help you out but this might be too difficult for me. Can't guarantee we'll fix your Switch but we can try.

Main issue; I can't access ofw OR emunand AT ALL anymore.

Since you have a modchip installed, I wonder if you can boot into OFW if you follow these steps:

1. Turn off your Switch completely (i.e. hold the Power button for 20-30 sec. if you're stuck on black screen).
2. Remove the SD card. Booting without sigpatches or sys-patch might invalidate your games so you'll have to reinstall them but that's a small price to pay if we can get it to work. Thankfully, you're using emuNAND so I hope you don't have any "game backups" installed on sysNAND as well?
3. While holding the volume + and -, power on your console. It should boot into OFW after a while, keep holding it until you see the lock screen, just to be sure.

Booting without your SD card should get you to the No SD card screen on hardmodded Switches, I guess. You may be getting the black screen error due to the fuse mismatch or AutoRCM thingy, I'm not sure as don't have a hardmodded Switch to tinker with.

If that works, great. Something's wrong with your CFW setup and we might be able to fix it.

I'd suggest backing up atmosphere and bootloader folders from your SD card, and getting the fresh copies of the Atmosphere, hekate and sys-patch at the very least to your SD card. your hekate_ipl.ini might need to be adjusted as well. Post the contents of it here so that I can take a look.

EDIT: Did you have a custom theme prior to updating your Switch?

 

[Littlebluepoodle]

Since you have a modchip installed, I wonder if you can boot into OFW if you follow these steps:

1. Turn off your Switch completely (i.e. hold the Power button for 20-30 sec. if you're stuck on black screen).
2. Remove the SD card. Booting without sigpatches or sys-patch might invalidate your games so you'll have to reinstall them but that's a small price to pay if we can get it to work. Thankfully, you're using emuNAND so I hope you don't have any "game backups" installed on sysNAND as well?
3. While holding the volume + and -, power on your console. It should boot into OFW after a while, keep holding it until you see the lock screen, just to be sure.

I'm really not sure what happened...I removed the SD card, got the 'No SD card' screen, held both volume + power buttons (Though admittedly, I remembered too late that I was supposed to hold down the power button for the duration too. I kinda just held down the volume buttons and hit power once and letting go to continue holding down the other two), and now my Switch just won't come back on no matter what I do.

Even plugging it up to charge won't turn it back on now.
Ah, wait a minute! The Switch seems to be turning on again, finally! That's a relief!
But the other issues still persist, sadly.

I think I still have the original backups to everything from before, so now that it's turning on again, let me try and see if I can install fresh copies of Atmosphere and everything else again.

As of right now, here's the info for the current hekate_ipl.ini:

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

[100% STOCK OFW]
ofw=1
icon=bootloader/res/ofw.bmp

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


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


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

EDIT 2: I managed to do a completely fresh reinstall of the latest HATS pack including Atmosphere and bootloader. Thankfully my Switch is still working, but I still have the same issue of OFW going to a black screen, but now going to emunand just gets me this:



Hard to tell which firmware I'm on though, since I still can't get to system settings in either OFW or Emunand.

 

[Blythe93]

As of right now, here's the info for the current hekate_ipl.ini:

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

[100% STOCK OFW]
ofw=1
icon=bootloader/res/ofw.bmp

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


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


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

The only thing I have that's different from yours is autohosoff which is 0 in my case. Not sure what it is about. On hekate's Github page it says: 0: Disable, 1: If woke up from HOS via an RTC alarm, shows logo, then powers off completely, 2: No logo, immediately powers off. The rest should be fine, I guess.

Thankfully my Switch is still working, but I still have the same issue of OFW going to a black screen, but now going to emunand just gets me this:

Can you get into hekate? I wonder if emuMMC is selected there. Once in hekate, go to emuMMC, then Change emuMMC I think. You should be able to select one of your partitions, probably the first one or something? Once done, it should say Enabled. If so reboot and see if it boots.

I managed to do a completely fresh reinstall of the latest HATS pack including Atmosphere and bootloader.

I'd suggest against using HATS pack, especially when trying to troubleshoot stuff. Stick to the manual setup and restore things as you go. I know it's handy to have all in one pack that you can put on your SD card but good luck figuring out when you run into issues.

 

[Littlebluepoodle]

Can you get into hekate? I wonder if emuMMC is selected there. Once in hekate, go to emuMMC, then Change emuMMC I think. You should be able to select one of your partitions, probably the first one or something? Once done, it should say Enabled. If so reboot and see if it boots.

Huh...going into emuMMC, it doesn't seem like there's any partitions to select.
Maybe that's my problem (Sorry for sounding noobish, still learning how these work!)?

I've already made backups to everything, so let me see what happens if I just make a new partition entirely.
Strange, cuz' I could've sworn I made a new one yesterday. Let me do that and I'll get back to you with the details!

I'd suggest against using HATS pack, especially when trying to troubleshoot stuff. Stick to the manual setup and restore things as you go. I know it's handy to have all in one pack that you can put on your SD card but good luck figuring out when you run into issues.

Ah, so instead of HATS packs, I should just get everything purely from Github directly? (Sorry, just trying to understand!)
Would you happen to have any specific recommendations to find everything I need or is it just as simple as 'Look for everything included in HATS pack, but just don't use HATS pack'?

 

[Blythe93]

Ah, so instead of HATS packs, I should just get everything purely from Github directly? (Sorry, just trying to understand!)

That's how I kept my Switch up-to-date and barely run into an issue to this date.

Here's what I suggest:
Minimum:

• Atmosphere
• hekate
• sys-patch (or sigpatches, but I strongly suggest sys-patch instead)
• LockpickRCM
• DNS MITM (For blocking Nintendo servers)
• Battery drain fix (if you run into it, here's how to fix it)

Recommended:

• DBI (latest Russian version) (my preferred title installer, don't use builds with unofficial translations as they might be unreliable), Tinwoo Installer or Goldleaf
• JKSV (Save manager that I personally use) or Checkpoint (apparently pretty decent save manager as well)
• Ultrahand + nx-ovlloader+ (Up-to-date and maintained replacement for the good old Tesla Menu and nx-ovlloader)
• linkalho (For linking and unlinking NNID accounts; some games like NSO emulators require a linked NNID account, either real or fake; version by mrdude works on 21.x.x and Atmosphere 1.10.x)
• sphaira (Alternative homebrew launcher and much more e.g. title installer, forwarder installer,...; DBI works a bit better in my use cases but give it a try)

Optional:

• emuiibo (amiibo emulation, TeslaMenu/Ultrahand + nx-ovlloader are required)
• AmiiboGenerator (Rebuilt for 1.10.x, probably has some bugs)
• MissionControl (If you use controllers from other consoles)
• NX-Activity-Log (Good for tracking your gaming activity on the Switch)

 

[Littlebluepoodle]

That's how I kept my Switch up-to-date and barely run into an issue to this date.

Here's what I suggest:
Minimum:

• Atmosphere
• hekate
• sys-patch (or sigpatches, but I strongly suggest sys-patch instead)
• LockpickRCM
• DNS MITM (For blocking Nintendo servers)
• Battery drain fix (if you run into it, here's how to fix it)

Recommended:

• DBI (latest Russian version) (my preferred title installer, don't use builds with unofficial translations as they might be unreliable), Tinwoo Installer or Goldleaf
• JKSV (Save manager that I personally use) or Checkpoint (apparently pretty decent save manager as well)
• Ultrahand + nx-ovlloader+ (Up-to-date and maintained replacement for the good old Tesla Menu and nx-ovlloader)
• linkalho (For linking and unlinking NNID accounts; some games like NSO emulators require a linked NNID account, either real or fake; version by mrdude works on 21.x.x and Atmosphere 1.10.x)
• sphaira (Alternative homebrew launcher and much more e.g. title installer, forwarder installer,...; DBI works a bit better in my use cases but give it a try)

Optional:

• emuiibo (amiibo emulation, TeslaMenu/Ultrahand + nx-ovlloader are required)
• AmiiboGenerator (Rebuilt for 1.10.x, probably has some bugs)
• MissionControl (If you use controllers from other consoles)
• NX-Activity-Log (Good for tracking your gaming activity on the Switch)

Thank you for the links! I'll have to go ahead and bookmark all of these for next time!

Huh...going into emuMMC, it doesn't seem like there's any partitions to select.
Maybe that's my problem (Sorry for sounding noobish, still learning how these work!)?

I've already made backups to everything, so let me see what happens if I just make a new partition entirely.
Strange, cuz' I could've sworn I made a new one yesterday. Let me do that and I'll get back to you with the details!

Alright! Turns out that was my issue, some how the partition I made yesterday just kinda disappeared somehow.
Still unsure, and likely just a big misstep on my part, but I've reinstalled most of my games and their original save files and am back to playing on Emunand for the most part! Yay!

Though sadly, trying to get back to OFW still leads me to a black screen.
Would you say the problem for that is a firmware issue?

Now that I can check system settings in emunand, it says I'm using firmware 20.5.0 / AMS 1.10.2IE.
Should I try using daybreak to go back to firmware 21.2.0, or is there a way to get everything working back to normal on 20.5.0?

 

[Blythe93]

Though sadly, trying to get back to OFW still leads me to a black screen.
Would you say the problem for that is a firmware issue?

Now that I can check system settings in emunand, it says I'm using firmware 20.5.0 / AMS 1.10.2IE.
Should I try using daybreak to go back to firmware 21.2.0, or is there a way to get everything working back to normal on 20.5.0?

Maybe the way you've updated the firmware on OFW? Might be a fuse mismatch issue which does result with a black screen. There's an option in hekate to check the number of burnt fuses, somewhere in console info section. If you can boot into CFW on sysNAND or at least semi-stock, it should skip the fuse check and boot into sysNAND. Can't really say as I don't have experience with that. Both of my modded Switches are on firmware that they had at the time of acquisition and I haven't updated ever since, only emuNAND is up-to-date. You can check this table to see how many fuses need to be burnt in order to boot into sysNAND normally without issue. If you have e.g. 22 burnt fuses but you're on 20.x.x or lower (i.e. lower than expected).

I'm not sure what's the correct approach to fixing this issue but it should be booting into semi-stock and updating the official way, provided that your Switch isn't banned and has access to eShop and everything. Otherwise, you can use Daybreak. Daybreak should be safe to use on sysNAND CFW if I remember correctly reading that SciresM made Daybreak update the console the same way official update does. I'm 99% sure, but don't quote me on that.

I haven't run into a problem on 21.2.0 yet other than a couple of homebrew apps not being up-to-date. 20.5.0 is still recent enough so you can stick to it if you want. You'll have to update eventually, though, so might as well check if everything you're using daily is up-to-date and update to the latest and greatest. emuNAND firmware doesn't really matter, it can be pretty much anything. You need to fix the sysNAND if you want to continue using it, though.

 

[Littlebluepoodle]

Maybe the way you've updated the firmware on OFW? Might be a fuse mismatch issue which does result with a black screen. There's an option in hekate to check the number of burnt fuses, somewhere in console info section. If you can boot into CFW on sysNAND or at least semi-stock, it should skip the fuse check and boot into sysNAND. Can't really say as I don't have experience with that. Both of my modded Switches are on firmware that they had at the time of acquisition and I haven't updated ever since, only emuNAND is up-to-date. You can check this table to see how many fuses need to be burnt in order to boot into sysNAND normally without issue. If you have e.g. 22 burnt fuses but you're on 20.x.x or lower (i.e. lower than expected).

I'm not sure what's the correct approach to fixing this issue but it should be booting into semi-stock and updating the official way, provided that your Switch isn't banned and has access to eShop and everything. Otherwise, you can use Daybreak. Daybreak should be safe to use on sysNAND CFW if I remember correctly reading that SciresM made Daybreak update the console the same way official update does. I'm 99% sure, but don't quote me on that.

I haven't run into a problem on 21.2.0 yet other than a couple of homebrew apps not being up-to-date. 20.5.0 is still recent enough so you can stick to it if you want. You'll have to update eventually, though, so might as well check if everything you're using daily is up-to-date and update to the latest and greatest. emuNAND firmware doesn't really matter, it can be pretty much anything. You need to fix the sysNAND if you want to continue using it, though.

Nice! Eveything seems to be working just fine once again, both ofw and emunand.

Turns out I did just have to use Daybreak to update it back to 21.2.0 in sysmmc (cfw) and now everything is completely back to normal. I guess it really was just a firmware mismatch issue all along. I've reinstalled two of my most important games on ofw (Monster Hunter Rise and Pokemon Scarlet), and they're working just fine now.

I think I finally have everything under control again!
Thank you so, so much for all your help, this is twice that you've helped me out of such a scary situation, and I appreciate it greatly. I'm gonna keep close tabs on our conversation, and bookmark everything if I need to, to use as future reference for next time should I somehow ever run into this problem again (Hopefully not!).

It'll be good to prevent me from panicking and making more rash and desperate decisions.
Once again, thank you so very much for helping me through all of this, you're awesome!