EMUNand upgrade has upgraded both CFW and OFW

[ace9094]

Hi All,

I was running OFW 5.0.1 and wanted to create a CFW EMUNand 6.2.0 while staying on OFW 5.0.1 - I followed the guide for updating banned consoles by using ChoidujourNX v1.0.1 - When the update completed both the EMU Nand and the switch OFW have updated to 6.2.0 leaving me a little confused.

Here is what I done:

1) Created Nand Back Up 5.0.1 (copied to PC but left on SD Card too)
2) Created Emu Nand 5.0.1 and booted CFW to Emu Nand (had gold box in SX OS saying Emu Nand Enabled)
3) Followed guide to the letter using ChoiDujourNX to install 6.2.0 choosing 6.2.0 exFat version
4) Guide stated it would reboot RCM mode, however mine booted to OFW and was 6.2.0 in settings

I followed this guide: https://team-xecuter.com/forums/thr...on-a-Banned-Nintendo-Switch-with-ChoiDujourNX

I rebooted to CFW and this was also 6.2.0, now I have no idea if I have burned fuses or not as it rebooted to OFW and not AutoRCA. I am unsure if I can now downgrade to 5.0.1 or not in case I get my sons console banned for a fuse mismatch etc. The CFW is still bootable running 6.2.0 the as OFW and working fine. I seen on youtube you can use briccmii to check burnt fuses but its a little confusing (no fuse pun intended)

Is it still possible to downgrade the OFW back to 5.0.1 using the NAND Back Up without getting banned ?

Thanks
ace

 

[anonymoose]

Hi All,

I was running OFW 5.0.1 and wanted to create a CFW EMUNand 6.2.0 while staying on OFW 5.0.1 - I followed the guide for updating banned consoles by using ChoidujourNX v1.0.1 - When the update completed both the EMU Nand and the switch OFW have updated to 6.2.0 leaving me a little confused.

Here is what I done:

1) Created Nand Back Up 5.0.1 (copied to PC but left on SD Card too)
2) Created Emu Nand 5.0.1 and booted CFW to Emu Nand (had gold box in SX OS saying Emu Nand Enabled)
3) Followed guide to the letter using ChoiDujourNX to install 6.2.0 choosing 6.2.0 exFat version
4) Guide stated it would reboot RCM mode, however mine booted to OFW and was 6.2.0 in settings

I followed this guide: https://team-xecuter.com/forums/thr...on-a-Banned-Nintendo-Switch-with-ChoiDujourNX

I rebooted to CFW and this was also 6.2.0, now I have no idea if I have burned fuses or not as it rebooted to OFW and not AutoRCA. I am unsure if I can now downgrade to 5.0.1 or not in case I get my sons console banned for a fuse mismatch etc. The CFW is still bootable running 6.2.0 the as OFW and working fine. I seen on youtube you can use briccmii to check burnt fuses but its a little confusing (no fuse pun intended)

Is it still possible to downgrade the OFW back to 5.0.1 using the NAND Back Up without getting banned ?

Thanks
ace

I had to do the same thing as you (though I am on OFW 3.0.1 as opposed to your 5.0.1) and I was worried, so I used my smartphone to video-record the whole process as I went, so that I could at least back you up if the same thing happened to me. For me though, everything worked perfectly fine and I have video confirmation.

Not to cast doubt, but I think you might have made a mistake at some step. It really should be impossible for Choi to update the OFW while in Emunand. The only thing I can think is that you somehow launched CFW with Emunand Disabled, before you ran Choi. If that is the case, there's no going back to earlier firmware.

 

[ace9094]

I had to do the same thing as you (though I am on OFW 3.0.1 as opposed to your 5.0.1) and I was worried, so I used my smartphone to video-record the whole process as I went, so that I could at least back you up if the same thing happened to me. For me though, everything worked perfectly fine and I have video confirmation.

Not to cast doubt, but I think you might have made a mistake at some step. It really should be impossible for Choi to update the OFW while in Emunand. The only thing I can think is that you somehow launched CFW with Emunand Disabled, before you ran Choi. If that is the case, there's no going back to earlier firmware.

Thanks for replying,

Maybe you are indeed correct and I made a mistake, but the goldb box 100% said Emunand enabled, but I may of messed up somewhere else. Either way my son wants to play Fortnite so I guess I would of needed to go OFW 6.2.0 anyway to avoid a ban.

Thanks agian
ace

 

[SephiroT]

I'm helping with EmuNAND and CFW updates in my polish community and for last 10 upgraded Switches none of such thing happened.

 

[ace9094]

I'm helping with EmuNAND and CFW updates in my polish community and for last 10 upgraded Switches none of such thing happened.

Must be something I have done wrong... Either way, its not the end of the world to be honest I still have a working CFW. I have the full back up of 5.0.1. Maybe I should also make a full backup of 6.2.0 OFW.

 

[imprezgc8]

Must be something I have done wrong... Either way, its not the end of the world to be honest I still have a working CFW. I have the full back up of 5.0.1. Maybe I should also make a full backup of 6.2.0 OFW.

100% make sure you have a sysnand backup of 6.2 and keep the 5.0.1 as well just in case. Downgrading is not ever recommend unless absolutely necessary for the sysnand. Downgrading emunand is not as big a deal because you can always wipe it off the SD card and start fresh.

It's hard to say what happened, but if you boot to the SX bootloader - click official firmware and check the settings, does it say that it is 6.2? If you boot to OFW firmware through the bootloader it will ignore fuse checks. Just one way to check the firmware. You can also boot up hekate and check how many fuses are burned there if you just want to know. Like you said though, if your son wants to play online you will need OFW 6.2 anyways, however you will need it through the official nintendo update, not Choi. Just keep that in mind.

 

[ace9094]

100% make sure you have a sysnand backup of 6.2 and keep the 5.0.1 as well just in case.

YEP Got those

It's hard to say what happened, but if you boot to the SX bootloader - click official firmware and check the settings, does it say that it is 6.2?

I will double check again, (read anoymoose's post wrong)

Like you said though, if your son wants to play online you will need OFW 6.2 anyways, however you will need it through the official nintendo update, not Choi. Just keep that in mind.

OH DAMN... I didn't think of that...

If you boot to OFW firmware through the bootloader it will ignore fuse checks. Just one way to check the firmware.

I wonder if it will be possible to Downgrade to 6.1 using Choi then boot to OFW via the bootloader skipping the fuse checks, then update to OFW 6.2 via the official nintendo update ?? Hopefully then he can play online.
If not then better keep him offline until the next official firmware release (providing it still works with SX OS) just in case

You can also boot up hekate and check how many fuses are burned there if you just want to know.

I will check it and post back. I had a look online about fuses, the wiki page was useful, telling you what fuses were burnt with each OFW, I was just a little confused on which app to use for checking.

Thanks again my friend, appreciated
ace

 

[josete2k]

Upgrade your system from Nintendo's servers with fuses patches running isn't a good idea...

If you want online burn your efuses.

 

[ace9094]

Upgrade your system from Nintendo's servers with fuses patches running isn't a good idea...

If you want online burn your efuses.
.

Hi Josete2k,

My issue is how do I get to OFW 6.2 or higher without Nintendo knowing ?
I have managed to upgraded using ChoidujourNX v1.0.1 ? As Impretzgc8 pointed out, surely Nintendo will know as soon as I try to update officially.

If I restore the NAND Back up I made back to 5.1.0 will Nintendo know if I then upgrade to OFW 6.2.0 using Nintendo Servers?

To be honest, the Switch is used so I do not even know if it is banned

 

[slamride]

Accidentally did the OFW update myself by not making sure I was on Emunand.
Changed the themes to white for OFW and Black for Emunand and now I know at boot which one I'm in

 

[imprezgc8]

Accidentally did the OFW update myself by not making sure I was on Emunand.
Changed the themes to white for OFW and Black for Emunand and now I know at boot which one I'm in

That's a great idea actually haha. I run a custom theme in my CFW, but for people who don't want to do that they should definitely do this.

Hi Josete2k,

My issue is how do I get to OFW 6.2 or higher without Nintendo knowing ?
I have managed to upgraded using ChoidujourNX v1.0.1 ? As Impretzgc8 pointed out, surely Nintendo will know as soon as I try to update officially.

If I restore the NAND Back up I made back to 5.1.0 will Nintendo know if I then upgrade to OFW 6.2.0 using Nintendo Servers?

To be honest, the Switch is used so I do not even know if it is banned

If your 5.1 nand backup is clean meaning you never booted CFW before making it and you know 100% that you have not burned your fuses you should not have any issues downgrading back to 5.1 from your backup. The fuses part being more important than it being clean of course. I would verify your fuse count using Hekate before attempting as it will be very difficult to fix if your fuses did get burned. Also make sure to make a new nand back up of 6.2. Sorry if I said that already, but it's very important if you are going to attempt to downgrade.