Hacking SWITCH NOOB PARADISE - Ask questions here

[RioStride]

This isn't about messing with anyone's program. Please refer to the discussion above.

 

[UsernamesAreWeird]

Alright then

 

[yankii]

Is there a way to mod my Switch V1 without an SD card? Say, by writing files to sysMMC? I don't care about bans, etc.

 

[Nynrah]

In that case, you could try with a different installer. There is TinWoo, for example. You could also re-verify your xci file with a different checker. I've been using NX Game Info for many years. It's old, but it still works. You just need to provide it with the latest prod.keys file.

The problem is not that I can't install the file with DBI (installing it at all costs isn't the goal), but that I can no longer trust in the integrity of any XCI or NSP file if problems are reported despite a valid signature and hash. This is the basis for how I check if an XCI or NSP file is OK:
invalid hash = corrupt crap that shouldn't be touched with a 10m pole
invalid signature = I rather avoid this for base games and patches, but tolerable as far as I know when there's no alternative (often the case for DLC, somehow...)

That's why I need to understand what's going on with this game.

 

[Nephiel]

The problem is not that I can't install the file with DBI (installing it at all costs isn't the goal), but that I can no longer trust in the integrity of any XCI or NSP file if problems are reported despite a valid signature and hash. This is the basis for how I check if an XCI or NSP file is OK:
invalid hash = corrupt crap that shouldn't be touched with a 10m pole
invalid signature = I rather avoid this for base games and patches, but tolerable as far as I know when there's no alternative (often the case for DLC, somehow...)

That's why I need to understand what's going on with this game.

Corrupted file somewhere along the way, perhaps? How exactly are you trying to install it? (MTP, FTP, HTTP, dbibackend...)

 

[Dust2dust]

The problem is not that I can't install the file with DBI (installing it at all costs isn't the goal), but that I can no longer trust in the integrity of any XCI or NSP file if problems are reported despite a valid signature and hash. This is the basis for how I check if an XCI or NSP file is OK:
invalid hash = corrupt crap that shouldn't be touched with a 10m pole
invalid signature = I rather avoid this for base games and patches, but tolerable as far as I know when there's no alternative (often the case for DLC, somehow...)

That's why I need to understand what's going on with this game.

Have you tried checking with NX Game Info, as I suggested? If it also tells you the xci is good, then it must be a problem with the installer, or the way you try to install. On the other hand, if NX Game Info tells you the xci is bad, then I guess NX File Viewer failed on that particular xci.

 

[Nynrah]

Corrupted file somewhere along the way, perhaps? How exactly are you trying to install it? (MTP, FTP, HTTP, dbibackend...)

I install with DBI, straight from USB thumbdrive. Checking with NxFileViewer (latest version) checks out valid for both signature and hash, but the installing itself fails (I included a screenshot a bit back in this thread, so you'd have to scroll back a bit). The result is consistent, so it's not a one-time anomaly.

Post automatically merged: Jul 20, 2025

Have you tried checking with NX Game Info, as I suggested? If it also tells you the xci is good, then it must be a problem with the installer, or the way you try to install. On the other hand, if NX Game Info tells you the xci is bad, then I guess NX File Viewer failed on that particular xci.

Yeah, I don't see any anomalies here. At least, it doesn't show red letters or error messages if that's what you mean.

As far as installers go, I just can't imagine how DBI and the way I install could be wrong. The latest Russian version of DBI didn't change anything and as far as I know there is no installer that installs better than DBI - only installers that just ignore errors and warnings and simply brute force the install anyway.

 

[CapitolLimited]

I've been noticing a ton more crashing after updating to 20.X, which I'm assuming is because of the decreased available RAM from running atmosphere and sysmodules. My question is, how do I remove some sysmodules. Is it as simple as deleting the .ovl files, or do I need to remove all traces of their respective folder from the system? Some of these have files that touch multiple folders on the SDCard, so that would be tricky.

 

[Nynrah]

Have you tried checking with NX Game Info, as I suggested? If it also tells you the xci is good, then it must be a problem with the installer, or the way you try to install. On the other hand, if NX Game Info tells you the xci is bad, then I guess NX File Viewer failed on that particular xci.

I finally got results. Turns out that it works flawlessly when I install the XCI directly from PC over USB cable (MTP responder). In other words, the issue is thankfully not in the file, but rather in DBI's handling of USB thumbdrives.

 

[Dust2dust]

I finally got results. Turns out that it works flawlessly when I install the XCI directly from PC over USB cable (MTP responder). In other words, the issue is thankfully not in the file, but rather in DBI's handling of USB thumbdrives.

Glad you got it sorted. I knew there was something fishy when you said both checkers reported the xci file as okay. Great troubleshooting! I usually use dbibackend to install my games, and never had a problem so far.

 

[Nynrah]

Glad you got it sorted. I knew there was something fishy when you said both checkers reported the xci file as okay. Great troubleshooting! I usually use dbibackend to install my games, and never had a problem so far.

The USB thumbstick is usually my go-to because I tend to keep my Switch docked and in airplane mode. But yeah, this usecase had weird written all over it. Never imagined there could be something amiss with the USB stack, especially because it's still present in the latest DBI despite all those updates it's received ever since it dropped support for English.

 

[cvskid]

If my official firmware is still on version 19 can i do a offline update to update my custom firmware to version 20.2.0 and not worry about updating the official firmware. If so what would i need to use and are there any side effects of having official and custom firmware on two different versions?

This is my first time doing a system update with custom firmware so i wanted to make sure i did it right.

 

[Nephiel]

If my official firmware is still on version 19 can i do a offline update to update my custom firmware to version 20.2.0 and not worry about updating the official firmware. If so what would i need to use and are there any side effects of having official and custom firmware on two different versions?

This is my first time doing a system update with custom firmware so i wanted to make sure i did it right.

Yes, if you have an emuNAND, you could update it to 20.2.0 and leave sysNAND at 19.x. First, make sure that your Atmosphère, Hekate, sysmodules and homebrew are on versions that support 20.2.0, and that you don't have any linked Nintendo user accounts on emuNAND, before updating.

You would have to obtain the 20.2.0 firmware update from somewhere, put the files in a folder on the SD, then run Daybreak on emuNAND CFW and select that folder. That way you update emuNAND firmware while keeping eFuses intact, so sysNAND OFW will still boot normally on an earlier FW version.

A side effect to watch out for is a battery drain issue, that happens when you have a linked Nintendo user account on the emuNAND, and then update that emuNAND to 20.x. While the console is left asleep but connected to a network, it will drain the battery fast and become warm. The only surefire way to fix this issue afterward (that I know of so far) is to rebuild the emuNAND, from a sysNAND that does not have any linked user accounts or that is already on 20.x.

 

[cvskid]

Yes, if you have an emuNAND, you could update it to 20.2.0 and leave sysNAND at 19.x. First, make sure that your Atmosphère, Hekate, sysmodules and homebrew are on versions that support 20.2.0, and that you don't have any linked Nintendo user accounts on emuNAND, before updating.

You would have to obtain the 20.2.0 firmware update from somewhere, put the files in a folder on the SD, then run Daybreak on emuNAND CFW and select that folder. That way you update emuNAND firmware while keeping eFuses intact, so sysNAND OFW will still boot normally on an earlier FW version.

A side effect to watch out for is a battery drain issue, that happens when you have a linked Nintendo user account on the emuNAND, and then update that emuNAND to 20.x. While the console is left asleep but connected to a network, it will drain the battery fast and become warm. The only surefire way to fix this issue afterward (that I know of so far) is to rebuild the emuNAND, from a sysNAND that does not have any linked user accounts or that is already on 20.x.

Just wanted to say thank you i have everything setup now. Even found out i could update sysnand using sysnand cfw which i only ever booted up to update the sysnand ofw firmware alongside emunand cfw firmware.

 

[Nephiel]

Even found out i could update sysnand using sysnand cfw

You could. If you ever boot stock OFW normally after that, eFuses will then be burnt to match what they should be at that OFW version, but this only prevents downgrading.

 

[DuplicatedPerson]

In 2022 I tried to install pokemon violet on my console directly and it got stuck in a perpetual loading.

Now its 2025 and I want to get rid of this and re-instal pokemon violet through the migswitch.

 

[Stroopwaffel]

Is there a way to enter precise numbers when partitioning with Hekate? Precise numbers with sliders is, well, less than ideal.

 

[Hayato213]

Is there a way to enter precise numbers when partitioning with Hekate? Precise numbers with sliders is, well, less than ideal.

There is just slider I believe.

Post automatically merged: Jul 26, 2025

In 2022 I tried to install pokemon violet on my console directly and it got stuck in a perpetual loading.

Now its 2025 and I want to get rid of this and re-instal pokemon violet through the migswitch.
View attachment 518765

You can try data management in system setting.

 

[DuplicatedPerson]

There is just slider I believe.

Post automatically merged: Jul 26, 2025

You can try data management in system setting.

Data management worked, thank.

 

[Stroopwaffel]

Edit: Turns out it was a bug. It will be fixed with the next update!

So finished installing LineageOS 22, and trying to sideload GApps with it during the install as per instructions. I went with the TV flavor, instead of tablet, because Marquee scrolling makes more sense for my needs, but I can't get either Android TV version of GApps to work. Both Full and Minimal, for TV 22/15 ARM64, claim that the Play Store "isn't compatible with your device," when I try and start them.

I formatted and reflashed LineageOS from TWRP for the second attempt specifically so it was a clean install. I'll probably leave this alone and sleep on it til tomorrow.