Hacking Suggestion Careful when using Rajkosto's upgrade system and SX OS

[Nemean]

Just a quick message from me I used Rajkosto's upgrade system which is great however i then let curiosity get the better of me and played with SX OS this booted into a black screen so i thought nothing of it and assumed it was broken. I have now checked my fuses and it i have 6 burnt fuses (5.x.x) when i should only have 5 (4.x.x). It seems SX OS boots and burns fuses if the version is different just like a normal fuse check. I would like this clarified as currently only 2 users have reported so anybody else who has tried please check fuses and a quick post here may save some people going forward.

Important: This thread is only relevant if you are using Rajkosto's method to upgrade if you are just using an old firmware switch i have no idea if it would be affected but would assume not.

 

[cearp]

Wow thanks for trialing it and pointing that out.
Thankfully it's just one more fuse, and probably without hekate you won't be able to boot up now, until a later fw version that actually needs 6 fuses.

 

[Deleted User]

It looks like SX OS just boots whatever is on eMMC boot0. I'm assuming you didnt have a 4.x.x nx bootloader on boot0?

 

[superss]

It happened to me as well. So I updated officially to 5.1 because the fuse was burned.

 

[mcmrc1]

Ok.. thx for the info.. Can someone point me out how to check the fuses ?

 

[Nemean]

It looks like SX OS just boots whatever is on eMMC boot0. I'm assuming you didnt have a 4.x.x nx bootloader on boot0?

No i had used the method of upgrading to 5.1 without burning fuses however i guess when SX OS booted it does it outside of RCM mode which i believe is what allows us to run higher firmware without burning fuses? Odd the way it works i'm sure we will have more info in the coming weeks.

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

Ok.. thx for the info.. Can someone point me out how to check the fuses ?

If you grab Briccmii V2 payload from Rajkosto it will tell you.

https://switchtools.sshnuke.net/

 

[Moquedami]

So, if the SX OS is burning efuses, that would render the nand backup useless right?
What would happen in case of a brick?
No way of recovery?

 

[Nemean]

Honestly i am not sure what would happen at that point i was under the impression that no matter what we would be able to use RCM mode so if you were happy with Hekate then its unbrickable?

 

[MonMonz]

So if i have 2.1 switch and boot offline to SX OS as i want to stay on my low firmware
Is it gonna burn my e-fuses to the latest (6) ?
Am confused

 

[lordelan]

So if i have 2.1 switch and boot offline to SX OS as i want to stay on my low firmware
Is it gonna burn my e-fuses to the latest (6) ?
Am confused

I'm confused as well now. I was planning on using it on my 3.0.0 Switch to play all 3.0.0 games with SX OS and staying on that FW until some emunand solution comes out.

 

[coolbird22]

Does the SX OS burn the efuses even if that Rajkostos upgrade system has not been used ? I guess a better question is, does it burn the efuses of each virgin switch ?

 

[Moquedami]

Yes, apparently it burns the efuses to the last firm aviable regardless of the firm you are in.

How do we check our fuses count easily?
That way we can check with anyone that already used SX OS with a lower firm

 

[Nemean]

So if i have 2.1 switch and boot offline to SX OS as i want to stay on my low firmware
Is it gonna burn my e-fuses to the latest (6) ?
Am confused

No sorry perhaps i should have been more clear. This as far as i know is only valid while using Rajkosto's upgrade method which allows you to upgrade the firmware on the switch (or downgrade) without burning fuses. Fantastic if you want to play online or use Eshop but not lose lower firmware. However for some unknown reason SX OS bypasses the fuse check skip and forces the fuses to be updated. Once again the issue i am talking about is only valid if you are using Rajkosto's upgrade method.

 

[MonMonz]

No sorry perhaps i should have been more clear. This as far as i know is only valid while using Rajkosto's upgrade method which allows you to upgrade the firmware on the switch (or downgrade) without burning fuses. Fantastic if you want to play online or use Eshop but not lose lower firmware. However for some unknown reason SX OS bypasses the fuse check skip and forces the fuses to be updated. Once again the issue i am talking about is only valid if you are using Rajkosto's upgrade method.

Oh okey thanks for the clarification.

 

[Nemean]

Yes, apparently it burns the efuses to the last firm aviable regardless of the firm you are in.

How do we check our fuses count easily?
That way we can check with anyone that already used SX OS with a lower firm

Just grab BriccMii V2 and run the payload this will show how many fuses are burnt.

 

[lordelan]

No sorry perhaps i should have been more clear. This as far as i know is only valid while using Rajkosto's upgrade method which allows you to upgrade the firmware on the switch (or downgrade) without burning fuses. Fantastic if you want to play online or use Eshop but not lose lower firmware. However for some unknown reason SX OS bypasses the fuse check skip and forces the fuses to be updated. Once again the issue i am talking about is only valid if you are using Rajkosto's upgrade method.

Sorry for being confused but ... does that mean fuses are only burnt by SX OS if you

1. used the upgrade tutorial to get on latest FW while keeping your fuses on something like 3.0.0?
   or
   
2. if you're really on a low firmware like 3.0.0 without following the tutorial and just by launching SX OS then?

 

[superss]

Quick fix: boot stock through hekate and then update to the latest firmware then sx os will work.

 

[pLaYeR^^]

Sorry for being confused but ... does that mean fuses are only burnt by SX OS if you

1. used the upgrade tutorial to get on latest FW while keeping your fuses on something like 3.0.0?
   or
   
2. if you're really on a low firmware like 3.0.0 without following the tutorial and just by launching SX OS then?

Afaik if you update your firmware with the tutorial and don't burn fuses, SX OS will burn them. If you stay on your firmware, you shouldn't have issues.

 

[Doodil]

However for some unknown reason SX OS bypasses the fuse check skip and forces the fuses to be updated.

That's standard switch boot procedure, if it detects you are on a high fw and you have less fuses burned than necessary it burns them. The question is rather why did you expect SX OS to have the fuse bypass implemented?

 

[Nemean]

Sorry for being confused but ... does that mean fuses are only burnt by SX OS if you

1. used the upgrade tutorial to get on latest FW while keeping your fuses on something like 3.0.0?
   or
   
2. if you're really on a low firmware like 3.0.0 without following the tutorial and just by launching SX OS then?

Nope thats fine it was me not being clear. Option 1 is correct so either stay on low firmware and use SX OS or use Rajkosto's method to update to 5.1 and not burn any fuses. You can not do both so i guess Rajkosto's if you want to play online/eshop/backup/not burn fuses and SX OS if you are happy to stay offline and on lower firmware but the backups seem smoother currently.

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

That's standard switch boot procedure, if it detects you are on a high fw and you have less fuses burned than necessary it burns them. The question is rather why did you expect SX OS to have the fuse bypass implemented?

I didnt expect it to have this implemented but as i had used Rajkosto's method to do this i expected it to not overwrite what had been done to Boot0 to bypass fuse checks. My question is does that mean it is altering my boot0 even if i dont activate autoRCM and if so as its closed source what specifically is it doing?