[Bug Report]:

[butawsky]

Switch Firmware Version

13.0.0 (Latest)

Atmosphère Version

1.1.1 (Latest)

Mission Control Version

0.6.0 (Latest)

Boot Method

Fusée

Issue Description

i tried to install mission control yesterday (latest release) but everytime i copied a new files to my content folder (via usb tool in hekate) and boot cfw using fusee i always had a blackscreen after atmos logo.. tried to remove mission control and copy a new file to atmos/content folder works fine again.. btw i also use sys-tweak

ams 1.1.1 fw 13.0

Error Report

No response

Additional Context

No response

[ndeadly]

Typically, black screens on boot occur for one of two reasons. Either you have a mistmatched Atmosphere/Mission Control version, or there is some other custom sysmodule installed that is interfering. I am running all the latest versions you've stated above and have never had any issues with booting, so I'm tempted to say it's a problem with your environment.

Can you show me what's in your atmosphere/contents directory? It's also probably worth redownloading the latest Atmosphere and Mission Control versions from their official github releases and reinstalling to make sure you're really running the versions you think you are.

[butawsky]

most of them are for custom icons and i always downloaded the files from official github.. maybe because of systweak?i remember that systweak is only recompile for ams 1.1.0 ...

thankyou very much for answering btw...

[ndeadly]

contents looks alright, but I would try temporarily renaming it to something else and then reinstalling Mission Control so that it's the only thing in the directory to be sure that there's nothing interfering. sys-tweak hasn't been known to create problems, but you never know.

Is there anything else different about your setup that I should know about? Have you messed with the settings in config/MissionControl or anything?

[butawsky]

i dont do anything about config/missioncontrol i just copy/paste it...

again thank you very very much for answering and for making this sysmodule ..i will try all of your suggestion and hope for the best 😬

[moto180]

Switch Firmware Version 13.0.0 (Latest)

Atmosphère Version 1.1.1 (Latest)

Mission Control Version 0.6.0 (Latest)

Boot Method Fusée

Issue Description Same exact problem except the only thing in my contents folder is mission control stuff.

ams 1.1.1 fw 13.0

Error Report No response

Additional Context Everything works normally once I remove MissionControl. I tried clean copying MissionControl but didn't work. it was working previously but it seemingly stopped working

[ndeadly]

@moto180 are you actually running Atmosphere 1.1.1 or have you installed the 1.2.0 pre-release version that was just released today? (I haven't updated the issue templates yet) Mission Control needs to be updated to work with this due to a bunch of breaking changes. A black screen would be expected in this case

[moto180]

yeah 1.1.1

[ndeadly]

Can you give me any additional information about your setup/contents of your SD card? What have you done between now and when it stopped working?

I am booting many times a day during development and have never encountered a black screen that wasn't due to a breaking atmosphere update. The fact that this is the only report of such an issue from ~8k downloads of the latest release suggests that this is not a widespread issue, and is more likely to be something unique to your console.

[moto180]

I turned off my console as usual so i could boot into the switchs' nand. I then tried to reboot into emunand so I booted into RCM the usual way and injected the payload but it black screened after AMS logo. I then tried to boot again and I got in but this time I got the corrupted data on microSD message in the emunand so my switch erased the corrupted data and reset itself but black screen after AMS logo again. I then reset my switch and went into RCM mode again and injected and then black screen after AMS logo again. I then hard powered off switch and tried multiple times to reboot into emunand but it just black screened after AMS logo. I then removed mission control and it finally booted.

I'm gonna try deleting my atmosphere folder and fresh copy of ams 1.1.1 and the patches along with mission control to see if I can get it to work.

[moto180]

I didn't add anything to my microSD from the time it worked and the time it didn't.

[moto180]

I deleted the atmosphere folder and fresh copied in a new 1.1.1 one and installed patches and mission control. my switch booted into emunand immediately on the first try. However after trying it again to make sure it works permanently I powered off and reinjected the payload and it black screened after AMS logo again. I tried injecting twice and it still black screened. I then removed Mission Control from my microSD and it booted on the first try.

idk what's happening but it seems booting into emunand a second time is causing the problem.

I was also able to pair my ps4 controller after the first boot fresh install

[moto180]

I updated to the recent Mission Control and HOS and my switch is no longer showing the problems stated. I think the problem may had something to do with my EXFAT formatted microSD corrupting all my installed games randomly. I would say this issue is solved but I am not the OP. Thanks for all your hard work.

[ndeadly]

@moto180 thanks for the followup. Corruption sounds likely in your case if everything else was otherwise up to date.

[ndeadly]

Closing due to inactivity. Original issue is likely user-related and not a Mission Control bug