Hacking Switch Suddenly Won't Boot Past Logo When Attempting to Launch CFW

[finalriches]

Hello.

I have a Switch running the latest version of Atmosphere, and earlier today I removed my SD card to add some files to it from my PC (which I've done many times before) and now for some reason every time I inject Hekate 5.0.1 and then attempt to launch CFW (SYSNAND) I seem to get stuck at the Nintendo Switch logo screen every time. I'm still able to boot into Lakka just fine, so I'm not really sure what the issue is.

If anyone can help me out, or link me to something that can I'd really appreciate it.

 

[Budsixz]

Hello.

I have a Switch running the latest version of Atmosphere, and earlier today I removed my SD card to add some files to it from my PC (which I've done many times before) and now for some reason every time I inject Hekate 5.0.1 and then attempt to launch CFW (SYSNAND) I seem to get stuck at the Nintendo Switch logo screen every time. I'm still able to boot into Lakka just fine, so I'm not really sure what the issue is.

If anyone can help me out, or link me to something that can I'd really appreciate it.

some files could have been broken. Try to remove the new files that you put. You can try reformatting card to fat32 with 32kb cluster size
Try to use the Kosmos Package

 

[NoNAND]

Some files might have gotten lost or altered. Consider doing a backup beforehand, then formatting your SD card with guiformat ( fat32+32kb cluster size)
re-download your CFW package of choose be it the Kosmos , Standalone Atmosphere ( ensure to download its respective fuse_primary payload), or ReiNX

have you tried booting your switch in OFW?

 

[finalriches]

Some files might have gotten lost or altered. Consider doing a backup beforehand, then formatting your SD card with guiformat ( fat32+32kb cluster size)
re-download your CFW package of choose be it the Kosmos , Standalone Atmosphere ( ensure to download its respective fuse_primary payload), or ReiNX

have you tried booting your switch in OFW?

Thanks for the suggestions. After reformatting my sd card and copying everything back over I was finally able to get it to boot up after a few tries. Then I randomly ended up having Atmosphere crash while running a emulator and now I just keep getting stuck at the logo again. I tried booting into stock system nand and ended up getting the same result. Not really sure what the issue is.

 

[Kafluke]

Is your SD card fake? You could have reached the end of the actual partition and started overwriting data.

 

[JT_Maston]

Thanks for the suggestions. After reformatting my sd card and copying everything back over I was finally able to get it to boot up after a few tries. Then I randomly ended up having Atmosphere crash while running a emulator and now I just keep getting stuck at the logo again. I tried booting into stock system nand and ended up getting the same result. Not really sure what the issue is.

Have you tried booting into stock nand without your sd card? Have you been using a 3rd party dock? It might be a greater issue than just cfw. Do you have a nand backup?

 

[finalriches]

Is your SD card fake? You could have reached the end of the actual partition and started overwriting data.

I really doubt that is the case since it came from a trusted source & I've kept my card near full capacity for a while without issue, plus I even tried loading a fresh copy of atmosphere from a different SD card. I really appreciate the idea though, cause it is something I haven't considered or ruled out. I will probably try to run a few tests on it just to make sure.

Have you tried booting into stock nand without your sd card? Have you been using a 3rd party dock? It might be a greater issue than just cfw. Do you have a nand backup?

Appreciate the response. I'm not sure how to boot into stock nand without a SD card, but i'd be willing to try. I did attempt to boot a fresh copy of atmosphere on a different sd card and got the same results. I've never used a 3rd party dock, and rarely use the official one much.

Hopefully it's nothing too serious, I mean I can navigate Hekate just fine, and even play games by booting to Lakka. I do have a nand back up as well, I made one earlier today through Hekate, and still have a old one that I believe I made prior to installing CFW.

 

[Pinkton]

What emulator is it you're running? While I doubt it might be causing issues, it's odd how it always seems to be homebrew that causes issues with memcards?

*EDIT*
It could be causing data errors on something to do with atmo' and the hid issue that SciresM has mentioned. Have you had issues previous to 094?

 

[JT_Maston]

I really doubt that is the case since it came from a trusted source & I've kept my card near full capacity for a while without issue, plus I even tried loading a fresh copy of atmosphere from a different SD card. I really appreciate the idea though, cause it is something I haven't considered or ruled out. I will probably try to run a few tests on it just to make sure.





Appreciate the response. I'm not sure how to boot into stock nand without a SD card, but i'd be willing to try. I did attempt to boot a fresh copy of atmosphere on a different sd card and got the same results. I've never used a 3rd party dock, and rarely use the official one much.

Hopefully it's nothing too serious, I mean I can navigate Hekate just fine, and even play games by booting to Lakka. I do have a nand back up as well, I made one earlier today through Hekate, and still have a old one that I believe I made prior to installing CFW.

To boot into stock nand, disable AutoRCM (if you're running it), remove the SD card and press the power button. The Nintendo logo should show up, followed by the switch one.

 

[KnightRiderX420]

Hello.

I have a Switch running the latest version of Atmosphere, and earlier today I removed my SD card to add some files to it from my PC (which I've done many times before) and now for some reason every time I inject Hekate 5.0.1 and then attempt to launch CFW (SYSNAND) I seem to get stuck at the Nintendo Switch logo screen every time. I'm still able to boot into Lakka just fine, so I'm not really sure what the issue is.

If anyone can help me out, or link me to something that can I'd really appreciate it.

I went threw this a few times at first with this atmos version. the way i fixed it was removing the old atmos files i.e. all folders and files that match the ones in the new atmos archive. then extracting the latest atmos as there right now are 2 versions of 9.4 see post about release to verify. grab latest build. check top of github page to see age. and extract it onto your sd card. and grab the latest espatches as they have to be reaplied cause they will be gone. make sure you have all of them not just the 9.0 stuff. and you should be fine. also if using kosmos. it got another update quick to 14.01 i would actualy put that on first then atmos 9.4 build 7****** on top of that copying over all then add the correct espatches. and if you really wanna get crazy hbgshop 4.1....


after tinkering with my unit for quite a while this is the answwer i came up with for me and now with the new hbg launcher v2 the buttons work as well. so all i need now is a new goldleaf and a new retroarch nsp as i prefer to just launch them right from the emunand menue.

 

[finalriches]

I went threw this a few times at first with this atmos version. the way i fixed it was removing the old atmos files i.e. all folders and files that match the ones in the new atmos archive. then extracting the latest atmos as there right now are 2 versions of 9.4 see post about release to verify. grab latest build. check top of github page to see age. and extract it onto your sd card. and grab the latest espatches as they have to be reaplied cause they will be gone. make sure you have all of them not just the 9.0 stuff. and you should be fine. also if using kosmos. it got another update quick to 14.01 i would actualy put that on first then atmos 9.4 build 7****** on top of that copying over all then add the correct espatches. and if you really wanna get crazy hbgshop 4.1....


after tinkering with my unit for quite a while this is the answwer i came up with for me and now with the new hbg launcher v2 the buttons work as well. so all i need now is a new goldleaf and a new retroarch nsp as i prefer to just launch them right from the emunand menue.

I really appreciate this advice, but I guess I should've mentioned that when i made this topic i was on Atmosphere 0.93, I attempted to try and update anyway though and didn't have much luck. It's weird, but I randomly had my switch boot up normally, but then after shutting it down I can't seem to boot past the Logo again.

 

[MrJackie]

Hey did you find a fix? I have the same problem Although mine happened after i was playing FE3H. I put the Switch into sleep mode cause it was docked and got a error atmosphere message error code 2001-0114.
I can boot up into hekate fine but OFW and CFW is stuck on the logo.
I was using Kosmos 14.1
Firmware 9.0.0
Atmosphere 0.9.4. I tried to boot into maintenance mode but it wont Even do that still stuck on the logo.

 

[finalriches]

Hey did you find a fix? I have the same problem Although mine happened after i was playing FE3H. I put the Switch into sleep mode cause it was docked and got a error atmosphere message error code 2001-0114.
I can boot up into hekate fine but OFW and CFW is stuck on the logo.
I was using Kosmos 14.1
Firmware 9.0.0
Atmosphere 0.9.4. I tried to boot into maintenance mode but it wont Even do that still stuck on the logo.

Unfortunately I never found a fix! I tried asking for help on discord, and a couple reddits, but didn't get any suggestions that worked. It's funny you say that you were using the dock though, cause I do seem to recall using the dock and atmosphere crashing with what I believe was the same error right before getting this issue.

One thing you might could try is restoring your NAND. I was going to but sadly my only backup has a different firmware on it, so I don't believe i'm able to. If you end up finding out any solutions please let me know.

 

[MrJackie]

Unfortunately I never found a fix! I tried asking for help on discord, and a couple reddits, but didn't get any suggestions that worked. It's funny you say that you were using the dock though, cause I do seem to recall using the dock and atmosphere crashing with what I believe was the same error right before getting this issue.

One thing you might could try is restoring your NAND. I was going to but sadly my only backup has a different firmware on it, so I don't believe i'm able to. If you end up finding out any solutions please let me know.

Hmmm I'll come back to you currently im going through different methods i know it aint dead since i can still boot into hekate just fine. But just FYI i did do a NAND restore, somehow worked for a little bit then crashed again same error same method (sleep mode dock on switch, Official dock btw)

 

[finalriches]

Hmmm I'll come back to you currently im going through different methods i know it aint dead since i can still boot into hekate just fine. But just FYI i did do a NAND restore, somehow worked for a little bit then crashed again same error same method (sleep mode dock on switch, Official dock btw)

That would be great. Yeah, I'm able go into hekate as well as play games in Lakka just fine, and was actually randomly able to just get things working past the NS logo a couple times before having the issue again. I was using the official dock & power supply as well.

 

[Boomerams]

Incompatible custom theme..hint hint

 

[MrJackie]

Incompatible custom theme..hint hint

No custom themes on my end thats for sure

 

[Boomerams]

No custom themes on my end thats for sure

Try removing atmosphere titles folder

 

[Deleted User]

having too much sysmodules enabled makes you hang on boot
although im not sure if thats the problem, try disabling some of them

 

[finalriches]

Try removing atmosphere titles folder

I've never ran any custom themes either. I believe I've tried deleting the titles folder, but I will look into it again.

having too much sysmodules enabled makes you hang on boot
although im not sure if thats the problem, try disabling some of them

This is something I haven't tried, or messed with before. How do you go about disabling some of them?


I appreciate the responses as well