Hacking Absolute NOOB could apreciate help

[Mr_P]

So bear with me:

Took the plunge and bought what is advertised as a brand new unpatched switch maybe running 3.0.2 firmware XAJ7 green (looking at the images attached to the auction) and have read the switch guide and looked but still am not 100%. So here goes:

1 - if it completely unpatched etc is the firmware fine or am i looking to upgrade it somehow to get better support etc for games?
2 - I see a lot about OFW & CFW. Does this mean there is a way to switch between the 2, not get detected by Nintendo in OFW and use shop and online play?
3 - Also reading the guide as long as i don't connect to the internet at all the guide lets me create a crisp clean NAND that I can switch between if necessary at the right stage in the guide. Specifically i was looking at a Reddit forum and this was what someone uses

"I've been using SX OS EmuNAND since December. I connect to the internet on EmuNAND using stealth mode + 90DNS (I know it's redundant but it makes me a less anxious) and I haven't been banned.

On EmuNAND I use both NSPs and XCIs. On OFW I have a Switch Online subscription and use that more often than EmuNAND. I don't have AutoRCM enabled and instead keep an Atmosphere Payload Pusher with me to boot into SX OS as needed."

Does this still fall in the scope of what the guide shows or is it better etc?

Appreciate the help and apologise for the daft questions that will follow there is just so much of it around to digest and would like the best of both worlds i guess but know that isn't always the case.

 

[FoxMcloud5655]

First thing's first; there is ALWAYS a chance of being banned since the moment you run CFW for the first time, no matter how much you do.

As for the best method of staying unbanned, it's best to create an EmuNAND and run all of your homebrew inside there, while keeping your OFW untouched. I won't get into the argument of SX OS vs. Atmosphere, but I personally use Atmosphere and know that it stays the most up-to-date with everything I need it for. Using Hekate, both Atmosphere and SX OS can use EmuNAND, so there's no need to pick one over the other, as the only real difference between the two functionally is the ability to directly play .XCI files from a USB storage device.

 

[Mr_P]

First thing's first; there is ALWAYS a chance of being banned since the moment you run CFW for the first time, no matter how much you do.

As for the best method of staying unbanned, it's best to create an EmuNAND and run all of your homebrew inside there, while keeping your OFW untouched. I won't get into the argument of SX OS vs. Atmosphere, but I personally use Atmosphere and know that it stays the most up-to-date with everything I need it for. Using Hekate, both Atmosphere and SX OS can use EmuNAND, so there's no need to pick one over the other, as the only real difference between the two functionally is the ability to directly play .XCI files from a USB storage device.

Thanks. Know you maybe can't answer too much but:
1 - If I mainly want backup games to play is SX OS the best choice?
2 - Is firmware version still important as i chose to pay more based on that and the serial no: for example I want to play Zelda: Links Awakening Or would've it been better to have bought 2 secondhand cheap switches?
3 - Could you explain a little clearer what the reddit guy is doing and does it seem a good option?

thanks again

 

[FoxMcloud5655]

1. No. SX OS is mainly used for piracy, and Atmosphere is used both for piracy and for legit backups. I'm glad you're going to be using it for legit games

2. Firmware versions as low as possible are best for iPatched Switches, but since you said that yours is not, it does not matter. It's a hardware vulnerability that no one can fix once it's in your hands, so it won't matter what firmware it runs.

3. They are taking a risk of being banned by going online with their EmuNAND CFW, but using software that tries to make the Switch as hard to identify as possible to minimize the risk of being banned by Nintendo. Since he has SX OS, he is using it to play .XCI (non-system specific dumps) and .NSP (system specific dumps) files, while keeping all of the Nintendo logins and credentials tied to his OFW to make it seem like nothing's out of the ordinary as viewed by Nintendo's servers.

 

[Itsuki235]

For unpatched consoles, the firmware version does not matter. Using a newer OFW firmware version like 8.1.0 or 9.0.0 has the best compatibility with current titles. Keeping the firmware version low is only important for patched consoles.

Currently, OFW 8.1.0 is the best place to be for homebrew due to some input issues with 9.0.0, but most of the major homebrew apps (checkpoint) support 9.0.0 already.

SX OS has 2 exclusive features right now: native XCI mounting allows for titles to launch without having to install them first (time saver) and USB HDD support. Those features are not really worth it for most users. It can be if you never use the "portable" aspect of the unit.

Here is the idea behind what the reddit person is doing: The idea is to create a second sandbox (stored on the SD card) where all CFW activities are done on and never launch CFW on the vanilla console. That should keep the official side clean. Then, as long as the CFW EmuMMC side of the console never connects online, the console should not ever get banned.

That person is messing up their own configuration by letting their CFW EmuMMC connect online... and then bragging about it apparently? o.O

The safest way of setting up the switch is to
1. create a nand back with hekate (first thing done)
2. activate autoRCM3. then create an emuMMC via an SD card partition and set it to autoboot
4. Launch CFW
5. Update CFW's Horizon version to latest supported (8.1.0 r 9.0.0) using choidujourNX
6. "Install" Incognito, then remove sysmodule
7. (optional) deactivate autoRCM
8. (optional) Update stock OFW to latest via official servers, and then disable automatic updates/delete WiFi settings
9. (optional) create second nand backup
10. (optional) enable autoRCM again

Then only use emuMMC from that point on and you should be safe from being banned by big N since you banned yourself using incognito preemptively.

 

[Mr_P]

1. No. SX OS is mainly used for piracy, and Atmosphere is used both for piracy and for legit backups. I'm glad you're going to be using it for legit games

2. Firmware versions as low as possible are best for iPatched Switches, but since you said that yours is not, it does not matter. It's a hardware vulnerability that no one can fix once it's in your hands, so it won't matter what firmware it runs.

3. They are taking a risk of being banned by going online with their EmuNAND CFW, but using software that tries to make the Switch as hard to identify as possible to minimize the risk of being banned by Nintendo. Since he has SX OS, he is using it to play .XCI (non-system specific dumps) and .NSP (system specific dumps) files, while keeping all of the Nintendo logins and credentials tied to his OFW to make it seem like nothing's out of the ordinary as viewed by Nintendo's servers.

Oh no 100% legit

 

[FoxMcloud5655]

^^ What this guy said. Thanks for the detailed explanation.

EDIT: Ninja'd What @Itsuki235 said.

 

[Mr_P]

For unpatched consoles, the firmware version does not matter. Using a newer OFW firmware version like 8.1.0 or 9.0.0 has the best compatibility with current titles. Keeping the firmware version low is only important for patched consoles.

Currently, OFW 8.1.0 is the best place to be for homebrew due to some input issues with 9.0.0, but most of the major homebrew apps (checkpoint) support 9.0.0 already.

SX OS has 2 exclusive features right now: native XCI mounting allows for titles to launch without having to install them first (time saver) and USB HDD support. Those features are not really worth it for most users. It can be if you never use the "portable" aspect of the unit.

Here is the idea behind what the reddit person is doing: The idea is to create a second sandbox (stored on the SD card) where all CFW activities are done on and never launch CFW on the vanilla console. That should keep the official side clean. Then, as long as the CFW EmuMMC side of the console never connects online, the console should not ever get banned.

That person is messing up their own configuration by letting their CFW EmuMMC connect online... and then bragging about it apparently? o.O

The safest way of setting up the switch is to
1. create a nand back with hekate (first thing done)
2. activate autoRCM3. then create an emuMMC via an SD card partition and set it to autoboot
4. Launch CFW
5. Update CFW's Horizon version to latest supported (8.1.0 r 9.0.0) using choidujourNX
6. "Install" Incognito, then remove sysmodule
7. (optional) deactivate autoRCM
8. (optional) Update stock OFW to latest via official servers, and then disable automatic updates/delete WiFi settings
9. (optional) create second nand backup
10. (optional) enable autoRCM again

Then only use emuMMC from that point on and you should be safe from being banned by big N since you banned yourself using incognito preemptively.

So as I understand it:

1 - create a clean nand backup in case of issues later
2 - Autoboot
3 - block connections
4 - update
5 - play using the CFW

hopes that’s right so far

Couple of questions then:

Are you suggesting SX OS or Atmosphere ?

If I follow the majority but want to play say Mario Kart online is that possible with this kind of setup ?

What is the 2nd NAND for and is that emu or stock, or does it cover both ?

Thanks

 

[Spider_Man]

main rules to follow when thinking of using sx os or cfw.

1) have a system that has not been patched
2) never connect a nintendo account to your console - this way you cant connect to eshop or play online, disable wifi when using sx os or cfw
3) never perform a firmware update (if wifi is off then it shouldnt be an issue as it cant download, if a new game prompts an update ignore it, with wifi off this will be a firmware update off the game).

no point creating a nand backup unless you plan on installing things that alter the system.

with sx os your pretty much safe because you can install xci/nsp games to your sd card, as long as you dont install anything to the consoles internal memory your safe.

the point of a nand for the switch is a safetey backup if you cock something up, if you simply want to run roms then you shouldnt need emunand or sysnand.

ive never bothered with either of them and never needed to either.

i dont have a nintendo account linked, i have sx os stealth mode enabled, i only enable wifi when i need to ftp cheat files over, i never perform firmware updates, i never play online or connect to eshop (cant as i dont have an account linked).

when in official firmware you need to take caution as nintendo may see what you have installed onto your sd card and see that its not a legit game and you may face been banned.

id advise if you plan on using the system for both cfw and ofw is that you have 2 sd cards.

SD 1) everything sx os/cfw related installed to (never install to console memory)
SD 2) only ofw content, this will have nothing illegal or exploit related stored thus wont be detected by nintedo.

or simply keep offline like me.

 

[Itsuki235]

It is possible to redirect read/writes to the NAND to instead read/write to an area on the SD card. That is EmuNAND (SX OS) or emuMMC (Atmosphere). Setting it up should be the second thing you do after creating a nand backup.

Theoretically, Mario Kart (with a cartridge) could be played online when booting into stock/OFW mode, relatively safely.

Which CFW to use is a judgement call you have to make. SX OS is probably simpler to use in the long run but costs money ($30 for a license). There is also ReiNX but that one gets updated less frequently as does not support read/write redirection yet.

with sx os your pretty much safe because you can install xci/nsp games to your sd card, as long as you dont install anything to the consoles internal memory your safe.

This still installs the poorly signed tickets to the NAND and stores related save data on the NAND and is therefore unsafe.

 

[Mr_P]

main rules to follow when thinking of using sx os or cfw.

1) have a system that has not been patched
2) never connect a nintendo account to your console - this way you cant connect to eshop or play online, disable wifi when using sx os or cfw
3) never perform a firmware update (if wifi is off then it shouldnt be an issue as it cant download, if a new game prompts an update ignore it, with wifi off this will be a firmware update off the game).

no point creating a nand backup unless you plan on installing things that alter the system.

with sx os your pretty much safe because you can install xci/nsp games to your sd card, as long as you dont install anything to the consoles internal memory your safe.

the point of a nand for the switch is a safetey backup if you cock something up, if you simply want to run roms then you shouldnt need emunand or sysnand.

ive never bothered with either of them and never needed to either.

i dont have a nintendo account linked, i have sx os stealth mode enabled, i only enable wifi when i need to ftp cheat files over, i never perform firmware updates, i never play online or connect to eshop (cant as i dont have an account linked).

when in official firmware you need to take caution as nintendo may see what you have installed onto your sd card and see that its not a legit game and you may face been banned.

id advise if you plan on using the system for both cfw and ofw is that you have 2 sd cards.

SD 1) everything sx os/cfw related installed to (never install to console memory)
SD 2) only ofw content, this will have nothing illegal or exploit related stored thus wont be detected by nintedo.

or simply keep offline like me.

Thanks.

Mainly Mario Kart really is like to do online but that could be disc based really so guessing wouldn’t need to link an ID

And does not updating cause issues with newer games like Links Awakening ?

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

It is possible to redirect read/writes to the NAND to instead read/write to an area on the SD card. That is EmuNAND (SX OS) or emuMMC (Atmosphere). Setting it up should be the second thing you do after creating a nand backup.

Theoretically, Mario Kart (with a cartridge) could be played online when booting into stock/OFW mode, relatively safely.

Which CFW to use is a judgement call you have to make. SX OS is probably simpler to use in the long run but costs money ($30 for a license). There is also ReiNX but that one gets updated less frequently as does not support read/write redirection yet.

Ok
So are then emuMMC and emuNAND the same thing ?
Don’t mind paying for SX but would the pro version be better for portability if it’s tethered ?
Lastly, what do you mean by the redirect and what would be a good place to start for looking into that ?

thanks again

 

[Itsuki235]

Link's Awakening needs OFW 8.1 or 8.0.1. An old OFW like 3.0.2 definitely cannot run newer titles. emuMMC/emuNAND are implemented slightly differently by each CFW but they serve the same functional purpose from the user's perspective.

Look at... https://nh-server.github.io/switch-guide/ and Code Dount for step-by-step guides.

 

[Mr_P]

Link's Awakening needs OFW 8.1 or 8.0.1. An old OFW like 3.0.2 definitely cannot run newer titles. emuMMC/emuNAND are implemented slightly differently by each CFW but they serve the same functional purpose from the user's perspective.

Look at... https://nh-server.github.io/switch-guide/ and Code Dount for step-by-step guides.

The Github guide was really good, thanks for that. Is this what you would recommend and does your initial process follow this?
Last few couple of questions I hope:

1 - Would you recommend the 2 SD card setup that RetroBoy suggested and can changing cards have any negative effect on the system if not in the machine or removed etc?
2 - Am i to assume Atmosphere loads games from an SD not USB ?
3 - The 90DNS method, is that still the recommended option and should it be setup on the emuMMC or the sysNAND as well?
4 - AutoRCM - does this affect detection at all from Nintendo? If i can do it well every time do you recommend using it or no?
5 - What differs around your steps from above and the guide? Is it mainly Incognito, remembering i would like to play Mario Kart 8 Online using a clean sysNAND.
6 - Do you recommend sd setup.com for emulators, xci converters etc or do they pose an extra risk

thanks

 

[Itsuki235]

1. A second SD card is not needed for anything. Just partition the first one and set up EmuMMC and you will have the same configuration.
2. All CFW can load games from SDXC. SX OS can also load from USB HDD.
3. The preferred method is to not have WiFi enabled at all when using CFW. That said, emuMMC should be used with either incognito and or 90DNS if WiFi is going to ever be enabled. Incognito is more foolproof, a one-time solution but does require more initial setup time
4. There is no evidence right now that indicates they are aware if the console booted normally or if it booted from recovery mode. It seems they cannot detect the change for some technical reason, although I am unsure why exactly.
5. Incognito basically. The author, blawar, is an asshole (don't ask). So, the idea of having to use his software bothers some people, even if that software is the best for the task. I also say to update your OFW, which, while technically unnecessary, has to be done at some point to make the console suitable for online play. The console can be updated prior to or after creating emuMMC. Updating it prior would be less work overall, but just remember to delete WiFi settings after updating.

https://github.com/blawar/incognito

6. SDCard setup is run by Team Atlas as an easy download tool for their repackage of Atmosphere + other apps they call "Kosmos". They have been around for over a year and are very trustworthy. They are a good source for a template, but they made the decision to stop including sig/es patches recently. Be sure to download those seperately. Also, their site tends to be updated less than their Kosmos Github page. Make sure the site uses the latest version of Atmosphere, otherwise, download it, but then swap the related files from their repository: https://github.com/AtlasNX/Kosmos/releases .

 

[Mr_P]

1. A second SD card is not needed for anything. Just partition the first one and set up EmuMMC and you will have the same configuration.
2. All CFW can load games from SDXC. SX OS can also load from USB HDD.
3. The preferred method is to not have WiFi enabled at all when using CFW. That said, emuMMC should be used with either incognito and or 90DNS if WiFi is going to ever be enabled. Incognito is more foolproof, a one-time solution but does require more initial setup time
4. There is no evidence right now that indicates they are aware if the console booted normally or if it booted from recovery mode. It seems they cannot detect the change for some technical reason, although I am unsure why exactly.
5. Incognito basically. The author, blawar, is an asshole (don't ask). So, the idea of having to use his software bothers some people, even if that software is the best for the task. I also say to update your OFW, which, while technically unnecessary, has to be done at some point to make the console suitable for online play. The console can be updated prior to or after creating emuMMC. Updating it prior would be less work overall, but just remember to delete WiFi settings after updating.

https://github.com/blawar/incognito

6. SDCard setup is run by Team Atlas as an easy download tool for their repackage of Atmosphere + other apps they call "Kosmos". They have been around for over a year and are very trustworthy. They are a good source for a template, but they made the decision to stop including sig/es patches recently. Be sure to download those seperately. Also, their site tends to be updated less than their Kosmos Github page. Make sure the site uses the latest version of Atmosphere, otherwise, download it, but then swap the related files from their repository: https://github.com/AtlasNX/Kosmos/releases .

Itsuki235 - thanks for all the help the switch arrived today and i have started most of the setup. Just a few more questions if i can?

1 - I did the emuMMC before the NAND backup. Will that make any issues do you think?
2 - When i setup up the 90dns and incognito are those settings applied across the CFW and OFW? And as i said before if i buy Mario Kart 8 and want to play it online, ill have to setup a nintendo id and account does this have any affect and will i be ok purchasing an online membership? (other than the inherent possible ban risks) Im guessing its just ensuring that connect only on OFW to play Mario, delete wifi settings after and then use CFW each time that i want to do it.
3 - with regards to the below - is that what you'd recommend:

Launching the Homebrew Menu
You will now be able to launch the Homebrew Menu by holding the R button while launching any game (including demos/cartridges), application (e.g. Youtube/Hulu), or the album. If R is not held, the album, game, or application will launch like normal.

A note about using the album for the Homebrew Menu

• Using the album for the Homebrew Menu instead of a game or application has several limitations, including but not limited to: a smaller amount of available memory (RAM), as well as being unable to launch a full-featured web browser. It is strongly recommended to launch homebrew through applications or games instead. If your games don't show up as "installed" on your switch, copy the contents of the Nintendo folder from the root of the sd card to the emummc/RAW1/Nintendo folder

If not could you point me in th right direction

4 - sorry to ask again but you said to update the official firmware to the latest. Is that via the software update on OFW and should that be 9 still or is there a way to put it at 8.1 if that's better?

thanks

 

[Itsuki235]

1. Just make a NAND backup now. As long as the system was never booted to OFW, then sysnand is still clean.
2. 90DNS/Incognito are specific to each nand instance, and 90DNS is also specific to every WiFi network. So Sysnand and emuMMC would each be a different instance. 90DNS also has to be applied every time which is why it is so error prone.
If buying MK8 digitally, then emuMMC should be made after downloading it and linking the account. Then that MK8 instance would be present in both sysnand and the emuMMC. For the cartridge version, that does not matter.
With regards to linking accounts, emuMMC/CFW should never connect online. Creating/Linking the account should only ever be done on sysnand+stock. Then delete the WiFi settings, create emuMMC, install CFW/Incognito.
The homebrew menu is setup to use the Album menu by holding R by default in Kosmos. There is no reason to change that setting.
4. Playing online will require 9.0.0 currently as that is the latest version so updating the sysnand using the official update method is best. For the emuMMC using CFW, that can be downgraded safely to 8.1.0 if emuMMC is created after updating to 9.0.0, or left/upgraded to 8.1.0. Either firmware version will work currently for essential homebrew.

 

[Mr_P]

1. Just make a NAND backup now. As long as the system was never booted to OFW, then sysnand is still clean.
2. 90DNS/Incognito are specific to each nand instance, and 90DNS is also specific to every WiFi network. So Sysnand and emuMMC would each be a different instance. 90DNS also has to be applied every time which is why it is so error prone.
If buying MK8 digitally, then emuMMC should be made after downloading it and linking the account. Then that MK8 instance would be present in both sysnand and the emuMMC. For the cartridge version, that does not matter.
With regards to linking accounts, emuMMC/CFW should never connect online. Creating/Linking the account should only ever be done on sysnand+stock. Then delete the WiFi settings, create emuMMC, install CFW/Incognito.
The homebrew menu is setup to use the Album menu by holding R by default in Kosmos. There is no reason to change that setting.
4. Playing online will require 9.0.0 currently as that is the latest version so updating the sysnand using the official update method is best. For the emuMMC using CFW, that can be downgraded safely to 8.1.0 if emuMMC is created after updating to 9.0.0, or left/upgraded to 8.1.0. Either firmware version will work currently for essential homebrew.

tbh i loaded the system up first with no internet at all connected even now to check the firmware was right and it hadn't been used/updated. After that the emuMMC was created, then a NAND backup. I have followed the tutorial you recommended otherwise. Just at the point where i want to update the CFW. Also i haven't activated autoRCM but looks like i will.

Lastly - AutRCM ? Shuld i enable when updating CFW - heard about it being difficult to come out of it. My concern is again playing online from stock or is choosing Stock SYS from atmosphere ok for online

 

[Itsuki235]

It is possible to boot stock after activating autoRCM by deactivating it in Hekate. Tools-> Archive bit * AutoRCM -> AutoRCM On -> change to disabled.

Booting in a semi-stock fashion is also possible with the default entries present with Kosmos for Hekate. It is very easy to go back and forth from autoRCM enabled to disabled as long as you have a reliable jig. High quality ones are usually bundled with RCM dongles.

 

[Mr_P]

It is possible to boot stock after activating autoRCM by deactivating it in Hekate. Tools-> Archive bit * AutoRCM -> AutoRCM On -> change to disabled.

Booting in a semi-stock fashion is also possible with the default entries present with Kosmos for Hekate. It is very easy to go back and forth from autoRCM enabled to disabled as long as you have a reliable jig. High quality ones are usually bundled with RCM dongles.

Ok, so just to clarify:

If i choose not to have AutoRCM when updating CFW it will be good but i will need to use the jig every time as well as the payload injected. It will boot stock otherwise and all should be as we discussed a little earlier, including account and online.
If i do then it will default boot into CFW and in order to go back to a stock option i will need to use the jig etc again and disable the AutoRCM but with the same OFW options?

To check then what if i choose the stock / Sysnand boot from the CFW??? (BTW i have edited the Sysnand CFW option out of the ill file so that can't be chosen)

 

[Itsuki235]

The jig is only needed when going from stock->AutoRCM mode. AutoRCM->DisablingAutoRCM or AutoRCM -> Booting stock does not require a jig. If using the Kosmos pack, choose to reboot to Hekate using the Kosmos Toolbox.

"Updating CFW" means using the newest Atmosphere/ReiNX/SXOS. That is performed by updating files on the SD card.

Updating the firmware, or updating Horizon, means updating the operating system that the switch uses after booting up. Updating the firmware to the latest version 9.0.0 can be done with or without AutoRCM. There is no reason not to leave it enabled until you are ready to switch to stock/OFW and ChoiDujourNX (the homebrew that allows for offline upgrades of the firmware) enables it by default. It can be disabled, but there is no reason to not have it always on.