ChoiDujourNX is an extremely straight-forward homebrew application that doesn't really require a tutorial on how to use. Just ensure that you are in EmuNAND when you launch the homebrew application. How to test that, well, I'm not really sure myself but I believe it automatically boots into EmuNAND once its configured.
i was gonna ask that so if you have emunand it will by default boot into it ? and i was told it's not linked so would like a theme change make it easy to tell
I try to play local wireless with smash ultimate but keeps saying version not right even though I've updated the sysfw and the game. Is there something about cfw that blocks it from connecting?
so how long did that clean nand back up take you ? i think you said you were on hour 13 yesterday. im asking cause i need to do a backup to
I just got my switch a few days ago (4.1.0 unpatched) I did NAND backup and keys dump on a 128gb fat32 card but was not able to figure out how to do a biskeys dump,(i am very new at switch hacking) I continued without the biskeys dump after reading 2 guides that mentioned restoring NAND did not require them. I tried out the lastest build of ReiNX and tried a few game dumps to see how it works. I decided to just buy a SX OS Pro so i would like to start over fresh.
Can I start off fresh with a system restore of my backed up NAND,then factory reset,and format sd card or did i need biskeys to fully restore and now im screwed?
Can I start off fresh with a system restore of my backed up NAND,then factory reset,and format sd card or did i need biskeys to fully restore and now im screwed?
Last edited by Outlawbiker,
I believe it does boot into EmuNAND by default and I also just remembered the easy trick to identifying SysNAND vs. EmuNAND is by setting a different theme on each.
Is your smash on version 1.2.1?
You can restore your NAND backup, meaning boot0/boot1 as well as rawnand, but it is pointless to perform a factory reset if you are going to be restoring your NAND since a NAND backup wipes the system a lot more clean than a factory reset.
The biskeys are only needed if you want to mount the NAND with hacdiskmount.
Thank you for the help, once i get back to "stock" can i or should i add exfat support via choirdjorNX then do a new NAND backup? or will exfat support "stick" to the system?
I have seen a few posts and have the same related question?
Using sx pro, I want to update emunand with choidujourNX, BUT how do I know that I am actually updating the emunand and not the sysnand.....or does choidournx do it automatically?
Using sx pro, I want to update emunand with choidujourNX, BUT how do I know that I am actually updating the emunand and not the sysnand.....or does choidournx do it automatically?
If your console didn't support exFAT before the NAND backup, you will lose it once you restore your NAND. You can add exFAT support with ChoiDujourNX if you want. Making another NAND backup after adding exFAT support is also another optional step.
Unfortunately there's no official way to differentiate between the two. This is why its recommended to set a different theme for SysNAND and EmuNAND in order for the user to not get confused.
Hi, I would really appreciate some advice. I've managed to pick up an unpatched switch today and plan on ordering the sx pro as soon as I can. So...where's best to order the sx pro from in the UK? and can I update the firmware on the switch to the current firmware now and still run the SX Pro? The switch is currently on firmware 3.0.1
Their website has a list of resellers you can choose from.
As for the firmware, since the exploit is hardware-based, SX Pro will work irregardless of firmware. However if you update before you get the SX Pro, you will burn fuses which will prevent you from downgrading back to your original firmware. Downgrading is important if there is a future exploit released such as a hypothetical untethered coldboot hack that only works on certain firmwares. If you want to update but preserve your fuses, I recommend using the homebrew application ChoiDujourNX.
And before you use ChoiDujourNX, you should do a complete NAND dump. That means dump boot0/boot1 as well as the eMMC raw GPP or rawnand. While SX OS has their own NAND dumping function, I advise you to use Hekate instead. Hekate can verify the dump which SX OS cannot do meaning SX OS may dump something corrupt while Hekate will ensure any dumps are proper once they pass verification.
Hello 
Long time lurker and have benefited from reading he forums a great deal.
Never thought I'd have to create an account to beg for help but here we are
Current system:
6.1 running ReinX.
AutoRCM enabled.
6.2 has been downloaded but not installed.
Nag is appearing every time I start a game, and 'gag-order' app doesn't seem to think there are any nags going on.
I have a NAND dump, but it's ancient.
In an effort to stop the nags, I booted into maintenance mode, while injecting ReinX via TegraRcmGUI.
I was holding the volume buttons before and during injection.
I then turned off the console, reconnected, and pushed the payload again.
ReinX splash screen appears, then disappears (as normal) but then nothing. Just black... No Nintendo logo, nothing.
TegraRcmGUI shows the green 'RCM OK' icon immediately after the ReinX splash screen.
I have tried pretty much every button combo I can think of with no luck.
I can't figure this out. Am I stuck in maintenance mode? Is there some way I can get more info on what's happening?
I've searched for the last 20-30 minutes or so but perhaps I'm searching poorly as I can't find any recent examples of this combination.
Many hopeful thanks in advance!
Long time lurker and have benefited from reading he forums a great deal.
Never thought I'd have to create an account to beg for help but here we are
Current system:
6.1 running ReinX.
AutoRCM enabled.
6.2 has been downloaded but not installed.
Nag is appearing every time I start a game, and 'gag-order' app doesn't seem to think there are any nags going on.
I have a NAND dump, but it's ancient.
In an effort to stop the nags, I booted into maintenance mode, while injecting ReinX via TegraRcmGUI.
I was holding the volume buttons before and during injection.
I then turned off the console, reconnected, and pushed the payload again.
ReinX splash screen appears, then disappears (as normal) but then nothing. Just black... No Nintendo logo, nothing.
TegraRcmGUI shows the green 'RCM OK' icon immediately after the ReinX splash screen.
I have tried pretty much every button combo I can think of with no luck.
I can't figure this out. Am I stuck in maintenance mode? Is there some way I can get more info on what's happening?
I've searched for the last 20-30 minutes or so but perhaps I'm searching poorly as I can't find any recent examples of this combination.
Many hopeful thanks in advance!
Last edited by SirDerpsalot,
Thank you for taking the time to help. I'll be honest, I'm not particularly clued up on this sort of thing. I think I'd struggle to follow the ChoiDujourNX guide, without worrying I was about to brick the thing. I did the Wii u hack before, I know it's easy but I was a clammy panicking mess throughout. Basically the less involved I get in the process the better the outcome will be. With this in mind...
What's so bad about burning fuses? If I update to new firmware now and then start using SX OS I wouldn't be able to go back to my original firmware but I would be able to create a nand through SXOS (I know you said henkate is the better way but I'd prob go for the easiest option) that I could always go back to for whatever reason?
Also, if I lose the jig thing or the SX OS loader, can I just boot into the official firmware and still run any games I have bought from cartridge? What happens if in a year's time a game comes out and I've been banned from receiving firmware updates by Nintendo and an update is required to run the new game. Will new firmware install from game cartridges or is this also banned?
What's so bad about burning fuses? If I update to new firmware now and then start using SX OS I wouldn't be able to go back to my original firmware but I would be able to create a nand through SXOS (I know you said henkate is the better way but I'd prob go for the easiest option) that I could always go back to for whatever reason?
Also, if I lose the jig thing or the SX OS loader, can I just boot into the official firmware and still run any games I have bought from cartridge? What happens if in a year's time a game comes out and I've been banned from receiving firmware updates by Nintendo and an update is required to run the new game. Will new firmware install from game cartridges or is this also banned?
ChoiDujourNX is a homebrew application. It doesn't even need a guide. That point is further lessened by the fact that all of the steps in ChoiDujourNX are straight-forward and coupled with a really good UI.
You can always restore a NAND regardless of your fuses however if you have more fuses burnt than the firmware of the NAND dump, then you can't boot it normally; you would have to boot it through RCM and use a bootloader that bypasses the fuse check.
Retail cartridges can be booted in CFW or OFW.
If you're banned, you can always download game updates in .NSP format and install them with your CFW or a homebrew application such as Goldleaf/Tinfoil.
Don't think the current ReiNX supports maintenance mode. Just download SX OS, put the boot.dat on your SD card's root, send the SX Loader, choose either CFW/OFW, and hold volume - and +; you should be able boot into maintenance mode that way.Hello
Long time lurker and have benefited from reading he forums a great deal.
Never thought I'd have to create an account to beg for help but here we are
Current system:
6.1 running ReinX.
AutoRCM enabled.
6.2 has been downloaded but not installed.
Nag is appearing every time I start a game, and 'gag-order' app doesn't seem to think there are any nags going on.
I have a NAND dump, but it's ancient.
In an effort to stop the nags, I booted into maintenance mode, while injecting ReinX via TegraRcmGUI.
I was holding the volume buttons before and during injection.
I then turned off the console, reconnected, and pushed the payload again.
ReinX splash screen appears, then disappears (as normal) but then nothing. Just black... No Nintendo logo, nothing.
TegraRcmGUI shows the green 'RCM OK' icon immediately after the ReinX splash screen.
I have tried pretty much every button combo I can think of with no luck.
I can't figure this out. Am I stuck in maintenance mode? Is there some way I can get more info on what's happening?
I've searched for the last 20-30 minutes or so but perhaps I'm searching poorly as I can't find any recent examples of this combination.
Many hopeful thanks in advance!
Because if you downgrade with burnt fuses, you can no longer boot the console up normally; you are stuck booting through RCM to bypass the fuse check. The whole purpose of downgrading is in case a future exploit is released that doesn't make use of RCM. If you have to use RCM to utilize that exploit, it defeats the purpose of downgrading since you have to now use 2 exploits to boot your console with burnt fuses.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
RedColoredStars:
There is an actual trailer with footage too. lol. Going to watch it tonight. Grabbed it from... a place. -
-
@
SylverReZ:
@Psionic Roshambo, JonTron's back yet again until he disappears into the void for another 6 or so months.+1 -
-
-
