Still on 5.1.0 - where to go from here?

LilaQ

Junior Member
Mar 21, 2006
15
0
Hi guys,

I'm still on 5.1.0, but now I experienced a few games not to boot, because my FW is too low.

Where is the best way to from here, which FW should I target now, and what precautions should I take?
I'm struggeling to get the correct info (which is still valid) from all the threads.

I would really appreciate any help on what I should and shouldn't do.

Thanks in advance!

Best regards,
LQ
 

lyn2018

Full Member
Sep 23, 2018
34
8
Set up an SD-emuNand and update it offline to the latest FW if you do not want to update your OFW!
 
Last edited:

imprezgc8

Bannnnnn-Kai!
Staff member
Troll Eating Dogs
Nov 26, 2007
2,424
138
The Cloud
Honestly if you do not have games requiring 6.2 firmware then theres really no reason to upgrade unless you really want to. Especially if you are staying offline. If you do still want to upgrade just because do like lyn2018 said. First make a new nand backup just in case. Create an emunand, boot to the emunand and run ChoijudourNX to upgrade to 6.2. Make sure you select exfat when upgrading. Also you will need to source the firmware file. There is a thread here with a link to them I think.
 

shoey

Noob Account
Dec 20, 2018
3
1
Set up an SD-emuNand and update it offline to the latest FW if you do not want to update your OFW!
Sorry to hop onto this thread, but i'm seeking help. And the information is probably useful for the TS as well.

My sysnand is on 5.1.0, created a hidden partition emunand and upgraded using choidujournx to 6.2.0 but unable to boot. First instance: Was stuck on a black screen when AutoRCM was selected in choidujournx. Second instance: Stuck on Nintendo Boot logo when AutoRCM was not selected.

Anybody had similar issues and was able to resolve it?

Many thanks!
 

n000ir

Noob Account
Dec 21, 2018
4
0
Sorry to hop onto this thread, but i'm seeking help. And the information is probably useful for the TS as well.

My sysnand is on 5.1.0, created a hidden partition emunand and upgraded using choidujournx to 6.2.0 but unable to boot. First instance: Was stuck on a black screen when AutoRCM was selected in choidujournx. Second instance: Stuck on Nintendo Boot logo when AutoRCM was not selected.

Anybody had similar issues and was able to resolve it?

Many thanks!
I'm setting up a brand new Switch and had the same issue when I updated emunand to 6.2.0 using ChoiDujourNX. Couldn't boot, stuck on black screen. Possible to boot OFW. I've deleted the emunand and are currently creating a new. Will try again, maybe using 6.1.0.
 

Bloodlust

Full Member
Jun 22, 2018
61
8
I am also on 5.1 ofw but planning to update to 6.2 on emunand using a sdcard. So it simply won't work without updating the ofw to 6.2 as well?
 

n000ir

Noob Account
Dec 21, 2018
4
0
Well, it didn't work for me! I tried to create a new Emunand after deleting the old one (that I tried to update to 6.2.0) but now I can't seem to boot into CFW at all. I just boot into OFW. Have tried to uninstall Autorcm and format SD card without luck.

EDIT: OK, this is weird. I tried to format the SD card using FAT32 and then I could boot CFW! Tried to format the card back to exFAT and then it booted into OFW. It seems the SD card somehow is the culprit, but I had CFW up and running using the same card format in exFAT a couple of hours ago. New (legit) 200GB SD card from Sandisk.
 
Last edited:

imprezgc8

Bannnnnn-Kai!
Staff member
Troll Eating Dogs
Nov 26, 2007
2,424
138
The Cloud
I am also on 5.1 ofw but planning to update to 6.2 on emunand using a sdcard. So it simply won't work without updating the ofw to 6.2 as well?
You do not need to upgrade you OFW in order for emunand to work on the same firmware. One of the reasons for emunand is to keep your OFW lower. If there is an issue something is happening on that users end that is causing the issue. Either the firmware file they have is corrupt or their SD card has corruption.
 
  • Like
Reactions: Bloodlust

shoey

Noob Account
Dec 20, 2018
3
1
Was there anything special that you did to update your emunand to 6.2.0? Or it was just through ChoiDujour NX and it worked right off the bat?
 

imprezgc8

Bannnnnn-Kai!
Staff member
Troll Eating Dogs
Nov 26, 2007
2,424
138
The Cloud
Was there anything special that you did to update your emunand to 6.2.0? Or it was just through ChoiDujour NX and it worked right off the bat?
For me it worked the first time, but I am using SD files emunand, not the partition or sysnand version. I followed the guide on here for updating banned switches offline, but just made sure I was booted to emunand first. I am currently running SX 2.5Beta. OFW 5.1.0 and emunand 6.2.

What I would do it this:

1. Back up your sysnand again just to be safe
2. Back whatever files up from the SD
3. Format the SD (I use exfat though there is a higher chance for corruption, you can use fat32 if you so choose. You'll need to split files larger than 4GB though)
4. Put only the license file and boot.dat file back on the SD and boot to SX bootloader
5. Enable emunand and check if it is working again with 5.1 (Like I said I use the SD files option)
6. If it is working, then download the 6.2 firmware again and verfiy that the download is not corrupt. You can use md5checker
7. If it is a clean download, create a folder on your SD card and put the 6.2 folder there
8. Make sure you have ChoijudourNX nro on your SD card and boot your CFW emunand
9. Load ChoijudourNX and follow the prompts. You can use the upgrading banned switches guide on here at this point
10. Test again that emunand is working on 6.2
 

shoey

Noob Account
Dec 20, 2018
3
1
For me it worked the first time, but I am using SD files emunand, not the partition or sysnand version. I followed the guide on here for updating banned switches offline, but just made sure I was booted to emunand first. I am currently running SX 2.5Beta. OFW 5.1.0 and emunand 6.2.

What I would do it this:

1. Back up your sysnand again just to be safe
2. Back whatever files up from the SD
3. Format the SD (I use exfat though there is a higher chance for corruption, you can use fat32 if you so choose. You'll need to split files larger than 4GB though)
4. Put only the license file and boot.dat file back on the SD and boot to SX bootloader
5. Enable emunand and check if it is working again with 5.1 (Like I said I use the SD files option)
6. If it is working, then download the 6.2 firmware again and verfiy that the download is not corrupt. You can use md5checker
7. If it is a clean download, create a folder on your SD card and put the 6.2 folder there
8. Make sure you have ChoijudourNX nro on your SD card and boot your CFW emunand
9. Load ChoijudourNX and follow the prompts. You can use the upgrading banned switches guide on here at this point
10. Test again that emunand is working on 6.2
Thanks for the detailed explanation. The only difference for me was that mine was on the hidden partition and that I didn't format my sd card prior to setting up the emunand.