Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,181,121
  • Replies Replies 48,022
  • Likes Likes 66
Okay. If you click on Album, does HB menu launches? What if you hold R button before you click on it and keep holding it afterwards until HB menu eventually launches?
Which firmware you're on?

If it still doesn't work, I'd suggest clean Atmosphere/Hekate/sys-patch install.
If you're on firmware 19.0.1, I'd suggest that you get Atmosphere (v1.8.0), and latest Hekate and sys-patch. While Hekate and sys-patch can be on the latest version, I'm not sure if the changes introduced in the latest Atmosphere affect anything negatively in the 19.0.1 or lower firmware (probably not?). Right now, there's no real need to update to the 20.x.x firmware.

Before you do that, make sure to backup atmosphere and bootloader folders on your SD card to your PC, maybe even the switch (where the apps are stored) folder. Once done, remove them from your SD card and drag and drop the fresh Atmosphere, Hekate and sys-patch that you've previously downloaded. If you don't have hekate_ipl.ini in your bootloader folder anymore, you can get a template from here and make sure to remove kip1patch=nosigchk lines as awell as remove the .template part from its filename.

Hopefully, you'll be able to launch HB menu via Album now.
I can open the album to the applet loader now, which is great. What I'm failing to understand is how to actually play anything. On one of the apps, I downloaded the game data from a cartridge I already had in my Switch, but on the home menu in atmosphere, is says there is still info to download and it can't open it.
 
On one of the apps, I downloaded the game data from a cartridge I already had in my Switch, but on the home menu in atmosphere, is says there is still info to download and it can't open it.
Probably needs a more recent update? Not all games work straight off the cartridge, some of them are incomplete. Also, make sure that sys-patch is working properly. If you have a Tesla menu and nx-ovlloader, just press the L + D-pad down + R stick combo, select sys-patch and check logs. It should say Patched for everything.

What I'm failing to understand is how to actually play anything.
Usually you just need to install either sigpatches or sys-patch. sys-patch is what i personally recommend.
 
Gah, somebody brought me an updated system. I was able to downgrade it back 19.0.1 then formatted the sd card back to normal. Installed the usual software and I'm getting this error.

At least I thought I downgraded it but checked in HOS and it's still at 20.0.1

Update: Was able to install the latest hekate/atmosphere/sigpatches/syspatch and all appears well.
:(
 

Attachments

  • 2025-05-11-12-45-17-671.jpg
    2025-05-11-12-45-17-671.jpg
    1.4 MB · Views: 33
Last edited by rsx,
  • Like
Reactions: Blythe93
Try to dowgrade you firmware
Before you do that, try updating (or by doing a clean install of) Atmosphere, Hekate and whichever payloads you're pushing (like fusee.bin). Downgrading is not recommended unless you're doing it on emuMMC (which you can recreate at any point if your sysMMC / stock firmware is working properly) or as a last resort. Downgrading on sysMMC might even get your console banned if you've sent telemetry back to Nintendo while on a higher firmware, so keep that in mind unless you don't really care whether your console gets banned or not.

Also, I don't recommend following outdated YouTube tutorials. Those errors usually happen when you're on a firmware version higher than the Atmosphere supports or when you're pushing an outdated fusee.bin payload. Always make sure to update everything properly or, at the very least, Atmosphere, Hekate, sys-patch/sigpatches and any extra sys-module that you may be using. Do that and you shouldn't see any of those errors if you're using latest official releases.

updated to 19.0.1 to 20.0.1 and after the 2 logos it shows "The software could not start" please help me
If you don't have sys-patch yet, grab it from here, reboot and let us know if your games work now, if that's the problem you're experiencing? Otherwise, post some screenshots or some additional details/info.
 
Last edited by Blythe93,
Came back to my modded switch after a lot of time, and I see Tinfoil is out of order.
What's the best way to go about installing NSPs nowadays without Tinfoil? I'm using Atmosphere. (I already have the NSPs of course)

Also - I remember in the past, I'd boot into Atmosphere CFW via RCM for homebrew & roms, and just boot regularly into the OFW, bypassing hekate altogether, to run genuine games/go online (just pressing the power button as if the switch wasn't modded). Should I bother going through hekate -> Stock SysNAND at all? Or is it virtually the same thing as just pressing the power button without going through RCM and hekate?

Should I worry about upgrading the firmware on the stock SysNAND? I've been updating it thus far and nothing broke, but can't tell if I've just been lucky so far.

Hope I didn't mess up my terms too much. Thank you in advance. :grog:
 
  • Like
Reactions: Blythe93
What's the best way to go about installing NSPs nowadays without Tinfoil? I'm using Atmosphere. (I already have the NSPs of course)
To install the games, I generally suggest using DBI [latest EN release][latest RU-only release]. I personally use the latest Russian version, but even the latest English one should work for installing games. Here's a good video tutorial by sthetix.
There's also a TinWoo Installer + NS-USBLoader as an alternative if you prefer an up-to-date installer in English language. Goldleaf has also been updated recently so it might be worth checking out as well.

Should I bother going through hekate -> Stock SysNAND at all? Or is it virtually the same thing as just pressing the power button without going through RCM and hekate?
Taken from here, this is what booting into stock via Hekate means:
This disables kernel patching and CFW kips.
Includes exosphere and warmboot, ONLY when >= 7.0.0 and Erista.
Includes exosphere on Mariko.
Exosphere/warmboot are not identifiable as it is now.
This is the closest to OFW, especially when AutoRCM is needed.

Should I worry about upgrading the firmware on the stock SysNAND? I've been updating it thus far and nothing broke, but can't tell if I've just been lucky so far.
If you're using online services on stock firmware, you'll need to update in order to continue using them. As far as I know it should be fine. As for the CFW side of the things, firmware 20.0.0 introduced some changes that Atmosphere had to address. Quoted from the latest release notes:
  • Please note: As a result of changes made to nintendo's software in 20.0.0, there is roughly 10MB less memory available for custom system modules.
    • We can only steal a maximum of 14MB from the applet pool, down from 40MB.
    • To compensate for this, ams.mitm's heap usage has been reduced by 20MB.
      • To facilitate this, a new helper module (memlet) was added, so that memory may be temporarily stolen during the romfs building process.
      • Hopefully, this results in relatively little breakage, however it is possible that user mods which replace extremely large numbers of files in The Legend of Zelda: Tears of the Kingdom may no longer function.
        • If you are affected by this, you will see "Data abort (0x101)" when trying to launch the game with mods.
        • Please reach out to sciresm on discord if this occurs to share your error report binary. However, some issues may be impossible to fix.
        • I apologize sincerely if the issue is impossible to resolve, but I have been forced unavoidably to make compromises here, and I think this is the best balance to be struck.
 
To install the games, I generally suggest using DBI [latest EN release][latest RU-only release]. I personally use the latest Russian version, but even the latest English one should work for installing games. Here's a good video tutorial by sthetix.

Thank you! DBI worked. One thing that wasn't mentioned anywhere in the guide, is that you might need some extra drivers - found out about zadig and it works like a charm now. (Before, I'd get this error: dbi NotImplementedError: Operation not supported or unimplemented on this platform) Otherwise, the MTP responder option also works without the extra drivers. (Just writing this out in case another noob has my same issue)

Taken from here, this is what booting into stock via Hekate means:
This disables kernel patching and CFW kips.
Includes exosphere and warmboot, ONLY when >= 7.0.0 and Erista.
Includes exosphere on Mariko.
Exosphere/warmboot are not identifiable as it is now.
This is the closest to OFW, especially when AutoRCM is needed.

So it still runs some CFW, but tries to act as closely as possible to OFW? Is this of any use only to people who decide to activate AutoRCM then? What I get from this is that booting straight into OFW would be preferrable, if the option is there.
 
Last edited by mobiusherz,
  • Like
Reactions: Blythe93
I can't change the atmosphere splash screen, I tried using the insert_splash_screen.py script, I tried to edit the hekate_ipl.ini,
the bootlogo is in bootloader/bootlogo.bmp, but it's still showing the default atmosphere logo when I boot emummc. Please help.
Post automatically merged:

I can't change the atmosphere splash screen, I tried using the insert_splash_screen.py script, I tried to edit the hekate_ipl.ini,
the bootlogo is in bootloader/bootlogo.bmp, but it's still showing the default atmosphere logo when I boot emummc. Please help.
 
One thing that wasn't mentioned anywhere in the guide, is that you might need some extra drivers - found out about zadig and it works like a charm now.
sthetix did mention it in the description, though, but I did forget to mention that it's required on the first try. After that, it works like a charm, indeed.

So it still runs some CFW, but tries to act as closely as possible to OFW? Is this of any use only to people who decide to activate AutoRCM then?
I've never used it myself, but I guess that's the case.

What I get from this is that booting straight into OFW would be preferrable, if the option is there.
I guess? On Erista, you can just reboot the Switch normally and it should boot into OFW by default. As for the Mariko, I believe that you need to hold a volume button or something during boot up for Switch to boot into OFW. Not sure if it loads into the "stock" Switch that way as I have no experience with the Mariko units.
 
  • Like
Reactions: mobiusherz
I've never extracted saves from my emuMMC partition before, but you can make a emuMMC backup by following this guide as if you're about to migrate to a new SD card up to the point when you end up having your backup on your PC. After that, follow either this or this guide. Hopefully, it won't be broken to the point that you can't access the USER partition of your emuMMC.
at this point I'm just going to wipe my emuNAND and build a new one, because apparently nothing I need will actually load on my connection

I would ask for a guide on setting up a new emuNAND but it's probably a rentry guide, too

1747140125768.png
 
  • Sad
Reactions: Blythe93
I would ask for a guide on setting up a new emuNAND but it's probably a rentry guide, too
NH Switch guide should do the trick. Additionally, don't forget to get sys-patch for game backups to work (optionally but highly recommend as well: Tesla menu + nx-olloader). I'd suggest getting hekate_ipl.ini from the sigpatches as well (you don't need the sigpatches).

As for the rentry guide, it used to be archived on archive.org, but nowadays sadly it's excluded. If you really need it, there's a post on Reddit where someone made a backup of the entire website. Not in the best readable format, but it should do the trick. Not sure if I can link to it here, though, so you'll have to look for it on your own.
 
the thing is the only link you've just shared that I CAN load is the sigpatches one and I've gone through and got AMS 1.8.0 with the updated sig/sys-patch running on 16.0.3

I've been trying to fix my emuNAND since october

nobody seems to understand that all these links simply do not load for me
 
I'm talking about rentry, github, and switch.hacks.guide

they do not LOAD for me at all
Are you trying to access those websites on a public WiFi or something? Like on college, university, dorm etc.? They might be blocked on your end but they definitely work on mine and, as it seems, on @Dust2dust's as well.
 
  • Like
Reactions: Dust2dust
yes, I know it's on my end. it's an https issue that I can't seem to diagnose and solve, because here I am on gbatemp which is USING https according to my browser, and nothing is wrong.
 
  • Sad
Reactions: Blythe93

Site & Scene News

Popular threads in this forum