Emunand detection failed in 2ds, release 85 about cakesforeverywan HOT 5 CLOSED

NAND CSD data :

40 40 8A E7 FF DB F6 6B 02 5A 0F 32 01 27 D0 00

Gives the size of ~1.21GB using @Normmatt's method. thaikoa also reported that his nand dump from GW is 1.21GB in size, while the one from Decrypt9 is 943MB in size.

He's using the nand dump from Decrypt9 which explains why we failed to detect it.

from cakesforeverywan.

That's because Decrypt9 doesn't dump the entire nand like it should.

from cakesforeverywan.

@Normmatt agreed.

So we have two options so far:

1. Integrate a rednand formatter - which means that CakesFW emunand will be incompatible with other CFWs.
2. Leave it as it is - some 2DSes will be incompatible with our/other CFWs, depending on which dump they use.

I'm going to leave this open until @mid-kid can chime in. Maybe there's another way to work around this.

from cakesforeverywan.

A malformed/incomplete NAND dump is a bad dump. No way around that.
We won't support loading a Toshiba NAND when it's clear you have a N3DS Samsung NAND on your 2DS.

The problem is, Decrypt9 and rxTools hard-code their NAND sizes, and since this console isn't detected as a N3DS, it uses a size too small. This gives a problem, since you can't boot rxTools with a GW-formatted emuNAND (GW detects it the right way), if you have this type of NAND. This is probably why this person created his emuNAND with a NAND dump from Decrypt9.

I believe this is a wontfix for this project. Other projects should fix up their stuff to get the correct NAND sizes.

from cakesforeverywan.

Also, it isn't a bug, it's a feature. :P

from cakesforeverywan.