Hacking Is it possible to restore sysnand with a clean nand backup without affecting emunand?

[derp421]

I want to have my sysnand as clean as possible so I want to restore my sysnand with a clean nand backup. My sysnand is on 5.1.0 and my emunand is on 6.1.0. I am wondering if I restore my sysnand will it impact the emunand or are they completely independent of each other? My SX OS is v2.3 BETA and my emunand is on the SD card.

 

[Draxzelex]

I want to have my sysnand as clean as possible so I want to restore my sysnand with a clean nand backup. My sysnand is on 5.1.0 and my emunand is on 6.1.0. I am wondering if I restore my sysnand will it impact the emunand or are they completely independent of each other? My SX OS is v2.3 BETA and my emunand is on the SD card.

If you restore the NAND, it will wipe out the modification made to boot1 which allows users to boot into EmuNAND in the first place. The copy of the USER partition which is the other half of what makes up their EmuNAND will still persist on your SD card but you will need to re-install EmuNAND, or at least partially, by re-modifying boot1.

 

[Hernie]

So, if I back up my boot1 now, since I have SD emuNand enabled. That boot1 will have the modification on it, right? So once I restore the nand, all I have to do is restore this modified boot1? Is there a way to reactivate this in the sxos menu, Instead of having to do all these backups? I don't want the emuNand to be deleted that's on my SD. Although, I can probably just back that one up and recopy it to the SD once I recreated emuNand. Just thinking out loud.

 

[Draxzelex]

So, if I back up my boot0 now, since I have SD emuNand enabled. That boot0 will have the modification on it, right? So once I restore the nand, all I have to do is restore this modified boot0? Is there a way to reactivate this in the sxos menu, Instead of having to do all these backups? I don't want the emuNand to be deleted that's on my SD. Although, I can probably just back that one up and recopy it to the SD once I recreated emuNand. Just thinking out loud.

First off, its boot1. Secondly, backing up and restoring it takes less than 5 minutes. Lastly, don't know if SX OS has an option for this or not.

 

[Hernie]

First off, its boot1. Secondly, backing up and restoring it takes less than 5 minutes. Lastly, don't know if SX OS has an option for this or not.

My bad....boot1, I'd be using hekate anyways, since that's what I used to make my update.

Thanks

Sent from my 2PZC5 using Tapatalk

 

[Naxster]

Wait i might be waaaaaay to behind now, but have they released a emuNAND for the switch console?
I haven't been that much active for the last couple of months

Is the emuNAND like the one in 3DS? For instance, we can still be in firmware 3.0.1 sysNAND but update and "play around" with the emuNAND without affecting the sysNAND?

 

[Hernie]

Wait i might be waaaaaay to behind now, but have they released a emuNAND for the switch console?
I haven't been that much active for the last couple of months

Is the emuNAND like the one in 3DS? For instance, we can still be in firmware 3.0.1 sysNAND but update and "play around" with the emuNAND without affecting the sysNAND?

Yes, sir! Sxos. I'm on 4.1.0 sys and 6.1.0 Emu

 

[Naxster]

Yes, sir! Sxos. I'm on 4.1.0 sys and 6.1.0 Emu

Really?!
Well then, it's settled, I will buy the SX pro so I can make it work
I'm guessing that Atmosphere doesn't have emuNAND yet?

Now all that is left is a way to boot the switch without any jig

 

[xabier]

If you restore the NAND, it will wipe out the modification made to boot1 which allows users to boot into EmuNAND in the first place. The copy of the USER partition which is the other half of what makes up their EmuNAND will still persist on your SD card but you will need to re-install EmuNAND, or at least partially, by re-modifying boot1.

AFAIK the nand partitions are not modified at all In sxos 2.3 microsd emunand.

 

[Hernie]

For anyone that's interested, i ended up only restoring the nand and not the boot0/1 and it worked fine.

 

[Draxzelex]

For anyone that's interested, i ended up only restoring the nand and not the boot0/1 and it worked fine.

That's only possible if the firmware of your NAND dump and the firmware you were running before the restoration match. You must restore boot0/boot1 if they do not match along with the NAND.

 

[nataliabf]

Just to clarify, it is perfectly possible to restore rawnand and boot 0/1 on sysnand and keep the emunand working if the emunand is on the SD. I've done that twice without any problems. Once downgrading the sysnand from 6.1 to 3.0.1 and leaving emunand on 6.1, and then again with sysnand going from 6.2 to 3.0.1, leaving emunand on 6.2. (Both times I made the emunand with an updated sysnand, then downgraded the sys).

 

[Draxzelex]

Just to clarify, it is perfectly possible to restore rawnand and boot 0/1 on sysnand and keep the emunand working if the emunand is on the SD. I've done that twice without any problems. Once downgrading the sysnand from 6.1 to 3.0.1 and leaving emunand on 6.1, and then again with sysnand going from 6.2 to 3.0.1, leaving emunand on 6.2. (Both times I made the emunand with an updated sysnand, then downgraded the sys).

Yes its fine. SD EmuNAND runs completely off of the SD card meaning it makes no modifications to the boot1 that would be wiped when you restore the entire NAND.

 

[thaikhoa]

If you restore the NAND, it will wipe out the modification made to boot1 which allows users to boot into EmuNAND in the first place. The copy of the USER partition which is the other half of what makes up their EmuNAND will still persist on your SD card but you will need to re-install EmuNAND, or at least partially, by re-modifying boot1.

Restoring Boot0/1 won't affect to the Emunand on SD files or SD partition.

 

[Draxzelex]

Restoring Boot0/1 won't affect to the Emunand on SD files or SD partition.

Thank you for quoting something from December.

 

[thaikhoa]

Thank you for quoting something from December.

Oops, my bad.