Using emuNAND not redNAND with sysNAND Mode works to use the exploit or cia to start gateway.

MT is dead and doesn't support any new emuNAND.

 

Could you tell me the difference between emuNAND and redNAND?

 

Maybe possible to use mt, but there won't be any progress since its dead like fixes for ap.

a9lh doesn't change anything, sysnand mode is possible.

Depending on your chip, its either 1,3gb or up to 2gb.

The difference for rednand/emunand is the start sector.

rednand starts at the beginning of the memorycard and has less wearout.

http://3dbrew.org/wiki/NAND_Redirection

 

Interesting. So with a9lh and luma3ds installed, how would I go about entering sysnand mode on gw/mt?

(long story short, I sold my GW +3ds ages ago but I still have my OOT and MT, am thinking of getting a n3ds again and I'm looking for ways to transfer my saves which I know MT-card can convert .sav via savedatafiller)

— Posts automatically merged - Please don't double post! —

Ahh, crap. My memory is failing me. I just remember that n3ds is 2x of o3ds. Thought o3ds was 2gb.

 

Wouldn't it automatically boot into luma3ds instead of gw menu?

 

Nobody did. I'm saying that al9h boots into luma3ds upon power cycle right? So from Luma3ds I can boot into gw menu?

 

Exploit as in MSET/OOThax?
CIA as in the .3dx gw file?

 

Yeah, that's what I'm doing now. Researching. So far what I can gather is that HBL can launch gw.3dsx to enter gateway menu.

What I can't seem to find is whether I can enter gw sysnand mode from within luma3ds.

 

http://gbatemp.net/threads/guide-how-to-use-gw-luma3ds-a9lh.424117/