Hacking SWITCH NOOB PARADISE - Ask questions here

[bloodpancake]

Hey all, I just recently updated Atmosphere to 1.1.1 and my emunand to software 13.0. When I start up now I get an error saying that my game cartridge slot cannot be read from. From what I understand this is because my emunand version is 13.0 but my stock system software is still on 11.0.1. In order to fix this, would it be as simple as removing the sd card, booting into the stock system and then updating my software through the nintendo servers? Or is there a work-around for this?

*EDIT*

As an aside to this, I originally was planning on never updating my system past 11.0.1 just in case a newer version removed functionality from running CFW, but I guess since my switch is unpatched it probably doesn't matter what software version I'm using right?

 

[ninja002]

I have a weird issue and have looked and looked for a solution to it, on cfw when after tinfoil is installed and shop added get new games and recommended on the side list after a .nsp install most games when launched fails to start software, thats not my issue the issue is when i reload Tinfoil it reverts back to the original version and the update i just did to tinfoil is gone same wirth the titles new games and recommended. I appreciate all the devs hard work and thank you for your time

 

[ninja002]

I have a weird issue and have looked and looked for a solution to it, on cfw when after tinfoil is installed and shop added get new games and recommended on the side list after a .nsp install most games when launched fails to start software, thats not my issue the issue is when i reload Tinfoil it reverts back to the original version and the update i just did to tinfoil is gone same wirth the titles new games and recommended. I appreciate all the devs hard work and thank you for your time

 

[androidguest64]

Can I clean Mariko SysNand (dirty by homebrews) just by factory reset? thanks

 

[3DSBricker]

Can I clean Mariko SysNand (dirty by homebrews) just by factory reset? thanks

No, but you can use Haku33. It will fully reset it as if it just came out of the box. All CFW traces will be deleted (including your games, saves and captures of course).

 

[androidguest64]

No, but you can use Haku33. It will fully reset it as if it just came out of the box. All CFW traces will be deleted (including your games, saves and captures of course).

Thanks man, but Is Haku33 works on Mariko though?

 

[3DSBricker]

Thanks man, but Is Haku33 works on Mariko though?

Yes it works on Mariko.

 

[androidguest64]

Yes it works on Mariko.

But on the Haku33 "ReadMe" file, there is a text saying:
> Mariko units are not supported avode 2.8 payloads can't be loaded

and also: https://github.com/StarDustCFW/Haku33/issues/16#issuecomment-924068646


Could you elaborate please? thanks.

 

[3DSBricker]

No, I don't know what "avode" is. (looked on the official Github page and the word is indeed on there). But if you look on the releases page you can see instructions for Mariko. Only reboot to payload doesn't work on it so you need to use Hekate. https://github.com/StarDustCFW/Haku33/releases

 

[androidguest64]

No, I don't know what "avode" is. (looked on the official Github page and the word is indeed on there). But if you look on the releases page you can see instructions for Mariko. Only reboot to payload doesn't work on it so you need to use Hekate. https://github.com/StarDustCFW/Haku33/releases

Hi m8, finally get it together and use this method instead: gbatemp.net/threads/cleaning-up-nand-to-play-online-safely.551767/

now I can link an account and browse eShop online. (never online before)

 

[clasnas]

Can homebrew in any way modify sysNAND while running on emuNAND? And if not, is this because of some safety measure in Atmosphere?

 

[cvskid]

Has anyone tried using web browser emulators through the nintendo switch hidden web browser

 

[3DSBricker]

Can homebrew in any way modify sysNAND while running on emuNAND? And if not, is this because of some safety measure in Atmosphere?

No, and it's because SysNAND and EmuNAND are completely separated.

 

[clasnas]

No, and it's because SysNAND and EmuNAND are completely separated.

To clarify, any modifications made to files in NAND from within emuNAND strictly refers to the emuNAND. Correct? Id imagine it says NAND since homebrew isnt aware of where its running on (as far as I know).

 

[Kallim]

I was just thinking. How Often is it reccomeded to make a backup of the Sysnand and Emunand on the switch??

I was thinking the Sysnand should be backed up everytime the firmware is updated.

And you don't really need to update the firmware on the emunand (might be worth doing if its old). But backup if you do update and backup when you've pretty much got mosy of the things you want on the SD card.

Does that seem sensible. I've never used one yet (or I did on the wii and 3DS). But I do think its worth keeping a backup of both nands or is that considered a waste of space (in other words keep the sysnand just re hack it for the emunand).

 

[clasnas]

I was just thinking. How Often is it reccomeded to make a backup of the Sysnand and Emunand on the switch??

I was thinking the Sysnand should be backed up everytime the firmware is updated.

And you don't really need to update the firmware on the emunand (might be worth doing if its old). But backup if you do update and backup when you've pretty much got mosy of the things you want on the SD card.

Does that seem sensible. I've never used one yet (or I did on the wii and 3DS). But I do think its worth keeping a backup of both nands or is that considered a waste of space (in other words keep the sysnand just re hack it for the emunand).

Id imagine you really only need to create another sysNAND backup when fuses are burned, seeing as you cant install a past backup once additional fuses are burned (without the use of cfw)

 

[3DSBricker]

To clarify, any modifications made to files in NAND from within emuNAND strictly refers to the emuNAND. Correct? Id imagine it says NAND since homebrew isnt aware of where its running on (as far as I know).

Indeed. Perhaps some homebrew do have code to check it, but normally it's always within EmuNAND (or SysNAND depending on which you're using). There's also an option in Atmosphère's Exosphere to enable/disable calls to SysNAND. Then it'd impossible for homebrew to use SysNAND (or they'd have to add many code, but you won't do that for a normal homebrew program without having malicious intentions)

 

[redsox786]

Hi All!

I currently have an Erista (unpatched) Switch and have been using SXOS, but would like to transition over to Atmosphere. The SysNAND is currently on version 6.2.0 and I previously had a EmuNAND on 11.0.0 running SX OS 3.1.0 using the SX Pro dongle.

The Switch has been wiped clean and factory reset and I'm trying to now figure out the easiest way to boot into Atmosphere. Can I use the SX Pro dongle to boot into Atmosphere? I don't care about going online and will only be using it for CFW. According to the Rentry guide, should I be following the "Set up Atmosphere with EmuNAND on Erista (SX Core)" section?

Any guidance would be appreciated!

 

[Choquette]

Hey all, I just recently updated Atmosphere to 1.1.1 and my emunand to software 13.0. When I start up now I get an error saying that my game cartridge slot cannot be read from. From what I understand this is because my emunand version is 13.0 but my stock system software is still on 11.0.1. In order to fix this, would it be as simple as removing the sd card, booting into the stock system and then updating my software through the nintendo servers? Or is there a work-around for this?

*EDIT*

As an aside to this, I originally was planning on never updating my system past 11.0.1 just in case a newer version removed functionality from running CFW, but I guess since my switch is unpatched it probably doesn't matter what software version I'm using right?

did you find the solution?

 

[Draxzelex]

Hey all, I just recently updated Atmosphere to 1.1.1 and my emunand to software 13.0. When I start up now I get an error saying that my game cartridge slot cannot be read from. From what I understand this is because my emunand version is 13.0 but my stock system software is still on 11.0.1. In order to fix this, would it be as simple as removing the sd card, booting into the stock system and then updating my software through the nintendo servers? Or is there a work-around for this?

*EDIT*

As an aside to this, I originally was planning on never updating my system past 11.0.1 just in case a newer version removed functionality from running CFW, but I guess since my switch is unpatched it probably doesn't matter what software version I'm using right?

Is this an error loading emuMMC or sysMMC?

I have a weird issue and have looked and looked for a solution to it, on cfw when after tinfoil is installed and shop added get new games and recommended on the side list after a .nsp install most games when launched fails to start software, thats not my issue the issue is when i reload Tinfoil it reverts back to the original version and the update i just did to tinfoil is gone same wirth the titles new games and recommended. I appreciate all the devs hard work and thank you for your time

I recommend using a better title installer such as TinWoo Installer

Has anyone tried using web browser emulators through the nintendo switch hidden web browser

Yes but its pretty bad.

Hi All!

I currently have an Erista (unpatched) Switch and have been using SXOS, but would like to transition over to Atmosphere. The SysNAND is currently on version 6.2.0 and I previously had a EmuNAND on 11.0.0 running SX OS 3.1.0 using the SX Pro dongle.

The Switch has been wiped clean and factory reset and I'm trying to now figure out the easiest way to boot into Atmosphere. Can I use the SX Pro dongle to boot into Atmosphere? I don't care about going online and will only be using it for CFW. According to the Rentry guide, should I be following the "Set up Atmosphere with EmuNAND on Erista (SX Core)" section?

Any guidance would be appreciated!

Yes, you can use the dongle to launch Atmosphere. You can do this by either chainloading fusee or Hekate from the SX OS menu or converting fusee/Hekate to boot.dat and placing it on your SD card. The only other thing you would need to do is put the Atmosphere CFW files on your SD card.