Hacking Question I just got a launch day unit and have a couple of questions

CapCaveman · Dec 17, 2018

Hey, guys!

I just got a Switch, and, believe it or not, it's the launch model. I pre-ordered the console when it was first announced, but only had it shipped to me very recently (importing is tough).

I also ordered the SX Pro (with dongle and jig), but that still hasn't arrived. From my research, the first step before messing with the Switch is to backup the NAND, so is there an easy way to dump the NAND that without a proper jig?

If not, since I own a bunch of games in cartridge form, is there any way to play them without updating the console? I know physical games come with firmware updates for the system, but I want to keep my Switch in its original "virgin" launch day state as much as possible, and use an updated EmuNAND for homebrew.

I'm mostly interested in Super Mario Odyssey, which requires version 3.0.1, according to this forum (4.0.0 with the day one patch). I'm dying to play it, but haven't even turned on my Switch yet, as to not risk having it updated - and the eFuses burned forever.

Any help is appreciated. Thanks in advance!

zattwat · Dec 17, 2018

CapCaveman said:
Hey, guys!

I just got a Switch, and, believe it or not, it's the launch model. I pre-ordered the console when it was first announced, but only had it shipped to me very recently (importing is tough).

I also ordered the SX Pro (with dongle and jig), but that still hasn't arrived. From my research, the first step before messing with the Switch is to backup the NAND, so is there an easy way to dump the NAND that without a proper jig?

If not, since I own a bunch of games in cartridge form, is there any way to play them without updating the console? I know physical games come with firmware updates for the system, but I want to keep my Switch in its original "virgin" launch day state as much as possible, and use an updated EmuNAND for homebrew.

I'm mostly interested in Super Mario Odyssey, which requires version 3.0.1, according to this forum (4.0.0 with the day one patch). I'm dying to play it, but haven't even turned on my Switch yet, as to not risk having it updated - and the eFuses burned forever.

Any help is appreciated. Thanks in advance!

SX OS has a built in NAND dumper function for backing up boot0/boot1 and raw NAND onto an SD card. Yes, you can play games without updating the OFW by using EMUNAND feature in SX OS 2.4.x. Just create an EMUNAND using a) system memory, or b)SD card space and update your EMUNAND using choidujournx, then play all your games using EMUNAND FW. The console’s OFW will remain intact using this method. Hope this helps...

Scitzo · Dec 17, 2018

CapCaveman said:
Hey, guys!

I just got a Switch, and, believe it or not, it's the launch model. I pre-ordered the console when it was first announced, but only had it shipped to me very recently (importing is tough).

I also ordered the SX Pro (with dongle and jig), but that still hasn't arrived. From my research, the first step before messing with the Switch is to backup the NAND, so is there an easy way to dump the NAND that without a proper jig?

If not, since I own a bunch of games in cartridge form, is there any way to play them without updating the console? I know physical games come with firmware updates for the system, but I want to keep my Switch in its original "virgin" launch day state as much as possible, and use an updated EmuNAND for homebrew.

I'm mostly interested in Super Mario Odyssey, which requires version 3.0.1, according to this forum (4.0.0 with the day one patch). I'm dying to play it, but haven't even turned on my Switch yet, as to not risk having it updated - and the eFuses burned forever.

Any help is appreciated. Thanks in advance!

For purposes of getting your initial CLEAN nand backup while its virgin, use hekate to do your initial virgin nand backup. Hekate obscures the fact that RCM was even used, so as far as nintendo knows the console never entered RCM. Sx os is fine for subsequent nand backups as you already have your virgin backup after that point.

ZachyCatGames · Dec 17, 2018

A launch system? That means it has fw 1.0.0, whatever you do, DO NOT update sysnand because 1.0 is the “holy grail” of firmwares, or you really need to, use choidujournx

On 1.0 you can get into RCM without a jig with a pegaswitch script. So do that, then use Hekate to backup your nand
Edit: https://github.com/pixel-stuck/reboot_to_rcm

CapCaveman · Dec 17, 2018

Thanks for the answers, everyone!

I still have some questions, though, which I’ll adress in quotes.

zattwat said:
SX OS has a built in NAND dumper function for backing up boot0/boot1 and raw NAND onto an SD card. Yes, you can play games without updating the OFW by using EMUNAND feature in SX OS 2.4.x. Just create an EMUNAND using a) system memory, or b)SD card space and update your EMUNAND using choidujournx, then play all your games using EMUNAND FW. The console’s OFW will remain intact using this method. Hope this helps...

It does help, thanks!

Does SX OS come with ChoidujourNX pre-installed?

Also, I’m still confused regarding the game cart update (is like to keep it “virgin” as well) and the exFAT update (apparently, 1.0.0 isn’t compatible with that format, and all my cards are 128GB in size).

Scitzo said:
For purposes of getting your initial CLEAN nand backup while its virgin, use hekate to do your initial virgin nand backup. Hekate obscures the fact that RCM was even used, so as far as nintendo knows the console never entered RCM. Sx os is fine for subsequent nand backups as you already have your virgin backup after that point.

Ah, gotcha! I’ll make sure to use Hekate first, then.

After backing up the NAND, I should update the system offline via ChoidujourNX, right? Is it as simple as just hitting update? Or does it require the creation of an EmuNAND first? Also, should I update to the latest version, or still keep it at a lower number?

I mentioned the game cart and exFAT updates in the above quote, which still confuse me.

After doing all that, what else do I need to dump backups of physical copies of games and play them?

ZachyCatGames said:
A launch system? That means it has fw 1.0.0, whatever you do, DO NOT update sysnand because 1.0 is the “holy grail” of firmwares, or you really need to, use choidujournx

On 1.0 you can get into RCM without a jig with a pegaswitch script. So do that, then use Hekate to backup your nand
Edit: https://github.com/pixel-stuck/reboot_to_rcm

That’s what I thought. The first (original) firmware version of any game console really tends to be the most sought after - as you said, the “Holy Grail” -, which is why I’m so determined to not lose access to it!

I’m not familiar with that pegaswitch script, and since I’m a complete noob, would you mind elaborating further or pointing me in the right direction, perhaps to a guide (the readme didn’t really do much for me)? I need all the help I can take.

Still, it sounds incredible that I don’t even need a jig and can actually do something on my Switch right away! Waiting for the dongles/jigs to arrive while staring at a brand new Switch that I haven’t even turned on yet has been extremely frustrating.

With that method, can I do something other than just backup my “virgin” NAND, like update the system offline via ChoidujourNX? I just want to play some Mario Odyssey without losing the Switch’s virginity.

ZachyCatGames · Dec 17, 2018

CapCaveman said:
Thanks for the answers, everyone!

I still have some questions, though, which I’ll adress in quotes.

It does help, thanks!

Does SX OS come with ChoidujourNX pre-installed?

Also, I’m still confused regarding the game cart update (is like to keep it “virgin” as well) and the exFAT update (apparently, 1.0.0 isn’t compatible with that format, and all my cards are 128GB in size).

Ah, gotcha! I’ll make sure to use Hekate first, then.

After backing up the NAND, I should update the system offline via ChoidujourNX, right? Is it as simple as just hitting update? Or does it require the creation of an EmuNAND first? Also, should I update to the latest version, or still keep it at a lower number?

I mentioned the game cart and exFAT updates in the above quote, which still confuse me.

After doing all that, what else do I need to dump backups of physical copies of games and play them?

That’s what I thought. The first (original) firmware version of any game console really tends to be the most sought after - as you said, the “Holy Grail” -, which is why I’m so determined to not lose access to it!

I’m not familiar with that pegaswitch script, and since I’m a complete noob, would you mind elaborating further or pointing me in the right direction, perhaps to a guide (the readme didn’t really do much for me)? I need all the help I can take.

Still, it sounds incredible that I don’t even need a jig and can actually do something on my Switch right away! Waiting for the dongles/jigs to arrive while staring at a brand new Switch that I haven’t even turned on yet has been extremely frustrating.

With that method, can I do something other than just backup my “virgin” NAND, like update the system offline via ChoidujourNX? I just want to play some Mario Odyssey without losing the Switch’s virginity.

You can find choidujournx here: https://gbatemp.net/threads/choiduj...ller-homebrew-for-the-nintendo-switch.513416/ and firmware files on xbins (can’t link because doing so would be piracy)

Also don’t use exfat, it causes corruption, you can use a tool called “guiformat” to format larger cards to fat32 on windows

I don’t know much about pegaswitch, but you could probably ask about it on the Reswitched discord

Edit: you can use this to dump physical cartridges https://github.com/DarkMatterCore/gcdumptool

CapCaveman · Dec 17, 2018

ZachyCatGames said:
You can find choidujournx here: https://gbatemp.net/threads/choiduj...ller-homebrew-for-the-nintendo-switch.513416/ and firmware files on xbins (can’t link because doing so would be piracy)

Also don’t use exfat, it causes corruption, you can use a tool called “guiformat” to format larger cards to fat32 on windows

I don’t know much about pegaswitch, but you could probably ask about it on the Reswitched discord

Edit: you can use this to dump physical cartridges https://github.com/DarkMatterCore/gcdumptool

Thanks again for the answers, I really appreciate it!

If I update via ChoiDujourNX, won’t I be required to use the exFAT format? Even if not, what if I have to transfer files that are over 4GB in size, won’t that cause issues?

As for the applications, since I’m still on 1.0.0, I can run all of them without the need for a jig, just by connecting my Switch to a PC via USB?

I’ve never used Discord, so I’m not even sure how to ask for help about the pegaswitch script there, haha!

ZachyCatGames · Dec 17, 2018

CapCaveman said:
Thanks again for the answers, I really appreciate it!

If I update via ChoiDujourNX, won’t I be required to use the exFAT format? Even if not, what if I have to transfer files that are over 4GB in size, won’t that cause issues?

As for the applications, since I’m still on 1.0.0, I can run all of them without the need for a jig, just by connecting my Switch to a PC via USB?

I’ve never used Discord, so I’m not even sure how to ask for help about the pegaswitch script there, haha!

You don’t need exfat for Choi, the fw file are only like 350mb

There isn’t really ever a reason to copy 4gb files to the sd card, most things can be split

What do you mean by application, homebrew apps or official switch apps? Well 1.0 should be compatible with most homebrew, although some do have issues since 1.0 is kind of “special”, and only like 10 official applications can run on 1.0

The way you would launch CFW/homebrew without a jig would be by using that pegaswitch thing to get into rcm, then push the payload over USB then launching CFW

DocKlokMan · Dec 17, 2018

CapCaveman said:
Hey, guys!

I just got a Switch, and, believe it or not, it's the launch model. I pre-ordered the console when it was first announced, but only had it shipped to me very recently (importing is tough).

I also ordered the SX Pro (with dongle and jig), but that still hasn't arrived. From my research, the first step before messing with the Switch is to backup the NAND, so is there an easy way to dump the NAND that without a proper jig?

If not, since I own a bunch of games in cartridge form, is there any way to play them without updating the console? I know physical games come with firmware updates for the system, but I want to keep my Switch in its original "virgin" launch day state as much as possible, and use an updated EmuNAND for homebrew.

I'm mostly interested in Super Mario Odyssey, which requires version 3.0.1, according to this forum (4.0.0 with the day one patch). I'm dying to play it, but haven't even turned on my Switch yet, as to not risk having it updated - and the eFuses burned forever.

Any help is appreciated. Thanks in advance!

Oh man, there's so many things you can do.

My personal recommendation would be to make a backup of your 1.0.0 NAND, make copies of it (it compresses small if you have no games stored on NAND, which you won't when you first get it) and keep it safe.

Next, install AutoRCM to make sure your Switch won't boot into stock firmware by mistake.

Then you can update your sysNAND to the latest 6.2.0 via ChoiDujourNX (you can choose the FAT32 or exFAT option, but honestly just use FAT32, it's less prone to corruption. All files on the Switch are automatically split to 4GiB pieces anyway even if you use exFAT and SX OS supports split NSPs and XCIs too), this will keep your eFuse count in-tact.

Once you're on 6.2.0, you'll want to link a Nintendo Online Account as some game REQUIRE one to play. You can create an emuNAND if you like. Once the emuNAND is made (it'll be 6.2.0) you can restore your NAND backup and return to 1.0.0 (or just leave it on 6.2.0 and AutoRCM so you always have the option to go back to 1.0.0 if you ever choose to).

Some things to keep in mind, once you update your system past 4.0.0, your game card slot will be updated. Once that's updated it won't work in any firmware lower than 4.0.0 after that. There's ways to block that from happening but then your game card slot won't work in any firmware 4.0.0 and above. You'll have to pick which you wanna do. If you ever accidentally boot stock firmware or do a regular system update, your eFuses will be updated.

Lastly, you may want to get with some of the popular scene developers as they have extreme interest in 1.0.0 launch Switches and may even buy one off you. At the very least they may want certain information dumped from your console.

CapCaveman · Dec 17, 2018

ZachyCatGames said:
You don’t need exfat for Choi, the fw file are only like 350mb
There isn’t really ever a reason to copy 4gb files to the sd card, most things can be split

What do you mean by application, homebrew apps or official switch apps? Well 1.0 should be compatible with most homebrew, although some do have issues since 1.0 is kind of “special”, and only like 10 official applications can run on 1.0

The way you would launch CFW/homebrew without a jig would be by using that pegaswitch thing to get into rcm, then push the payload over USB then launching CFW

Oh, I was more concerned about the size of game backups. I own a bunch of them in cartridge format and will be dumping them to the SD card (as, apparently, the game cart slot becomes unusable after 4.0.0). So they can be split?

And yeah, by applications I mean all homebrew required for my needs: backup NAND, enable AutoRCM, update via Choi, run CFW, etc. Someone mentioned in the noob thread that most aren’t compatible with the pegaswitch method, unfortunately.

AnalogMan said:
Oh man, there's so many things you can do.

My personal recommendation would be to make a backup of your 1.0.0 NAND, make copies of it (it compresses small if you have no games stored on NAND, which you won't when you first get it) and keep it safe.

Next, install AutoRCM to make sure your Switch won't boot into stock firmware by mistake.

Then you can update your sysNAND to the latest 6.2.0 via ChoiDujourNX (you can choose the FAT32 or exFAT option, but honestly just use FAT32, it's less prone to corruption. All files on the Switch are automatically split to 4GiB pieces anyway even if you use exFAT and SX OS supports split NSPs and XCIs too), this will keep your eFuse count in-tact.

Once you're on 6.2.0, you'll want to link a Nintendo Online Account as some game REQUIRE one to play. You can create an emuNAND if you like. Once the emuNAND is made (it'll be 6.2.0) you can restore your NAND backup and return to 1.0.0 (or just leave it on 6.2.0 and AutoRCM so you always have the option to go back to 1.0.0 if you ever choose to).

Some things to keep in mind, once you update your system past 4.0.0, your game card slot will be updated. Once that's updated it won't work in any firmware lower than 4.0.0 after that. There's ways to block that from happening but then your game card slot won't work in any firmware 4.0.0 and above. You'll have to pick which you wanna do. If you ever accidentally boot stock firmware or do a regular system update, your eFuses will be updated.

Lastly, you may want to get with some of the popular scene developers as they have extreme interest in 1.0.0 launch Switches and may even buy one off you. At the very least they may want certain information dumped from your console.

That’s a lot of information for me to digest, haha! I’ll try to break it down in order of what I must do, so please correct me if I’m wrong:

1) Backup the NAND (using Hekate instead of SX OS for the first backup?);

2) Install AutoRCM (How? Is it part of Hekate/SX OS or a separate homebrew?);

3) Update to the latest firmware via ChoiDujourNX using FAT32 (Again, how exactly? If I’ve booted into RCM, it will automatically install an “emulated” firmware, even without the need for an EmuNAND?);

4) Create EmuNAND (is that for online play?);

5) Link Nintendo Online profile (optional, depends on game);

6) Restore the 1.0.0 NAND backup - I’m not sure if I understand that one. Won’t the “official” Switch firmware still be 1.0.0? Why would I need to restore the NAND when using CFW? Can I keep AutoRCM on all the time?

7) Another one that still confuses me: the cartridge slot update. I don’t want to update it (would like to keep my Switch as “virgin” as pristine as possible, including all firmwares), só even when running CFW, I won’t be able to play physical games? Will I still be able to backup them from cartridges, though? I don’t mind losing access to physical games in order to preserve the original firmware, if I can still backup them and run their digital files.

I have no idea how to get in touch with developers, but I’m more than glad to help!

DocKlokMan · Dec 17, 2018

CapCaveman said:
Oh, I was more concerned about the size of game backups. I own a bunch of them in cartridge format and will be dumping them to the SD card (as, apparently, the game cart slot becomes unusable after 4.0.0). So they can be split?

And yeah, by applications I mean all homebrew required for my needs: backup NAND, enable AutoRCM, update via Choi, run CFW, etc. Someone mentioned in the noob thread that most aren’t compatible with the pegaswitch method, unfortunately.

That’s a lot of information for me to digest, haha! I’ll try to break it down in order of what I must do, so please correct me if I’m wrong:

1) Backup the NAND (using Hekate instead of SX OS for the first backup?);

2) Install AutoRCM (How? Is it part of Hekate/SX OS or a separate homebrew?);

3) Update to the latest firmware via ChoiDujourNX using FAT32 (Again, how exactly? If I’ve booted into RCM, it will automatically install an “emulated” firmware, even without the need for an EmuNAND?);

4) Create EmuNAND (is that for online play?);

5) Link Nintendo Online profile (optional, depends on game);

6) Restore the 1.0.0 NAND backup - I’m not sure if I understand that one. Won’t the “official” Switch firmware still be 1.0.0? Why would I need to restore the NAND when using CFW? Can I keep AutoRCM on all the time?

7) Another one that still confuses me: the cartridge slot update. I don’t want to update it (would like to keep my Switch as “virgin” as pristine as possible, including all firmwares), só even when running CFW, I won’t be able to play physical games? Will I still be able to backup them from cartridges, though? I don’t mind losing access to physical games in order to preserve the original firmware, if I can still backup them and run their digital files.

I have no idea how to get in touch with developers, but I’m more than glad to help!

Oh man, yeah, you need a lot of clarification on how this stuff actually works.

CFW isn't an alternate OS that you run, it's a series of patches that run on top of the official firmware. When you boot into CFW, it's still the official firmware running underneath it. So with that info let see if I can clarify:

Backup the NAND: You can use either Hekate or SX OS to backup the NAND, doesn't really matter.
Install AutoRCM: This is one of the menu option in Hekate and SX OS, it's done while you're still in RCM mode, before you start the CFW.
Update to the latest firmware via ChoiDujourNX using FAT32: You would boot your Switch into a CFW (whether it's Atmosphere or SX OS, doesn't matter). Once booted you can open the Album applet to access the Homebrew Menu and run the ChoiDujourNX homebrew. You'll need to download the firmware files ahead of time and put them on your SD card. When you start the update it'll show two buttons, FAT32 or exFAT, doesn't matter which you choose but I recommend you keep your SD as FAT32, exFAT is known to get corrupted and lose data when used with certain homebrew.
Create EmuNAND: EmuNAND is a clone of your Switch's built-in NAND. It's exactly identical, but separate. People keep their emuNAND COMPLETELY offline, never ever connecting it to the internet. This is because they run pirated games or homebrew, or use cheats in the emuNAND and any telemetry or error logs that are generated will stay safely contained in the emuNAND and never make it back to Nintendo, mitigating risk of being banned. If you want to play online, people use their sysNAND, updated to the latest firmware version and clean of all homebrew or pirated games, to play online.
Link Nintendo Online profile: This is recommended because if your Switch ever gets banned, you won't be able to do this any more, then any games out now or in the future that require an online profile to be linked will not be playable. So it's suggested to link it when you have the chance.
Restore the 1.0.0 NAND backup: As I mentioned, CFW is not an alternate operating system, when you update your Switch via ChoiDujourNX you are updating the STOCK NINTENDO FIRMWARE.
Cartridge slot firmware: If you don't update it you can't play physical games OR XCI games on firmware's higher than 4.0.0, you'd only be able to play digital eShop games.

Developers can be usually contacted via Discord, Twitter, or some may even be found here on GBATemp.

CapCaveman · Dec 17, 2018

AnalogMan said:
Oh man, yeah, you need a lot of clarification on how this stuff actually works.

CFW isn't an alternate OS that you run, it's a series of patches that run on top of the official firmware. When you boot into CFW, it's still the official firmware running underneath it. So with that info let see if I can clarify:

Backup the NAND: You can use either Hekate or SX OS to backup the NAND, doesn't really matter.

Install AutoRCM: This is one of the menu option in Hekate and SX OS, it's done while you're still in RCM mode, before you start the CFW.

Update to the latest firmware via ChoiDujourNX using FAT32: You would boot your Switch into a CFW (whether it's Atmosphere or SX OS, doesn't matter). Once booted you can open the Album applet to access the Homebrew Menu and run the ChoiDujourNX homebrew. You'll need to download the firmware files ahead of time and put them on your SD card. When you start the update it'll show two buttons, FAT32 or exFAT, doesn't matter which you choose but I recommend you keep your SD as FAT32, exFAT is known to get corrupted and lose data when used with certain homebrew.

Create EmuNAND: EmuNAND is a clone of your Switch's built-in NAND. It's exactly identical, but separate. People keep their emuNAND COMPLETELY offline, never ever connecting it to the internet. This is because they run pirated games or homebrew, or use cheats in the emuNAND and any telemetry or error logs that are generated will stay safely contained in the emuNAND and never make it back to Nintendo, mitigating risk of being banned. If you want to play online, people use their sysNAND, updated to the latest firmware version and clean of all homebrew or pirated games, to play online.

Link Nintendo Online profile: This is recommended because if your Switch ever gets banned, you won't be able to do this any more, then any games out now or in the future that require an online profile to be linked will not be playable. So it's suggested to link it when you have the chance.

Restore the 1.0.0 NAND backup: As I mentioned, CFW is not an alternate operating system, when you update your Switch via ChoiDujourNX you are updating the STOCK NINTENDO FIRMWARE.

Cartridge slot firmware: If you don't update it you can't play physical games OR XCI games on firmware's higher than 4.0.0, you'd only be able to play digital eShop games.

Developers can be usually contacted via Discord, Twitter, or some may even be found here on GBATemp.

Okay, I think I have a better understanding of many of those terms now.

1. Someone mentioned (either on this thread or the noob paradise one) that you shouldn’t use SX OS to dump the NAND for the first time, as it doesn’t make an entirely clean backup. They said you shold use Hekate instead, what do you think?

2. Ah, got it, so you’re able to install AutoRCM even before running the CFW. Good to know.

3. Is Choi included in any CFW?

4. How do you switch between EmuNAND and SysNAND? Does the former only run along the CFW, while the latter runs in “normal” boot mode (not RCM)?

5. Should I create an entirely new Nintendo ID for the Switch, then? I’ve had mine forever and only used it in devices that weren’t tampered with. I don’t want to risk having it banned and losing my digital games, etc.

6. This terminology is what gets me. CFW means Custom Firmware, doesn’t it? You’re replacing the stock firmware with a new, modified one, right? But if you’re updating Nintendo’s firmware, how can you go back to 1.0.0? Isn’t the point to have 1.0.0 “running” in your system so future exploits have a better chance of being compatible?

7. I’d like to prevent the cartridge slot from being updated (apparently, it’s an option when upgrading via Choi). Would I still be able to backup my physical games after updating to 6.2 and preventing the game cart slot update (keeping it at the original launch firmware)?

I’ve been out of the scene for a while. Last time I got into it was during the PSP days, which, coincidentally, also used CFWs as the base of its exploits.

DocKlokMan · Dec 17, 2018

CapCaveman said:
Okay, I think I have a better understanding of many of those terms now.

1. Someone mentioned (either on this thread or the noob paradise one) that you shouldn’t use SX OS to dump the NAND for the first time, as it doesn’t make an entirely clean backup. They said you shold use Hekate instead, what do you think?

2. Ah, got it, so you’re able to install AutoRCM even before running the CFW. Good to know.

3. Is Choi included in any CFW?

4. How do you switch between EmuNAND and SysNAND? Does the former only run along the CFW, while the latter runs in “normal” boot mode (not RCM)?

5. Should I create an entirely new Nintendo ID for the Switch, then? I’ve had mine forever and only used it in devices that weren’t tampered with. I don’t want to risk having it banned and losing my digital games, etc.

6. This terminology is what gets me. CFW means Custom Firmware, doesn’t it? You’re replacing the stock firmware with a new, modified one, right? But if you’re updating Nintendo’s firmware, how can you go back to 1.0.0? Isn’t the point to have 1.0.0 “running” in your system so future exploits have a better chance of being compatible?

7. I’d like to prevent the cartridge slot from being updated (apparently, it’s an option when upgrading via Choi). Would I still be able to backup my physical games after updating to 6.2 and preventing the game cart slot update (keeping it at the original launch firmware)?

I’ve been out of the scene for a while. Last time I got into it was during the PSP days, which, coincidentally, also used CFWs as the base of its exploits.

I didn't know about that. I've only ever used Hekate. If there's any debate on SX OS dumping properly, better play it safe than sorry and use Hekate.
Yes, you can also opt to install it through Choi during the update.
No, no CFW includes any homebrew, as CFW is just memory patches that run in RAM. All homebrew to do things like update your system (ChoiNX), backup saves (Checkpoint), play retro games (Retroarch) are separately downloadable apps you need to get and put on your SD card to use.
By default SX OS boots into the last one you used, but you can switch on the main SX OS menu when you restart the Switch. To access that menu just hold down the Volume Up button while inserting the SX Pro dongle until you see the main menu.
All the console bans currently done only affect the consoles. There's been only one report of an account ban and the circumstances for it are still unclear. So it's up to you if you want to use a different account or not. Since emuNAND is the one that's going to be used for illegitimate things you could use one NNID on the emuNAND and your regular one on sysNAND.
Traditionally CFW was where you took the stock firmware, modified its files, then wrote it back to the device so that it ran a modified version of its firmware. On current gen consoles you can't install modified firmware files and still have the console boot, so instead we boot the official firmware and through an exploit load memory patches and custom processes that run on top of the official firmware to accomplish what we want. This is why the CFW only lasts until you restart the console and then you need to exploit it again. You would return to 1.0.0 using the NAND backup you make. Everyone who has a 1.0.0 backup is simply holding on to it to restore in the future IF a software exploit is released that no longer needs the jig and payload injector, in the meantime they're running 6.2.0 with their eFuses protected so they can play online.
No. If you don't update the cartridge slot it 100% doesn't work to do anything. It won't play games, it won't dump games, it won't even mount backup games. You'd be restricted to NSP digital game installs ONLY. This is the hardest choice people typically make when dealing with consoles that came with FW lower than 4.0.0 on them.

CapCaveman · Dec 17, 2018

AnalogMan said:
I didn't know about that. I've only ever used Hekate. If there's any debate on SX OS dumping properly, better play it safe than sorry and use Hekate.

Yes, you can also opt to install it through Choi during the update.

No, no CFW includes any homebrew, as CFW is just memory patches that run in RAM. All homebrew to do things like update your system (ChoiNX), backup saves (Checkpoint), play retro games (Retroarch) are separately downloadable apps you need to get and put on your SD card to use.

By default SX OS boots into the last one you used, but you can switch on the main SX OS menu when you restart the Switch. To access that menu just hold down the Volume Up button while inserting the SX Pro dongle until you see the main menu.

All the console bans currently done only affect the consoles. There's been only one report of an account ban and the circumstances for it are still unclear. So it's up to you if you want to use a different account or not. Since emuNAND is the one that's going to be used for illegitimate things you could use one NNID on the emuNAND and your regular one on sysNAND.

Traditionally CFW was where you took the stock firmware, modified its files, then wrote it back to the device so that it ran a modified version of its firmware. On current gen consoles you can't install modified firmware files and still have the console boot, so instead we boot the official firmware and through an exploit load memory patches and custom processes that run on top of the official firmware to accomplish what we want. This is why the CFW only lasts until you restart the console and then you need to exploit it again. You would return to 1.0.0 using the NAND backup you make. Everyone who has a 1.0.0 backup is simply holding on to it to restore in the future IF a software exploit is released that no longer needs the jig and payload injector, in the meantime they're running 6.2.0 with their eFuses protected so they can play online.

No. If you don't update the cartridge slot it 100% doesn't work to do anything. It won't play games, it won't dump games, it won't even mount backup games. You'd be restricted to NSP digital game installs ONLY. This is the hardest choice people typically make when dealing with consoles that came with FW lower than 4.0.0 on them.

1. I’ll probably go with Hekate, then.

2. Awesome!

3. I see. But can I load everything to the SD card before even doing the “basic” stuff (backing up NAND, installing AutoRCM)?

4. But what’s the use of EmuNAND vs. SysNAND, other than having a backup of the original SysNAND for future exploits?

5. Well, I guess it’s related to this point. I’m still trying to wrap my mind around the concept of different NANDs. From what what I understood: EmuNAND basically serves for offline use and illegal stuff. SysNAND, if you ever want to play online and/or legit games, either downloaded from the e-Shop or via cartridges (not that it would matter if I prevented the game cart slot from being updated).

6. That’s a great explanation, thanks for making it clear for me. So the original NAND backup has to stay on the SD card that you’re currently using for all other things? Also, how is it possible to update the firmware without an EmuNAND? Where is it stored, if it doesn’t replace the original? Does it work like a temporary “patch” over the SysNAND’s firmware?

7. It’s because after version 4.0.0, the system firmware and the cartridge slot firmware have to match, correct? If I update to 6.2 (using an EmuNAND or not), but prevent the game cart slot update using homebrew, they’re not compatible between each other anymore. So I should NEVER put a game cartridge in the slot if that’s my setup and I want to preserve the slot’s original firmware, right? Is there a point in updating to anything 4.0.0 and above if I’m not planning on playing online?

DocKlokMan · Dec 17, 2018

CapCaveman said:
1. I’ll probably go with Hekate, then.

2. Awesome!

3. I see. But can I load everything to the SD card before even doing the “basic” stuff (backing up NAND, installing AutoRCM)?

4. But what’s the use of EmuNAND vs. SysNAND, other than having a backup of the original SysNAND for future exploits?

5. Well, I guess it’s related to this point. I’m still trying to wrap my mind around the concept of different NANDs. From what what I understood: EmuNAND basically serves for offline use and illegal stuff. SysNAND, if you ever want to play online and/or legit games, either downloaded from the e-Shop or via cartridges (not that it would matter if I prevented the game cart slot from being updated).

6. That’s a great explanation, thanks for making it clear for me. So the original NAND backup has to stay on the SD card that you’re currently using for all other things? Also, how is it possible to update the firmware without an EmuNAND? Where is it stored, if it doesn’t replace the original? Does it work like a temporary “patch” over the SysNAND’s firmware?

7. It’s because after version 4.0.0, the system firmware and the cartridge slot firmware have to match, correct? If I update to 6.2 (using an EmuNAND or not), but prevent the game cart slot update using homebrew, they’re not compatible between each other anymore. So I should NEVER put a game cartridge in the slot if that’s my setup and I want to preserve the slot’s original firmware, right? Is there a point in updating to anything 4.0.0 and above if I’m not planning on playing online?

Good call
NA
Yes
emuNAND stays offline to prevent any telemetry or error logs regarding homebrew from phoning home to Nintendo and getting your console banned. sysNAND is kept clean so you can play online (or later on in the future as an alternative way to launch emuNAND)
Basically, yes.
No, you can move your backup to a computer (I mentioned earlier about making multiple copies of it and keeping it safe). You don't need to keep it in the SD card. As for updating the firmware, you're ACTUALLY updating it. You are updating the firmware, stored in the NAND chip on your Switch's motherboard. It's just like officially updating it, but by using ChoiNX it prevents your eFuses from getting burned after the update. There's no faking here, you're legitimately updating your Switch's firmware.
Correct, they need to match otherwise they won't talk to one another. If you do put a game card in it'll simply not read it. Game cards alone won't update the card slot. As for updating passed 4.0, only if you want to play a legit game released in the last 14 months.If you're not going to do ANY online play you can keep sysNAND at 1.0.0 and only update emuNAND (but you'll still have the issue where none of your cartridge games will be playable in emuNAND).

radicalwookie · Dec 17, 2018

CapCaveman said:
Hey, guys!

I just got a Switch, and, believe it or not, it's the launch model. I pre-ordered the console when it was first announced, but only had it shipped to me very recently (importing is tough).

I also ordered the SX Pro (with dongle and jig), but that still hasn't arrived. From my research, the first step before messing with the Switch is to backup the NAND, so is there an easy way to dump the NAND that without a proper jig?

If not, since I own a bunch of games in cartridge form, is there any way to play them without updating the console? I know physical games come with firmware updates for the system, but I want to keep my Switch in its original "virgin" launch day state as much as possible, and use an updated EmuNAND for homebrew.

I'm mostly interested in Super Mario Odyssey, which requires version 3.0.1, according to this forum (4.0.0 with the day one patch). I'm dying to play it, but haven't even turned on my Switch yet, as to not risk having it updated - and the eFuses burned forever.

Any help is appreciated. Thanks in advance!

Good ol EU
Still rocking those 1.0.0 Switches in the stores. Man I love it!

CapCaveman · Dec 17, 2018

AnalogMan said:
Good call

NA

Yes

emuNAND stays offline to prevent any telemetry or error logs regarding homebrew from phoning home to Nintendo and getting your console banned. sysNAND is kept clean so you can play online (or later on in the future as an alternative way to launch emuNAND)

Basically, yes.

No, you can move your backup to a computer (I mentioned earlier about making multiple copies of it and keeping it safe). You don't need to keep it in the SD card. As for updating the firmware, you're ACTUALLY updating it. You are updating the firmware, stored in the NAND chip on your Switch's motherboard. It's just like officially updating it, but by using ChoiNX it prevents your eFuses from getting burned after the update. There's no faking here, you're legitimately updating your Switch's firmware.

Correct, they need to match otherwise they won't talk to one another. If you do put a game card in it'll simply not read it. Game cards alone won't update the card slot. As for updating passed 4.0, only if you want to play a legit game released in the last 14 months.If you're not going to do ANY online play you can keep sysNAND at 1.0.0 and only update emuNAND (but you'll still have the issue where none of your cartridge games will be playable in emuNAND).

1/2/3. \o/

4/5. So they’re basically “images” of the same NAND that can be loaded accordingly? If you want to play legit games, you don’t have to boot into regular mode; you can still boot into RCM, load SX OS with the SysNAND (EmuNAND off) and do whatever you want, like connecting to the e-Shop and playing online?

6. Right, right. I got the part about multiple backups, just wanted to make sure that you also don’t need one in the SD card at all times, for whatever reason. And when you “restore” your NAND backup, you’re actually downgrading the Switch’s firmware, then?

7. I’m thinking about keeping the SysNAND at 1.0.0 (shouldn’t have to take any extra steps in order to do that, right?), and updating the EmuNAND to something like 3.0.1. I believe most (if not all) of the games that I own are below that requirement (Zelda, Mario, Mario + Rabbids, Arms, Mario Kart, etc.), so there’s really no need for me to update to a newer version - at least for now (Octopath need 5.0.0, if I’m not mistaken, and that’s on my wishlist).

radicalwookie said:
Good ol EU
Still rocking those 1.0.0 Switches in the stores. Man I love it!

Hah, I actually got mine from the US! But, as I mentioned, it was a pre-order that got delivered on launch day. It’s just that I relied on a friend to have it shipped to me, and he took his merry ass time.

DocKlokMan · Dec 17, 2018

CapCaveman said:
1/2/3. \o/

4/5. So they’re basically “images” of the same NAND that can be loaded accordingly? If you want to play legit games, you don’t have to boot into regular mode; you can still boot into RCM, load SX OS with the SysNAND (EmuNAND off) and do whatever you want, like connecting to the e-Shop and playing online?

6. Right, right. I got the part about multiple backups, just wanted to make sure that you also don’t need one in the SD card at all times, for whatever reason. And when you “restore” your NAND backup, you’re actually downgrading the Switch’s firmware, then?

7. I’m thinking about keeping the SysNAND at 1.0.0 (shouldn’t have to take any extra steps in order to do that, right?), and updating the EmuNAND to something like 3.0.1. I believe most (if not all) of the games that I own are below that requirement (Zelda, Mario, Mario + Rabbids, Arms, Mario Kart, etc.), so there’s really no need for me to update to a newer version - at least for now (Octopath need 5.0.0, if I’m not mistaken, and that’s on my wishlist).

Hah, I actually got mine from the US! But, as I mentioned, it was a pre-order that got delivered on launch day. It’s just that I relied on a friend to have it shipped to me, and he took his merry ass time.

Seems like you've got it all sorted out now. If you stay below 4.0.0 then your game cart should be fine, but be careful about installing updates as they can make the game unplayable unless you update.

Hacking Question I just got a launch day unit and have a couple of questions

Well-Known Member

New Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Plugin Dev

Well-Known Member

Plugin Dev

Well-Known Member

Plugin Dev

Well-Known Member

Plugin Dev

Well-Known Member

Well-Known Member

Plugin Dev

Similar threads

Popular threads in this forum