Hacking SWITCH NOOB PARADISE - Ask questions here

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
19,011
Trophies
2
Age
29
Location
New York City
XP
13,378
Country
United States
Picked up a brand new hackable Switch last week running 4.1.0 on OFW and loaded up Hekate and Atmosphere after full NAND backup. So far I've done nothing aside from play with the Retroarch NRO and haven't gone once into OFW or loaded a single NSP or updated beyond 4.1.0. I hear you can use a modified eShop NSP to access Homebrew with full RAM access without a ban risk though so now I'm curious.

If I switch from CFW to OFW from the Hekate launcher and try to access the eShop via normal Wi-Fi (no 90DNS) is this a high risk scenario for a ban in itself? I presume it's only risky to access eShop from within a CFW.

Also, would it be better to update to latest system update officially or via Choi at this point? I know the former burns fuses but I'm more concerned about Choi triggering a ban accessing the eShop in OFC. That is unless updating officially kills Hekate/CFW access...

Thanks for any help here!
If you don't restore a clean NAND backup prior to going online, regardless if you're currently in CFW or OFW, you risk getting banned since traces of CFW persist even after the console is shut off.

Also, there is no "better" way to update as both have their pros and cons. Updating without burning fuses lets you retain the ability to downgrade in case future exploits come out for lower firmwares such as a hypothetical untethered coldboot but you risk getting banned this way. You can update officially which will most likely not lead to you getting banned (if done safely) but by doing so, you will irreversibly burn fuses rendering yourself unable to downgrade meaning you may be stuck using a jig and USB cable to boot CFW for a very long time. Weigh which one is more important to you, downgrading or being banned.

Anyone know what s the easiest way of keeping your home brew apps and cfw up to date?

I'm using Kosmo atm and switch has been in airplane mode since I hacked it.
Kosmos has its own updater tool that you can use to update the package whenever there is a new version. You can use this without getting banned if you setup 90DNS on your Wi-Fi settings (they are literally just DNS settings). The offline alternative is downloading the latest Kosmos and replacing any files/folders from the old Kosmos.

Hi, looking for advice from the geniuses on here! I''ve been using sxos for quite a while and have finally created an emunand. I'm on 6.1 at the moment but plan to update to 6.2 with choidujournx.

After creating the emunand I now have an emutendo folder on my sd card - am I supposed to transfer everything from my nintendo folder into that folder? Or only some files? Or just leave it as is? Any help much appreciated!
If you want to transfer, make a copy of your Nintendo folder and rename it to Emutendo. By the way, the Nintendo/Emutendo folder only contains data for installed content on the SD card; it does not have any save data or content installed to internal memory.

Need help, ok so I have SX OS installed emuNAND 6.1.0 and on sysNAND I am on 4.0.1. I updated with ChoiDujourNX with exFAT support. In the SX OS boot menu emuNAND is currently enabled. When I disable it and try to boot CFW the nintendo logo comes up but quickly disappears and I am left with a black screen and have to force shutdown. Is this happening because I updated in emuNAND? Also when I boot up into sysNAND is there anyway to NOT get the “update system to use microSD card” notification? Thank you for the answers!
Your SysNAND's firmware has not been patched for exFAT support. Either patch it by either updating to the latest firmware which will irreversibly burn fuses or with homebrew applications such as ChoiDujourNX. Or the simplest option is reformat the SD card to FAT32.

I will ask again since my first post never got answered. Is there any plans for a game cube and ps2 emulator for the switch? or r there already ones out to download? P.s will they be added to the hb app store.
Retroarch had some Gamecube support however something happened which caused them to pick up support for the N64 over the Gamecube meaning the only option left is running Dolphin via Lakka which is not pretty. PS2 emulation will probably also be handled by Retroarch since there are no other PS2 emulators planned on being added to the Switch.

Hi guys,

Ive been reading as much as i can to prepare myself to install my SXPRO but still have a few questions.

So i know i need to create a back up of my clean NAND before installing the SXPRO cfw, probably a silly question but how is this done?

Also i still need some clarification on updating the system software once CFW is installed. Am i right in saying that once i have created emuNAND i can use ChoiDujourNX to update sysnand from 5.1.0 to 6.1?

is 6.1 the most desirable to to upgrad sysnand to?

Lastly, once i have updated my sysnand to 6.1 what version will emuNAN be on?

Thanks in advance, really appreciate the support this site offers!
You can either use Hekate or SX OS to dump the NAND. I recommend using Hekate since, unlike SX OS, it can verify the backup. Hekate is a payload so you can either send it as the primary payload with a USB-C cable or chainload it from the SX OS menu.

While you can use ChoiDujourNX to update your SysNAND, if you want to play online without getting banned with SysNAND, it would be best to avoid using a homebrew application to update your SysNAND.

Right now, most people would say 6.2 is the "most desirable" firmware since it is the latest firmware and the exploit works on all firmware so most people are going to end up on the latest firmware one way or another.

When EmuNAND is first created, it is a 1:1 copy of your SysNAND so its firmware will be whatever your SysNAND was on when you created EmuNAND.
 

TPMJB

Well-Known Member
Member
Joined
Aug 27, 2014
Messages
204
Trophies
0
Age
35
Location
Syracuse, New York
XP
417
Country
United States
Once you've installed backups, they're installed, whether you're in OFW or in CFW (or which CFW you use). Just be aware that, if you install backups, allowing your switch to connect to Nintendo's servers runs a high risk of a ban - not just launching them (which will error or crash on OFW), but just having them installed - and that's why the guides recommend taking a 'clean nand backup' immediately after launching a payload the first time, BEFORE doing anything CFW-related, homebrew or otherwise, and then blocking Nintendo's servers with 90DNS or removing wifi connections.
I have to correct this. ACTUAL backups don't carry a high risk of ban, e.g. cartridges that you own that are ripped to XCI and installed to the OS. I have done this to all my games. If you rip to the other format you're boned, however.
 

ZanderX420

Well-Known Member
Newcomer
Joined
May 8, 2018
Messages
85
Trophies
0
XP
268
Country
United States
If you don't restore a clean NAND backup prior to going online, regardless if you're currently in CFW or OFW, you risk getting banned since traces of CFW persist even after the console is shut off.

Also, there is no "better" way to update as both have their pros and cons. Updating without burning fuses lets you retain the ability to downgrade in case future exploits come out for lower firmwares such as a hypothetical untethered coldboot but you risk getting banned this way. You can update officially which will most likely not lead to you getting banned (if done safely) but by doing so, you will irreversibly burn fuses rendering yourself unable to downgrade meaning you may be stuck using a jig and USB cable to boot CFW for a very long time. Weigh which one is more important to you, downgrading or being banned.

Kosmos has its own updater tool that you can use to update the package whenever there is a new version. You can use this without getting banned if you setup 90DNS on your Wi-Fi settings (they are literally just DNS settings). The offline alternative is downloading the latest Kosmos and replacing any files/folders from the old Kosmos.

If you want to transfer, make a copy of your Nintendo folder and rename it to Emutendo. By the way, the Nintendo/Emutendo folder only contains data for installed content on the SD card; it does not have any save data or content installed to internal memory.

Your SysNAND's firmware has not been patched for exFAT support. Either patch it by either updating to the latest firmware which will irreversibly burn fuses or with homebrew applications such as ChoiDujourNX. Or the simplest option is reformat the SD card to FAT32.

Retroarch had some Gamecube support however something happened which caused them to pick up support for the N64 over the Gamecube meaning the only option left is running Dolphin via Lakka which is not pretty. PS2 emulation will probably also be handled by Retroarch since there are no other PS2 emulators planned on being added to the Switch.

You can either use Hekate or SX OS to dump the NAND. I recommend using Hekate since, unlike SX OS, it can verify the backup. Hekate is a payload so you can either send it as the primary payload with a USB-C cable or chainload it from the SX OS menu.

While you can use ChoiDujourNX to update your SysNAND, if you want to play online without getting banned with SysNAND, it would be best to avoid using a homebrew application to update your SysNAND.

Right now, most people would say 6.2 is the "most desirable" firmware since it is the latest firmware and the exploit works on all firmware so most people are going to end up on the latest firmware one way or another.

When EmuNAND is first created, it is a 1:1 copy of your SysNAND so its firmware will be whatever your SysNAND was on when you created EmuNAND.
Ok ty
 

Xana

Well-Known Member
Newcomer
Joined
Mar 2, 2016
Messages
73
Trophies
0
XP
253
Country
United States
I have to correct this. ACTUAL backups don't carry a high risk of ban, e.g. cartridges that you own that are ripped to XCI and installed to the OS. I have done this to all my games. If you rip to the other format you're boned, however.

The impression I get from reading through switchbrew is that, if you install any non-legit ticket to your system (which would be any ticket that doesn't originate from a personally owned digital title), you're boned whenever Nintendo decides to sync tickets with their server.
 

Acidburn135

Well-Known Member
Newcomer
Joined
Oct 3, 2013
Messages
61
Trophies
1
Age
38
XP
286
Country
United States
So trying to use a "clean" SysNAND w/ OFW to go online and play legit games and have a EmuNAND that I install NSP, old-gen emulators, Homebrew etc.
I initially made a backup of NAND (4.1) and then had to use choidujournx to update to latest firmware & to also get exFAT SD card support without burning fuses. I then created the EmuNAND on SD card. Nothing else has been done yet. Before I take SysNAND/OFW online did updating with Choidujournx make my SysNAND "dirty" and have stuff on telemetry ping my account when I go online? Not sure what other option I have since updating officially will burn my fuses.

Also, I read another thread about unlinking SysNAND from EmuNAND. Isn't creating it on SD card already keeping the 2 seperate?
 

jackirate

Active Member
Newcomer
Joined
Dec 7, 2016
Messages
36
Trophies
0
Age
35
XP
61
Country
You can either use Hekate or SX OS to dump the NAND. I recommend using Hekate since, unlike SX OS, it can verify the backup. Hekate is a payload so you can either send it as the primary payload with a USB-C cable or chainload it from the SX OS menu.

While you can use ChoiDujourNX to update your SysNAND, if you want to play online without getting banned with SysNAND, it would be best to avoid using a homebrew application to update your SysNAND.

Right now, most people would say 6.2 is the "most desirable" firmware since it is the latest firmware and the exploit works on all firmware so most people are going to end up on the latest firmware one way or another.

When EmuNAND is first created, it is a 1:1 copy of your SysNAND so its firmware will be whatever your SysNAND was on when you created EmuNAND.

Firstly, thanks again for the detailed response, It must get tiring repeating yourself so for that im sorry!

Okay so once emuNAND is set up and i have updated it with ChoiDujourNX will i then be able to update my sysnand just by removing the memory card and taking the console online? If n will not that burn the fuses?

About online play, im not looking to take anything illegitimate online from my emuNAND, but lets say i remove my memory card and the sysnand is up to date i could use my bought carts to play?
 

Notshane

Well-Known Member
Member
Joined
Dec 13, 2012
Messages
204
Trophies
0
XP
359
Country
United States
You seem to not want to use the hardware exploit, given that you want to avoid injecting payloads. Yes, the hardware exploit is firmware-independent and unpatchable, but it will also always require a payload injection. I was suggesting that, if you want to maintain the highest chance of a haxchi-like coldboot exploit, maintaining the ability to downgrade is desirable.

Oh, well, that's good to know then. I was mainly hoping for it to be easier like Haxchi was in the future, but I do want to mod Ultimate, so knowing it'll still be safe to go up to 5.1 and still use a payload, I can live with that. Sorry about the confusion. Oh, I think I asked this once before, but if I were to go up to 5.1, do I have to backup the NAND again?
 

Xana

Well-Known Member
Newcomer
Joined
Mar 2, 2016
Messages
73
Trophies
0
XP
253
Country
United States
Oh, well, that's good to know then. I was mainly hoping for it to be easier like Haxchi was in the future, but I do want to mod Ultimate, so knowing it'll still be safe to go up to 5.1 and still use a payload, I can live with that. Sorry about the confusion. Oh, I think I asked this once before, but if I were to go up to 5.1, do I have to backup the NAND again?

You'll probably want to take a new one regardless in order to save yourself the hassle of re-updating if you need to restore it, but if you burn fuses (no AutoRCM), then you'll definitely want to take a new NAND backup.
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
19,011
Trophies
2
Age
29
Location
New York City
XP
13,378
Country
United States
So trying to use a "clean" SysNAND w/ OFW to go online and play legit games and have a EmuNAND that I install NSP, old-gen emulators, Homebrew etc.
I initially made a backup of NAND (4.1) and then had to use choidujournx to update to latest firmware & to also get exFAT SD card support without burning fuses. I then created the EmuNAND on SD card. Nothing else has been done yet. Before I take SysNAND/OFW online did updating with Choidujournx make my SysNAND "dirty" and have stuff on telemetry ping my account when I go online? Not sure what other option I have since updating officially will burn my fuses.

Also, I read another thread about unlinking SysNAND from EmuNAND. Isn't creating it on SD card already keeping the 2 seperate?
ChoiDujourNX may have made your SysNAND dirty.

And the issue with unlinking was an old one. EmuNAND and SysNAND both used the same "Nintendo" folder but you can install content in EmuNAND/SysNAND which will cause a disparity thus leading to the opposite NAND you didn't install said content to not recognize the Nintendo folder and then delete the folder. However now EmuNAND makes its own "Emutendo" folder so EmuNAND and SysNAND are now unlinked by default.

Firstly, thanks again for the detailed response, It must get tiring repeating yourself so for that im sorry!

Okay so once emuNAND is set up and i have updated it with ChoiDujourNX will i then be able to update my sysnand just by removing the memory card and taking the console online? If n will not that burn the fuses?

About online play, im not looking to take anything illegitimate online from my emuNAND, but lets say i remove my memory card and the sysnand is up to date i could use my bought carts to play?
If you update online, it will burn fuses, EmuNAND or SysNAND.

And if SysNAND is up to date, you can play your retail cartridges online. However I don't see the need to remove the SD card since there is no evidence Nintendo scans the SD card. They don't even scan the internal memory of the Switch.
 

jackirate

Active Member
Newcomer
Joined
Dec 7, 2016
Messages
36
Trophies
0
Age
35
XP
61
Country
ChoiDujourNX may have made your SysNAND dirty.

And the issue with unlinking was an old one. EmuNAND and SysNAND both used the same "Nintendo" folder but you can install content in EmuNAND/SysNAND which will cause a disparity thus leading to the opposite NAND you didn't install said content to not recognize the Nintendo folder and then delete the folder. However now EmuNAND makes its own "Emutendo" folder so EmuNAND and SysNAND are now unlinked by default.

If you update online, it will burn fuses, EmuNAND or SysNAND.

And if SysNAND is up to date, you can play your retail cartridges online. However I don't see the need to remove the SD card since there is no evidence Nintendo scans the SD card. They don't even scan the internal memory of the Switch.

Okay i think im getting there aha. Ive had a look at Hekate it mentiones supporting ExFat but not Fat32 which is what i have formatted my card to after SX recommendation. Does it support 32 and if not i should just use the SXPRO to create the back up?

I remember from installing cfw on my 3ds that i had to set up SD in a specific way with folders ect but there is zero mention of this anywhere? Are files just good on the Root?
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
19,011
Trophies
2
Age
29
Location
New York City
XP
13,378
Country
United States
Okay i think im getting there aha. Ive had a look at Hekate it mentiones supporting ExFat but not Fat32 which is what i have formatted my card to after SX recommendation. Does it support 32 and if not i should just use the SXPRO to create the back up?

I remember from installing cfw on my 3ds that i had to set up SD in a specific way with folders ect but there is zero mention of this anywhere? Are files just good on the Root?
Hekate supports both exFAT and FAT32. Also, Hekate supports exFAT even if your system doesn't support exFAT because its loaded outside of the system.

Whatever guide you're following will tell you how to setup the file structure. Generally, all homebrew applications go in the /switch folder and all CFW files go in /"name of the specific CFW" folder. There are some other caveats that are specific to certain CFW. Also all of these folders should be on the root.
 
  • Like
Reactions: jackirate

TPMJB

Well-Known Member
Member
Joined
Aug 27, 2014
Messages
204
Trophies
0
Age
35
Location
Syracuse, New York
XP
417
Country
United States
The impression I get from reading through switchbrew is that, if you install any non-legit ticket to your system (which would be any ticket that doesn't originate from a personally owned digital title), you're boned whenever Nintendo decides to sync tickets with their server.
Right, that's what I've gleaned as well. The stuff I do is all legitimate so I'm gonna be pretty upset if I'm banned. Yeah maybe in the 360 days I earned my dozen or so bans, but this time I'm turning over a new leaf :)
 

Notshane

Well-Known Member
Member
Joined
Dec 13, 2012
Messages
204
Trophies
0
XP
359
Country
United States
You'll probably want to take a new one regardless in order to save yourself the hassle of re-updating if you need to restore it, but if you burn fuses (no AutoRCM), then you'll definitely want to take a new NAND backup.

Alright, thank you.
 

Adran_Marit

Walküre's Hacker
Member
Joined
Oct 3, 2015
Messages
3,781
Trophies
1
Location
42*South
XP
4,552
Country
Australia
I backed up my 2.1.0, but they are all separated:

w9a90w.jpg


In the videos I saw, it's normally just one "rawnand.bin" so I am confused. Should I just accept this result or will it be screwed up if I ever revert it.


this is fine. you just need to join them with these SCRIPTS
 

Outlawbiker

Active Member
Newcomer
Joined
Jan 19, 2017
Messages
29
Trophies
0
Age
42
XP
211
Country
United States
Just got a brand new switch today. Got lucky and found an unpatched one and on 4.1.0. I wanted to get my switch backed up before i did anything to it, i got Komos/atmosphere/hekate on the sd card, struggled to jump the pins,followed a guide here and noticed 2 things so far.

1. i can find anything in my hekate to backup or show biskeys,do i need to? if so,how?
2. i have 5 burnt fuses already ??????

I checked all the packaging over and over again,this was a brand new never used console, is it normal to have fuses already burnt? i havent upgraded or messed with this other than to put it in airplane mode/disable auto updates/never connected to the net, and just tried to back up the nand. any thoughts?
 
Last edited by Outlawbiker,

supersega

Well-Known Member
Newcomer
Joined
Apr 25, 2018
Messages
83
Trophies
0
Location
A place in a place
XP
184
Country
United States
Just got a brand new switch today. Got lucky and found an unpatched one and on 4.1.0. I wanted to get my switch backed up before i did anything to it, i got Komos/atmosphere/hekate on the sd card, struggled to jump the pins,followed a guide here and noticed 2 things so far.

1. i can find anything in my hekate to backup or show biskeys,do i need to? if so,how?
2. i have 5 burnt fuses already ??????

I checked all the packaging over and over again,this was a brand new never used console, is it normal to have fuses already burnt? i havent upgraded or messed with this other than to put it in airplane mode/disable auto updates/never connected to the net, and just tried to back up the nand. any thoughts?

I know nothing about software part, but are you sure they are fuses that are blown? If so, pictures please? You may be looking at a film capacitor.
 

Xana

Well-Known Member
Newcomer
Joined
Mar 2, 2016
Messages
73
Trophies
0
XP
253
Country
United States

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    HiradeGirl @ HiradeGirl: Wlak like a Wlaker