Hacking SWITCH NOOB PARADISE - Ask questions here

Draxzelex said:

You can only unlink the account if you format the console as explained on their website but its better to have one linked than not to have one at all because some applications need a linked account to work such as the NES app or the game Pianista. Plus Nintendo primarily bans consoles, not accounts.

Click to expand...

1. Shall I upgrade from 5.1.0 to OFW 6.2.0 SysNan and then install Atmosphere. Unlink the existing and create a new Acc.
2. Stay on 5.1.0 do Atmosphere and stay? (But here I have in future the problem, that games, which need to have a newer version, I'm not able to play or I need to upgrade anyway and burn the fuses)
3. Install SX, stay on SysNan 5.1.0 and on EmuNan 6.2.0? (No fuses get burned because everything runs on EmuNan).

1. What if I do a factory reset? Then the account is not anymore connect (even if the switch says so). Nintendo says on the website I can connect to more then one console me Acc so that could work right? Then I upgrad with "ChoiDujourNX" to 6.2.0 and create a new Acc? Does Nintendo check the fuses and Bans me?
2. What about upgrade to 6.2.0 via "ChoiDujourNX" and then unlink the Acc and create a new one? Again does Nintendo check the fuses?

dagarui said:

What do you recommend? I already unlinked the "Nintendo Network ID" it via the website, but thats probably something different. Isn't it?

What would be your suggestion?
Options:

1. Shall I upgrade from 5.1.0 to OFW 6.2.0 SysNan and then install Atmosphere. Unlink the existing and create a new Acc.
2. Stay on 5.1.0 do Atmosphere and stay? (But here I have in future the problem, that games, which need to have a newer version, I'm not able to play or I need to upgrade anyway and burn the fuses)
3. Install SX, stay on SysNan 5.1.0 and on EmuNan 6.2.0? (No fuses get burned because everything runs on EmuNan).

Is there a downside to upgrade to 6.2.0
Thanks for your help

edit: I read that everyone says not to upgrade on 6.2.0?! :/ why?
edit 2:

1. What if I do a factory reset? Then the account is not anymore connect (even if the switch says so). Nintendo says on the website I can connect to more then one console me Acc so that could work right? Then I upgrad with "ChoiDujourNX" to 6.2.0 and create a new Acc? Does Nintendo check the fuses and Bans me?
2. What about upgrade to 6.2.0 via "ChoiDujourNX" and then unlink the Acc and create a new one? Again does Nintendo check the fuses?

Click to expand...

1. ChoiDujourNX is a homebrew application meaning it requires CFW to be used which Nintendo can detect and potentially ban you for
2. ChoiDujour is what ChoiDujourNX is based off of. Its a Windows command line program that patches firmware files on your computer that you transfer with memloader which is a payload. And payloads exist solely in RCM. And RCM is triggered before the NAND. Meaning ChoiDujour is virtually undetectable. Its a long and involved process that takes roughly between 30 minutes to an hour.
3. An easy but more risky way of updating without burning fuses is simply by booting back into RCM after the system update is finished installing. This method relies solely on your jig because if it fails to boot you back into RCM, you will burn fuses. This is about as detectable as method #2 but it trades effectiveness for efficiency

Draxzelex said:

Stealth Mode is sufficient alone.

Click to expand...

1. Boot into RCM and load CTCaer mod (= improved Hekate?) as a payload by making use of the Fusée Gelée exploit. I plan on getting the AceNS Loader which has an easy to use jig to boot into RCM and a nice dongle to put the payload on.
2. Make a System NAND Backup including boot0/boot1 and raw eMMC GPP. This would enable me to revert everyhthing I do to with my Switch and allow me to safely play online again in the future if I'd like to. I'd be back on my old and totally clean 4.1.0 system when loading that backup.
3. use the biskeydump payload to backup my BIS keys. They would allow me to reinstall any firmware version manually (useful if I lost my NAND backup or it got corrupted)
4. use ChoiDujour to install the 6.2.0 update without burning fuses
5. enable AutoRCM through Hekate. This way my Switch will always boot into RCM to avoid burning any fuses. Ever booting through the stock bootloader would immediately burn fuses and therefore I should always boot trough RCM and Hekate. But I guess AutoRCM might be detectable and result in a console ban?
6. Boot stock FW through Hekate
7. play Pokémon!

Charli said:

First of all, thanks for providing this noobie paradise and all those people answering everyones questions here, esp. Draxzelex

I've got an unpatched Switch on 4.1.0 and plan on toying around with CFW. But I'd also really like to play Pokémon which just arrived at my door But I'd need to update my switch to be able to play.

From what I've gathered, CFW like Atmosphère and ReiNX runs and installs just fine on a Switch with the latest 6.2.0 update as long as I have an unpatched console (I guess the news section of the first post here should be updated to reflect that?)
But letting my switch install the update would physically and thus permanently burn fuses, which I'd rather like to avoid.

I think the wise way to go would be:

1. Boot into RCM and load CTCaer mod (= improved Hekate?) as a payload by making use of the Fusée Gelée exploit. I plan on getting the AceNS Loader which has an easy to use jig to boot into RCM and a nice dongle to put the payload on.
2. Make a System NAND Backup including boot0/boot1 and raw eMMC GPP. This would enable me to revert everyhthing I do to with my Switch and allow me to safely play online again in the future if I'd like to. I'd be back on my old and totally clean 4.1.0 system when loading that backup.
3. use the biskeydump payload to backup my BIS keys. They would allow me to reinstall any firmware version manually (useful if I lost my NAND backup or it got corrupted)
4. use ChoiDujour to install the 6.2.0 update without burning fuses
5. enable AutoRCM through Hekate. This way my Switch will always boot into RCM to avoid burning any fuses. Ever booting through the stock bootloader would immediately burn fuses and therefore I should always boot trough RCM and Hekate. But I guess AutoRCM might be detectable and result in a console ban?
6. Boot stock FW through Hekate
7. play Pokémon!

Did I get everything right? Or is there something I misunderstood?

Click to expand...

Ranshiro said:

Ideally how will Deja Vu work? i know it's not released yet but is there any idea what the end process will be for the user? I'm sitting on 4.1.0 mainly because with my bad luck, anything that can go wrong will go wrong. So a process with less physical steps is great for me.

Will it still require going into RCM and/or having autoRCM on? will it all occur before loading Horizon? Will it be able to load different payloads or only Atmosphere? Will it be able to load straight into an emuNAND (be it sx os' current one or atmosphere's upcoming one)?

Click to expand...

Goofy Time said:

Just passing in here with a general question.

I have a launch model Switch and the most recent firmware due to playing Smash Bros. Is this system hackable, and if so, what methods are available?

Click to expand...

Draxzelex said:

1. Yes, the only purpose of RCM is to send a payload. Once you send a payload, you either boot into CFW or OFW. Sleep Mode is fine with or without AutoRCM
2. Yes
3. Yes
4. Filler
5. Yes. You can also back it up to a hard drive or a cloud if you want.

Click to expand...

Charli said:

I think the wise way to go would be:

Click to expand...

1. Boot into RCM using a jig and load CTCaer mod (= improved Hekate?) as a payload via a USB dongle;
2. Make a System NAND Backup including boot0/boot1 and raw eMMC GPP while still in RCM;
3. Use the biskeydump payload to backup my BIS keys. They would allow me to reinstall any firmware version manually (optional?)
4. use ChoiDujour to install the 6.2.0 update without burning fuses (better than doing it on the EmuNAND, or does it end up being the same thing?)
5. Prevent the cartridge slot from updating (if there really is such an option in Choi) - that way, you can truly revert your system to its original state later;
6. Enable AutoRCM through Hekate (apparently, auto-enabled by default when using Choi);
7. Boot stock FW through Hekate (by that, do you mean CFW or OFW?)
8. Forgot to add this step: link a Nintendo account (Nintendo ID) as soon as you boot into CFW (or is it OFW? I’m not sure), so if it’s required for anything and you’re banned later, it’s alteady there;
9. Play Pokémon (a legit copy, I assume, so you just used the CFW to bypass the firmware requirement and avoid burning fuses by booting into the OFW/Horizon?).

Zedroid said:

are there any cheat engines where i do not need to be conndcted to a computer at all times? kinda like sx?

Click to expand...

Zap2000 said:

Few questions to ask

Xci file do I need the update files if playing offline?
no

Dlc for is using with xci files is in a diff format? How do I install ? Wat program?
no some come with the base

Recommend settings and why? sx ok stealth mode? No WiFi connection setup? airaplane mode? 90dns and what do you mean by no wifi?

So child friendly settings recommended to stop them messing things up? switch should come with them in system settings like a lock screen

Some useful homebrew progs for use with sx os homebrew?

Click to expand...

yoshimashi said:

So I'm on step number 3 of guide.sdsetup and my switch is telling me that I need to update my system for it to accept my sd card. It's 200gb so the only options I had was exfat and NTFS. I am on the latest firmware. Never touched cfw besides hekate and that was to follow the step number 2 of the guide. So.. my question is: Is it safe to update this device to accept my sdcard?

Also: I have games that I bought from eshop. I want to buy another switch strictly for online play later on so should I unlink my account so that it doesn't get banned? Or is it okay to just play on normal boot but with the internet off?

Click to expand...

makanayam said:

Hi,

I haven't touched my switch in a while, but AFAIK it is currently in 4.1.0 (exFAT patched) with RajNX inside.

If I want to update it to 6.2.0 and use Atmosphere, can I just use the latest Kosmos package then install 6.2.0 via ChoiDujourNX and call it a day?

Click to expand...

CapCaveman said:

Thanks again, Draxzelex, you’re an invaluable source of information!

I was thinking about when exactly to update the console. I’m planning on following your advice to another user and going with method #2: using ChoiDuJour (not NX) while in RCM, after backing up the SysNAND with Hekate (as per your recommendation), and updating to the latest firmware without burning any fuses. Questions:

1. Should I use CTCaer? Is that a branch of Hekate?

2. ChoiDuJour gives you the option to update the firmware while preventing the cartridge slot from updating, right?

3. How is that process different than booting into SX OS (without updating first), creating an EmuNAND, and then using ChoiDuJourNX to perform the update?

4. Regardless of the method, I should still never boot into the OFW, or it will burn fuses, correct? Is there any risk of that happening if AutoRCM is on (and it’s enabled by default when updating with Choi, as you mentioned)? If so, what’s the best way of preventing that from happening?

As for game backups, since I’m determined to maintain my cartridge slot in its original state, I may have to download them instead of dumping from my own carts. I’ve been reading about NSOs and XCIs, but couldn’t come to a conclusion.

5. Is there a consensus as to which one is better? I’ll be using SX OS, so I believe I can run both;

6. I’ve read something about “trimming” files, is that similar to what people used to do to PSP ISOs, back in the day?

6.1 If so, can I just download the trimmed versions? Do they perform the same?

6.2 Are there tools so I can trim the files myself? Is that easy/recommended to do?

7. I’ve also read about updates to the controllers’ firmwares. How can one go on about updating those?

8. Forgot to ask this one: if you update applying the exFAT patch, can you revert to the same firmware without it (“remove” the patch and use the FAT32 version) or vice-versa?



I’m on the same boat, buddy, the only difference being that I’m on 1.0.0.

It’d be great if we could define the proper order of doing things. Here’s what I got (adding to your own list):

1. Boot into RCM using a jig and load CTCaer mod (= improved Hekate?) as a payload via a USB dongle;
2. Make a System NAND Backup including boot0/boot1 and raw eMMC GPP while still in RCM;
3. Use the biskeydump payload to backup my BIS keys. They would allow me to reinstall any firmware version manually (optional?)
4. use ChoiDujour to install the 6.2.0 update without burning fuses (better than doing it on the EmuNAND, or does it end up being the same thing?)
5. Prevent the cartridge slot from updating (if there really is such an option in Choi) - that way, you can truly revert your system to its original state later;
6. Enable AutoRCM through Hekate (apparently, auto-enabled by default when using Choi);
7. Boot stock FW through Hekate (by that, do you mean CFW or OFW?)
8. Forgot to add this step: link a Nintendo account (Nintendo ID) as soon as you boot into CFW (or is it OFW? I’m not sure), so if it’s required for anything and you’re banned later, it’s alteady there;
9. Play Pokémon (a legit copy, I assume, so you just used the CFW to bypass the firmware requirement and avoid burning fuses by booting into the OFW/Horizon?).

Click to expand...

1. CTCaer is the name of a developer of Hekate and his fork is the only that's public
2. It does but it generates a kip that not only has to be loaded alongside the other kips but is firmware-specific meaning it will have to be regenerated every time you change firmware. That method of preventing the update is outdated hence why no one uses ChoiDujour to update their firmware without burning fuses
3. That just involves updating EmuNAND, not SysNAND
4. You can technically boot OFW without burning fuses. Hekate has a Stock Launch Profile which is Hekate's version of OFW. It applies none of the CFW patches but since you are booting OFW through Hekate, you won't burn any fuses because Hekate disables the fuse check. As for booting non-RCM OFW with AutoRCM, if you ever update the system online, it will remove AutoRCM and subsequently burn fuses
5. SX OS runs both and they're both equally interchangeable now. .XCI files are slower and larger than .NSP files but unlike .NSP files, .XCI files can be read and loaded straight from the HDD while .NSP files must first be installed and can only be installed to the internal memory or an SD card, not an HDD
6. Wasn't a part of the PSP scene but .XCI files are 1:1 copies of cartridges and because games don't take up the full space on the cartridge, there is a lot of empty space in the .XCI file itself that artificially inflates its size. Trimming removes this dead space. You also cannot trim a .NSP file as that is the smallest version of a game. Now since I don't own SX OS, I don't use .XCI files that often and as such, am unaware of the trimmers available. But if you look them up Google, you should be able to find one
7. These are installed whenever you install a firmware update. They are usually the first message you see after installing a new firmware. As long as you haven't modded your Joy-Con to bridge pins 9 & 10 together, these are safe to perform
8. There is no FAT32 version of firmware; the console supports FAT32 out of the box. exFAT is not supported on the console without a patch which you can either obtained officially from Nintendo themselves or with homebrew. Thus you have more to lose when you don't apply the exFAT version of the firmware you are installing because you get less support that way.

Draxzelex said:

About Step 3. Biskeys are only needed for decrypting the NAND with hackdismount. The keys needed for installing firmware versions are listed in the lockpick thread (and could be subsequently obtained via Google). Also if you are going to be updating your firmware with either ChoiDujour or ChoiDujourNX, they enable AutoRCM by default after installing the firmware so you don't have to enable it yourself. And lastly, while AutoRCM may be detectable, nobody has been banned thus far for solely using it. Plus its about as detectable as running SX OS EmuNAND on your SD card which no one has been banned for either.

Click to expand...

Shockfire said:

When i start fusee it shows me an Fatal Error: Failed to stat stage2 (fusee-secondary.bin) i cant find this fusee secondarybin nowehere. What did i wrong?

Click to expand...