Homebrew Question Can the Switch Downgrade?

[Mat37]

Yep! (But zero reason to do so ATM.)

Do you think i can update games and then restore the 5.0.1 system partition ?

 

[SomeGamer]

Do you think i can update games and then restore the 5.0.1 system partition ?

Please don't do that, there is no point in doing so.

 

[Mat37]

Please don't do that, there is no point in doing so.

I don't get why. Will restoring the system partition make the update unusable or something like this ?

 

[SomeGamer]

I don't get why. Will restoring the system partition make the update unusable or something like this ?

No, but there is literally no reason to downgrade right now.

 

[switchalex]

There are 2 types of updates on the Switch: Those that burn fuses and those that don't. Whenever an update burns a fuse, that means NAND backups from before that update can not be booted anymore.

So if you update from 4.1.0 to 5.0.1 for example, you burn a fuse, meaning you can not downgrade to below 5.x anymore.
If, however, you update from 5.0.1 to 5.1.0 you don't burn a fuse, meaning you can downgrade by simply writing back your NAND backup.

As a rule of thumb: When the major version number changes (e.g. 4 -> 5) a fuse is burnt and you can not downgrade anymore. This is not a fixed rule though, occasionally an update will burn a fuse even on same major versions (for example 3.0.0 -> 3.0.1) so always look it up before doing anything rash.

Damn so I can’t go back to 5.1 from 6.0 I’m guessing. Damn it

 

[Draxzelex]

Damn so I can’t go back to 5.1 from 6.0 I’m guessing. Damn it

Well you can because we can bypass the fuse check of the bootloader with our substitute payloads that double as bootloaders such as Hekate or ReiNX. However even if you do this, you lose out on sleep mode since we cannot bypass this check at the current time.

 

[switchalex]

Well you can because we can bypass the fuse check of the bootloader with our substitute payloads that double as bootloaders such as Hekate or ReiNX. However even if you do this, you lose out on sleep mode since we cannot bypass this check at the current time.

I was mostly hoping to revert to clean ofw to check if I was banned, and if I’m clean I do a clean update to 6.0 and make a clean back up for that as well
( although when I was looking around I saw alot about a choju-something for updating without burning fuses which sounds handy as well)

I just want to know if I’m going to need to buy a new switch for smash or not because I have a very good real near me selling just the switch with no joycons or dock for $120 atm

 

[switchalex]

Well you can because we can bypass the fuse check of the bootloader with our substitute payloads that double as bootloaders such as Hekate or ReiNX. However even if you do this, you lose out on sleep mode since we cannot bypass this check at the current time.

I’m sorry to bother you again but do you think what I suggested in my comment above is do able? And would I get rid of the no sleep issue when updating from clean 5.1 to clean 6.0? Using that choju- thing

 

[Draxzelex]

I’m sorry to bother you again but do you think what I suggested in my comment above is do able? And would I get rid of the no sleep issue when updating from clean 5.1 to clean 6.0? Using that choju- thing

Yes, that's perfectly fine. The only thing I would advise is that if your console went online with firmware 6.0, do not update the clean 5.1 NAND online since Nintendo believes you're on firmware 6.0 now;instead use ChoiDujourNX. If you didn't go online with your firmware 6.0, then update either using ChoiDujourNX or online.

 

[switchalex]

Yes, that's perfectly fine. The only thing I would advise is that if your console went online with firmware 6.0, do not update the clean 5.1 NAND online since Nintendo believes you're on firmware 6.0 now;instead use ChoiDujourNX. If you didn't go online with your firmware 6.0, then update either using ChoiDujourNX or online.

Awesome, just a last thing to clear up before I start,

So I'm using ChoiDujourNX to downgrade to 5.1, then restoring to my back up on 5.1 , then using ChoiDujourNX again to head to 6.0 ?

I use SXOS, so when you mentioned using reinx or hekate as boot loaders I wasn't to positive in where they fit in this or if sxos is fine to run ChoiDujourNX as a home-brew app

 

[Draxzelex]

Awesome, just a last thing to clear up before I start,

So I'm using ChoiDujourNX to downgrade to 5.1, then restoring to my back up on 5.1 , then using ChoiDujourNX again to head to 6.0 ?

I use SXOS, so when you mentioned using reinx or hekate as boot loaders I wasn't to positive in where they fit in this or if sxos is fine to run ChoiDujourNX as a home-brew app

I thought you were using your NAND and boot0/boot1 to downgrade to 5.1 since that one is clean?

Terms like bootloaders and CFW can get confusing, especially when some act as both. Hekate is purely a bootloader; its function is to run CFW. ReiNX and SX OS on the other hand are both bootloaders and CFWs. However SX OS has them split unlike ReiNX (the CFW is boot.dat while the bootloader is loader.bin). I've heard SX OS V2.0 finally supports ChoiDujourNX but haven't confirmed this myself.

 

[switchalex]

I thought you were using your NAND and boot0/boot1 to downgrade to 5.1 since that one is clean?

Terms like bootloaders and CFW can get confusing, especially when some act as both. Hekate is purely a bootloader; its function is to run CFW. ReiNX and SX OS on the other hand are both bootloaders and CFWs. However SX OS has them split unlike ReiNX (the CFW is boot.dat while the bootloader is loader.bin). I've heard SX OS V2.0 finally supports ChoiDujourNX but haven't confirmed this myself.

That's what I'm trying to do , I assumed I had to use ChoiDujourNX to do that, but looking back what you said and after watching a video on how to restore nand, so what I'm doing is:

I am using hekate and my backup to restore down to 5.1 clean ( where the issue with not being able to use sleep will be that you mentioned) THEN I use ChoiDujourNX to go to a clean 6.0(sleep issue fixed, logs cleaned, clean nand) and make a new clean backup for later use, and from here it is a "new switch" again? Or well ChoiDujourNX would imply home-brew so the 6.0 wouldn't be clean ? Or does it remove itself when installing a target fw

Again thanks so much for helping man I appreciate every word of wisdom

 

[Draxzelex]

That's what I'm trying to do , I assumed I had to use ChoiDujourNX to do that, but looking back what you said and after watching a video on how to restore nand, so what I'm doing is:

I am using hekate and my backup to restore down to 5.1 clean ( where the issue with not being able to use sleep will be that you mentioned) THEN I use ChoiDujourNX to go to a clean 6.0(sleep issue fixed, logs cleaned, clean nand) and make a new clean backup for later use, and from here it is a "new switch" again? Or well ChoiDujourNX would imply home-brew so the 6.0 wouldn't be clean ? Or does it remove itself when installing a target fw

Again thanks so much for helping man I appreciate every word of wisdom

That's the problem, we don't know if it will be clean or not if you use ChoiDujourNX to update the firmware. You can either take the risk or not.

 

[switchalex]

That's the problem, we don't know if it will be clean or not if you use ChoiDujourNX to update the firmware. You can either take the risk or not.

Ah okay . I’ll give it a go then

 

[Canna]

Can I restore my 5.0.2 backup to a 5.1.0 nintendo switch and downgrade or is that not a possibility?

5.0.2 AND 5.1.0 USE THE SAME FUSE COUNT

so you can go back from 5.1.0 to 5.0.2 but its pointless why u even want to do that i do not know..
5.1.0 is the Best atm.. Until we work our way around 6.0

 

[switchalex]

That's the problem, we don't know if it will be clean or not if you use ChoiDujourNX to update the firmware. You can either take the risk or not.

Hey sorry to drag you back, but I've searched around and quite can't fix this issue,
Whenever I inject a payload now, I just get a black screen. Whether its the sx payload or memloader nothing comes up and I haven't changed anything. I' on 6.0 , I installed the drivers in Tegra, it shows that it finds my switch in ram and that the payload is injected but nothing happens. Any advice?

--------------------- MERGED ---------------------------

never mind, I was running windows through parallel and it wasn’t working but in bootcamp it Is. Strange since my parallel vm is using bootcamp as an iso