RedNAND usually saves space compared to the Gateway style. It dumps only what's needed, while the Gateway setup tends to include garbage data, wasting space. RedNAND is also the only option for people with those Pokémon 3DSes, as far as I understand.
if I remember correctly, those 2DSes have an unusual NAND chip (1.8GB or something, same as some N3DSes). I think @d0k3 was getting some help from people with those consoles so that Decrypt9/EmuNAND9 support them, so maybe he can elaborate more, if he wishes.
These 2DS consoles have a 1.2GB NAND chip, of which only ~940MB is used. If you really want to know why they don't work with a standard / GW type EmuNAND, read about it - there's a link with a good description of the difference between standard / GW type EmuNAND and RedNAND in the EmuNAND9 readme. Hint: It is because the NAND header is beyound the 1GB limit. Typical O3DS based consoles have their NAND chip sizes below 1GB, and thus their NAND headers below that limit.
Yeah, but that is is a N3DS, which has a larger NAND chip anyways.Seconding this!(Fun fact: one of my 3DSes has a 1888MB NAND, emuNAND works perfectly on it.)
from what I can tell, RedNAND does not work with AuReiNAND when converted via EmuNAND9 as the conversion with EmuNAND9 causes AuReiNAND to not boot EmuNAND but it can boot once converted back to Gateway NAND.
EDIT: after further testing, it seems RedNAND can be booted via AuReiNAND after converting with EmuNAND9 but requires booting with B for second EmuNAND boot.
EDIT2: It seems entering System Settings on RedNAND (booted via B) causes it to back out into system NAND :/
EDIT3: I switched back to EmuNAND, RedNAND is not worth it if it will exit back to SysNAND all the time like having a non AL9H CFW with EmuNAND.
EDIT: after further testing, it seems RedNAND can be booted via AuReiNAND after converting with EmuNAND9 but requires booting with B for second EmuNAND boot.
EDIT2: It seems entering System Settings on RedNAND (booted via B) causes it to back out into system NAND :/
EDIT3: I switched back to EmuNAND, RedNAND is not worth it if it will exit back to SysNAND all the time like having a non AL9H CFW with EmuNAND.
Last edited by driverdis,
I think I have an idea what happens here... @Aurora Wright, could you put the RedNAND detection (you do it via the header, right?) before the Gateway EmuNAND detection? It is more safe in that order.
Yup, that's possible too, for N3DS consoles. NAND sizes vary even in the same console type. There are no N3DS NANDS < 1GB though.
I wonder what that extra 500mb is doing in those Pokémon ones, considering it's the same system. Strange.
Nothing, that is. I guess Nintendo just got these bigger NAND chips cheaper for one reason or another.
Similar threads
-
K3Nv2
-
Psionic Roshambo
-
HiradeGirl
-
SwordShielder
-
Xdqwerty
what are you looking at?
-
-
@
Psionic Roshambo:
Phones worked great for DS emulation with DraStic and a controller that held your phone
-
-
-
@
K3Nv2:
Yeah it works great but it's the obvious Ds factor you loose from it it's not like playing atari games on atari because Nintendo actually use to give a reason to buy their hardware+1
-
@
Psionic Roshambo:
Honestly Ken I actually have the hardware and it's hacked and works fine, prefer my phone lol
-
@
Psionic Roshambo:
Microphone is more sensitive, DraStic has a high res mode, screen is way better just overall a better experience
-
@
K3Nv2:
I just like game consoles how they were intended to play if they have a unique enough reason to buy them anything else yeah just download emulation for it
-
-
-
-
-
@
K3Nv2:
I'd like to see a DS emulator that allows casting top screen to TV then use bottom for the touch screen stuff+1
-
-
-
@K3Nv2 I did that using Citra for 3DS games. Bottom screen was my smartphone. Until I got the touch screen.
-
-
-
-
@
Psionic Roshambo:
Ken I have that sort of set up on Drastic on Pi for games that don't require touch
-
-
-
Any TV with your PC connected with Citra and any smartphone to use as a screen using a free play store app.+1
-
-