Some questions before downgrading

[Pingoo]

I hear you on feeling a bit "tricked" since it advertises it works on every firmware. Similar to you, I purchased SX OS when my Switch was already on 7.0. That said, downgrading to 6.2 was actually a lot easier than I expected and worked flawlessly for me. Maybe I got lucky.

So now I'm enjoying SX OS which is completely worth it in my opinion b/c of emunand and SX OS is great. I'm personally glad I did the downgrade so I can enjoy SX OS now instead of just refreshing these forums every few hours.

Having received my SX PRO after the 7.0 update, I wanted to try this solution, starting by making a backup of my SYSNAND with SX OS before any manipulation.
I then did the following to return to 6.2:

• Downgrade in 6.2 with ChoidujourNX,
• Creation of an EMUNAND with SX OS,
• and finally Restore my Backup.

I did everything twice, and the result is always the same: when I start my CFW with EMUNAND 6.2, the switch hangs on a black screen!

since that, I saw this message:

If you still want to downgrade that's totally up to you. After you do the downgrade you will need to reinstall the 6.2 update with Choi overtop of itself to correct the boot 0/1 issues allowing you to use SX OS CFW again.

As for emunand you cannot downgrade that as far as I know since Atmosphere does not support emunand. If you already have an emunand on 6.2 than you should be able to just boot SX with the 2.5.3 update. If not, to create one you would need to downgrade first, reinstall the 6.2 update and then create emunand.

As I understand it, we have to update to 6.2 after downgrading to 6.2 ?!?
What is the principle and is it because of this that my EMUNAND does not work ?
What is the method for doing this ? Twice ChoiNX ? must we reboot between the two ?

Thank you for the explanations ;-)

 

[josete2k]

Having received my SX PRO after the 7.0 update, I wanted to try this solution, starting by making a backup of my SYSNAND with SX OS before any manipulation.
I then did the following to return to 6.2:

• Downgrade in 6.2 with ChoidujourNX,
• Creation of an EMUNAND with SX OS,
• and finally Restore my Backup.

I did everything twice, and the result is always the same: when I start my CFW with EMUNAND 6.2, the switch hangs on a black screen!

since that, I saw this message:


As I understand it, we have to update to 6.2 after downgrading to 6.2 ?!?
What is the principle and is it because of this that my EMUNAND does not work ?
What is the method for doing this ? Twice ChoiNX ? must we reboot between the two ?

Thank you for the explanations ;-)

Try to downgrade to 6.1.0, create emunand and check if it works.

Once you have your emunand working you can upgrade to 6.2.0 with choidujournx and restore your sysnand with your backup.

 

[imprezgc8]

Did you install 6.2 over itself after you downgraded before creating the emunand?

Downgrading causing issues with the boot0/1 of the nand which causes issues booting SX and needs to be installed over itself to fix it. Make sure you choose exFAT or you could have issues with your SD after.

 

[flamesdragon]

How to install 6.2 over itself? Thanks

 

[imprezgc8]

How to install 6.2 over itself? Thanks

Yes, if you downgrade using Choi you need to install 6.2 over itself for SX to work again as mentioned above.

 

[flamesdragon]

But how do I do that? I use Choi again to install 6.2 over itself?

 

[MacD]

Jesus...

I was thinking about being impatient and trying a downgrade...

...until I read this thread.

My patience for 7.0.0 support just went straight back up again lol !!

 

[ceycey]

Jesus...

I was thinking about being impatient and trying a downgrade...

...until I read this thread.

My patience for 7.0.0 support just went straight back up again lol !!

I am new to Switch CFW and for me it worked perfectly fine and easy. I just had issues with files on the sd card coming from a Mac which was easy to handle with some terminal commands.

 

[Pingoo]

But how do I do that? I use Choi again to install 6.2 over itself?

Thank you for these clarifications, but as said "flamesdragon", how to achieve this, can you tell the procedure for "install 6.2 over itself".
Which tool ?, reboot between the two operations? Some details would be welcome

 

[Trickz]

So for me, fortunately, I didn't have to install 6.2 over itself? I just downgraded to 6.2 and when I created it emunand, I checked the firmware and it even said 6.2 AMS.

After that, my Emunand just said 6.2 (no AMS or anything), then I restored my 7.0 NAND and it worked out. I never messed with any of this before so not sure if having a super "clean nand" had anything to do with it.

 

[imprezgc8]

Thank you for these clarifications, but as said "flamesdragon", how to achieve this, can you tell the procedure for "install 6.2 over itself".
Which tool ?, reboot between the two operations? Some details would be welcome

You just run Choi again and pick the 6.2 firmware. There is no special process.

So for me, fortunately, I didn't have to install 6.2 over itself? I just downgraded to 6.2 and when I created it emunand, I checked the firmware and it even said 6.2 AMS.

After that, my Emunand just said 6.2 (no AMS or anything), then I restored my 7.0 NAND and it worked out. I never messed with any of this before so not sure if having a super "clean nand" had anything to do with it.

If you booted Atmo (which we do not support) after you downgrade you would not have had the issue. The issue is with SX and the boot 0/1 of the nand after downgrading. Atmo also does not support emunand so if you booted your 6.2 emunand to SX then it will not say AMS with the version.