Hacking SWITCH NOOB PARADISE - Ask questions here

[Simbaatje]

I have updated a number of games on my Switch, and now it indicates that some files are corrupted. What can I do about it?? They won't start up after the update. The switch has not been updated.

 

[Draxzelex]

I have updated a number of games on my Switch, and now it indicates that some files are corrupted. What can I do about it?? They won't start up after the update. The switch has not been updated.

Try updating your patches by downloading the latest ones from this thread.

 

[Simbaatje]

I've already done that. With no result.

 

[Hayato213]

I've already done that. With no result.

SD card format?

 

[Simbaatje]

SD card format?

There are a number of games that stop working after updating such as Pokemon, Minecraft etc. I only updated these games, and after that they didn't work anymore. Then I downloaded the patches and put them on the sd card with no result.

 

[Draxzelex]

There are a number of games that stop working after updating such as Pokemon, Minecraft etc. I only updated these games, and after that they didn't work anymore. Then I downloaded the patches and put them on the sd card with no result.

No he meant how is your SD card formatted? Is it exFAT?

 

[Hayato213]

There are a number of games that stop working after updating such as Pokemon, Minecraft etc. I only updated these games, and after that they didn't work anymore. Then I downloaded the patches and put them on the sd card with no result.

I asked about the SD card format like exFAT or FAT32 etc

 

[Simbaatje]

I asked about the SD card format like exFAT or FAT32 etc

Sorry,

exFAT.

 

[Lamcza]

You mean I need to reformat the sd card? And then have to put all the files on it again.

dude he is asking you how is your sd card formated now exfat or fat32?

 

[Hayato213]

Sorry,

exFAT.

You should copy the files off the SD and reformat to FAT32. exFAT is the source of your file corruption.

 

[Simbaatje]

You should copy the files off the SD and reformat to FAT32. exFAT is the source of your file corruption.

Okay, thank you. I'm going to try that!

 

[Plermpel]

I can't get the bigger emuNAND to work, I don't quite get what is the problem, I resizesed a backup of my 4GB atmosphere emuNAND and then created a new one directly to the SD Card with NxNandManager.

The emuNand seems to boot somehow, if I try it, I get the atmosphere logo, then the Nintendo logo, and after that, this error:

Now some things I found out yet:

1.) The original emuNAND from Hekate has unused sectors in front of it, the NxNandManager created one starts at 0x00000000
I can not set the starting point of the partition to 0 in the emummc.ini, because for hekate "0" means the emuNand is a file and not a partition.

2.) The original emuNAND from Hekate is on a RAW partition, the NxNandManager created one is on a hidden partition, which can't be read by Hekates partition tool or anything else but there is still data on it, since I can mount the Nand with hekates USB tools.

3.) The original emuNAND from Hekate shows 0 Bytes free space in NxNandManager on the USER partition, while the newly created one shows the same number "free" as "availiable"


Is there anybody yet, that achieved a bigger emuNand?

 

[binkinator]

I can't get the bigger emuNAND to work, I don't quite get what is the problem, I resizesed a backup of my 4GB atmosphere emuNAND and then created a new one directly to the SD Card with NxNandManager.

The emuNand seems to boot somehow, if I try it, I get the atmosphere logo, then the Nintendo logo, and after that, this error:

View attachment 342055


Now some things I found out yet:

1.) The original emuNAND from Hekate has unused sectors in front of it, the NxNandManager created one starts at 0x00000000
I can not set the starting point of the partition to 0 in the emummc.ini, because for hekate "0" means the emuNand is a file and not a partition.

2.) The original emuNAND from Hekate is on a RAW partition, the NxNandManager created one is on a hidden partition, which can't be read by Hekates partition tool or anything else but there is still data on it, since I can mount the Nand with hekates USB tools.

3.) The original emuNAND from Hekate shows 0 Bytes free space in NxNandManager on the USER partition, while the newly created one shows the same number "free" as "availiable"


Is there anybody yet, that achieved a bigger emuNand?

Try following this: https://rentry.org/EmuNANDNewSDcard

I prefer the Hekate method. Any of the three will work.

 

[Lamcza]

Try following this: https://rentry.org/EmuNANDNewSDcard

I prefer the Hekate method. Any of the three will work.

I think that nx method needs to be tweaked at point 19 because it also creates a folder "emutendo" and you need to either copy the files from your "nintendo" folder to it or rename it to Nintendo insted of Emutendo and when you are doing it you can just rename that ER00 to Raw1 in emummc/emummc.ini because why not.

There is a chance that i mess up and emutendo is some kind of my mistake ;d

I can't get the bigger emuNAND to work, I don't quite get what is the problem, I resizesed a backup of my 4GB atmosphere emuNAND and then created a new one directly to the SD Card with NxNandManager.

The emuNand seems to boot somehow, if I try it, I get the atmosphere logo, then the Nintendo logo, and after that, this error:

View attachment 342055


Now some things I found out yet:

1.) The original emuNAND from Hekate has unused sectors in front of it, the NxNandManager created one starts at 0x00000000
I can not set the starting point of the partition to 0 in the emummc.ini, because for hekate "0" means the emuNand is a file and not a partition.

2.) The original emuNAND from Hekate is on a RAW partition, the NxNandManager created one is on a hidden partition, which can't be read by Hekates partition tool or anything else but there is still data on it, since I can mount the Nand with hekates USB tools.

3.) The original emuNAND from Hekate shows 0 Bytes free space in NxNandManager on the USER partition, while the newly created one shows the same number "free" as "availiable"


Is there anybody yet, that achieved a bigger emuNand?

I have a feeling that you overide some files from emummc point 18

after nx is done with creating the partition you need to copy files from emummc point 18 but not override it.
Then check if you have that ER00 folder or just RAW1 inside of emummc point 19

 

[Plermpel]

I prefer the Hekate method. Any of the three will work.

How should I do that with hekate it only makes emuMMCs with the same sice as the original one or smaller.
Do you maybe know what files I need to use EmuTool, so I could try to create the Nand with Nx and then load it on the SD Card with EmuTool, because it looks like this allows me to manually set the starting sector for the partition.

I think that nx method needs to be tweaked at point 19 because it also creates a folder "emutendo" and you need to either copy the files from your "nintendo" folder to it or rename it to Nintendo insted of Emutendo and when you are doing it you can just rename that ER00 to Raw1 in emummc/emummc.ini because why not.

There is a chance that i mess up and emutendo is some kind of my mistake ;d



I have a feeling that you overide some files from emummc point 18

after nx is done with creating the partition you need to copy files from emummc point 18 but not override it.
Then check if you have that ER00 folder or just RAW1 inside of emummc point 19

You are right, it does that, but I allready tried to rename everything to the normal things hekate creates, I also can't see why that should be a problem.

Can you explain that further? What files do I need to copy, from where, I just leave everything as it is after Nx is done.

 

[Lamcza]

How should I do that with hekate it only makes emuMMCs with the same sice as the original one or smaller.
Do you maybe know what files I need to use EmuTool, so I could try to create the Nand with Nx and then load it on the SD Card with EmuTool, because it looks like this allows me to manually set the starting sector for the partition.



You are right, it does that, but I allready tried to rename everything to the normal things hekate creates, I also can't see why that should be a problem.

Can you explain that further? What files do I need to copy, from where, I just leave everything as it is after Nx is done.

On moving your files from old sd or your backup folder (point 18) I think the place where you can quck up is to override emuMMC/RAW1/raw-based (when NX crates ER00 instead of RAW1)
At least i think this was my error source.

below something unnecessary

At the end just copy folder "emutendo" from the main directory to somewhere else on your pc just to be safe and delete it from sd xD than go to emuMMC folder and inside rename folder ER00 to RAW1 next edit emummc.ini and change every ER00 to RAW1

 

[binkinator]

How should I do that with hekate it only makes emuMMCs with the same sice as the original one or smaller.
Do you maybe know what files I need to use EmuTool, so I could try to create the Nand with Nx and then load it on the SD Card with EmuTool, because it looks like this allows me to manually set the starting sector for the partition.

@mikefor20 has a doc for doing dual emunand on one SDCard. In the middle there is a section on shrinking partitions. The entire doc is fantastic so you should read it in context but here’s the pertinent bit:

Spoiler: Shrinkage

OPTIONAL: Shrink SXOS EmuNAND

If you shrink your EmuNAND make sure you backup all saves first! Back them saves up even if you don't shrink the EmuNAND

If you would like to shrink your SXOS EmuNAND now is the time. This will make all installed NSP stop working. You can reinstall but it won't hold much. The intent is to make SXOS's impact minimal. I make SuperXCI (XCI files that contain all updates and DLC for the game) I convert NSP files and make Super XCIs out of them as well. This way Everything for SXOS compatible games is on the HDD. Except a Small EmuNAND.

You can select whatever USER data size you want. I only intend to have SAVE data on this EmuNAND so 8GB is enough for me. I play all NSP off of my SD in Atmosphere. SXOS is just for XCI USB loading.


In NxNandManager

1. Select File>Open File and select your EmuNAND raw backup.
2. Select Options > Resize EmuNAND
3. Check Format User (this is optional, however this process will render the current USER data useless anyway so just format it to make it clean, Input file will not be altered)
4. Select New Size.. I went with 5504 MB for user partition (8 GB Total) to keep enough room for saves.. some games have fairly large save files, you can choose whatever you want,
5. Click Save As,, name the file whatever you want and choose the working directory. I call mine SXOSemuRESIZED
6. Click Save.

https://gbatemp.net/threads/how-to-...en-partitions-on-the-same-sd-tutorial.601607/

 

[bassgs333]

Hi, just got homebrew working on a friends switch for him. The idea is to eventually give it back soon. Is there a way to dump and upload save data from a different profile? Since his account is bound to the hacked switch it only ever shows that even if I put my nintendo folder on the SD card.

 

[binkinator]

Hi, just got homebrew working on a friends switch for him. The idea is to eventually give it back soon. Is there a way to dump and upload save data from a different profile? Since his account is bound to the hacked switch it only ever shows that even if I put my nintendo folder on the SD card.

Game saves are in the Emunand (or Sysnand, if you didn’t make an Emunand you filthy savage.)

Here’s a tut for how to manipulate your game saves with JKSV and NXNandManager:

https://gbatemp.net/threads/recovering-games-saves-from-nand-using-nxnandmanager-and-jksv.620758/

 

[bassgs333]

Game saves are in the Emunand (or Sysnand, if you didn’t make an Emunand you filthy savage.)

Here’s a tut for how to manipulate your game saves with JKSV and NXNandManager:

*link*

Well the reason why I ask is my switch isn't hackable and would like to modify my personal game save. Will this let me modify saves across profiles.