Hacking SWITCH NOOB PARADISE - Ask questions here

[Draxzelex]

I've just restored my original switch nand from pre-meddling days, and I'd like to go online. I have a couple questions:
1) I restored the nand and found that rather than 6.0.1 as I expected, my system was on 5.0.1, yet my switch didn't crash on boot and appears to be running fine. Is that something to be concerned about if I'm going to update anyway?

2) My emuMMC has my same data including my NNID-linked user profile. How should I remove that account connection info from my emuMMC to ensure no cross-talk trips up nintendo's servers? Or can I just keep my emuMMC never online and avoid any issue?

3) Do emuMMCs face the same issue with fuses on boot? Meaning, will the switch flip out if you had, say, 11.0.1 on your clean sysnand, and 6.0.1 on your dirty emuMMC, and wanted to boot both of them interchangeably?

4) How best to update the emuMMC if it is needed, and how to avoid the NNID problem that could come with it?

1. No because if anything, that just means you didn't have any save data that only works on 6.X or higher. That and fuses are the only things that cause issues when downgrading especially across major firmware versions
2. Switch doesn't use NNID. Only the 3DS and Wii U do
3. Fuses are only checked with the stock bootloader of the Switch. To boot emuMMC, it is impossible to do that with the stock bootloader so the only way is with a custom bootloader such as a payload. And modern custom bootloaders bypass the fuse check by default
4. You can use homebrew applications such as ChoiDujourNX or Daybreak to update the firmware of emuMMC offline

 

[plegenda]

Hello guys! I humbly request assistance to undo my past mistakes >.>
Situation is this... I have an old revision Switch (non-mariko, if anyone know the name of these to stop calling them non-mariko I'd appreciate it) which is using SX OS and I'd like to switch it to Atmosphere. Could any of you point me in the right direction to do this?

here are the specifics.
about the switch:
-its old one (non-mariko)
-Its running Emunand on 10.2.0
-SX OS V3.0.5
-currently on autoRCM
-Has a SXOS Pro Dongle thingy
-I think Sysnand is 10.2.0 as well (has a system update ready, but I havent clicked to update it, so it doesnt show me the number)


about me:
-its been a long time since I "hacked" the console and there has to be a lot to catch up
-bricks scare me >.>

plz forum, send guidance

 

[Draxzelex]

Hello guys! I humbly request assistance to undo my past mistakes >.>
Situation is this... I have an old revision Switch (non-mariko, if anyone know the name of these to stop calling them non-mariko I'd appreciate it) which is using SX OS and I'd like to switch it to Atmosphere. Could any of you point me in the right direction to do this?

here are the specifics.
about the switch:
-its old one (non-mariko)
-Its running Emunand on 10.2.0
-SX OS V3.0.5
-currently on autoRCM
-Has a SXOS Pro Dongle thingy
-I think Sysnand is 10.2.0 as well (has a system update ready, but I havent clicked to update it, so it doesnt show me the number)


about me:
-its been a long time since I "hacked" the console and there has to be a lot to catch up
-bricks scare me >.>

plz forum, send guidance

Luckily for you, a lot of people have not only begun switching from SX OS to Atmosphere but others have noticed there is a stark lack of guides for this very topic. I recommend following this guide for transitioning CFW. And to answer your first question, the first revision are referred to as "Erista" units named after Marvel heroes much like Mariko.

 

[plegenda]

yeah, I think a lot of us have been waiting for a new release on SX OS side not for supporting them but merely for commodity or plain laziness to redo the hack. But at this point... I think they are dead, even their forums have been down for a few days now. We all should have changed a while ago tbh.

Thanks Draxzelex!!! will use the guide and let you know how it went!

 

[actualkoifish]

@Draxzelex Sorry, on #2 I was confused between NNID and Nintendo Account. I have the same Nintendo account linked on both eMMC and on emuMMC.

Follow-up on #1, does it mean also that once you upgrade to current firmware you can't restore back to that old nand? I noticed a segment in the restore nand section of NH guides about how you have to ensure autorcm is on to prevent a crash on boot after restoring a NAND from an older version, but it didn't mention whether that was a permanent problem for trying to restore an older sysnand or if it lets you boot sysnand again in the end.

 

[Draxzelex]

@Draxzelex Sorry, on #2 I was confused between NNID and Nintendo Account. I have the same Nintendo account linked on both eMMC and on emuMMC.

Follow-up on #1, does it mean also that once you upgrade to current firmware you can't restore back to that old nand? I noticed a segment in the restore nand section of NH guides about how you have to ensure autorcm is on to prevent a crash on boot after restoring a NAND from an older version, but it didn't mention whether that was a permanent problem for trying to restore an older sysnand or if it lets you boot sysnand again in the end.

Under normal circumstances, the answer would have been yes. However we have an exploit that is triggered before the fuse check so we can bypass that part in order to boot any firmware we want. Practically however this is not very useful as this requires us to use the exploit to boot a lower firmware version so if you think this is useful for exploits on lower firmware versions, understand that that would mean you have to use an already existing exploit to take advantage of another exploit; in other words, its pointless. But there are situations where this can be useful such as allowing us to be able to restore older eMMC backups even if the firmware on the backup is lower than the fuse count. That is why burning fuses on unpatched models is not a permanent problem because the exploit allows us to always have a way to bypass the fuse check and the exploit cannot be patched out.

 

[plegenda]

Luckily for you, a lot of people have not only begun switching from SX OS to Atmosphere but others have noticed there is a stark lack of guides for this very topic. I recommend following this guide for transitioning CFW. And to answer your first question, the first revision are referred to as "Erista" units named after Marvel heroes much like Mariko.

ok I found my first obstacle.
this guide uses a python3 script which requires some modules. I downloaded python and been struggling to do the module thingy. The script doesnt seem to download or create any files for me >.<

Sorry to bother again Draxzelex, but by any chance do you know of another guide with manual downloads and stuff?
I'll keep diggin on my side, but just in case you do

 

[Draxzelex]

ok I found my first obstacle.
this guide uses a python3 script which requires some modules. I downloaded python and been struggling to do the module thingy. The script doesnt seem to download or create any files for me >.<

Sorry to bother again Draxzelex, but by any chance do you know of another guide with manual downloads and stuff?
I'll keep diggin on my side, but just in case you do

Its funny you mention a guide with manual downloads because that guide is actually based on a pre-existing guide full of those. You can find it in the thread I originally linked in the first post but here is the same link to save yourself a click. The only reason I didn't recommend it in the beginning is because OP mentions that he has not updated the guide in a while but the main principle should be the same.

 

[plegenda]

Its funny you mention a guide with manual downloads because that guide is actually based on a pre-existing guide full of those. You can find it in the thread I originally linked in the first post but here is the same link to save yourself a click. The only reason I didn't recommend it in the beginning is because OP mentions that he has not updated the guide in a while but the main principle should be the same.

Thanks!
I went into that one earlier and disregarded it for that same reason.
Will take a good read there and follow that path, thanks Drax!

 

[ganonleboucher]

Hi!
First at all i would like to thanks the community for all the work done here! Serously guys you are the best!

I just hack my switch with Heckate/Atmosphere and everything is working very well!
I made a emuMMC and block Nin serv with 90dns and Incognito (for emuMMC as well as sysMMC).
I succeed to install nsp files with TinWoo and Tinleaf (couldn't success to make Goldleaf works so far (Error 2001-0123 with version 0.9.0-dev) but it's ok).

The only thing for what i didn't find ''proper'' answer is :

Is it safe to install nsp files on my internal storage from my emuMMC or better keeping installing on my sd card and ''reserve'' my internal storage for games i already bought on the eshop?

Once again huge big up to the community!

 

[actualkoifish]

Under normal circumstances, the answer would have been yes. However we have an exploit that is triggered before the fuse check so we can bypass that part in order to boot any firmware we want. Practically however this is not very useful as this requires us to use the exploit to boot a lower firmware version so if you think this is useful for exploits on lower firmware versions, understand that that would mean you have to use an already existing exploit to take advantage of another exploit; in other words, its pointless. But there are situations where this can be useful such as allowing us to be able to restore older eMMC backups even if the firmware on the backup is lower than the fuse count. That is why burning fuses on unpatched models is not a permanent problem because the exploit allows us to always have a way to bypass the fuse check and the exploit cannot be patched out.

Thanks for that explanation. I do wonder though, does that only work if you use a certain boot method for sysnand? ie. on my system I use hekate and on the boot menu, I just select "stock sysnand". Is that not what one should do?

 

[Draxzelex]

Thanks for that explanation. I do wonder though, does that only work if you use a certain boot method for sysnand? ie. on my system I use hekate and on the boot menu, I just select "stock sysnand". Is that not what one should do?

To try and make things simple, think of a bootloader as something that boots CFW/OFW. When you turn on the console normally, this is using the stock bootloader built into the console itself. When you send a payload that boots CFW or OFW such as Hekate, then you are using a custom bootloader. Therefore booting something such as "Stock sysNAND" would count as using as a custom bootloader because you are not using the stock bootloader but an external one via a payload.

 

[actualkoifish]

To try and make things simple, think of a bootloader as something that boots CFW/OFW. When you turn on the console normally, this is using the stock bootloader built into the console itself. When you send a payload that boots CFW or OFW such as Hekate, then you are using a custom bootloader. Therefore booting something such as "Stock sysNAND" would count as using as a custom bootloader because you are not using the stock bootloader but an external one via a payload.

Thanks for explainin it all.

Unrelated to that but still an issue, is this thread appropriate for asking questions about goldleaf install problems, or does that go over the line for accepted discussion?

 

[Draxzelex]

Thanks for explainin it all.

Unrelated to that but still an issue, is this thread appropriate for asking questions about goldleaf install problems, or does that go over the line for accepted discussion?

That is the wonderful thing about this thread; because there is no topic, you can ask as many questions unrelated to your original issue and still get answers.

Anyway, this is just my personal opinion but Goldleaf is arguably the worst title installer for various reasons. If you have any issues with it, I wouldn't be surprised in the slightest. Before you even tell me about the problem, give TinWoo Installer a spin and see if it solves your dilemma.

 

[Regained]

I'm on version 9.2 firmware and wanted to update to 10.2 on emummc so i put on the latest atmosphere. When i get to Hekate and chose emummc, its giving me a yellow screen. I updated my rcmloader then with the latest fusee primary, and it boots all the way without a Hekate menu.

When i chose Reboot to payload, it takes me to Hekate, but when i select emummc, i get the yellow screen again.

Did atmosphere break my emummc partition? how do i fix this? thanks

 

[SkyDX]

Quick question, when in Atmosphere, can I somehow access the SD-card over USB?

EDIT: And two other questions, if I want to enable Exosphere Prodinfo Blanking on my emuMMC I would copy exosphere.ini from config_templates to config and set blank_prodinfo_emummc=1 at the end right?

Same question for the new DNS stuff:

I would copy system_settings.ini to config and then alter these lines?

; Controls whether dns.mitm is enabled
; 0 = Disabled, 1 = Enabled
; enable_dns_mitm = u8!0x1
; Controls whether dns.mitm uses the default redirections in addition to
; whatever is specified in the user's hosts file.
; 0 = Disabled (use hosts file contents), 1 = Enabled (use defaults and hosts file contents)
; add_defaults_to_dns_hosts = u8!0x1

I ask because the default template here has this weird "u8!0x1" as default o.o

 

[Draxzelex]

Quick question, when in Atmosphere, can I somehow access the SD-card over USB?

EDIT: And two other questions, if I want to enable Exosphere Prodinfo Blanking on my emuMMC I would copy exosphere.ini from config_templates to config and set blank_prodinfo_emummc=1 at the end right?

Same question for the new DNS stuff:

I would copy system_settings.ini to config and then alter these lines?

; Controls whether dns.mitm is enabled
; 0 = Disabled, 1 = Enabled
; enable_dns_mitm = u8!0x1
; Controls whether dns.mitm uses the default redirections in addition to
; whatever is specified in the user's hosts file.
; 0 = Disabled (use hosts file contents), 1 = Enabled (use defaults and hosts file contents)
; add_defaults_to_dns_hosts = u8!0x1

I ask because the default template here has this weird "u8!0x1" as default o.o

You can use the homebrew application nxmtp to move files via USB. As for your second question, I guess so although I am afraid that I'm unfamiliar with prodinfo blanking via exosphere.

 

[RikkuSuave]

I am very new to homebrew on the switch, as in i just installed CFW/Homebrew on my switch like 3 days ago. I have a legit physical copy of ACNH and the firmware on my switch is 11.0.1. the game wants me to update but i dont have it hooked up to the internet out of paranoia and i don't fully understand how playing online with a hacked switch works. Can i update my game normally? i dont have any weird hacks in my town, just gave myself some bells and items no weird trees or anything sketchy. if not, how do i update? and can i play online at all? thanks!

 

[Draxzelex]

I am very new to homebrew on the switch, as in i just installed CFW/Homebrew on my switch like 3 days ago. I have a legit physical copy of ACNH and the firmware on my switch is 11.0.1. the game wants me to update but i dont have it hooked up to the internet out of paranoia and i don't fully understand how playing online with a hacked switch works. Can i update my game normally? i dont have any weird hacks in my town, just gave myself some bells and items no weird trees or anything sketchy. if not, how do i update? and can i play online at all? thanks!

Connecting a hacked console carries a risk of getting banned. There is really no way to circumvent or reduce the chances outside of simply not hacking the console. If you don't want to risk getting banned by updating online, you can download the update illegally from the Internet then install it with any of the available title managers.

 

[RikkuSuave]

I thought as much! I am not sure where to begin with the title managers and update files, is there a guide someplace that could help me with that?