Hacking Question Atmosphere won't finish booting after Switch logo

pakoito

Well-Known Member
OP
Member
Joined
Nov 16, 2006
Messages
110
Trophies
0
XP
258
Country
I have followed all the steps outlined in https://rentry.co/SwitchHackingIsEasy to put Hekate and Atmosphere. I have used the latest versions and I believe my folder structure is correct.

After bootking hekate and trying to load Atmosphere I get the sequence seen in this video. After the Atmos logos it takes literal minutes to get to the Nintendo Switch screen, from which the CFW never finishes to boot and eventually goes on a blank screen.

This is a newly formatted Mini SD card, although it's on the oldish side, circa 2012.

What could I do to debug this behavior, and maybe apply a fix? I have tried the obvious ones of repeating the process, and SysNand boots just okay.
 

petspeed

Well-Known Member
Member
Joined
Nov 13, 2009
Messages
830
Trophies
0
Age
47
XP
725
Country
Denmark
How fast is the SD card and is it of good quality? Since it takes minutes for the Nintendo screen to appear it could be problems reading the SD card.
 

Tom77_no

Member
Newcomer
Joined
Jun 5, 2017
Messages
15
Trophies
0
Age
44
XP
225
Country
Norway
I have followed all the steps outlined in https://rentry.co/SwitchHackingIsEasy to put Hekate and Atmosphere. I have used the latest versions and I believe my folder structure is correct.

After bootking hekate and trying to load Atmosphere I get the sequence seen in this video. After the Atmos logos it takes literal minutes to get to the Nintendo Switch screen, from which the CFW never finishes to boot and eventually goes on a blank screen.

This is a newly formatted Mini SD card, although it's on the oldish side, circa 2012.

What could I do to debug this behavior, and maybe apply a fix? I have tried the obvious ones of repeating the process, and SysNand boots just okay.

Had the same problem a while ago. Until I deleted the file exosphere.ini. Booted fine without this file.
 

pakoito

Well-Known Member
OP
Member
Joined
Nov 16, 2006
Messages
110
Trophies
0
XP
258
Country
Had the same problem a while ago. Until I deleted the file exosphere.ini. Booted fine without this file.
I just tried and it didn't work :(

Someone on reddit suggested using the Atmos that first introduced my firmware, because it still is from 2018/9
 
General chit-chat
Help Users
  • No one is chatting at the moment.
    KennieDaMeanie @ KennieDaMeanie: Let gravity be the parent