Hacking ChoiDujourNX didn't install exfat update correctly, need help

Doogie Boogie

Well-Known Member
Member
Joined
Jan 21, 2016
Messages
138
Reaction score
69
Trophies
0
Age
42
XP
371
Country
United States
I recently updated to 6.1.0 from 4.1.0 using ChoiDujourNX and applied the exfat update. I launched my CFW through the hekate payload and the switch booted without my CFW running. I also received an error that the switch needed to be updated due to not having microSDXC compatibility. I assume this is why my CFW didn't load because it couldn't read the card (I'm assuming).

What's the best way to fix this? Downgrade back to 4.1.0, format my SD to FAT32, and reapply the 6.1.0 update all together or can I just install the exfat update? Is it possible there is a different problem? Thanks for any help.

Also, I've had AutoRCM running so my fuses should not be burned so I can go back to my 4.1.0 NAND.
 
try to install again the exfat update. You need to format it back first to fat32 and do it again.
 
I launched my CFW through the hekate payload and the switch booted without my CFW running. I also received an error that the switch needed to be updated due to not having microSDXC compatibility. I assume this is why my CFW didn't load because it couldn't read the card (I'm assuming).

hekate doesn't use Nintendo's exFAT driver, it has it's own. So that assumption is wrong.
 
hekate doesn't use Nintendo's exFAT driver, it has it's own. So that assumption is wrong.
Good to know :) But how do we install/load the driver? Does it automatically doing it?
Sorry if that‘s a dump question but i only have experience with SX OS and there you only need the exFAT update for the switch firmware.
 
Good to know :) But how do we install/load the driver? Does it automatically doing it?
Sorry if that‘s a dump question but i only have experience with SX OS and there you only need the exFAT update for the switch firmware.

I think sx os has it's own exfat driver like hekate/atmosphere/etc, it's built in and can't be removed but it's only used for booting up.
 
Managed to figure out the problem on my own. It was the exfat update. Hetake was working fine, it was booting the CFW that was the issue. The exfat update wasn't installed. I formatted my SD back to FAT32, then reapplied the 6.1.0 update with exfat. Atmosphere was able to boot when my SD was FAT32 so it was possible to fix the problem that way without having to do something as inconvenient as rolling back the NAND or anything.
 
  • Like
Reactions: noX1609
I think sx os has it's own exfat driver like hekate/atmosphere/etc, it's built in and can't be removed but it's only used for booting up.
Ah ok got it. So it uses the Nintendo exFAT driver when booting into the os and just uses the own driver for the boot menu right?
 
Correct. If the console couldn't read the SD card it couldn't read the CFW files needed to boot. Hetake isn't dependent on the SD card because it's injected into the RCM before anything else loads. I figured that out the hard way, lol.
 

Site & Scene News

Popular threads in this forum