Hacking Is my sysNand considered dirty.

[kimguan07]

Hi

I have a sysnand on FW 4.1 and a emmuNand on FW 9.2. I have never went online on sysnand after creating my emmunand and have left my sysnand on FW 4.1 and not updated it.
Recently i accidently launched CFW on sysnand, entered HB menu, then the system errored and crashed prompting me to restart to hekate. I did not go online during this time. I then realised my mistake and launched into emmunand as usual.

Im just wondering, is my sysnand now considered “dirty”, as i lauched CFW and hbmenu.
I have a clean nand backup(FW 4.1) made when creating my emmunand.

Should i restore my backup as i am considering to puchase legit animal crossing and go online in sysnand?

Thanks

 

[Kafluke]

It's probably ban safe but it is considered dirty now.

 

[kassio69]

Hi

I have a sysnand on FW 4.1 and a emmuNand on FW 9.2. I have never went online on sysnand after creating my emmunand and have left my sysnand on FW 4.1 and not updated it.
Recently i accidently launched CFW on sysnand, entered HB menu, then the system errored and crashed prompting me to restart to hekate. I did not go online during this time. I then realised my mistake and launched into emmunand as usual.

Im just wondering, is my sysnand now considered “dirty”, as i lauched CFW and hbmenu.
I have a clean nand backup(FW 4.1) made when creating my emmunand.

Should i restore my backup as i am considering to puchase legit animal crossing and go online in sysnand?

Thanks

If i were you i would follow this tutorial:

https://gbatemp.net/threads/multipl...restoring-a-clean-nand-for-online-use.562188/

Don't touch your sysnand anymore, keep it at 4.1 and use PegaScape> Caffeine> Hekate (so you eliminate the need of a dongle)

In Hekate you select one of the two emuMMC that you will create following the tutorial mentioned above.

So you have:
- clean emuNAND: can be updated by Nintendo servers, in wich you can play Animal Crossing online
- dirty emuNAND: can be updated by ChoidujourNX, for homebrew/nsp

 

[Nemix77]

Same thing happen to me a few days ago, while trying out vanilla Atmosphere and Kosmos.

If you have a nand backup do a restore and then remove the Sysnand CFW boot from Hetake's ini file in the future.

 

[Al3Drk]

Same thing happen to me a few days ago, while trying out vanilla Atmosphere and Kosmos.

If you have a nand backup do a restore and then remove the Sysnand CFW boot from Hetake's ini file in the future.

How to do the removing part? Does this prevent accidental boot into sysnand with atmosphere?

 

[kassio69]

How to do the removing part? Does this prevent accidental boot into sysnand with atmosphere?

Whats is your real sysnand firmware?

 

[Nemix77]

How to do the removing part? Does this prevent accidental boot into sysnand with atmosphere?

Yes it prevents from accidental booting into the Sysnand CFW via Hekate.

Just edit the hekate_ipl.ini in the bootloader folder and remove the Sysnand option.

You might also have to re-enable Autoboot to Emunand in Hekate depending if you had it enabled before.

 

[Al3Drk]

Whats is your real sysnand firmware?

9.2

Yes it prevents from accidental booting into the Sysnand CFW via Hekate.

Just edit the hekate_ipl.ini in the bootloader folder and remove the Sysnand option.

You might also have to re-enable Autoboot to Emunand in Hekate depending if you had it enabled before.

I assume Autoboot into emunand is different from auto rcm. Is it the thing that gives you the option to press the volume button to reboot to payload and power to reboot normally?I've never edited any settings in hekate.
And another question, may I ask is it any different if I directly inject fuse primary and don't do Hekate and then inject fuse primary?

 

[kassio69]

9.2

9.2 with burnt fuses? Do you have a lower firmware NAND backup?

If low burnt fuse count + lower firmware NAND backup: restore backup and follow my tutorial (see previous post), that way you may leave AutoRCM off > boot to real sysnand (no dongle) > Hekate > choose desired emuMMC
If high burnt fuse count and/or no lower firmware NAND backup: AutoRCM on > inject Hekate payload with dongle > emuMMC

I assume Autoboot into emunand is different from auto rcm. Is it the thing that gives you the option to press the volume button to reboot to payload and power to reboot normally?I've never edited any settings in hekate.
And another question, may I ask is it any different if I directly inject fuse primary and don't do Hekate and then inject fuse primary?

I'll try to clarify things for you:

AutoRCM puts the Switch, as the name says, automatically in recovery mode. You need a payload (Hekate, Atmosphere's fusee-primary, etc) to access Horizon, so your fuses don't burn.
You can turn it on/off in Hekate > Tools > Others

Autoboot to emuNAND is problably a SX OS feature, I can't give more information about this because I don't use it.

Reboot to payload is an Atmosphere's feature:
- make sure this is set in system_settings.ini: power_menu_reboot_function = str!payload
- copy your desired payload to atmosphere folder and rename it to reboot_payload.bin
- when you hold power and tap restart it will automatically load that payload (I use Hekate)

Some settings may change depending on whether you boot to Hekate > fusee-secondary or directly to fusee-primary.
I'm not the most experienced in this, but nogc config comes to mind:
- in Hekate > Options you can set Auto NoGC on/off
- in Atmosphere > config > BCT.ini you can add nogc = 0/1
- I believe that the option that will be loaded is related to the payload that you inject

And for your original question in this post, you should remove this lines from hekate_ipl.ini, so Hekate won't give you the option to start sysnand with CFW:

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

 

[Al3Drk]

9.2 with burnt fuses? Do you have a lower firmware NAND backup?

If low burnt fuse count + lower firmware NAND backup: restore backup and follow my tutorial (see previous post), that way you may leave AutoRCM off > boot to real sysnand (no dongle) > Hekate > choose desired emuMMC
If high burnt fuse count and/or no lower firmware NAND backup: AutoRCM on > inject Hekate payload with dongle > emuMMC



I'll try to clarify things for you:

AutoRCM puts the Switch, as the name says, automatically in recovery mode. You need a payload (Hekate, Atmosphere's fusee-primary, etc) to access Horizon, so your fuses don't burn.
You can turn it on/off in Hekate > Tools > Others

Autoboot to emuNAND is problably a SX OS feature, I can't give more information about this because I don't use it.

Reboot to payload is an Atmosphere's feature:
- make sure this is set in system_settings.ini: power_menu_reboot_function = str!payload
- copy your desired payload to atmosphere folder and rename it to reboot_payload.bin
- when you hold power and tap restart it will automatically load that payload (I use Hekate)

Some settings may change depending on whether you boot to Hekate > fusee-secondary or directly to fusee-primary.
I'm not the most experienced in this, but nogc config comes to mind:
- in Hekate > Options you can set Auto NoGC on/off
- in Atmosphere > config > BCT.ini you can add nogc = 0/1
- I believe that the option that will be loaded is related to the payload that you inject

And for your original question in this post, you should remove this lines from hekate_ipl.ini, so Hekate won't give you the option to start sysnand with CFW:

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

Thank you for the information I learned a lot.
This is assuming I'm using kosmos right? Because I'm using vanilla atmosphere and hekate payload so there is no option as such in bootloader folder.
I have another quick question. What are the down sides of using AutoRcm?

 

[sorabora]

I have another quick question. What are the down sides of using AutoRcm?

would love to get an opinion on this as well.

And perhaps a corollary question: if you’ve already burnt fuses by accidentally booting into SysNAND Horizon (OFW, 9.2), is there any upside to using AutoRCM?

 

[kassio69]

This is assuming I'm using kosmos right? Because I'm using vanilla atmosphere and hekate payload so there is no option as such in bootloader folder.

Kosmos is basically an all-in-one package.
If you're not that experienced you should download it, but you can put all those programs together on your own.
The system_settings.ini is located in atmosphere > config folder.

I have another quick question. What are the down sides of using AutoRcm?

You can't turn off the console properly, there is always some battery drain, with the possibility of total drainage and de-calibration.
Besides, obviously, the need of a payload injection to start the system.

And perhaps a corollary question: if you’ve already burnt fuses by accidentally booting into SysNAND Horizon (OFW, 9.2), is there any upside to using AutoRCM?

It's the only way for you to start your CFW, isn't it?