Hacking How to update Firmware in SX OS 2.0 Emunand offline

[BGR]

On the new SX OS 2.0 Emunand what would be the best way to update this to 5.1.0 or 6.0 whilst leaving OFW at 4.1.0? My switch has been in airplane mode since before SX OS installation so would like to do offline if at all possible. If on emunand I take it no efuses are burnt when upgrading emunand firmware and only if OFW updated? Also I take it if I update emunand firmware offline then exfat will still work post-update?

 

[rrocha]

I am on the exact same situation as you. So here are the steps I took to bring my emuNAND to fw 6.0.0:

Requirements: Latest build of ChoiDujourNX installed into your homebrew dir and a copy of N's v6.0.0 FW files (google for multiple ways to get them)

1. boot on your OFW and change the theme to the opposite of your preference (if you prefer dark, change it to white or vice-versa). This will help you to visually identify which of the fw versions you're booting from now on.
2. Boot SX OS while keeping the vol+ pressed so you can get into SXOS menu
3. Setup emuNAND
4. Make sure EmuNAND enabled is shown on the SX OS main menu and click "Boot custom FW"
5. Make sure you boot into emuNAND version of 4.1.0 (as it was just copied from your OFW). This can be confirmed by going into the album and checking if the SXOS logo states "SX OS V2.0 EMUNAND". If it says just "SX OS V2.0", you're on sysNAND. Reboot to SX OS menu with long-press Vol+ and go back to the beginning of this step!
6. Go into the settings and change the theme to your preference. Now we can always identify which one is booting since you'll have te visual queue
7. go into homebrew, run ChoiDujourNX, select your NX6 fw folder, select exfat or no-exfat (depending on your taste) and proceed.
8. When finished, you'll be prompted to reboot. Even with SXOS running, doing so will reboot you to your OFW 4.1.0. You'll be able to easily spot this as you'll see the old theme showing up -> This is OK. Just long-press power until you get to the power menu and power off your console
9. Boot SXOS again with your jig+dongle/px/phone/whatever

You should now be on 6.0.0 emuNAND while your 4.1.0 is preserved together with your fuses. This can be confirmed if you boot Hekate and check that you still retain 5 burnt fuses instead of 7
Bonus on top of this, if you go back and boot the OFW 4.1.0, the card slot is still usable.

 

[BGR]

I am on the exact same situation as you. So here are the steps I took to bring my emuNAND to fw 6.0.0:

Requirements: Latest build of ChoiDujourNX installed into your homebrew dir and a copy of N's v6.0.0 FW files (google for multiple ways to get them)

1. boot on your OFW and change the theme to the opposite of your preference (if you prefer dark, change it to white or vice-versa). This will help you to visually identify which of the fw versions you're booting from now on.
2. Boot SX OS while keeping the vol+ pressed so you can get into SXOS menu
3. Setup emuNAND
4. Make sure you boot into emuNAND version of 4.1.0 (as it was just copied from your OFW). This can be confirmed by going into the album and checking if the SXOS logo states "2.0 EMUNAND"
5. Go into the settings and change the theme to your preference. Now we can always identify which one is booting since you'll have te visual queue
6. go into homebrew, run ChoiDujourNX, select your NX6 fw folder, select exfat or no-exfat (depending on your taste) and proceed.
7. When finished, you'll be prompted to reboot. Even with SXOS running, doing so will reboot you to your OFW 4.1.0. You'll be able to easily spot this as you'll see the old theme showing up -> This is OK. Just long-press power until you get to the power menu and power off your console
8. Boot SXOS again with your jig+dongle/px/phone/whatever

You should now be on 6.0.0 emuNAND while your 4.1.0 is preserved together with your fuses. This can be confirmed if you boot Hekate and check that you still retain 5 burnt fuses instead of 7
Bonus on top of this, if you go back and boot the OFW 4.1.0, the card slot is still usable.

Thanks alot for this. Great idea with the theme also

 

[comput3rus3r]

On the new SX OS 2.0 Emunand what would be the best way to update this to 5.1.0 or 6.0 whilst leaving OFW at 4.1.0? My switch has been in airplane mode since before SX OS installation so would like to do offline if at all possible. If on emunand I take it no efuses are burnt when upgrading emunand firmware and only if OFW updated? Also I take it if I update emunand firmware offline then exfat will still work post-update?

wouldn't the opposite make more sense? I mean why are you trying to update your hacked firmware to latest if that's the one that's going to play offline? Shouldn't you update your OFW to latest for online play and keep your hacked FW low for future hacking needs?

 

[Deleted User]

wouldn't the opposite make more sense? I mean why are you trying to update your hacked firmware to latest if that's the one that's going to play offline? Shouldn't you update your OFW to latest for online play and keep your hacked FW low for future hacking needs?

thats the best way for the "waiter fraction"
those people like to stay as low as possible in case a coldboot exploit will be made for lower versions (especially hackers said there might be one for up to 4.1...)


i prefer your way though...^^

 

[rrocha]

thats the best way for the "waiter fraction"
those people like to stay as low as possible in case a coldboot exploit will be made for lower versions (especially hackers said there might be one for up to 4.1...)


i prefer your way though...^^

Exactly this! Keeping my Switch on the lowest possible (shipped with 4.1.0) and just play the waiting game. I virtually banned myself since day 1 as this switch never see the glory of a simple wifi connection. Having emuNAND on v6.0.0 allows me to play every released game, update and DLC. But this only works if you don't care about online.

One extra thing I intend to do is to repeat the process but right after I do a NAND restore. Since I did the backup right after first boot, I will retain the console in perfect mint condition with the only two changes being the BOOT1 change to allow the emuNAND and the NANDx.bin files within the user partition. Since I don't intend on booting into OFW for the time-being and Nintendo certainly didn't had NANDx.bin file search and flag code on 4.1.0 (although BOOT1 integrity check might be there already), I believe I'll leave my console as vanilla as it can get while still allowing me to have all the latest and greatest content making the wait for a better exploit much enjoyable.

 

[z1010]

Exactly this! Keeping my Switch on the lowest possible (shipped with 4.1.0) and just play the waiting game. I virtually banned myself since day 1 as this switch never see the glory of a simple wifi connection. Having emuNAND on v6.0.0 allows me to play every released game, update and DLC. But this only works if you don't care about online.

One extra thing I intend to do is to repeat the process but right after I do a NAND restore. Since I did the backup right after first boot, I will retain the console in perfect mint condition with the only two changes being the BOOT1 change to allow the emuNAND and the NANDx.bin files within the user partition. Since I don't intend on booting into OFW for the time-being and Nintendo certainly didn't had NANDx.bin file search and flag code on 4.1.0 (although BOOT1 integrity check might be there already), I believe I'll leave my console as vanilla as it can get while still allowing me to have all the latest and greatest content making the wait for a better exploit much enjoyable.

If your not going online just update to 6.0 without burning fuses and then you can always just flash your 4.1 NAND back if you ever want to..

 

[BGR]

If your not going online just update to 6.0 without burning fuses and then you can always just flash your 4.1 NAND back if you ever want to..

Wouldn't you need autorcm turned on though with the old way? This new way doesn't require that I dont think so can just power down normally via the menu.

 

[porto]

I am on the exact same situation as you. So here are the steps I took to bring my emuNAND to fw 6.0.0:

Requirements: Latest build of ChoiDujourNX installed into your homebrew dir and a copy of N's v6.0.0 FW files (google for multiple ways to get them)

1. boot on your OFW and change the theme to the opposite of your preference (if you prefer dark, change it to white or vice-versa). This will help you to visually identify which of the fw versions you're booting from now on.
2. Boot SX OS while keeping the vol+ pressed so you can get into SXOS menu
3. Setup emuNAND
4. Make sure you boot into emuNAND version of 4.1.0 (as it was just copied from your OFW). This can be confirmed by going into the album and checking if the SXOS logo states "2.0 EMUNAND"
5. Go into the settings and change the theme to your preference. Now we can always identify which one is booting since you'll have te visual queue
6. go into homebrew, run ChoiDujourNX, select your NX6 fw folder, select exfat or no-exfat (depending on your taste) and proceed.
7. When finished, you'll be prompted to reboot. Even with SXOS running, doing so will reboot you to your OFW 4.1.0. You'll be able to easily spot this as you'll see the old theme showing up -> This is OK. Just long-press power until you get to the power menu and power off your console
8. Boot SXOS again with your jig+dongle/px/phone/whatever

You should now be on 6.0.0 emuNAND while your 4.1.0 is preserved together with your fuses. This can be confirmed if you boot Hekate and check that you still retain 5 burnt fuses instead of 7
Bonus on top of this, if you go back and boot the OFW 4.1.0, the card slot is still usable.

@rrocha

Great "HOW TO"
I am now waiting for the SX OS 2.0 to be compatible with my FW 3.0.0
May be a new SX OS 2.1

 

[rrocha]

If your not going online just update to 6.0 without burning fuses and then you can always just flash your 4.1 NAND back if you ever want to..

Forgot to mention that I don't like or use the auto-RCM feature. Having a kid a around and him being able to simply powering on the console, popping in a cartridge and play that specific game with no more gimmicks gives me peace of mind

 

[GeraltOfRivia]

First of all, thanx a lot for your help and explanation, really appreciate! This is, in my opinion, the best way to use the shadow nand: ofw kept low and second nand updated to enjoy latest contents. choidujourNx is one of the greatest tool ever created, so simple and essential for the hacking scene. I wanted to know how autoRCM is working if we choose this scenario, should it be mandatory to keep our fuse unburned, isn't it? We must boot with something that bypass fuse check to prevent fuses from burning but I heard many many people complaining about autoRCM not working with sx os 2.0 ; so, what can we do? Thanks for your time

 

[oleg77]

From what I understand, there's no fuse check from the 'emuNAND' so even if you upgraded this emuNAND to 6.0, the only fusecheck you could get is from OFW (if or when you boot it), and as the fuses you burned are those related to OFW (stock 4.1 for example), there should be no issue. You don't need autoRCM then (with this emuNAND method).

 

[GeraltOfRivia]

Thanks Mr. Oleg77! But are you sure? If this is correct, that would be a fantastic feature!! I am on 4.10 ofmw too, and I would like to update the shadow nand to latest firmware to enjoy newest contents.when choidujourNx finish the updating process, autoRCM is enabled by default so, I have to untick the enabled option and let the sistem reboot as usual? Please @rrocha could you please explain better this passage?Do You confirm there is no fuse check with the "emunand" option and my fuse will remain unburned if I use choidujourNx without autoRCM? Thank you @oleg77 and @rrocha

 

[rrocha]

Thanks Mr. Oleg77! But are you sure? If this is correct, that would be a fantastic feature!! I am on 4.10 ofmw too, and I would like to update the shadow nand to latest firmware to enjoy newest contents.when choidujourNx finish the updating process, autoRCM is enabled by default so, I have to untick the enabled option and let the sistem reboot as usual? Please @rrocha could you please explain better this passage?Do You confirm there is no fuse check with the "emunand" option and my fuse will remain unburned if I use choidujourNx without autoRCM? Thank you @oleg77 and @rrocha

Although I had autoRCM selected when I used ChoiDujourNX, BOOT0 was not affected by it so the autoRCM was never installed on the emuNAND. I did check the fuses and only 5 are burnt (4.1.0) so it's safe

 

[GeraltOfRivia]

Thank you very much for your help and support @rrocha !

 

[r6tro]

@rrocha

Great "HOW TO"
I am now waiting for the SX OS 2.0 to be compatible with my FW 3.0.0
May be a new SX OS 2.1

i am on 3.0.1 and i just tested emunand and it works.

tutorial:

- on 3.0.1; use choidujournx to update to 6.0.0
- boot sx os and create emunand
- exit
- on original-nand downgrade back to 3.0.1

done!
- original-nand: 3.0.1, emunand: 6.0.0

 

[porto]

i am on 3.0.1 and i just tested emunand and it works.

tutorial:

- on 3.0.1; use choidujournx to update to 6.0.0
- boot sx os and create emunand
- exit
- on original-nand downgrade back to 3.0.1

done!
- original-nand: 3.0.1, emunand: 6.0.0

Thanks r6tro for you help,
Very good method with a few more steps to follow
TX will make compatible its SX OS 2.0 with lowers firmwares (3.0.0, 3.0.1 ...) or it is not possible ??

 

[r6tro]

Thanks r6tro for you help,
Very good method with a few more steps to follow
TX will make compatible its SX OS 2.0 with lowers firmwares (3.0.0, 3.0.1 ...) or it is not possible ??

maybe sx os 2.1 ;p

 

[CreativeMan]

Has anyone confirmed @rrocha tutorial working ? It's known ChoidujourNX has issues with SX OS, because of some restrictions on debugging iirc, and I can't myself manage to update that way (error thrown midway of setup).

 

[r6tro]

Has anyone confirmed @rrocha tutorial working ? It's known ChoidujourNX has issues with SX OS, because of some restrictions on debugging iirc, and I can't myself manage to update that way (error thrown midway of setup).

confirmed it works, tried on 3.0.1 with a few additional steps