Nintendo Switch Oled Stuck at Nintendo Logo

[naldo29]

Heres what happenend. After successfully modding my console and closing it up. I then went ahead and procceded with an emunand after that finished i entered the emunand and when into DBI the console turned off and when i booted it up again wouldnt boot into either OFW SYSNAND OR EMUNAND, always getting stuck on the nintendo/atmosphere logo. Ive tried everything in restoring the nand, following sthetix guide (lvl 1 and 2) and the same issue still persists.

The issue here is, the nintendo logo issue usually is a system partition issue, but i dont think thats the case here. Both emunand and sysnand got nuked at the same time, neither works which leads me to believe that it has somthing to do with hardware but i dont recall doing anything wrong in the instalation, and i can load into hakete just fine. Everything looks solid and just incase i redid the instalation and still got the same issue. Sometimes when entering atmoshpere, it would give me an error mesage such as this. But these ocasions were rare.

I need guidance on what I should try next, any help would be greatly appriciated, thank you!

 

[Hayato213]

Look up the program ID, since you post three different fata error.

 

[naldo29]

Look up the program ID, since you post three different fata error.

They all happened in the exact same scenario, why would the error code be different everytime? shouldnt it be the same?

 

[Hayato213]

They all happened in the exact same scenario, why would the error code be different everytime? shouldnt it be the same?

Can you post clearer picture, those aren't one that are stuck on Nintendo switch logo, you got crashes.

 

[naldo29]

0100000000000001
0100000000000005
0100415444530000

 

[Hayato213]

You on exFAT or FAT32?

 

[realtimesave]

looks like you either need to update some homebrew apps or delete them..

 

[naldo29]

You on exFAT or FAT32?

FAT32

Post automatically merged: Apr 29, 2024

looks like you either need to update some homebrew apps or delete them..

Why wouldnt it work on OFW or when i remove the entire chip then?

 

[Hayato213]

Since you messed with your NAND does your OFW still boot?

 

[naldo29]

Since you messed with your NAND does your OFW still boot?

Same issue, gets stuck on the nintendo logo

 

[Hayato213]

Same issue, gets stuck on the nintendo logo

Well you bigger problem here is that your OFW/Sysnand CFW NAND doesn't work, as they share the same NAND, you got any NAND backup prior to doing any of the level 1 and 2 restore?

 

[naldo29]

Well you bigger problem here is that your OFW/Sysnand CFW NAND doesn't work, as they share the same NAND, you got any NAND backup prior to doing any of the level 1 and 2 restore?

yes, i do. Should i try to restore back to the backup that i did before trying to restore?

 

[Hayato213]

yes, i do. Should i try to restore back to the backup that i did before trying to restore?

If you got a working NAND backup restore that, you need the boot0/boot1 and the rawnand.bin

 

[naldo29]

If you got a working NAND backup restore that, you need the boot0/boot1 and the rawnand.bin

No the nand backup isnt of a functioning back. its from right before doing the system restore and doing lvl 1 and lvl 2, just incase i messed up the system restore i could go back to square 1.

Basicvally restoring the backup would do nothing since the console is still having the exact same problem after the nand restore

 

[Hayato213]

No the nand backup isnt of a functioning back. its from right before doing the system restore and doing lvl 1 and lvl 2, just incase i messed up the system restore i could go back to square 1.

Basicvally restoring the backup would do nothing since the console is still having the exact same problem after the nand restore

Having the boot0/boot1 and the rawnand it is different from the level 1 / 2 restore. Anyway I wanted to know if you had a backup of the NAND when it was working fine.

 

[naldo29]

Having the boot0/boot1 and the rawnand it is different from the level 1 / 2 restore. Anyway I wanted to know if you had a backup of the NAND when it was working fine.

lol, i wish i had a blackup. but no, unfortunately i do not have a backup on when it was working fine. the only weird thing is, if they were fine at first. i didnt install anything or did anythnig apart from the normal. I didnt install any app or nothing. It was as soon as i finished the emunand where i just entered DBI and boom just bricked.

 

[Hayato213]

lol, i wish i had a blackup. but no, unfortunately i do not have a backup on when it was working fine. the only weird thing is, if they were fine at first. i didnt install anything or did anythnig apart from the normal. I didnt install any app or nothing. It was as soon as i finished the emunand where i just entered DBI and boom just bricked.

Well you doing the level 1 and 2 restore probably bricked it, those fatal errors are just crashes that can be fixed.

 

[cgtchy0412]

You can try to remove/redo the clk point. First remove it and test again.. if still persisst then remove dat0 point also.

 

[naldo29]

You can try to remove/redo the clk point. First remove it and test again.. if still persisst then remove dat0 point also.

removed everything and the same issue persists sadly

 

[naldo29]

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