Hacking SWITCH NOOB PARADISE - Ask questions here

[DooKuu]

The simplest answer is setting up an emuMMC. You can run all of your homebrew apps and CFW in emuMMC then go online with sysMMC. While SX OS has the ability to setup emuMMC, I would recommend using Hekate to setup emuMMC instead.

As for going online, you will need to restore your eMMC backup to your sysMMC first. Seeing as your eMMC backup is in 7 parts, I'm assuming it was made with SX OS. Now while I know SX OS also supports restoring backups, I think it would still be a better idea to use Hekate to restore it rather than SX OS since Hekate has a verification feature. So once you restore your eMMC backup, your console will revert back into the state it was in when you first made that backup which hopefully is clean meaning made before ever running any CFW or homebrew.

Hey bud

Thanks for the quick response I really appreciate it as the itch to play some Switch is really getting bad. haha.

Is the eMMC the same as the SysNAND that I have? Also you're 100% correct that I made that SysNand backup with SX OS that contains those 7 bin files. The SysNAND clean backup was all I thought I needed if I wanted to ever keep my switch clean and revert at any point with no future bans... guess I took a gamble.

The only other "backups" I made was copying the contents off the SD card which had the following folder Nintendo, Album, Contents (inside this folder is just placehld, registered, private, private 1)

Yes my SysNAND backup was made before running any CFW except I'm not sure how that works exactly as I had to create it with SX OS from the Switch with dongle and jig installed if I remember correctly.

So would I have to format the SD card, get Hekate, follow the instructions and dongle thingy, creating a emuMMC with Hekate (basically getting rid of SX OS and in turn getting Hekate) then using Hekate I would have to restore my SysNAND which was created by SX OS to the sysMMC?

Giving me the option to still use custom firmware and switch between Hekate and OFW?

Sorry this is extremely confusing and now I'm worried because the only backup I have is that 7 part SysNAND created by SX OS but I made sure to create that before going any further with instructions to keep my SysNAND as clean as possible.

I'm basically willing to format everything back to only stock OFW with my SysNAND backup and then redoing all the other steps to get Hekate, SX OS, Atmosphere and other CFW's installed and running as long as this still allows me to maintain my original Nintendo account with online functionality without any possible flaggins or bans while also being able to boot into my desired CFW if I wish without comprising my ability to use online functions with my main Nintendo account. (I really do not want my account or console flagged or banned that's why I would rather just go back to stock FW with the 10.0.4 SysNAND and be able to play my carts and online features, but I assume that will take away any chances of CFW in the future which I am okay with if I can get back to stock without any bans)

P.S I know this is like wanting to have the cake and eat it. . . a lot to ask for.

Sorry I am a complete noob and haven't touched my Switch in ages or anything FW related, been to busy.

What is the safest way for me to currently boot my Switch. It was running SX OS and died completely for a few months. I'm not sure if I had autoRCM enabled or not can't remember.

 

[Draxzelex]

Hey bud

Thanks for the quick response I really appreciate it as the itch to play some Switch is really getting bad. haha.

Is the eMMC the same as the SysNAND that I have? Also you're 100% correct that I made that SysNand backup with SX OS that contains those 7 bin files. The SysNAND clean backup was all I thought I needed if I wanted to ever keep my switch clean and revert at any point with no future bans... guess I took a gamble.

The only other "backups" I made was copying the contents off the SD card which had the following folder Nintendo, Album, Contents (inside this folder is just placehld, registered, private, private 1)

Yes my SysNAND backup was made before running any CFW except I'm not sure how that works exactly as I had to create it with SX OS from the Switch with dongle and jig installed if I remember correctly.

So would I have to format the SD card, get Hekate, follow the instructions and dongle thingy, creating a emuMMC with Hekate (basically getting rid of SX OS and in turn getting Hekate) then using Hekate I would have to restore my SysNAND which was created by SX OS to the sysMMC?

Giving me the option to still use custom firmware and switch between Hekate and OFW?

Sorry this is extremely confusing and now I'm worried because the only backup I have is that 7 part SysNAND created by SX OS but I made sure to create that before going any further with instructions to keep my SysNAND as clean as possible.

I'm basically willing to format everything back to only stock OFW with my SysNAND backup and then redoing all the other steps to get Hekate, SX OS, Atmosphere and other CFW's installed and running as long as this still allows me to maintain my original Nintendo account with online functionality without any possible flaggins or bans while also being able to bought into my desired CFW if I wish without comprising my ability to use online functions with my main Nintendo account. (I really do not want my account or console flagged or banned that's why I would rather just go back to stock FW with the 10.0.4 SysNAND and be able to play my carts and online features, but I assume that will take away any chances of CFW in the future which I am okay with if I can get back to stock without any bans)

Sorry I am a complete noob and haven't touched my Switch in ages or anything FW related, been to busy.

What is the safest way for me to currently boot my Switch. It was running SX OS and died completely for a few months. I'm not sure if I had autoRCM enabled or not can't remember.

You seem to be confused on the proper terminology. There is no such thing as "sysNAND" for the Switch. The Switch doesn't have a NAND chip, it uses an eMMC instead therefore proper terminology involves usage of the word "eMMC". Otherwise, the steps you outlined are perfectly fine to follow. Its always better to do research and ask questions because you never know if you are at risk for making a mistake. Feel free to ask more questions after you are done if there is anything else bothering you.

 

[DooKuu]

Okay awesome.

Sorry like I said I am a bit confused and scared at the moment.

I only have the SysNAND created by SXOS and now I do not even know how to uninstall all CFW and go back to OFW because Hekate uses more files and paths for their backup of the SysNAND.

I'm over CFW and just want OFW back to play online and download my games like normal.

END GOAL: Delete all traces of CFW, restore the backup SysNand created by SXOS, get Switch to original state with just normal OFW only to use as intended.

 

[DooKuu]

So I booted into SXOS splash screen emuNAND was enabled, and I had the option to boot into that or into Original stock firmware.

I would like to know can I just keep the switches as is and continue like normal with updates and physical games if I choose not to enable AutoRCM and boot normally?

I am currently on FW 10.0.4 in the emuNAND
and
OFW is 10.0.2 which I would like to update?

I would honestly just like to completely remove all traces of any custom firmware and backup using the SysNAND backup created by SXOS but does not seem to include all the files needed by the Hekate guides.

Can I just format the SD card completely and then use some tool to install my original SysNAND and use my Switch like normal?

 

[Draxzelex]

So I booted into SXOS splash screen emuNAND was enabled, and I had the option to boot into that or into Original stock firmware.

I would like to know can I just keep the switches as is and continue like normal with updates and physical games if I choose not to enable AutoRCM and boot normally?

I am currently on FW 10.0.4 in the emuNAND
and
OFW is 10.0.2 which I would like to update?

I would honestly just like to completely remove all traces of any custom firmware and backup using the SysNAND backup created by SXOS but does not seem to include all the files needed by the Hekate guides.

Can I just format the SD card completely and then use some tool to install my original SysNAND and use my Switch like normal?

If you haven't already restored your clean eMMC backup, now would be the time to do so. There is no other way to prevent a ban. As I explained earlier, you already have all of the files; it is only a matter of placing them on the SD card then restoring them via Hekate.

 

[cukiyoko]

Hi guys,

So, I've got my unpatched, unbanned switch ready to go, and just want to triple check:

This is the most up-to-date, recommended guide, yes?

https://switch.homebrew.guide/

Also, I was wondering what the purpose of a dongle is? I mean, once you've successfully hacked your switch?

 

[Hayato213]

Hi guys,

So, I've got my unpatched, unbanned switch ready to go, and just want to triple check:

This is the most up-to-date, recommended guide, yes?

https://switch.homebrew.guide/

Also, I was wondering what the purpose of a dongle is? I mean, once you've successfully hacked your switch?

The hack isn't permanent every time you shut off the unit you need the dongle again to inject payload if that is how you are injecting payload. No suggestion on guide though, you would want to use an emunand (emulated NAND) if you want to keep the Sysnand for online play.

 

[cukiyoko]

The hack isn't permanent every time you shut off the unit you need the dongle again to inject payload if that is how you are injecting payload. No suggestion on guide though, you would want to use an emunand (emulated NAND) if you want to keep the Sysnand for online play.

Ah, thank you. Do you mean when the switch goes to sleep, or only when you power it off completely. Is it something I should get?

I also found this guide - would you say it's more relevant?

https://rentry.co/SwitchHackingIsEasy

 

[Hayato213]

Ah, thank you. Do you mean when the switch goes to sleep, or only when you power it off completely. Is it something I should get?

I also found this guide - would you say it's more relevant?

https://rentry.co/SwitchHackingIsEasy

When the system completely power off when you power back on again you need to use the Jig and the payload dongle to inject a payload again, it ain't permanent. No suggestion on guide.

Well you need to understand how the CFW work, and which bootloaders to use and which signature patches that goes a long with it, there are certain patches go along with certain bootloaders, as for Hekate/Fss0 build you need hekate patches, as for Fusee-Primary, you use fusee patches. You can chainload fusee primary from hekate . First thing I would recommend is load up Hekate and do a NAND backup prior to loading CFW.

Hekate patches
Hekate-> Fusee Secondary

Fusee Patches
Hekate->Fusee-Primary-> Fusee Secondary
Fusee-Primary-> Fusee Secondary

 

[cukiyoko]

When the system completely power off when you power back on again you need to use the Jig and the payload dongle to inject a payload again, it ain't permanent. No suggestion on guide.

Well you need to understand how the CFW work, and which bootloaders to use and which signature patches that goes a long with it, there are certain patches go along with certain bootloaders, as for Hekate/Fss0 build you need hekate patches, as for Fusee-Primary, you use fusee patches. You can chainload fusee primary from hekate . First thing I would recommend is load up Hekate and do a NAND backup prior to loading CFW.

Hekate patches
Hekate-> Fusee Secondary

Fusee Patches
Hekate->Fusee-Primary-> Fusee Secondary
Fusee-Primary-> Fusee Secondary

Ah, great - I understand the dongle a bit better, do you have to keep it in when playing, or is it just a tool to use every now and then?

I really appreciate your trying to help, but I'm completely lost. Things seem a lot more complicated all of a sudden. I'd just like to know what the current recommendations are and how to get started.

OK, this guide seems pretty accurate, but I'm kind of scared to start now.
https://nh-server.github.io/switch-guide/

 

[Hayato213]

Ah, great - I understand the dongle a bit better, do you have to keep it in when playing, or is it just a tool to use every now and then?

I really appreciate your trying to help, but I'm completely lost. Things seem a lot more complicated all of a sudden. I'd just like to know what the current recommendations are and how to get started.

OK, this guide seems pretty accurate, but I'm kind of scared to start now.
https://nh-server.github.io/switch-guide/

The payload dongle and the jig is only needed when injecting payload, after it load you can take it off. Recommendation is to do some reading, understand how CFW work, what bootloader and signature patches to use would help you in the long run.

https://gbatemp.net/threads/guide-to-choose-which-atmosphere-patches-to-use-on-switch-fw-10.563886/

this help explain patches a bit.

 

[cukiyoko]

The payload dongle and the jig is only needed when injecting payload, after it load you can take it off. Recommendation is to do some reading, understand how CFW work, what bootloader and signature patches to use would help you in the long run.

https://gbatemp.net/threads/guide-to-choose-which-atmosphere-patches-to-use-on-switch-fw-10.563886/

this help explain patches a bit.

Thanks, I'll do my best, this is a lot harder than I thought it would be...

 

[harticho]

Hello everyone, I've decided to FINALLY get a Switch but I'm a bit lost... If someone can enlighten me on these points, I'd be grateful

First thing first: if I get a V1 version, is it 100% sure I can hack it? It would me mainly for Retroarch. Previous user probably upgraded stuff so I want to be sure it will still work

 

[Hayato213]

Hello everyone, I've decided to FINALLY get a Switch but I'm a bit lost... If someone can enlighten me on these points, I'd be grateful

First thing first: if I get a V1 version, is it 100% sure I can hack it? It would me mainly for Retroarch. Previous user probably upgraded stuff so I want to be sure it will still work

You need v1 unpatched if you want 100% CFW access without the need of a modchip.

 

[harticho]

Ok, and you know that with the serial number, right?

 

[Draxzelex]

Ok, and you know that with the serial number, right?

Well yes but the serial number can only get you so far especially if its in the orange section which is "Possibly Patched". The definitive way to find out would be to test the exploit on the console. You do not have anything to fear by trying it out since even if the exploit fails or succeeds, nothing will immediately happen to the console.

 

[Hayato213]

Ok, and you know that with the serial number, right?

https://gbatemp.net/threads/switch-...he-first-post-before-asking-questions.481215/
https://ismyswitchpatched.com/
https://damota.me/ssnc/checker/

Ideally you want a 100% unpatched unit if you get borderline you have 50% patched 50% unpatched.

 

[harticho]

Well yes but the serial number can only get you so far especially if its in the orange section which is "Possibly Patched". The definitive way to find out would be to test the exploit on the console. You do not have anything to fear by trying it out since even if the exploit fails or succeeds, nothing will immediately happen to the console.

I see what you mean, but you have to understand that unfortunately I won't be able to test the exploit BEFORE buying the console :/ That's why I want to be sure that the Switch I'm buying is unpatched!

 

[chocoswitch]

Hi guys!

When booting Atmosphere I get this error :

A fatal error occured when running Atmosphere.
Program ID : 010041544d53000
Error Desc: std::abort() called (0xffe)
Report saved to /atmosphere/fatal_errors/report_00000000008243988.bin

Last time I used the switch there was no problem and I did not modify it or the SD card since then.

Any guess on how to fix it please?

I'm running on emuMMC on SD card partition (brand new SD formated FAT32)

Thanks for your help

EDIT : I already tried fixing arch bit via hekate without success

 

[Hayato213]

Hi guys!

When booting Atmosphere I get this error :

A fatal error occured when running Atmosphere.
Program ID : 010041544d53000
Error Desc: std::abort() called (0xffe)
Report saved to /atmosphere/fatal_errors/report_00000000008243988.bin

Last time I used the switch there was no problem and I did not modify it or the SD card since then.

Any guess on how to fix it please?

I'm running on emuMMC on SD card partition (brand new SD formated FAT32)

Thanks for your help

U a Mac user?