Hacking SWITCH NOOB PARADISE - Ask questions here

[BigOnYa]

I found the cheats online with the TID and build ID! So I’ve been naming them wrong? Thought the title id has to be the file name? IE 0100F7E00C70E000, so where do I put the TID number?

TitleID/"cheats"/text file named BuildID
Example:
2980E59C32A0E147(folder name)/ cheats(folder name)/ 550F2E8B387B4520(text file name)

 

[TudorBlue]

TitleID/"cheats"/text file named BuildID
Example:
2980E59C32A0E147(folder name)/ cheats(folder name)/ 550F2E8B387B4520(text file name)

So I’ve got the name of the folder and file name mixed up?

 

[BigOnYa]

So I’ve got the name of the folder and file name mixed up?

I don't know what you did, just telling you how it should be.

 

[TudorBlue]

TitleID/"cheats"/text file named BuildID
Example:
2980E59C32A0E147(folder name)/ cheats(folder name)/ 550F2E8B387B4520(text file name)

Booooommm working like a treat

 

[shoawnestswager]

Hello! While making my emummc with hekate, I realized that i made a really stupid choice and started making it while on like eighteen percent battery. Fast forward a little bit, my switch dies. Will this mess with the switch, or should I just boot up hekate, partition the SD again, and create another emummc? (btw i am not a first time modder, im just new to switch modding)

 

[lightautodark]

Hello! While making my emummc with hekate, I realized that i made a really stupid choice and started making it while on like eighteen percent battery. Fast forward a little bit, my switch dies. Will this mess with the switch, or should I just boot up hekate, partition the SD again, and create another emummc? (btw i am not a first time modder, im just new to switch modding)

As long as the emmc setup has been completed, there shouldn't be any problem? can you launch cfw of Emunand ?

 

[shoawnestswager]

Sadly, no. It was around 70% done when the switch's battery ran out, and I'm afraid smth may happen when I try and launch the emummc. ill see if emummc can boot tho

UPDATE: my switch boots into hekate fine but isn't able to boot emummc. It displays the error message:

Error while loading fss0:
atmosphere/package3
wrong ini cfg or missing / corrupt files!
Failed to launch HOS!

I haven't put any atmosphere folders or anything onto the SD yet, im just making sure its ok to partition the SD again and/or create a new emummc. Thanks!

 

[dragonz]

Yes DLC can be exported from a NAND e imported on the other

Would you please let me know how? I was wondering, has anyone tried using a file manager like Goldleaf to navigate to the DLC data on SysNAND? I believe the DLC is typically found in the Nintendo/contents folder, associated with the specific game ID. Has this method worked for anyone?

 

[impeeza]

Would you please let me know how? I was wondering, has anyone tried using a file manager like Goldleaf to navigate to the DLC data on SysNAND? I believe the DLC is typically found in the Nintendo/contents folder, associated with the specific game ID. Has this method worked for anyone?

you can use DBI to export the installed content and also for install the dump.

There is an hombrew called NXDumpTool https://github.com/DarkMatterCore/nxdumptool/

But I recommend DBI.

 

[shoawnestswager]

Sadly, no. It was around 70% done when the switch's battery ran out, and I'm afraid smth may happen when I try and launch the emummc. ill see if emummc can boot tho

UPDATE: my switch boots into hekate fine but isn't able to boot emummc. It displays the error message:

Error while loading fss0:
atmosphere/package3
wrong ini cfg or missing / corrupt files!
Failed to launch HOS!

I haven't put any atmosphere folders or anything onto the SD yet, im just making sure its ok to partition the SD again and/or create a new emummc. Thanks!

DISREGARD: this was solved by just reinjecting the hekate payload and just partitioning the SD card + setting up emummc again. Now, emummc boots and works just fine!

 

[Oriordan]

Hello
I have a switch on fw 18.1.0 without exfat driver, i don't want to update to 19.0.0
Is there a way to install the driver manually ? (safe and not too complicated)

 

[Hayato213]

Hello
I have a switch on fw 18.1.0 without exfat driver, i don't want to update to 19.0.0
Is there a way to install the driver manually ? (safe and not too complicated)

You don't need exFAT.

 

[Oriordan]

You don't need exFAT.

I put a 256 gb sd card, it asked to update the console, i don't want to format the sd card with fat32

 

[Hayato213]

I put a 256 gb sd card, it asked to update the console, i don't want to format the sd card with fat32

You can reflash 18.1.0 with daybreak if you have CFW, but there is no perk of using exFAT when everything can be done on FAT32, even unmodded switch I have is on FAT32.

 

[kidkat210]

I put a 256 gb sd card, it asked to update the console, i don't want to format the sd card with fat32

Fat32 is strongly recommended since the exfat driver is prone to corruption with cfw. Even without cfw it happens

 

[Oriordan]

Fat32 is strongly recommended since the exfat driver is prone to corruption with cfw. Even without cfw it happens

Ok
Thank you
I will format it to fat32 for the moment

 

[dragonz]

Hi , I need help,
I created game-forwarding icons for melonDS and designed two title images for them, allowing me to launch both games. However, I'm encountering an issue where the melonds.ini file is affecting the settings for both games. I want separate screen settings for each ROM, but the last game I launch overrides the settings for the other.

I renamed the melonDS.nro for the first game to melonds1.nro and the second to melonds2.nro, and I created separate folders for each. Despite this, the melonds.ini still controls the settings for both games. Do you have any ideas on why this is happening?

 

[MikeyTaylorGaming]

Just a quick question - Is the latest atmosphere backwards compatible with older firmware? I'm currently on FW16.0.3 and AMS 1.5.4, but I'd like to update Atmosphere to 1.7.1 first, then install FW 18.1.0.

That way, when I install the firmware I know that Atmosphere will be ready to use without having to troubleshoot!

Also wondering if older versions of DBI work with 18.1.0 update, I've been using DBI V569 for the longest time, but the latest version in English is V658 and the latest overall which is Russian only is 707. Don't know if I'll have problems with the older V's but though I'd ask!

EDIT- I put AMS1.7.1 onto my SD and it does in fact work with older firmware, however, I tried to load the Homebrew Menu by holding R and opening Super Bomberman R, and it came up with a message stating that data is corrupted? Is this because I've not updated to the latest Switch FW yet? It's just checked through the corrupted data and stated that 'the micro SD card data is corrupted' which I don't think is the case. Any advice?

Thanks all

 

[Blythe93]

Is the latest atmosphere backwards compatible with older firmware?

Yep. Latest Atmosphere 1.7.1 supports all firmware revisions up to 18.1.0, meaning you can use newer Atmosphere with an older firmware.

Also wondering if older versions of DBI work with 18.1.0 update, I've been using DBI V569 for the longest time, but the latest version in English is V658 and the latest overall which is Russian only is 707. Don't know if I'll have problems with the older V's but though I'd ask!

To be honest, if the only thing you're using DBI for is installing games, I think you'll be fine with the DBI 658. I do suggest that you check out the latest Russian-only version and install the games through it just to be on a safe side. It's not hard to figure out which options to select once you get used to DBI 658.

however, I tried to load the Homebrew Menu by holding R and opening Super Bomberman R, and it came up with a message stating that data is corrupted? Is this because I've not updated to the latest Switch FW yet? It's just checked through the corrupted data and stated that 'the micro SD card data is corrupted' which I don't think is the case. Any advice?

Did you try opening it with another game? Make sure that you update sigpatches or sys-patch (recommended). I usually open homebrew menu in applet mode so I'm not sure what may be the issue other than maybe a faulty SD card (maybe formatted to exFAT as well?), faulty game install or outdated sigpatches.

 

[MikeyTaylorGaming]

Yep. Latest Atmosphere 1.7.1 supports all firmware revisions up to 18.1.0, meaning you can use newer Atmosphere with an older firmware.


To be honest, if the only thing you're using DBI for is installing games, I think you'll be fine with the DBI 658. I do suggest that you check out the latest Russian-only version and install the games through it just to be on a safe side. It's not hard to figure out which options to select once you get used to DBI 658.


Did you try opening it with another game? Make sure that you update sigpatches or sys-patch (recommended). I usually open homebrew menu in applet mode so I'm not sure what may be the issue other than maybe a faulty SD card (maybe formatted to exFAT as well?), faulty game install or outdated sigpatches.

Thanks for your quick response, I've not tried any other games yet nor have I tried to update the console to 18.1.0 yet. I've not tried booting another game yet as I really don't want to corrupt another one ahaha. I did install the new sigpatches in all folders, though I just copy pasted and replaced them rather delete all and put them in their respective location.

Another thing, I've just used DBI to install Mario Party Jamboree and it gives me these messages;
[TRANSFER OK] [SIGNATURE: Invalid]
[TRANSFER OK] [SIGNATURE: XCI => NSP]
[TRANSFER OK] [SIGNATURE: XCI => NSP]
[TRANSFER OK] [SIGNATURE: Invalid]

Perhaps this means that the sigpatches aren't correct?