Hacking [4.1.0 IPatched] Newcomer to Switch Hacking - Questions about Caffeine and others

[Francesca]

I've recently purchased a Switch with 4.1.0 system firmware that I checked to learn that it is Ipatched. I've learnt that it qualifies for firmware installation using Caffeine. Got some rather urgent questions that I'd appreciate a knowledgeable person to help me find answers to. My aim right now is to set up homebrew / custom firmware as soon as possible with minimal risk to the system.

1. The Homebrew Guide states that memloader, ChoiDujour and "other homebrew" (their description is given but names not listed) should be avoided to prevent bricking. I'll definitely remember the first two names should they ever pop up anywhere, but what about the rest? Are they ever suggested further in the guide as potential options for users whose consoles are unpatched, so that I know to avoid them on my patched device? This basically threatens death of the system, so I'm taking all precautions I can in advance.

2. Is it even a good idea to go through with custom firmware / homebrew setup at this point in time, when the guide mentions emuMMC still not available right now? Trying to figure things out on my own may lead to fatal errors that I'd rather avoid, so I'm wondering if it's really important enough to postpone any actions until necessary instructions / information are available. Perhaps I can take some steps in my setup but not others as I wait for info to come? e.g. backing up the system NAND or something else.

3. When I got the console, I refused to set up a WiFi connection and, just to be on the safe side (dunno why, really), even turned on Airplane Mode or w/e it's called. I imagine a lot of games will require some online communication in order to be played (haven't done anything with my Switch to know yet, just guessing) so I'm wondering if I should do it at all, and if so, how, taking into account I'm on an ipatched unit. I already do have a Fire Emblem Heroes account, to which I'm rather hesitant to link my Switch considering the risk of ban.

This is my first time with the Switch and hacking it so I'd be really grateful if somebody could help me with these worries and doubts.

 

[Lacius]

I've recently purchased a Switch with 4.1.0 system firmware that I checked to learn that it is Ipatched. I've learnt that it qualifies for firmware installation using Caffeine. Got some rather urgent questions that I'd appreciate a knowledgeable person to help me find answers to. My aim right now is to set up homebrew / custom firmware as soon as possible with minimal risk to the system.

1. The Homebrew Guide states that memloader, ChoiDujour and "other homebrew" (their description is given but names not listed) should be avoided to prevent bricking. I'll definitely remember the first two names should they ever pop up anywhere, but what about the rest? Are they ever suggested further in the guide as potential options for users whose consoles are unpatched, so that I know to avoid them on my patched device? This basically threatens death of the system, so I'm taking all precautions I can in advance.

2. Is it even a good idea to go through with custom firmware / homebrew setup at this point in time, when the guide mentions emuMMC still not available right now? Trying to figure things out on my own may lead to fatal errors that I'd rather avoid, so I'm wondering if it's really important enough to postpone any actions until necessary instructions / information are available. Perhaps I can take some steps in my setup but not others as I wait for info to come? e.g. backing up the system NAND or something else.

3. When I got the console, I refused to set up a WiFi connection and, just to be on the safe side (dunno why, really), even turned on Airplane Mode or w/e it's called. I imagine a lot of games will require some online communication in order to be played (haven't done anything with my Switch to know yet, just guessing) so I'm wondering if I should do it at all, and if so, how, taking into account I'm on an ipatched unit. I already do have a Fire Emblem Heroes account, to which I'm rather hesitant to link my Switch considering the risk of ban.

This is my first time with the Switch and hacking it so I'd be really grateful if somebody could help me with these worries and doubts.

First, do not connect your Switch to the internet yet. When you do set it up with the internet, input the wrong password intentionally, save the settings, go into the settings, add the PegaScape DNS settings, correct the password, and then save the settings. If you connect to the internet without blocking Nintendo's servers, your web browser will get an unremovable supernag, and your Switch will be blocked from hacks permanently.

After all that, use Hekate to backup your NAND and BOOT0/1. That's absolutely the second thing you should do.

I'll address your questions when I am not on my phone.

 

[Deleted User]

1. just dont install something what edits the SysNAND because 2. you cant backup it (ReiNX toolbox can dump it but i dont think that you should try because you should ask someone else)
3. connecting these accounts is completly impossible. if you want the game + account you must update to newest firm in order to install the game and homebrew for ipatched devices isnt possible on 6.x+ or so idk the ipatch exploit with highest firmware is 5.1 or something like that

--------------------- MERGED ---------------------------

First, do not connect your Switch to the internet yet. When you do set it up with the internet, input the wrong password intentionally, save the settings, go into the settings, add the PegaScape DNS settings, correct the password, and then save the settings. If you connect to the internet without blocking Nintendo's servers, your web browser will get an unremovable supernag, and your Switch will will blocked from hacks permanently.

After all that, use Hekate to backup your NAND and BOOT0/1. That's absolutely the second thing you should do.

I'll address your questions when I am not on my phone.

how Hekate?

 

[Lacius]

how Hekate?

One can run Hekate on 4.1.0 using the warmboot browser exploit, assuming there is no supernag.

 

[Deleted User]

One can run Hekate on 4.1.0 using the warmboot browser exploit, assuming there is no supernag.

do you mean Nereba did it got updated for 4.1?

 

[Lacius]

do you mean Nereba did it got updated for 4.1?

It's not technically Nereba, but Deja Vu was released for 4.1.0, so you can run payloads using the web browser on 4.1.0 (even if the system is patched), assuming the web browser doesn't have the supernag.

 

[Deleted User]

It's not technically Nereba, but Deja Vu was released for 4.1.0, so you can run payloads using the web browser on 4.1.0 (even if the system is patched), assuming the web browser doesn't have the supernag.

really didnt noticed....

 

[Lacius]

1. The Homebrew Guide states that memloader, ChoiDujour and "other homebrew" (their description is given but names not listed) should be avoided to prevent bricking. I'll definitely remember the first two names should they ever pop up anywhere, but what about the rest? Are they ever suggested further in the guide as potential options for users whose consoles are unpatched, so that I know to avoid them on my patched device? This basically threatens death of the system, so I'm taking all precautions I can in advance.

You can use whatever you want with emuNAND/emuMMC. You want to avoid system-modifying homebrew on your sysNAND because there will be no way for you to recover if something goes wrong. That's okay though, since you will only ever be using your sysNAND to run the warmboot browser exploit.

2. Is it even a good idea to go through with custom firmware / homebrew setup at this point in time, when the guide mentions emuMMC still not available right now? Trying to figure things out on my own may lead to fatal errors that I'd rather avoid, so I'm wondering if it's really important enough to postpone any actions until necessary instructions / information are available. Perhaps I can take some steps in my setup but not others as I wait for info to come? e.g. backing up the system NAND or something else.

emuMMC is available with Atmosphere, and it's highly recommended if you meet one or both of these conditions:

1. You have a patched system, and your sysNAND is on 4.1.0. You will create an offline emuNAND that you can update to 8.1.0 with ChoiDujourNX to use all of your homebrew and backups with.
2. You plan on using online play. You need another emuNAND (or sysNAND, if a person's Switch is unpatched) that is updated and untouched by hacks.

3. When I got the console, I refused to set up a WiFi connection and, just to be on the safe side (dunno why, really), even turned on Airplane Mode or w/e it's called. I imagine a lot of games will require some online communication in order to be played (haven't done anything with my Switch to know yet, just guessing) so I'm wondering if I should do it at all, and if so, how, taking into account I'm on an ipatched unit. I already do have a Fire Emblem Heroes account, to which I'm rather hesitant to link my Switch considering the risk of ban.

If you use an offline emuNAND for hackery and a clean emuNAND for online play, you should be fine. On the dirty emuNAND for hackery, you can also install 90DNS and/or Incognito to reduce the risk of a ban if it were to accidentally connect to the internet.

See my first post for your first steps.

 

[gRoberts84]

I'm in the same boat, so chipping in with my experience and keen to hear others.

New iPatched 4.1.0 unit which has now been warmbooted via Caffeine/Hekate. Backed up Nand/Boot sectors/keys etc.

I'm now stuck trying to get EmuMMC to boot anything. Essentially I want to keep my sysnand totally clean and literally not touch it unless I have to. Then with EmuMMC or similar, upgrade to the latest firmware etc.

Unfortunately Atmosphere appears to have a bug with the version shipped with SDSetup, which looks to have been fixed yesterday, so hoping to check that out tonight.

ChoiDujournx is supposed to be ok with EmuMMC, just make sure you do not allow AutoRCM.

 

[Lacius]

ChoiDujournx is supposed to be ok with EmuMMC, just make sure you do not allow AutoRCM.

ChoiDujourNX is perfectly fine with emuNAND/emuMMC, as long as you aren't using that emuNAND for online play.

 

[masagrator]

ChoiDujournx is supposed to be ok with EmuMMC, just make sure you do not allow AutoRCM.

Newest version of ChoiDojourNX (1.0.2) blocks automatically autoRCM enable option if it will recognize ipatched Switch.

 

[gRoberts84]

Tutorials are a bit thin on the ground at the moment for EmuMMC and ChoiDojourNX.

Are you specifically asked whether to install on EmuMMC or SysNand? Paranoid I'll end up doing it on SysNand lol

 

[gRoberts84]

D'oh double post

 

[Lacius]

Tutorials are a bit thin on the ground at the moment for EmuMMC and ChoiDojourNX.

Are you specifically asked whether to install on EmuMMC or SysNand? Paranoid I'll end up doing it on SysNand lol

ChoiDojourNX will install to whichever NAND you're currently running.

 

[gRoberts84]

ChoiDojourNX will install to whichever NAND you're currently running.

Does that mean I'd need to warmboot into Hekate, launch EmuMMC Stock and then warmboot again so I can run ChoiDojourNX from Hekate?

 

[Lacius]

Does that mean I'd need to warmboot into Hekate, launch EmuMMC Stock and then warmboot again so I can run ChoiDojourNX from Hekate?

ChoiDojourNX is a homebrew application. You run it from the homebrew launcher in CFW, not from Hekate.

You would warmboot into Hekate, load emuMMC CFW, load the homebrew launcher, and load ChoiDojourNX.

 

[gRoberts84]

ChoiDojourNX is a homebrew application. You run it from the homebrew launcher in CFW, not from Hekate.

Ah ok - suppose that's where I'm getting confused then, as I thought you updated Stock on EmuMMC, not CFW.

I can run ChoiDojourNX from Hekate, as they give you the option, which added to the confusion.

 

[Lacius]

Ah ok - suppose that's where I'm getting confused then, as I thought you updated Stock on EmuMMC, not CFW.

I can run ChoiDojourNX from Hekate, as they give you the option, which added to the confusion.

What is the purpose of your emuMMC: Homebrew and backups, or online play?

 

[gRoberts84]

What is the purpose of your emuMMC: Homebrew and backups, or online play?

Mostly Homebrew and backups, but may end up with a third EmuMMC for online play, so have that in mind when looking around.

Assuming that if I'm just doing homebrew/backups, then CFW is not an issue as I won't be online?

 

[Lacius]

Mostly Homebrew and backups, but may end up with a third EmuMMC for online play, so have that in mind when looking around.

Assuming that if I'm just doing homebrew/backups, then CFW is not an issue as I won't be online?

That is correct. If your are keeping your emuNAND offline, then you can do whatever you want to it without consequences.

I would also recommend installing 90DNS and/or Incognito on the offline emuNAND, just in case it accidentally connects to the internet.

 

[gRoberts84]

That is correct. If your are keeping your emuNAND offline, then you can do whatever you want to it without consequences.

I would also recommend installing 90DNS and/or Incognito on the offline emuNAND, just in case it accidentally connects to the internet.

Cheers - It's on my list, although I assumed I could keep on using Caffeines DNS server. It wouldn't take much for me to setup something more permanent.