Hacking SX OS and Nintendo Update Questions

LeeRocker1623 · Jun 4, 2019

I Havent see any threads for my SX OS and intended Nintendo firmware versions.

Current OFW: 4.0.1
Current emuNAND: 6.0.2
Current SX OS: 2.5.3

1. I am trying to update OFW to 8.0.1 on OFW with auto RCM enabled. I have heard that this breaks autoRCM and might not even work if SX OS doesn't support it. Will it still break autoRCM?

2. If autoRCM breaks, can I still recover it using the method I've seen in a post about a year ago?

3. Does SXOS support 8.0.1?

4. Is my autoRCM method on OFW plausible? (As in will it work without burning fuses and getting banned).

I'm aware there is a ban risk whenever you connect to Nintendo servers in any way.

paulzheng · Jun 4, 2019

you needn't to upd ofw if you have emunand. otherwise i think you want to make dual-nand to play games online.
anyway. you can update emunand the latest 8.01 by choidujournx offline installation method. and don't forget replace boot.dat on microsd's root folder with sxos's new version 2.71.

SXOS 2.71 is support top to ofw 8.01， i don't think autorcm method have any brick risk so far. i think you have to backup console's rawnand or system partitions

physical nand and emunand be seperated with each other. if you want to play online game in physical nand reduce be banned risk. i think you should disable autorcm setting and shift another microsd.

LeeRocker1623 · Jun 4, 2019

paulzheng said:
you needn't to upd ofw if you have emunand. otherwise i think you want to make dual-nand to play games online.
anyway. you can update emunand the latest 8.01 by choidujournx offline installation method. and don't forget replace boot.dat on microsd's root folder with sxos's new version 2.71.

SXOS 2.71 is support top to ofw 8.01， i don't think autorcm method have any brick risk so far. i think you have to backup console's rawnand or system partitions

physical nand and emunand be seperated with each other. if you want to play online game in physical nand reduce be banned risk. i think you should disable autorcm setting and shift another microsd.

I was under the assumption that in order to play online and install from the eShop, I would need to be on OFW. Regardless, the reason why I need to update my OFW is to recover my cloud save data. Nintendo forces you to update on order to recover cloud saves.

Will I just be able to update OFW after manual RCM? I don't want to burn any fuses, and I've read that the Nintendo updates force restarts during the update, which is why you need autoRCM.

The dual SIM method is enticing and seems less risky, but I would have to research it more

astrodraco · Jun 4, 2019

LeeRocker1623 said:
I Havent see any threads for my SX OS and intended Nintendo firmware versions.

Current OFW: 4.0.1
Current emuNAND: 6.0.2
Current SX OS: 2.5.3

1. I am trying to update OFW to 8.0.1 on OFW with auto RCM enabled. I have heard that this breaks autoRCM and might not even work if SX OS doesn't support it. Will it still break autoRCM?

2. If autoRCM breaks, can I still recover it using the method I've seen in a post about a year ago?

3. Does SXOS support 8.0.1?

4. Is my autoRCM method on OFW plausible? (As in will it work without burning fuses and getting banned).

I'm aware there is a ban risk whenever you connect to Nintendo servers in any way.

1) It doesn't "break" it in the tense you're thinking. It more or less "disables" it. You can enable it again from the SX OS recovery menu again.

2) Dunno what that post is, but you can turn autoRCM back on with no problem at all.

3) Yes.

4) If you update through the system normally, you will burn fuses regardless. If you want to preserve your fuses (I think this is a smarter approach for various different reasons) you should disable emuNAND, boot into CFW with Stealth Mode enabled, then use Choi to update. It even has an option to preserve your fuses and reenable autoRCM. After that, enable EmuNAND, boot into it, use Choi to update emuNAND.

LeeRocker1623 · Jun 4, 2019

astrodraco said:
1) It doesn't "break" it in the tense you're thinking. It more or less "disables" it. You can enable it again from the SX OS recovery menu again.

2) Dunno what that post is, but you can turn autoRCM back on with no problem at all.

3) Yes.

4) If you update through the system normally, you will burn fuses regardless. If you want to preserve your fuses (I think this is a smarter approach for various different reasons) you should disable emuNAND, boot into CFW with Stealth Mode enabled, then use Choi to update. It even has an option to preserve your fuses and reenable autoRCM. After that, enable EmuNAND, boot into it, use Choi to update emuNAND.

I want to use Nintendo's cloud save recovery and it is forcing me to update. I don't want to go online with CFW, which is why I thought it was smartest to do it on OFW. My OFW also doesn't support exfat. Is there any way I can update OFW without burning fuses? The cloud saves, online play and exfat support are a deal breaker for me.

astrodraco · Jun 4, 2019

LeeRocker1623 said:
I want to use Nintendo's cloud save recovery and it is forcing me to update. I don't want to go online with CFW, which is why I thought it was smartest to do it on OFW. My OFW also doesn't support exfat. Is there any way I can update OFW without burning fuses? The cloud saves, online play and exfat support are a deal breaker for me.

OFW and CFW are the same NAND - it depends on if you use emuNAND on CFW or not. If you disable emuNAND and boot into CFW, any changes you make there are being made to your OFW. You can also do a completely offline update to 8.0.1 with Choi.

Basically the only way to update and not burn fuses is to run Choi.

LeeRocker1623 · Jun 4, 2019

astrodraco said:
OFW and CFW are the same NAND - it depends on if you use emuNAND on CFW or not. If you disable emuNAND and boot into CFW, any changes you make there are being made to your OFW. You can also do a completely offline update to 8.0.1 with Choi.

Basically the only way to update and not burn fuses is to run Choi.

Wow, this bit of information I did not know. For some reason my CFW version is different from my OFW version, so this mislead me into thinking they were entirely separate FW. I will update my CFW then thank you so much.

astrodraco · Jun 4, 2019

LeeRocker1623 said:
Wow, this bit of information I did not know. For some reason my CFW version is different from my OFW version, so this mislead me into thinking they were entirely separate FW. I will update my CFW then thank you so much.

It should only show up as different if you boot into emuNAND while booting into CFW. If you disable emuNAND, it should show the same firmware as your sysNAND (or what you had once called OFW).

LeeRocker1623 · Jun 4, 2019

astrodraco said:
It should only show up as different if you boot into emuNAND while booting into CFW. If you disable emuNAND, it should show the same firmware as your sysNAND (or what you had once called OFW).

Great explanation. Disabling emuNAND and updating with Choi, as well as so os, now has my OFW to the latest version. Thank you for your help, I can use cloud saves now!

LeeRocker1623 · Jun 5, 2019

astrodraco said:
1) It doesn't "break" it in the tense you're thinking. It more or less "disables" it. You can enable it again from the SX OS recovery menu again.

2) Dunno what that post is, but you can turn autoRCM back on with no problem at all.

3) Yes.

4) If you update through the system normally, you will burn fuses regardless. If you want to preserve your fuses (I think this is a smarter approach for various different reasons) you should disable emuNAND, boot into CFW with Stealth Mode enabled, then use Choi to update. It even has an option to preserve your fuses and reenable autoRCM. After that, enable EmuNAND, boot into it, use Choi to update emuNAND.

astrodraco said:
OFW and CFW are the same NAND - it depends on if you use emuNAND on CFW or not. If you disable emuNAND and boot into CFW, any changes you make there are being made to your OFW. You can also do a completely offline update to 8.0.1 with Choi.

Basically the only way to update and not burn fuses is to run Choi.

Update:

I disabled emuNAND, updated using Choi, and after enabling emuNAND, my OFW is still on version 4.0. This proves that when emuNAND is disabled and an update is made, it DOES NOT get applied to the OFW. I still am back to my original issue, my OFW is at 4.0

astrodraco · Jun 5, 2019

LeeRocker1623 said:
Update:

I disabled emuNAND, updated using Choi, and after enabling emuNAND, my OFW is still on version 4.0. This proves that when emuNAND is disabled and an update is made, it DOES NOT get applied to the OFW. I still am back to my original issue, my OFW is at 4.0

I’m not sure what could be wrong. You have something wrong structurally because it shouldn’t work this way at all. Your sysNAND is the only other NAND outside of emuNAND, so if you boot CFW with emuNAND disabled, your OFW and CFW should reflect each other.

Unless there’s something different happening with SX OS and the terminology being used doesn’t match up, there’s something structurally wrong with everything here.

Hacking SX OS and Nintendo Update Questions

Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Member

Member

Well-Known Member

Similar threads

Popular threads in this forum