Nintendo Switch Oled Stuck at Nintendo Logo

[Hayato213]

I restoed the backup to get the fatal error messages. Now its just 0100000000000001. What should i do to fix this error?

Delete your cfw file and put new one see if it fix it.

 

[naldo29]

Delete your cfw file and put new one see if it fix it.

brand new cfw and same issue unfortunately

 

[Hayato213]

brand new cfw and same issue unfortunately

You using stock Atmosphere or a premade pack ?

 

[naldo29]

You using stock Atmosphere or a premade pack ?

premade pack. but i also tried just using stock atmoshpere and it didnt work either

 

[Reecey]

premade pack. but i also tried just using stock atmoshpere and it didnt work either

Get your sd card and reformat it too Fat32 then put a fresh 1.6.2 Atmosphere (https://github.com/Atmosphere-NX/Atmosphere/releaseson) leave off Hekate "its shit" only use the Atmosphere payload you dont need setting up emunand it wont stop a ban or help you in anyway. If you are on the latest firmware 18.0.1 then it will have to be version 1.7.0 this time "delete the contents folder from the atmosphere folder" and start your switch let me know what you get. I assume you are using somesort of dongle to access rcm? so if it is like me you are using an sxos Pro or sxos Gear you will need to change the atmosphere fusee.bin too payload.bin on your sd card, if you are using some sub-standard cheap dongle too access rcm then I dont know how you set it up

 

[naldo29]

Get your sd card and reformat it too Fat32 then put a fresh 1.6.2 Atmosphere (https://github.com/Atmosphere-NX/Atmosphere/releaseson) leave off Hekate use the Atmosphere payload you dont need setting up emunand it wont stop a ban or help you in anyway. If you are on the laetst firmware 18.0.1 then it will have to be version 1.7.0 this time "delete the contents folder from the atmosphere folder" and start your switch. I assume you are using somesort of dongle to access rcm? so if it is like me you are using an sxos Pro or and sxos Gear you will need to change the atmosphere fusee.bin too payload.bin on your sd card, if you are using some sub-standard cheap dongle too access rcm then I dont know how you set it up

Im using a modchip that i installed myself. Ive already tried doing a fresh install which resulted the same issue. Ive even talked to the creator of atmosphere about my issue. My issue isnt anything with software. Its something on the hardware thats not letting me boot further the nintendo logo.

 

[Reecey]

Im using a modchip that i installed myself. Ive already tried doing a fresh install which resulted the same issue. Ive even talked to the creator of atmosphere about my issue. My issue isnt anything with software. Its something on the hardware thats not letting me boot further the nintendo logo.

Are you sure because error code 0100000000000001 is related too the contents folder within the atmosphere folder I've come across it myself over the years. If that is what you are seeing when booting up its not your modchip installation. Also if you are seeing any sort of atmosphere error code pop up starting your switch I doubt its modchip related

Edit: also make 100% sure your firmware works with the correct atmosphere version so if you are on 17.0.0 for example use version 1.6.2 etc.. and "dump Hekate" I havent used it for years, it causes nothing but issues especially for exfat users

 

[naldo29]

Are you sure because error code 0100000000000001 is related too the contents folder within the atmosphere folder I've come across it myself over the years. If that is what you are seeing when booting up its not your modchip installation. Also if you are seeing any sort of atmosphere error code pop up starting your switch I doubt its modchip related

Thats the issue. Sometimes the problem happens. Sometimes not. The atmosphere crash isnt reproducible everytime i boot it and sometimes it even gives out different errors.


Basically when i boot my console, it leads to a bunch of different results.
1. Nothing happens
2. Nintendo logo only and then black
3. Nintendo logo only and then atmosphere crash (error id changes sometimes)
4. It got as far as the joycon logo
5. It got past the joycon logo but then black (only happened to me once tho)

This “randomness” just lead me to believe that this issue is of something going on in the hardware. Something loose or damaged thats trying to make a connection but gives up in the end.