Hacking SWITCH NOOB PARADISE - Ask questions here

[Adran_Marit]

Hi, I'm thinking of hacking my switch. What's the worst thing that can happen, ban?

Brick then Ban

If you want to hack your switch (if it compatiable but before anything else) the first thing you want to do is follow this guide HERE

After that, follow the CFW guide of your choice. SDFiles(Atmosphere)ReiNX,RajNX or SXOS

 

[Buszu92]

Hello guys! How can i update .xci files without ban risk? is it possible?

 

[Adran_Marit]

Hello guys! How can i update .xci files without ban risk? is it possible?

you can update a .xci using a .nsp as the .nsp installs the update to the console for the game.. if that makes sense

 

[pepoy]

ive been reading loads of bad stuff regarding TX. should i use another CFW instead? also can do homebrew apps such as tinfoil, checkpoint and others work the same on SXOS and REINX?

 

[OrGoN3]

So what is thought to be the safest way to play backups? I know to make a nand backup of my system prior to doing anything "dirty" to it. My question mainly arises when I want to restore that backup and go online with my switch. if i don't burn fuses during updates, I can restore that nand backup, right? And then once restored, my system will not have any pending logs to report back to Nintendo, or issues loading OFW since the burnt fuses match, right? Or wrong? I can then update my system if I wanted to through Ninty servers as well? I plan on using 90DNS and ReiNX (unless I have to use Atmosphere + hekate for creport? Do I need hekate + ReiNX for this feature as well or can just ReiNX accomplish this? I figure loading hekate the first time and creating my nand backup through there, as well as dumping my keys. THen go through the ReiNX guide. I know ReiNX guide has me dump NAND, but that's only after loading up ReiNX. Would that be as clean of a backup as doing a backup with hekate the first time I enter RCM?

I know to not go online with the switch in cfw mode, unless I use 90DNS. Is there any other way to block Nintendo Telemetry data being sent? Is there a better way?

My last question is a bit more complex, but simple: how are people loading cfw, or at least homebrew, on a system, purchasing Nintendo Online sub, increasing their NES titles, and not getting banned?

 

[Alexissimo]

Hello i have a 256gb micro sdxc and my 2.3.0 switch prompt me with an update, i have to use guiformat?

 

[OrGoN3]

Hello i have a 256gb micro sdxc and my 2.3.0 switch prompt me with an update, i have to use guiformat?

Do you want to use FAT32 or ExFAT? if FAT32 then use guiformat to format your card. If ExFAT then there are tutorials on how to install the exfat component to your Switch. Once that's installed the Switch can format your card to exfat for you.

Be warned that exfat has been known to cause issues when used with certain homebrew. If you're using homebrew it's advised to use fat32.

 

[Alexissimo]

Do you want to use FAT32 or ExFAT? if FAT32 then use guiformat to format your card. If ExFAT then there are tutorials on how to install the exfat component to your Switch. Once that's installed the Switch can format your card to exfat for you.

Be warned that exfat has been known to cause issues when used with certain homebrew. If you're using homebrew it's advised to use fat32.

I dont need exfat, thanks

 

[Draxzelex]

ive been reading loads of bad stuff regarding TX. should i use another CFW instead? also can do homebrew apps such as tinfoil, checkpoint and others work the same on SXOS and REINX?

Homebrew applications work better on non-SX OS based CFW such as ReiNX and Atmosphere.

So what is thought to be the safest way to play backups? I know to make a nand backup of my system prior to doing anything "dirty" to it. My question mainly arises when I want to restore that backup and go online with my switch. if i don't burn fuses during updates, I can restore that nand backup, right? And then once restored, my system will not have any pending logs to report back to Nintendo, or issues loading OFW since the burnt fuses match, right? Or wrong? I can then update my system if I wanted to through Ninty servers as well? I plan on using 90DNS and ReiNX (unless I have to use Atmosphere + hekate for creport? Do I need hekate + ReiNX for this feature as well or can just ReiNX accomplish this? I figure loading hekate the first time and creating my nand backup through there, as well as dumping my keys. THen go through the ReiNX guide. I know ReiNX guide has me dump NAND, but that's only after loading up ReiNX. Would that be as clean of a backup as doing a backup with hekate the first time I enter RCM?

I know to not go online with the switch in cfw mode, unless I use 90DNS. Is there any other way to block Nintendo Telemetry data being sent? Is there a better way?

My last question is a bit more complex, but simple: how are people loading cfw, or at least homebrew, on a system, purchasing Nintendo Online sub, increasing their NES titles, and not getting banned?

Restoring a clean hack-free NAND backup made in Hekate is the safest way to use a hacked Switch online as long as you remain offline with all of your hacks. The issue here is one, you will need to constantly make new NAND backups every time you return offline because you cannot restore the same NAND backup twice (for obvious reasons) and two, any content saved into the NAND will be lost upon the restoration. This includes games, updates/DLC, and save data.

For blocking telemetry, the only other ways are manually blocking the Nintendo URLs yourself (see here for a list) or deleting Wi-Fi settings and enabling Airplane Mode (deleting Wi-Fi settings is more important as Airplane Mode can get disabled when switching between docked/handheld/sleep modes).

And as for your last question, its pure luck much like people getting banned in the first place.

 

[Jokiz]

I've suddenly run into issues where most of my games will freeze after awaking from sleep. It seems to occur during load screens. The weird thing is that music and loading animations run, but never seem to finish.
Now this happened after two "changes" to my switch.
Firstly, I updated to 6.0 via ChoiDujourNX, could that cause some issues?
Secondly (and probably the reason). I installed retroarch and some other homebrew (tho I had some on the switch before this) on my exfat SD card, so it might have been corrupted??

I run SX OS btw!
Anyone encounter something similar?

 

[Miles54321]

Heya guys, I'm thinking of using my Nintendo Switch 2.1.0 with ReinX, was wondering about a few things before I hack my switch

1) In order to get into RCM you have to do a specific method...I was wondering if there are any gbatemp users that sell 3D Printer Models that you can use on the right hand side of the Switch, that's seems like one of the most reliable methods and was wondering if there are any sellers

2) What is the Largest MicroSD card the Switch can use for CFW/Homebrew/Switch, Is it 128GB/256GB, just wondering before I buy one
P.S: Is Samsung the only make of MicroSD card you would recommend?

3) There is no recommended USB-C to A cables for the switch, can I just use any old ones? Or is there a recommend brand that anyone knows of?

Thanks Again!

 

[Draxzelex]

I've suddenly run into issues where most of my games will freeze after awaking from sleep. It seems to occur during load screens. The weird thing is that music and loading animations run, but never seem to finish.
Now this happened after two "changes" to my switch.
Firstly, I updated to 6.0 via ChoiDujourNX, could that cause some issues?
Secondly (and probably the reason). I installed retroarch and some other homebrew (tho I had some on the switch before this) on my exfat SD card, so it might have been corrupted??

I run SX OS btw!
Anyone encounter something similar?

Sleep mode is actually unstable on firmware 6.0 thanks to Nintendo so its not all that weird if you experience problems waking up from sleep. You can try updating your firmware to 6.0.1 since sleep mode is more stable on that than 6.0. I would recommend using ChoiDujourNX to update your firmware. And if the SD card is indeed corrupted, you can use your computer to check for that. Although a quick format wouldn't hurt even if it isn't corrupted.

Heya guys, I'm thinking of using my Nintendo Switch 2.1.0 with ReinX, was wondering about a few things before I hack my switch

1) In order to get into RCM you have to do a specific method...I was wondering if there are any gbatemp users that sell 3D Printer Models that you can use on the right hand side of the Switch, that's seems like one of the most reliable methods and was wondering if there are any sellers

2) What is the Largest MicroSD card the Switch can use for CFW/Homebrew/Switch, Is it 128GB/256GB, just wondering before I buy one

3) There is no recommended USB-C to A cables for the switch, can I just use any old ones? Or is there a recommend brand that anyone knows of?

Thanks

1. I don't know of anyone selling them on the site as well since they can be found on eBay and all sorts of other third-party websites. The only thing I can say is pay attention to any reviews, if they have them
2. The size limit is 2 TB which doesn't even exist so the largest SD card you can find is supported. Just make sure it is not fake which you can't really verify before purchasing it but usually if its too good to be true, it usually is
3. As long as the USB cable supports data transfer (some USB cables only provide charging capabilities), then you can use it. Not sure how to check for this however.

 

[OrGoN3]

Homebrew applications work better on non-SX OS based CFW such as ReiNX and Atmosphere.
Restoring a clean hack-free NAND backup made in Hekate is the safest way to use a hacked Switch online as long as you remain offline with all of your hacks. The issue here is one, you will need to constantly make new NAND backups every time you return offline because you cannot restore the same NAND backup twice (for obvious reasons) and two, any content saved into the NAND will be lost upon the restoration. This includes games, updates/DLC, and save data.

For blocking telemetry, the only other ways are manually blocking the Nintendo URLs yourself (see here for a list) or deleting Wi-Fi settings and enabling Airplane Mode (deleting Wi-Fi settings is more important as Airplane Mode can get disabled when switching between docked/handheld/sleep modes).

And as for your last question, its pure luck much like people getting banned in the first place.

Hey buddy. Thanks for your assistance. I understand I would need to create a NAND backup a new every time I went back online and then offline. As for the content being gone, yes, I would need to backup my saves, or go one step further and create a NAND backup of my offline installation that I can return to, as long as I'm not updating FW and burning fuses.

I assume most people just don't go back online with theirs, and they assume it'll be banned if they go online. Now, there are two different bans, right? A ban and a super ban? If my console gets banned, does that mean it cannot get firmware updates anymore? Although now that I think about it, I don't care that much since I just realized that darth site has the updates on there, which I should be able to use with ChoiDujourNX.

Ok, now, this is opinion I guess. if I'm going ReiNX route (over RajNX, lol, sorry) would you recommend first booting to hekate and then ReiNX? Does that get me any better/different protection than just ReiNX? My only other question might be answered over at the ReiNX channels. If I want to prevent fuse burns and I'm not using Hekate, and I install the new ones through ChoiDujourNX are there any special settings I need? Their tutorial to prevent fuse burning is simply to keep the jig in the system while updating through System Settings. Doesn't that defeat the point of keeping your Switch offline? But those are the only directions it gives when it comes to saving fuses.

 

[Draxzelex]

Ok, now, this is opinion I guess. if I'm going ReiNX route (over RajNX, lol, sorry) would you recommend first booting to hekate and then ReiNX? Does that get me any better/different protection than just ReiNX? My only other question might be answered over at the ReiNX channels. If I want to prevent fuse burns and I'm not using Hekate, and I install the new ones through ChoiDujourNX are there any special settings I need? Their tutorial to prevent fuse burning is simply to keep the jig in the system while updating through System Settings. Doesn't that defeat the point of keeping your Switch offline? But those are the only directions it gives when it comes to saving fuses.

If your intention is to backup the NAND as cleanly as possible, I would use Hekate first then use ReiNX for CFW purposes (although you can use Hekate to load Atmosphere).

In order to prevent fuses from burning, you must use a bootloader that does not burn fuses. The one inside the console primarily handles this. However by booting into RCM, we prevent the built-in bootloader from working and we must substitute our own. In order to substitute it, we send a payload that doubles as a bootloader. Bootloaders that can be sent as payloads and prevent fuses from being burnt include Hekate, ReiNX, and all versions of SX OS past V1.2. ChoiDujourNX also installs AutoRCM to prevent the normal bootloader from ever starting because without it, if you accidentally turn on the console, the normal bootloader will take over and burn fuses.

I believe the tutorial you are referring to does not involve ChoiDujourNX but a risky yet easier way of updating without burning fuses. That method involves rebooting the console into RCM before the normal bootloader can burn the fuses since the console reboots after installing a system firmware update. That guide is totally separate from updating using ChoiDujourNX which runs as a homebrew application from a CFW.

 

[OrGoN3]

If your intention is to backup the NAND as cleanly as possible, I would use Hekate first then use ReiNX for CFW purposes (although you can use Hekate to load Atmosphere).

In order to prevent fuses from burning, you must use a bootloader that does not burn fuses. The one inside the console primarily handles this. However by booting into RCM, we prevent the built-in bootloader from working and we must substitute our own. In order to substitute it, we send a payload that doubles as a bootloader. Bootloaders that can be sent as payloads and prevent fuses from being burnt include Hekate, ReiNX, and all versions of SX OS past V1.2. ChoiDujourNX also installs AutoRCM to prevent the normal bootloader from ever starting because without it, if you accidentally turn on the console, the normal bootloader will take over and burn fuses.

I believe the tutorial you are referring to does not involve ChoiDujourNX but a risky yet easier way of updating without burning fuses. That method involves rebooting the console into RCM before the normal bootloader can burn the fuses since the console reboots after installing a system firmware update. That guide is totally separate from updating using ChoiDujourNX which runs as a homebrew application from a CFW.

Yes, that's correct on the guide. So basically just stick with ChoiDujourNX.

What I meant when I asked about running hekate first, was if I needed to run hekate as the payload and then boot into ReiNX. I know ReiNX can be a payload as well, but it wasn't clear in the ReiNX guide if it needed any additional settings to prevent fuse burning.

Ah, ChoiDujourNX is homebrew I just run on the Switch. That's more simplistic than the original method. So there's nothing I need to do anymore to prevent fuse burning? Aside from enabling AutoRCM for obvious reasons. This is getting easier as the day goes on!

 

[Draxzelex]

Yes, that's correct on the guide. So basically just stick with ChoiDujourNX.

What I meant when I asked about running hekate first, was if I needed to run hekate as the payload and then boot into ReiNX. I know ReiNX can be a payload as well, but it wasn't clear in the ReiNX guide if it needed any additional settings to prevent fuse burning.

Ah, ChoiDujourNX is homebrew I just run on the Switch. That's more simplistic than the original method. So there's nothing I need to do anymore to prevent fuse burning? Aside from enabling AutoRCM for obvious reasons. This is getting easier as the day goes on!

You can either directly load into ReiNX or chainload into it using Hekate. That choice is left up to you. Since Hekate can chainload any payload/CFW, I'd argue using Hekate first is more useful since you'll have access to some of Hekate's other useful functions such as fixing the Archive flag on SD cards or the battery de-sync.

ChoiDujourNX will enable AutoRCM by default so you don't need to enable it yourself. Once AutoRCM is enabled, as explained previously, the console's built-in bootloader will fail to launch since RCM is initiated before the console turns on meaning we can now substitute our own bootloader. And I've listed all of the bootloaders/payloads that prevent fuses from being burnt in the first place so there is really not much left for me to explain.

 

[OrGoN3]

You can either directly load into ReiNX or chainload into it using Hekate. That choice is left up to you. Since Hekate can chainload any payload/CFW, I'd argue using Hekate first is more useful since you'll have access to some of Hekate's other useful functions such as fixing the Archive flag on SD cards or the battery de-sync.

ChoiDujourNX will enable AutoRCM by default so you don't need to enable it yourself. Once AutoRCM is enabled, as explained previously, the console's built-in bootloader will fail to launch since RCM is initiated before the console turns on meaning we can now substitute our own bootloader. And I've listed all of the bootloaders/payloads that prevent fuses from being burnt in the first place so there is really not much left for me to explain.

Nope, you've explained it quite thoroughly. Thanks for your assistance!

 

[koyuki38]

Hi.

I want to make a Back up of Nand/Switch/Whatever the name we gave it.

The back up needs to contain all NSP/games/official DLC or anything i installed, so that when I restore it, every installed thing should be working like it is right now (assuming i do not update/burn efuse).

What should I back up ?
- Boot 0, 1 ?
- Rawnand.bin ?
- EMMC SYS ?
- EMMC User ?
- all of this ?

Thanks for your help.

* The reason is that my current Xenoblade Save is incompatible with any DLC NSP i found on the web.
I did not get them from the E-shop, but i used to perform a game restoration from online services and fixed any corrupted file/dlc/thing. Don't ask my how, but it worked with installed nsp dlc. That's the only way i found to make the save load again.
I won't be able to do that again soon (because ban is a thing), so i need a way to restore thing in case of problem.

My next step is to try making NSP/NCA from my Switch/Nand content but for now I focus on the Back up

 

[Draxzelex]

Hi.

I want to make a Back up of Nand/Switch/Whatever the name we gave it.

The back up needs to contain all NSP/games/official DLC or anything i installed, so that when I restore it, every installed thing should be working like it is right now (assuming i do not update/burn efuse).

What should I back up ?
- Boot 0, 1 ?
- Rawnand.bin ?
- EMMC SYS ?
- EMMC User ?
- all of this ?

Thanks for your help.

* The reason is that my current Xenoblade Save is incompatible with any DLC NSP i found on the web.
I did not get them from the E-shop, but i used to perform a game restoration from online services and fixed any corrupted file/dlc/thing. Don't ask my how, but it worked with installed nsp dlc. That's the only way i found to make the save load again.
I won't be able to do that again soon (because ban is a thing), so i need a way to restore thing in case of problem.

My next step is to try making NSP/NCA from my Switch/Nand content but for now I focus on the Back up

The NAND is broken up into 4 parts: eMMC raw GPP, Boot0, Boot1, and some fourth unused one whose name eludes me. eMMC raw GPP is comprised of two portions: eMMC SYS and eMMC USER. So a complete NAND backup includes eMMC raw GPP and boot0/boot1.

 

[zboubinou]

Hi !
I was trying the new usb install of tinfoil.
I install the proper usb driver with zadig and also libusb and pyusb for python (as written on the usb install script). So far so good (my switch is waiting for header) but when i try to launch the script i have this error :

Traceback (most recent call last):
File "C:\Users\MyName\Downloads\tinfoil-267ef5b\tools\usb_install_pc.py", line 134, in <module>
dev = usb.core.find(idVendor=0x057E, idProduct=0x3000)
File "C:\Users\MyName\AppData\Local\Programs\Python\Python37-32\lib\site-packages\usb\core.py", line 1263, in find
raise NoBackendError('No backend available')
usb.core.NoBackendError: No backend available

anyone know what this is please ?

Also because it's not working my switch still showing "waiting for header". How can i get back to mainscreen ? thx