This guide is outdated, use this easier guide instead: guide, original thread: ChoiDujourNX

*************

Warning: Use at your own risk, using a wrong version of a game dump could prevent the console from booting.

Warning: Because we install the driver without ever requesting this from Nintendo, this could be detected if you go online and result in a ban.


Intro:

How to install the exFAT driver without updating you console.
I used the game dump "Penny.Punching.Princess.NSW-BigBlueBox" on my 3.0.2 Switch.
I'm assuming you know how FG works and how to send payloads to the console before proceeding.

There are two methods of installing this:
1, Stock: Installing it to the system like a cartridge would. This works on stock firmware but exFAT support would be lost after a system update.
2, CFW: When booting Horizon via hekate, a .kip1 file will be injected. The console's eMMC remains unaltered and will not have the driver loaded when booting normally and not via hekate.

Method 1, Stock:

Necessities:

- A console with firmware version 2.0 or higher (does not work on 1.0.0)
- A Game dump with an update on it that is the same version as the console (tested: trimmed xci works)
- Switch encryption keys (these can't be shared, Google 'nswroms' to find them)
- patch.zip: link
- TegraRcmGUI / TegraRcmSmash (TegraRcmGUI)
- memloader (https://switchtools.sshnuke.net/)
- HacDiskMount (https://switchtools.sshnuke.net/)

Steps:

step 1: Copy the contents of the sample directory of memloaderv1.zip to the root of your SD card.
step 2: Enter RCM using your prefered method: how-to-test-fusee-gelee.
step 3: Inject the memloader.bin payload that is located inside of memloaderv1.zip.
step 4: Select 'ums_emmc.ini' by navigating with the volume buttons and confirming with the power button.
step 5: open HacDiskMount as administrator and select 'Linux UMS disk 0':

Spoiler

step 6: Double click BCPKG2-1-Normal-Main and a window will pop-up:

Spoiler

step 7: Use the 'Start' button in the 'Dump to file' section to extract the partition.
step 8: (!) Create a backup of BCPKG2-1-Normal-Main.bin and store it somewhere safe.
step 9: Create a new directory and extract the contents of patch.zip into it.
step 10: Copy the game dump and BCPKG2-1-Normal-Main.bin to the same directory.
step 11: Create a file named keys.txt in the same directory.
step 12: Copy all of the Switch encryption keys to this file.

Spoiler

The keys.txt file should contain at least the following keys, replace the ... with the keys you found online.

master_key_00 = ...
master_key_01 = ...
master_key_02 = ...
master_key_03 = ...
master_key_04 = ...
aes_kek_generation_source = ...
aes_key_generation_source = ...
key_area_key_application_source = ...
header_kek_source = ...
header_key_source = ...

step 13: Inside of the directory we created, drag the game dump .xci onto the patch.bat file.
step 14: If the process executed successfully you should see something like this:

(The number of bytes can vary)
(Don't worry about the 'Failed to match key' warnings)
step 15: Go back to HacDiskMount and click on 'Browse' in the 'Restore from file' section and select BCPKG2-1-Normal-Main.bin that we just patched.
step 16: Close the pop-up window and doucle click on BCPKG2-2-Normal-Sub.
step 17: Repeat step 15 and restore the same BCPKG2-1-Normal-Main.bin file (optional, but advised).
step 18: Hold the power button on your Switch for 12 seconds to turn it off and then boot it again to see the results!

Results:

Before:

Spoiler

After:

Spoiler

Credits:

@Raugo for creating the original Spanish tutotial: link

Method 2, CFW:

Necessities:

- Everything from method 1, except: memloader and HacDiskMount
- sdfiles.zip (https://github.com/tumGER/SDFilesSwitch/releases)
- hekate (https://github.com/CTCaer/hekate/releases)

Steps:

step 1: Create a new directory and extract the contents of patch.zip into it.
step 2: Copy the game dump to the same directory.
step 3: Create a file named keys.txt in the same directory.
step 4: Copy all of the Switch encryption keys to this file.

Spoiler

The keys.txt file should contain at least the following keys, replace the ... with the keys you found online.

master_key_00 = ...
master_key_01 = ...
master_key_02 = ...
master_key_03 = ...
master_key_04 = ...
aes_kek_generation_source = ...
aes_key_generation_source = ...
key_area_key_application_source = ...
header_kek_source = ...
header_key_source = ...

step 6: Inside of the directory we created, drag the game dump .xci onto the patch-cfw.bat file.
step 7: If the process executed successfully you should see something like this:

step 8: Copy the file FS.kip1 that was just created in the 'out' directory, to the root of your SD card.
step 8: Copy the contents of sdfiles.zip to the root of your SD card.
step 9: On your SD card, open hekate_ipl.ini inside of a text editor.
step 10: Add the following line below each boot entry that you want to inject:

kip1=FS.kip1

A boot entry is a line that starts with [ and ends with ], for example:

[CFW]
kip1=modules/newfirm/loader.kip
kip1=modules/newfirm/sm.kip
kip1=FS.kip1

step 11: Put the SD card back into your Switch.
step 12: Enter RCM using your prefered method: how-to-test-fusee-gelee.
step 13: Inject the hekate.bin payload

After booting hekate and selecting either 'stock' or 'CFW' from the 'Launch firmware' section, the exFAT driver will be injected!

 

[chronoss]

where does this "patch.zip" come from? If it's from method 1, the link is inaccessible.

https://mega.nz/#!pZxACSSD!8JQxAxvLMrQBvW6F1t6BbEQ7aan8VIA9xDn3qe5p3IA

 

[Moko]

have tried method 1... now i got only a blue screen after switching on

Firmware was 4.1.0

 

[Clydefrosch]

have tried method 1... now i got only a blue screen after switching on

in that case, you must've made a mistake somewhere, maybe used the wrong game to patch BCPKG2-1-Normal-Main.bin

Can you still enter rcm?
If you kept a backup of the untouched file as the guide instructed, that way, you should be able to fix it by inserting the untouched file.

 

[Moko]

have restored the BCPKG2-1-Normal-Main.bin, now the switch is booting again
next try tomorrow

cant awaiting..and try it again
it works, thank you very much for the tutorial

 

[djricekcn]

I got it working I think? I used method 2 but when i reboot the Switch, it seems to lose the exfat support. only tried ofw and tried it twice.

 

[Darklinkreturns]

disregard this post

 

[riyyi]

I got it working I think? I used method 2 but when i reboot the Switch, it seems to lose the exfat support. only tried ofw and tried it twice.

That is correct, you will only get exFAT support when booting via hekate using the CFW method. Once Atmosphere is released, you will always want to boot via that anyways.

 

[comput3rus3r]

That is correct, you will only get exFAT support when booting via hekate using the CFW method. Once Atmosphere is released, you will always want to boot via that anyways.

this only works until you reboot?
NVM. I read all the comments before i read the OP.

 

[comput3rus3r]

I'm still confused. Does method 1 keep exfat driver after a reboot? Also it only looses it when you update system through Nintendo?

What's the difference between this tutorial and the one posted here
https://gbatemp.net/threads/how-to-...tch-console-on-any-ofw-without-update.505182/

 

[riyyi]

I'm still confused. Does method 1 keep exfat driver after a reboot? Also it only looses it when you update system through Nintendo?

What's the difference between this tutorial and the one posted here
https://gbatemp.net/threads/how-to-...tch-console-on-any-ofw-without-update.505182/

Correct.
My tutorial was posted first and isn't a huge bloated mess, only relevant information is posted. And the other tutorial doesn't explain the CFW method.

 

[djricekcn]

That is correct, you will only get exFAT support when booting via hekate using the CFW method. Once Atmosphere is released, you will always want to boot via that anyways.

Thank you for clarifying. If I ever need to, will the savedata under the same account read after the reboot on OFW from the previous boot?

 

[riyyi]

Thank you for clarifying. If I ever need to, will the savedata under the same account read after the reboot on OFW from the previous boot?

As far as I'm aware saves are stored on the internal eMMC storage, so after a reboot those will still work.

 

[Mat37]

Is there any game with the 5.0.1 update ? I tried to take only the F55A04978465EBF5666CA93E21B26DD2.nca which contains the 5.0.1 package2 (i think it's this one) and continuing with this but it got stuck on 'read package2' when booting hekate

 

[temper999]

Method 2 is working like charm for me.
Thx for the guide!

 

[0000ff]

Any chance of updating method 2 to work with tumGER's SDFiles25.zip? I get "failed to load firmware" when trying to use the config given for hekate_ipl.ini, including changing the file paths to match SDFiles25.zip directory layout.

I am able to get it to work using the very first version with "sdfiles.zip"

 

[kirby44]

So "Method 2" is temporary? I used the first one and it works pretty great.

 

[riyyi]

Any chance of updating method 2 to work with tumGER's SDFiles25.zip? I get "failed to load firmware" when trying to use the config given for hekate_ipl.ini, including changing the file paths to match SDFiles25.zip directory layout.

I am able to get it to work using the very first version with "sdfiles.zip"

It should already work, we are not modifying the contents of the zip in any way. Try to manually add this to the hekate_ipl.ini of SDFiles25.zip,

kip1=FS.kip1

below the [CFW] section.

Edit: SDFiles25.zip changed the directory structure of the .kip files, I updated method 2 to reflect this change.

So "Method 2" is temporary? I used the first one and it works pretty great.

Yes, because the RCM entrypoint is tethered and therefor hekate injecting the .kip1 file on boot, it will obviously not do this during a normal boot.

 

[Clydefrosch]

Is there any game with the 5.0.1 update ? I tried to take only the F55A04978465EBF5666CA93E21B26DD2.nca which contains the 5.0.1 package2 (i think it's this one) and continuing with this but it got stuck on 'read package2' when booting hekate

if you're at 5.0.1 you might as well just update normally and get exfat that way.

 

[Mat37]

if you're at 5.0.1 you might as well just update normally and get exfat that way.

That's why i did and i don't regret cause i can now profit of backup loading ^^

 

[0000ff]

It should already work, we are not modifying the contents of the zip in any way. Try to manually add this to the hekate_ipl.ini of SDFiles25.zip,

kip1=FS.kip1

below the [CFW] section.

Edit: SDFiles25.zip changed the directory structure of the .kip files, I updated method 2 to reflect this change.

I have tried these changes and I still get "failed to launch firmware". FS.kip1 is in the root dir

[CFW]
kip1=modules/newfirm/loader.kip
kip1=modules/newfirm/sm.kip
kip1=FS.kip1

cancel that- once I left that in the ini file exclusively, it worked as it should. thanks for you help!