Hacking SWITCH NOOB PARADISE - Ask questions here

HoTsHoTz79 · Jul 22, 2019

Question about AutoRCM: How do I enable it in Hekate / Nyx version 5?

Have 8.1.0 with latest Kosmos/Atmosphere, emuMMC enabled and setup was done following the guide @ scenefolks which didn't mention how/where to enable it.

The only option i found in Nyx was under Tools > AutoBoot, which is on but i think that just automatically launches the CFW option

Lacius · Jul 22, 2019

aarti said:
Device F: is completely empty, can I just put files in there as I do in E:?

Your emuNAND partition should be left alone.

HoTsHoTz79 said:
Question about AutoRCM: How do I enable it in Hekate / Nyx version 5?

Have 8.1.0 with latest Kosmos/Atmosphere, emuMMC enabled and setup was done following the guide @ scenefolks which didn't mention how/where to enable it.

The only option i found in Nyx was under Tools > AutoBoot, which is on but i think that just automatically launches the CFW option

Are you using an 8.1.0 sysNAND, or are you using an 8.1.0 emuNAND with an ipatched system? You cannot install AutoRCM on an ipatched system.

alexj9626 · Jul 22, 2019

Can SXOS install splitted XCIs?

HoTsHoTz79 · Jul 22, 2019

Lacius said:
Are you using an 8.1.0 sysNAND, or are you using an 8.1.0 emuNAND with an ipatched system? You cannot install AutoRCM on an ipatched system.

I am not sure if its iPatched... I bought a used one that was updated to FW 8.1.0 and serial # starts with XAW7-000852...

For launch option, i am selecting 'CFW (emuMMC)'

Lacius · Jul 22, 2019

HoTsHoTz79 said:
I am not sure if its iPatched... I bought a used one that was updated to FW 8.1.0 and serial # starts with XAW7-000852...

For launch option, i am selecting 'CFW (emuMMC)'

Your system is unpatched. Have you tried using Hekate without Nyx? I don't have a lot of experience with Nyx (none), but the AutoRCM options should be under Tools. We aren't talking about launch options.

HoTsHoTz79 · Jul 22, 2019

Lacius said:
Your system is unpatched. Have you tried using Hekate without Nyx? I don't have a lot of experience with Nyx (none), but the AutoRCM options should be under Tools.

Didn't know that was an option, when i inject hekate_ctcaer_5.0.1.bin, it takes me to the new fancy GUI (Nyx)... how do i go to Hekate from there?

Lacius · Jul 22, 2019

HoTsHoTz79 said:
Didn't know that was an option, when i inject hekate_ctcaer_5.0.1.bin, it takes me to the new fancy GUI (Nyx)... how do i go to Hekate from there?

Remove the Nyx file from your SD card or boot into Hekate without your SD card.

HoTsHoTz79 · Jul 22, 2019

Ah ok, thank you for your help... i'll remove the nyx.bin from the sys folder and give it a shot later tonight.

DrDoctor · Jul 22, 2019

Brand new factory sealed Switch at 3.0.0.

Did a eMMC BOOT0 & BOOT1, eMMC RAW GPP, and BIS Keys backup without even configuring the system.

My goal is to update the OFW to 8.1.0 while saving fuses.
I know I need to enable AutoRCM, but do I launch Atmosphere CFW from sysnand or emunand? I assume the latter, but I'm not sure.

Thanks!

Lacius · Jul 22, 2019

DrDoctor said:
Brand new factory sealed Switch at 3.0.0.

Did a eMMC BOOT0 & BOOT1, eMMC RAW GPP, and BIS Keys backup without even configuring the system.

My goal is to update the OFW to 8.1.0 while saving fuses.
I know I need to enable AutoRCM, but do I launch Atmosphere CFW from sysnand or emunand? I assume the latter, but I'm not sure.

Thanks!

If you aren't planning on keeping your sysNAND clean for online play, then you should update to 8.1.0 using ChoiDujourNX. Doing so automatically installs AutoRCM during the update process, preserving your fuse count.

If you aren't using an emuNAND, then you will launch Atmosphere CFW from the sysNAND.

DrDoctor · Jul 22, 2019

Lacius said:
If you aren't planning on keeping your sysNAND clean for online play, then you should update to 8.1.0 using ChoiDujourNX. Doing so automatically installs AutoRCM during the update process, preserving your fuse count.

Yes, I want to keep sysNAND clean. Which option do I use to load ChoiDujourNX? CFW (sysnand) or CFW (emunand)?

Lacius said:
If you aren't using an emuNAND, then you will launch Atmosphere CFW from the sysNAND.

Do I need to create an emuNAND before selecting it in the Launch menu?

I just tried out launching CFW (emunand) and configured the system, did I just get booted into CFW (sysnand) because I didn't have an emuNAND set up?

Is that why when I tried both Stock (sysnand) and Stock (emunand), they were sharing the same system configuration?

I thought I wasn't touching CFW (sysnand).

Lacius · Jul 22, 2019

DrDoctor said:
Yes, I want to keep sysNAND clean. Which option do I use to load ChoiDujourNX? CFW (sysnand) or CFW (emunand)?

Do I need to create an emuNAND before selecting it in the Launch menu?

I just tried out launching CFW (emunand) and configured the system, did I just get booted into CFW (sysnand) because I didn't have an emuNAND set up?

Is that why when I tried both Stock (sysnand) and Stock (emunand), they were sharing the same system configuration?

I thought I wasn't touching CFW (sysnand).

Is your plan to use online play? If not, then you don't need to worry about using an emuNAND.

DrDoctor · Jul 22, 2019

Lacius said:
Is your plan to use online play? If not, then you don't need to worry about using an emuNAND.

Yes, I want to use my Switch for online play.

Lacius · Jul 22, 2019

DrDoctor said:
Yes, I want to use my Switch for online play.

In that case, you should do the following in order:

From Hekate, install AutoRCM if you have not already done so.
Boot into Atmosphere CFW on your sysNAND (as long as you don't do anything else, your sysNAND should stay relatively clean). This is required to keep your sysNAND up to date for online play while also preserving fuses.
Update to 8.1.0 in the system settings. If you're using Atmosphere, AutoRCM will be preserved.
Create an emuNAND.

This will leave you with a relatively clean sysNAND for online play on 8.1.0, an offline emuNAND for hackery (also on 8.1.0), AutoRCM installed, and keeping only 3 fuses burnt. I recommend installng 90DNS and/or Incognito on your emuNAND so you don't accidentally connect to Nintendo's servers on the emuNAND and get the Switch banned.

Whenever you want to play your clean sysNAND for online play, you need to boot OFW from Hekate. Whenever you want to use your dirty emuNAND, you need to boot Atmosphere CFW emuNAND.

You should use ChoiDujourNX whenever you want to update your emuNAND in the future. You need to boot into Atmosphere sysNAND and update in the system settings whenever you want to update your sysNAND. You should never update your sysNAND nor emuNAND unless CFW has been updated to support new system versions.

DrDoctor · Jul 22, 2019

Lacius said:
In that case, you should do the following in order:

From Hekate, install AutoRCM if you have not already done so.

Boot into Atmosphere CFW on your sysNAND (as long as you don't do anything else, your sysNAND should stay relatively clean). This is required to keep your sysNAND up to date for online play while also preserving fuses.

Update to 8.1.0 in the system settings. If you're using Atmosphere, AutoRCM will be preserved.

Create an emuNAND.

I thought the process was to use ChoiDujourNX for any firmware update, but you're saying it's only for CFW. So it's safe to update OFW directly from the system settings?

Update OFW = launch » CFW (sysnand) » system settings
Update CFW = launch » CFW (emunand) » ChoiDujourNX

Correct?

Lacius said:
Whenever you want to play your clean sysNAND for online play, you need to boot OFW from Hekate. Whenever you want to use your dirty emuNAND, you need to boot Atmosphere CFW emuNAND.

In summary:
CFW (sysnand) = nope, better not touch
CFW (emunand) = safe offline tinkering
OFW (sysnand) = safe online play

What about OFW (emunand), what the purpose of that?

Also, just to confirm, booting from Hekate will always spare the fuses, correct?

Ninn · Jul 22, 2019

Lacius said:
In that case, you should do the following in order:

From Hekate, install AutoRCM if you have not already done so.

Boot into Atmosphere CFW on your sysNAND (as long as you don't do anything else, your sysNAND should stay relatively clean). This is required to keep your sysNAND up to date for online play while also preserving fuses.

Update to 8.1.0 in the system settings. If you're using Atmosphere, AutoRCM will be preserved.

Create an emuNAND.

This will leave you with a relatively clean sysNAND for online play on 8.1.0, an offline emuNAND for hackery (also on 8.1.0), AutoRCM installed, and keeping only 3 fuses burnt. I recommend installng 90DNS and/or Incognito on your emuNAND so you don't accidentally connect to Nintendo's servers on the emuNAND and get the Switch banned.

Whenever you want to play your clean sysNAND for online play, you need to boot OFW from Hekate. Whenever you want to use your dirty emuNAND, you need to boot Atmosphere CFW emuNAND.

You should use ChoiDujourNX whenever you want to update your emuNAND in the future. You need to boot into Atmosphere sysNAND and update in the system settings whenever you want to update your sysNAND. You should never update your sysNAND nor emuNAND unless CFW has been updated to support new system versions.

I will do it this way today or tomorrow, but When you do it this way, you create a folder with atmosphere in it(then follow the steps and update SysNand). Do you then use same folder with Atmos in it when you make 2 partitions for emuNAND ? So both emuNAND and sysNAND will use this same folder with Atmost in it?

This is the last step where i am a little confused.

Lacius · Jul 22, 2019

DrDoctor said:
I thought the process was to use ChoiDujourNX for any firmware update, but you're saying it's only for CFW. So it's safe to update OFW directly from the system settings?

You don't want to use ChoiDujourNX on a clean NAND. Using ChoiDujourNX on a NAND to use to play online can cause your Switch to be banned.

It is safe to update directly in the system settings with Atmosphere running. If you update without Atmosphere, AutoRCM will be removed.

DrDoctor said:
Update OFW = launch » CFW (sysnand) » system settings
Update CFW = launch » CFW (emunand) » ChoiDujourNX

Correct?

That is correct. The CFW must also be Atmosphere.

DrDoctor said:
In summary:
CFW (sysnand) = nope, better not touch
CFW (emunand) = safe offline tinkering
OFW (sysnand) = safe online play

For your purposes, that's absolutely right.

DrDoctor said:
What about OFW (emunand), what the purpose of that?

That's for people who want to use a clean emuNAND for online play, which is not recommended unless you have an ipatched system and it's your only option.

DrDoctor said:
Also, just to confirm, booting from Hekate will always spare the fuses, correct?

That is correct.

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

Ninn said:
I will do it this way today or tomorrow, but When you do it this way, you create a folder with atmosphere in it(then follow the steps and update SysNand). Do you then use same folder with Atmos in it when you make 2 partitions for emuNAND ? So both emuNAND and sysNAND will use this same folder with Atmost in it?

This is the last step where i am a little confused.

I'm not sure what you're asking. You're using the same Atmosphere files for all Atmosphere steps.

DrDoctor · Jul 22, 2019

Lacius said:
That is correct. The CFW must also be Atmosphere.

Thank you. Just to be 100% sure, Atmosphere is the CFW that comes with the "Kosmos Defaults" package, right?

EDIT:

Btw, I have the feeling that when I choose Launch » CFW (emunand), it defaulted to CFW (sysnand), as I didn't set up an emuNAND before and it didn't create anything in the SD card to emulate from. Doesn't sound like a good system...

Anyway, I ended opening the Album with R pressed, does that register as doing dirt with the system? Should I factory reset the Switch just to be safe?

Ninn · Jul 22, 2019

So its ok to reboot with the same sd card from emuNAND to SysNand, even if its loaded with homebrew and NSP files, both Nands use the same space.
Maybe it's more safe to use 2 different sd cards, one for SysNand and one for emuNAND.

Lacius · Jul 22, 2019

DrDoctor said:
Thank you. Just to be 100% sure, Atmosphere is the CFW that comes with the "Kosmos Defaults" package, right?

That is correct.

DrDoctor said:
Btw, I have the feeling that when I choose Launch » CFW (emunand), it defaulted to CFW (sysnand), as I didn't set up an emuNAND before and it didn't create anything in the SD card to emulate from. Doesn't sound like a good system...

Anyway, I ended opening the Album with R pressed, does that register as doing dirt with the system? Should I factory reset the Switch just to be safe?

I'm not sure what you're describing, but you need to setup an emuNAND properly before you can launch an emuNAND properly.

If all you did was boot into the Homebrew Launcher one time on your sysNAND, it's probably not dirty.

Doing a factory reset will not clean a dirty NAND. If you are paranoid, you can restore your clean NAND backup to your sysNAND, but it's likely unnecessary.

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

Ninn said:
So its ok to reboot with the same sd card from emuNAND to SysNand, even if its loaded with homebrew and NSP files, both Nands use the same space.
Maybe it's more safe to use 2 different sd cards, one for SysNand and one for emuNAND.

An emuNAND uses a different folder than the sysNAND for installed titles. In addition, titles have to be installed to the sysNAND to be visible on the sysNAND.

Hacking SWITCH NOOB PARADISE - Ask questions here

GIC-Developer

Well-Known Member

Well-Known Member

GIC-Developer

Well-Known Member

GIC-Developer

Well-Known Member

GIC-Developer

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum