Hacking Switch "bricked" after updating offline with ChoidujourNX

[Hirotsugi]

I updated my Switch offline using ChoidujourNX. Everything was fine, but after i clicked on the reboot button, I wasn't able to boot the console normally. The Switch gives me only a black screen. I tried a lot of things to start it again, but it seems that I can only boot the switch using ReiNX and only if I select the official firmware (I tried with ReiNX alone, and ReiNX with LayeredFS, but nothing changes, even with the other options like Debug ecc.). So this is my situation. I don't know if it can help but I have an SX OS Pro, but the console wasn't on AutoRCM and I did not use it before or after the update. By the way, the Switch firmware is now 6.0.0, before the update it was at 5.0.1, so the update seems to have worked. Do you have some advice for solving this situation? Thanks.

 

[gt10]

i think ChoiDujourNX activates autorcm automatically, so you don't burn your fuses.
that why ChoiDujourNX made.
to make it possible to go back to lower firmware.

 

[lordelan]

I updated my Switch offline using ChoidujourNX. Everything was fine, but after i clicked on the reboot button, I wasn't able to boot the console normally. The Switch gives me only a black screen. I tried a lot of things to start it again, but it seems that I can only boot the switch using ReiNX and only if I select the official firmware (I tried with ReiNX alone, and ReiNX with LayeredFS, but nothing changes, even with the other options like Debug ecc.). So this is my situation. I don't know if it can help but I have an SX OS Pro, but the console wasn't on AutoRCM and I did not use it before or after the update. By the way, the Switch firmware is now 6.0.0, before the update it was at 5.0.1, so the update seems to have worked. Do you have some advice for solving this situation? Thanks.

Sounds like AutoRCM is enabled.
Try putting the SDfiles on your SD card. Then boot using your SX Pro while holding VOL-
Select "load external payload", load hekate and load a CFW from there.

 

[Hirotsugi]

Sounds like AutoRCM is enabled.
Try putting the SDfiles on your SD card. Then boot using your SX Pro while holding VOL-
Select "load external payload", load hekate and load a CFW from there.

I tried booting the Switch with the SX, but it doesn't change nothing, the screen remains black.

 

[regnad]

Get TegraRcmGUI and inject a payload like briccme.bin, or get the hekate or reinx files on the SD and inject that payload.

 

[urherenow]

In other words, you CAN’T boot your switch without RCM, because now the number of burnt fuses is inappropriate for your firmware version. This is why I think updating this way is stupid. It’s a PITA and completely useless, especially since you were above 3.x to begin with (rumors/hopes of coldboot CFW in the future for 3.x). Only reason someone has a valid excuse to update this way above 3.x is if you’re already banned and can’t update normally.

 

[Working_Goose]

You have to learn to read, then you would know what you are doing

 

[Der_Blockbuster]

In other words, you CAN’T boot your switch without RCM, because now the number of burnt fuses is inappropriate for your firmware version. This is why I think updating this way is stupid. It’s a PITA and completely useless, especially since you were above 3.x to begin with (rumors/hopes of coldboot CFW in the future for 3.x). Only reason someone has a valid excuse to update this way above 3.x is if you’re already banned and can’t update normally.

What the fuck? There is no problem with updating with Choijour if people would just be careful and properly read what to do.
What's negative about having the choice of going back? Rather then not?
Having the choice is always good. If you update this way how it's meant to be, then the fuse count will be ignored.
Tx users, may be not that informed about RCM and such, because it's often not relevant for their use case.
And now fiddleing with non Tx software could be a bit dangerous because such people don't take any precautions.

 

[Risingdawn]

Just stick the most recent Boot.dat from TX on your SD card and use your sxpro to boot!

I don't see what the problem is here?

 

[Hirotsugi]

Ok, using briccme I was able to disable the autoRCM and booting the console normally. But now there is another problem, the console doesn't read my sd card, so I can't boot using the SX OS. I already formatted the sd card in exFAT as I read online somewhere, but this didn't resolve the problem. Any suggestions?

 

[Working_Goose]

did u use it on exfat befor?

 

[Hirotsugi]

did u use it on exfat befor?

Honestly I don't remember how I formatted the sd card the first time. This problem has started after I updated to 6.0.0. It tells me that to use my microSDXC card, I need to update.

 

[Solitario]

did you enable the option upgrade to 6.0.1 with exfat support ?

 

[Hirotsugi]

did you enable the option upgrade to 6.0.1 with exfat support ?

I've updated to 6.0.0, so I don't think so. I will update to 6.0.1 and find some guide to enable exfat support then, thanks.

 

[lufeig]

this is gbatemp: people have to learn to read before doing what they don't know

choidujournx automatically enables autorcm

if you don't want it enabled, just click on it before writing the new firmware

 

[kumikochan]

Are you also sure you got the latest Reinx installed and not the prior version that didn't work on 6.0 ?

 

[Hirotsugi]

After updating again with the exFat support, everything was ok. And yes, to be safe I downloaded the latest versions of all the things I needed. I wanted to thank everyone for the help!

 

[urherenow]

What the fuck? There is no problem with updating with Choijour if people would just be careful and properly read what to do.
What's negative about having the choice of going back? Rather then not?
Having the choice is always good. If you update this way how it's meant to be, then the fuse count will be ignored.
Tx users, may be not that informed about RCM and such, because it's often not relevant for their use case.
And now fiddleing with non Tx software could be a bit dangerous because such people don't take any precautions.

Watch your mouth. What's negative is the fact that until a coldboot method comes around to the public, autorcm makes your system unbootable without a tether, whether it be an android phone, PC or dongle. It's a pain. And you get threads like this. More than that, updating this way makes it impossible to boot without CFW. I am not banned and prefer to NOT be in CFW when visiting the eshop, thank you.

 

[Der_Blockbuster]

Watch your mouth. What's negative is the fact that until a coldboot method comes around to the public, autorcm makes your system unbootable without a tether, whether it be an android phone, PC or dongle. It's a pain. And you get threads like this. More than that, updating this way makes it impossible to boot without CFW. I am not banned and prefer to NOT be in CFW when visiting the eshop, thank you.

Don't like it don't use it. You got it bro.

 

[Tackey]

Hello OP, I made the same mistake as you when I updated to 7.0.0 on my Switch. Now all I get is a black screen. How were you able to use briccme to disable AutoRCM?