It's because N3DS nand is twice bigger than 3DS nand (954 MB against 1.84 GB).
My dump is 1.2GB... Hmmmmmm
Same here.
Some N3DS will be 1.2GB, and others will be 1.8GB. It's to be expected because of different underlying chips. The extra 0.6GB should all be 0s, so gateway was lazy with their dumping.
My SYSnand dump was also 1,2gbMy dump is 1.2GB... Hmmmmmm
I got a 32gb samsung evo class 10 and I still get the GW3D bug
i'm not surprised, but the '...' at the end of your post you make it seem like it should support it already, when we have had new3ds emunand support for less than 12 hours
Well, I figured that the size of the emunand was stored in the emunand. Making it so that this would work with any size of emunand.
which offset?
I do not know, I just thought that because of good software design. But this is GW...
oh, sorry - you mean you guess the size of the emunand would be in the emunand itself - i doubt that.
it's not about good software design or gw, emunand is supposed to simply be the nand, on the sd card
i doubt nintendo needs to store the size of the nand within the nand itself
Same. I have a Scandisk Extreme (Class 10) and still got the bug.
Same. I have a Scandisk Extreme (Class 10) and still got the bug.
The problem is not that it's not showing GW, because we don't really care about that.
Just that it's risky to update when it's not written, someone said he updated and it worked fine, but personally, when I remove the Micro-SD Card in the settings, the N3DS doesn't crash, which mean I'm already on the sysnand and that it might be risky to update.
which offset?
Yeah, thats why you should use the standard 4gb micro SD that the console came with and transfer it for now
I have a Sandisk Ultra SDHC 32GB (Class 10) and I don't have the GW3D bug.