Hacking Does SX OS prevent updating game card firmware?

[jonnyh585]

If you dont insert a gc then SX OS will prevent card fw updates. If you insert a gc it fallbacks to original behavior which is to update the gc asic if needed.
Also seems it only does this with a legit license. If you dont have a license it will fallback again

this is very helpful info not posted anywehre on gba temp or reddit, thank you for your post!!

sx os users, update away dont stress over nogc kip!!!!!!!

 

[mikefor20]

is this true?

 

[badpix11]

I think they dont prevent the gc update intended its just because SXOS redirect it for the gamecard emulation.

 

[loler55]

If you dont insert a gc then SX OS will prevent card fw updates. If you insert a gc it fallbacks to original behavior which is to update the gc asic if needed.
Also seems it only does this with a legit license. If you dont have a license it will fallback again

time to resell my one game

 

[mikefor20]

But is it true, intended or not. Is the update prevented as long as I don't use the slot?

 

[bundat]

But is it true, intended or not. Is the update prevented as long as I don't use the slot?

I mean, json seems to have a very in-depth understanding of the Switch's inner workings, and has knowledge of lots of undocumented stuff, like:

• How to use/setup Atmosphere's creport on SX OS:
  • https://gbatemp.net/threads/team-xe...v6-0-compatibility.517002/page-7#post-8260307
• Creating tools to analyze the USER partition while analyzing how SX OS emunand works:
  • https://gbatemp.net/threads/how-does-sx-os-emunand-work.518936/page-2#post-8297810
• In-depth knowledge of how SX OS Stealth mode works
  • https://gbatemp.net/threads/team-xe...lth-mode-and-more.516197/page-16#post-8248089
    
  • https://gbatemp.net/threads/sx-os-stealth-mode-is-not-creport.516455/page-3#post-8248098
• He even seems to have access to (or knowledge of) private scene hacking stuff:
  • https://gbatemp.net/threads/deja-vu-exploit-given-to-nintendo.521166/page-2#post-8341201

So I'd say he's a pretty reliable source of info, he seems to be at the same level as a scene dev (or close to it).

I understand you'd still hate to take the risk yourself though, and end up with cart v2 when you have a cart v1 gc unit.

If I was in your position, I'd @ tag him (or pm him) and ask for details as to how he got this info about the "unintended (?) nogc behavior" SX OS has, just to set my mind at ease.

 

[Draxzelex]

I mean, json seems to have a very in-depth understanding of the Switch's inner workings, and has knowledge of lots of undocumented stuff, like:

• How to use/setup Atmosphere's creport on SX OS:
  • https://gbatemp.net/threads/team-xe...v6-0-compatibility.517002/page-7#post-8260307

This one is actually false and I had a feeling it was because its due to a misunderstanding of how creport is enabled. Contrary to popular opinion, its not enabled via LayeredFS but the loader sysmodule of the CFW. ReiNX and Atmosphere both already supported it so I decided to conduct a simple test to debunk this once and for all.

What I did was cause a crash when using the old version of kezplez. Both ReiNX and Atmosphere successfully redirected the error report to the SD card in the /atmosphere/crash_reports however SX OS did not. I did a double check by going to System Settings -> Support/Health & Safety -> Error History. I did not see the error reports generated in ReiNX nor Atmosphere but I saw the one generated in SX OS. Therefore SX OS does not support Atmosphere's creport which makes me further question his knowledge on SX OS.

 

[bundat]

Therefore SX OS does not support Atmosphere's creport which makes me further question his knowledge on SX OS.

Well, while we wait for @json to respond (if he does), can you tell me the details on how to cause a crash with the old version of kezplez? I'm guessing I need the v1.0 release on github.

 

[Draxzelex]

Well, while we wait for @json to respond (if he does), can you tell me the details on how to cause a crash with the old version of kezplez? I'm guessing I need the v1.0 release on github.

That's exactly what I used. I just put the .nro and .nacp into the /switch/kezplez-nx folders then launched it. I also dumped my tsec keys and fuse info with Hekate V4.2 so they were in the wrong spot which may have led to the crash. You might be able to generate the crash without those files anyway since tesnos' version of kezplez expects them to be directly in the /backup folder and nowhere else.

 

[BL4Z3D247]

If you dont insert a gc then SX OS will prevent card fw updates. If you insert a gc it fallbacks to original behavior which is to update the gc asic if needed.
Also seems it only does this with a legit license. If you dont have a license it will fallback again

So has this been 100% confirmed? Because I have a friend who is trying to preserve his 1.0.0 and wants to keep the card slot working on <4.0.0 firmwares.

He's done a full NAND backup and updated to 5.1.0 via ChoiDujourNX. At this point he's holding off on using SX OS until he finds out if keeping a game out of the game card slot in while booted into SX OS actually prevents the game card slot from updating.

 

[mikefor20]

So has this been 100% confirmed? Because I have a friend who is trying to preserve his 1.0.0 and wants to keep the card slot working on <4.0.0 firmwares.

He's done a full NAND backup and updated to 5.1.0 via ChoiDujourNX. At this point he's holding off on using SX OS until he finds out if keeping a game out of the game card slot in while booted into SX OS actually prevents the game card slot from updating.

I have been wanting this information as well. I want my GC fuses preserved.

 

[BL4Z3D247]

I have been wanting this information as well. I want my GC fuses preserved.

You can preserve the efuses by using ChoiDujourNX, it automatically enables AutoRCM which bypasses the fuse check and prevents any fuses from being burned.

The game card slot firmware is a different story though. SX OS doesn't support kip1 patching which to my knowledge is the only way of preserving the game card slot firmware(ChoiDujourNX makes a configuration file for you to use).

Unless what json claimed is true, then it would be possible to preserve the game card slot firmware while booted into SX OS as well as the other CFWs.

 

[GBCTEMP]

I'm also waiting for confirmation about GC fuse protection before I use SX OS. Maybe @garyopa could find out for us?

 

[fatterdude2000]

json is correct. Using sx 2.3 I updated to emunand 5.1 (without gamecard inserted). I then booted back to Sysnand 3.0.0. I could use my original Zelda card.

Seconds later I booted into emunand BUT forgot to take out the gamecard... now when I boot into sysnand with gamecard inserted I get an error.

Took a moment lapse of concentration by leaving the gamecard inserted. I was happy one second and disappointed the next. 5minutes later I'm back in the real world and only slightly annoyed with myself.

 

[GBCTEMP]

json is correct. Using sx 2.3 I updated to emunand 5.1 (without gamecard inserted). I then booted back to Sysnand 3.0.0. I could use my original Zelda card.

Seconds later I booted into emunand BUT forgot to take out the gamecard... now when I boot into sysnand with gamecard inserted I get an error.

Took a moment lapse of concentration by leaving the gamecard inserted. I was happy one second and disappointed the next. 5minutes later I'm back in the real world and only slightly annoyed with myself.

Thanks for letting us know. It's annoying that happened to you tho, but at least it isnt the end of the world.

 

[pLaYeR^^]

I'm wondering if there are any news on this?

 

[deanspeed]

Why can't we get any confirmation on this from TX?

 

[mikefor20]

Gary did confirm it. Your GC slot fuses will be fine if you don't use the slot itself and you are on the latest SX OS. SX OS protects the slot by disabling it automatically. It re-enables if you put a cart in the slot so don't so that.

It is worth mentioning that it has been said by some VERY RELIABLE people that there will be a way to bypass the GC fuse check in the future anyway.

 

[pLaYeR^^]

Gary did confirm it. Your GC slot fuses will be fine if you don't use the slot itself and you are on the latest SX OS. SX OS protects the slot by disabling it automatically. It re-enables if you put a cart in the slot so don't so that.

It is worth mentioning that it has been said by some VERY RELIABLE people that there will be a way to bypass the GC fuse check in the future anyway.

Can you send me a link where he confirmed it?

 

[thaikhoa]

Can you send me a link where he confirmed it?

Confirmed by me.