Have fun.Hooray!.. Now, we needsigpatches/ Hekate support.
https://github.com/ITotalJustice/patches/releases/tag/14.0.0-1.3.0Hooray!.. Now, we needsigpatches/ a Hekate support.
No game card plugged in. It just crashes randomly while playing. I have not jet found a cause for the crash. It just seems random, for example: My son plays a game, hands me the console to finish a level, it crashes.Do you have a game in? Remove it and try again.
Does it tend to happen when the console is moved, like this example? Do you play enough in OFW (Atmosphere not running) to know if it ever happens there too?No game card plugged in. It just crashes randomly while playing. I have not jet found a cause for the crash. It just seems random, for example: My son plays a game, hands me the console to finish a level, it crashes.
That means, your console doesn't like you xDMy son plays a game, hands me the console to finish a level, it crashes.
I never use ofw^^ I always use emummc(hidden partition) on both of my switches. I own 2 consoles, both used to be on sx os.,but I did a compleat format of the SD cards and factory resented the consoles befor migrating to atmo. So the crash screen doesn't give any indication on why it crashed?Does it tend to happen when the console is moved, like this example? Do you play enough in OFW (Atmosphere not running) to know if it ever happens there too?
If it's the Atmosphere fatal screen with all the numbers and addresses, then yeah lots of info, get a photo of it if you can. I wouldn't be able to decode that, but someone smarter like SciresM could tell a lot from that screen and any crash logs that get saved.I never use ofw^^ I always use emummc(hidden partition) on both of my switches. I own 2 consoles, both used to be on sx os.,but I did a compleat format of the SD cards and factory resented the consoles befor migrating to atmo. So the crash screen doesn't give any indication on why it crashed?
After a quick google search, it seems the TitleID 0100000000001000 relates to custom themes. Do you have any installed? In either case, you need to delete the folder "0100000000001000" inside ./atmosphere/contents/OK here is the error screen again
Thanks in advance.
I'm interested in that theory, given that with emummc you'd expect things to crash if SD card lost connection ;PI was asking whether it seemed to be related to physical movement in case there's a loose connection in the hardware somewhere - the SD slot is known for that, for example
You need to update hekate, too.Sorry for being a noob, but... help? I updated to the latest version of Atmosphère (1.3.0-prerelease) and entered Stock CFW to update my SysNAND. Now I can't boot into Stock (without CFW) anymore and receive an error. My outdated EmuNAND runs fine.
Ahh, thank you, that did the trick. In the past I always used sdsetup which included everything necessary, so I wasn't aware of this.You need to update hekate, too.