I have been trying for the last 48 hours to dump my nand and it fails everytime. I even removed my 3ds folder and replaced it with the 3ds folder in the file and it still fails. Its a downgraded n3ds on 9.2. The SD card was formatted to fat 32 before I downgraded.
Cool.
Graphics updated accordingly... Emunand9UI release is nearing! On the topic of graphics, which graphics actually AREN'T used by E9?
Obviously the menuXXXX images are, as are cancel, failed, done, logo, progress, unmount. Are the danger_s and danger_e images actually used at all? I only see one unlock sequence needed. So i guess only one image is needed for that, so we might need an update for E9 only in regards to that.
No, gw still does it the same way. I guess he just worded it wrong.
As for the other question, i have no idea tbh. I don't feel like wiping my sd card to try tbh. haha
Should be does, d0k3 is german so english probably isn't his first language (though he writes it really well). Anyways, if you need to have a way to backup/restore with the old PC tools that haven't been updated then you need the legacy option, but that wastes space (about 600 MB total)
EDIT: not sure on the second question, just test it out I guess
oh, so the "Complete Emunand Setup" doesn't use the GW format, then I guess that's why I coudn't use emunandTool with my cousin's 3ds, I had no trouble backing up the emuNAND.bin, but when injecting I got "Wrong NAND size". Nice updates, glad to see you keep going with your amazing tools.
Incorrectly downgraded NAND... I guess you have to update back and try again. Or wait until that downgrade thingie is stable enough.
The unlock gfx aren't used at all in the moment, cause these sequences are handled differently. Think we should build the gfx back in? Other than that, I'll check later for which graphics are used and which not.Cool.
On the topic of graphics, which graphics actually AREN'T used by E9?
Obviously the menuXXXX images are, as are cancel, failed, done, logo, progress, unmount. Are the danger_s and danger_e images actually used at all? I only see one unlock sequence needed. So i guess only one image is needed for that, so we might need an update for E9 only in regards to that.
No, gw still does it the same way. I guess he just worded it wrong.
As for the other question, i have no idea tbh. I don't feel like wiping my sd card to try tbh. haha
Well, that was past tense because you shouldn't use GW software to setup an EmuNAND anymore
. And no, GW will work fine even with the default option. EmuNAND Tool is the problematic one here. Nothing much that I can do here... n1ghty obviously doesn't want to release the EmuNAND Tool source and he has been absent from the forums for months. BTW, the legacy option wastes up to 800MB (same as GW does), but only for N3DSs with the 1.2GB NAND size.I can enable EmuNAND9 to automatically trim / pad NAND backups with the wrong size, no trouble. In fact there's already an issue open for that over on GitHub. The only reason why I haven't done that so far is that now NAND backups are also checked by their size, meaning more safety for the user, and with the automatic trimming / padding, that would be gone.
ooh so i can use the smaller nand partition with gw? and save 800mb? cool. oh, only save 809mb if n3ds, if old3ds there is no point?
what if i already have created emunand with gw... is it too late?
also, with this tool, incan have an emunand dumo and no emunand partition set up, and this will create the partiton and restore my dump to it?
i had a little trouble understanding it in the op sorry.
what if i already have created emunand with gw... is it too late?
also, with this tool, incan have an emunand dumo and no emunand partition set up, and this will create the partiton and restore my dump to it?
i had a little trouble understanding it in the op sorry.
I don't have a GW, but everything I know so far says the smaller EmuNAND partition won't mean trouble with GW. There are also N3DS consoles with 1.8GB NAND chips (mine has that), on these you'd only save ~200MB. With O3DS you'll save only very little, guess 60MB or something.
To resize the EmuNAND partition with EmuNAND9, you'll also need to format your SD card. So you'd need to backup everything first (your EmuNAND backup, too). But, yes, once you have done that and wrote everything back, you can just write back your EmuNAND backup and everything will be the same again. I suggest you first test with another SD card if GW complains about the EmuNAND size (unlikely), then proceed.
Last edited by d0k3,
Hello everyone.
@d0k3, I'm sorry but I have another question.
I will receive another, bigger µSD card tomorrow and I would like to know what are the steps to copy my actual emuNAND to the new SD card.
I think I will do it like this :
1 - Launch EmuNAND9 and backup my EmuNAND (as I injected BBM in the health software and updated it to 9.5 since the last first backup)
2 - Use the deconnect SD card option (didn't remember the real name of this function)
3 - Put my "old" SD card in my computer, retrieve the EmuNAND.bin and all other data
4- Put the new SD card in the console
5 - Use the "Complete emuNAND setup"
6 - Use the deconnect SD card option again
7 - Put the "new" SD card in my computer, and put the EmuNAND.bin and all other data on it
8 - Use the "EmuNAND restore from EmuNAND.bin" to get my EmuNAND back.
What do you think of this process ? Would it work ?
@d0k3, I'm sorry but I have another question.
I will receive another, bigger µSD card tomorrow and I would like to know what are the steps to copy my actual emuNAND to the new SD card.
I think I will do it like this :
1 - Launch EmuNAND9 and backup my EmuNAND (as I injected BBM in the health software and updated it to 9.5 since the last first backup)
2 - Use the deconnect SD card option (didn't remember the real name of this function)
3 - Put my "old" SD card in my computer, retrieve the EmuNAND.bin and all other data
4- Put the new SD card in the console
5 - Use the "Complete emuNAND setup"
6 - Use the deconnect SD card option again
7 - Put the "new" SD card in my computer, and put the EmuNAND.bin and all other data on it
8 - Use the "EmuNAND restore from EmuNAND.bin" to get my EmuNAND back.
What do you think of this process ? Would it work ?
Hello @d0k3!
Thank you for this great homebrew, however I have a couple of questions that I hope you can answer.
I have created an EmuNAND with your tool and I have set up a CFW into the default 4GB micro sd card.
I plan to buy a 64GB SDXC micro sd but it will come in exFAT, so should I format it first in FAT32 with external tools (guiformat...) or your EmunNAND9Tool already formats it to FAT32?
And what will be the best method for transfering all the content of the old to the new sd using your homebrew?
Thank you in advance for your help!
Thank you for this great homebrew, however I have a couple of questions that I hope you can answer.
I have created an EmuNAND with your tool and I have set up a CFW into the default 4GB micro sd card.
I plan to buy a 64GB SDXC micro sd but it will come in exFAT, so should I format it first in FAT32 with external tools (guiformat...) or your EmunNAND9Tool already formats it to FAT32?
And what will be the best method for transfering all the content of the old to the new sd using your homebrew?
Thank you in advance for your help!
Last edited by GKGC34,
That'll work just fine and is exactly what the "EmuNAND restore from EmuNAND.bin" option is designed for
Instead of step 5 you can just format your SD for EmuNAND (in the SD format options). Use the default / with EmuNAND option, starter pack is optional. Otehr than that it is fine.
For EmuNAND transfer, read above, SD contents -> good old fashioned copy somewhere on your PCs HD then back. EmuNAND9 formats in FAT32, but some stuff inside of there tries to access the file system, which may lead to problems with exFAT. Just format it in FAT32 before you use it.
i hope there will be a new version of emunandtool which support this partition size.
because back up n restore emunand are much faster on pc. and if i have to do it on 3ds, it actually requires more free space (a size of nand.bin) than that wasted space in gateway emunand.
because back up n restore emunand are much faster on pc. and if i have to do it on 3ds, it actually requires more free space (a size of nand.bin) than that wasted space in gateway emunand.
Don't ask to request, just request and d0k3 will decide if he'd like to do it or not@d0k3 Could I request a feature for EmuNand9tool
Similar threads
-
- Portal
