Hacking SXOS Question

[shanefromoz]

Hello i have a switch which has been banned currently on 9.1.0.
I am wanting to update to 9.2.0.
Previously i have used Choid to update.
Can i just use normal system update then replace sxox boot or should i continue to use Choid?

Thanks

 

[Hayato213]

Use ChoidujourNX.

 

[shanefromoz]

Use ChoidujourNX.

Others are saying seeing im banned i can just update normally.
Just want to be 100% sure

 

[Hayato213]

Others are saying seeing im banned i can just update normally.
Just want to be 100% sure

Well it is up to you, ChoidujourNX preserves fuses.

 

[RednaxelaNnamtra]

Well it is up to you, ChoidujourNX preserves fuses.

Depending on the cfw you are using, they are also preserved when updating normally. I never used choidojour, on any of my unbaned switches with atmosphere/sxos, always updated normally while having autorcm enabled in cfw and no fuses got burned.

 

[Hayato213]

Depending on the cfw you are using, they are also preserved when updating normally. I never used choidojour, on any of my unbaned switches with atmosphere/sxos, always updated normally while having autorcm enabled in cfw and no fuses got burned.

You do know that updating from Nintendo server regardless AutoRCM or not it still burn fuse right?

 

[shanefromoz]

Depending on the cfw you are using, they are also preserved when updating normally. I never used choidojour, on any of my unbaned switches with atmosphere/sxos, always updated normally while having autorcm enabled in cfw and no fuses got burned.

Really. I didnt know this

 

[RednaxelaNnamtra]

You do know that updating from Nintendo server regardless AutoRCM or not it still burn fuse right?

It's not since cfws started protecting the partition, meaning the normal package1loader (if I remember the module correctly) is never run, so no fuses are burned.
Before the cfws got this feature, it was also possible to prevent fuse burning when updating, by using the jig and entering rcm mode directly on the reboot, and directly reinstalling autorcm.

 

[Hayato213]

It's not since cfws started protecting the partition, meaning the normal package1loader (if I remember the module correctly) is never run, so no fuses are burned

No, OFW update disable AutoRCM , fuse get burned. Do your research.

 

[RednaxelaNnamtra]

No, OFW update disable AutoRCM , fuse get burned. Do your research.

that's very outdated information. Like I said, most current cfws protect the partition containing the autorcm modification, resulting in autorcm not being removed.

 

[Hayato213]

that's very outdated information. Like I said, most current cfws protect the partition containing the autorcm modification, resulting in autorcm not being removed.

Well the thing is it doesn't boot into CFW when you update via Nintendo server, it jump directly into Non CFW state Sysnand, that why fuse is burn, don't believe try it.

 

[RednaxelaNnamtra]

Well the thing is it doesn't boot into CFW when you update via Nintendo server, it jump directly into Non CFW state Sysnand, that why fuse is burn, don't believe try it.

Like I said, I always updated both of my switches this way, and while I needed to manually boot into rcm on reboot in the beginning when doing it this way, I don't need to do anything to preserve autormc anymore, since the cfws I use protect it

Don't belive me? Here is one of the atmosphere code parts, where you can check it yourself:
* https://github.com/Atmosphere-NX/At...atosphere/source/updater/updater_api.cpp#L337

Also here are changelog parts of atmosphere about this topic:
* https://github.com/Atmosphere-NX/At...329e4f8afa7b321fe3f7879/docs/changelog.md#080
* https://github.com/Atmosphere-NX/At...329e4f8afa7b321fe3f7879/docs/changelog.md#081
* https://github.com/Atmosphere-NX/At...29e4f8afa7b321fe3f7879/docs/changelog.md#0810

Do your homework, before trying to spread outdated informations ^^

 

[JayMathis]

Popcorn.gif

 

[Hayato213]

Like I said, I always updated both of my switches this way, and while I needed to manually boot into rcm on reboot in the beginning when doing it this way, I don't need to do anything to preserve autormc anymore, since the cfws I use protect it

Don't belive me? Here is one of the atmosphere code parts, where you can check it yourself:
* https://github.com/Atmosphere-NX/At...atosphere/source/updater/updater_api.cpp#L337

Also here are changelog parts of atmosphere about this topic:
* https://github.com/Atmosphere-NX/At...329e4f8afa7b321fe3f7879/docs/changelog.md#080
* https://github.com/Atmosphere-NX/At...329e4f8afa7b321fe3f7879/docs/changelog.md#081
* https://github.com/Atmosphere-NX/At...29e4f8afa7b321fe3f7879/docs/changelog.md#0810

Do your homework, before trying to spread outdated informations ^^

Im not spreading rumors, you don;t know how Nintendo bootloader work, when you update via Nintendo server it bypass custom bootloader. I burned fuse in the past with modchip units so I know how it work.

 

[RednaxelaNnamtra]

Im not spreading rumors, you don;t know how Nintendo bootloader work, when you update via Nintendo server it bypass custom bootloader. I burned fuse in the past with modchip units so I know how it work.

Did you even read any of the link I showed?
Yeah, in the past updating without the jig inserted and manually entering rcm mode resulted in the removal of autorcm and burned fuses, but even then it was possible to manually entering RCM mode and reinstall autorcm, before even loading nintendos code again.
And like I said CFWs added protection mechanisms to prevent this from happening, first they prevented autorcm from being overwritten by using a mitm module, then they highjacked the reboot, to directly reboot into cfw again, which will happen independend of the source of the reboot.

I could also capture a video of one of my switches being update, I you really want to see another proof, besides litereally the CFW code and Changelog itself.

 

[Draxzelex]

Dunno about SX OS because their changelogs don't even highlight half of the changes but Atmosphere and ReiNX both preserve AutoRCM when updating online. Of course, you have to be in CFW as the protection will not be there in OFW.