Hacking Does emunand tool only support smaller emunand partitions?

[crimpshrine]

I have used emunand tool to backup my emunand partitions on all my 3ds units without issue. (all of those are usually 1 Gig emunand)

Today I tried using it on a Hyrule N3DS emunand partition, that is 1.8 Gigabytes in size (because the Hyrule N3ds has that large of a sysnand)

Emunand tool say No Emunand SD detected. I have tried numerous readers, and the SD card is accessible, I can read it with win32diskimager.

Is there any other windows tool out there to extract the emunand partition, and inject it that I can try?


Thanks

 

[gamesquest1]

make sure your using the latest emunandtool it did originally only work with o3DS emunand sizes, but was quickly fixed after the n3DS hax were released, you may just have a old copy

 

[crimpshrine]

make sure your using the latest emunandtool it did originally only work with o3DS emunand sizes, but was quickly fixed after the n3DS hax were released, you may just have a old copy

Thanks,

Yes I am using the most current version (emuNANDTool_1.0.3.exe) Unless there is a newer one I am unaware of.

I believe there are at least 2 different size sysNAND for N3DS, the Hyrule one I have is like 2 Gigabytes which is the largest.

 

[izy]

Use the emunand9 homebrew instead

btw about the 1.8gb Nand regardless of you having that nintendo limits what it accesses to 1.2gb thats why tools like emunand9 and decrypt9 only make 1.2gb emunands and emunand dumps.

 

[gamesquest1]

i have used emunandtool to backup a 1.8gb emunand before with no issues, not sure whats going wrong for you, but i guess you could just dump it via emunand9 instead, what toold did you use to format it? maybe emunandtool doesn't play well with emunand9 created emunand's or something if thats what it was created with

 

[crimpshrine]

Use the emunand9 homebrew instead

btw about the 1.8gb Nand regardless of you having that nintendo limits what it accesses to 1.2gb thats why tools like emunand9 and decrypt9 only make 1.2gb emunands and emunand dumps.

Are you sure about that? I just used EmuNAND9-20160310-104344 to dump the emunand to file and the file is 1,979,711,488 bytes, and the emunand was created originally USING emunand 9. (which copied sysnand at that time from this Hyrule N3ds)

--------------------- MERGED ---------------------------

i have used emunandtool to backup a 1.8gb emunand before with no issues, not sure whats going wrong for you, but i guess you could just dump it via emunand9 instead, what toold did you use to format it? maybe emunandtool doesn't play well with emunand9 created emunand's or something if thats what it was created with

OH ok, I only have 1 N3ds here that is that size, so it might be something wrong. Do you know in your case the 1.8GB emunand was it created with emunand9?

Thanks

 

[izy]

Are you sure about that? I just used EmuNAND9-20160310-104344 to dump the emunand to file and the file is 1,979,711,488 bytes, and the emunand was created originally USING emunand 9. (which copied sysnand at that time from this Hyrule N3ds)


OH ok, I only have 1 N3ds here that is that size, so it might be something wrong. Do you know in your case the 1.8GB emunand was it created with emunand9?

Thanks

When i used gateway to originally dump my Nand it was 1.8gb (MM XL) then every dump and Nand creation i have made has been 1.2gb

its even stated on 3Dbrew

The Nintendo 3DS has a 1GB NAND Flash chip. Due to the NCSD header, the actual used size of the Old3DS NAND is 0x3AF00000-bytes(943MiB). On New3DS, the actual NAND size and the total size used by the partitions, is 0x4D800000-bytes(1240MiB).

Basically there are 2 types 1.2gb and 1.8gb the 3DS is designed firmware wise to only use the smaller size.

Which yeah its stupid and i wish it could be fixed but for now its 1.2 for you

 

[crimpshrine]

When i used gateway to originally dump my Nand it was 1.8gb (MM XL) then every dump and Nand creation i have made has been 1.2gb

its even stated on 3Dbrew



Basically there are 2 types 1.2gb and 1.8gb the 3DS is designed firmware wise to only use the smaller size.

Which yeah its stupid and i wish it could be fixed but for now its 1.2 for you

Thanks for the information.

I just did a test.. I just booted on my N3ds hyrule edition and went into EmuNAND9-20160310-104344

I unmounted micro sd card, and inserted new micro sd card, I did complete emunand setup it formatted the card and copied SysNand to emunand, and while it was copying it Said:

Cloning SysNAND to EmuNAND (1888MB)

When it completed I inserted card into my pc and emunand tool 1.3 does NOT detect the emunand partition.

Partition manager shows the emunand partition is 1.85 GB

So is there any chance here that on certain N3DS units 1.8 GB is used? Or is something just really wrong with my N3ds?

 

[izy]

try using decrypt9

 

[Garou]

or use 3DS Multi EmuNAND Creator

 

[crimpshrine]

try using decrypt9

decrypt9 says this when I go to dump emunand:

Using EmuNAND @ 3B0000/000000
Dumping EmuNAND. Size (MB): 1888

--------------------- MERGED ---------------------------

or use 3DS Multi EmuNAND Creator

Thanks!! That actually works for me.

It recognized and extracted the 1.8 GB emunand from my SD card quickly. (was 1,979,711.488 bytes)

The process is just so slow on the N3DS, that is why I wanted to do it on the pc.

 

[crimpshrine]

Just a follow up, EVERY 3ds tool I tried uses the whole 1.8 GB, nothing truncates it to 1.2 GB.

I tried decrypt9, OTP helper, EmuNand9.

As far as I know there are 3 different sizes for Sysnand's between the O3DS xl and N3DS xl.

1 gig (I have an O3ds xl with this)

1.3 gig (I had an N3ds xl I no longer have)

1.98 gig (Hyrule N3ds xl I have currently)