Homebrew [RELEASE] The BootCTR9 release thread

[RednaxelaNnamtra]

How exactly do I set this up to get boot animations with B9S? Like where do I put the files on my SD card?

Everything except the config file, which needs to be in one of the supported folders listet here or "sighax" or "boot9strap", can be where you want to put it, because you set them in the config file.
For more informations about the usage check out the wiki (and especially this) and the example config inside of he zip

 

[TheCyberQuake]

Here is a first BootCTR firm build for usage with sighax.

It boots .firm and some arm9loaderhax payloads (decrypt 9 started, while gw is not).

To load a firm payload set payload to 2(firm) or -1 (auto)

Just gave it a test. So far everything is working properly. Good work.

 

[duffmmann]

I'm trying to get this working properly, can anyone help me. I'm on B9S, do I put boot.firm on the root of my SD or in /luma/payloads (if it is on the root, do I move the boot.firm already in the root somewhere else or rename it or something)?

Then, it sounds like boot_config.ini can sit in the root of the SD card, is that true? And if I want to load the animation from /anim/0 (where my animation rests from boot9anim), where exactly do I change that in the boot_config.ini file?

I'm sorry I'm a little dumb with this kind of stuff, but I'm really struggling to get this done right.

 

[TheCyberQuake]

I'm trying to get this working properly, can anyone help me. I'm on B9S, do I put boot.firm on the root of my SD or in /luma/payloads (if it is on the root, do I move the boot.firm already in the root somewhere else or rename it or something)?

Then, it sounds like boot_config.ini can sit in the root of the SD card, is that true? And if I want to load the animation from /anim/0 (where my animation rests from boot9anim), where exactly do I change that in the boot_config.ini file?

I'm sorry I'm a little dumb with this kind of stuff, but I'm really struggling to get this done right.

I renamed luma's boot.firm to luma.firm, placed the CTRBoot9 boot.firm on the root, and then changed the [DEFAULT] section of boot_config.ini to change path to /luma.firm

 

[duffmmann]

I renamed luma's boot.firm to luma.firm, placed the CTRBoot9 boot.firm on the root, and then changed the [DEFAULT] section of boot_config.ini to change path to /luma.firm

I've done that, but i get the message that an error is found in the config file. I can't figure out what the error would be. I removed the ; before the luma boot animation section, so I'm really not sure what I'm missing here.

 

[RednaxelaNnamtra]

I'm trying to get this working properly, can anyone help me. I'm on B9S, do I put boot.firm on the root of my SD or in /luma/payloads (if it is on the root, do I move the boot.firm already in the root somewhere else or rename it or something)?

Then, it sounds like boot_config.ini can sit in the root of the SD card, is that true? And if I want to load the animation from /anim/0 (where my animation rests from boot9anim), where exactly do I change that in the boot_config.ini file?

I'm sorry I'm a little dumb with this kind of stuff, but I'm really struggling to get this done right.

Like TheCyberQuake said, just put BootCTR9's boot.firm on the root of your sd-card and rename the boot.firm from luma like you want it.
I named it luma.firm and moved it to the boot9strap folder, in which case it would look like this:

[DEFAULT]
path = /boot9strap/luma.firm
delay = 1000
splash = 4
splash_image = /anim/0

The delay in ms is to allow you to press a key before the payload is loaded. One example would be select to open the luma settings.

Also for support requests like that please use the support thread to keep the release thread clean ^^

--------------------- MERGED ---------------------------

I've done that, but i get the message that an error is found in the config file. I can't figure out what the error would be. I removed the ; before the luma boot animation section, so I'm really not sure what I'm missing here.

Please post the content of your config file in the support thread, this way we can check it out

 

[RednaxelaNnamtra]

Example config file in the latest dev release is now fixed.

Thanks to @TheCyberQuake for finding the problem.

 

[Stack3r]

Today I would like to release the Pre 1.0 version of BootCTR9.

This version adds support for boot animations and adds boot passwords, fast softboots, luma payload patching and more.

For a full feature list and informations about the usage check out the github wiki.

What is BootCTR9:

• BootCTR9 is an ARM9 bootloader for the 3DS System. It's based on BootCTR and its configuration, but with some additional features.

Downloads:

• Sourcecode
• Release

Dev-releases

• Sighax compatible build here.

What I should not post here:

• Feature discussions - this should be done in Github issues
• Support requests - they should be posted in the Support thread

Awesome thanks for this!, btw github wiki link in the op is not working, the one on the download page works fine

 

[RednaxelaNnamtra]

Awesome thanks for this!, btw github wiki link in the op is not working, the one on the download page works fine

thanks, fixed it

 

[RaikouKun]

How exactly do I set this up to get boot animations with B9S? Like where do I put the files on my SD card?

Readme.txt:

Use github wiki to find out more about the usage:
https://github.com/hartmannaf/BootCtr9/wiki

 

[duffmmann]

Readme.txt:

Use github wiki to find out more about the usage:
https://github.com/hartmannaf/BootCtr9/wiki

No need for that at this point, I was able to figure it out in the Support thread. Thanks!

 

[Vandes]

This zip also includes arm9loader binarys, which should in theory be able to load firm binarys, but keep in mind, every payload depending on the otp will not work from a9lh.

Bit of clarification needed:

1) This means that I can load this new version of BootCTR9 with my existing a9lh install and potentially chainload one of the future .firm Luma versions without upgrading to B9S?

2) What about the opposite? I mean, upgrading my console to B9S, and using BootCTR9 to chainload older a9lh .bin payloads?

Thanks!

 

[RednaxelaNnamtra]

Bit of clarification needed:

1) This means that I can load this new version of BootCTR9 with my existing a9lh install and potentially chainload one of the future .firm Luma versions without upgrading to B9S?

2) What about the opposite? I mean, upgrading my console to B9S, and using BootCTR9 to chainload older a9lh .bin payloads?

Thanks!

1) if luma uses the otp and the secret key sector to get the keys for the firmware, then its not possible, but everyting that works witout access to the otp ,secretkeysector or bootrom should work, but I have not testet it yet.

2) yes, most older a9lh payloads should work.

 

[Vandes]

1) if luma uses the otp and the secret key sector to get the keys for the firmware, then its not possible, but everyting that works witout access to the otp ,secretkeysector or bootrom should work, but I have not testet it yet.

2) yes, most older a9lh payloads should work.

1) right.
2) ...but not gateway, right? I think that's the only payload that risks not being updated to .firm, and I would like to keep access to gw just in case.

 

[RednaxelaNnamtra]

1) right.
2) ...but not gateway, right? I think that's the only payload that risks not being updated to .firm, and I would like to keep access to gw just in case.

There is a way to use the gateway based on the a9lhv2 solution here

 

[Vandes]

There is a way to use the gateway based on the a9lhv2 solution here

Awesome, thanks!

 

[ombus]

where one gets boot animations ?

 

[pietempgba]

@ombus https://gbatemp.net/threads/a9lh-bootanim9-animations-thread.420421/

 

[annson24]

Here is another dev firm build of BootCTR9.

This build should fix a problem with boot animations and added the folders "sighax" and "boot9strap" to the supported folders for the "boot_config.ini" file.

This zip also includes arm9loader binarys, which should in theory be able to load firm binarys, but keep in mind, every payload depending on the otp will not work from a9lh.

Can this be converted to .bin? A friend of mine is still stubborn as fvck and still want to stick too emunand, however, since luma3ds will now only support .firm payloads, she's now stuck on an older firmware. What I'm trying to achieve is to have a .bin chainloader that can chainload .firm payloads. That way, I can chainload the chainloader (wut?) with safehax and I'm a step closer into sleepin..er..having dinner with her.

 

[RednaxelaNnamtra]

Can this be converted to .bin? A friend of mine is still stubborn as fvck and still want to stick too emunand, however, since luma3ds will now only support .firm payloads, she's now stuck on an older firmware. What I'm trying to achieve is to have a .bin chainloader that can chainload .firm payloads. That way, I can chainload the chainloader (wut?) with safehax and I'm a step closer into sleepin..er..having dinner with her.

like I wrote, it contains a a9lh payload, but its not realy testet, and if a firm payload uses the otp or secret key sektor directly it will most likely not run properly, since they are not available in a9lh.
Also he could use the emunand with sighax/boot9strap and luma without any problem.