Hacking SWITCH NOOB PARADISE - Ask questions here

CapCaveman

Well-Known Member
Newcomer
Joined
Dec 17, 2018
Messages
54
Trophies
0
XP
105
Country
Sweden
No but there is a way to preserve your 1.0 and play your game. The answer is to update your firmware without burning fuses. Fuses primarily are designed to prevent downgrading but there is a homebrew application named ChoiDujourNX that can put you on whatever firmware you give it without burning any fuses. How it prevents fuses from being burnt is that it enables AutoRCM after installing the firmware. AutoRCM, as the name implies, causes the Switch to AUTOmatically enter RCM. It does so "bricking" the Switch but its an easily reversable brick. With AutoRCM, you cannot boot the Switch normally; instead you will have to send a payload to use the console so if you don't use sleep mode or turn off the console a lot, you may have to change your habits. Another thing to note is that with AutoRCM, turning off the console will cause it to reboot into RCM. This is only a minor inconvenience as it is still possible to turn off a console with AutoRCM. All you have to do is power it off from RCM. Options include a manual shutdown in RCM (holding power for 12 seconds) or using the Power Off function in Hekate which involves sending Hekate as a payload.

Thanks again for the very thorough explanation. I’m new to these forums (and to the Switch scene as a whole), and I can already tell that you’re extremely patient and helpful in your replies, not just to myself.

I’ve been doing as much research as I can, but I still have some questions, as most of these concepts are alien to me and I’m still getting used to the terminology.

Regarding AutoRCM, I’ve read about some battery draining issues, have those been addressed/fixed? I will mostly be using my Switch docked, so I assume it’s best to just always keep it in sleep mode? And if I do power it off using any of the methods you mentioned, does that turn off AutoRCM and make the console boot into the OFW? I really don’t want to risk burning those eFuses.

Also, in my thread, someone mentioned a method to backup the NAND without the need of a jig or dongle on 1.0.0, using something called a pegaswitch script. Would I be able to update the console without burning fuses thought that method, as well? I’m just looking for the fastest way to play Mario Odyssey without losing my Switch’s “virginity”.

There are some other issues that still confuse me, like the game cart and exFAT updates. Apparently, I’ll have to update to exFAT regardless (especially since my cards are 128GB in size) and after updating the firmware even without burning fuses (offline), I won’t be able to play physical copies of games anymore?
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
What’s the most practical and simple method? To keep nand backup safe?

If I use exfat to keep it all in one bit will I be able to switch to fat32 for rest of setup easy?

Also with regards to emuNAND on file in sd card or as hidden partion. If card corrupted how would u recover in each instance?
Which one is recommended if starting fresh?
There is no best method for dumping the NAND since they both have their pros and cons. With exFAT, you get a single file but you have to wait for it to finish. With FAT32, its dumped in parts that you can dump at your own pace. Forgot to mention that you need exFAT to restore the NAND so it may be slightly better with exFAT if you only have one SD card. Meaning you can just use exFAT for dumping/restoring the NAND and FAT32 for regular CFW/homebrew usage.

And I did some research and with regards to corruption, there is a difference with EmuNAND. If its set as a partition, it won't corrupt the entire SD card if something happens in EmuNAND and vice-versa. If its installed normally, you risk EmuNAND corrupting the SD card and regular usage of the SD card corrupting EmuNAND. The only downside to partitioning is that it cannot be easily removed. Formatting the SD card won't remove it, it needs to be removed with a specific tool which I believe only exists within SX OS. So since they have their own benefits and negatives, weigh which one you would prefer to use.

Thanks again for the very thorough explanation. I’m new to these forums (and to the Switch scene as a whole), and I can already tell that you’re extremely patient and helpful in your replies, not just to myself.

I’ve been doing as much research as I can, but I still have some questions, as most of these concepts are alien to me and I’m still getting used to the terminology.

Regarding AutoRCM, I’ve read about some battery draining issues, have those been addressed/fixed? I will mostly be using my Switch docked, so I assume it’s best to just always keep it in sleep mode? And if I do power it off using any of the methods you mentioned, does that turn off AutoRCM and make the console boot into the OFW? I really don’t want to risk burning those eFuses.

Also, in my thread, someone mentioned a method to backup the NAND without the need of a jig or dongle on 1.0.0, using something called a pegaswitch script. Would I be able to update the console without burning fuses thought that method, as well? I’m just looking for the fastest way to play Mario Odyssey without losing my Switch’s “virginity”.

There are some other issues that still confuse me, like the game cart and exFAT updates. Apparently, I’ll have to update to exFAT regardless (especially since my cards are 128GB in size) and after updating the firmware even without burning fuses (offline), I won’t be able to play physical copies of games anymore?
The battery drain with AutoRCM was due to people not realizing that turning off the Switch normally causes it to reboot into RCM which drains battery at a rate of about 5% per hour. I don't even know if this can be fixed but with careful management, your battery will never drain with AutoRCM. By careful management, I mean ensuring the console is off when you turn it off (or just use Sleep Mode).

The homebrew application to update without burning fuses needs permissions that I don't believe can be granted with Pegaswitch alone. You can certainly try but since Fusee Gelee is superior to Pegaswitch in almost every conceivable way, good luck trying to set it up or someone even willing to help.

You don't have to use exFAT because there are ways to bypass the 4 GB limit on FAT32. It will depend on the type of file you are transferring. Plus exFAT can corrupt your SD card unlike FAT32. But if you wish to use exFAT, when you use ChoiDujourNX to update your firmware without burning fuses, it gives you the option of patching the firmware to have exFAT support or not. So if you want exFAT support for that firmware, you go with the exFAT option.

Another thing you reminded me of is the gamecart slot update. If you boot firmware 4.0 or higher, it will irreversibly update the gamecart slot. This prevents the slot from being used on firmwares 4.0. Now depending on the CFW you use, you can prevent it from being updated. But to prevent it from being updated, it breaks the slot temporarily (for as long as you boot the CFW with the appropriate patch). This means you won't be able to use cartridges on firmwares of 4.0 and higher if you wish to be able to use it on firmwares below 4.0 and vice-versa.
 
  • Like
Reactions: CapCaveman

CapCaveman

Well-Known Member
Newcomer
Joined
Dec 17, 2018
Messages
54
Trophies
0
XP
105
Country
Sweden
The battery drain with AutoRCM was due to people not realizing that turning off the Switch normally causes it to reboot into RCM which drains battery at a rate of about 5% per hour. I don't even know if this can be fixed but with careful management, your battery will never drain with AutoRCM. By careful management, I mean ensuring the console is off when you turn it off (or just use Sleep Mode).

The homebrew application to update without burning fuses needs permissions that I don't believe can be granted with Pegaswitch alone. You can certainly try but since Fusee Gelee is superior to Pegaswitch in almost every conceivable way, good luck trying to set it up or someone even willing to help.

You don't have to use exFAT because there are ways to bypass the 4 GB limit on FAT32. It will depend on the type of file you are transferring. Plus exFAT can corrupt your SD card unlike FAT32. But if you wish to use exFAT, when you use ChoiDujourNX to update your firmware without burning fuses, it gives you the option of patching the firmware to have exFAT support or not. So if you want exFAT support for that firmware, you go with the exFAT option.

Another thing you reminded me of is the gamecart slot update. If you boot firmware 4.0 or higher, it will irreversibly update the gamecart slot. This prevents the slot from being used on firmwares 4.0. Now depending on the CFW you use, you can prevent it from being updated. But to prevent it from being updated, it breaks the slot temporarily (for as long as you boot the CFW with the appropriate patch). This means you won't be able to use cartridges on firmwares of 4.0 and higher if you wish to be able to use it on firmwares below 4.0 and vice-versa.

Okay, let me make sure I got all that right:

1. The battery draining “issues” were experienced by people who weren’t really turning off their consoles or even putting them into sleep mode, which caused the console to boot into RCM and remain fully on and operational?

2. What is the recommended approach, then? Like I said, my Switch will mostly stay docked, connected to a TV. Can I just use sleep mode... forever? How do I that on CFW, in order to have AutoRCM always on?

3. Does powering off using the methods you listed disable AutoRCM?

4. So, with pegaswitch, I’ll only be able to backup the NAND, and not use any other homebrew applications? If that really is the case, I won’t even bother with it and just wait for my dongles/jigs.

5. About exFAT and FAT32, you mentioned in a reply to another user that you need exFAT to restore the NAND, so should I just go with that, even if the risk of corruption is higher? The files that I’ll be transferring the most will be backups of physical games, so probably bigger than 4GB.

6. Finally, the game cart slot update. As I understand, if I do everything right, my Switch will be able to boot in two different modes: a) RCM with a payload injecting a CFW running an emulated version of a firmware; b) “traditional” boot (no RCM) with official firmware still on 1.0.0. Correct? Now:

6.1 If the emulated firmware in the CFW is equal or greater than 4.0.0, the cartridge slot becomes unusable?

6.2 In the official firmware, I’ll still be able to play physical games, but only if they’re compatible with 1.0.0 and don’t require an update? Are there any games that only require 1.0.0?
 

Zap2000

Well-Known Member
Member
Joined
Oct 19, 2018
Messages
640
Trophies
0
Age
43
XP
808
Country
United Kingdom
There is no best method for dumping the NAND since they both have their pros and cons. With exFAT, you get a single file but you have to wait for it to finish. With FAT32, its dumped in parts that you can dump at your own pace. Forgot to mention that you need exFAT to restore the NAND so it may be slightly better with exFAT if you only have one SD card. Meaning you can just use exFAT for dumping/restoring the NAND and FAT32 for regular CFW/homebrew usage.

And I did some research and with regards to corruption, there is a difference with EmuNAND. If its set as a partition, it won't corrupt the entire SD card if something happens in EmuNAND and vice-versa. If its installed normally, you risk EmuNAND corrupting the SD card and regular usage of the SD card corrupting EmuNAND. The only downside to partitioning is that it cannot be easily removed. Formatting the SD card won't remove it, it needs to be removed with a specific tool which I believe only exists within SX OS. So since they have their own benefits and negatives, weigh which one you would prefer to use.

The battery drain with AutoRCM was due to people not realizing that turning off the Switch normally causes it to reboot into RCM which drains battery at a rate of about 5% per hour. I don't even know if this can be fixed but with careful management, your battery will never drain with AutoRCM. By careful management, I mean ensuring the console is off when you turn it off (or just use Sleep Mode).

The homebrew application to update without burning fuses needs permissions that I don't believe can be granted with Pegaswitch alone. You can certainly try but since Fusee Gelee is superior to Pegaswitch in almost every conceivable way, good luck trying to set it up or someone even willing to help.

You don't have to use exFAT because there are ways to bypass the 4 GB limit on FAT32. It will depend on the type of file you are transferring. Plus exFAT can corrupt your SD card unlike FAT32. But if you wish to use exFAT, when you use ChoiDujourNX to update your firmware without burning fuses, it gives you the option of patching the firmware to have exFAT support or not. So if you want exFAT support for that firmware, you go with the exFAT option.

Another thing you reminded me of is the gamecart slot update. If you boot firmware 4.0 or higher, it will irreversibly update the gamecart slot. This prevents the slot from being used on firmwares 4.0. Now depending on the CFW you use, you can prevent it from being updated. But to prevent it from being updated, it breaks the slot temporarily (for as long as you boot the CFW with the appropriate patch). This means you won't be able to use cartridges on firmwares of 4.0 and higher if you wish to be able to use it on firmwares below 4.0 and vice-versa.


There is no best method for dumping the NAND since they both have their pros and cons. With exFAT, you get a single file but you have to wait for it to finish. With FAT32, its dumped in parts that you can dump at your own pace. Forgot to mention that you need exFAT to restore the NAND so it may be slightly better with exFAT if you only have one SD card. Meaning you can just use exFAT for dumping/restoring the NAND and FAT32 for regular CFW/homebrew usage.

And I did some research and with regards to corruption, there is a difference with EmuNAND. If its set as a partition, it won't corrupt the entire SD card if something happens in EmuNAND and vice-versa. If its installed normally, you risk EmuNAND corrupting the SD card and regular usage of the SD card corrupting EmuNAND. The only downside to partitioning is that it cannot be easily removed. Formatting the SD card won't remove it, it needs to be removed with a specific tool which I believe only exists within SX OS. So since they have their own benefits and negatives, weigh which one you would prefer to use.

The battery drain with AutoRCM was due to people not realizing that turning off the Switch normally causes it to reboot into RCM which drains battery at a rate of about 5% per hour. I don't even know if this can be fixed but with careful management, your battery will never drain with AutoRCM. By careful management, I mean ensuring the console is off when you turn it off (or just use Sleep Mode).

The homebrew application to update without burning fuses needs permissions that I don't believe can be granted with Pegaswitch alone. You can certainly try but since Fusee Gelee is superior to Pegaswitch in almost every conceivable way, good luck trying to set it up or someone even willing to help.

You don't have to use exFAT because there are ways to bypass the 4 GB limit on FAT32. It will depend on the type of file you are transferring. Plus exFAT can corrupt your SD card unlike FAT32. But if you wish to use exFAT, when you use ChoiDujourNX to update your firmware without burning fuses, it gives you the option of patching the firmware to have exFAT support or not. So if you want exFAT support for that firmware, you go with the exFAT option.

Another thing you reminded me of is the gamecart slot update. If you boot firmware 4.0 or higher, it will irreversibly update the gamecart slot. This prevents the slot from being used on firmwares 4.0. Now depending on the CFW you use, you can prevent it from being updated. But to prevent it from being updated, it breaks the slot temporarily (for as long as you boot the CFW with the appropriate patch). This means you won't be able to use cartridges on firmwares of 4.0 and higher if you wish to be able to use it on firmwares below 4.0 and vice-versa.

There is no best method for dumping the NAND since they both have their pros and cons. With exFAT, you get a single file but you have to wait for it to finish. With FAT32, its dumped in parts that you can dump at your own pace. Forgot to mention that you need exFAT to restore the NAND so it may be slightly better with exFAT if you only have one SD card. Meaning you can just use exFAT for dumping/restoring the NAND and FAT32 for regular CFW/homebrew usage.

And I did some research and with regards to corruption, there is a difference with EmuNAND. If its set as a partition, it won't corrupt the entire SD card if something happens in EmuNAND and vice-versa. If its installed normally, you risk EmuNAND corrupting the SD card and regular usage of the SD card corrupting EmuNAND. The only downside to partitioning is that it cannot be easily removed. Formatting the SD card won't remove it, it needs to be removed with a specific tool which I believe only exists within SX OS. So since they have their own benefits and negatives, weigh which one you would prefer to use.


When u say
Meaning you can just use exFAT for dumping/restoring the NAND and FAT32 for regular CFW/homebrew usage.

Do u mean I should partition and run ex fat and store nand there and run another partition with fat32 for my cfw setup?
I thought it was advise to just use fat 32 system in sd card due to corrupting
Should I keep my nand in my sd card after I get cfw installed?
I have a spare 32gb card and I’m using a 256gb for the switch but I don’t think that 32 is big enough for nand? I could store in my external hard and order a 64gb if needed?

Have u any links and guides for preparing my sd card and doing nand back up?

With the emuNAND on sd card I take it swapping sd cards for different games is out now?

With emuNAND the 2 different methods sd card how would u recover from corruption of sd card?
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
Okay, let me make sure I got all that right:

1. The battery draining “issues” were experienced by people who weren’t really turning off their consoles or even putting them into sleep mode, which caused the console to boot into RCM and remain fully on and operational?

2. What is the recommended approach, then? Like I said, my Switch will mostly stay docked, connected to a TV. Can I just use sleep mode... forever? How do I that on CFW, in order to have AutoRCM always on?

3. Does powering off using the methods you listed disable AutoRCM?

4. So, with pegaswitch, I’ll only be able to backup the NAND, and not use any other homebrew applications? If that really is the case, I won’t even bother with it and just wait for my dongles/jigs.

5. About exFAT and FAT32, you mentioned in a reply to another user that you need exFAT to restore the NAND, so should I just go with that, even if the risk of corruption is higher? The files that I’ll be transferring the most will be backups of physical games, so probably bigger than 4GB.

6. Finally, the game cart slot update. As I understand, if I do everything right, my Switch will be able to boot in two different modes: a) RCM with a payload injecting a CFW running an emulated version of a firmware; b) “traditional” boot (no RCM) with official firmware still on 1.0.0. Correct? Now:

6.1 If the emulated firmware in the CFW is equal or greater than 4.0.0, the cartridge slot becomes unusable?

6.2 In the official firmware, I’ll still be able to play physical games, but only if they’re compatible with 1.0.0 and don’t require an update? Are there any games that only require 1.0.0?
  1. Well RCM isn't exactly fully on and operational but yes, this was the cause of the battery drain
  2. You can just use Sleep Mode forever. Its honestly underutilized by people who are used to turning off their devices. The main thing is that you will have to ensure it has charge because if it runs out and you updated without burning fuses but you're not using AutoRCM, you'll burn fuses when you recharge the console unless you manage to reboot it into RCM as soon as you start recharging it
  3. No. Disabling AutoRCM is usually done with the same tool used to enable it
  4. Like I said, you could give it a try but Pegaswitch is not easy to setup
  5. I mean if you don't mind the risk of corruption looming over your head, sure. Corruption is easy to correct as a simple SD card format will fix it. But if you have a lot of files on the SD card, the simple solution then involves backing up those files.
  6. Although now outdated, nswdb.com has a listing of all games that can run on firmware 1.0. Also yes, you will update the gamecart slot whenever you are running a firmware of 4.0 or higher, CFW (without the appropriate patch) or OFW. This doesn't make it completely unusable, just unusable on firmwares 4.0
When u say
Meaning you can just use exFAT for dumping/restoring the NAND and FAT32 for regular CFW/homebrew usage.

Do u mean I should partition and run ex fat and store nand there and run another partition with fat32 for my cfw setup?
I thought it was advise to just use fat 32 system in sd card due to corrupting
Should I keep my nand in my sd card after I get cfw installed?
I have a spare 32gb card and I’m using a 256gb for the switch but I don’t think that 32 is big enough for nand? I could store in my external hard and order a 64gb if needed?

Have u any links and guides for preparing my sd card and doing nand back up?

With the emuNAND on sd card I take it swapping sd cards for different games is out now?

With emuNAND the 2 different methods sd card how would u recover from corruption of sd card?
That's not what partition means. It doesn't partition the SD card as FAT32 or exFAT or any type of file system; partition means it dedicates part of the SD card for a certain purpose. In this case, part of the SD card's space will be dedicated to storing EmuNAND.

For dumping your NAND, you can follow this guide. 32 GB may be enough but it needs at least 29.1 GB of free space on the SD card.

And the fix for corruption is always the same, formatting the SD card.
 
  • Like
Reactions: CapCaveman

RitchieRitchie

Well-Known Member
Member
Joined
Nov 15, 2013
Messages
787
Trophies
0
Age
49
XP
762
Country
Apologies for all the questions but I'm a bit paranoid about messing this up. I've looked at threads on making an emunand and there seems to be a problem of nsps being deleted as the sysnand and emunand use the same nintendo folder - is this still the case even with the latest version of sxos? If it is still a probelm what is the best way around it? Some suggested formatting the sysnand without the micro sd card to separate them and renaming the folders sysnintendo/emunintendo but would this mean that every time I want to boot I would first have to change the relevant folder back to nintendo? Is there an easier way to do this?

EDIT: Just read another thread so in the latest version of sxos an emutendo folder is created which deals with this - note to self, read more before wasting people's time on here with questions :-)
 
Last edited by RitchieRitchie,

Zap2000

Well-Known Member
Member
Joined
Oct 19, 2018
Messages
640
Trophies
0
Age
43
XP
808
Country
United Kingdom
  1. Well RCM isn't exactly fully on and operational but yes, this was the cause of the battery drain
  2. You can just use Sleep Mode forever. Its honestly underutilized by people who are used to turning off their devices. The main thing is that you will have to ensure it has charge because if it runs out and you updated without burning fuses but you're not using AutoRCM, you'll burn fuses when you recharge the console unless you manage to reboot it into RCM as soon as you start recharging it
  3. No. Disabling AutoRCM is usually done with the same tool used to enable it
  4. Like I said, you could give it a try but Pegaswitch is not easy to setup
  5. I mean if you don't mind the risk of corruption looming over your head, sure. Corruption is easy to correct as a simple SD card format will fix it. But if you have a lot of files on the SD card, the simple solution then involves backing up those files.
  6. Although now outdated, nswdb.com has a listing of all games that can run on firmware 1.0. Also yes, you will update the gamecart slot whenever you are running a firmware of 4.0 or higher, CFW (without the appropriate patch) or OFW. This doesn't make it completely unusable, just unusable on firmwares 4.0
That's not what partition means. It doesn't partition the SD card as FAT32 or exFAT or any type of file system; partition means it dedicates part of the SD card for a certain purpose. In this case, part of the SD card's space will be dedicated to storing EmuNAND.

For dumping your NAND, you can follow this guide. 32 GB may be enough but it needs at least 29.1 GB of free space on the SD card.

And the fix for corruption is always the same, formatting the SD card.
  1. Well RCM isn't exactly fully on and operational but yes, this was the cause of the battery drain
  2. You can just use Sleep Mode forever. Its honestly underutilized by people who are used to turning off their devices. The main thing is that you will have to ensure it has charge because if it runs out and you updated without burning fuses but you're not using AutoRCM, you'll burn fuses when you recharge the console unless you manage to reboot it into RCM as soon as you start recharging it
  3. No. Disabling AutoRCM is usually done with the same tool used to enable it
  4. Like I said, you could give it a try but Pegaswitch is not easy to setup
  5. I mean if you don't mind the risk of corruption looming over your head, sure. Corruption is easy to correct as a simple SD card format will fix it. But if you have a lot of files on the SD card, the simple solution then involves backing up those files.
  6. Although now outdated, nswdb.com has a listing of all games that can run on firmware 1.0. Also yes, you will update the gamecart slot whenever you are running a firmware of 4.0 or higher, CFW (without the appropriate patch) or OFW. This doesn't make it completely unusable, just unusable on firmwares 4.0
That's not what partition means. It doesn't partition the SD card as FAT32 or exFAT or any type of file system; partition means it dedicates part of the SD card for a certain purpose. In this case, part of the SD card's space will be dedicated to storing EmuNAND.

For dumping your NAND, you can follow this guide. 32 GB may be enough but it needs at least 29.1 GB of free space on the SD card.

And the fix for corruption is always the same, formatting the SD card.


No I mean exfat could I use for nand bank up the change to fat32 for cfw? Wat do most user use to back nand up?

With regard to fixing emuNAND if card corrupted would u just restore nand and make emuNAND again as the partition is hidden take it it would be hard to copy.

Can I change sd card for diff games if running emuNAND on sd card ?
 

OnnRyuu

Well-Known Member
Newcomer
Joined
Aug 17, 2018
Messages
67
Trophies
0
Age
36
XP
99
Country
United States
I'm trying to update my switch but I'm having dificulties with formating the keys.txt file
What does exactly needs to be inside the keys.txt file for ChoiDujour to work?
Do I need all the keys extracted from the console (HWI, SBK, TSEC, Device, BIS, etc)?
Do I just need TSEC and Device?
What is the content of the TXT like? "TSEC KEY: 0101010101...etc" or just the "0101010101...etc" part?
 

Xcakepiggie

Member
Newcomer
Joined
Dec 16, 2018
Messages
15
Trophies
0
Age
28
XP
77
Country
United States
Noub Question: Hacked switch (CFW). Can I play online? (Paladins, Fortnite, etc.) (read for more info)
Hello, Hackers,

Question: Hacked switch (CFW). Can I play online? (Paladins, Fortnite, etc.)

Basically, I hacked my switch & installed stuff & they dont work if not in cfw mode.

If I were to boot normally (power button) & not cfw (RCM payload) Will I be able to play paladins/fortnite? If I can, will I get banned? (NOT CFW)

Quick question: what happens if I use internet while not in cfw? (RCM payload)

Thanks,
Scared of ban
 

CapCaveman

Well-Known Member
Newcomer
Joined
Dec 17, 2018
Messages
54
Trophies
0
XP
105
Country
Sweden
  1. Well RCM isn't exactly fully on and operational but yes, this was the cause of the battery drain
  2. You can just use Sleep Mode forever. Its honestly underutilized by people who are used to turning off their devices. The main thing is that you will have to ensure it has charge because if it runs out and you updated without burning fuses but you're not using AutoRCM, you'll burn fuses when you recharge the console unless you manage to reboot it into RCM as soon as you start recharging it
  3. No. Disabling AutoRCM is usually done with the same tool used to enable it
  4. Like I said, you could give it a try but Pegaswitch is not easy to setup
  5. I mean if you don't mind the risk of corruption looming over your head, sure. Corruption is easy to correct as a simple SD card format will fix it. But if you have a lot of files on the SD card, the simple solution then involves backing up those files.
  6. Although now outdated, nswdb.com has a listing of all games that can run on firmware 1.0. Also yes, you will update the gamecart slot whenever you are running a firmware of 4.0 or higher, CFW (without the appropriate patch) or OFW. This doesn't make it completely unusable, just unusable on firmwares 4.0

1. Ah, you mean the Switch uses 5% of battery per hour even when in sleep mode, if it’s been previously booted into RCM?

2. Okay, now I’m more confused. If I enable AutoRCM and use sleep mode, but the battery is 100% drained, the next time the Switch starts, it will boot into regular mode and burn the eFuses (and update the cartridge slot if I prevented that update before)? Also, if I keep it docked in sleep mode I should be fine, right?

3. So it won’t be disabled after turning the Switch off, either voluntarily or accidentally?

4. Got it.

5. I’d rather not have to worry about corrupting files, but I’d still like to keep a backup of my original 1.0.0 NAND. I can’t dump it to an exFAT SD card and then revert the system (via Choi) to FAT32, because it won’t be compatible if I want to restore it, correct? I’m not even sure if you can revert to FAT32 after updating the firmware to exFAT.

6. Okay, so I want to keep the original firmware also for the cartridge slot. Choi gives me that option, yes? If I then update it to 6.2, the game cart slot (that hasn’t been updated) becomes unusable and won’t risk being updated as long as AutoRCM is on and I’m running a CFW? What about if the Switch loses power (as mentioned before regarding the eFuses issue)? Would I still be able to backup my physical games using the cartridge slot?

It’s just so many things. My head hurts, lol.
 

Zap2000

Well-Known Member
Member
Joined
Oct 19, 2018
Messages
640
Trophies
0
Age
43
XP
808
Country
United Kingdom
1. Ah, you mean the Switch uses 5% of battery per hour even when in sleep mode, if it’s been previously booted into RCM?

2. Okay, now I’m more confused. If I enable AutoRCM and use sleep mode, but the battery is 100% drained, the next time the Switch starts, it will boot into regular mode and burn the eFuses (and update the cartridge slot if I prevented that update before)? Also, if I keep it docked in sleep mode I should be fine, right?

3. So it won’t be disabled after turning the Switch off, either voluntarily or accidentally?

4. Got it.

5. I’d rather not have to worry about corrupting files, but I’d still like to keep a backup of my original 1.0.0 NAND. I can’t dump it to an exFAT SD card and then revert the system (via Choi) to FAT32, because it won’t be compatible if I want to restore it, correct? I’m not even sure if you can revert to FAT32 after updating the firmware to exFAT.

6. Okay, so I want to keep the original firmware also for the cartridge slot. Choi gives me that option, yes? If I then update it to 6.2, the game cart slot (that hasn’t been updated) becomes unusable and won’t risk being updated as long as AutoRCM is on and I’m running a CFW? What about if the Switch loses power (as mentioned before regarding the eFuses issue)? Would I still be able to backup my physical games using the cartridge slot?

It’s just so many things. My head hurts, lol.


I would like to know about point 5 also if I’m dumping my nand to exfat to keep it as one file but then changing over to fat32 would my nand be compatible later using sx os ?

Or would like make it a lot harder to restore it later than just dumping nand to fat32 and using joiner later if needed?
 
  • Like
Reactions: CapCaveman

Light9384

Active Member
Newcomer
Joined
Mar 19, 2018
Messages
27
Trophies
0
XP
117
Country
United States
Hello,
For some reason, I am unable to enter RCM mode or turn on the Switch. How can I fix this ? (SXOS 2.3, tried with 2.4.1, Hekate 4.5, tried with 4.6) Switch version 6.1.
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
No I mean exfat could I use for nand bank up the change to fat32 for cfw? Wat do most user use to back nand up?

With regard to fixing emuNAND if card corrupted would u just restore nand and make emuNAND again as the partition is hidden take it it would be hard to copy.

Can I change sd card for diff games if running emuNAND on sd card ?
I don't know what formatting system most users use for NAND backup.

If EmuNAND becomes corrupted, you restore the NAND, then make another EmuNAND partition, you will lose whatever data was stored in the EmuNAND such as save data or installed content.

And if EmuNAND is running on your SD card, changing SD cards means you won't be able to boot EmuNAND anymore. Meaning if there are backups you wish to play using EmuNAND on another SD card, you will have to install EmuNAND on that SD card. Retail games such as cartridges or digital purchases will be fine regardless of SD card or EmuNAND/SysNAND.
I'm trying to update my switch but I'm having dificulties with formating the keys.txt file
What does exactly needs to be inside the keys.txt file for ChoiDujour to work?
Do I need all the keys extracted from the console (HWI, SBK, TSEC, Device, BIS, etc)?
Do I just need TSEC and Device?
What is the content of the TXT like? "TSEC KEY: 0101010101...etc" or just the "0101010101...etc" part?
The lockpick thread tells you exactly what keys you need to use ChoiDujour.
Noub Question: Hacked switch (CFW). Can I play online? (Paladins, Fortnite, etc.) (read for more info)
Hello, Hackers,

Question: Hacked switch (CFW). Can I play online? (Paladins, Fortnite, etc.)

Basically, I hacked my switch & installed stuff & they dont work if not in cfw mode.

If I were to boot normally (power button) & not cfw (RCM payload) Will I be able to play paladins/fortnite? If I can, will I get banned? (NOT CFW)

Quick question: what happens if I use internet while not in cfw? (RCM payload)

Thanks,
Scared of ban
While CFW does not persist if you turn off the console then turn it on while not sending a payload, traces of CFW persist in the console that can get transmitted in OFW and flag you for a ban. The best practice is to make a clean hack-free NAND backup before setting up CFW/homebrew so you can restore it prior to going online. But if you don't have one, you can either risk the ban or buy another console.

1. Ah, you mean the Switch uses 5% of battery per hour even when in sleep mode, if it’s been previously booted into RCM?

2. Okay, now I’m more confused. If I enable AutoRCM and use sleep mode, but the battery is 100% drained, the next time the Switch starts, it will boot into regular mode and burn the eFuses (and update the cartridge slot if I prevented that update before)? Also, if I keep it docked in sleep mode I should be fine, right?

3. So it won’t be disabled after turning the Switch off, either voluntarily or accidentally?

4. Got it.

5. I’d rather not have to worry about corrupting files, but I’d still like to keep a backup of my original 1.0.0 NAND. I can’t dump it to an exFAT SD card and then revert the system (via Choi) to FAT32, because it won’t be compatible if I want to restore it, correct? I’m not even sure if you can revert to FAT32 after updating the firmware to exFAT.

6. Okay, so I want to keep the original firmware also for the cartridge slot. Choi gives me that option, yes? If I then update it to 6.2, the game cart slot (that hasn’t been updated) becomes unusable and won’t risk being updated as long as AutoRCM is on and I’m running a CFW? What about if the Switch loses power (as mentioned before regarding the eFuses issue)? Would I still be able to backup my physical games using the cartridge slot?

It’s just so many things. My head hurts, lol.
  1. No, RCM is its own mode separate from being on or in sleep mode. RCM is the state where you send payloads. In reality, its the type of recovery mode most phones come with that the Switch just so also happens to come with because the chip used for the Switch is used in most phones. I also forgot to mention that charging in RCM with AutoRCM enabled is extremely slow but you shouldn't be charging in RCM in the first place
  2. I said if AutoRCM was disabled. Reread the point.
  3. It can get disabled if you perform an online system update although if you are using the latest version of Atmosphere, it can prevent this. No other CFW offers this type of protection.
  4. This is just to keep the numbers aligned
  5. Dumping and restoring the NAND are typically performed outside of Horizon, the name of the Switch's OS. What this means is that exFAT support is irrelevant when it comes to dumping or restoring the NAND. Basically, you can dump and restore the NAND with exFAT even on 1.0
  6. As stated previously, this will depend on the CFW you are using. For example, ReiNX applies the patch via an extension less file titled "nogc" which would go in the /ReiNX folder. For Atmosphere, it has a configuration for nogc in the bct.ini file. Without this patch, it will be updated irreversibly rendering the gamecart slot unusable for dumping, playing, and anything else that interacts with the system
 
  • Like
Reactions: CapCaveman

Zap2000

Well-Known Member
Member
Joined
Oct 19, 2018
Messages
640
Trophies
0
Age
43
XP
808
Country
United Kingdom
I don't know what formatting system most users use for NAND backup.

If EmuNAND becomes corrupted, you restore the NAND, then make another EmuNAND partition, you will lose whatever data was stored in the EmuNAND such as save data or installed content.

And if EmuNAND is running on your SD card, changing SD cards means you won't be able to boot EmuNAND anymore. Meaning if there are backups you wish to play using EmuNAND on another SD card, you will have to install EmuNAND on that SD card. Retail games such as cartridges or digital purchases will be fine regardless of SD card or EmuNAND/SysNAND.
The lockpick thread tells you exactly what keys you need to use ChoiDujour.
While CFW does not persist if you turn off the console then turn it on while not sending a payload, traces of CFW persist in the console that can get transmitted in OFW and flag you for a ban. The best practice is to make a clean hack-free NAND backup before setting up CFW/homebrew so you can restore it prior to going online. But if you don't have one, you can either risk the ban or buy another console.


  1. No, RCM is its own mode separate from being on or in sleep mode. RCM is the state where you send payloads. In reality, its the type of recovery mode most phones come with that the Switch just so also happens to come with because the chip used for the Switch is used in most phones. I also forgot to mention that charging in RCM with AutoRCM enabled is extremely slow but you shouldn't be charging in RCM in the first place
  2. I said if AutoRCM was disabled. Reread the point.
  3. It can get disabled if you perform an online system update although if you are using the latest version of Atmosphere, it can prevent this. No other CFW offers this type of protection.
  4. This is just to keep the numbers aligned
  5. Dumping and restoring the NAND are typically performed outside of Horizon, the name of the Switch's OS. What this means is that exFAT support is irrelevant when it comes to dumping or restoring the NAND. Basically, you can dump and restore the NAND with exFAT even on 1.0
  6. As stated previously, this will depend on the CFW you are using. For example, ReiNX applies the patch via an extension less file titled "nogc" which would go in the /ReiNX folder. For Atmosphere, it has a configuration for nogc in the bct.ini file. Without this patch, it will be updated irreversibly rendering the gamecart slot unusable for dumping, playing, and anything else that interacts with the system

I take it I dump my nand on exfat will I be able to restore no matter if I use fat32?

Also on this tut
https://gbatemp.net/threads/tut-dealing-with-nand-emunand-safely.525274/
It says
SX 2.3 supports separated Nintendo folder as Emutendo for emunand. Linked the two nands on the same possible firmware is recommended.

I thought u said I would be ok using sysnand 4.1 and emunand 6.2? Wat does this mean above? Should I be on the same fw on both?


Also says
> Make a backup/ copy of NAND and/or EMUNAND before doing anything.

Should I be copying my emunand also and nand back up? Not sure if needed?
 
Last edited by Zap2000,

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
I take it I dump my nand on exfat will I be able to restore no matter if I use fat32?

Also on this tut
https://gbatemp.net/threads/tut-dealing-with-nand-emunand-safely.525274/
It says
SX 2.3 supports separated Nintendo folder as Emutendo for emunand. Linked the two nands on the same possible firmware is recommended.

I thought u said I would be ok using sysnand 4.1 and emunand 6.2? Wat does this mean above? Should I be on the same fw on both?


Also says
> Make a backup/ copy of NAND and/or EMUNAND before doing anything.

Should I be copying my emunand also and nand back up? Not sure if needed?
A recommendation is just a recommendation; its not mandatory. And I would make a backup of EmuNAND as well.
 

CapCaveman

Well-Known Member
Newcomer
Joined
Dec 17, 2018
Messages
54
Trophies
0
XP
105
Country
Sweden
  1. No, RCM is its own mode separate from being on or in sleep mode. RCM is the state where you send payloads. In reality, its the type of recovery mode most phones come with that the Switch just so also happens to come with because the chip used for the Switch is used in most phones. I also forgot to mention that charging in RCM with AutoRCM enabled is extremely slow but you shouldn't be charging in RCM in the first place
  2. I said if AutoRCM was disabled. Reread the point.
  3. It can get disabled if you perform an online system update although if you are using the latest version of Atmosphere, it can prevent this. No other CFW offers this type of protection.
  4. This is just to keep the numbers aligned
  5. Dumping and restoring the NAND are typically performed outside of Horizon, the name of the Switch's OS. What this means is that exFAT support is irrelevant when it comes to dumping or restoring the NAND. Basically, you can dump and restore the NAND with exFAT even on 1.0
  6. As stated previously, this will depend on the CFW you are using. For example, ReiNX applies the patch via an extension less file titled "nogc" which would go in the /ReiNX folder. For Atmosphere, it has a configuration for nogc in the bct.ini file. Without this patch, it will be updated irreversibly rendering the gamecart slot unusable for dumping, playing, and anything else that interacts with the system

1. I see. But as soon as it loads a CFW (SX OS or Atmosphere, for example), it “exits” RCM mode, right? So if I’m running SX OS/Atmos, put the Switch in sleep mode and leave it charging, I should be fine?

2. Ah, okay. As long as AutoRCM is enabled, everything’s good, then.

3. No need to worry if the system isn’t connected to the internet, though?

4. :D

5. Interesting. So the SD card format doesn’t matter for NAND backups. And you don’t have to keep it in the card that you’re using for homebrew? I could back up the original 1.0.0 SysNAND to an SD card formatted in exFAT and have the system update to a firmware in FAT32 using a different card?

6. Got it. Kinda sucks that even the cartridge slot is protected by its own firmware, but that’s Nintendo for you.
 
Last edited by CapCaveman,

Zap2000

Well-Known Member
Member
Joined
Oct 19, 2018
Messages
640
Trophies
0
Age
43
XP
808
Country
United Kingdom
A recommendation is just a recommendation; its not mandatory. And I would make a backup of EmuNAND as well.

Will my sysnand be ok on 4.1 I don't want to brick or mess up.

How come u didn't tell me to back up emunand how do I do it? I don't understand that tut can u explain the back up method?

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

A recommendation is just a recommendation; its not mandatory. And I would make a backup of EmuNAND as well.


Why is it recommended tho? I don't want to brick or mess up my system? R u sure I'm safe on lower sysnand?

How do I make a copy of emunand? I don't understand that tut
 

Xcakepiggie

Member
Newcomer
Joined
Dec 16, 2018
Messages
15
Trophies
0
Age
28
XP
77
Country
United States

Wait but isnt getting a NAND backup also being in hekate which is basically CFW? (Traceable)
also will there be an untraceable cfw in the future?
 

xdarkmario

Philosopher
Member
Joined
Dec 30, 2010
Messages
1,635
Trophies
1
Location
Mushroom Kingdom
XP
2,563
Country
United States
Question, I was wondering if in a sense does switch backups works a bit like early 3ds hacks. What I mean by that is. There was a time on the 3ds that if you were using a flash cart to play your game dumps in order to play online "safer" you had to inject your personal cart headder into the ROM file.
Is that still a possibility/necessity?
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    straferz @ straferz: Anybody know why this is happening to my ACWW town...