
Are you sure your sigpatches are even working?Using 19.0.1SYS/1.8.0AMS|E
I have the most recent sigpatches but the latest update for Super Smash Bros. doesn't seem to work. I get "the software was closed because an error occurred". The integrity check passes for the update, so I'm not sure what could be wrong.
Ideas?
bootloader/hekate_ipl.bin will already have everything you need to have configured.Try with sys-patch instead.Using 19.0.1SYS/1.8.0AMS|E
I have the most recent sigpatches but the latest update for Super Smash Bros. doesn't seem to work. I get "the software was closed because an error occurred". The integrity check passes for the update, so I'm not sure what could be wrong.
Ideas?
Interesting! You link to a newer version (1.5.6). Do you know what's different on this fork, compared to @impeeza 's version 1.5.5?3) Use sys-patch instead of sigpatches.

If I remember correctly, nothing much other than precious config file being removed if present upon first run of sys-patch 1.5.6 and a version dump. If you're on 1.5.5 and everything's working properly, there's no need to update.Interesting! You link to a newer version (1.5.6). Do you know what's different on this fork, compared to @impeeza 's version 1.5.5?

Do you have the latest sigpatches and/or sys-patch module installed? If not, you can try that and see if that fixes the error you're getting,What shall I do to make them work?
Try with sys-patch instead.
Thanks. Let me look into this. I have sys-patch installed (1.5.5) but wasn't clear on its functionality. What do I need to do with it?Are you sure your sigpatches are even working?
Atmosphere 1.7.0 or newer no longer supports ips kip patches which are usually used for piracy reasons. Therefore sigpatches won't work unless you:
1) Load Atmosphere's package3 via Hekate's FSS0 - You'll need to reboot to Hekate, go to Launch and select sysNAND CFW since that's what you're currently running. If you've downloaded the sigpatches from here. yourbootloader/hekate_ipl.binwill already have everything you need to have configured.
2) Use modified fusee.bin payload with ips kip patches support.
3) Use sys-patch instead of sigpatches.
I've been personally using sys-patch for more than a year now and I never run into any issues so far. While you can use sigpatches alongside sys-patch, they can be removed to reduce the clutter on your SD card.
[Atmosphere]
fss0=atmosphere/package3
kip1patch=nosigchk
Launch and select sysNAND CFW since that's what you're currently running.
19.0.1|1.8.0AMS|E.Once sys-patch is installed, you don't need to do anything special with it, just reboot your console for sys-patch to do its work. It effectively replaces sigpatches. You don't need both installed, in fact, I'm only using sys-patch here, but both can co-exist without creating conflicts, though. With sys-patch, you can boot atmosphere just using plain fusee.bin as a payload, and it will still work. You can also use Tesla overlay to see if sys-patch is working ok, but it's not mandatory.Thanks. Let me look into this. I have sys-patch installed (1.5.5) but wasn't clear on its functionality. What do I need to do with it?
My hekate setup looks like this:
Code:[Atmosphere] fss0=atmosphere/package3 kip1patch=nosigchk
Sorry, I think my shorthand may have been confusing. I'm using Atmosphere 1.8.0 on EmuNAND -19.0.1|1.8.0AMS|E.
Thanks. i am trying that now. I removed sigpatches.Once sys-patch is installed, you don't need to do anything special with it, just reboot your console for sys-patch to do its work. It effectively replaces sigpatches. You don't need both installed, in fact, I'm only using sys-patch here, but both can co-exist without creating conflicts, though. With sys-patch, you can boot atmosphere just using plain fusee.bin as a payload, and it will still work. You can also use Tesla overlay to see if sys-patch is working ok, but it's not mandatory.
The only thing I can think of is different region nsp for the update. The base game and the update should have the same ID except for the last 3 digits... 000 for base, and 800 for update.Thanks. i am trying that now. I removed sigpatches.
So far, everything looks good. I tried a few titles and they worked.
The one problem I have is that Super Smash Bros. Ultimate v29 is not booting ("an error occurred") but v0 works. I verified the update nsp integrity and didn't see any problems. Any ideas?
Yes, the IDs are the same (excluding the last three digits).The only thing I can think of is different region nsp for the update. The base game and the update should have the same ID except for the last 3 digits... 000 for base, and 800 for update.
Well, that's strange. If you're absolutely positive the nsp files are good, I guess you don't have many options. Is your emuNAND on the latest firmware (19.0.1)? Cause the update, depending if it's recent enough, might require a high firmware version. In a worse case scenario, un-install both the base game and the updates, remove the tickets for good measure with something like DBI, and then re-install again from scratch.Yes, the IDs are the same (excluding the last three digits).
Do you and see if that fixes the error you're getting,
If that doesn't help, did you try going into maintenance mode in order to clear cache? Sometimes that fixes the software refusing to start. Here's how:
If that didn't help either, try reinstalling the problematic game with the latest
- Make sure that your Internet connection is disabled if you're connected right now and remove any saved connections as well (unless you have place).
- Turn off your console (when in home menu, hold the power button for a few seconds and select power off).
- Right before you send your fusse.bin payload, hold volume + and volume - at the same time. Keep holding until you get into maintenance mode (you'll see Atmosphere bootlogo first, Switch logo after that one). After a while your Switch should enter into the maintenance mode. At this point the cache is cleared as well as any pending update you don't need to press and/or select anything.
- Press the power button once again. It'll shut down the console.
- Boot into CFW the way you usually do and make sure to activate flight mode. (Connecting to the Internet is safe only if you have DNS MITM in place.)
- Problematic game should work now.
Thanks for your replygood video on how to use it.
Otherwise, check thread for other possible solutions.
I used NxFileViewer and I also tried NSC Builder.Well, that's strange. If you're absolutely positive the nsp files are good, I guess you don't have many options. Is your emuNAND on the latest firmware (19.0.1)? Cause the update, depending if it's recent enough, might require a high firmware version. In a worse case scenario, un-install both the base game and the updates, remove the tickets for good measure with something like DBI, and then re-install again from scratch.
Out of curiosity, what did you use to check the integrity of the nsp files?

Can it be that you've installed an update from another region or skipped installing the base game entirely?But something changes. Instead "the software was closed becouse of error accured" it askes now to connect to internet and said you need to purchase the software.
You could solve it by not using Tinfoil, and downloading nsp files from some websites, then installing them with DBI or similar app.Guys tinfoil downloads very slow for me. (0.5 instead of 7-10mb/s) I tried cleaned orphaned files but speed stays very low, how do I solve it?
Guys tinfoil downloads very slow for me. (0.5 instead of 7-10mb/s) I tried cleaned orphaned files but speed stays very low, how do I solve it?