Mine is New3DS tooMine is 1.8GB (new3DS user here). If you have an o3DS, I think that's normal.
Mine is New3DS tooMine is 1.8GB (new3DS user here). If you have an o3DS, I think that's normal.
Mine is New3DS too
Yes, there are two types of emmc chipsI heard that the NAND size depends on n3DS. Some are 1.2GB, some are 1.8GB.
I can't restore my EmuNAND, it says that the dump is not valid... However it has the same size than my older EmuNAND backups so I think it is valid... Is it a problem with the EmuNAND check feature of EmuNAND9Tool ?
Decrypt9 says the file is too small, but it's not.
EDIT : Was able to restore the dump as regular EmuNAND using MultiEmuNAND Tool, so the dump is definitely valid.
Try the Decrypt9 test build:Conversion should work, but it takes the same size than GW EmuNAND...
It's just that the EmuNAND restoration feature is obviously broken, so I though I should report it.
That is because the size can't be further reduced with that small NAND chip of yours. 1.21GB is the minimum size.The size of my regular EmuNAND partition is 1.21GB.
It's strange that even I did it by the following tips, the size of EmuNAND partitaion is still 1.21GB.
Format SD... For EmuNAND (min size)
Try the Decrypt9 test build:
http://workupload.com/file/fq3VOYee
Also, why did you not try restoring that EmuNAND with EmuNAND9 tool?
That is because the size can't be further reduced with that small NAND chip of yours. 1.21GB is the minimum size.
@everyone, the EmuNAND9 readme is updated and should answer basically all of your questions.
Well, then you were lucky, as that file is missing data almost 100%. What console type do you have and what is the exact size of that NAND backup?Sorry, I wasn't clear. EmuNAND9Tool says the NAND file is not valid, and Decrypt9 says it's too small. Both are broken.
I was able to restore it using Multi EmuNAND Tool (on Windows), it works perfectly well.
Well, then you were lucky, as that file is missing data almost 100%. What console type do you have and what is the exact size of that NAND backup?
That size looks good. What is your console type, N3DS? And could you restore the two previous ones? You should retry with a recent D9 test version or most recent EmuNAND9.Sorry, I didn't understood. Which file is missing which data ?
My dump's size is 1 300 234 240 bytes, just like the two other previous dumps I made. They're all working fine.
That size looks good. What is your console type, N3DS? And could you restore the two previous ones? You should retry with a recent D9 test version or most recent EmuNAND9.
Ah, okay, then I can look into it. Newest D9 test build is here, btw: http://workupload.com/file/oPxXBmn6Yep, regular black N3DS XL.
The previous ones were OK, but that was on EmuNAND, not RedNAND. I used the latest version of both Decrypt9 and EmuNAND9.
I did the thing you said in your mini-guide : backup NAND, backup SD, format it using EmuNAND9 (minsize to have a RedNAND) then tried to restore it (first with EmuNAND9, then with Decrypt9, both failed).
EDIT : Don't know if that matters, but both were booted using A9LH.
Ah, okay, then I can look into it. Newest D9 test build is here, btw: http://workupload.com/file/oPxXBmn6
Nope, wait for a bit. The error message you got (in EmuNAND9) was: "Not a proper NAND dump!", right? Can you perhaps show me the first 512 byte of your NAND backup? I absolutely don't need the full thing, just these 512 byte. EDIT: you can use HxD for this, for example.Thanks. Should I retry formatting my SD with RedNAND before using it ?
Nope, wait for a bit. The error message you got (in EmuNAND9) was: "Not a proper NAND dump!", right? Can you perhaps show me the first 512 byte of your NAND backup? I absolutely don't need the full thing, just these 512 byte. EDIT: you can use HxD for this, for example.
Okay, thanks! This was a good catch, and it is fixed now. It should work now in both D9 and E9.Yes, I got this exact message.
Sure, here you go : https://mega.nz/#!GVhADDxJ!Q6QTaknb5Xx4dTwDayyHLDW187v0mACIHN5pUwynxrU
Okay, thanks! This was a good catch, and it is fixed now. It should work now in both D9 and E9.
Everyone else, check my GitHub for the new release!
If you can, also try the restore on the D9 test build - that needs testing more than E9 right now.Thanks, amazing work as always. I'll retry to setup RedNAND
If you can, also try the restore on the D9 test build - that needs testing more than E9 right now.
Just the standard restore option. Not 'forced', not 'keep A9LH'. You need to set up the RedNAND first in EmuNAND9 (via either 'Complete RedNAND Setup' or via 'Restore Backup' after the minsize formatting) for this to work in D9.No problem, but what should I use ? There's a lot of options to backup/restore.
I have right now a GW EmuNAND and want to switch to RedNAND.
Just the standard restore option. Not 'forced', not 'keep A9LH'. You need to set up the RedNAND first in EmuNAND9 (via either 'Complete RedNAND Setup' or via 'Restore Backup' after the minsize formatting) for this to work in D9.
The indicator is already in there (bottom of the menu). I'll think about adding information about the size, too. And feature request are okay on both. Thanks for testing!Okay, I'm doing this right now.
Oh, and one last thing : do you prefer feature requests here or on GitHub ? I though that an "indicator" to see on what nand type we are could be useful on EmuNAND9Tool (EmuNAND/RedNAND Full Size/RedNAND Min Size).