Hacking Question SX OS fails to load after updating switch to 6.2.0 using ChoiDujour

Shirpie · Dec 18, 2018

Hi, I used ChoiDujour to update my switch from 5.1.0 to 6.2.0, after I did that it worked fine. But then the system crashed, and I had to power off, after I powered off it doesn't load up anymore.
I tried restoring my boot0/1 backup but that doesn't do anything. How can I fix this?
Also I removed autorcm and booted to stock, but a blue screen comes up.

Ian San Miguel · Dec 18, 2018

Shirpie said:
Hi, I used ChoiDujour to update my switch from 5.1.0 to 6.2.0, after I did that it worked fine. But then the system crashed, and I had to power off, after I powered off it doesn't load up anymore.
I tried restoring my boot0/1 backup but that doesn't do anything. How can I fix this?
Also I removed autorcm and booted to stock, but a blue screen comes up.

Silly question, but you are using SXOS 2.41 right? I had a similar issue when I updated with ChoidujourNX, but then realised what I had done.
This was on emunand - worked fine after I updated boot.dat. Also made sure not to turn RCM on through ChoixdujourNX.

Shirpie · Dec 18, 2018

Ian San Miguel said:
Silly question, but you are using SXOS 2.41 right? I had a similar issue when I updated with ChoidujourNX, but then realised what I had done.
This was on emunand - worked fine after I updated boot.dat. Also made sure not to turn RCM on through ChoixdujourNX.

Yeah, I am on 2.41. I'll try that now thanks.

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

I downloaded the boot.dat from their website, and the boot logo came up, which it didn't before. But now there is a blue screen after the logo disappears.

Shirpie · Dec 19, 2018

Help anyone?

Wasi_White · Dec 19, 2018

Shirpie said:
Help anyone?

You resorted boot0/boot1 of your 5.1 backup it won't boot with 6.2
Restore your 5.1 backup with boot0/boot1 than RMC and load hekate 4.6 payload than load cfw and update. Or get the Kosmos SD Files and try with Kosmos SD Files

OraSama · Dec 19, 2018

I had the same issue and i solve it by formatting my sdcard as fat32 with guiformat

Shirpie · Dec 19, 2018

Thanks for the tips, I'll try them and see if it works

Shirpie · Dec 22, 2018

After following the steps in the ChoiDujour to restore my firmware I followed all the steps untill the last one when it just says "failed to launch firmware". what can i do?

Kafluke · Dec 22, 2018

Check your fuse count. It's wrong. You should have never tried to boot OFW without autorcm. You've probably burned your fuses up to 6.2 now and you flashed a 5.1 boot loader. You now have to update fully to 6.2 in order to fix

Shirpie · Dec 23, 2018

Update: Thanks to all who helped, my switch is now working perfectly.

Dovla · Dec 23, 2018

I had the same issue but then it turned out that the SX dongle ran out of battery...charged it again and it worked fine

designgears · Dec 23, 2018

Kafluke said:
Check your fuse count. It's wrong. You should have never tried to boot OFW without autorcm. You've probably burned your fuses up to 6.2 now and you flashed a 5.1 boot loader. You now have to update fully to 6.2 in order to fix

This is wrong, you could always downgrade but sleep mode would cause the switch to reboot. That's been fixed in all current CFW.

Kafluke · Dec 23, 2018

You cant downgrade OFW ever if you have fuses burned. You can still boot to OFW using CFW because it doesnt check fuses but if you want to actually downgrade your sysnand you have to have same number of fuses

naddel81 · Dec 23, 2018

Ian San Miguel said:
Silly question, but you are using SXOS 2.41 right? I had a similar issue when I updated with ChoidujourNX, but then realised what I had done.
This was on emunand - worked fine after I updated boot.dat. Also made sure not to turn RCM on through ChoixdujourNX.

why not use RCM with SX OS?

designgears · Dec 23, 2018

Kafluke said:
You cant downgrade OFW ever if you have fuses burned. You can still boot to OFW using CFW because it doesnt check fuses but if you want to actually downgrade your sysnand you have to have same number of fuses

Using Choi/NX you can downgrade to any FW version, fuses don't matter.

Kafluke · Dec 23, 2018

You cant downgrade and then run OFW without first loading a custom boot loader if you have burnt fuses. Are you even listening to me? If your fuse count is higher than the firmware you are trying to downgrade to then your switch wont boot without first going into RCM every time. Or autorcm. It's the CFW that allows bypassing fuse check but your switch will not boot at all by itself into OFW if your fuse count is wrong.

Ian San Miguel · Dec 24, 2018

naddel81 said:
why not use RCM with SX OS?

Because you're in emunand already - you don't need to worry about fuses getting burned if you accidentally turn on your switch into OFW. Only need RCM on through choidujour if you're booting straight into CFW WITHOUT emunand, as you want to update without burning fuses.

Kafluke · Dec 24, 2018

Does the switch autoboot to emunand without RCM? I thought you still needed to launch a payload first.

Armen · Dec 24, 2018

Shirpie said:
Update: Thanks to all who helped, my switch is now working perfectly.

Can you please let us know what you did and the steps to get it working again? I want to do some stuff on my switch and if I run into any issues, I would like to learn and get as much information as I can, if you don't mind to share.

Thanks and Happy Holidays!

naddel81 · Dec 24, 2018

Ian San Miguel said:
Because you're in emunand already - you don't need to worry about fuses getting burned if you accidentally turn on your switch into OFW. Only need RCM on through choidujour if you're booting straight into CFW WITHOUT emunand, as you want to update without burning fuses.

I never used emunand, since I do not play online with anything. maybe I could use fortnite, but... meh. So I only use CFW and will update with choidujourNX and RCM on.

is there a way to start a fresh emunand without any treacherous telemetry data sent to nintendo?

Hacking Question SX OS fails to load after updating switch to 6.2.0 using ChoiDujour

Well-Known Member

Member

Well-Known Member

Well-Known Member

Active Member

New Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Active Member

Well-Known Member

Similar threads

Popular threads in this forum