Hacking emuNAND Tool - Release and Support thread

  • Thread starter Thread starter n1ghty
  • Start date Start date
  • Views Views 466,845
  • Replies Replies 580
  • Likes Likes 83
You can transfer the sysnand to emunand After separating the nand? Obviously with the backup of files (Nintendo 3DS Folder) and the original nand (NAND.bin)
 
I know I have errors all over with all but 1.01. That will let me extract and inject fine for 2 old 2ds.
I tried with a N3DS but it seems it doesnt like the bigger size.
So I'll have to use emunand9, which I'd rather not as via pc is 2-3x faster.
 
So I just switched to a 128 gig MicroSD and got all my stuff over but EmuNANDTool can no longer extract my EmuNAND. Says no SD with EmuNAND Found. Any ideas?
 
So I just switched to a 128 gig MicroSD and got all my stuff over but EmuNANDTool can no longer extract my EmuNAND. Says no SD with EmuNAND Found. Any ideas?
So, to get it straight on your NEW 128 gig SD, you have emuNAND set up and it won't extract it? How exactly was emuNAND set up on this (128 gig) card initially, with emuNAND9 or by transferring the old emuNAND to the new card from an image of the old card?
 
So, to get it straight on your NEW 128 gig SD, you have emuNAND set up and it won't extract it? How exactly was emuNAND set up on this (128 gig) card initially, with emuNAND9 or by transferring the old emuNAND to the new card from an image of the old card?
I used Win32DiskImager to make an exact copy of the entire SD and it's partitions, then I restored it and used the EaseUS Partition Manager to extend the normal partition so I could use my new space. As described in this guide.

It was initially set up on the old card using Gateway.
 
I used Win32DiskImager to make an exact copy of the entire SD and it's partitions, then I restored it and used the EaseUS Partition Manager to extend the normal partition so I could use my new space. As described in this guide.
OK, that might be a problem (though emuNAND9 SHOULD be able to handle it, apparently it can't... @d0k3 you should check into this) in the meantime, if you have the old card and haven't erased it, copy your emuNAND off (by making an emuNAND.bin out of it with emuNAND9) of the old card, format the new card, do a "complete emuNAND setup" from emuNAND9 on the new card, once that's done transfer the emuNAND.bin to the new card and restore it, then copy the files from the old SD card onto the new one... that should get you up and running :)
 
Last edited by dark_samus3,
OK, that might be a problem (though emuNAND9 SHOULD be able to handle it apparently it can't @d0k3 you should check into this) in the meantime, if you have the old card and haven't erased it, copy your emuNAND off (by making an emuNAND.bin out of it with emuNAND9) of the old card, format the new card, do a "complete emuNAND setup" from emuNAND9 on the new card, once that's done transfer the emuNAND.bin to the new card and restore it, then copy the files from the old SD card onto the new one... that should get you up and running :)
Does it matter if the partition table is GPT or MBR?
 
Does it matter if the partition table is GPT or MBR?
EmuNAND (in general, that doesn't only apply to EmuNAND9) will work only with an MBR boot record. You can try with EmuNAND9 or Decrypt9, but Multi EmuNAND Creator might do the job as well. In general, Multi EmuNAND Creator should be prefered over EmuNAND tool now, cause EmuNAND tool's development has apparently been given up and there are several incompatibilities now.
 
  • Like
Reactions: Shadowfied
EmuNAND (in general, that doesn't only apply to EmuNAND9) will work only with an MBR boot record. You can try with EmuNAND9 or Decrypt9, but Multi EmuNAND Creator might do the job as well. In general, Multi EmuNAND Creator should be prefered over EmuNAND tool now, cause EmuNAND tool's development has apparently been given up and there are several incompatibilities now.
Thank you!
 

Site & Scene News

Popular threads in this forum