Hacking Luma3DS - Noob-proof 3DS Custom Firmware
- Thread starter Aurora Wright
- Start date
- Views 2,726,821
- Replies 19,840
- Likes 261
- Status
I prefer type 1 myself, since it avoids potential boot loops when launching SysNAND, but whatever works for you. If you want to run boot.3dsx with your current setup, you need to install the HBL CIA. Because there's no way to have Luma run a .3dsx file that I'm aware of.
You can probably use Luma's chain loader to run .bin payloads by placing them in "luma/payloads" but I'm not sure how well it works with Menuhax. However, it won't be able to run .3dsx and .dat files is the thing. What you really want to have it do is boot something like "auto.3dsx" instead of "luma.3dsx". It avoids implying a specific CFW or app. You can still make Luma the "auto.3dsx" if you decide that's what works best, but it won't confuse you if you decide to go with a boot manager.
So, you have a boot manager setup? What you need to do is make your boot manager "auto.3dsx" instead of "boot.3dsx" -- "boot.3dsx" should be your HB Menu (I recommend GridLauncher). So, then you have Menuhax launch your boot manager, and you configure the .cfg or .ini file of your boot manager to run Luma as default, with additional menu items or hotkeys for other things, depending on which you are using. As long as you have Menuhax booting Luma instead of your boot manager, you can only run .bin payloads from "luma/payloads" and not .dat or .3dsx files.
I've uploaded some examples of how to implement both CBM and BootCTR (managers included, though the copy of CBM may not be the latest, because I haven't used it in a while) with them named as "auto.3dsx" for example purposes. You can use them for examples of how to setup your own configuration, or use them as is. They should have most of the things you would want. They may have some things you don't use. Feel free to make changes. These are only examples. The CBM setup is what I used for everyday use for a while. However, my BootCTR configuration is designed to simplify installing A9LH, and not necessarily for everyday use (you may want to replace "OTP Helper" and "Safe A9LH Installer" with "EmuNAND9" and "Uncart" if they aren't interested in A9LH). It has also been modified to use a different .ini file than normal, so it can coexist with BootCTR9.
EDIT: Made some slight changes to the files. My old files were setup with GW as the default. Switched them to run Luma by default instead to better reflect your desired setup.
Last edited by Kazuma77,
That be the boot.3dsx that be in the root of your sd card
Sent from my LG-D851 using Tapatalk
Hi,
If I install a9lh ans Luma3ds, is there a way to get back to the original state without a9lh and custom firmware ?
For exemple in order to send back my n3ds to Nintendo or sell it...
If I install a9lh ans Luma3ds, is there a way to get back to the original state without a9lh and custom firmware ?
For exemple in order to send back my n3ds to Nintendo or sell it...
Yes, you must keep a NAND backup of your Sysnand from before installing A9LH, then you can just flash it back when you want it to be clean of any hacks.
Keep your SysNAND_original.bin in a safe place. Store it on thumb drives, burn it to DVD, whatever it takes to ensure you always have a copy. You can always use that to restore your 3DS to it's pre-A9LH state. EDIT: Looks like I got ninja'd.
Last edited by Kazuma77,
hm, yes could be.
but the same thing happened with my n3ds some day ago, i left it in sleep mode and put it on charge and later when it was done charging i opened it up and was greeterd with the error to power off my ds.
maybe my mSD has some sort of sleep function 'standby' function and thus it giving me an error.
i use Silicon Power HC U1 Class 10.
it could be my mSD
(and oh yeah, both my og and n3ds have the same brand same class of the sd card that i use both formatted at 64kb cluster size)
i do not have NAND backup of my sysNAND from before installing A9LH anymore, i replaced it with the backup of my A9LH sysNAND , and i always want to keep A9LH so am i good ?
Last edited by leonmagnus99,
neat, i have a sysNAND backup which i titled 'updated sysNAND' haha, i believe updated sysNAND is only possible with A9LH correct?
if so ,then that is my A9LH sysNAND backup, so if i were to flash that if in case i got a problem on my ds, i would not need to re-install A9LH since it is a A9LH sysNAND yes?
So I've been trying to figure out how to use Luma3DS in conjunction with Gateway sharing the same emuNAND on my 2DS.
My sysNAND is on 7.2 and emuNAND on 11.420blazeit.
Currently I don't want to use A9LH, or update my 7.2 firmware. So I've been trying the browser since that's how I've been launching Gateway (using go.gateway-3ds.com) with its own Launcher.dat.
I tried using the Homebrew Launcher using the browser via http://yls8.mtheall.com/3dsbrowserhax_auto.php. To no avail.
I deleted my browsers everything (history, cache, the initialize data deal). I tried using the more direct URLs then 3dsbrowserhax_auto. I redid my SD card 1.21 jizzillion times. 3ds folder with homebrew launcher, luma folder with O3DS firmware, Luma3DS.dat and boot.3dsx at the root of the SD card. Nuthin'.
Is there a way that I can get this to work? Or is this a [crack]pipe dream?
My sysNAND is on 7.2 and emuNAND on 11.420blazeit.
Currently I don't want to use A9LH, or update my 7.2 firmware. So I've been trying the browser since that's how I've been launching Gateway (using go.gateway-3ds.com) with its own Launcher.dat.
I tried using the Homebrew Launcher using the browser via http://yls8.mtheall.com/3dsbrowserhax_auto.php. To no avail.
I deleted my browsers everything (history, cache, the initialize data deal). I tried using the more direct URLs then 3dsbrowserhax_auto. I redid my SD card 1.21 jizzillion times. 3ds folder with homebrew launcher, luma folder with O3DS firmware, Luma3DS.dat and boot.3dsx at the root of the SD card. Nuthin'.
Is there a way that I can get this to work? Or is this a [crack]pipe dream?
the only way you can use the homebrew launcher via browserhax is to update to any version 9.0+.
https://github.com/Plailect/Guide/wiki/9.2.0-Update
Can someone help me? I'm trying to get the dev version to boot up but it doesn't work but it just hangs on a black screen after choosing the Enable developer features option on 5.5-6a280723. I tried reinstalling A9LH through SafeA9LHInstaller but even after going back to Delebile's version, It doesn't work. I have no idea why is this happening.
Edit: Figured it out. I had changed to the test menu some time ago and by enabling it. Unitinfo doesn't work.
Edit: Figured it out. I had changed to the test menu some time ago and by enabling it. Unitinfo doesn't work.
Last edited by HenryLeonheart,
Yes that's correct, A9LH will still be on your 3DS. Even if you had a non-A9LH backup, you can still flash it and keep A9LH with Decrypt9 using the "keep A9LH" option!
neat, could i use the keep a9lh in decrypt9 even if i am using a a9lh sys nand to restore? i guess yes.
- Status
Similar threads
- No one is chatting at the moment.
-
@
Psionic Roshambo:
I wonder if I could recommend that to some emulation devs that perhaps the sound could use some smoothing out to simulate those old TVs -
@
Psionic Roshambo:
I think a few of the early systems could benefit from that, at least up to the 8 bit generation, by the 16 bit generation I think TVs had gotten a lot better in almost every way
-
-
-
-
-
-
-
-
-
-
@
Xdqwerty:
it says it only works for the original R4, R4i Gold (r4ids.cn), R4iDSN (r4idsn.com) and Acekard R.P.G. -
-
-
-
-
-
@
Psionic Roshambo:
Just give it a try, but honestly if you have a 3DS you can play DS games without a card just off the internal SD card
-
-
-
-
-
-
-
