Hacking SWITCH NOOB PARADISE - Ask questions here

[Themscope]

I’m on an emummc that is version 12.0.1 and atmosphere version 0.19.2

 

[Draxzelex]

I need help with my sigpatches i cant get them to work none of my games open and i cant get out of applet mode and run awoo installer

Well do you know that there are actually 2 different sets of patches for Atmosphere? They are differentiated by the bootloader used to launch Atmosphere which are either fusee or Hekate so if you are having issues with the patches, its possible your patches don't match your bootloader? It is also possible that wherever you obtained the patches are not up to date. Lastly, Applet Mode is a consequence of how you launch a homebrew application. If you launch it via an Applet such as the Album, naturally you will be in Applet Mode.

 

[KoalaMelba]

Hello.

I've recently hacked my Switch, but am having issues installing two base games on it (the DLC for the two games installs as expected). I've tried Awoo, Goldleaf and TinWoo; I'm using Hekate, so haven't tried Tinfoil. I've tried nsp and xci, and different sources.

The error I got from Awoo and TinWoo were "OpenFileSystemWithId:124: Failed to open file system" and "OpenFileSystemWithId:122: Failed to open file system" respectively. Search indicates that this is a sigpatches issue, however, I've downloaded the most recent sigpatches using AIO Updater, and all other games are working perfectly, it's just these two base games.

Firmware: 12.0
Atmosphere: 0.19.2
Hekate: 5.5.5
AIO Updater: 2.4.9

Any suggestions?

 

[Draxzelex]

Hello.

I've recently hacked my Switch, but am having issues installing two base games on it (the DLC for the two games installs as expected). I've tried Awoo, Goldleaf and TinWoo; I'm using Hekate, so haven't tried Tinfoil. I've tried nsp and xci, and different sources.

The error I got from Awoo and TinWoo were "OpenFileSystemWithId:124: Failed to open file system" and "OpenFileSystemWithId:122: Failed to open file system" respectively. Search indicates that this is a sigpatches issue, however, I've downloaded the most recent sigpatches using AIO Updater, and all other games are working perfectly, it's just these two base games.

Firmware: 12.0
Atmosphere: 0.19.2
Hekate: 5.5.5
AIO Updater: 2.4.9

Any suggestions?

Don't use the AIO updater or any other tool to download patches. You should always download patches manually as there can be bugs in homebrew apps or programs that don't download the latest patches. Get the most up-to-date patches from here.

 

[Themscope]

I tried using hekate and fusee along with their sigpatches and still wasn’t able to get out of the applet mode or open games I tried opening a the full home brew launcher by holding the r trigger while opening a game and I just get an error this has been annoying me for 2 days

 

[Draxzelex]

I tried using hekate and fusee along with their sigpatches and still wasn’t able to get out of the applet mode or open games I tried opening a the full home brew launcher by holding the r trigger while opening a game and I just get an error this has been annoying me for 2 days

Well if you leave out crucial details, it becomes harder to help you. For example, you only just now mentioned you got an error trying to open the homebrew menu by holding R on a game. How would we have known that? And you're not even mentioning the code which is always accompanied with any error on the Switch. I understand you're frustrated but being vague and leaving out information makes it equally frustrating to help you because we don't know what the problem is.

 

[Themscope]

I get the error “unable to launch game return to home menu and try again” while holding the r trigger and opening a game and just trying to open a game In general and some games when I try to open them it says corrupt data detected. Anything else you need to know

 

[Draxzelex]

I get the error “unable to launch game return to home menu and try again” while holding the r trigger and opening a game and just trying to open a game In general and some games when I try to open them it says corrupt data detected. Anything else you need to know

Where did you download your patches from? Also where did you download Atmosphere and Hekate from?

 

[Themscope]

Both came from the most recent GitHub releases

 

[Draxzelex]

Both came from the most recent GitHub releases

For Atmosphere, that is fine but Hekate doesn't work out of the box if you just download it straight from its GitHub page. The most important file missing would be the hekate_ipl.ini file which while you can configure yourself, most people do not. Did you ever download Hekate from anywhere else before? Also the patches don't have an official GitHub page so you will have to be more specific.

 

[Themscope]

I used and configured the ini in hekate and I got the sigpatches from https://github.com/ITotalJustice/patches/releases

 

[Redverd]

Hello. I need help, I'm trying to migrate from SXOS to Atmosphere but I encountered a problem which is due to my noob action.
I updated my sysnand using choidujourNX.

I found a solution but I don't have the necessary item or knowhow to do it.

I found this on rentry:
"If you updated via ChoiDujourNX on your sysNAND then you have to either get a donor boot0/boot1 or use a backup of your sysNAND boot0/boot1 and then restore it via NxNandManager, hekate, or sxos bootmenu. This is because ChoiDuJourNX corrupts your boot0/boot1 and will prevent you from being able to boot into sysNAND on Atmosphere."

Can anyone help me?
I need a donor boot0/boot1 and maybe a step by step on how to restore it? The site doesn't mention how to do it.

 

[Draxzelex]

I used and configured the ini in hekate and I got the sigpatches from https://github.com/ITotalJustice/patches/releases

I had a feeling that is where you got the patches from. There is only one place where I trust to get patches and that is from the pinned thread on this forum.

Hello. I need help, I'm trying to migrate from SXOS to Atmosphere but I encountered a problem which is due to my noob action.
I updated my sysnand using choidujourNX.

I found a solution but I don't have the necessary item or knowhow to do it.

I found this on rentry:
"If you updated via ChoiDujourNX on your sysNAND then you have to either get a donor boot0/boot1 or use a backup of your sysNAND boot0/boot1 and then restore it via NxNandManager, hekate, or sxos bootmenu. This is because ChoiDuJourNX corrupts your boot0/boot1 and will prevent you from being able to boot into sysNAND on Atmosphere."

Can anyone help me?
I need a donor boot0/boot1 and maybe a step by step on how to restore it? The site doesn't mention how to do it.

Did you use ChoiDujourNX on a Mariko Switch?

 

[Redverd]

I had a feeling that is where you got the patches from. There is only one place where I trust to get patches and that is from the pinned thread on this forum.

Did you use ChoiDujourNX on a Mariko Switch?

yes

 

[Themscope]

Ok I’ll try those patches when I get home and update on whether it works or not

 

[KoalaMelba]

Don't use the AIO updater or any other tool to download patches. You should always download patches manually as there can be bugs in homebrew apps or programs that don't download the latest patches. Get the most up-to-date patches from here.

That worked, thanks.

 

[codexdragon]

Quick question, I'm following the homebrew guide.

When you use lockpick to make a backup of your keys, u then copy it to a safe folder on your PC. Do you delete it from your sd card? I just backed up the eMMC boot0 etc, and on the guide it says to delete it from the sd card after backing it up. It doesn't say what to do with the switch/prod.keys file after you back it up. Delete it from sd card? Leave it on there?

 

[Draxzelex]

Quick question, I'm following the homebrew guide.

When you use lockpick to make a backup of your keys, u then copy it to a safe folder on your PC. Do you delete it from your sd card? I just backed up the eMMC boot0 etc, and on the guide it says to delete it from the sd card after backing it up. It doesn't say what to do with the switch/prod.keys file after you back it up. Delete it from sd card? Leave it on there?

This is why guides explained to you the why instead of what...Anyways, the purpose of backing up keys is two-fold: certain tools require a keys file populated with the public Switch keys and in the event you do not have an eMMC backup, you can regenerate most of your eMMC provided you have a dump of your console-specific keys otherwise known as the BIS keys. So as you can see, neither of these require them to be actively on the SD card. Its a similar principle to eMMC backups where they are moreso meant to be reserved for a rainy day rather than something you keep on hand at all times.

 

[codexdragon]

This is why guides explained to you the why instead of what...Anyways, the purpose of backing up keys is two-fold: certain tools require a keys file populated with the public Switch keys and in the event you do not have an eMMC backup, you can regenerate most of your eMMC provided you have a dump of your console-specific keys otherwise known as the BIS keys. So as you can see, neither of these require them to be actively on the SD card. Its a similar principle to eMMC backups where they are moreso meant to be reserved for a rainy day rather than something you keep on hand at all times.

Thank you!! I figured that's what it was. I just didn't want to delete it from my sd card and it ended up being something that was supposed to stay on there.

 

[Themscope]

i tried the new patches and it still doesn't work