OK, what have I done wrong this time?

  • Thread starter Thread starter Waifu4Life
  • Start date Start date
  • Views Views 2,571
  • Replies Replies 10
  • Likes Likes 1

Waifu4Life

Well-Known Member
Member
Joined
Mar 6, 2017
Messages
264
Reaction score
67
Trophies
0
Age
46
XP
1,839
Country
Canada
God I can't wait for the Switch 2 just so that Nintendo will easy-up on the Switch 1 firmware updates. So what am I doing wrong this time?:

20240724_202446.jpg
 
  • Like
Reactions: impeeza
That's the mission control folder... back it up, delete it from SD card and your Switch will boot. Go to hbstore to download mission control again.

EDIT : Mission control is used for connecting other peripherals that ninty blocked connections to.

EDIT EDIT : Mission Control folder acts just like custom themes folder at firmware updates, they need to be removed before updating firmware.
 
That's the mission control folder... back it up, delete it from SD card and your Switch will boot. Go to hbstore to download mission control again.

EDIT : Mission control is used for connecting other peripherals that ninty blocked connections to.

EDIT EDIT : Mission Control folder acts just like custom themes folder at firmware updates, they need to be removed before updating firmware.

I'm not able to get into my custom firmware, so the hbstore is out of the question. I copied the MissionControl folder from my previous setup into my MicroSD, but it didn't change anything, I get the same issue. I didn't think it would have fixed the problem because all there was in there was an empty "controllers" folder and a file called missioncontrol.ini.template.
 
I'm not able to get into my custom firmware, so the hbstore is out of the question. I copied the MissionControl folder from my previous setup into my MicroSD, but it didn't change anything, I get the same issue. I didn't think it would have fixed the problem because all there was in there was an empty "controllers" folder and a file called missioncontrol.ini.template.
You've been told how to fix it - basically remove your entire Atmosphere folder from your micro sd card and put a fresh clean version downloaded directly from the github page on your sd card, then you'll be able to boot. You can then install sigpatches or plugins after this.
 
You've been told how to fix it - basically remove your entire Atmosphere folder from your micro sd card and put a fresh clean version downloaded directly from the github page on your sd card, then you'll be able to boot. You can then install sigpatches or plugins after this.

Where exactly was the Atmosphere folder mentioned in this topic before your reply?
 
I said what I said, cuz I just went through this the other night after a firmware update. I deleted the mission control folder and viola Atmosphere boot.

EDIT : Or start fresh with everything on the SD card, as stated
 
Last edited by Deleted member 681324,
  • Love
Reactions: impeeza

While you may have deleted your post, it's actually what solved my issue. I did download the new Atmosphere and
hekate and added everything from my previous setup.... including the atmosphere/contents folder and this was the issue. Cheers!
 

Site & Scene News

Popular threads in this forum