Hacking Bricked Switch

[Calyptor]

https://github.com/StarDustCFW/ChoiDujour
this is a modified version which is what I used, this allowed me to create 8.0.1 and 8.1.0 successfully. RetroGamer74 released a vid which someone on here linked me too. I’ve used his PS4 payloads before and we’re decent. His vid on it looks successful. Mine unfortunately as mentioned black screen after Nintendo logo. I believe again, this is system partition related and hopefully should be an easy fix. Try creating your 6.x firmware Witt this. Make sure the firmware is signed. It will tell you. And ensure you have your bis keys in HacDiskMount partitions. Restore the newly created partitions from the modified chor version above to your switch. - BUT before doing that. If you have the Nintendo logo already. And you’re already on 6.x. Then create firmware as mentioned above and just replace system partition with the files / folders from there. Then try again

Awesome a glimmer of hope appears.... this might be a little far fetched but could it also maybe have to do with exfat/fat32...
Let me explain perhaps our issue stems from the fact that the flashed nand back up used fat32 (least I know this was my case) while the files generated by choi use exfat (though this can be changed by adding --noexfat to the command line).

So when the system boots it looks for exfat in the nand while the nand is fat32?.... I don't know...

 

[jellybeangreen2]

Awesome a glimmer of hope appears.... this might be a little far fetched but could it also maybe have to do with exfat/fat32...
Let me explain perhaps our issue stems from the fact that the flashed nand back up used fat32 (least I know this was my case) while the files generated by choi use exfat (though this can be changed by adding --noexfat to the command line).

So when the system boots it looks for exfat in the nand while the nand is fat32?.... I don't know...

This is also a possibility. Something I will be trying if clearing the system partition doesn’t work.

give it a try and let me know the outcome before I try if you can

 

[Calyptor]

This is also a possibility. Something I will be trying if clearing the system partition doesn’t work.

give it a try and let me know the outcome before I try if you can

I'm in town getting drunk so you'll probably do it before me but I won't fail to keep you updated here

 

[Calyptor]

hmmmm im getting some py errors when i try using the script... probably need an update somewhere I have to head out now but ill dig deeper when im back...


Using source firmware files from folder fw
Traceback (most recent call last):
File "ChoiDujour.py", line 529, in <module>
File "ChoiDujour.py", line 237, in call_hactool
Exception: Error: section 0 is corrupted!

[12564] Failed to execute script ChoiDujour

 

[jellybeangreen2]

hmmmm im getting some py errors when i try using the script... probably need an update somewhere I have to head out now but ill dig deeper when im back...


Using source firmware files from folder fw
Traceback (most recent call last):
File "ChoiDujour.py", line 529, in <module>
File "ChoiDujour.py", line 237, in call_hactool
Exception: Error: section 0 is corrupted!

[12564] Failed to execute script ChoiDujour

You gave to install python3 and if you’re trying to do —noexfat I did that last night and it won’t create the firmware cause it can’t locate the linked hash to the firmware.

if anyone sees this post and can provide some advice. I have updated the original post with what I have done / current situation. Any advice would be appreciated.

 

[Calyptor]

no luck on your end huh? for some reason the keys.txt file is not working with the new version of choi. getting section 0 is corrupted error and from what iv have gathered this is due to soemthing being wrong with the keys file...

 

[jellybeangreen2]

no luck on your end huh? for some reason the keys.txt file is not working with the new version of choi. getting section 0 is corrupted error and from what iv have gathered this is due to soemthing being wrong with the keys file...

What command are you typing?

 

[Calyptor]

What command are you typing?

--keyset=keys.txt (the file is in the same folder and i also tried specifying the location) fw (here too i tried with the entire path to the firmware file written out...)

 

[jellybeangreen2]

Just to let everyone know, this wasn't fixed. - 8.1.0 boots to the Nintendo screen without any autoRCM/payload etc. However black screen after this. When looking in to this further, it seems to be you get the black screen if you have PRODINFO partition errors. funny enough, when I entered BIS KEY 0. The key would fail to validate. I even restored the PRODINFO partition no joy. I spent around 17 hours on it. Research, testing, fixing other issues, testing via backup etc. No joy. My friend was grateful for the attempt at least and has learnt to not just restore via backup (I hope). Backups don't always solve the problem!

 

[thesjaakspoiler]

Are you sure that your friend didn't accidently grab the latest 9.0.1 firmware?
If you try to run 8.1 it will freak out because of the number of burned fuses is too high.

 

[Ericthegreat]

Keep us updated when you get it working so people in the future know what worked, but yea your switch should be savable.

 

[Calyptor]

When I try to use lockpicker I get kglob 1 2 and 3 error (or whatever it's called) corruption error. Not sure if you too and if it might help you narrow down the problem.... mine is still under warranty so I'm going to try to pull a switch-(ha)-eroo..... hoping super Mario doesn't show up at my door and fist jumps my ass...

 

[jellybeangreen2]

Are you sure that your friend didn't accidently grab the latest 9.0.1 firmware?
If you try to run 8.1 it will freak out because of the number of burned fuses is too high.

Definitely sure. Fuse count is 10. Meaning he installed 8.1.0. I manually obtained this and installed it. The hash of the file matched what is known for 8.1.0