Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,098,565
  • Replies Replies 47,953
  • Likes Likes 66
Thank for your answer, now i am able to run game, but only by using using Fusee payload in RCM, sysMMC and emuMMC don't let me start the game, is this the right method right now ? Actually I have no problem playing game, no crash or whatsoever, what make me curious is homebrew saying i'm running in applet mode.

applet mode doesn't have all the available memory, so some homebrew might not run well, as for how to enter full ram mode, hold down r button while entering a game or install the homebrew menu nsp forwarder to access full ram mode.
 
  • Like
Reactions: Lacius
I was able to migrate from SX to Atmosphere. (Previously was using only SX on sysnand, now using Atmosphere on emunand, and no need for SX anymore)
I have two minor problems since doing this. #1. Every previous game I had installed shows up when Atmos emunand boots up, however every game prompts me with the "Some necessary data could not be found. It will be downloaded now.", and if I click on "Start Software" it then prompts for a software update....this is happening to EVERY game that existed prior to the migration to Atmosphere...
I can see the SD card space is taken up by the games so they are actually installed. Just the Switch "thinks" they aren't. If I install a new nsp, that new title works fine however.

Using Goldleaf to browse the system, I see I have at the root of my SD card a Nintendo folder, and also a emuMMC folder. Am I supposed to just move the Nintendo folder into the emuMMC folder? I don't have room to copy it over without moving, it's too big. (If this is the correct step/fix, does it have to go into a subfolder in the emuMMC folder?? Will it still remember all the game saves and such on the emunand side?)

#2. When I power on the switch (using the SX jig/dongle) I can NOT get back into Hekate since completing/migrating to Atmosphere. It just ALWAYS boots into Atmosphere emunand, which generally is fine. BUT....it would be nice in case I need to ever run a different payload or have some issue that I need to get into hekate and use some tool, idk.

I have tried to hold down either vol + or vol -, as typical, but it does nothing like it used to when I was still using SX to get into the SX boot menu/select sys or CFW and such. Any help is appreciated. Thank you!
 
Last edited by Bonovox40, , Reason: error description clarity
Hello everyone. I've been reading a lot of guides and threads in different languages and full-time in the previous 3 days with the only outcome of me being so burned out and confused that I'm scared AF to even do the simplest things. Hopefully you will kindly erase any doubts about these following question. Sorry if they've already been answered many times.

So, I bought a refurbished unpatched console that came with firmware 12.0.1. After the initial account and WiFi setup , I was prompted to upgrade the firmware. I did not do that. I powered off my console and injected a test payload to be 100% sure it was hackable, and it is. And here my brain starts to crash:

1) Should I go online and upgrade the firmware before taking a NAND backup?

2) Many hacking guides say it is very important to have at least a game cartridge inserted or an eshop application/demo installed on the console before taking any further steps. On the other hand, many guides state that the cleanest NAND backup is just with no wifi + airplane mode and they do not mention any app/cartridge. Who should I trust?

3) About efuses. I think I shouldn't worry about them since my switch came with OFW 12.0.1. Should I?

4) I'm going to setup an emunand on a yet-to-be-bought 256 GB microsd. Many say to avoid nintendo licensed ones and to go with Sandisk. Someone else says Samsung is better. Which one should I go for?

5) Is AutoRCM eventually going to get me banned once I go online with sysnand? I've read it writes 1 byte to the sysNAND so I'm a bit worried.

6) Will I ever be able to go online on emunand without getting banned? I've read many things about 90DNS and Incognito and I became convinced they add more "suspiciousness" to my activities than ban-proofing. Should I go online only on my sysnand?

And I think that's it. These are the things that worry me the most as I don't know which source to trust. I've decided to trust this community and I'm only going to ask here, so I really appreciate you for reading thus far and sorry for being so dramatically verbose.
  1. No, make an eMMC backup before doing anything further including updating the firmware
  2. You can trust both. While it is important to have a cartridge or an eShop app, it is not absolutely required. And a clean eMMC backup only refers to one made before running CFW or homebrew so it has nothing to do with retail carts or eShop titles
  3. There is no advantage to burning efuses so I'd recommend trying to preserve them if possible. You never know when a new exploit for lower firmware versions could be released
  4. The brand of your SD card is not very important. What is more important is that it is not fake. While it is tricky to determine if it is fake or not before purchasing, a good rule of thumb is that if the deal is too good to be true or very cheap, then it is most likely fake. Either way, test the SD card with a program like FakeFlashTest to ensure it is not fake
  5. There is always a risk of being banned if you go online with CFW or homebrew. It has nothing to do with sysMMC or emuMMC; everyone is banned for usage of CFW/homebrew.
I have read many threads from sxos users that there likely will never be another update to sxos.

Found the thread on how to migrate from sxos to atmosphere.

My questions are just to confirm a couple things before I go through the motion of doing that.

I have a couple switches for my kids, they are autoRCM I believe it is referred to as.

From a powered off state I insert the SX pro dongle and it boots up and then I go to the photo album to easily install NSP’s off a USB attached HD attached to the doc onto the micro sd card in the switch.

1. If I replace sxos, can I still use the sxpro dongle to boot up from a powered off state to Atmosphere?

2. And is it as easy to install NSP’s like I do in Sxos right from the photo album app (sx os) to the internal micro sd card running Atmosphere? (meaning I can install these NSP's from a USB attached hard drive to the dock like I currently do with sxos)

3. If I do the migration to the most current version of Atmosphere, then I am free to update to 12.0.3 if I wanted to then in the same way I always did before under sxos (ChoiDujour I believe is what I have always used) I have usually stayed one minor version behind in switch firmware.
  1. Yes, just be aware that the dongle will automatically load the SX OS menu by default so you will need to hold volume + in order to chainload into Atmosphere either via the fusee or hekate payload
  2. You will have to use a separate homebrew application to install .NSP files because Atmosphere does not come with one. I recommend using TinWoo Installer to install all of your .NSP files. You will also need patches to launch said .NSP files which you can find in the pinned thread on this forum
  3. ChoiDujour only supports up to firmware 6.2. For a more up-to-date firmware installer, you can use the homebrew app Daybreak which comes bundled with Atmosphere by default
I was able to migrate from SX to Atmosphere. (Previously was using only SX on sysnand, now using Atmosphere on emunand, and no need for SX anymore)
I have two minor problems since doing this. #1. Every previous game I had installed shows up when Atmos emunand boots up, however every game prompts me with the "Some necessary data could not be found. It will be downloaded now.", and if I click on "Start Software" it then prompts for a software update....this is happening to EVERY game that existed prior to the migration to Atmosphere...
I can see the SD card space is taken up by the games so they are actually installed. Just the Switch "thinks" they aren't. If I install a new nsp, that new title works fine however.

Using Goldleaf to browse the system, I see I have at the root of my SD card a Nintendo folder, and also a emuMMC folder. Am I supposed to just move the Nintendo folder into the emuMMC folder? I don't have room to copy it over without moving, it's too big. (If this is the correct step/fix, does it have to go into a subfolder in the emuMMC folder?? Will it still remember all the game saves and such on the emunand side?)

#2. When I power on the switch (using the SX jig/dongle) I can NOT get back into Hekate since completing/migrating to Atmosphere. It just ALWAYS boots into Atmosphere emunand, which generally is fine. BUT....it would be nice in case I need to ever run a different payload or have some issue that I need to get into hekate and use some tool, idk.

I have tried to hold down either vol + or vol -, as typical, but it does nothing like it used to when I was still using SX to get into the SX boot menu/select sys or CFW and such. Any help is appreciated. Thank you!
  1. Did you download the patches to launch backups and place them on your SD card? If not, you can download them from the pinned thread on this forum
  2. Are you using the fusee payload to launch into Atmosphere? If so, then you have to switch to using Hekate to launch Atmosphere instead in order to enter the Hekate menu
 
  • Like
Reactions: Montblanc
Hi, what's the best way to upgrade SD cards? I am currently using exfat on a 256gb card, want to upgrade to a new 512gb card but not sure what the latest tools or guides to help me are. I have emunand, which is why i ask.
 
There is no advantage to burning efuses so I'd recommend trying to preserve them if possible. You never know when a new exploit for lower firmware versions could be released

First of all, thank you so much for your time and sorry for the hassle. I think the Switch wants to upgrade to 12.1.0 from 12.0.1. Let me get this straight: is it because upgrading from 12.0.1 to 12.0.2+ burns one more fuse according to this list? So I will take a backup at the current state, but won't I be forced to upgrade OFW nonetheless if I want to play legit online on my sysnand?

There is always a risk of being banned if you go online with CFW or homebrew. It has nothing to do with sysMMC or emuMMC; everyone is banned for usage of CFW/homebrew.

So don't you think that switching from emunand (no wifi) to sysnand (wifi) would trigger some mismatch in e.g. titles, firmware and so on that would flag me immediately? Sorry for the stupid questions but I greatly appreciate your help.

Also, I bought a Samsung Evo Select sold and shipped by Amazon so I think I should be safe but I will run the test as suggested. Thank you!
 
First of all, thank you so much for your time and sorry for the hassle. I think the Switch wants to upgrade to 12.1.0 from 12.0.1. Let me get this straight: is it because upgrading from 12.0.1 to 12.0.2+ burns one more fuse according to this list? So I will take a backup at the current state, but won't I be forced to upgrade OFW nonetheless if I want to play legit online on my sysnand?
Not necessarily. Having unburnt fuses has not been shown to be a bannable cause as I go online with my Switch with a lower than expected fuse count. There are ways of updating the firmware without burning fuses ranging from using homebrew applications to installing the system updates in CFW while AutoRCM is enabled to manually enabling RCM after the system update is installed with a jig.



So don't you think that switching from emunand (no wifi) to sysnand (wifi) would trigger some mismatch in e.g. titles, firmware and so on that would flag me immediately? Sorry for the stupid questions but I greatly appreciate your help.

Also, I bought a Samsung Evo Select sold and shipped by Amazon so I think I should be safe but I will run the test as suggested. Thank you!
I don't see any reason why it would since one is offline and the other is online; emuMMC and sysMMC do not interact with each other and operate independently.
 
  • Like
Reactions: Montblanc
Is there a guide for connecting switch ftpd to your phone? preferably in detail or with pictures, because im a complete noob in ftp connections. also, which app should i use?
 
hi everyone.

I just recently switched to Atmosphere from SXOS, but there is still some problem I cannot find a solution to.
This is my usual boot sequence.

I still use my SX Pro dongle to turn on my switch and keep pressing down the volume - button to get into SX menu, then I go into payload and there I launch hekate_ctcaer_5.6.0.bin (that I have renamed "payload.bin" for ease of use)

I have an emuMMC 12.0.3 (not hidden just like that into the SD card)

it launched into hekate. there I need to manually select payload and launch "fusee-primary" because if I just select atmosphere from the "launch" option, i get a weird error before it boot into atmosphere (FATAL ERROR [NXBOOT] Failed to run TSEC firmware -6 d0d0d0d0 d0d0d0d0d0f)

this is my hekate_ipl.ini

Code:
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0
{------ Atmosphere ------}
{Pick this option to launch CFW.}
[Atmosphere]
payload=atmosphere/fusee-primary.bin
{}
{------ Stock ------}
{NOTE: This option does not launch CFW.}
[Stock]
fss0=atmosphere/fusee-secondary.bin
stock=1
{}

1- Which patches should I use ??? the Fusee ones or the Hekate ones ???

2- and finally when I am in atmosphere, everything works perfectly expect from edizon, every time I start a game the cheats are ON by default even after I modified the system_settings.ini ad placed it into the config folder !!!

my system_settings.ini

Code:
[eupld]
; Disable uploading error reports to Nintendo
; upload_enabled = u8!0x0
[usb]
; Enable USB 3.0 superspeed for homebrew
; 0 = USB 3.0 support is system default (usually disabled), 1 = USB 3.0 support is enabled.
; usb30_force_enabled = u8!0x0
[ro]
; Control whether RO should ease its validation of NROs.
; (note: this is normally not necessary, and ips patches can be used.)
; ease_nro_restriction = u8!0x1
; Atmosphere custom settings
[atmosphere]
; Reboot from fatal automatically after some number of milliseconds.
; If field is not present or 0, fatal will wait indefinitely for user input.
; fatal_auto_reboot_interval = u64!0x0
; Make the power menu's "reboot" button reboot to payload.
; Set to "normal" for normal reboot, "rcm" for rcm reboot.
; power_menu_reboot_function = str!payload
; Controls whether dmnt cheats should be toggled on or off by
; default. 1 = toggled on by default, 0 = toggled off by default.
; dmnt_cheats_enabled_by_default = u8!0x0
; Controls whether dmnt should always save cheat toggle state
; for restoration on new game launch. 1 = always save toggles,
; 0 = only save toggles if toggle file exists.
; dmnt_always_save_cheat_toggles = u8!0x0
; Enable writing to BIS partitions for HBL.
; This is probably undesirable for normal usage.
; enable_hbl_bis_write = u8!0x0
; Enable reading the CAL0 partition for HBL.
; This is probably undesirable for normal usage.
; enable_hbl_cal_read = u8!0x0
; Controls whether fs.mitm should redirect save files
; to directories on the sd card.
; 0 = Do not redirect, 1 = Redirect.
; NOTE: EXPERIMENTAL
; If you do not know what you are doing, do not touch this yet.
; fsmitm_redirect_saves_to_sd = u8!0x0
; Controls whether am sees system settings "DebugModeFlag" as
; enabled or disabled.
; 0 = Disabled (not debug mode), 1 = Enabled (debug mode)
; enable_am_debug_mode = u8!0x0
; Controls whether dns.mitm is enabled
; 0 = Disabled, 1 = Enabled
; enable_dns_mitm = u8!0x1
; Controls whether dns.mitm uses the default redirections in addition to
; whatever is specified in the user's hosts file.
; 0 = Disabled (use hosts file contents), 1 = Enabled (use defaults and hosts file contents)
; add_defaults_to_dns_hosts = u8!0x1
; Controls whether dns.mitm logs to the sd card for debugging
; 0 = Disabled, 1 = Enabled
; enable_dns_mitm_debug_log = u8!0x0
; Controls whether htc is enabled
; 0 = Disabled, 1 = Enabled
; enable_htc = u8!0x0
[hbloader]
; Controls the size of the homebrew heap when running as applet.
; If set to zero, all available applet memory is used as heap.
; The default is zero.
; applet_heap_size = u64!0x0
; Controls the amount of memory to reserve when running as applet
; for usage by other applets. This setting has no effect if
; applet_heap_size is non-zero. The default is 0x8600000.
; applet_heap_reservation_size = u64!0x8600000

thank a lot in advance for all your help !
 
1- Which patches should I use ??? the Fusee ones or the Hekate ones ???


2- and finally when I am in atmosphere, everything works perfectly expect from edizon, every time I start a game the cheats are ON by default even after I modified the system_settings.ini ad placed it into the config folder !!!


1. If you use fusee setup fusee patches, hekate/fss0 use hekate patches.

2.change from above to this.
; 0 = Disabled, 1 = Enabled
; enable_dns_mitm = u8!0x1


; 0 = Disabled, 1 = Enabled
enable_dns_mitm = u8!0x0

so it disable enable all cheat by default.
 
Last edited by Hayato213,
  • Like
Reactions: Youffie
1. If you use fusee setup fusee patches, hekate/fss0 use hekate patches.

2.change from above to this.
; 0 = Disabled, 1 = Enabled
; enable_dns_mitm = u8!0x1


; 0 = Disabled, 1 = Enabled
enable_dns_mitm = u8!0x0

so it disable enable all cheat by default.

Do you know why when I´m in hekate, I need to manually select payload and launch "fusee-primary" because if I just select atmosphere from the "launch" option, I get a weird error before it boot into atmosphere (FATAL ERROR [NXBOOT] Failed to run TSEC firmware -6 d0d0d0d0 d0d0d0d0d0f)
 
Do you know why when I´m in hekate, I need to manually select payload and launch "fusee-primary" because if I just select atmosphere from the "launch" option, I get a weird error before it boot into atmosphere (FATAL ERROR [NXBOOT] Failed to run TSEC firmware -6 d0d0d0d0 d0d0d0d0d0f)

Probably has to do with SX Pro, what happen if you inject the hekate payload from a computer without going through SX OS bootloader menu?
 
  • Like
Reactions: Youffie
Probably has to do with SX Pro, what happen if you inject the hekate payload from a computer without going through SX OS bootloader menu?

Let me try and I´ll post my result

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

Probably has to do with SX Pro, what happen if you inject the hekate payload from a computer without going through SX OS bootloader menu?

yeah it works without error this time. so it's because of the SX Pro dongle... bummer, I liked that dongle.

but the cheat problem still persist, my game starts with all cheats on even after changing
; 0 = Disabled, 1 = Enabled
enable_dns_mitm = u8!0x0

Code:
[eupld]
; Disable uploading error reports to Nintendo
; upload_enabled = u8!0x0
[usb]
; Enable USB 3.0 superspeed for homebrew
; 0 = USB 3.0 support is system default (usually disabled), 1 = USB 3.0 support is enabled.
; usb30_force_enabled = u8!0x0
[ro]
; Control whether RO should ease its validation of NROs.
; (note: this is normally not necessary, and ips patches can be used.)
; ease_nro_restriction = u8!0x1
; Atmosphere custom settings
[atmosphere]
; Reboot from fatal automatically after some number of milliseconds.
; If field is not present or 0, fatal will wait indefinitely for user input.
; fatal_auto_reboot_interval = u64!0x0
; Make the power menu's "reboot" button reboot to payload.
; Set to "normal" for normal reboot, "rcm" for rcm reboot.
; power_menu_reboot_function = str!payload
; Controls whether dmnt cheats should be toggled on or off by
; default. 1 = toggled on by default, 0 = toggled off by default.
; dmnt_cheats_enabled_by_default = u8!0x0
; Controls whether dmnt should always save cheat toggle state
; for restoration on new game launch. 1 = always save toggles,
; 0 = only save toggles if toggle file exists.
; dmnt_always_save_cheat_toggles = u8!0x0
; Enable writing to BIS partitions for HBL.
; This is probably undesirable for normal usage.
; enable_hbl_bis_write = u8!0x0
; Enable reading the CAL0 partition for HBL.
; This is probably undesirable for normal usage.
; enable_hbl_cal_read = u8!0x0
; Controls whether fs.mitm should redirect save files
; to directories on the sd card.
; 0 = Do not redirect, 1 = Redirect.
; NOTE: EXPERIMENTAL
; If you do not know what you are doing, do not touch this yet.
; fsmitm_redirect_saves_to_sd = u8!0x0
; Controls whether am sees system settings "DebugModeFlag" as
; enabled or disabled.
; 0 = Disabled (not debug mode), 1 = Enabled (debug mode)
; enable_am_debug_mode = u8!0x0
; Controls whether dns.mitm is enabled
; 0 = Disabled, 1 = Enabled
; enable_dns_mitm = u8!0x0
; Controls whether dns.mitm uses the default redirections in addition to
; whatever is specified in the user's hosts file.
; 0 = Disabled (use hosts file contents), 1 = Enabled (use defaults and hosts file contents)
; add_defaults_to_dns_hosts = u8!0x1
; Controls whether dns.mitm logs to the sd card for debugging
; 0 = Disabled, 1 = Enabled
; enable_dns_mitm_debug_log = u8!0x0
; Controls whether htc is enabled
; 0 = Disabled, 1 = Enabled
; enable_htc = u8!0x0
[hbloader]
; Controls the size of the homebrew heap when running as applet.
; If set to zero, all available applet memory is used as heap.
; The default is zero.
; applet_heap_size = u64!0x0
; Controls the amount of memory to reserve when running as applet
; for usage by other applets. This setting has no effect if
; applet_heap_size is non-zero. The default is 0x8600000.
; applet_heap_reservation_size = u64!0x8600000
 
Let me try and I´ll post my result

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



yeah it works without error this time. so it's because of the SX Pro dongle... bummer, I liked that dongle.

but the cheat problem still persist, my game starts with all cheats on even after changing
; 0 = Disabled, 1 = Enabled
enable_dns_mitm = u8!0x0

Code:
[eupld]
; Disable uploading error reports to Nintendo
; upload_enabled = u8!0x0
[usb]
; Enable USB 3.0 superspeed for homebrew
; 0 = USB 3.0 support is system default (usually disabled), 1 = USB 3.0 support is enabled.
; usb30_force_enabled = u8!0x0
[ro]
; Control whether RO should ease its validation of NROs.
; (note: this is normally not necessary, and ips patches can be used.)
; ease_nro_restriction = u8!0x1
; Atmosphere custom settings
[atmosphere]
; Reboot from fatal automatically after some number of milliseconds.
; If field is not present or 0, fatal will wait indefinitely for user input.
; fatal_auto_reboot_interval = u64!0x0
; Make the power menu's "reboot" button reboot to payload.
; Set to "normal" for normal reboot, "rcm" for rcm reboot.
; power_menu_reboot_function = str!payload
; Controls whether dmnt cheats should be toggled on or off by
; default. 1 = toggled on by default, 0 = toggled off by default.
; dmnt_cheats_enabled_by_default = u8!0x0
; Controls whether dmnt should always save cheat toggle state
; for restoration on new game launch. 1 = always save toggles,
; 0 = only save toggles if toggle file exists.
; dmnt_always_save_cheat_toggles = u8!0x0
; Enable writing to BIS partitions for HBL.
; This is probably undesirable for normal usage.
; enable_hbl_bis_write = u8!0x0
; Enable reading the CAL0 partition for HBL.
; This is probably undesirable for normal usage.
; enable_hbl_cal_read = u8!0x0
; Controls whether fs.mitm should redirect save files
; to directories on the sd card.
; 0 = Do not redirect, 1 = Redirect.
; NOTE: EXPERIMENTAL
; If you do not know what you are doing, do not touch this yet.
; fsmitm_redirect_saves_to_sd = u8!0x0
; Controls whether am sees system settings "DebugModeFlag" as
; enabled or disabled.
; 0 = Disabled (not debug mode), 1 = Enabled (debug mode)
; enable_am_debug_mode = u8!0x0
; Controls whether dns.mitm is enabled
; 0 = Disabled, 1 = Enabled
; enable_dns_mitm = u8!0x0
; Controls whether dns.mitm uses the default redirections in addition to
; whatever is specified in the user's hosts file.
; 0 = Disabled (use hosts file contents), 1 = Enabled (use defaults and hosts file contents)
; add_defaults_to_dns_hosts = u8!0x1
; Controls whether dns.mitm logs to the sd card for debugging
; 0 = Disabled, 1 = Enabled
; enable_dns_mitm_debug_log = u8!0x0
; Controls whether htc is enabled
; 0 = Disabled, 1 = Enabled
; enable_htc = u8!0x0
[hbloader]
; Controls the size of the homebrew heap when running as applet.
; If set to zero, all available applet memory is used as heap.
; The default is zero.
; applet_heap_size = u64!0x0
; Controls the amount of memory to reserve when running as applet
; for usage by other applets. This setting has no effect if
; applet_heap_size is non-zero. The default is 0x8600000.
; applet_heap_reservation_size = u64!0x8600000

My fault I meant

this instead

dmnt_cheats_enabled_by_default = u8!0x0
 
did you remove the semicolon, and is the system_setting.ini in the config folder instead of config template?
I had forgot the semicolon on this one, sorry. Thanks you so much.

Also I just updated to Atmosphère 0.20.0 and now I can´t see the overlay when i press the L+DOWN+R3 combo !!!
O.o is it because of the new atmosphere version ?

sorry for so many questions
 
I had forgot the semicolon on this one, sorry. Thanks you so much.

Also I just updated to Atmosphère 0.20.0 and now I can´t see the overlay when i press the L+DOWN+R3 combo !!!
O.o is it because of the new atmosphere version ?

sorry for so many questions

Try 0.19.5 I guess, I don't use overlay so can't help on that.
 
Lets say, i want to upgrade my SD Card. Moving all Files / Folders to the new works without a problem.

But i want to install a lot of new games at once, is it possible to install these directly onto the card, while bypassing the switch completly? I saw that there is a way for the old 3DS, so i could avoid slow I/O, network transfers and so on and do all the work on the PC. Maybe by extracting nsps with some sort of tool?
 
If I buy a second hand white boxed Nintendo Switch and that person upgraded the firmware, is it still possible to hack the Nintendo Switch? I want to buy a second hand Switch and I'm not sure it is hackable. The device is from 2017.
 

Site & Scene News

Popular threads in this forum