Homebrew Question Can the Switch Downgrade?

[froggestspirit]

actually a good question, are nand backups made before a fuse burn still useful for anything?

This is speculation on my part, But once atomosphere is out, you may be able to boot those backups, as I believe RCM does not check fuses. Someone correct me if I'm wrong

 

[m4xw]

Speculation: they contain device unique info, that could possibly be used to hack together with a newer donor nand in case you corrupt yours without a backup.

I think you can always boot a old backup with hekate. One of the patches applied to the securemonitor is the version check. Tho that might need a little fix since I don't know of anyone how did that yet

 

[reminon]

I think you can always boot a old backup with hekate. One of the patches applied to the securemonitor is the version check. Tho that might need a little fix since I don't know of anyone how did that yet

Ah ok.

 

[Lacius]

This is speculation on my part, But once atomosphere is out, you may be able to boot those backups, as I believe RCM does not check fuses. Someone correct me if I'm wrong

This is correct. However, it also defeats the purpose of downgrading, since you will only be able to boot your Switch using a jig/AutoRCM. There will never be any reason to downgrade a Switch.

 

[m4xw]

This is correct. However, it also defeats the purpose of downgrading, since you will only be able to boot your Switch using a jig/AutoRCM. There will never be any reason to downgrade a Switch.

I am a dev, I disagree. Would've loved to have a 4x Image on hand last week, wouldve saved me 1.5 days of debugging.

But for the average user there isn't much reason, unless you only ever use autorcm and boot through hekate on newer versions (it does disable burning fuses, but still has a version check, depending on the version, then you could actually downgrade)

Ofc thats nothing in comparision to emuNAND

 

[Lacius]

I am a dev, I disagree. Would've loved to have a 4x Image on hand last week, wouldve saved me 1.5 days of debugging.

But for the average user there isn't much reason, unless you only ever use autorcm and boot through hekate on newer versions (it does disable burning fuses, but still has a version check, depending on the version, then you could actually downgrade)

Ofc thats nothing in comparision to emuNAND

I don't know what the average user using AutoRCM would gain from a downgrade.

 

[m4xw]

I don't know what the average user using AutoRCM would gain from a downgrade.

You could inject the newest fw onto your nand, corrupt it from your PC (autoRCM, so it never is able to boot and burn the fuses), then boot it up with hekate (does disable burn fuses command & patch ver check) and access the eShop or whatever

 

[SomeGamer]

You could inject the newest fw onto your nand, corrupt it from your PC (autoRCM, so it never is able to boot and burn the fuses), then boot it up with hekate (does disable burn fuses command & patch ver check) and access the eShop or whatever

B-but what about emuNAND then?

 

[Lacius]

You could inject the newest fw onto your nand, corrupt it from your PC (autoRCM, so it never is able to boot and burn the fuses), then boot it up with hekate (does disable burn fuses command & patch ver check) and access the eShop or whatever

You're describing a manual upgrade that avoids burning efuses and creates a downgrade path, not a downgrade.

B-but what about emuNAND then?

emuNAND is a much better solution.

 

[m4xw]

You're describing a manual upgrade that avoids burning efuses, not a downgrade.


emuNAND is a much better solution.

Yes but after you did what you wanted to do, you can just downgrade to your original version without troubles, Thats the only use case I see besides dev

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

B-but what about emuNAND then?

Never said its a better solution (this hacky process i described) lol, quite the opposite

 

[SomeGamer]

Never said its a better solution lol, quite the opposite

But with emuNAND you can continue to use your sysNAND as before.

 

[froggestspirit]

I don't know what the average user using AutoRCM would gain from a downgrade.

It will probably be more like the 3DS at that point, where it is possible, but not many people will do it

 

[m4xw]

But with emuNAND you can continue to use your sysNAND as before.

Not saying anyone should do it, just that its possible.

Not even gonna discuss ban stuff with this method (non-emunand), because thats obv.

 

[Lacius]

It will probably be more like the 3DS at that point, where it is possible, but not many people will do it

Unless one creates a downgrade path manually by doing what @m4xw described above, a purposeful downgrade will never be possible because of efuses. If I were to downgrade 5.1.0 to 3.0.0, for example, I would have to use a jig/AutoRCM to boot an RCM payload each time I wanted to boot my Switch, which defeats any purpose to downgrading.

 

[Mat37]

Can I update to 5.1.0 from 5.0.1 and then return to 5.0.1 ?

 

[SomeGamer]

Can I update to 5.1.0 from 5.0.1 and then return to 5.0.1 ?

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

 

[The Real Jdbye]

actually a good question, are nand backups made before a fuse burn still useful for anything?

They will be once we have emuNAND

 

[pman152]

ONLY 5.1.0 can go back to 5.0.0, this is because 5.1.0 did NOT burn any efuses.
If you were to try do this from for example 5.1.0 to 4.1.0 e.t.c it would end up in a full brick.

 

[linuxares]

ONLY 5.1.0 can go back to 5.0.0, this is because 5.1.0 did NOT burn any efuses.
If you were to try do this from for example 5.1.0 to 4.1.0 e.t.c it would end up in a full brick.

Nah, just a full Horizon brick. RCM should still work.

 

[pman152]

Nah, just a full Horizon brick. RCM should still work.

Oh, kk