Someone with pics and steps on how to replicate the issue should email Gateway so that they know the issue is there and perhaps they can work on a quick fix for it on an upcoming release.
Someone with pics and steps on how to replicate the issue should email Gateway so that they know the issue is there and perhaps they can work on a quick fix for it on an upcoming release.
It's not a bug, it's expected behavior. A system with 4.x sysnand can not use savegames created by a system with 6.x+ sysnand. That's because the system will still use your sysnand keys to encrypt the savegame and that encryption changed on fw 6.0.
The only real issue here is that MM3D doesn't ask the user beforehand here, but then again in Nintendos view the game can not be played in a system < 9.2 so they rightly so do not see this as an issue affecting their legit costumers. Only users with a hacked device and emunand are affected by the issue.
So uh, I'm not sure if I'm misunderstanding or...what--but I played MM3DS (E) on my US console. SysNAND 7.X and emuNAND 9.2. I transferred the save file to a 4.3 sysNAND/9.3 emuNAND and the save worked no problem.
Same thing happened to me, what I don't get is why would affect me that my sysnand is in 4.5 if my emunand (where I attempted to play the game and got my data wiped) is in 10.3.... I've a O3DS.