Hacking SWITCH NOOB PARADISE - Ask questions here

[Friko]

Hello amazing people,

I am using SX OS and my Switch is on 6.0. I do not use AutoCRM at all, never did and the console has been completely offline before I started using SX OS.
My question is whether I can go online and make the Switch connect to the Nintendo servers to update to 6.2, go back offline and continue using the newest version SX OS?
Will Nintendo be able to know my console has been hacked?

 

[OnnRyuu]

Morning! I get a Switch (second hand) that came with version 6.0.1 ReinX installed. The previous owner barely used it so sell me for a fair price, but he didn´t knew anything about NAND, backups and else.
What did I do to update it, get the safer and better CFW, block updates, change, if recommended, the ReinX CFW, and other hints?

Thanks!!

My advice to you would be to Factory Reset your switch. Go online, download a demo and play it to test if it is already banned. If everything is OK, backup your NAND and reinstall a CFW

 

[MUDD_BR]

My advice to you would be to Factory Reset your switch. Go online, download a demo and play it to test if it is already banned. If everything is OK, backup your NAND and reinstall a CFW

Thanks, I´ll do this. Can you please provide me with some good tutorial or guide to do all of this with safety?

 

[BATMAN-]

Hello everyone,

If I am going to upgrade to 6.2 using ChoiDujournx does my nand backup with 5.1.0 become worthless or can I still have it saved to my computer and eventually use it at some point?

Thanks in advance

 

[Huge_Heffner]

My advice to you would be to Factory Reset your switch. Go online, download a demo and play it to test if it is already banned. If everything is OK, backup your NAND and reinstall a CFW

Thanks for helping people out my friend! I’m in a slightly different situation but I think what you posted will help. I just want to better understand how the NAND and backups work and have a few questions that I can’t seem to find a concise answer to.

I “assumed” that NAND backups gave the user the ability to restore back to a non-modified state. But the more I read, I get the feeling that it’s more intended to give the user a way out, in the event of a soft-brick situation or as a way to revert to a lower firmware versioning . Is this true?

The reason I ask, is that I wanted to revert back to stock (on 6.2) and remove any trace of being “hacked”, however I get an error when trying to restore the NAND backup I made. I assumed that I was screwed. But after reading your post, I get the vibe that I can just do a system restore and be good to go?

I have zero interest in downgrading firmware versions or anything like that.

 

[Ranshiro]

Hello everyone,

If I am going to upgrade to 6.2 using ChoiDujournx does my nand backup with 5.1.0 become worthless or can I still have it saved to my computer and eventually use it at some point?

Thanks in advance

as long as you don't burn any fuses, you could always restore your 5.1.0 nand backup. that being said, you might want to make another backup once on 6.2 just in case you accidentally burn any fuses.

 

[OnnRyuu]

Thanks for helping people out my friend! I’m in a slightly different situation but I think what you posted will help. I just want to better understand how the NAND and backups work and have a few questions that I can’t seem to find a concise answer to.

I “assumed” that NAND backups gave the user the ability to restore back to a non-modified state. But the more I read, I get the feeling that it’s more intended to give the user a way out, in the event of a soft-brick situation or as a way to revert to a lower firmware versioning . Is this true?

The reason I ask, is that I wanted to revert back to stock (on 6.2) and remove any trace of being “hacked”, however I get an error when trying to restore the NAND backup I made. I assumed that I was screwed. But after reading your post, I get the vibe that I can just do a system restore and be good to go?

I have zero interest in downgrading firmware versions or anything like that.

If you have no interest on runing a CFW then yea, just do a factory reset. You will have a clean console and Nintendo has no way of knowing if it was modded.
If you try to go online and can't, its probably because you bought an already banned switch

 

[Huge_Heffner]

If you have no interest on runing a CFW then yea, just do a factory reset. You will have a clean console and Nintendo has no way of knowing if it was modded.
If you try to go online and can't, its probably because you bought an already banned switch

I do plan on running CFW, but wanted to mess with EmuNAND and wanted to start fresh. I appreciate you taking the time to respond! That’s not something that’s clarified in any of the modding tutorials I’ve read and seems like something worth knowing.

Edit: and it’s definitely not banned. I was able to use it online just fine prior to loading any CFW (and it’s been offline since then)

Cheers

 

[starbury86]

I'm on firmware 4.01 and would like to update my sysnand to 6.2 to play online. However I don't know if I should use autorcm. I know I would burn my fused without it but is it possible for Nintendo to detect that there are unburned fuses on 6.2. I don't want to get banned.

I only used backups on emunand and always offline.

 

[er3eroMKII]

Hello guys, i'll be a little dense here but i dont want to mess up my switch.
I just bought a Switch currently on version 4.1.0 and a SX PRO. I've read a bunch of tutorials already but I have a concern about exFAT FAT32. Therfore, I'll write a list of steps I think i should take and you guys could correct any mistakes, I would be glad.
1 - Get sd card to FAT32 and put the boot.dat and license.dat on the root of the sd.
2 - Create a paste with the name Switch and put henkate there.
3 - Enter de CFW and on the album select henkate.
4 - Do a NAND backup there.
5 - Copy all my sd to a safe place (pc and personal gdrive).
6 - Enter SX OS 2.4 and create a emuNAND.
7 - copy ChoiDujourNX to the paste switch.
8 - Use ChoiDujourNX as the tutorials suggest to upgrade to 6.2 but now select exFAT.
With this I should have a exFAT sd? with emunand in 6.2 and OFW in 4.1.0.
Or should I between topics 5 and 6 use ChoiDujourNX to enable exFAT on 4.1.0 then do 6,7,8.

In advance, thank you for your help.
EDIT: Reading a little about 2.4. Should I care about fuses? Can I just download 6,2 online from the nintendo servers then use 2.4 to play games? What exactly do I lose with the lost of fuses?

 

[Andaman]

I have a question before updating from 3.0 to 6.2.

I've been stuck on 3.0 with my Switch only gathering dust for ages and now I have pretty much had enough of waiting. I really want to get Mega Man 11 and get my BotW DLC so I'm considering updating with latest OFW. I don't care that much of the online play but it would be nice to access the store. I would still like to have the option to run homebrew sometime in the future.

As I've read the 6.2 is still Atmosphere compatible even with the new signatures. Is there really any big downside for me to update now?

 

[Draxzelex]

How to merge splited NSP?Before i used to install nsp via sd now via USB but my nsp are splitted and aluminumfoil wont recognize it. I want to reinstall my games but some of them are splited.

Any file merger script or program should work. Just Google it.

Hello amazing people,

I am using SX OS and my Switch is on 6.0. I do not use AutoCRM at all, never did and the console has been completely offline before I started using SX OS.
My question is whether I can go online and make the Switch connect to the Nintendo servers to update to 6.2, go back offline and continue using the newest version SX OS?
Will Nintendo be able to know my console has been hacked?

If you don't have a clean NAND backup before you started using SX OS, Nintendo may be able to tell you were using SX OS the second you bring your console online.

I'm on firmware 4.01 and would like to update my sysnand to 6.2 to play online. However I don't know if I should use autorcm. I know I would burn my fused without it but is it possible for Nintendo to detect that there are unburned fuses on 6.2. I don't want to get banned.

I only used backups on emunand and always offline.

As far as I know, Horizon (Switch's OS) doesn't check for fuses because that check is already conducted by the console's bootloader. But if you're feeling super paranoid, you can choose not to enable AutoRCM and let your fuses be burnt preventing you from downgrading to firmware 4.0.1 in case a future exploit comes out such as untethered coldboot.

Hello guys, i'll be a little dense here but i dont want to mess up my switch.
I just bought a Switch currently on version 4.1.0 and a SX PRO. I've read a bunch of tutorials already but I have a concern about exFAT FAT32. Therfore, I'll write a list of steps I think i should take and you guys could correct any mistakes, I would be glad.
1 - Get sd card to FAT32 and put the boot.dat and license.dat on the root of the sd.
2 - Create a paste with the name Switch and put henkate there.
3 - Enter de CFW and on the album select henkate.
4 - Do a NAND backup there.
5 - Copy all my sd to a safe place (pc and personal gdrive).
6 - Enter SX OS 2.4 and create a emuNAND.
7 - copy ChoiDujourNX to the paste switch.
8 - Use ChoiDujourNX as the tutorials suggest to upgrade to 6.2 but now select exFAT.
With this I should have a exFAT sd? with emunand in 6.2 and OFW in 4.1.0.
Or should I between topics 5 and 6 use ChoiDujourNX to enable exFAT on 4.1.0 then do 6,7,8.

In advance, thank you for your help.
EDIT: Reading a little about 2.4. Should I care about fuses? Can I just download 6,2 online from the nintendo servers then use 2.4 to play games? What exactly do I lose with the lost of fuses?

By "hekate", I assume you meant the bootloader Hekate, which as you can guess by the name, is a payload not a homebrew application. Meaning you don't load Hekate from the Album but from either the SX Loader menu or you just send Hekate as the payload instead of SX Loader.

There's not much reason to have exFAT support on SysNAND especially if you don't plan on using CFW/homebrew which you shouldn't as that is one of the purposes of EmuNAND. And since you are updating EmuNAND, you don't need to worry about fuses. Speaking of fuses, they are designed to prevent downgrading. They accomplish this by having the console check the fuses and the current firmware; if the fuses are lower than the firmware, it will burn them to compensate. It the fuses are higher than the firmware, the console will refuse to boot up. Downgrading is useful in case a future exploit is revealed on a lower firmware such as an untethered coldboot.

I have a question before updating from 3.0 to 6.2.

I've been stuck on 3.0 with my Switch only gathering dust for ages and now I have pretty much had enough of waiting. I really want to get Mega Man 11 and get my BotW DLC so I'm considering updating with latest OFW. I don't care that much of the online play but it would be nice to access the store. I would still like to have the option to run homebrew sometime in the future.

As I've read the 6.2 is still Atmosphere compatible even with the new signatures. Is there really any big downside for me to update now?

Since all CFW now support 6.2, not really.

 

[Zap2000]

Why are efuses important to keep is it just for ability to downgrade or anything’s else?

 

[Andaman]

Any file merger script or program should work. Just Google it.
If you don't have a clean NAND backup before you started using SX OS, Nintendo may be able to tell you were using SX OS the second you bring your console online.
As far as I know, Horizon (Switch's OS) doesn't check for fuses because that check is already conducted by the console's bootloader. But if you're feeling super paranoid, you can choose not to enable AutoRCM and let your fuses be burnt preventing you from downgrading to firmware 4.0.1 in case a future exploit comes out such as untethered coldboot.
By "hekate", I assume you meant the bootloader Hekate, which as you can guess by the name, is a payload not a homebrew application. Meaning you don't load Hekate from the Album but from either the SX Loader menu or you just send Hekate as the payload instead of SX Loader.

There's not much reason to have exFAT support on SysNAND especially if you don't plan on using CFW/homebrew which you shouldn't as that is one of the purposes of EmuNAND. And since you are updating EmuNAND, you don't need to worry about fuses. Speaking of fuses, they are designed to prevent downgrading. They accomplish this by having the console check the fuses and the current firmware; if the fuses are lower than the firmware, it will burn them to compensate. It the fuses are higher than the firmware, the console will refuse to boot up. Downgrading is useful in case a future exploit is revealed on a lower firmware such as an untethered coldboot.

Since all CFW now support 6.2, not really.

Thanks, kinda thought so.

 

[Draxzelex]

Why are efuses important to keep is it just for ability to downgrade or anything’s else?

Because some people don't like the fact that the current exploit relies on something conductive to enter RCM and is tethered to an internal/external device to send payloads. They may be spoiled from the 3DS scene where they are holding out for an untethered coldboot which has a higher chance of being released on a lower firmware. Overall, avoiding having the fuses burnt gives you more options. When firmware 6.2 came out and people ended up burning fuses, CFW did not support it so their only option was to downgrade. But if you downgrade with burnt fuses, you lose out on Sleep Mode.

 

[er3eroMKII]

By "hekate", I assume you meant the bootloader Hekate, which as you can guess by the name, is a payload not a homebrew application. Meaning you don't load Hekate from the Album but from either the SX Loader menu or you just send Hekate as the payload instead of SX Loader.

There's not much reason to have exFAT support on SysNAND especially if you don't plan on using CFW/homebrew which you shouldn't as that is one of the purposes of EmuNAND. And since you are updating EmuNAND, you don't need to worry about fuses. Speaking of fuses, they are designed to prevent downgrading. They accomplish this by having the console check the fuses and the current firmware; if the fuses are lower than the firmware, it will burn them to compensate. It the fuses are higher than the firmware, the console will refuse to boot up. Downgrading is useful in case a future exploit is revealed on a lower firmware such as an untethered coldboot.

So if I my understanding is right i just need to:
1 - use sx loadder to boot henkate and backup my nand
2 - Create a emunand throught SX OS 2.3 (I've read somewhere on this forum that the emunand is not working on 4.1.0 OFW with SX OS 2.4).
3 - Update the emuNAND to 6.2 with Choi and enable exFAT leaving me with OFW 4.1.0 no exfat support and emuNAND 6.2 exfat support.
4 - Stay offline
5 - hope for a coldbot someday.

 

[Draxzelex]

So if I my understanding is right i just need to:
1 - use sx loadder to boot henkate and backup my nand
2 - Create a emunand throught SX OS 2.3 (I've read somewhere on this forum that the emunand is not working on 4.1.0 OFW with SX OS 2.4).
3 - Update the emuNAND to 6.2 with Choi and enable exFAT leaving me with OFW 4.1.0 no exfat support and emuNAND 6.2 exfat support.
4 - Stay offline
5 - hope for a coldbot someday.

Essentially yes. Although I haven't heard of any issues of EmuNAND not working on 4.1.

 

[Huge_Heffner]

I'm on firmware 4.01 and would like to update my sysnand to 6.2 to play online. However I don't know if I should use autorcm. I know I would burn my fused without it but is it possible for Nintendo to detect that there are unburned fuses on 6.2. I don't want to get banned.

I only used backups on emunand and always offline.

If 6.2 is broken wide open, why would you ever care about downgrading back to an earlier firmware?

There may be a reason, but it seems impractical and has a lot of negative side effects from what I can tell. I don’t really see an upside, at least.

 

[Ranshiro]

So if I my understanding is right i just need to:
1 - use sx loadder to boot henkate and backup my nand
2 - Create a emunand throught SX OS 2.3 (I've read somewhere on this forum that the emunand is not working on 4.1.0 OFW with SX OS 2.4).
3 - Update the emuNAND to 6.2 with Choi and enable exFAT leaving me with OFW 4.1.0 no exfat support and emuNAND 6.2 exfat support.
4 - Stay offline
5 - hope for a coldbot someday.

Team Xecuter has put out a post on their forums which says that their 2.4 doesn't work with ofw 4.1.0 and below. Also they have said that on 2.4 you can't boot other payloads (so ox will freeze if you choose this option) so for your first step you'd need to find another way to push hekate to your switch.

 

[er3eroMKII]

Team Xecuter has put out a post on their forums which says that their 2.4 doesn't work with ofw 4.1.0 and below. Also they have said that on 2.4 you can't boot other payloads (so ox will freeze if you choose this option) so for your first step you'd need to find another way to push hekate to your switch.

As far as I know, SX OS 2.3 can push henkate and create emuNAND (sort of, but i don't pretend to go online right now anyway, so this kind of emuNAND works just fine).
So i'll have a emunand on 6.2 and my OFW on 4.1.0 without burned fuses.