Hacking SWITCH NOOB PARADISE - Ask questions here

[kyomagi]

Hey all, i have been out of the switch modding scene for a bit and finally decided to mod my oled. its fully updated and before i did the mod, i put it in airplane mode and deleted all my internet connections.

I set up the SD card as i remembered back when i modded my old V1 but with this OLED, i want to still try and play some online games IF possible.

Basically what are the newest methods of keeping your switch un-banned other than never taking it online?

I remember EMUnand and backing up my original. Never going CFW on sysnand and never going online on EMUnand/CFW. Is there anything else that i can do? Mainly looking to just play tetris 99 online and splatoon 3 along with Mario Strikers with purchased carts.

 

[bupeapoop]

After numerous failed attempts at successfully injecting the Hekate payload, I just want to double check I'm doing this right.

In this pic HERE, you'll see the root of my SD card. The contents contained are after doing the rentry step below where it says

• Extract these files into the root of your SD card:
  • hekate_ctcaer_x.x.x_Nyx_x.x.x.zip
  • atmosphere-x.x.x-master.zip
  • SigPatches.zip

The next step in the guide is as follows

• Place the file named fusee.bin in your /bootloader/payloads/ folder.

As you can see from my screenshot HERE, there is no /bootloader/payloads/ folder within the root of the SD Card for me to place fusee.bin into?

Can someone please help me out here? This seems to be a hurdling block on the 'How to set up emuNAND with Atmosphere on Erista (Unpatched)' part of the rentry guide.

Thank you.

 

[binkinator]

After numerous failed attempts at successfully injecting the Hekate payload, I just want to double check I'm doing this right.

In this pic HERE, you'll see the root of my SD card. The contents contained are after doing the rentry step below where it says


The next step in the guide is as follows


As you can see from my screenshot HERE, there is no /bootloader/payloads/ folder within the root of the SD Card.

Can someone please help me out here? This seems to be a hurdling block on the 'How to set up emuNAND with Atmosphere on Erista (Unpatched)' part of the rentry guide.

Thank you.

edit: you might have to go into those directories and pull the real directories up one level. I bet they are inside the folders you’re showing.

You need to unzip the files you show in the picture and put the contents of the result in the root of your SD card. The Hekate.x.x.x.zip file will expand to be your /bootloader directory.

 

[binkinator]

Hey all, i have been out of the switch modding scene for a bit and finally decided to mod my oled. its fully updated and before i did the mod, i put it in airplane mode and deleted all my internet connections.

I set up the SD card as i remembered back when i modded my old V1 but with this OLED, i want to still try and play some online games IF possible.

Basically what are the newest methods of keeping your switch un-banned other than never taking it online?

I remember EMUnand and backing up my original. Never going CFW on sysnand and never going online on EMUnand/CFW. Is there anything else that i can do? Mainly looking to just play tetris 99 online and splatoon 3 along with Mario Strikers with purchased carts.

is your OLED chipped already? An Aula behaves similarly to a Mariko And requires a modchip. Just want to clarify what you mean when you say you did the mod.

 

[kyomagi]

is your OLED chipped already? An Aula behaves similarly to a Mariko And requires a modchip. Just want to clarify what you mean when you say you did the mod.

Sorry i chipped my oled

 

[binkinator]

Sorry i chipped my oled

Most things are still the same as you remember them.

The biggest new thing is Exosphere. It does Prodinfo blanking and 90DNS-ish telemetry blocking of Ninty’s servers.

Here’s a quick blurb on setting it up:

Create the file exosphere.ini in the root of your SD card and paste this inside
(this step is needed in order to blank your prodinfo so that you can avoid having your switch be banned):

1 2 3 4 5 6 7 8 9 10 11

[exosphere] debugmode=1 debugmode_user=0 disable_user_exception_handlers=0 enable_user_pmu_access=0 blank_prodinfo_sysmmc=0 blank_prodinfo_emummc=1 allow_writing_to_cal_sysmmc=0 log_port=0 log_baud_rate=115200 log_inverted=0

Afterwards create a file named default.txt in /atmosphere/hosts/ (the hosts folder won't exist, so make sure to create it)
and paste this in your default.txt file (this step is prevents you from connecting to Nintendo's servers):

1 2 3 4 5 6

# Block Nintendo Servers 127.0.0.1 *nintendo.* 127.0.0.1 *nintendo-europe.com 127.0.0.1 *nintendoswitch.* 95.216.149.205 *conntest.nintendowifi.net 95.216.149.205 *ctest.cdn.nintendo.net

Source: https://rentry.org/MarikoEmuNAND which is a page from https://rentry.co/SwitchHackingIsEasy

 

[kyomagi]

Most things are still the same as you remember them.

The biggest new thing is Exosphere. It does Prodinfo blanking and 90DNS-ish telemetry blocking of Ninty’s servers.

Here’s a quick blurb on setting it up:

Create the file exosphere.ini in the root of your SD card and paste this inside
(this step is needed in order to blank your prodinfo so that you can avoid having your switch be banned):

1 2 3 4 5 6 7 8 9 10 11

[exosphere] debugmode=1 debugmode_user=0 disable_user_exception_handlers=0 enable_user_pmu_access=0 blank_prodinfo_sysmmc=0 blank_prodinfo_emummc=1 allow_writing_to_cal_sysmmc=0 log_port=0 log_baud_rate=115200 log_inverted=0

Afterwards create a file named default.txt in /atmosphere/hosts/ (the hosts folder won't exist, so make sure to create it)
and paste this in your default.txt file (this step is prevents you from connecting to Nintendo's servers):

1 2 3 4 5 6

# Block Nintendo Servers 127.0.0.1 *nintendo.* 127.0.0.1 *nintendo-europe.com 127.0.0.1 *nintendoswitch.* 95.216.149.205 *conntest.nintendowifi.net 95.216.149.205 *ctest.cdn.nintendo.net

Source: https://rentry.org/MarikoEmuNAND which is a page from https://rentry.co/SwitchHackingIsEasy

Thank you! so does this only apply to the emunand with CFW or even when im on sysnand no cfw?

 

[binkinator]

Thank you! so does this only apply to the emunand with CFW or even when im on sysnand no cfw?

ONLY applies to CFW.

No CFW? Then no blanking and no blocking.

Nand is irrelevant In this case.

 

[bupeapoop]

edit: you might have to go into those directories and pull the real directories up one level. I bet they are inside the folders you’re showing.

You sir are an absolute legend!

The guide wasn't 100% clear on that. It turns out, like you said, I had to copy the contents of each directory to the root of the directory and delete the folders in the screenshot in my post above. The contents of the SigPatches.zip had to me moved to the appropriate folders. So anything held in the Sigpatches bootloader file, had to be moved into the Hekate bootloader folder etc.

I've now progressed to the next phase of the setup guide! Onwards and upwards! Thanks again bro!

 

[k28]

so i want to install a trinet m0 into an unpatched unit and im not sure if a got it right:

1: copy sdsetup, latest sigpatches etc on sd card and create emuMMC
2: flash chip with latest file
3: solder trinket m0 with all straps.

now how do i boot ofw and emunand? is it now possible to just press power button and the switch boots to ofw and holding volUP button + power button the switch boots to emummc?

 

[umsta]

Hey guys so sorry i know its been asked a million times but the more i read the more links/tabs i open and the more confused i become. So i need help jumping from SXOS to Atmosphere my details as best i can remember are an original Switch that was on 6. something now running SXOS 3.0.5, current sys 10.2.0 when i power on i use a dongle and i think its an emunand. So i just want to run Atmosphere i dont care if its emunand i dont care about SXOS or any games on it at the present. Also i kept reading about choi du jour causing issues and i think it was used on my system. please can you steer me right thanks fellers

 

[binkinator]

Hey guys so sorry i know its been asked a million times but the more i read the more links/tabs i open and the more confused i become. So i need help jumping from SXOS to Atmosphere my details as best i can remember are an original Switch that was on 6. something now running SXOS 3.0.5, current sys 10.2.0 when i power on i use a dongle and i think its an emunand. So i just want to run Atmosphere i dont care if its emunand i dont care about SXOS or any games on it at the present. Also i kept reading about choi du jour causing issues and i think it was used on my system. please can you steer me right thanks fellers

This will get you there…end to end.

https://rentry.org/mys8q

Choi would only impact the nand you used it on (which should be emunand.)

it’s recommended practice to upgrade your sysnand FW by going into OFW and upgrading using Ninty official servers.

For emunand, use Daybreak moving forward.

edit: if you want to just start from scratch pick your setup from here and go. https://rentry.org/CFWGuides

 

[binkinator]

so i want to install a trinet m0 into an unpatched unit and im not sure if a got it right:

1: copy sdsetup, latest sigpatches etc on sd card and create emuMMC
2: flash chip with latest file
3: solder trinket m0 with all straps.

now how do i boot ofw and emunand? is it now possible to just press power button and the switch boots to ofw and holding volUP button + power button the switch boots to emummc?

Correct. that’s is the default setup Key presses. I actually reversed mine so it always boots into CFW and I have to press the key combo to bypass and Boot OFW, this means I simply power up and go straight into Atmosphere. It’s as close to cold boot as were going to get.

 

[Pantonio3]

Anyone able to run Lakka successfully off of the same SD card when on firmware 13.2.1, CFW Atmosphere 1.2.6, and Hekate 5.7.0?​

Hi everyone - thank you to the folks that replied to my last post recommending that I update my firmware. I did end up updating my firmware by downloading firmware 13.2.1 using AIO Installer, and then using Daybreak to install the new firmware. So far so good. I was having issues running retroarch and pFBA on the newest firmware and custom firmware, but I downloaded the newest version or retroarch, and found a newer/newish version of pFBA online, ran those both, and was able to get them both to work. I can also run newer games using Tinfoil, but I have to run the applet version of Tinfoil, because the Tinfoil installer will not work. So that is the update of how well things are working right now, which is relatively well.

There is one missing piece of the puzzle I want to get to work though.

Is anyone out there currently successfully running Lakka off of the same MicroSD card where you have the newest version of Atmosphere and Hekate? That is, will the newest version of Lakka, version 3.6.7, even run on the newest version of Hekate, version 5.7.0? If you can get Lakka to run of of the same SD card that you the newest version of Atmosphere and Hekate on, please let me know if you think you know what I might be doing wrong, or if there is some additional step I might need to take to get things to work that I might have missed. I downloaded Lakka version 3.6.7, overwrote over my old Lakka directory, and overwrote the Lakka files in the bootloader. I can select Lakka to load in Hekate, but when I press the Lakka button for it to load, it gets stuck on teh Lakka loading screen and freezes on the Lakka loading screen. Should I have just deleted the previous Lakka folder before copying the new Lakka folder over instead of overwriting? I think I have already tried this to no avail, but any tips and help you might have would be greatly appreciated.

Thank you!!!

 

[DJPlace]

does anyone know how to turn off the switch when it auto start's when i plug the charger in? it does that every time and i want that to stop for good.

 

[binkinator]

does anyone know how to turn off the switch when it auto start's when i plug the charger in? it does that every time and i want that to stop for good.

According to this it’s a feature, similar to cell phones, where these devices briefly turn on to give indication that they are charging. This is so you won’t be disappointed to come back and find out it wasn’t plugged in properly many hours later.

 

[binkinator]

Anyone able to run Lakka successfully off of the same SD card when on firmware 13.2.1, CFW Atmosphere 1.2.6, and Hekate 5.7.0?​

Hi everyone - thank you to the folks that replied to my last post recommending that I update my firmware. I did end up updating my firmware by downloading firmware 13.2.1 using AIO Installer, and then using Daybreak to install the new firmware. So far so good. I was having issues running retroarch and pFBA on the newest firmware and custom firmware, but I downloaded the newest version or retroarch, and found a newer/newish version of pFBA online, ran those both, and was able to get them both to work. I can also run newer games using Tinfoil, but I have to run the applet version of Tinfoil, because the Tinfoil installer will not work. So that is the update of how well things are working right now, which is relatively well.

There is one missing piece of the puzzle I want to get to work though.

Is anyone out there currently successfully running Lakka off of the same MicroSD card where you have the newest version of Atmosphere and Hekate? That is, will the newest version of Lakka, version 3.6.7, even run on the newest version of Hekate, version 5.7.0? If you can get Lakka to run of of the same SD card that you the newest version of Atmosphere and Hekate on, please let me know if you think you know what I might be doing wrong, or if there is some additional step I might need to take to get things to work that I might have missed. I downloaded Lakka version 3.6.7, overwrote over my old Lakka directory, and overwrote the Lakka files in the bootloader. I can select Lakka to load in Hekate, but when I press the Lakka button for it to load, it gets stuck on teh Lakka loading screen and freezes on the Lakka loading screen. Should I have just deleted the previous Lakka folder before copying the new Lakka folder over instead of overwriting? I think I have already tried this to no avail, but any tips and help you might have would be greatly appreciated.

Thank you!!!

I haven’t upgraded mine to all latest yet but found this:


Anyone else got any ideas on this?

 

[HelloShitty]

So, I just bought an original SXOS chip and if customs don't f... me up, I'll get the chip in a week or 2 maybe. No idea. It's crossing the Atlantic from USA to southwestern Europe. But I need to purchase the cables. I will try to install this chip in an OLED console. So, what are the best options (links, if possible) to install an original SXOS into an OLED console?

 

[husky3g]

Have an older Switch that I RCM and flashed a payload. Installed a few games. What sort of actions can get the console banned from Switch Online? How can I avoid getting my console banned? I typically leave the internet disconnected on it unless I'm streaming my PC games with Moonlight.

Also, I've been updating my games direct from Nintendo. (nsz installs) rather than download the patches and installing manually and they still seem to work.

I'm not 100% informed as to how to keep my switch from getting banned. Any videos on the subject?

 

[binkinator]

Have an older Switch that I RCM and flashed a payload. Installed a few games. What sort of actions can get the console banned from Switch Online? How can I avoid getting my console banned? I typically leave the internet disconnected on it unless I'm streaming my PC games with Moonlight.

Also, I've been updating my games direct from Nintendo. (nsz installs) rather than download the patches and installing manually and they still seem to work.

I'm not 100% informed as to how to keep my switch from getting banned. Any videos on the subject?

This is the Switch Ban Hub https://gbatemp.net/threads/nintendo-switch-banning-hub-warning.508710/ where folks talk about what got them banned. Nothing is 100% and things that worked in the past are not guaranteed to work tomorrow.

You should be running exosphere to minimize risk. Check out the 3rd bullet onward of the 3rd step here: https://rentry.org/EristaEmuNAND

• Create the file exosphere.ini in the root of your SD card and paste this inside (this step is needed in order to blank your prodinfo so that you can avoid getting your switch banned):

[exosphere]
debugmode=1
debugmode_user=0
disable_user_exception_handlers=0
enable_user_pmu_access=0
blank_prodinfo_sysmmc=0
blank_prodinfo_emummc=1
allow_writing_to_cal_sysmmc=0
log_port=0
log_baud_rate=115200
log_inverted=0

• Afterwards create a file named default.txt in /atmosphere/hosts/ (the hosts folder won't exist, so make sure to create it) and paste this in your default.txt file (this step is prevents you from connecting to Nintendo's servers):

# Block Nintendo Servers
127.0.0.1 *nintendo.*
127.0.0.1 *nintendo-europe.com
127.0.0.1 *nintendoswitch.*
95.216.149.205 *conntest.nintendowifi.net
95.216.149.205 *ctest.cdn.nintendo.net


As for the updates, are you saying you go online and update your questionable .nsp installs using Ninty’s servers?

If so then you’re likely a dead man walking already and none of these preventative measures probably matter anyway, but let’s hear what you have to say…