Hacking [Idea/Theory] Booting EmuNAND in extended memory mode?

  • Thread starter Thread starter Jaitsu
  • Start date Start date
  • Views Views 3,089
  • Replies Replies 13

Jaitsu

Yet Another GBATemp Furry
Member
Joined
Jun 2, 2015
Messages
152
Reaction score
51
Trophies
0
Age
33
XP
226
Country
United States
EDIT: I think I done fucked up something and this is probably totally unnecessary. Please disregard unless this has other applications.

So, as I recently discovered, it's impossible to play games such as Super Smash Bros. or MH4U on an EmuNAND, because the system has to reboot into extended memory mode - which means it kicks you out of EmuNAND, and gives a "The SD card was removed." error because SysNAND is on 4.5 (in my case, at least) and doesn't know what to do with the "boot in extended memory mode" command.

SO! My idea is thus. We already have launcher.dats that can patch all sorts of checks (Pasta, Palantine, PBT...). Is it possible to create one that instructs the EmuNAND to boot in extended memory mode? As I recall, the games LEAVE the 3DS in that mode, which is why someone made a program specifically for the sake of getting out of that. I'm very interested in finding out whether or not the games still reboot the 3DS if they detect that it's *already* in that mode.

Thoughts? Ideas? (Hell, I REALLY need to learn how to code this stuff.)
 
Last edited by Jaitsu,
This is for the New 3DS, correct? I am just asking because Super Smash Bros. works perfectly fine on my o3DS XL with sysNAND 4.5 (not-downgraded) and emuNAND 9.6+ (9.6 is the oldest emuNAND version I remember playing it on).
 
This is for the New 3DS, correct? I am just asking because Super Smash Bros. works perfectly fine on my o3DS XL with sysNAND 4.5 (not-downgraded) and emuNAND 9.6+ (9.6 is the oldest emuNAND version I remember playing it on).

No, actually, I'm talking about an o3DS. It works for you? Strange. It doesn't work for me; the instant I try to boot it, it reboots into sysNAND with that error.
 
Is the ROM trimmed? Some games have issues with that.

Nope. I'm confused. I wrote this thread on the basis that someone in another thread told me that it wasn't working because it's rebooting the 3DS.

I'm curious, though. My emuNAND is 9.2, not 9.6. Maybe I'll try with 9.6.
 
Both of those games work fine on gateway emuNAND. The system reboots after you close the game, not when you launch it.
 
you can get away with it by launching another app and closing that one instead of directly closing SSB
 
What are you using to run your emuNAND?

Both rxTools and Gateway should both be patched to run Smash/MH4 (and in the case of rxTools you'll need to have the slot0x25KeyX.bin on your SD card).
 
Both of those games work fine on gateway emuNAND. The system reboots after you close the game, not when you launch it.
This.
I've got Smash4 to work both on gateway red card and as a CIA, without doing anything special.
My setup is a O3DS 4.2 sysnand + 9.8 emunand + GW 3.2.2 launcher.
The only problem is that if you close Smash4 directly it will reboot the O3DS, kicking you to sysnand.
 
I must've done something wrong somewhere along the line, I don't know. I'll let you guys know if I figure anything out. I'm still curious about launching into extended-memory mode, though.
 
I must've done something wrong somewhere along the line, I don't know. I'll let you guys know if I figure anything out. I'm still curious about launching into extended-memory mode, though.
One thing I've remembered just now, what is the size of your SD card (the one that goes in the 3DS)?
MH4 and Smash4 had problems to run in GW redcard or CIA if your SD had less than 4GB in capacity (this includes 4gb cards with emunand partitions). Had you tried using a bigger SD card?
 
This is for the New 3DS, correct? I am just asking because Super Smash Bros. works perfectly fine on my o3DS XL with sysNAND 4.5 (not-downgraded) and emuNAND 9.6+ (9.6 is the oldest emuNAND version I remember playing it on).
what region o3ds do you have?

--------------------- MERGED ---------------------------

No, actually, I'm talking about an o3DS. It works for you? Strange. It doesn't work for me; the instant I try to boot it, it reboots into sysNAND with that error.
the same thing been happening to me

--------------------- MERGED ---------------------------

What are you using to run your emuNAND?

Both rxTools and Gateway should both be patched to run Smash/MH4 (and in the case of rxTools you'll need to have the slot0x25KeyX.bin on your SD card).
i have all that but it still wouldnt work, guess its just my region
 
I must admit that I have had no problems with Smash Bros myself. I purchased it from the eShop before obtaining my Gateway (so I'm not sure if that changes anything), and I've played in the following setups, all on Old 3DS:
sysNand <= 9.2, 4 GB System SD card, no emuNand
sysNand 9.2, 4 GB System SD card, emuNand 9.5ish
sysNand 4.2, 4 GB System SD card, emuNand 9.5ish
sysNand 4.2, 32 GB System SD card, emuNand 9.8

I was actually playing it yesterday morning, and then when I went to close the system, the right hinge snapped off, so I'm going to have to order a replacement part.
 

Site & Scene News

Popular threads in this forum