Hacking Bricked Switch

[jellybeangreen2]

Well, here goes. (Not my Switch, a friends)

little story. Was on 5.1.0 (backup from 4.1 I believe). He offline updated to 8.1.0 burning his efuse since it is banned, but forgot to update his SXOS boot.dat. He thought it was then bricked. Restored his nand and bam. Then he made some gpp / gpt changes. And as a result black screen.
I have a backup of all partitions and rawnand. I have restored this. Still no success. (Again the backup is either version 4.1.0 / 5.1.0)

I have also followed a guide to manually recreate the partitions, obtain the keys, flash boot0/1 etc. Manually create the firmware (I did do 5.1.0 not 8.1.0) using the desktop version of Choi.

Does anyone have any advice / help the best way for me to resolve this please?



UPDATE: Full explanation of what’s happened so far. Console bricked after manual update from 5.1.0 to 8.1.0 (fuse count 10). User thought console was bricked after trying to load SXOS but forgot to update boot.dat. Restored old nand backup. Black screen completely. GPT reset still black screen.

then I got ahold of it. I have done a manual firmware install following these steps:https://switch.homebrew.guide/usingcfw/manualchoiupgrade

I now have firmware 8.1.0 installed, I now have a Nintendo boot logo. After this I get a black screen.

So now I have a Nintendo logo the firmware is at least on the switch and it is now trying to load up through the Nintendo bootloader. CFW, also boots to black screen. SXOS/Renix/ Atmosphere. Firmware is in exfat mode with an exfat sd. I tried using a fat/32 sd and the switch will not detect it at all. Nor can I create —noexfat firmware using the above link via pc.

Has anyone got any ideas in regards to the black screen after Nintendo logo please?

 

[edwardsalazar97]

.

 

[Hayato213]

You can try to go to 4.1 or 6.2, if 5.1 firmware option with Choidujour doesn't work.

 

[edwardsalazar97]

I think there is nothing to do if you have burned efuses

 

[Basketto]

You would need the ability to update firmware via payload, and idk if it is the works but atm pretty sure the switch is staying bricked.

 

[edwardsalazar97]

@jellybeangreen2 you're in luck just a method with a modified choi for superior firmwares

 

[OrGoN3]

Well, here goes. (Not my Switch, a friends)

little story. Was on 5.1.0 (backup from 4.1 I believe). He offline updated to 8.1.0 burning his efuse since it is banned, but forgot to update his SXOS boot.dat. He thought it was then bricked. Restored his nand and bam. Then he made some gpp / gpt changes. And as a result black screen.
I have a backup of all partitions and rawnand. I have restored this. Still no success. (Again the backup is either version 4.1.0 / 5.1.0)

I have also followed a guide to manually recreate the partitions, obtain the keys, flash boot0/1 etc. Manually create the firmware (I did do 5.1.0 not 8.1.0) using the desktop version of Choi.

Does anyone have any advice / help the best way for me to resolve this please?

Bricked? Doubtful. Does it enter RCM mode? Can you inject a payload? Why not inject Hekate and restore your nand backup? Then boot AMS with hekate and do what you need to do in Choi. Booting with Hekate will make the console not care about the efuses. AMS is best for homebrew and Choi works just fine in there. SX OS has issues with homebrew.

 

[jellybeangreen2]

@jellybeangreen2 you're in luck just a method with a modified choi for superior firmwares

can you please provide more information?

--------------------- MERGED ---------------------------

Bricked? Doubtful. Does it enter RCM mode? Can you inject a payload? Why not inject Hekate and restore your nand backup? Then boot AMS with hekate and do what you need to do in Choi. Booting with Hekate will make the console not care about the efuses. AMS is best for homebrew and Choi works just fine in there. SX OS has issues with homebrew.

It does boot in to RCM. I restored the backup and it boots to a black / blue ish screen.

 

[OrGoN3]

can you please provide more information?

--------------------- MERGED ---------------------------



It does boot in to RCM. I restored the backup and it boots to a black / blue ish screen.

Make sure your sd card isn't corrupt, and then put on a fresh clean install of atmosphere and try again.

 

[jellybeangreen2]

Thanks for the advice guys. So, I now have a Nintendo screen which I didn’t before. FW is 8.0.1 / 8.1.0 I have tried both, after the Nintendo boot screen after 3-5 secs I get a black screen. Atmosphere boots to a black screen also.

 

[Calyptor]

Im in the exact same boat I think...does your screen flash the atmosphereo logo when you hold the power button for 15 seconds after trying to boot atmospphere?

 

[chippy]

Booting fuse primary or through Hekate?
Try in Hekate to boot payload and select fuse primary and see if that works

 

[Calyptor]

Booting fuse primary or through Hekate?
Try in Hekate to boot payload and select fuse primary and see if that works

In my particular case either payloads don't work. But I don't want to thread jack Ops thread... would be nice if I got a reply on mine... I'll be following this one closely though as I think it's the closest one to my situation...

Good luck OP!

 

[jellybeangreen2]

Im in the exact same boat I think...does your screen flash the atmosphereo logo when you hold the power button for 15 seconds after trying to boot atmospphere?

The switch I’m working on used to do that. It uses SXOS. However, first time booting atmosphere it did do that (using older tools for firmware 5.1.0) fuse count was 10. I have now re-done it using newer tools for firmware 8.1.0. And it now boots the Nintendo logo. (Stock boot loader) after that black screens. Now I am at this part I think I know what the problem is, I will have to check tonight and will reply back.

--------------------- MERGED ---------------------------

Im in the exact same boat I think...does your screen flash the atmosphereo logo when you hold the power button for 15 seconds after trying to boot atmospphere?

Is yours bricked too I presume?

 

[Calyptor]

The switch I’m working on used to do that. It uses SXOS. However, first time booting atmosphere it did do that (using older tools for firmware 5.1.0) fuse count was 10. I have now re-done it using newer tools for firmware 8.1.0. And it now boots the Nintendo logo. (Stock boot loader) after that black screens. Now I am at this part I think I know what the problem is, I will have to check tonight and will reply back.

--------------------- MERGED ---------------------------


Is yours bricked too I presume?

Kinda.... it boots into RCM no prob but at first I could not even get the Nintendo logo to appear but now after manually updating to 6.2 I can see it, followed by black/grey screen. As mentioned AMS flashes once then same thing black/grey screen. If I hold the power button to "hard turn it off" the logo will flash a couple times more then finally turn off. I started having issues after I tried downgrading with choi. You're buddy might have done the same and I'm also guessing my stock nand (4.0.1) was useless... my fuse count went from 3 to 8 so I'm for sure on 6.2 now...

 

[jellybeangreen2]

Kinda.... it boots into RCM no prob but at first I could not even get the Nintendo logo to appear but now after manually updating to 6.2 I can see it, followed by black/grey screen. As mentioned AMS flashes once then same thing black/grey screen. If I hold the power button to "hard turn it off" the logo will flash a couple times more then finally turn off. I started having issues after I tried downgrading with choi. You're buddy might have done the same and I'm also guessing my stock nand (4.0.1) was useless... my fuse count went from 3 to 8 so I'm for sure on 6.2 now...

That’s exactly what he did. He forgot to update his SXOS boot.dat and thought cause he updated from 5.1.0 to 8.x it was bricked. Then he restored his 5.x nand backup. Reset the gpt partitions etc. From what I read. If you have the same problem I am having. You have to fully delete everything within the SYSTEM partition. Then copy only the folders / files from the firmware you manually created to that partition. Ensure your BIS keys are entered correctly. Do a test and save. Then just power the system on and let it go through the default Nintendo boot loader. (Presuming you are on the same firmware number as your fuse count). This is what I will do tonight.

 

[Calyptor]

That’s exactly what he did. He forgot to update his SXOS boot.dat and thought cause he updated from 5.1.0 to 8.x it was bricked. Then he restored his 5.x nand backup. Reset the gpt partitions etc. From what I read. If you have the same problem I am having. You have to fully delete everything within the SYSTEM partition. Then copy only the folders / files from the firmware you manually created to that partition. Ensure your BIS keys are entered correctly. Do a test and save. Then just power the system on and let it go through the default Nintendo boot loader. (Presuming you are on the same firmware number as your fuse count). This is what I will do tonight.

Thank you for the replies on your own thread man, I really appreciate it.....sadly i tried this with both the 4.0.1 files generated by choidujour and with the 6.2 firmware files found on "unbrick_your_switch" on xbins but to no avail.... the thing is that i think I fully screwed myself becasue I have a 4.0.1 nand back up but my fuse count is now 8. so if i try to install the 4.0.1 files on OFW i boot to a blue screen.... where as if i boot with the 6.2 files i see the nintendo logo and then black screen...

 

[jellybeangreen2]

Thank you for the replies on your own thread man, I really appreciate it.....sadly i tried this with both the 4.0.1 files generated by choidujour and with the 6.2 firmware files found on "unbrick_your_switch" on xbins but to no avail.... the thing is that i think I fully screwed myself becasue I have a 4.0.1 nand back up but my fuse count is now 8. so if i try to install the 4.0.1 files on OFW i boot to a blue screen.... where as if i boot with the 6.2 files i see the nintendo logo and then black screen...

You have to do it with 6.2. And you have to use choidujour to generate the firmware on PC using your prod.keys / keys.txt. - I will text this last part myself tonight. - You are using hackdiskmount to mount your system partition aren’t you?

 

[Calyptor]

You have to do it with 6.2. And you have to use choidujour to generate the firmware on PC using your prod.keys / keys.txt. - I will text this last part myself tonight.

Choi support stops at 6.0 if im not mistaken and yes using hackdiiscmount....But for sure keep me in the loop and again thank you for your replies

 

[jellybeangreen2]

Choi support stops at 6.0 if im not mistaken. But for sure keep me in the loop and again thank you for your replies

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