I installed ReiNand on my O3DS just fine, everything works, AGB, TWL but looks like Sm4sh is rebooting to Sysnand, it gives me a "unable to find the latest data..." and if I press the Home button the console crashes, how do I fix it?
What?!it will if you dont have emu/red nand
why would you want non-screen init? get with the times grandpaSo I'm using a non screen init arm9 that I'd like to continue to use, does Reinand work with this version of screen init? I tried but got a black screen and I recall reading another user had to screen init to get it to work.
I'm going through the lengthy process now of removing my emunand partition from my sdcards.
Er.. There's actually updated forks without screen-init.why would you want non-screen init? get with the times grandpa
Are you using Shadowtrance's latest build?Why doesnt BootNTR.cia work in ReiNAND?
Why doesnt BootNTR.cia work in ReiNAND?
Im on sysNAND 9.0 EU and GW emuNAND 9.0 EU (N3DS). The latest BootNTR.cia 3.2 (from 44670) works fine if booting my GW emunand with the GW red card but it doesnt works if I boot the same GW emunand with ReiNAND. Everything else works fine in ReiNAND (twl, agb etc), except for BootNTR.cia (error: unknown menu and not supported firmware)
BTW whats the difference between Shadowtrances build, 44670 and BootNTR-Mode3?
Guys about this problem with the saves on GBA games, I've been playing "Super Mario Advanced 2 - Super Mario World" for a while (I've installed the game in sys and emu) and it saves normally, even when it boots directly on emuNand.
I'm testing it again here with another game to be sure (Eur version of Minish Cap), but I think that this problem is in the GBA .cia file you are using...
Edit: Yep, it saves just fine, I'm pretty sure that this problem is with the GBA injected .cia that you are using...
You are playing them from emuNAND, right? Try playing just from sysNAND and without going back to it(AKA: Install GBA to sysNAND(don't install on emuNAND), play it, reboot directly to emuNAND). Launching it from emuNAND is fine, but it means that you have to waste space by installing them twice.Guys about this problem with the saves on GBA games, I've been playing "Super Mario Advanced 2 - Super Mario World" for a while (I've installed the game in sys and emu) and it saves normally, even when it boots directly on emuNand.
I'm testing it again here with another game to be sure (Eur version of Minish Cap), but I think that this problem is in the GBA .cia file you are using...
Edit: Yep, it saves just fine, I'm pretty sure that this problem is with the GBA injected .cia that you are using...
You are playing them from emuNAND, right? Try playing just from sysNAND and without going back to it(AKA: Install GBA to sysNAND(don't install on emuNAND), play it, reboot directly to emuNAND). Launching it from emuNAND is fine, but it means that you have to waste space by installing them twice.
This may be up your alley.You are playing them from emuNAND, right? Try playing just from sysNAND and without going back to it(AKA: Install GBA to sysNAND(don't install on emuNAND), play it, reboot directly to emuNAND). Launching it from emuNAND is fine, but it means that you have to waste space by installing them twice.
Ah, you are using Menuhax, that affects only people who use ARM9LoaderHax, as it skips sysNAND during boot. MenuHax loads sysNAND to run Menuhax and then goes to emuNAND, so both are loaded, even if you can't see.Yep I'm playing it from emuNand, my setup is emu + MenuHax + CtrBootM + Rei 3.6b.
I don't know if this matters but GBA games wont open in sys if I dont run Pasta CFW first.
I will try to play the Super Mario World from the sys (it is more easy to save from some level on map screen and see if works), but after reboot in emuNand you want me to run it again from sys or from emu ?
I am already running Updated sysNAND via A9LH So I'm fineThis may be up your alley.
https://gbatemp.net/threads/tutorial-create-tiny-gba-forwarders-for-emunand.413737/
Ah, you are using Menuhax, that affects only people who use ARM9LoaderHax, as it skips sysNAND during boot. MenuHax loads sysNAND to run Menuhax and then goes to emuNAND, so both are loaded, even if you can't see.
--------------------- MERGED ---------------------------
I am already running Updated sysNAND via A9LH So I'm fine