What should I do to install exFAT driver without update firmwork now?

[slamride]

The way I understand fuse count is
If you want to be able to downgrade at a later date use Autorcm. For instance if I want to update (not in emunand) to 6.1 but retain the option to return to 5.0 then use Autorcm because if booted normally into 6.1 the fuses will be burnt to current firmware blocking it.
May be wrong. If anyone can confirm please do

 

[slamride]

Don't have to have Emunand but it is a great option. It allows you to have basically 2 versions of firmware. Great thing about Emunand is anything in that environment does not alter the factory environment (with a few exceptions). So emunand can be 6.1 with CFW and the original switch OS remains untouched so you have a failsafe. You can also keep original on lower firmware or with factory installed games,etc. Still unsure if a ban possible online even on original so be careful. Emunand takes a dump you can just delete it and your back to factory starting over with no downgrading,nand rewrites,etc

 

[Nickoy]

Thankyou for the info provided it is definately helping me in understanding the processes. So you would recommend using emunand and AutoRCM? As I wasn’t going to bother. I had heard that AutoRCM can cause battery drain. All the best nickoy

 

[Nickoy]

Ps my SX Pro has just been delivered. Looking forward to getting this set up tonight!!!!

 

[slamride]

Ps my SX Pro has just been delivered. Looking forward to getting this set up tonight!!!!

I highly recommend Emunand. I personally use Emunand and not AutoRCM. The only issue I have with AutoRCM is hard to see if screen is on or off sometimes(killing battery) and I can't be sure exactly what status my switch is in. I am using 6.1 for OFW and CFW so I really don't need it anyway. Also I picked the standard white theme and removed all my games from OFW screen so I can tell if I am in Emunand really easily. I used Black theme for Emunand and games show so I know Im on emunand CFW. It automatically sets up to boot to emunand (can be changed)but I like to be certain. I have a 4 year old using it so simplicity and failsafe is my goal. Emunand acts the same as OFW except allows added features so you will notice no difference really. Great thing is not altering original nand which is how you end up with bricks if not very careful. Highly reduced chances of a brick with Emunand (nothing is 100%).Only takes few mins to setup and benefits heavily out weight time spent. AutoRCM is personal choice for those wanting to maintain lowest firmware for possibly coldboot exploits and so on. MAKE PLENTY OF BACKUPS of nand and keys.You can never have enough email it,backup to cloud,put on usb or sd and don't use for anything else. A lot of bricks can be fixed when you have backups. Also don't just do 1 dump and copy it make multiple dumps and name them using serial on console to help later if you have multiple systems. Spending an hour or so now can make the difference later. I have backups from XBOX still and have used them recently. Read tutorials 2-3 times before doing them...it helps..and follow step by step not skipping anything. Above all take your time and verify every step and don't rush to get it done. You will be glad you did when it works with less or no issues.

 

[xs4all]

@Game_Over

Thanks for the insight as to how Fuses work, makes things much clearer.
Question:
Are you,your team or anyone able to confirm when using ChoiDujourNX to update Emunand, will it flag to burn a FUSE be carried over to OFW? Or does the Emunand has something built in to bypass this in either Emunand or OFW?

...Now regarding ChoiDujourNX, do you require AUTORCM so you don't burn a efuse in Enumand?
From my personal experience, this DOES NOT apply to Emunand because the OFW doesn't know anything about your Emunand and what you've been up to.
As a test, I don't have AUTORCM enabled, I have booted into my OFW with and without my SD CARD a few times, and checked my FUSE and the count IS still 7, which is correct for 6.x.x FW.
I'm using the RCM Jig that came with the SX PRO package.

Just quoting what I wrote above in my previous reply, I have updated the above statement with some added info.
After some investigation, if you read information about the Switch's FUSES HERE (Scroll down to the bottom of the page). I'm pretty sure the reason my FUSE count is STILL 7 is because, from what I can understand from the link provided, if your on FW 6.0.0, any FW upgrade within 6.0.0 and 6.1.0 doesn't burn a fuse? So that would explain why I'm on still 7 and not 8? So I should be ok, as I want to avoid using AUTORCM altogether.

Now if my OFW was on 5.x.x, and I updated my Emunand to 6.x.x, a fuse will need to be burn, so the question is, will AUTORCM be required so no fuses will be burn? Or is Emunand environment contained? Cant find any confirmation on this info, I guess only way to find out is when FW 6.2.0 is all good and ready to go, update Emunand to 6.2.0 and see what happens in OFW and see if any fuses are burnt.

 

[Nickoy]

Hello Slamride. Thankyou for taking the time to give me your thoughts. I have taken it all on board and will be installing emunand now. Makes no sense to ignore this function. I will also be making plenty of back ups. As I learn I hope to be able to feed back to the community and help as you have helped me. All the best

 

[rahvin]

UPDATE:

So we managed to get it all working last night and the process Nickoy laid down is spot on;

1)Format the SD card to Fat32 - windows will not be able to do this, you will need a 3rd party softwear (I used this http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm)
2)Load sx os and then do a nand backup - (very important if things go wrong!)(no need for an activated license at this stage)
3)Copy nand backup on to computer for safe keeping
4)Install ChoiDujou (Game_Over did a fantastic guide on this https://team-xecuter.com/forums/threads/154987-How-to-Update-Firmware-on-a-Banned-Nintendo-Switch) make sure you follow it precisely.
5)Install 6.1.0 (we were already on FW 6.1, we were just missing the SD "drivers" so you can overwrite 6.1 with ChoiDujou 6.1) including exFAT firmware (important you select the exFAT option on ChoiDujou)
6)Format sd card back to exFAT (FAT32 doesn't support large file transfers, you can use standard windows format options to format to exFAT)
7) Copy all of your folders, boot files and licenses back over to the SD card
8) Load games and enjoy

Things to note;
Keep aeroplane mode on - no need to connect to wifi.
Make sure you have the "Nintendo" folder on the root of the SD card.
We activated the license through the TX website and just copied over the license.dat file once the SD card was formatted back to exFAT.

Overall it was a fairly smooth process. big thanks to all the guides and tutorials that have been made to make this process very simple and easy to do.

Hello, i think i have a very similar problem with my switch. Sxos doesnt recognize my 128gb sd (fat32 formatted) so it keeps prompting me to update to 6.2 (im on 6.1).

My problem is i cant load the sxos custom firmware because i think my sd card isnt supported (even while its already fat32 formatted). Opening album just boots me back to the main menu.

So my question is, What did you mean by saying to make sure there was a Nintendo folder at the root of the sd card? Will this help sxos recognize my sd card and not prompt an update?

 

[califrex]

Created an account to say thanks to you, Slam and Gameover for the info in this thread.

One question I had is: When the Switch reboots it goes back to OFW 4.1. Do you have to insert the dongle and use the jig to and boot to CFW (emunand) everytime the switch restarts/reboots?

For those who wish to have Emunand along side your unmodified OFW, I can confirm the following works.

I got my SX PRO on the 2nd round of shipments back in the day and I just recently got myself a Switch, normally I'm a day one purchase for new consoles, but I held out for the Switch.

Setup:
Switch on OFW 6.0.1 (with NO exFAT support)
128GB SD CARD
SX Pro

I searched all over and nothing I read gave me the answer I wanted, just snippets, so I gathered all the info I found and tried to piece everything together.

So basically I want to use my OFW for legit cart games and play online, and have Emunand for my dirty stuff. My main goal was to have my OFW as is (untouched with exFAT support) and want to setup and use Emunand for backups/homebrew/etc.
I was meaning to upgrade my OFW to 6.1.0 with exFAT support but I was too late when FW 6.2.0 dropped.

What these steps will get you is, you get to keep your OFW as is so you can play legit carts and go online without Ban (not confirmed as nothing is 100% safe) and your Emunand to FW 6.1.0 with exFAT support and staying OFFLINE.

1 - To start off with a clean slate, factory reset your Switch and go through and setup your Switch to the point where you are at the Switch's homes screen.
2 - Turn off Switch
3 - Format your SD CARD to FAT32, I recommend you get a minimum of 64GB, I'm using 128GB.
4 - Setup your SD CARD for booting into SX OS.
5 - Either use the built in SX OS's NAND backup or use other alternatives to backup your NAND, either way, it's going to take some time to make a backup. DONT SKIP THIS STEP.
6 - Once NAND backup has been completed, transfer you NAND backup to somewhere safe, delete the NAND backup on the SD CARD to free up space.
7 - Grab a copy of ChoiDujourNX and put it on the root of your SD CARD, we will need this later.
8 - Grab a copy of the OFW 6.1.0 and place the files in a folder on the SD CARD.
9 - Boot back into SX OS and create a EMUNAND, this will take a while.
10 - Once completed, boot into the Emunand, launch the Photo Album to confirm it's the Emunand by looking at the SX logo, it should say Emunand.
11 - From here, launch ChoiDujourNX.
12 - Navigate to the OFW 6.1.0 firmware and install, make sure you select exFAT.
13 - Now this is the part that got me confused the most, ChoiDujourNX will enabled AUTORCM but default. I could not find the answer to: Is AUTORCM required for Emunand to prevent burning an eFuse? The answer is NO, AUTORCM is NOT required, I'll explain later in my post.
14 - Once you updated the Emunand FW to 6.1.0, choose to shutdown the switch.
15 - Backup your SD CARD to your computer.
16 - Format your SD CARD to exFAT.
17 - Copy the SD CARD files back to your SD CARD.
18 - Put SD CARD back into your Switch.
19 - Boot into Emunand via the SX OS boot menu.
20 - Go to the Photo Album to make sure your in Emunand.
21 - Exit out of this menu and go to the settings menu and check your FW, if you done everything correctly, it should show FW 6.1.0.
22 - Congrats, your Emunand is now on 6.1.0 with exFAT support and also have your unmodified OFW.

Stay safe by staying OFFLINE in Emunand, of course nothing is 100% safe but by staying offline is the next best thing.

Now regarding ChoiDujourNX, do you require AUTORCM so you don't burn a efuse in Enumand?
From my personal experience, this DOES NOT apply to Emunand because the OFW doesn't know anything about your Emunand and what you've been up to.
As a test, I don't have AUTORCM enabled, I have booted into my OFW with and without my SD CARD a few times, and checked my FUSE and the count IS still 7, which is correct for 6.x.x FW.
I'm using the RCM Jig that came with the SX PRO package.
ADDED NOTES:
Regarding the above statement, after some investigation, if you read information about the Switch's FUSES HERE (Scroll down to the bottom of the page). I'm pretty sure the reason my FUSE count is STILL 7 is because, from what I can understand from the link provided, if your on FW 6.0.0, any FW upgrade within 6.0.0 and 6.1.0 doesn't burn a fuse, so that would explain why I'm on still 7 and not 8, so it could very well be that I should be ok with my OFW on 6.0.1 and don't have to worry about burning a fuse.

Not confirmed is, will you be banned if you use OFW to play legit carts and go online? I've very interested to find out, but not until FW 6.2.0 has been sorted out.
Now comes the decision, when FW 6.2.0 is all working with CFW/Emunand, do I use ChoiDujourNX to update and keep by eFuse intact in case I want to downgrade later. But in doing this you need AUTORCM enabled so you don't burn a eFuse.
I'm a bit on the fence with AUTORCM as could this be one of the triggers for a ban?

Hope this info helps out for those want to know or are in the same boat as me.

 

[imprezgc8]

Created an account to say thanks to you, Slam and Gameover for the info in this thread.

One question I had is: When the Switch reboots it goes back to OFW 4.1. Do you have to insert the dongle and use the jig to and boot to CFW (emunand) everytime the switch restarts/reboots?

Yes. Any time your battery dies or shutdown/restart the console. You could install autorcm to avoid having to use the jig each time, but you will need the dongle. Look into autorcm before installing as a lot of people say it drains their battery quicker. Also if the console loses charge while that is turned on it will take a while to charge so that you can boot back up again. If you don't mind using the jig and dongle each time then do not worry about autorcm.

 

[califrex]

Thanks for clarifying.

Some threads recommend to install autorcm as extra precaution to prevent burning fuses. As a result, I left it on when I installed cfw 6.1 via choidujournx.

My switch rarely goes out of my place so battery drain is a non issue.

 

[califrex]

Also, after reading some issues with sdcard corruption with exfat format, is the current recommendation now (12/27/18) to keep the Fat32 format? And just split xci/nsp files as needed?

 

[imprezgc8]

Also, after reading some issues with sdcard corruption with exfat format, is the current recommendation now (12/27/18) to keep the Fat32 format? And just split xci/nsp files as needed?

I know a lot of people who run retroarch for emulation us fat32 to avoid the corruption. I personally still use exfat. I had corruption happen once, but I am pretty sure it was because I did not close retroarch correctly. I just make sure to back my game saves up with checkpoint and also back the sd card up to my pc once in a while. I think as long as you don't let the battery die with apps still open ot just make sure to close them when you are done playing it should be fine. Just my opinion though. I don't honestly care to spend time splitting my files just to use fat32.