Hacking Nintendo Switch Doesn't Open Up No More

Downgrade via choidujour nx? If so that wouldn't "kill" it.

What format is your sdcard?
If it is exFAT have you maybe accidentally selected the non exFAT firmware in choidujour nx?

If so either use another sdcard formatted as FAT32 to "upgrade" to 8.1 or, copy the data off your sdcard to pc, format sd as FAT32, copy data back. It will work now.

You can then copy data off and reformat to exFAT or just stay on FAT32.
 
It's not dead. Just Burnt Fuses or like Dave said the SD card is in wrong format. I faced the same problem this week.
What i did were
- plugging it to the PC to detect the RCM mode via TegraRcmGUI.
- Keep Pressing Power and Vol+ several times until it go to RCM Mode
- When it go to RCM mode, just use choidujour nx to upgrade to firmware 9
 
Last edited by dudephanith,
Downgrade via choidujour nx? If so that wouldn't "kill" it.

What format is your sdcard?
If it is exFAT have you maybe accidentally selected the non exFAT firmware in choidujour nx?

If so either use another sdcard formatted as FAT32 to "upgrade" to 8.1 or, copy the data off your sdcard to pc, format sd as FAT32, copy data back. It will work now.

You can then copy data off and reformat to exFAT or just stay on FAT32.
So what I saw my SD card has been on FAT32 for a while.

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

It's not dead. Just Burnt Fuses or like Dave said the SD card is in wrong format. I faced the same problem this week.
What i did were
- plugging it to the PC to detect the RCM mode via TegraRcmGUI.
- Keep Pressing Power and Vol+ several times until it go to RCM Mode
- When it go to RCM mode, just use choidujour nx to upgrade to firmware 9
How does one go in RCM mode and choose ChoidujourNX?
 
So what I saw my SD card has been on FAT32 for a while.
How does one go in RCM mode and choose ChoidujourNX?
I'm not exactly sure but if you prepare an SD card with Hekate and add the ChoiDuJoirNX.nro to the 'switch' folder, you seem to be able to start it from the Tools menu.
For upgrading you also need the firmware on that SD card.

There is also the option of doing it with a PC when all hope is lost :
https://switch.homebrew.guide/usingcfw/manualchoiupgrade#
But I would try Hekate first....

For entering RCM mode you need a jig and payload injector (pc/smartphone/standalone).
Pressing vol- and power should get you into RCM mode.
But I presume you've done that before as you are already on a CFW.
 
Last edited by thesjaakspoiler,
I'm not exactly sure but if you prepare an SD card with Hekate and add the ChoiDuJoirNX.nro to the 'switch' folder, you seem to be able to start it from the Tools menu.
For upgrading you also need the firmware on that SD card.

There is also the option of doing it with a PC when all hope is lost :
https://switch.homebrew.guide/usingcfw/manualchoiupgrade#
But I would try Hekate first....

For entering RCM mode you need a jig and payload injector (pc/smartphone/standalone).
Pressing vol- and power should get you into RCM mode.
But I presume you've done that before as you are already on a CFW.
I'm pretty sure you can't launch ChoiDujourNX from RCM, but that's not a bad idea. Someone should make that happen.
 
So what I saw my SD card has been on FAT32 for a while.

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


How does one go in RCM mode and choose ChoidujourNX?
What i meant is keep pressing Power button and Vol+ until can go to RCM mode then inject Hekate payload. then choose CFW(sysnand). After that just downgrade.
 
Alright let's get some things straight.

> My switch burnt fuses from v9.0.0 to v8.1.0
> I think it burnt 11 fuses based on Wikipedia
> I cannot go in it normally as it tells me I have an error
> I tried doing it exFAT and FAT32 but nothing good happens
> I thinking my BOOT0 and BOOT1 is corrupted...
 
Alright let's get some things straight.

> My switch burnt fuses from v9.0.0 to v8.1.0
> I think it burnt 11 fuses based on Wikipedia
> I cannot go in it normally as it tells me I have an error
> I tried doing it exFAT and FAT32 but nothing good happens
> I thinking my BOOT0 and BOOT1 is corrupted...
You cant burn fuses by downgrading to 8.1.0. You burnt fuses by updating to 9.0.0 if you didn't protect with autoRCM. Can you enter RCM?
 
Alright let's get some things straight.

> My switch burnt fuses from v9.0.0 to v8.1.0
> I think it burnt 11 fuses based on Wikipedia
> I cannot go in it normally as it tells me I have an error
> I tried doing it exFAT and FAT32 but nothing good happens
> I thinking my BOOT0 and BOOT1 is corrupted...
What CFW are you using? Which payload are you using? Hekate wouldn't care about fuses and wouldn't panic. Why do you think your boot0/1 is corrupt? How did you downgrade from 9 to 8.1? Using ChoiDujourNX or something else? Since you seemed to be unfamiliar with ChoiDujourNX.
 
What CFW are you using? Which payload are you using? Hekate wouldn't care about fuses and wouldn't panic. Why do you think your boot0/1 is corrupt? How did you downgrade from 9 to 8.1? Using ChoiDujourNX or something else? Since you seemed to be unfamiliar with ChoiDujourNX.
Alright.
> CFW. You mean how I boot into Switch? Atmosphere
> I’m just using Hekate now.
> Because I’m trying to get keys using BOOT0/BOOT1
> I used ChoiDujuorNX to downgrade
 
Alright.
> CFW. You mean how I boot into Switch? Atmosphere
> I’m just using Hekate now.
> Because I’m trying to get keys using BOOT0/BOOT1
> I used ChoiDujuorNX to downgrade
Alright. A good start. If you boot Hekate/Nyx and try to dump your boot0/1 keys, what happens?
 
Atmosphere logo. Nintendo logo. Switch logo. Then error.
What error? Does it show an error? If so, please include a screenshot/photo. Saying 'error' doesn't help too much, as that doesn't describe what is happening.

Are you using Kosmos? Is it updated?
 
What error? Does it show an error? If so, please include a screenshot/photo. Saying 'error' doesn't help too much, as that doesn't describe what is happening.

Are you using Kosmos? Is it updated?
Here are the two errors I get.
 

Attachments

  • 6426B408-5526-4F8C-9601-AB56C560C216.jpeg
    6426B408-5526-4F8C-9601-AB56C560C216.jpeg
    1.3 MB · Views: 255
  • 5E819A2A-E3D9-43C5-AB5D-CF9CA68919CD.jpeg
    5E819A2A-E3D9-43C5-AB5D-CF9CA68919CD.jpeg
    1.6 MB · Views: 230

Site & Scene News

Popular threads in this forum