I have a 2DS on 7.2.0-17u so can i use EmuNAND 7.2.0 on it without a flashcart? I can boot classic mode successfuly without GW Red Card but whenever i try to enter System Settings it just loops on the 3DS logo splash screen. Any fix for this?
Hacking [2DS] EmuNAND without Flashcart QUESTION
- Thread starter WateredFire19
- Start date
- Views 1,837
- Replies 11
You can with the MT CARD launcher.dat but idk if you can load it using the GW 3.0 exploit...
Hmm..... I wonder why no one wants to develop for 2DS. I see more and more people carrying them around over time. *BEGS FOR A 4.5 DOWNGRADE FIRMWARE FOR 2DS THAT HAS A BUILT IN WIRELESS FUNCTION TOGGLER*
No, you can't. But what about if you install ROP Installer first? Wouldn't that enableit to load the MT Launcher.DAT?
yeah they probably could....but whats the point, the MSET exploit only works for 4.x, which is what the old style launcher use....also they want people to buy gateway cards, so they would prefer people to just buy one and then they can use emunand with all the features.....the real issue here is that gateway doesn't allow 7.x decryption (used for newer games like ORAS,Smash bros etc) in classic mode unless you insert the red card.......in 7.2, system settings was using 7.x encryption, which is why it works but not the system settings part, if you inserted a gateway card before entering classic mode, it would work fine
The MSET exploit was patched in 7.0 actually. They could probably make 3.0 work with MSET on consoles up to 6.3 if they wanted
nope the NDS profile exploit was patched in 7.x, the MSET exploit (i.e the important one) was blocked with 5.x+, which is why it was 4.x only....question would be, could the NDS profile exploit be used to trigger the new exploit, but still it would need a new launcher.dat for the new exploit to be given by MT to work with the new exploitThe MSET exploit was patched in 7.0 actually. They could probably make 3.0 work with MSET on consoles up to 6.3 if they wanted
I thought the mset exploit WAS the NDS profile exploit, since mset = system settings.
Well regardless, the rest of what I said is still true.
ooohhh my bad i think it is....too many exploitsI thought the mset exploit WAS the NDS profile exploit, since mset = system settings.
Well regardless, the rest of what I said is still true.
still if the NDS profile exploit was reworked to work with the new kernel exploit it would still only work with the new format launcher files, meaning MT would need to supply a update with new exploit capabilities
PS, sorry for the confusion, its just that they are always so commonly linked that i kinda think of MSET as the whole 4.x exploit and NDS profile exploit separate....but really its the other way around
....i think we need a catchy name for the 4.x kernel/process9 exploit need a catchy name so it can be differentiated from MSET 
