Hacking Switch randomly freezing while atmosphere boots.

[HBubli]

Sometimes when i start atmosphere the switch gets stuck on a blackscreen after the 3rd logo (the one before the switch logo). Pressing the power or any other buttons does absolutely nothing. To get out of it i have to force power off and go into rcm and inject the payload again. Is this normal, and if not, how can i fix it?

 

[Calzy_G]

Sometimes when i start atmosphere the switch gets stuck on a blackscreen after the 3rd logo (the one before the switch logo). Pressing the power or any other buttons does absolutely nothing. To get out of it i have to force power off and go into rcm and inject the payload again. Is this normal, and if not, how can i fix it?

Had it myself a couple of times on the latest Atmosphere and have no idea why. It's a bit annoying.

 

[Maupiti]

Sometimes when i start atmosphere the switch gets stuck on a blackscreen after the 3rd logo (the one before the switch logo). Pressing the power or any other buttons does absolutely nothing. To get out of it i have to force power off and go into rcm and inject the payload again. Is this normal, and if not, how can i fix it?

How is your sd card formatted ?

 

[HBubli]

How is your sd card formatted ?

FAT32.

 

[Maupiti]

FAT32.

How did you update AMS ? Copy paste or deleting ? How do you launch AMS ? Fusee primary ?

 

[HBubli]

How did you update AMS ? Copy paste or deleting ? How do you launch AMS ? Fusee primary ?

Copy paste, and fusee primary.

 

[Maupiti]

Copy paste, and fusee primary.

Do you have any sysmodules running ? (Tesla menu, Edizon, Emuibo..)
You can try a clean install deleting sept folder
Are your sigpatches uptodate?

 

[HBubli]

Do you have any sysmodules running ? (Tesla menu, Edizon, Emuibo..)
You can try a clean install deleting sept folder
Are your sigpatches uptodate?

Yeah i do have sysmodules, and sigpatches are up to date.

 

[Maupiti]

Yeah i do have sysmodules, and sigpatches are up to date.

So disable sysmodules, and enable them one by one, you may find one giving issue with your AMS version

 

[HBubli]

So disable sysmodules, and enable them one by one, you may find one giving issue with your AMS version

I'll try the next time it happens.

 

[AamitMorthos]

Hey, I'm having this same problem as well. I also use sysmodules but I'm pretty sure they were disabled when I updated. However, I'm able to boot just fine after removing the contents folder. I thought maybe it had something to do with sys-clk's folder so I removed that and still nothing. I read that ppl were saying to delete 0100000000001000 but I don't have that folder.

edit: I'm currently moving the stuff I had in contents over one by one to see which one stops it from booting...

edit 2: So I found out, for me, it was folder 010000000000bd00. I'm unsure if this folder would've had the same contents as 0100000000001000 does, but removing that helped. I'm also not sure if the bd00 folder has stuff I actually need. Would it be fine to just leave it out for right now?

 

[Calzy_G]

I can't figure out why it has happened randomly for me. FAT32 and no sys modules. Clean Atmosphere and latest sig patches.

Could possibly have something to do with migrating the sxos emunand to Atmosphere and the installed games showing up as corrupted.

I've since deleted everything other than saves and reinstalled all games with DBI over USB.

Seems fine so far but who knows.

 

[Maupiti]

Hey, I'm having this same problem as well. I also use sysmodules but I'm pretty sure they were disabled when I updated. However, I'm able to boot just fine after removing the contents folder. I thought maybe it had something to do with sys-clk's folder so I removed that and still nothing. I read that ppl were saying to delete 0100000000001000 but I don't have that folder.

edit: I'm currently moving the stuff I had in contents over one by one to see which one stops it from booting...

edit 2: So I found out, for me, it was folder 010000000000bd00. I'm unsure if this folder would've had the same contents as 0100000000001000 does, but removing that helped. I'm also not sure if the bd00 folder has stuff I actually need. Would it be fine to just leave it out for right now?

Do you have saltyNx installled ? Some sysmodules can be toggled off on reboot, but some will re-enable after a reboot. The only way to be sure to not load a sysmodule and activate it manually is to edit the config in AMS. Be sure to have all sysmodules up to date to avoid conflict with latest release of AMS.

Could possibly have something to do with migrating the sxos emunand to Atmosphere and the installed games showing up as corrupted..

Yes, as corrupted games can crash loading the album.

 

[bad361]

Hey, I'm having this same problem as well. I also use sysmodules but I'm pretty sure they were disabled when I updated. However, I'm able to boot just fine after removing the contents folder. I thought maybe it had something to do with sys-clk's folder so I removed that and still nothing. I read that ppl were saying to delete 0100000000001000 but I don't have that folder.

edit: I'm currently moving the stuff I had in contents over one by one to see which one stops it from booting...

edit 2: So I found out, for me, it was folder 010000000000bd00. I'm unsure if this folder would've had the same contents as 0100000000001000 does, but removing that helped. I'm also not sure if the bd00 folder has stuff I actually need. Would it be fine to just leave it out for right now?

010000000000bd00 is for Mission Control sys-module. And you have to update it after installing new atmos ver. cause it clearly says on github Atmosphère >= 0.19.5 is required to run this release. So if you updated your atmos and forgot to update mission control, most probably that was the reason why you had problems on boot.

If you have any issues when booting atmos, always try do a clean setup, this will solve most of your problems. Then you can just add your stuff 1 by 1 and update if necessary.

 

[AamitMorthos]

Do you have saltyNx installed? Some sysmodules can be toggled off on reboot, but some will re-enable after a reboot. The only way to be sure to not load a sysmodule and activate it manually is to edit the config in AMS. Be sure to have all sysmodules up to date to avoid conflict with latest release of AMS.

010000000000bd00 is for Mission Control sys-module. And you have to update it after installing new atmos ver. cause it clearly says on github Atmosphère >= 0.19.5 is required to run this release. So if you updated your atmos and forgot to update mission control, most probably that was the reason why you had problems on boot.

I've never used saltyNx before but I have tried out mission control. I had removed it after trying it so I didn't think to update it, ya know. Seems I forgot to remove its folder from contents.

 

[bad361]

I've never used saltyNx before but I have tried out mission control. I had removed it after trying it so I didn't think to update it, ya know. Seems I forgot to remove its folder from contents.

Doesn't look like you removed it if the folder was still there.

 

[Maupiti]

Mission control effectively…

 

[Draxzelex]

I can't figure out why it has happened randomly for me. FAT32 and no sys modules. Clean Atmosphere and latest sig patches.

Could possibly have something to do with migrating the sxos emunand to Atmosphere and the installed games showing up as corrupted.

I've since deleted everything other than saves and reinstalled all games with DBI over USB.

Seems fine so far but who knows.

If the games are showing up as corrupted, you are missing the patches which can be found under the pinned thread on this forum.