Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,791,844
  • Replies Replies 9,395
  • Likes Likes 93
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.
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?
 
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?
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?
 
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?
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 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
 
OK here is the error screen again

Thanks in advance.
 

Attachments

  • IMG_20220320_182748.jpg
    IMG_20220320_182748.jpg
    2.2 MB · Views: 96
OK here is the error screen again

Thanks in advance.
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/

Edit: Seems I was wrong about the themes, but deleting this folder should still fix your problem
 
  • Like
Reactions: binkinator
you aren't wrong about the themes, that folder is one of the themes, delete that and the others related to themes:

0100000000001000
0100000000001007
0100000000001013

and any other folder related to sysmodules. the safest way is to backup and delete CONTENTS folder, boot and THEN reinstall any theme(when become supported on the new FW), sysmodule (if is supported on the new FW) cheat, and MOD you have.
 
0100000000001000 is not "the themes", it's qlaunch in general. It's something that can be modified with themes but it's entirely possible for it to have crashes which are not caused by themes. Especially here where it just randomly crashes mid-play, if there was a faulty theme you wouldn't have been getting in game to begin with.

I 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
I'm interested in that theory, given that with emummc you'd expect things to crash if SD card lost connection ;P
 
0100000000001000 its really HOS menu. Yo can modify that app for theming. For nevi replacement (qmenu, umenu, etc.). The important IS YOU NEED TO REMOVE THAT FILDER and only copy there files compatibles with the new Atmosphère 1.3.0. Many homebrew need get corrected for work on it
 
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.
 

Attachments

  • IMG_20220326_105153_4.jpg
    IMG_20220326_105153_4.jpg
    837.2 KB · Views: 75
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.
You need to update hekate, too.
 
  • Like
Reactions: impeeza and bjaxx87

Site & Scene News