Hacking SWITCH NOOB PARADISE - Ask questions here

[Smoker1]

Where did you put BCT.ini?

default, it is in Atmosphere\config_templates

 

[Lacius]

default, it is in Atmosphere\config_templates

That's the templates folder. Nothing is read there. You need to move it to config.

 

[Smoker1]

That's the templates folder. Nothing is read there. You need to move it to config.

Should I put the System Settings, Override Config Files in it as well?

 

[Lacius]

Should I put the System Settings, Override Config Files in it as well?

As it pertains to your game cartridge slot, no.

 

[Smoker1]

As it pertains to your game cartridge slot, no.

No, I mean in the Config Folder

 

[Lacius]

No, I mean in the Config Folder

If you want to update your game cartridge slot (without booting OFW just one time), the only thing you need to put into the config folder is your altered BCT.ini file.

I don't know what you're asking.

 

[Smoker1]

If you want to update your game cartridge slot (without booting OFW just one time), the only thing you need to put into the config folder is your altered BCT.ini file.

I don't know what you're asking.

In Config_Templates, there are 4 Files for a fresh Atmosphere Folder.
BCT.ini
exosphere.ini
override_config.ini
and system_settings.ini

Should I place all 4 Files in the "Atmosphere\config" Directory? Or do I just need the BCT?

 

[Lacius]

In Config_Templates, there are 4 Files for a fresh Atmosphere Folder.
BCT.ini
exosphere.ini
override_config.ini
and system_settings.ini

Should I place all 4 Files in the "Atmosphere\config" Directory? Or do I just need the BCT?

Forgive my impatience, but as I've said three times now, you only need to move the BCT.ini file into the config folder.

 

[Windsall]

Yes, you aren't understanding emuNAND or it's purpose. emuNAND pretends to be the internal storage of the switch. A switch, like let's say mine. It has 32gb of internal storage and 128gb sdcard. The sysNAND uses the 32gb of internal storage, but when I'm booted up in emuNAND mode it looks at a specific 32gb section of the sdcard and is tricked into thinking that 32gb of sdcard memory is in fact internal storage. So, you aren't just limited to putting save game data there. When you install a game to the internal storage while running emuNAND you're actually installing the game inside that 32gb of reserved space.

In essence, the emuNAND isn't really "wasting" any storage at all.

Also to clarify, no, emuNAND cannot "just read from internal storage" as you suggest. When you are running booted up as emuNAND the internal storage of your switch is not touched at all. That's why people are sure you cannot be banned for actions you take offline in emuNAND, they literally do not effect anything inside the internal storage of the switch.

To be clear.

If you are starting with an 128gb empty sdcard and you think that's enough storage, using emuNAND shouldn't really change your opinion at all on if the size is right for you. Wanting to use emuNAND isn't really a reason to need a bigger sdcard (although you will need one bigger than 32gb, which yours already is). Wanting a large library of pirated games to be available at all times? That's a good reason to want a bigger sdcard. You might as well use what you have though, it's plenty big enough, and in a few months if it's too small you can always migrate/upgrade to a larger sdcard. As I said before, you can't simply copy/paste an emuNAND to a new sdcard but hekate does have an option to migrate to a new sdcard. And the files other than the emuNAND can be copy/pasted.

Thank you that was very clear, I appreciate it.

I'll use my 128gb card for now since if I can install to the fake internal memory portion then it should be enough to have a good array at one time. I do think I might want more (with bigger sized card), but there's no rush. So long as it's not hard to navigate a large amount from over 300gb of installed nsp files lol. (if I can create folders I'm guessing it should be fine)

When someone migrates it to a new card, does it partition it and everything like before, or do I need to go through some of the process for that? Just wondering because I may get that new card next month.

 

[Windsall]

I have a question about sigpatches, because I saw a bit of discussion around it and there's some things I'm not sure about.

If I follow the main guide for modding, which uses atmosphere, when it's time to update the sigpatches, is it only about replacing the atmosphere files, or does hekate and the other patch there need to replace as well?

And is it only where there's a new version of these? I don't know if or when hekate gets updated, and how it works for the sigpatches compared to atmosphere.

 

[Smoker1]

anyone have another method if installing Homebrew or MTP via USB? nxmtp no longer works. Get that 0100000000001000 Error, even though there is no Folder of it anywhere on the SD Card

 

[laz305]

anyone have another method if installing Homebrew or MTP via USB? nxmtp no longer works. Get that 0100000000001000 Error, even though there is no Folder of it anywhere on the SD Card

gotta use Hekate now, until they update nxmtp. Hopefully they will

 

[Smoker1]

gotta use Hekate now, until they update nxmtp. Hopefully they will

Hekate has a MTP function?

 

[NANASHI89]

So, I hear SX OS was cracked.

Anyone got it working on the latest FW?

 

[Lacius]

So, I hear SX OS was cracked.

Anyone got it working on the latest FW?

The license was cracked, but SX OS is still closed-source, and there is no version of it that works on anything higher than 11.0.0. My guess is there probably never will be.

 

[Draxzelex]

I have a question about sigpatches, because I saw a bit of discussion around it and there's some things I'm not sure about.

If I follow the main guide for modding, which uses atmosphere, when it's time to update the sigpatches, is it only about replacing the atmosphere files, or does hekate and the other patch there need to replace as well?

And is it only where there's a new version of these? I don't know if or when hekate gets updated, and how it works for the sigpatches compared to atmosphere.

If you are using fusee_primary to launch Atmosphere, you only have to update the fusee patches. If you are using Hekate instead, then you have to update those patches. Patches have to be updated whenever you update your firmware and/or version of Atmosphere regardless of which patches you use.

Hekate has a MTP function?

It does, it can be found under Tools.

 

[Windsall]

If you are using fusee_primary to launch Atmosphere, you only have to update the fusee patches. If you are using Hekate instead, then you have to update those patches. Patches have to be updated whenever you update your firmware and/or version of Atmosphere regardless of which patches you use.
It does, it can be found under Tools.

Got it, thanks.
Is there a big difference in what someone uses to boot atmosphere? I know the guide makes it that I'll have both fusee and hekate, though I'm not sure about the 'primary' aspect.

As soon as I get the jig and usb I ordered, that's when I can think more about actually getting to the modding

 

[Draxzelex]

Got it, thanks.
Is there a big difference in what someone uses to boot atmosphere? I know the guide makes it that I'll have both fusee and hekate, though I'm not sure about the 'primary' aspect.

As soon as I get the jig and usb I ordered, that's when I can think more about actually getting to the modding

Both fusee_primary and Hekate use fusee_secondary to launch Atmosphere. That is one of the differences; you use a different payload to launch Atmosphere whether its fusee_primary or Hekate. Another difference is that Hekate or fss0 launches Atmosphere faster than fusee_primary. Also Hekate/fss0 can launch multiple emuMMC with one configuration or even sysMMC with CFW while fusee_primary can only launch emuMMC or sysMMC with CFW by default, limiting its options. Lastly, nogc is handled differently; fusee_primary reads the BCT.ini file while Hekate can be managed from Hekate itself. Objectively speaking, Hekate/fss0 is superior to fusee_primary but for one reason or another, some people prefer to use fusee_primary.

 

[namad]

Thank you that was very clear, I appreciate it.

I'll use my 128gb card for now since if I can install to the fake internal memory portion then it should be enough to have a good array at one time. I do think I might want more (with bigger sized card), but there's no rush. So long as it's not hard to navigate a large amount from over 300gb of installed nsp files lol. (if I can create folders I'm guessing it should be fine)

When someone migrates it to a new card, does it partition it and everything like before, or do I need to go through some of the process for that? Just wondering because I may get that new card next month.

The migration process is very easy as long as you have a computer you can use with plenty of storage space to hold the data on temporarily. The migration from one sdcard to another isn't significantly more complicated than installing an emuNAND for the first time. Hekate does it, there's options, you pick the right ones. However you will need a special program for your computer to format sdcards. At least to follow the recommended guideline. Microsoft doesn't think sdcard's above 32gb should be formatted in FAT32 but nintendo does. So you'll want to prepare an sdcard by formatting it in FAT32 rather than exfat, which will require a 3rd party formatting tool on your computer, but most guides reference said tool. At least that's how I've always done it, and how I've always read guides. In theory exfat should work fine, but why bother with "should work fine".

When creating an emuNAND either a new one or a migrated one, yes hekate will create a new partition on the sdcard. Hopefully that clarifies the matter.

You don't need to read the stuff below here, unless you buy a 2nd sdcard in a distant future month and want to migrate your emuNAND from the current smaller one to the future larger one.

This looks reasonably up to date: https://nh-server.github.io/switch-guide/extras/transfer_sd/ which also references https://switchgui.de/switch-guide/user_guide/emummc/partitioning_sd/

Essentially it's almost as easy as copy/pasting the files. Because it's as easy as copy/pasting the files, knowing how to tell hekate to create the correct partition and knowing how to tell hekate to use a backup rather than starting fresh.

 

[Windsall]

The migration process is very easy as long as you have a computer you can use with plenty of storage space to hold the data on temporarily. The migration from one sdcard to another isn't significantly more complicated than installing an emuNAND for the first time. Hekate does it, there's options, you pick the right ones. However you will need a special program for your computer to format sdcards. At least to follow the recommended guideline. Microsoft doesn't think sdcard's above 32gb should be formatted in FAT32 but nintendo does. So you'll want to prepare an sdcard by formatting it in FAT32 rather than exfat, which will require a 3rd party formatting tool on your computer, but most guides reference said tool. At least that's how I've always done it, and how I've always read guides. In theory exfat should work fine, but why bother with "should work fine".

When creating an emuNAND either a new one or a migrated one, yes hekate will create a new partition on the sdcard. Hopefully that clarifies the matter.

You don't need to read the stuff below here, unless you buy a 2nd sdcard in a distant future month and want to migrate your emuNAND from the current smaller one to the future larger one.

This looks reasonably up to date: https://nh-server.github.io/switch-guide/extras/transfer_sd/ which also references https://switchgui.de/switch-guide/user_guide/emummc/partitioning_sd/

Essentially it's almost as easy as copy/pasting the files. Because it's as easy as copy/pasting the files, knowing how to tell hekate to create the correct partition and knowing how to tell hekate to use a backup rather than starting fresh.

Thanks I'm sure that will help a lot.

I think I'm done with questions for now xD. Until I get everything to mod, and then we'll see what comes up
I appreciate everyone's time.