Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,099,221
  • Replies Replies 47,953
  • Likes Likes 66
Nope. Those are two completely separate things. nx-ovlloader is a host process for loading Switch overlays, while Tesla menu is and initial menu to be loaded with nx-ovlloader. sys-patch is a sys-module which comes with its overlay as well that you can access via Tesla menu.
Thank you!
Post automatically merged:

What is daybreaK
You can access it through your homebrew apps and find it in the homebrew channel. Once you have your firmware on your SD card, daybreak can install it for you.
 
  • Like
Reactions: Blythe93
My ofw is 16.0.03 and my CFW is 14.1.2 ams on my emunand.
Is this normal?? I thought my ofw was as lower till I checked before updating emunand
 
Is this normal?? I thought my ofw was as lower till I checked before updating emunand
I don't see a reason not to be normal? Accidental updates can happen from time to time, therefore seeing that your sysNAND is on higher firmware than your emuNAND is not uncommon.
 
I don't see a reason not to be normal? Accidental updates can happen from time to time, therefore seeing that your sysNAND is on higher firmware than your emuNAND is not uncommon.
Yeah maybe the kids done that.
Would that make my last nand back up harder to use because of the fuse count with higher OFW?
If I make a new Nand back up before updating my emunand is it doing it from sysnand ?
Post automatically merged:

I have broken cable to send payloads and unable to book up. I have a lot of cheap usb c cable but not work.

Is the a specific type I need to get usb c - usb
If anyone could recommend a good one do the job on Amazon?
 
So how do / should I update games? How do I get / install dlc? Or are they both not possible with hacked switches?

Thank you!
 
Would that make my last nand back up harder to use because of the fuse count with higher OFW?
Indeed. Also, you'll be missing logs that were sent after you made your backup, when your Switch connected to the Nintendo servers. While that backup is useful in case you brick your Switch and there's no other backup available, you're most likely to cause mismatch between the logs in your console and on Nintendo servers.
For NAND backup usefulness as far as avoiding ban goes, I'll quote the steps from this thread:
The correct process for trying to avoid a ban are as follows:
  1. Make a clean NAND backup before doing any other hacks/CFW/homebrew using Hekate including boot0/boot1 and raw eMMC GPP (which will become a rawnand.bin)
  2. Perform any and all hacking offline with the Wi-Fi settings deleted and Airplane Mode to prevent accidental connection to Nintendo Hotspots (think 3DS Spotpass)
  3. Restore the clean NAND backup as well as boot0/boot1 prior to going online
  4. Make another NAND backup as well as boot0/boot1 at this point since your NAND has made permanent changes while connected to Nintendo's servers that are not present in your original NAND backup
  5. Repeat steps 2-4
With that being said, I'd definitely recommend that you remove all saved WiFi connections on your console and make a NAND backup afterwards. Make sure that your console never goes online (or, more specifically, connect to the Nintendo servers) after that. However, if you're using your sysNAND for playing legit games online, then you probably don't need a NAND backup to be made every so often as your console will be connected to the Nintendo servers all the time. Having one clean backup in that case is probably enough in case your NAND goes bad or corrupt in not so near future. Again, restoring such NAND is risky due to the log mismatch so keep that in mind.

As for the fuse count, you can still restore the old backup, but your console probably won't be able to boot. I'm no expert but I believe that you'll be able to boot into Atmosphere CFW on your sysNAND regardless of fuse mismatch, after which you can update your console via Daybreak to whichever firmware you want. Again, remember the log mismatch whenever you go about restoring backups.

If I make a new Nand back up before updating my emunand is it doing it from sysnand ?
Sure. I've made my first backup by following this guide.

Is the a specific type I need to get usb c - usb
It is advisable to use an A-to-C cable (for Windows, if using TegraRCMGUI) and USB OTG adapter (for Android, if using Rekado).
 
  • Like
Reactions: BigOnYa
hey guys, I want to upgrade my sd card. What should I do? I have to convert it to fat32 & exfat in the first place through hekate I guess. Am I able to move all the files from the old Sd card to the newer ones?
 
hey guys, I want to upgrade my sd card. What should I do? I have to convert it to fat32 & exfat in the first place through hekate I guess. Am I able to move all the files from the old Sd card to the newer ones?
Here's the guide I followed. I suggest NxNandManager method.
 
So I have backed up my pokken T and splatoon cartriges. Is there any way to play these games online without the cartridge in my switch and not get a ban? emmu nand? sysnand? stock? Or should I just forget about online splatoon and pokken tournament?

Thank you!
 
As far as I know, the only way to play those is to purchase the digital versions and play them on your clean sysNAND.

Since I already bought the physical game, if I put it in and out of the three options (emunand atmo, sysnand atmo, and stock ) chose stock to boot (the only way you can boot without a jig), I should then be OK, right?

If that is what it takes I may just keep Splatoon (or Mario Kart, or Pokken in semi permanently)

If it makes a difference:

1)

I have exosphere and the default.txt file in /atmosphere/hosts/
# 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

on my modded emu and modded sys nand. I did not add it to my stock unmodded nand.

2) I updated my firmware in IO updated and told it to update it on everything (so it updated formware on stock I belive). If that is a problem, can I use my nand backup to restore stock firmware to a lower firmware or am I hosed?

Thank you!
 
Since I already bought the physical game, if I put it in and out of the three options (emunand atmo, sysnand atmo, and stock ) chose stock to boot (the only way you can boot without a jig), I should then be OK, right?
Using cartridges in all of the three options is alright, if that's what you're asking? I don't really understand the question. At worst, on CFW your cart won't work if game card reader is disabled in Atmosphere by default.

1)

I have exosphere and the default.txt file in /atmosphere/hosts/
# 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

on my modded emu and modded sys nand. I did not add it to my stock unmodded nand.
Looking good. You can not add those list to the stock, but you can set up 90DNS instead.

2) I updated my firmware in IO updated and told it to update it on everything (so it updated formware on stock I belive). If that is a problem, can I use my nand backup to restore stock firmware to a lower firmware or am I hosed?
If you're talking about all-in-one updater of sorts, I'm not familiar with how those work as I update my stuff manually. Restoring backups on stock is only safe if you haven't connected your Switch to the Internet afterwards (more precisely, to the Nintendo servers) as you may run into logs mismatch (i.e. your console logs won't match with the ones on Nintendo servers). Also, I'm not sure if you've burnt fuses after updating firmware on your sysNAND. That would limit how low you can downgrade your firmware before running into fuse mismatch.
 
Using cartridges in all of the three options is alright, if that's what you're asking? I don't really understand the question. At worst, on CFW your cart won't work if game card reader is disabled in Atmosphere by default.


Looking good. You can not add those list to the stock, but you can set up 90DNS instead.


If you're talking about all-in-one updater of sorts, I'm not familiar with how those work as I update my stuff manually. Restoring backups on stock is only safe if you haven't connected your Switch to the Internet afterwards (more precisely, to the Nintendo servers) as you may run into logs mismatch (i.e. your console logs won't match with the ones on Nintendo servers). Also, I'm not sure if you've burnt fuses after updating firmware on your sysNAND. That would limit how low you can downgrade your firmware before running into fuse mismatch.
So, if I put the cartridge in my switch, I can play splatoon online with nintendo servers in any of the 3 modes, even emunand? And nintendo won't care?

Well I guess in my case, since I have that blocking txt file, I could only access nintendo servers in stock. But to be clear, putting the cartridge in my switch on stock firmware, I can play online without any fear of Nintendo bans?

Also, if it makes a diff, I did get the update/dlc online and added them via DBI on my emunand.

Thank you Blythe93!!! ...again, lol.
 
So, if I put the cartridge in my switch, I can play splatoon online with nintendo servers in any of the 3 modes, even emunand? And nintendo won't care?

Well I guess in my case, since I have that blocking txt file, I could only access nintendo servers in stock. But to be clear, putting the cartridge in my switch on stock firmware, I can play online without any fear of Nintendo bans?

Also, if it makes a diff, I did get the update/dlc online and added them via DBI on my emunand.

Thank you Blythe93!!! ...again, lol.

If your nand isn't clean then no for Splatoon.
 
And last question on the host folder there is also a default.txt but i had read in the guide that if i plan to play offline on emunand i should change the default.txt to emummc.txt, so can i delete it and just let only the emummc.txt on the folder?

According to the official documentation, the guide is wrong. The documentation says default.txt is auto created and is recommended to keep it as is.

Hosts file selection​

Atmosphère will try to read hosts from the following file paths, in order, stopping once it successfully performs a file read:

  • (emummc only) /atmosphere/hosts/emummc_%04lx.txt, formatted with the emummc's id number (see emummc.ini).
  • (emummc only) /atmosphere/hosts/emummc.txt.
  • (sysmmc only) /atmosphere/hosts/sysmmc.txt.
  • /atmosphere/hosts/default.txt
If /atmosphere/hosts/default.txt does not exist, atmosphère will create it to contain the defaults.

Atmosphère defaults​

By default, atmosphère's default redirections are parsed in addition to the contents of the loaded hosts file.

This is equivalent to thinking of the loaded hosts file as having the atmosphère defaults prepended to it.

This setting is considered desirable, because it minimizes the telemetry risks if a user forgets to update a custom hosts file on a system update which changes the telemetry servers.
 

Site & Scene News

Popular threads in this forum