Homebrew [RELEASE] CtrBootManager/CtrBootManager9
- Thread starter OperationNT
- Start date
- Views 32,390
- Replies 170
- Likes 30
Hello dmc310,
In which condition did you use CtrBootManager9? Directly as "arm9loaderhax.bin" or as Luma3DS payload?
I use it in the second condition (Luma3DS payload named "start_CtrBootManager9.bin") and I don't meet any issue with Luma3DS 6.5 and Decrypt9WIP version 2016/10/05.
Can you specify your "a9lh.cfg" file content and your Decrypt9 version?
Thank you for your report!
In which condition did you use CtrBootManager9? Directly as "arm9loaderhax.bin" or as Luma3DS payload?
I use it in the second condition (Luma3DS payload named "start_CtrBootManager9.bin") and I don't meet any issue with Luma3DS 6.5 and Decrypt9WIP version 2016/10/05.
Can you specify your "a9lh.cfg" file content and your Decrypt9 version?
Thank you for your report!
I use Ctrbootmanager as start_CtrBootManager9.bin so its boots up when I hold start on bootup,
here is how i have the a9lh.cfg, I have the latest Emunand9 and Decrypt9, funny thing is that they work when I make them boot off any key on the 3ds but they dont boot off the ctrmanager
[general]
timeout=-1;
recovery=3;
default=0;
[theme]
bgTop1=000000;
bgTop2=000000;
bgBottom=000000;
highlight=FF00004F;
borders=C9FFFCBF;
font1=C9FFFCBF;
font2=C9FFFC;
bgImgTop=/luma/payloads/splash/bgTop.bin;
bgImgBot=/luma/payloads/splash/bgBot.bin;
[animation]
highlight=12:0:FF0000AF;
menuFadeIn=20:10;
[entry]
title=Luma3DS;
path=/anim/arm9payload.bin;
offset=12000;
thumbTop=/luma_thumb.bin;
thumbTopParams=316:12:64:64:yes;
key=-1;
[entry]
title=Decrypt9;
path=/luma/payloads/Decrypt9WIP.bin;
offset=12000;
key=-1;
[entry]
title=EmuNAND9;
path=/luma/payloads/EmuNAND9.bin;
offset=12000;
key=-1;
[entry]
title=Hourglass9;
path=/luma/payloads/Hourglass9.bin;
offset=0;
key=-1;
[entry]
title=SafeMode9;
path=/luma/payloads/SafeMode9.bin;
offset=0;
key=-1;
timeout=-1;
recovery=3;
default=0;
[theme]
bgTop1=000000;
bgTop2=000000;
bgBottom=000000;
highlight=FF00004F;
borders=C9FFFCBF;
font1=C9FFFCBF;
font2=C9FFFC;
bgImgTop=/luma/payloads/splash/bgTop.bin;
bgImgBot=/luma/payloads/splash/bgBot.bin;
[animation]
highlight=12:0:FF0000AF;
menuFadeIn=20:10;
[entry]
title=Luma3DS;
path=/anim/arm9payload.bin;
offset=12000;
thumbTop=/luma_thumb.bin;
thumbTopParams=316:12:64:64:yes;
key=-1;
[entry]
title=Decrypt9;
path=/luma/payloads/Decrypt9WIP.bin;
offset=12000;
key=-1;
[entry]
title=EmuNAND9;
path=/luma/payloads/EmuNAND9.bin;
offset=12000;
key=-1;
[entry]
title=Hourglass9;
path=/luma/payloads/Hourglass9.bin;
offset=0;
key=-1;
[entry]
title=SafeMode9;
path=/luma/payloads/SafeMode9.bin;
offset=0;
key=-1;
Last edited by dmc310,
People can help me install this?
I already have Luma 3ds with last FW, gateway, emunand9, hourglass and decrypt9wip.
Where i put the files in the zip? i need to put all in SD root or in payloads?
Help me please Thanks
I already have Luma 3ds with last FW, gateway, emunand9, hourglass and decrypt9wip.
Where i put the files in the zip? i need to put all in SD root or in payloads?
Help me please Thanks
Hello @skinnedpt,
It depends on what you want to do:
- You can either use CtrBootManager9 from cold boot, in that case, you must rename it "arm9loaderhax.bin" and put it at the root of your SD card
- Or you can use it as a Luma3DS payload (which would be firstly the best choice), in that case, name it for example "start_CtrBootManager9.bin" and put it in "/luma/payloads"
CtrBootManager9 will read the file named "a9lh.cfg" at the root of the SD card for its configuration (or it will create this file if it doesn't exist). You can easily edit the list of default entries:
- Remove an entry by pressing the "X" button when the cursor stays on it
- Add new entries to the "File Browser" in "More..." by pressing "X" button on an executable binary (".bin" or ".dat")
If there was no entry at all, you need CtrBootManager9 restart to make entries appear.
Once you have all your entries configurated, you can retreive the "a9lh.cfg" file to fully customize entries and the theme. CtrBootManager9 offers a lot of customization options (which can make it a little bit hard to understand/use). You can read in detail the following documentation if you feel brave enough
:
https://github.com/OperationNT414C/CtrBootManager/wiki/CtrBootManager-setup
You can also see some preconfigured theme examples on the first post.
Have fun!
It depends on what you want to do:
- You can either use CtrBootManager9 from cold boot, in that case, you must rename it "arm9loaderhax.bin" and put it at the root of your SD card
- Or you can use it as a Luma3DS payload (which would be firstly the best choice), in that case, name it for example "start_CtrBootManager9.bin" and put it in "/luma/payloads"
CtrBootManager9 will read the file named "a9lh.cfg" at the root of the SD card for its configuration (or it will create this file if it doesn't exist). You can easily edit the list of default entries:
- Remove an entry by pressing the "X" button when the cursor stays on it
- Add new entries to the "File Browser" in "More..." by pressing "X" button on an executable binary (".bin" or ".dat")
If there was no entry at all, you need CtrBootManager9 restart to make entries appear.
Once you have all your entries configurated, you can retreive the "a9lh.cfg" file to fully customize entries and the theme. CtrBootManager9 offers a lot of customization options (which can make it a little bit hard to understand/use). You can read in detail the following documentation if you feel brave enough
:https://github.com/OperationNT414C/CtrBootManager/wiki/CtrBootManager-setup
You can also see some preconfigured theme examples on the first post.
Have fun!
Hello @skinnedpt,
It depends on what you want to do:
- You can either use CtrBootManager9 from cold boot, in that case, you must rename it "arm9loaderhax.bin" and put it at the root of your SD card
- Or you can use it as a Luma3DS payload (which would be firstly the best choice), in that case, name it for example "start_CtrBootManager9.bin" and put it in "/luma/payloads"
CtrBootManager9 will read the file named "a9lh.cfg" at the root of the SD card for its configuration (or it will create this file if it doesn't exist). You can easily edit the list of default entries:
- Remove an entry by pressing the "X" button when the cursor stays on it
- Add new entries to the "File Browser" in "More..." by pressing "X" button on an executable binary (".bin" or ".dat")
If there was no entry at all, you need CtrBootManager9 restart to make entries appear.
Once you have all your entries configurated, you can retreive the "a9lh.cfg" file to fully customize entries and the theme. CtrBootManager9 offers a lot of customization options (which can make it a little bit hard to understand/use). You can read in detail the following documentation if you feel brave enough
https://github.com/OperationNT414C/CtrBootManager/wiki/CtrBootManager-setup
You can also see some preconfigured theme examples on the first post.
Have fun!
Thanks for the godd work at CtrBootManager9 and for the reply.
I will try this tomorrow. Why you recomend Luma payload instead coldboot?
Because it is easier to set up, since you do not have to ue a custom path and have to nnesesarily have to edit the config of the luma or star updater. There are still some users (like me), who like it as there main a9 payload just because they like to boot Decrypt9 after rebooting a gba game to make a save backup, and lumas chainloading only works the first time you booted your console. Maybe I will write a guide in the future of all the different ways to boot your console.
Hello, when I put the arm9loaderhax.bin on the root of the sd card and the a9lh.cfg, when I turn on the system I see nothing. I did add the screeninit and nothing happen. I am using a new 3ds xl on 11.2 with a9lh.Hello @skinnedpt,
It depends on what you want to do:
- You can either use CtrBootManager9 from cold boot, in that case, you must rename it "arm9loaderhax.bin" and put it at the root of your SD card
- Or you can use it as a Luma3DS payload (which would be firstly the best choice), in that case, name it for example "start_CtrBootManager9.bin" and put it in "/luma/payloads"
CtrBootManager9 will read the file named "a9lh.cfg" at the root of the SD card for its configuration (or it will create this file if it doesn't exist). You can easily edit the list of default entries:
- Remove an entry by pressing the "X" button when the cursor stays on it
- Add new entries to the "File Browser" in "More..." by pressing "X" button on an executable binary (".bin" or ".dat")
If there was no entry at all, you need CtrBootManager9 restart to make entries appear.
Once you have all your entries configurated, you can retreive the "a9lh.cfg" file to fully customize entries and the theme. CtrBootManager9 offers a lot of customization options (which can make it a little bit hard to understand/use). You can read in detail the following documentation if you feel brave enough
https://github.com/OperationNT414C/CtrBootManager/wiki/CtrBootManager-setup
You can also see some preconfigured theme examples on the first post.
Have fun!
Sorry for the late response. Here is my a9lh.cfg file: remove the ".txt" extension.
Hello @Polarise,
"autobootfix=8;" is useless on A9LH version
"screeninit=3;" is useless if you didn't set "timeout=0;" (for instant chainload if the recovery key is not pressed)
"path=/Luma3DS.bin;" with "offset=12000;" will probably cause a crash on Luma3DS load: an offset of "0x12000" bytes was meant for a file with ".dat" extension, not for a ".bin" extension so you should change "offset=12000;" to "offset=0;"
You did not answer to one of my previous question, if you don't put any "a9lh.cfg" file, do CtrBootManager9 starts?
"autobootfix=8;" is useless on A9LH version
"screeninit=3;" is useless if you didn't set "timeout=0;" (for instant chainload if the recovery key is not pressed)
"path=/Luma3DS.bin;" with "offset=12000;" will probably cause a crash on Luma3DS load: an offset of "0x12000" bytes was meant for a file with ".dat" extension, not for a ".bin" extension so you should change "offset=12000;" to "offset=0;"
You did not answer to one of my previous question, if you don't put any "a9lh.cfg" file, do CtrBootManager9 starts?
Last edited by OperationNT,
I've chained CtrBootManager with the arm9loaderhax.bin provided for a9lh version 2 that is currently so popular around. It boots the sysNAND fine but although I've selected it, the "sys" string doesn't appear in system settings. This makes me wonder whether the chaining applies the usual a9lh patches and safeguards. Is there a better way to chain these?
D
Deleted User
Guest
Is there anywhere I could find a proper tutorial on installing this with a9lh? I've never tried ctr boot manager and I'd like to use it to swap between cfw's without having to rename my arm9loaderhax.bin in FBI every time.
Last edited by ,
Actually, "CtrBootManager9.bin" (provided in releases) can be directly renamed as "arm9loaderhax.bin" and the 3DS will directly boot it on start. Then you can use the "File Browser" to launch a CFW or add an entry which will pop up in the first menu on next restart.
You have 2 choices:
- "Safe" way, payload for Luma3DS: rename "CtrBootManager9.bin" to "start_CtrBootManager9.bin" and put it in "/luma/payloads"; then, when you start Luma3DS, you can maintain "Start" button to direcly boot into CtrBootManager (Luma3DS won't even start as a CFW)
- "Advanced" way, direct boot: Rename "CtrBootManager9.bin" to "arm9loaderhax.bin" and put it at the root of your SD card
I recommend you the safe way to set up your "a9lh.cfg" file (CtrBootManager configuration file) because if something is wrong, you can still boot in a CFW to make some configuration modifications. Once you made a proper configuration, simply go to the advanced way.
D
Deleted User
Guest
Thanks.The safe way works nicely for me.What I did was set the chainload with one of the cfg's someone posted that had reinand and luma paths set already but I backed it up so I can set the timer to 0 and boot straight into reinand by holding 1 button.So if I ever want to switch to a different cfw all I have to do is set the .bin path on the backup cfg and then replace it with the one that doesn't have the timer set.The thing is though when you reboot you get kicked back into luma so if I set it up as my arm9loaderhax.bin I can easily make it autoboot,I just have to repaste my cfg backup.
Last edited by ,
- Joined
- May 17, 2014
- Messages
- 535
- Trophies
- 0
- Age
- 31
- Location
- Warrnambool, Victoria, Australia
- XP
- 499
- Country
It's great to see a version of CtrBootManager that uses A9LH. I have a question though, will .3dsx files ever be supported as boot files in the future for the A9LH version of CtrBootManager9? I know that they're already supported for the .3dsx version of CtrBootManager9.
No, it is technically not possible: 3DSX executable files requires the Nintendo firmware environment. When CtrBootManager9 is loaded, the Nintendo firmware isn't.
Nintendo firmware is only loaded on coldboot if you don't set up A9LH or when you start a CFW (and when you exit "Settings" application, the firmware is "unloaded" too).
Nintendo firmware is only loaded on coldboot if you don't set up A9LH or when you start a CFW (and when you exit "Settings" application, the firmware is "unloaded" too).
Last edited by OperationNT,
Is it possible to put two or more memory patches that search for a string and replace it? I'm thinking that like the sdmc:/arm9loaderhax.bin can be overwritten, it might be possible to redirect sdmc:/luma/config.bin. Then it would be possible to have multiple concurrent Luma installs each with their own restart path as well as configuration. Says that you can use up to 4 patches per entry but can you actually specify more than one search-and-replace patch? How would that look in the config?
EDIT: I think I'm doing it right but apparently the "config.bin" string isn't stored in memory in any way I can discern - not "sdmc:/luma/config.bin" not "config.bin" not "config.bin" with null between each byte...
EDIT: I think I'm doing it right but apparently the "config.bin" string isn't stored in memory in any way I can discern - not "sdmc:/luma/config.bin" not "config.bin" not "config.bin" with null between each byte...
Last edited by Searinox,
Similar threads
-
-
@
RedColoredStars:
Grilled peanut butter sandwiches with banana, bacon, and marshmallow cream. YUM!!!! -
-
-
-
-
-
-
-
-
-
-
@
RedColoredStars:
i only buy new ones when theres a new standard and I have gear that uses it. Otherwise my cables seem to last forever.
-
-
-
@
RedColoredStars:
@SylverReZ Yup. Been a longtime fan of Ween. Not a mega-fan by any means but I'm pretty familiar with most of their tunes.+1
-
-
@
ZeroT21:
I like electronics that use detachable cables, that way if the cable breaks you can just swap in a new one instead of replacing the whole unit -
-
-
-
-
-
-
@
RedColoredStars:
the L hdmi cables work great on my tv and receiver. so much less stress on the ports using them than regular cables. in that instance anyway.
@
RedColoredStars:
the L hdmi cables work great on my tv and receiver. so much less stress on the ports using them...