Can't play games, "An error occured"

  • Thread starter Thread starter Mimikyu
  • Start date Start date
  • Views Views 1,569
  • Replies Replies 17

Mimikyu

Well-Known Member
Member
Joined
Apr 1, 2020
Messages
148
Reaction score
23
Trophies
1
Age
26
Location
The Shadow Realm
XP
837
Country
Germany
Hello. Lately while installing some games I found myself with two games successfully installed but not being able to play them. The one game being Mario Party Jamboree, opes, like the switch banner shows up and then it's telling me "Software has closed because an error occurred".

I have the latest Atmosphere and sys-patch version installed. My CFW is on Version 16.0.0, and I don't really want to update.

Is there any way to get those games to work?
 
Last edited by Mimikyu,
Yeh, the thing is tho that I could install Luigi's Mansion 2 HD with 16.0.0, eventho I would have needed 18.0.0
Not sure what could be there. Could be that your most updated Atmosphere is incompatible with 16.0 firmware for some things, for example my CFW wouldn't boot at all with the most recent Atmosphere with firmware 19.0. It could also be that Jamboree needs something from 18.0 that Luigi's Mansion doesn't.
 
  • Like
Reactions: Mimikyu
i am pretty sure (unproven) that the newmario party wont run on 16.0.0
also, there are always two requirements: the encryption key used and the firmware version
i also often are able to install a game that "requires the semi-newest firmware" (20) but works and only needs an older decryption key , like 18
 
  • Like
Reactions: Mimikyu
So you say I should install the cfw 18.0.0? Is everything from the homebrew part still working there? I didn't update cause ppl said many thing wouldn't work on 18.0.0, that's why I didn't want to update.
And updating with Daybreak right? Without loosing any data?
 
So you say I should install the cfw 18.0.0? Is everything from the homebrew part still working there? I didn't update cause ppl said many thing wouldn't work on 18.0.0, that's why I didn't want to update.
And updating with Daybreak right? Without loosing any data?
Yes everything work on 18.x.x (and 19 for that matter). I think most also work on 20 but I would not upgrade to that version yet
 
  • Like
Reactions: Mimikyu
https://switch.hacks.guide/extras/updating.html?tab=dumping-your-firmware-via-tegraexplorer

I assume I need to follow this guide, right? Another small question, it says that I have to dump the firmware of the sysMMC. Do I have to update in the sysMMC or can I update the OFW/Stock, to dump it in sysMMC? I'm rather new to this stuff around the sysMMC, and I'm kinda scared of bricking or getting banned while being online with Homebrew stuff.
If you update your SysMMC the official way then it will be updated to the latest version (20.3.0). You could also find the firmware version you want by Googling 'Switch firmware 18.1.0' for instance. There is another guide here on GBATemp that you could also follow: https://gbatemp.net/threads/ultimate-guide-to-upgrade-your-firmware-atmosphere.661148/
 
  • Like
Reactions: Mimikyu
If you update your SysMMC the official way then it will be updated to the latest version (20.3.0). You could also find the firmware version you want by Googling 'Switch firmware 18.1.0' for instance. There is another guide here on GBATemp that you could also follow: https://gbatemp.net/threads/ultimate-guide-to-upgrade-your-firmware-atmosphere.661148/
Just found out that my OFW is luckily on 18.1.0 so I just have to dump it 🥹👍🏻
Thanks y'all for the help!
Post automatically merged:

Another question :,(
It says:

Starting the process.​

Restart your console to Hekate's NYX and load UMS tool, or remove the card and put on your PC, is up to you, Hakate may be a little bit slower but you do not risk physically your console.
  • Delete SDMC:/atmosphere/contents or SDMC:/atmosphere/titles, you should have backed up this folder before.
  • Delete the next folders, that's because the first time you load new Atmosphère that folders will emptied and that can take a lot of time so you could think your console got frozen, so in order to avoid that false alarm it's better to delete them before start console.
    • SDMC:/atmosphere/crash_reports
    • SDMC:/atmosphere/erpt_reports
    • SDMC:/atmosphere/fatal_reports
  • If you had used INCOGNITO_RCM, is advisable to remove incognito from yours *NAND, having PRODINFO blanked via Incognito RCM can create problems on the new firmware/atmosphère versions.
  • Extract Atmosphère zip file and copy to the root of your SD, overwrite all files.
  • Edit your SDMC:/exosphere.ini file and add/change the next values to «1» in order to enable Atmosphère incognito on telemetry:
blank_prodinfo_sysmmc=1
blank_prodinfo_emummc=1

[*]Enable DNSMiTM, by editing the SDMC:/atmosphere/config/system_settings.ini and be sure the parameter enable_dns_mitm have the value u8!0x1:
[/LIST]
enable_dns_mitm = u8!0x1
Be sure you remove the «;» at start of the line.
  • Extract the downloaded Hekate zip file, and copy to the root of your SD, overwrite all files.
  • Upgrade your payload.bin file, if you use a injector on the injector, if you use a modchip replacing the file SDMC:/payload.bin file, if you use Hekate rename the file hekate_ctcaer_X.Y.Z.bin to payload.bin and copy to root of your SDCard.
  • Extract the sigpatches file and copy to the root of your SD Card, overwrite all files.
  • Etract the Sys-Patch zip file and copy to the root of your SD Card, overwrite all files.
  • Create a folder on your SD Card and copy on it the extracted files for the firmware.
Everything makes sense but I don't quite understand the part with Incognito_RCM, i mean i have that but i'm not sure if i have the rcm version? i use it with the tool/app: 90DNS. Like do i have to delete those files anyways even if Atmosphere is fine with it? This is quite confusing... but i have a dump, that worked!
Also it says later on i should boot into the HOS, is that the emuMMC? or OFW?
 
Last edited by Mimikyu,
Just found out that my OFW is luckily on 18.1.0 so I just have to dump it 🥹👍🏻
Thanks y'all for the help!
By doing that, you lose save data/games that are only on your emuNAND since it overwrites everything, unless you take special care to only do the sys partition and boot0/boot1.

It's honestly way easier and quicker to just update with daybreak. Takes literally a couple minutes.

So you say I should install the cfw 18.0.0? Is everything from the homebrew part still working there? I didn't update cause ppl said many thing wouldn't work on 18.0.0, that's why I didn't want to update.
And updating with Daybreak right? Without loosing any data?
I'd recommend 19.x at the least because some games require it. No point in updating to such an ancient firmware then need to update again in a few weeks because you found more games that don't work.
 
  • Like
Reactions: Mimikyu
By doing that, you lose save data/games that are only on your emuNAND since it overwrites everything, unless you take special care to only do the sys partition and boot0/boot1.

It's honestly way easier and quicker to just update with daybreak. Takes literally a couple minutes.


I'd recommend 19.x at the least because some games require it. No point in updating to such an ancient firmware then need to update again in a few weeks because you found more games that don't work.
So wait you're telling me dumping is useless? I just want to update my EmuMMC. By updating i delete everything?
 
Just found out that my OFW is luckily on 18.1.0 so I just have to dump it 🥹👍🏻
Thanks y'all for the help!
Post automatically merged:

Another question :,(
It says:

Starting the process.​

Restart your console to Hekate's NYX and load UMS tool, or remove the card and put on your PC, is up to you, Hakate may be a little bit slower but you do not risk physically your console.
  • Delete SDMC:/atmosphere/contents or SDMC:/atmosphere/titles, you should have backed up this folder before.
  • Delete the next folders, that's because the first time you load new Atmosphère that folders will emptied and that can take a lot of time so you could think your console got frozen, so in order to avoid that false alarm it's better to delete them before start console.
    • SDMC:/atmosphere/crash_reports
    • SDMC:/atmosphere/erpt_reports
    • SDMC:/atmosphere/fatal_reports
  • If you had used INCOGNITO_RCM, is advisable to remove incognito from yours *NAND, having PRODINFO blanked via Incognito RCM can create problems on the new firmware/atmosphère versions.
  • Extract Atmosphère zip file and copy to the root of your SD, overwrite all files.
  • Edit your SDMC:/exosphere.ini file and add/change the next values to «1» in order to enable Atmosphère incognito on telemetry:
blank_prodinfo_sysmmc=1
blank_prodinfo_emummc=1

[*]Enable DNSMiTM, by editing the SDMC:/atmosphere/config/system_settings.ini and be sure the parameter enable_dns_mitm have the value u8!0x1:
[/LIST]
enable_dns_mitm = u8!0x1
Be sure you remove the «;» at start of the line.
  • Extract the downloaded Hekate zip file, and copy to the root of your SD, overwrite all files.
  • Upgrade your payload.bin file, if you use a injector on the injector, if you use a modchip replacing the file SDMC:/payload.bin file, if you use Hekate rename the file hekate_ctcaer_X.Y.Z.bin to payload.bin and copy to root of your SDCard.
  • Extract the sigpatches file and copy to the root of your SD Card, overwrite all files.
  • Etract the Sys-Patch zip file and copy to the root of your SD Card, overwrite all files.
  • Create a folder on your SD Card and copy on it the extracted files for the firmware.
Everything makes sense but I don't quite understand the part with Incognito_RCM, i mean i have that but i'm not sure if i have the rcm version? i use it with the tool/app: 90DNS. Like do i have to delete those files anyways even if Atmosphere is fine with it? This is quite confusing... but i have a dump, that worked!
Also it says later on i should boot into the HOS, is that the emuMMC? or OFW?
Could you also please help me with that? If you know something about it?
 
So wait you're telling me dumping is useless? I just want to update my EmuMMC. By updating i delete everything?
Depends what you mean by dumping. Dumping the firmware as nsps, sure, you can do that and use those files with Daybreak. Dumping sys to emu with Hekate essentially creates a new emuNAND.
 

Site & Scene News

Popular threads in this forum