Hacking Nintendo Switch Does Not Boot Anymore

[Ujico]

EDIT: ISSUE IS FIXED. This is how you can fix it:

EDIT 2: I figured, it's better to not update from 9.2.0 from within the OFW. Nintendo can see that your fusecount doesn't match and might ban you for it. Better to download it somewhere externally.

1. Insert your SD-card into your PC and delete all the files on it.
2. Download atmosphere-0.11.1-master-d81a3bdc+hbl-2.3.1+hbmenu-3.3.0.zip and fusee-primary.bin
   on GitHub.
3. Extract the contents of atmosphere-0.11.1-master-d81a3bdc+hbl-2.3.1+hbmenu-3.3.0.zip to the root of your SD-card.
4. Download Hekate hekate_ctcaer_5.1.4_Nyx_0.8.7.zip from GitHub.
5. Extract hekate_ctcaer_5.1.4_Nyx_0.8.7.zip to the root of your SD-card.
6. Go into the [bootloader] folder on your SD-card and create a [payloads] folder inside of it if it doesn't exist yet.
7. Place the fusee-primary.bin file inside the [payloads] folder.
8. Put the SD-card back into your Nintendo Switch and inject the hekate_ctcaer_5.1.4.bin file like normally, via TegraRCMGUI on your PC and insert the RCM-jig into your NSwitch etc.
9. After Hekate loaded, click on the Payloads button in the Hekate Bootloader and start the fusee-primary.bin file.
10. Update your Switch to 10.0.
11. Reboot completely and you're done! Your CFW will still work after updating since you updated everything to the latest version.

Hi, I downgraded my Nintendo Switch from 10.0 to 9.2. I messed up big time. I know.

Anyhow. I was able to revert to version 9.2 for both CFW and OFW. The problem is. Whenever I try to boot my Nintendo Switch I receive nothing. No lights, no sound. As if the Nintendo Switch is dead. Is there any way to restore this?

I can however load RCM mode and inject Hekate. If I boot OFW or CFW from there, it loads perfectly fine. I read A LOT today. I think it has to do with my fuse count? It was 13 when I updated to 10.0. I probably have to revert from 9.2.0 to 10.0 again to match the Switch Fuse? But how do I do that? I did not make a backup of the 10.0 version, which was incredibly stupid. To clarify; my Switch does work. But only if I load the firmware via Hekate.

Any ideas/advice? Thanks in advance... I just realized I can actually update from 9.2.0 to 10.0 again and probably fix it but that would make me lose my CFW I guess?

 

[osaka35]

Hi, I downgraded my Nintendo Switch from 10.0 to 9.2. I messed up big time. I know.

Anyhow. I was able to revert to version 9.2 for both CFW and OFW. The problem is. Whenever I try to boot my Nintendo Switch I receive nothing. No lights, no sound. As if the Nintendo Switch is dead. Is there any way to restore this?

I can however load RCM mode and inject Hekate. If I boot OFW or CFW from there, it loads perfectly fine. I read A LOT today. I think it has to do with my fuse count? It was 13 when I updated to 10.0. I probably have to revert from 9.2.0 to 10.0 again to match the Switch Fuse? But how do I do that? I did not make a backup of the 10.0 version, which was incredibly stupid. To clarify; my Switch does work. But only if I load the firmware via Hekate.

Any ideas/advice? Thanks in advance... I just realized I can actually update from 9.2.0 to 10.0 again and probably fix it but that would make me lose my CFW I guess?

You can boot to CFW, download the official 10.0 from..somewhere (not here) and update to 10.0 using choidujournx. Update atmosphere first before you do.

CFW will boot regardless, but OFW won't boot with mismatched fuses.

 

[josephdin]

If anyone finds the 10.0 link please let us know

 

[pcwizard7]

yea if fw 10.0 ups the fuse count and you downgrade to 9.2. the only way to boot 9.2 is with Hekate else you have to be on fw 10.0 to boot without a payload.

if this is your cfw switch I would stay on 9.2 for a bit until the official update atmos is up ( the current one is a pre release to weed out bugs) as u need hekate for it anyways.

If anyone finds the 10.0 link please let us know

if you google it you find it

 

[pLaYeR^^]

I think it has to do with my fuse count? It was 13 when I updated to 10.0. I probably have to revert from 9.2.0 to 10.0 again to match the Switch Fuse?

You can't revert the fuse count. Once they burned, you can't boot lower firmware with official boot loader anymore.

 

[pcwizard7]

You can't revert the fuse count. Once they burned, you can't boot lower firmware with official boot loader anymore.

once they update to 10.0 they can. boot into hos with hekate update back to 10.0 and bam u can use official bootloader again

remember to update your sd files for fw 10 cfw and its done

 

[pLaYeR^^]

once they update to 10.0 they can. boot into hos with hekate update back to 10.0 and bam u can use official bootloader again

remember to update your sd files for fw 10 cfw and its done

Yes but not lower firmwares like I have mentioned.

 

[josephdin]

yea if fw 10.0 ups the fuse count and you downgrade to 9.2. the only way to boot 9.2 is with Hekate else you have to be on fw 10.0 to boot without a payload.

if this is your cfw switch I would stay on 9.2 for a bit until the official update atmos is up ( the current one is a pre release to weed out bugs) as u need hekate for it anyways.



if you google it you find it

i googled multiple variations of "nintendo switch 10.0 update download" and no download links in the first 2 pages so i stopped looking. GOOD ONE DUDE

 

[Kafluke]

i googled multiple variations of "nintendo switch 10.0 update download" and no download links in the first 2 pages so i stopped looking. GOOD ONE DUDE

We cant provide you links on here. You have to find it yourself.

I just found download links in two minutes of googling. If you cant find it that's your problem.

 

[Ujico]

Hi, I downgraded my Nintendo Switch from 10.0 to 9.2. I messed up big time. I know.

Anyhow. I was able to revert to version 9.2 for both CFW and OFW. The problem is. Whenever I try to boot my Nintendo Switch I receive nothing. No lights, no sound. As if the Nintendo Switch is dead. Is there any way to restore this?

I can however load RCM mode and inject Hekate. If I boot OFW or CFW from there, it loads perfectly fine. I read A LOT today. I think it has to do with my fuse count? It was 13 when I updated to 10.0. I probably have to revert from 9.2.0 to 10.0 again to match the Switch Fuse? But how do I do that? I did not make a backup of the 10.0 version, which was incredibly stupid. To clarify; my Switch does work. But only if I load the firmware via Hekate.

Any ideas/advice? Thanks in advance... I just realized I can actually update from 9.2.0 to 10.0 again and probably fix it but that would make me lose my CFW I guess?

EDIT: I can also use OFW. But via Hekate. For clarification.

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

You can boot to CFW, download the official 10.0 from..somewhere (not here) and update to 10.0 using choidujournx. Update atmosphere first before you do.

CFW will boot regardless, but OFW won't boot with mismatched fuses.

I might as well just start Hekate, boot the official firmware (OFW) from there and update it to 10.0. This will restore the fuse mismatch, correct? And download Hekate 10.0 payload file to boot into Hekate afterwards right? Atmosphere doesn't fully support 10.0 yet, it's a pre-release so I'll have to wait for that.

 

[pcwizard7]

EDIT: I can also use OFW. But via Hekate. For clarification.
.

atmos and hekate have been updated so if u update your sd card files and you can use choi or official way to update to fw 10.0

PS: google "nintendo switch firmware download"

 

[Ujico]

You can't revert the fuse count. Once they burned, you can't boot lower firmware with official boot loader anymore.

I know.It's only possible to load the OFW with an unofficial bootloader such as Hekate. By booting the OFW via Hekate, I can update it to 10.0 and restore my Switch's fuse count mismatch right? So that the internal fuse count of 13 matches the OFW update from 9.2 to 10.0? But that'll remove my atmosphere CFW since it's currently only for 9.2?

 

[pcwizard7]

I know.It's only possible to load the OFW with an unofficial bootloader such as Hekate. By booting the OFW via Hekate, I can update it to 10.0 and restore my Switch's fuse count mismatch right? So that the internal fuse count of 13 matches the OFW update from 9.2 to 10.0? But that'll remove my atmosphere CFW since it's currently only for 9.2?

once you on the firmware that matches the fuse count i.e fw 10.0 you can use the official bootloader again. atmos and hekate have been updated so if u update your sd files it will work

 

[Ujico]

yea if fw 10.0 ups the fuse count and you downgrade to 9.2. the only way to boot 9.2 is with Hekate else you have to be on fw 10.0 to boot without a payload.

if this is your cfw switch I would stay on 9.2 for a bit until the official update atmos is up ( the current one is a pre release to weed out bugs) as u need hekate for it anyways.



if you google it you find it

OK so. Hekate 10.0 is released. In short: If I boot the OFW via Hekate and update from 9.2.0 to 10.0, I will be able to use the Nintendo Bootloader again to start the OS correct? This will also remove my CFW. Hekate can still be loaded since it now supports version 10.0 but my CFW will be lost, correct? As you said, Atmosphere is currently in pre-release. So the best thing to do is wait a bit for Atmosphere to release a 10.0 version and then update?

 

[pcwizard7]

OK so. Hekate 10.0 is released. In short: If I boot the OFW via Hekate and update from 9.2.0 to 10.0, I will be able to use the Nintendo Bootloader again to start the OS correct? This will also remove my CFW. Hekate can still be loaded since it now supports version 10.0 but my CFW will be lost, correct? As you said, Atmosphere is currently in pre-release. So the best thing to do is wait a bit for Atmosphere to release a 10.0 version and then update?

if you asking about cfw trance left on the console then no. if you update atmos too cfw will work again too

go here to grab all update files and select kosmos defaults then feel free to select things you wish to add to it
https://www.sdsetup.com/

then you need to update hekate and atmos so once you have the above on the sd card then overwrite files with these updates
https://github.com/Atmosphere-NX/Atmosphere/releases/latest
https://github.com/CTCaer/hekate/releases/latest

 

[Ujico]

if you asking about cfw trance left on the console then no. if you update atmos too cfw will work again too

go here to grab all update files and select kosmos defaults then feel free to select things you wish to add to it
https://www.sdsetup.com/

then you need to update hekate and atmos so once you have the above on the sd card then overwrite files with these updates
https://github.com/Atmosphere-NX/Atmosphere/releases/latest
https://github.com/CTCaer/hekate/releases/latest

Dope. Switch is working again. Thanks for the help.

What I did was: Download Hekate 10.0 release. Download Atmosphere 10.0 release. And replaced the files on my SD-card. Executed fusee-primary.bin. Updated my Switch to 10.0 and rebooted. Works! Thanks again.

 

[Ujico]

i googled multiple variations of "nintendo switch 10.0 update download" and no download links in the first 2 pages so i stopped looking. GOOD ONE DUDE

Check my post. I made an edit on how to fix it.

 

[Naitsrk]

I did something a little different

I was on 10.0.2 and restored my NAND to the backup I created prior to me hacking the switch. (9.2). I know. I'm an idiot.

I didn't make another backup before doing this because I thought why would I need a backup of the one I don't want? For whatever reason I - even following this guide - can't boot into atmosphere. I get as far as the A logo then black screen of doom.

EDIT: I was able to fix it by going into Hekate>Launch>STOCK>Update via wifi. I couldn't boot into CFW at all i'd get the silent black screen of death. Since stock is the only thing that worked I had no choice but to connect to the internet and update via regular means. My nand backup was pre-all hacks and I had no issues updating my console to 10.0.3.

 

[pLaYeR^^]

I did this too.. But I also installed autoRCM, then uninstalled autoRCM because I didn't think I needed it while my switch was in *no sound or anything mode*

Now even with a jig I can't get it to boot into RCM.. I think this one is completely toast

Note for everyone else in the future: If you accidentally downgrade via restoring an old NAND and manage to get into RCM - Don't INSTALL/UNINSTALL AutoRCM because then you are bricked for good.

If something changes I will update.

You should still be able to boot to RCM with a jig no matter if you have autoRCM or not.

 

[Naitsrk]

You should still be able to boot to RCM with a jig no matter if you have autoRCM or not.

You are right - the jig I have wasn't working and I did the old fashioned foil on the joycon method and it worked.

That being said, this guide still doesn't fix my problem unfortunately.

My goal was to restore my nand to pre-hack and then do an emunand instead. Of course I spaced that my NAND backup was 9.2 (I was on 10.0.2). So I restored the nand and now my switch won't boot (i can get into rcm though). CFW doesn't even work and this guide doesn't fix my issue.. I wonder if there's something else?

EDIT: I was able to fix it by going into Hekate>Launch>STOCK>Update via wifi. I couldn't boot into CFW at all i'd get the silent black screen of death. Since stock is the only thing that worked I had no choice but to connect to the internet and update via regular means. My nand backup was pre-all hacks and I had no issues updating my console to 10.0.3.