Hacking Moved to emummc - how to restore stock sysnand?

[ChameleonSkin]

I installed sysnand cfw last year before emummc was available, and a couple months ago I moved over to using emummc by copying my sysnand cfw to emummc. So right now I basically have cfw on both my sysnand and emummc (although I updated to a newer firmware version on emummc only since then). At this point I'd like to revert my sysnand to stock so I can use it for eshop/ buying online games. I have two questions:

1. What is the easiest/safest way to restore my sysnand to stock without disrupting my emunand?
2. I used ChoiDujourNX to update my emunand from 7.0.1 to 8.x (can't remember which subversion right off). I never used ChoiDujourNX to update my sysnand cfw. I'm about 99% sure that this shouldn't cause any problems when returning my sysnand to stock but wanted to make sure I'm not overlooking anything.

 

[Andalitez]

Where's your original nand backup?

 

[nachuz]

restore the nand backup you made before modding your switch

 

[ChameleonSkin]

Where's your original nand backup?

restore the nand backup you made before modding your switch

I have that. Do I need to take any special precautions to ensure it doesn't wipe out my emunand/android/l4t etc.? Also, what is the difference between doing this and just doing a factory reset?

 

[BaamAlex]

There is no difference. A factory reset should be enough.

 

[Andalitez]

I have that. Do I need to take any special precautions to ensure it doesn't wipe out my emunand/android/l4t etc.? Also, what is the difference between doing this and just doing a factory reset?

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

Which firmware version is your nandbackup on?
The difference is, anything you did cfw related on your sysnand could have set off flags that might alert Nintendo to what you were doing (if/when going online again). If you factory reset, it doesn't remove those flags as it's not recorded in userland (this was the theory of the scene devs at the time hekate was released for example). Restoring the nandbackup should return the device to an *unflagged state (if the back was created before any cfw shananigans took place)
This should be much safer than just factory resetting it if you plan to go online.

It won't affect your emummc or anything else for that matter.

The only thing that comes to mind are the fuses you might have burnt when updating your switch

 

[urherenow]

Yea, if you have burnt fuses, your best bet is to stay offline and upgrade (NO AUTORCM, DO use exfat option and don't avoid the GC update) with choi, after restoring your original backup. For good measure, I don't have ANY CFW or homebrew files on the SD I use for sysnand, and I swap cards out for homebrew/emunand. My console is not banned, and I've been using it (to include eshop) since day 1. So if you want to be paranoid like me, delete all traces of homebrew as soon as you use choi.

 

[BaamAlex]

DO use exfat option

Ehm...why should anyone use exfat? This file system corrupts your data to 100%. There is no reason to use that.

 

[Andalitez]

Ehm...why should anyone use exfat? This file system corrupts your data to 100%. There is no reason to use that.

Just for better compatibility I guess.
If op was using exfat before and op doesn't select this then the console will want to format it since it can't read the data

 

[BaamAlex]

Just for better compatibility I guess.
If op was using exfat before and op doesn't select this then the console will want to format it since it can't read the data

Ehm...my second switch is totally clean and reads a fat32 formatted sd card perfectly. There is no reason to use exfat. Except you want to loose your data.

 

[Andalitez]

Ehm...my second switch is totally clean and reads a fat32 formatted sd card perfectly. There is no reason to use exfat. Except you want to loose your data.

Sorry maybe we misunderstood each other.
If OP is already using an exfat card, then not selecting exfat when upgrading using Choi will leave op with the issue I mentioned above.

For the record I'm also only using FAT32, but when updating fw,I always choose the exfat option just incase I need it for a large game install or something

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

Sorry, also depending on which version of hekate used to create the nand backup, OP might need exfat to restore anyway

 

[BaamAlex]

I always choose the exfat option just incase I need it for a large game install or something

Unnecessary. You can also install games via USB.

OP might need exfat to restore anyway

Even that is bullshit. Hekate creates a backup in small files so that they can also be restored with FAT32 cards.

 

[urherenow]

Ehm...why should anyone use exfat? This file system corrupts your data to 100%. There is no reason to use that.

I didn't say anyone "should use exFAT". I said to choose the exFAT option when upgrading the sysnand firmware. OP wants an official sysnand to go online with. You aren't given the choice when upgrading the official way. Installing the exFAT driver does NOT mean you have to use exFAT.

I'm still on fat32 myself, but I ALWAYS use the exfat option and update the game card controller. I get the feeling you have no idea what it means when you chose the exfat option, or you wouldn't be making such a fuss over it. At the same time, I don't understand why it is even an option to begin with (lower firmwares WILL WORK with exFAT if the driver is installed, but then it wouldn't be a "stock" firmware and therefore detectable if Ninty decided to look for it for some reason). With all CFW compatible with the latest version, there is still no reason to downgrade. Some people still holding out for a coldboot CFW, I guess. It's simply NOT a consideration for someone who wants to go online and use eshop and such.

Just for better compatibility I guess.
If op was using exfat before and op doesn't select this then the console will want to format it since it can't read the data

Good point, but not my point. See above.

Ehm...my second switch is totally clean and reads a fat32 formatted sd card perfectly. There is no reason to use exfat. Except you want to loose your data.

No kidding? Do you know what else? Your system also has the exFAT driver installed if it's on firmware 4.x or above.

 

[EmanueleBGN]

There is no difference. A factory reset should be enough.

No, it isn't. The Reset option in System Settings doesn't delete the events log

 

[urherenow]

edit: Oh, dear... dunno what happened here. Disregard this post.

 

[BaamAlex]

No, it isn't. The Reset option in System Settings doesn't delete the events log

Atmosphere has creport. This moves all errors to the sd card. So, yes. A factory reset should be enough.

 

[ChameleonSkin]

Thanks all - I got busy for a bit and I'm just getting back to this thread now. I've never updated my stock firmware since I got my switch, so there shouldn't be any burnt fuses. I have the sysnand that I made when I first purchased it (7.0.0). So reading through everything above, it sounds like a factory reset should work ok? @BaamAlex do I need to do anything to make use of creport that you mentioned above? Or is that already active, i.e. all of my events are already being sent to the sd card because I'm using Atmosphere? What about any events that were created when I was running cfw on sysnand before I moved to emuMMC? Are those also on my SD card?

 

[Draxzelex]

Thanks all - I got busy for a bit and I'm just getting back to this thread now. I've never updated my stock firmware since I got my switch, so there shouldn't be any burnt fuses. I have the sysnand that I made when I first purchased it (7.0.0). So reading through everything above, it sounds like a factory reset should work ok? @BaamAlex do I need to do anything to make use of creport that you mentioned above? Or is that already active, i.e. all of my events are already being sent to the sd card because I'm using Atmosphere? What about any events that were created when I was running cfw on sysnand before I moved to emuMMC? Are those also on my SD card?

Creport is automatically included with Atmosphere. Any of the crash reports on the SD card will stay on the SD card and not affect the console.