Hacking Question Nintendo switch stuck on logo after update.

[Op07ita]

Hello Everyone,

I have a switch that can't go past the Nintendo switch logo, the person i got it from said he was doing an update but probably something went wrong (or he's lying).
I tried to unplug the battery but nothing changed. I can boot in rcm and use hekate.
I know it could be a wifi chip problem so before trying a reflow i wanted to know what i could try.
Thank you all for reading and help.

 

[Hayato213]

If he was doing an update and if he didn't finish updating he probably bricked the sysNAND.

 

[Op07ita]

Considering that i don't have a nand backup, am i screwed?

 

[Hayato213]

If you have no NAND backup then you can try the following methods, you need your bis keys, you can try that to rebuild the NAND with Choidujour or Emmchaccgen, the keys can be obtained from biskeydump or lockpick_RCM.

https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/
https://github.com/suchmememanyskill/EmmcHaccGen

 

[Op07ita]

The switch had 14 blown fuses so i tried with 11 and 12 fw but same result, It dosen't work.
It's probably an harware fault. I'll try a quick reflow.

 

[IZUNYA]

It is a sysnand hacked console ? Or a emunand ?

If it's a emunand hack, it can be a sysmodule problem.

 

[Op07ita]

I don't know i got it without an sd and i don't know the story, how can i verify if it was a emunand?

 

[IZUNYA]

If there is no SD its a sysnand hack then

 

[Hayato213]

If there is no SD its a sysnand hack then

You need SD to use CFW on sysnand or Emunand, base on how much fusee he burn probably it is Sysnand, but regardless in his situation, it is sysnand that is broken since it won't boot into OFW.

 

[IZUNYA]

You need SD to use CFW on sysnand or Emunand, base on how much fusee he burn probably it is Sysnand, but regardless in his situation, it is sysnand that is broken since it won't boot into OFW.

True, i forgot about that

 

[Draxzelex]

Hello Everyone,

I have a switch that can't go past the Nintendo switch logo, the person i got it from said he was doing an update but probably something went wrong (or he's lying).
I tried to unplug the battery but nothing changed. I can boot in rcm and use hekate.
I know it could be a wifi chip problem so before trying a reflow i wanted to know what i could try.
Thank you all for reading and help.

What happens when you try booting CFW and/or OFW?

 

[wargreymon89]

Sorry for hijacking the thread, figured it was better than creating a new exactly same. I have pretty much same story for a Switch, it was bought as "defect with battery connector broken, worked before that", person before me had managed to tear the connector from the main board and nothing else, I now think this is bull though. So I got it quite cheap, the console started and turned off after Nintendo logo when it was broke and I used a charger. I soldered the connector and battery worked. However it did the same thing. Nintendo Logo and then turns off.

I have now tried every possible guide to restore the FW 12.0.2 (Boot0/Boot1/System etc from above guides and also Such Meme, Many Skill's unbricking guide that uses systemRestore.te script to flash from TegraExplorer) that was on the console (I checked it against a downloaded that had exactly same files so all seems well. Tried a 6.0.1 Firmware also.

The console has 15 burnt fuses, doesn't matter to me, I just want to get it to work with either stock FW or CFW.

What works:
* RCM
* Sending Payloads
* Flashing partitions
* Hekate

What doesn't work:
* Booting normally it shows Nintendo Logo and turns off
* Booting it into Recovery with +/- when booting normally due to it turning off
* Booting through Hekate and Stock it shows Hekate logo and turns off
* Booting Atmosphere through Hekate or sending fusee-primary payload shows Atmosphere logo (3 screens of logos) and then turns off

Are there any more payloads for testing hardware or so? Everything I have seen in Hekate looks fine as far as I can tell, I have no issues with biskeys or dumping/flashing anything.

What happens when you try booting CFW and/or OFW?

 

[Draxzelex]

Sorry for hijacking the thread, figured it was better than creating a new exactly same. I have pretty much same story for a Switch, it was bought as "defect with battery connector broken, worked before that", person before me had managed to tear the connector from the main board and nothing else, I now think this is bull though. So I got it quite cheap, the console started and turned off after Nintendo logo when it was broke and I used a charger. I soldered the connector and battery worked. However it did the same thing. Nintendo Logo and then turns off.

I have now tried every possible guide to restore the FW 12.0.2 (Boot0/Boot1/System etc from above guides and also Such Meme, Many Skill's unbricking guide that uses systemRestore.te script to flash from TegraExplorer) that was on the console (I checked it against a downloaded that had exactly same files so all seems well. Tried a 6.0.1 Firmware also.

The console has 15 burnt fuses, doesn't matter to me, I just want to get it to work with either stock FW or CFW.

What works:
* RCM
* Sending Payloads
* Flashing partitions
* Hekate

What doesn't work:
* Booting normally it shows Nintendo Logo and turns off
* Booting it into Recovery with +/- when booting normally due to it turning off
* Booting through Hekate and Stock it shows Hekate logo and turns off
* Booting Atmosphere through Hekate or sending fusee-primary payload shows Atmosphere logo (3 screens of logos) and then turns off

Are there any more payloads for testing hardware or so? Everything I have seen in Hekate looks fine as far as I can tell, I have no issues with biskeys or dumping/flashing anything.

Have you tried GPTrestore?

 

[wargreymon89]

Have you tried GPTrestore?

Yes. I have tried that also Assume there is no newer than the one on switchtools?

 

[Draxzelex]

Yes. I have tried that also Assume there is no newer than the one on switchtools?

There is also eMMCHacGen that you can try.

 

[wargreymon89]

HacDiskMount

There is also eMMCHacGen that you can try.

I used that when generating the files for 12.0.2 that I flashed, since Choidujour can't do firmware above 6.something(?).

I have no problem flashing the files or so. I have used the guide posted by Hayato213.

Only thing I haven't found to try restore is BCPKG2-5-Repair-Main and BCPKG2-6-Repair-Sub. The partitions are there when using HacDiskMount, but no idea if they are corrupt or not.

 

[Draxzelex]

HacDiskMount
I used that when generating the files for 12.0.2 that I flashed, since Choidujour can't do firmware above 6.something(?).

I have no problem flashing the files or so. I have used the guide posted by Hayato213.

Only thing I haven't found to try restore is BCPKG2-5-Repair-Main and BCPKG2-6-Repair-Sub. The partitions are there when using HacDiskMount, but no idea if they are corrupt or not.

Well it might be worth a shot then.

 

[anthony_harvey1]

HacDiskMount
I used that when generating the files for 12.0.2 that I flashed, since Choidujour can't do firmware above 6.something(?).

I have no problem flashing the files or so. I have used the guide posted by Hayato213.

Only thing I haven't found to try restore is BCPKG2-5-Repair-Main and BCPKG2-6-Repair-Sub. The partitions are there when using HacDiskMount, but no idea if they are corrupt or not.

Sorry for reviving an old thread but did you manage to sort your issue? I am facing exactly the same

 

[Draxzelex]

Sorry for reviving an old thread but did you manage to sort your issue? I am facing exactly the same

Try restoring the 2 things that user mentioned in his post.