Brick recovery is the main reason for having them.
But I upgraded and downgraded all the time for testing stuff.
But seriously keep a nand backup for recovery
Brick recovery is the main reason for having them.
But I upgraded and downgraded all the time for testing stuff.
But seriously keep a nand backup for recovery
Hi, I have a problem when I install games with Tinfoil, after installing them, when I launch them sometimes I get this message "The software was closed because an error occured".
It doesn't do that with all the games but a good part still. Like Persona 5 Strikers, Xenoblade Chronicles 2 etc... I tried to download the games elsewhere but It does the same result.
I'm on 12.0, on the latest version of Atmosphere, Hekate and I think I have the latest sigpatches too. This also happened on the old firmware 11.0.1.
I don't know what to do, do you have any suggestions?
Thanks
It doesn't do that with all the games but a good part still. Like Persona 5 Strikers, Xenoblade Chronicles 2 etc... I tried to download the games elsewhere but It does the same result.
I'm on 12.0, on the latest version of Atmosphere, Hekate and I think I have the latest sigpatches too. This also happened on the old firmware 11.0.1.
I don't know what to do, do you have any suggestions?
Thanks
Okay but in 11.0.1 the same games didn't work either and I didn't find a solution, while other people didn't have this problem with the same games
Firstly, 12.0.0 es patches arent working yet so while the issue may be unrelated to sigpatches, you will still not be able to run them until you downgrade or patches are out (assuming they are nsp copies and not xci)
Secondly, theres two likely fixes to the issue. One is that it may be a sysmodule interference. Its not uncommon for certain games to conflict with sysmodules and not launch until the sysmodule is removed, so id try removing all sysmodules temporarily, easiest way is to rename the atmosphere folder and put on a fresh one from the atmosphere github with sigpatches and *nothing* else. Second possible fix is sometimes games cache bad data, and you can fix it by booting maintenance mode while launching the nand that the games are on. An example of how to do this would be to boot into rcm, hold volume up and down, while still holding them push fusee primary, then once you see the new unique menu let go of volume. Dont select any options in maintenance mode, just booting it clears the cache.
The only way to hack it is with the SX Core modchip which requires soldering and is hard to track down. There is also nobody actively working on finding an exploit for patched units so you're better off buying an unpatched console.
I dont like the 'v1 and v2' thing because not all eristas are unpatched. SOME original non mariko systems can be modded without a modchip. And yes you can download games from pc.
There is no such thing as "v1" or even a "v2". There are about 3 types of Nintendo Switch consoles: unpatched Erista units, patched Erista units, and Mariko units. Both patched Erista and Mariko units cannot be hacked without a modchip (you can technically hack a patched Erista unit if the firmware is 4.1 or lower but this is unlikely). Unpatched Erista units can be hacked regardless of firmware. As for your second question, the answer is yes.
I assume this is the same reason for getting a "Could not start the software. Please try again from the HOME screen" on every game since updating to Atmosphere v 0.19 ??
But, hey, @Draxzelex you were right about it not being a corrupted SD card
--------------------- MERGED ---------------------------
Well the latest files in the OP of this thread - https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-secondary-only.571543/ - appear to have a fixed practically all my "could not start the software" errors but on same games I am now getting "corrupted data detected" (or something like that). Is that easy to fix or do those need a re-install ? And a re-install is needed, will the saved games files still be there ?
- Joined
- Jul 23, 2018
- Messages
- 6,056
- Trophies
- 1
- Age
- 29
- Location
- Lampukistan
- Website
- hmpg.net
- XP
- 6,169
- Country
The saves are on the emmc chip. Or if you use an emummc, on the hidden partition.
I believe I had this error once. The problem is the Switch thinks the games are corrupted but in reality they aren't because they are pirated. While you could re-install them, I think if you let the Switch try to diagnose the issue without deleting the game, it should let you launch it provided you're in CFW.
I will give that a try with some others. I already tried that with one of them and it said I had to 'redownload'. Not a major issue - if, as @BaamAlex says, the save files are safe - just a minor annoyance :|
THANK YOU!!! I did the second fix and my games are working now!!! It's been days since I had this problem, thank you again
Hi everyone! I'm planning on buying an SX Core to mod my Nintendo Switch.
I've tried hacking it before, but it was not possible to get it to load the fusee-test. That was like 2 years ago.
Now the console is on 12.0 firmware and I want to confirm that the SX Core will work with it.
If so, what are the steps for getting it to work and have a dual booting option (Emu AND Sys Nand) ?
Thank you.
I've tried hacking it before, but it was not possible to get it to load the fusee-test. That was like 2 years ago.
Now the console is on 12.0 firmware and I want to confirm that the SX Core will work with it.
If so, what are the steps for getting it to work and have a dual booting option (Emu AND Sys Nand) ?
Thank you.
So I have some good and bad news. The good news is that you will be able to hack your console. The bad news is that you will not be able to use the CFW that comes with the SX Core because SX OS does not support any firmware higher than 11.0. The caveat is that Atmosphere supports even the latest firmware. If you want a guide, I recommend following this one. However are you sure that your console is patched? Just because it fails the test doesn't mean its patched because there are other factors that can make the exploit fail such as USB port, cable, or even OS.
