Homebrew [RELEASE] The BootCTR9 release thread

[RednaxelaNnamtra]

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.
• B9s 1.3 compatible release 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

 

[Xandrid]

This looks very interesting, I need to look into this, good job man

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

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.

Downloads:

• Sourcecode
• Release

Dev-releases

• Currently there are no new dev releases, but they will be posted in this thread.

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

By boot passwords do you mean that when you boot, you have to put in a password to continue or something else?

 

[RednaxelaNnamtra]

This looks very interesting, I need to look into this, good job man

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


By boot passwords do you mean that when you boot, you have to put in a password to continue or something else?

Its to prevent the booting of non default payloads. To boot these the user needs to input a bootpassword/Pin using the 3DS Keys when the feature is enabled.
An example would be something like something like: "KEY_UP KEY_DOWN KEY_DOWN KEY_A" for "Up Down Down A"

 

[Xandrid]

Its to prevent the booting of non default payloads. To boot these the user needs to input a bootpassword/Pin using the 3DS Keys when the feature is enabled.
An example would be something like something like: "KEY_UP KEY_DOWN KEY_DOWN KEY_A" for "Up Down Down A"

Ahhh ok, right right right, very interesting, well now I know what I'm doing to my n3ds today, lol

 

[Deleted User]

HURRAY!! I love this payload!

 

[shoemaker]

It seems that pressing the Start or Select button acts as some kind of stopper for the chainloading, perhaps for people to switch what button they pressed. Is there a way to turn this off? I boot from this into Luma3DS, and there's no way to access the Luma settings (hold Select), because holding Select seems to pause the animation that I've placed on boot. In addition, I have a CTR Boot Manager payload on Start (that way, on boot: Select = Luma Settings, Start = All other A9LH payloads) that doesn't work for the same reason. If I place it on any other button, it works with BootCTR9, but not Start. So, is there a way to turn keep the Start and Select buttons from not booting its payload?

 

[RednaxelaNnamtra]

It seems that pressing the Start or Select button acts as some kind of stopper for the chainloading, perhaps for people to switch what button they pressed. Is there a way to turn this off? I boot from this into Luma3DS, and there's no way to access the Luma settings (hold Select), because holding Select seems to pause the animation that I've placed on boot. In addition, I have a CTR Boot Manager payload on Start (that way, on boot: Select = Luma Settings, Start = All other A9LH payloads) that doesn't work for the same reason. If I place it on any other button, it works with BootCTR9, but not Start. So, is there a way to turn keep the Start and Select buttons from not booting its payload?

Yes, to stop an animation, before its finished, you just need to press START+SELECT. I never had the problem that Lumas settings were shown after stopping an animation, because you need to press it only a short moment to stop the animation, and you can release it directly after that.

And for the start problem, maybe you just need to update the payload you are trying to start with the start key, because start is working for me without any problem.

 

[Naked_Snake]

I hope @Aurora Wright can implement pass codes into luma that would be sweet

 

[RednaxelaNnamtra]

I hope @Aurora Wright can implement pass codes into luma that would be sweet

i think there is a pull request for a 4 key pin system, which is using encryption to hide the pin files contend.

 

[The Catboy]

Because I will not derail another thread for my problems

It should Say more than just boot config error. Could you post your configuration and its path, indluding the filename?

I am using stock boot_config.ini

Comments starts with ";" or "#", so you need to remove it first to the
;line actually do something.

;configuration with ascii boot Image
;You have also 1 sec to press the button for the payload you want to boot
[BOOTCTR9]
key_delay = 1000
boot_splash = 3
enableAutosoftboot = 1
enableArm9CompanionBoot = 1

;Section to allow a9lh net companion payload auto booting
[COMPANION]
path = /a9nc.bin
delay = 100
offset = 0
payload = -1

;luma with BootAnimation and enabled Pathfix
[DEFAULT]
path = /Payloads/luma.bin
delay = 1000
splash = 4
splash_image = /Animations/anim
screenBrightness = 0x30
enablePathFix = 1

;cakes.dat with splash screen and offset
[KEY_R]
path = /Cakes.dat
delay = 1000
offset = 0x12000
splash = 3
splash_image = /Splashes/splash.bin

;Reinand.dat with offset and ascii splash
[KEY_DUP]
path = /ReiNand.dat
delay = 1000
offset = 0x12000
splash = 1

;Each key can be defined using a section, like the example below. Section
;names must be ALL caps, and between "[]". Valid keys:
;You MUST set at least "path" for each section, and it is the ONLY option you
;should set in the majority of cases.
;Double check the path, since it must be correct (including caps).
;Boot examples for almost every CFW out there.
;You can use only binary (.bin, .dat) payloads
;[KEY_A]
;path = /rxTools/sys/code.bin
;[KEY_B]
;path = /Cakes.dat
;[KEY_Y]
;path = /ReiNand.dat
;An important remark: the majority of CFWs set L button to show menu instead
;of autobooting. So it is generally a bad idea to set L button to CFW boot,
;but if you use a delay, you have time to release the key so the CFW menu will
;not be shown.

I made no deviations to the ini file or the file set up and I get the error

[PANIC] Error found in config file, err
Press any key to shutdown

I am running shadowNAND, but this was tested with versions of A9LHv2

 

[RednaxelaNnamtra]

Because I will not derail another thread for my problems

I am using stock boot_config.ini

Comments starts with ";" or "#", so you need to remove it first to the
;line actually do something.

;configuration with ascii boot Image
;You have also 1 sec to press the button for the payload you want to boot
[BOOTCTR9]
key_delay = 1000
boot_splash = 3
enableAutosoftboot = 1
enableArm9CompanionBoot = 1

;Section to allow a9lh net companion payload auto booting
[COMPANION]
path = /a9nc.bin
delay = 100
offset = 0
payload = -1

;luma with BootAnimation and enabled Pathfix
[DEFAULT]
path = /Payloads/luma.bin
delay = 1000
splash = 4
splash_image = /Animations/anim
screenBrightness = 0x30
enablePathFix = 1

;cakes.dat with splash screen and offset
[KEY_R]
path = /Cakes.dat
delay = 1000
offset = 0x12000
splash = 3
splash_image = /Splashes/splash.bin

;Reinand.dat with offset and ascii splash
[KEY_DUP]
path = /ReiNand.dat
delay = 1000
offset = 0x12000
splash = 1

;Each key can be defined using a section, like the example below. Section
;names must be ALL caps, and between "[]". Valid keys:
;You MUST set at least "path" for each section, and it is the ONLY option you
;should set in the majority of cases.
;Double check the path, since it must be correct (including caps).
;Boot examples for almost every CFW out there.
;You can use only binary (.bin, .dat) payloads
;[KEY_A]
;path = /rxTools/sys/code.bin
;[KEY_B]
;path = /Cakes.dat
;[KEY_Y]
;path = /ReiNand.dat
;An important remark: the majority of CFWs set L button to show menu instead
;of autobooting. So it is generally a bad idea to set L button to CFW boot,
;but if you use a delay, you have time to release the key so the CFW menu will
;not be shown.

I made no deviations to the ini file or the file set up and I get the error

[PANIC] Error found in config file, err
Press any key to shutdown

I am running shadowNAND, but this was tested with versions of A9LHv2

Is there a ';' in the beginning of the first line in your config file? If it's not there, it should cause the problem, because BootCTR9 will try to interpret the first line, and doesn't know what to do with it.

Also there is a thread for support requests (even if nobody used it till now)
http://gbatemp.net/threads/support-the-bootctr9-support-thread.435348/

 

[The Catboy]

Is there a ';' in the beginning of the first line in your config file? If it's not there, it should cause the problem, because BootCTR9 will try to interpret the first line, and doesn't know what to do with it.

Also there is a thread for support requests (even if nobody used it till now)
http://gbatemp.net/threads/support-the-bootctr9-support-thread.435348/

I blame gbatemp's shitty search function for me not finding that and because I didn't find it, it's going on my Helpful Homebrew thread!
Also your advice worked!

 

[RednaxelaNnamtra]

I blame gbatemp's shitty search function for me not finding that and because I didn't find it, it's going on my Helpful Homebrew thread!
Also your advice worked!

No problem, but the first post should be able to inform about it.

Also you didn't said if it was realy the problem.

 

[The Catboy]

No problem, but the first post should be able to inform about it.

Also you didn't said if it was realy the problem.

It actually fixed the problem, I added the symbol at the start like you said and now it's working just fine!

 

[azerti1304]

My config file but its not complete.
So i want to boot in Luma, emunand 9 and decrypt 9 with on top a splash screen and at the bottom a anim.

 

[RednaxelaNnamtra]

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)

 

[Deleted User]

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)

What do you name the config so it reads it.

 

[RednaxelaNnamtra]

What do you name the config so it reads it.

the finename needs to be boot_config.ini and it needs to be in one of the supported folders: https://github.com/hartmannaf/BootCtr9/wiki/Usage

Seems I forgot to add it to the wiki, because normaly I make a zip with an example config ^^

 

[RednaxelaNnamtra]

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.

 

[duffmmann]

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.

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