I use the trbo-code branch to dump badges, but it hasn't updated to Luma v7. Is there a way I could keep both versions on my SD and possibly chainload them like with decrypt9 without creating an emuNand?
Hacking Is there a streamlined way of using multiple Luma versions?
- Thread starter spongeabc5
- Start date
- Views 2,359
- Replies 14
Sure you can put another CFW (for a very liberal definiton of "another" - could even be the same version) as an alternate payload of the first!
However, you'll likely want to recompile one of the two Lumas to use a different path from /luma/ for its work folder, so that you can have separate configurations - that you will need due to one not needing the custom path option and the other doing!
However, you'll likely want to recompile one of the two Lumas to use a different path from /luma/ for its work folder, so that you can have separate configurations - that you will need due to one not needing the custom path option and the other doing!
You don't need to create an emuNAND to use multiple CFWs. 3DS CFWs do not actually effect the NAND and you can run multiple CFWs at the same time. I know because I am running 5 of them right now, all on one sysNAND.
To run multiple versions of Luma3DS, you would have to compile each version with a different path. So like @Ryccardo said, you would have to compile the launcher to work from another folder instead of the /luma
To run multiple versions of Luma3DS, you would have to compile each version with a different path. So like @Ryccardo said, you would have to compile the launcher to work from another folder instead of the /luma
Assuming I'm following the Compiling instructions for trbocode's repo, what else do I do to change the path? Am I changing references in the files or something else?
It might be simpler to just open one payload in a hex editor and replace /luma with something else, like /lum2 or something.
What's different about turbocode's fork? This is the first time I've heard of it.
Last edited by Zidapi,
It adds a different font to the Luma3DS settings.
Last edited by The Catboy,
lol that's all? I don't spend enough time at the settings screen to hate the existing font. I certainly couldn't justify using an old/outdated build of luma for the sake of a "prettier" one.
The only time I visit the config screen is to disable L2 cache so I can boot the homebrew launcher, which is very rarely these days.
You're helpful as always, thanks for the info.
You can use CtrBootManager as arm9loaderhax.bin and rename all the luma binaries to something else. Then, set up multiple boot entries in CBM's a9lh.cfg file one for each luma launch. Finally, to separate their activity, you'll need a hex editor. Use it to open the luma binaries and search and replace every entry of "config.bin" and "path.txt" so that they are all unique. Keep the same length on the newly renamed entries. Now create those path.txt files in the /luma folder and in each of them you need to have a path pointing back to the luma .bin it's going to be running with.
It looks like the trbocode branch has been updated for 7.0 now. https://github.com/trbocode/Luma3DS/pull/16
https://github.com/trbocode/Luma3DS/pull/16
Edit: Actually it was updated to 7.0.1 a while ago: https://github.com/trbocode/Luma3DS/pull/15
Now listen here you-
As far as I know, the font swapping is a newer feature, I use it because (as far as I know) it's the most up-to date fork that has the crypto-patches necessary to use SciresM's badge arcade tool.
Thanks for this, I guess I don't need to get grep for this!
Last edited by spongeabc5,
Similar threads
