Hacking Is this website still good for switch hacks?

[Naxster]

I personally don't use it, but it's up to date and usable, yes.

Is there any other guides? I mean is there any "better" guides?

 

[Lacius]

Is there any other guides? I mean is there any "better" guides?

This is the best guide, in my opinion. That being said, I don't use Kosmos. I use Atmosphere with fusee-primary and the proper signature patches. This allows for fewer issues down the road and quicker updates.

 

[Naxster]

This is the best guide, in my opinion. That being said, I don't use Kosmos. I use Atmosphere with fusee-primary and the proper signature patches. This allows for fewer issues down the road and quicker updates.

Sweet thank you, i will look into that guide

Hmmm should i go with the one you have right now, or should i buy SX OS in order to use EmuNAND?? I don't want to update my SysNAND (3.0.1).

 

[Lacius]

Sweet thank you, i will look into that guide

Hmmm should i go with the one you have right now, or should i buy SX OS in order to use EmuNAND?? I don't want to update my SysNAND (3.0.1).

1. There is no reason to buy SX OS. Atmosphere can do just about everything SX OS can, including emuNAND.
2. If you don't want to use emuNAND, you can update your sysNAND while keeping your fuse count low so you can downgrade later if you want. This can be accomplished using AutoRCM.
3. Unless you care about future exploits, there is no reason to stay on 3.0.1 or preserve your fuse count.

 

[Deleted-401606]

Turns out I don't have a USB-C cable.Had to order one from the internet as well as an RCM jig.

 

[Naxster]

1. There is no reason to buy SX OS. Atmosphere can do just about everything SX OS can, including emuNAND.
2. If you don't want to use emuNAND, you can update your sysNAND while keeping your fuse count low so you can downgrade later if you want. This can be accomplished using AutoRCM.
3. Unless you care about future exploits, there is no reason to stay on 3.0.1 or preserve your fuse count.

Really? Daam i must have missed the part where Atmosphere included EmuNAND
Wait, so it's possible to downgrade our Switch now?
The only reason i stayed on 3.0.1, is because i want to be able to boot the Switch without any jig.... You know, Warm boot/cold boot.

One dumb question, i have seen this A LOT... But how do you preserve the fuse? And how do you even burn them? I've seen people writing not to burn the fuses, but how do you even do that? And is there a way NOt to burn them at all?

 

[Lacius]

Turns out I don't have a USB-C cable.Had to order one from the internet as well as an RCM jig.

You don't need to order a jig. A paperclip works nicely to get into RCM and install AutoRCM. You can also use the browser method if you're on 4.0.1, which doesn't require a jig, and you might be able to install AutoRCM from the browser method.

 

[Deleted-401606]

You don't need to order a jig. A paperclip works nicely to get into RCM and install AutoRCM. You can also use the browser method if you're on 4.0.1, which doesn't require a jig, and you might be able to install AutoRCM from the browser method.

Alright I just cancelled it. Do you have a guide for browser method? This has just been a bit confusing and I don't know how I forgot the USB-C cable. Feelsbadman.

 

[Lacius]

Really? Daam i must have missed the part where Atmosphere included EmuNAND
Wait, so it's possible to downgrade our Switch now?
The only reason i stayed on 3.0.1, is because i want to be able to boot the Switch without any jig.... You know, Warm boot/cold boot.

One dumb question, i have seen this A LOT... But how do you preserve the fuse? And how do you even burn them? I've seen people writing not to burn the fuses, but how do you even do that? And is there a way NOt to burn them at all?

Fuses prevent downgrades. If you've booted 3.0.1 normally, then that means you have 4 burnt fuses, and you can never effectively downgrade to anything lower than 3.0.1. You can prevent fuses from being burnt by keeping AutoRCM installed so the Switch can never boot normally, or you can keep your sysNAND low and only update your emuNAND.

A warmboot browser exploit already exists for 4.1.0 and lower.

 

[Naxster]

Fuses prevent downgrades. If you've booted 3.0.1 normally, then that means you have 4 burnt fuses, and you can never effectively downgrade to anything lower than 3.0.1. You can prevent fuses from being burnt by keeping AutoRCM installed so the Switch can never boot normally, or you can keep your sysNAND low and only update your emuNAND.

A warmboot browser exploit already exists for 4.1.0 and lower.

I have never booted my Nintendo Switch, i have only booted into recovery mode, just to check which version it was when i bought it 1 year ago (if not more).. I dont know if that counts as booted.

Which would you recommend, the AutoRCM or EmuNAND? The only reason i like EmuNAND is because you can "play" with the system without affecting the "real" system.. Just like in 3DS.

Where can i find this warmboot?
I have nothing against using a jig, but i do know that one of my little siblings or even my younger cousin will mess up and update the shit so i won't work anymore since they dont know how to use the jig, that's why i waited until we get a warmboot so they don't accidentally update the console

 

[PHiLiPZ]

To prevent someone booting the OFW use the AutoRCM. Don’t configure any WiFi connections in sysnand too. And to be completely sure install an emunand (with AutoRCM still active, they can and should both be used at the same time).

 

[Deleted-401606]

Edit.Double post.

 

[Lacius]

I have never booted my Nintendo Switch, i have only booted into recovery mode, just to check which version it was when i bought it 1 year ago (if not more).. I dont know if that counts as booted.

You can check how many fuses are burnt in Hekate's fuse info menu. If the system arrived on 3.0.1, it has 4 burnt fuses regardless of whether or not you've booted Horizon. That means the Switch can never be downgraded to anything lower than 3.0.1 in any way that would be beneficial.

Which would you recommend, the AutoRCM or EmuNAND?

If the goal is only to preserve fuses, that's a matter of personal preference. Personally, I use AutoRCM because I find it to be very convenient. In fact, I would be using AutoRCM even if it didn't preserve fuses. Some people don't like AutoRCM, however.

If you care about online play, then you need to use an emuNAND for hacks and a clean sysNAND for online play. I don't use online play, so I don't have an emuNAND.

If your concern is being able to recover from a brick when using an emuNAND, it should be noted that having a NAND backup is just as helpful as using an emuNAND, so brick-recovery isn't a real reason to use an emuNAND.

Where can i find this warmboot?

You can follow this guide to use the warmboot exploit, but you will have to update to 4.0.1 or 4.1.0. Using the warmboot exploit requires that you boot 4.0.1 or 4.1.0 normally though, meaning you would have to burn fuses, and you would be unable to downgrade to anything lower than 4.0.0.

I have nothing against using a jig, but i do know that one of my little siblings or even my younger cousin will mess up and update the shit so i won't work anymore since they dont know how to use the jig, that's why i waited until we get a warmboot so they don't accidentally update the console

1. If your concern is siblings accidentally updating your Switch, you don't want to rely on a warmboot exploit. If the system is accidentally updated, that is the exploit you will be locked out of. The RCM exploit cannot be patched by system updates.
2. If you install AutoRCM, you don't have to use a jig. The system will automatically coldboot into RCM. This can be convenient, but it also means that you cannot fully power off the system and turn it back on without having to plug the Switch into a computer or phone to launch an RCM payload like Hekate or fusee-primary. As long as the system is kept in sleep mode when you're not using it, you shouldn't run into any problems.
3. It is very easy to block online systems updates with 90DNS and/or Incognito. If you're paranoid, you can use both. Keeping the system offline also helps.

 

[Naxster]

You can check how many fuses are burnt in Hekate's fuse info menu. If the system arrived on 3.0.1, it has 4 burnt fuses regardless of whether or not you've booted Horizon. That means the Switch can never be downgraded to anything lower than 3.0.1 in any way that would be beneficial.

Wow thank you for all this information! Really helpful!
It's okay if i can't downgrade it lower than 3.0.1, at least i can install CFW on it

If the goal is only to preserve fuses, that's a matter of personal preference. Personally, I use AutoRCM because I find it to be very convenient. In fact, I would be using AutoRCM even if it didn't preserve fuses. Some people don't like AutoRCM, however.

Hmmm i've read that AutoRCM drains the battery a lot faster and "destroys" the console after a while... Is that true? :/

If you care about online play, then you need to use an emuNAND for hacks and a clean sysNAND for online play. I don't use online play, so I don't have an emuNAND.

If your concern is being able to recover from a brick when using an emuNAND, it should be noted that having a NAND backup is just as helpful as using an emuNAND, so brick-recovery isn't a real reason to use an emuNAND.

Naah i'm not intrested at all to play online, i don't even care if it gets banned
Yea the first thing i'm going to do is to backup everything by using this guide: https://gbatemp.net/threads/backup-...-your-biskeys-tseckeys-keys-txt-guide.513386/
Is that guide still relevant or is there a "better" guide out there now?

You can follow this guide to use the warmboot exploit, but you will have to update to 4.0.1 or 4.1.0. Using the warmboot exploit requires that you boot 4.0.1 or 4.1.0 normally though, meaning you would have to burn fuses, and you would be unable to downgrade to anything lower than 4.0.0.

1. If your concern is siblings accidentally updating your Switch, you don't want to rely on a warmboot exploit. If the system is accidentally updated, that is the exploit you will be locked out of. The RCM exploit cannot be patched by system updates.
2. If you install AutoRCM, you don't have to use a jig. The system will automatically coldboot into RCM. This can be convenient, but it also means that you cannot fully power off the system and turn it back on without having to plug the Switch into a computer or phone to launch an RCM payload like Hekate or fusee-primary. As long as the system is kept in sleep mode when you're not using it, you shouldn't run into any problems.
3. It is very easy to block online systems updates with 90DNS and/or Incognito. If you're paranoid, you can use both. Keeping the system offline also helps.

1. Let say that i update it to 4.0.1, and then install EmuNAND, would that Warmboot still work to boot up directly to EmuNAND instead of SysNAND?
2. Daam i thought we could power off the system completely.. Well it's a a bummer we can't do that without having to plug the Switch into a computer/Phone... What happens if the battery dies when it's on sleep mode?
3. i will look into this 90DNS thingy and see how it works

 

[Lacius]

Hmmm i've read that AutoRCM drains the battery a lot faster and "destroys" the console after a while... Is that true? :/

AutoRCM is relatively safe and will not drain (nor destroy) your battery. If you accidentally leave your system in RCM, it will drain your battery, but this should never happen if you do things correctly. If you have AutoRCM installed, you should leave your Switch in sleep mode whenever it's not being used.

Naah i'm not intrested at all to play online, i don't even care if it gets banned

If you don't care about online play, then there's probably no real reason to use an emuNAND.

Yea the first thing i'm going to do is to backup everything by using this guide: https://gbatemp.net/threads/backup-...-your-biskeys-tseckeys-keys-txt-guide.513386/
Is that guide still relevant or is there a "better" guide out there now?

All you need to do is launch Hekate and backup your NAND and BOOT0/1. These things should be stored somewhere safe (compressed in an online location like Google Drive is recommended).

This guide is recommended for all things Switch (except emuNAND), and it has a section on backing up your NAND and whatnot: https://switch.homebrew.guide/usingcfw/hekate

1. Let say that i update it to 4.0.1, and then install EmuNAND, would that Warmboot still work to boot up directly to EmuNAND instead of SysNAND?

No, not exactly. Warmboot means you can't "boot up directly" into hacks of any kind. That would be a coldboot.

If you have a 4.0.1 sysNAND and an 8.1.0 emuNAND, for example, you will have to power on your 4.0.1 Switch, load the internet browser, run PegaScape, run Hekate, and then boot into your emuNAND. If you keep your Switch in sleep mode when it's not being used, you will rarely have to leave your emuNAND. The only reason to do this setup on an unpatched system is if you a.) Hate the RCM exploit, and/or b.) Want to keep your fuses relatively low without using AutoRCM.

2. Daam i thought we could power off the system completely.. Well it's a a bummer we can't do that without having to plug the Switch into a computer/Phone...

You can power off the system completely, but you will have to either a.) Boot into RCM again and run a payload, or b.) Use the warmboot browser exploit after powering on your system again. The Switch was designed to be kept in sleep mode when unused, so this isn't much of an issue at all.

If you want to install a modchip, you can also setup your system so that it coldboots into RCM with AutoRCM and automatically runs a payload like Hekate from the modchip. This is the only way to get a true untethered coldboot experience, but it's a little pointless, in my opinion, with the existence of sleep mode.

What happens if the battery dies when it's on sleep mode?

1. It's unlikely the battery will die in sleep mode, unless you're keeping it undocked for days or weeks at a time.
2. If the battery does die while in sleep mode with AutoRCM installed, you will have to plug it into your computer to push a payload as though you had fully powered it off. If the battery is fully dead, you might have to wait for the Switch to trickle charge enough to boot into RCM, which can take half an hour or so in extreme circumstances usually only seen if the Switch was left in RCM accidentally.

3. i will look into this 90DNS thingy and see how it works

90DNS is merely a DNS that blocks Nintendo's servers. Incognito removes all identifiable information from your Switch, making it impossible to ban you (for anything done after installing Incognito) and effectively blocking connections to Nintendo's servers. In other words, both of these things keep you safe from bans and accidental system updates.

 

[Naxster]

AutoRCM is relatively safe and will not drain (nor destroy) your battery. If you accidentally leave your system in RCM, it will drain your battery, but this should never happen if you do things correctly. If you have AutoRCM installed, you should leave your Switch in sleep mode whenever it's not being used.

Then sleep mode it is! If that work, then i will use that

If you don't care about online play, then there's probably no real reason to use an emuNAND.

The only reason i want emuNAND is to "play" with the system without affecting the real system (SysNAND).. I mean if something happens, i can just remove the emuNAND from the SD-card and install a new one... I think it's the same thing as 3DS.
I remember when i screwed up the emuNAND in 3DS after experimenting with it too much, i just deleted the emuNAND in the SD-card and install a new emuNAND

All you need to do is launch Hekate and backup your NAND and BOOT0/1. These things should be stored somewhere safe (compressed in an online location like Google Drive is recommended).

This guide is recommended for all things Switch (except emuNAND), and it has a section on backing up your NAND and whatnot: https://switch.homebrew.guide/usingcfw/hekate

Sweet thank you very much! I will follow that guide!

No, not exactly. Warmboot means you can't "boot up directly" into hacks of any kind. That would be a coldboot.

If you have a 4.0.1 sysNAND and an 8.1.0 emuNAND, for example, you will have to power on your 4.0.1 Switch, load the internet browser, run PegaScape, run Hekate, and then boot into your emuNAND. If you keep your Switch in sleep mode when it's not being used, you will rarely have to leave your emuNAND. The only reason to do this setup on an unpatched system is if you a.) Hate the RCM exploit, and/or b.) Want to keep your fuses relatively low without using AutoRCM.

Ahhh i see!
So i have a 4.0.1 sysNAND and a 8.1.0 emuNAND can i still use AutoRCM to boot into emuNAND directly?

You can power off the system completely, but you will have to either a.) Boot into RCM again and run a payload, or b.) Use the warmboot browser exploit after powering on your system again. The Switch was designed to be kept in sleep mode when unused, so this isn't much of an issue at all.

If you want to install a modchip, you can also setup your system so that it coldboots into RCM with AutoRCM and automatically runs a payload like Hekate from the modchip. This is the only way to get a true untethered coldboot experience, but it's a little pointless, in my opinion, with the existence of sleep mode.

1. It's unlikely the battery will die in sleep mode, unless you're keeping it undocked for days or weeks at a time.
2. If the battery does die while in sleep mode with AutoRCM installed, you will have to plug it into your computer to push a payload as though you had fully powered it off. If the battery is fully dead, you might have to wait for the Switch to trickle charge enough to boot into RCM, which can take half an hour or so in extreme circumstances usually only seen if the Switch was left in RCM accidentally.

90DNS is merely a DNS that blocks Nintendo's servers. Incognito removes all identifiable information from your Switch, making it impossible to ban you (for anything done after installing Incognito) and effectively blocking connections to Nintendo's servers. In other words, both of these things keep you safe from bans and accidental system updates.

A modchip won't be necessary, since we, as you wrote, have the sleep mode feature.
Ahhh that's good! I thought i drain a lot of battery even if it was on sleep mode (my 3DS did that)...

But one last question, that just popped up in my mind..

Let say that i have AutoRCM, and that i have accidentally, turn it off completely... Instead of using my computer or a phone to load the payload, can't i, and i quote as you wrote "load the internet browser, run PegaScape, run Hekate, and then boot into your emuNAND" ??

 

[Lacius]

The only reason i want emuNAND is to "play" with the system without affecting the real system (SysNAND).. I mean if something happens, i can just remove the emuNAND from the SD-card and install a new one... I think it's the same thing as 3DS.
I remember when i screwed up the emuNAND in 3DS after experimenting with it too much, i just deleted the emuNAND in the SD-card and install a new emuNAND

If you mess up your sysNAND, you can always restore an old sysNAND backup. It's functionally the same thing as making a new emuNAND if you mess up your emuNAND, minus the headache of having to use an emuNAND. In summary, I don't recommend bothering with an emuNAND unless you want to use online play.

So i have a 4.0.1 sysNAND and a 8.1.0 emuNAND can i still use AutoRCM to boot into emuNAND directly?

AutoRCM will not allow you to boot into emuNAND directly. It will only allow you to coldboot into RCM. You still need to inject a payload using something like your computer to boot your Switch into sysNAND or emuNAND with AutoRCM installed.

If you leave your Switch in sleep mode when you're not using it, you will stay in emuNAND.

Let say that i have AutoRCM, and that i have accidentally, turn it off completely... Instead of using my computer or a phone to load the payload, can't i, and i quote as you wrote "load the internet browser, run PegaScape, run Hekate, and then boot into your emuNAND" ??

No. With AutoRCM installed, your Switch will always coldboot into RCM, and you cannot leave RCM without pushing a payload. In other words, you cannot coldboot your Switch into anything at all without a computer or something to push a payload. That's the drawback with AutoRCM, and it's why it should be kept in sleep mode whenever it's not being used.

 

[Naxster]

If you mess up your sysNAND, you can always restore an old sysNAND backup. It's functionally the same thing as making a new emuNAND if you mess up your emuNAND, minus the headache of having to use an emuNAND. In summary, I don't recommend bothering with an emuNAND unless you want to use online play.

Didn't think about that, you are right :/
I will see what i will do when i begin installing a CFW

AutoRCM will not allow you to boot into emuNAND directly. It will only allow you to coldboot into RCM. You still need to inject a payload using something like your computer to boot your Switch into sysNAND or emuNAND with AutoRCM installed.

If you leave your Switch in sleep mode when you're not using it, you will stay in emuNAND.

Ahhh now i get it! Well i guess i should keep it in sleep mode then

No. With AutoRCM installed, your Switch will always coldboot into RCM, and you cannot leave RCM without pushing a payload. In other words, you cannot coldboot your Switch into anything at all without a computer or something to push a payload. That's the drawback with AutoRCM, and it's why it should be kept in sleep mode whenever it's not being used.

Is there a way to uninstall this AutoRCM if i don't want it anymore?

 

[Lacius]

Is there a way to uninstall this AutoRCM if i don't want it anymore?

AutoRCM can be removed at any time with Hekate.

 

[Naxster]

AutoRCM can be removed at any time with Hekate.

Sweet, thank you for all your help!!
I will read that guide carefully a few times before I begin to install Atmosphere

EDIT: Wait one last question, let say there is a new update, would it be easy enough to update the system? Or should I just update it to 8.1.0 and never touch it again?