Indeed. Especially with Luma having most of the same features people use it for. Then again, you might as well keep it, because you can have Luma boot SysNAND with 10.4 and 10.2 with the same setup, thanks to unintended uses of the "SysNAND is updated" setting. Turning it off causes firmware.bin to replace EmuNAND's NATIVE_FIRM. Obviously, this was intended to boot an updated EmuNAND and 9.2 SysNAND (when "R" is held) with 10.2. However, it works just fine for booting a 10.7 SysNAND with 10.2. Thus, by turning the option off, you get 10.4 NATIVE_FIRM by default, and 10.2 "NTR mode" SysNAND if you hold "R" at startup. The only bad thing is that since EmuNAND also gets booted with 10.2, no GW until you turn it back on
But GW's A9LH payload should fix that. Guess this means Aurora needs to change the description again
.
Welcome to the best CFW (as of at least 3 months ago, oh well, better late than never).
I assure you the file is in the archive. It's name is "arm9loaderhax.bin" -- you should be using it already if you're running A9LH. You should always use the "arm9loaderhax.bin" file (you have to rename it for everything except your chosen launcher of course) that comes with any CFW or tool you download, if it exists. If not, as is the case with Cakes, you can make one with a hex editor. Just select 12000 (hex) to the end of the file, copy, and paste to a new file, then save it with a .bin extension (for CMB9 and BootCTR9 something like "Cakes.bin" works just fine, but for config-less loaders like Luma and Arm9Select, you'll need to use "y_Cakes.bin" or "y.bin" to make it work of course). Luma's .bin file has some actual differences from the .dat file, being made specifically for A9LH use (makes things like "force A9LH detection" unnecessary). Anyway, copy the file to the "pathchanger" folder. Rename the "arm9loaderhax.bin" to something like "Luma3DS.bin". You can then either use the python script from a command line -- "pathchanger.py Luma3DS.bin a9lh/Luma3DS.bin" for example, or move the file to the Windows folder, drag it onto "pathchanger.exe" in Explorer, and type the path (if you're putting it somewhere other than the root) and name, and hit enter. For example, "a9lh/Luma3DS.bin" if you want to place it in the "a9lh" folder (the tutorial kind-of got me doing that, but you could simply use "Luma3DS.bin" if you would rather leave it in the root, and for anyone reading this that's using Arm9select, it has be in "arm9select" so something like "arm9select/default.bin" would be what you use). Now just copy your patched .bin to the place that matches what you entered, point your boot manager to the file, and it should work now (it works for me, DSTwo and AK2i both working fine, and so is "Four Swords"). Hope that helps.
I used to be a fan of CBM too, but the A9LH guide got me hooked on BootCTR9 since one guide option uses it. I didn't know this had a boot manager at the time, but it was readily apparent the "Cakes" option used one, and could therefore run both, so I followed that guide, but made this the default, and put Cakes on "Y" instead. Now I realize that this can run it too, but keeping what I have means I can place a hotkey over a feature I don't use, like "B". I find hotkeys faster and more direct. No more having to hit "down" multiple times, just hold a button or d-pad direction. I can literally boot Decrypt9 in one second. Anyway, you might want to try it. You might like it better, or you might not. It's a matter of personal taste.
BTW, could you tell me where you found a working RxTools for A9LH? I wanted to include it in my A9LH transition, if only for the sake of completion, but the only thing I could find was over a month old at the time. I would like to see what progress is being made. Though I'm sure it probably has a long way to go yet. Not to sound critical. It would probably take me years to figure out thousands of lines of some other guy's source code. They're making good progress given the situation.
@
SylverReZ:
@
BigOnYa:
@
Psionic Roshambo:
@
HiradeGirl:
