Homebrew [RELEASE] The BootCTR9 release thread

[RednaxelaNnamtra]

is there a reason why the boot animation i use looks fuzzy and low quality (and some of the others i've used play too fast)

Is the animation configuration file named correctly? [animationname].cfg for an plaintext file or [animationname].cfgb for an binary config, like its defined here.

 

[RandomMan25XX]

the animation i'm currently using didn't come with a config file

 

[RednaxelaNnamtra]

the animation i'm currently using didn't come with a config file

For the animations that are running to fast, try to create a plaintext config file to set the fps, and maybe it could also help fixing the other problem.

 

[RandomMan25XX]

i've made one but it hasn't changed the fps or anything

 

[RednaxelaNnamtra]

i've made one but it hasn't changed the fps or anything

How did you name the config and the animation?
If the animation is named "3ds.anim" the config need to be named "3ds.anim.cfg"

 

[RandomMan25XX]

the animation and config file are named the same as was specified in the guide you linked me to

 

[Deleted User]

You just need to set the boot splash in the main configuration to 0 to disable it, as it is documented here

Thanks.I was wondering if that could be disabled.

 

[Derpyderp]

So im running B9S and have a custom ini set to /luma/animation/anim and /luma/payloads/luma.firm and have put the ini file in the root of my sd and same for the boot.firm file and my anim files are in the anim folder but when ever i boot my 3ds it just shows a screen with boot9strap and then some text underneath it and the animation i have is not playing at all

 

[RednaxelaNnamtra]

So im running B9S and have a custom ini set to /luma/animation/anim and /luma/payloads/luma.firm and have put the ini file in the root of my sd and same for the boot.firm file and my anim files are in the anim folder but when ever i boot my 3ds it just shows a screen with boot9strap and then some text underneath it and the animation i have is not playing at all

It seems you are pointing to a folder in your config, but you need point directly to the animation file

 

[Derpyderp]

It seems you are pointing to a folder in your config, but you need point directly to the animation file

so then would it need to be /luma/animation/anim/<the animations folder>

 

[Derpyderp]

Wew finally thanks for the help i was going crazy not knowing what i was doing wrong xD

 

[Kazuma77]

Here is a first b9s 1.2 compatible dev build.

This dev-release only include a firm, since the .bin build is not yet running.

The next targes will be more code cleanup and getting the a9lh payload running again on a9lh.

I will also try to get the gateway payload running directly, but Gateway should maybe release a updated payload, since it should not be that hard for them.

Awesome release. Works great with Gateway. Surprisingly, it also gets Puma working too. You still need to point path.txt to a .bin copy to get reboot patches to work right, but, it works. Nice job. Now, if you could just figure out what Salt's hangup is, we'd have every A9LH payload working in B9S (well, I haven't tried converting Uncart or AGBSave9, but there's really no point). I know, Salt is currently dead because the author bricked his device. I'd offer to take it over, having a hard modded device and all, but I'm no coder. The closest I get are my non-keymapping AHK scripts for pseudo direct movement in non-import PC APRGs.

Just one question. If, say, I wanted to build a second copy that uses a different .ini file, what options would I use in firmtool? The example commands don't seem to work at all. In case you're wondering why, I'm using mini BootCTR9 configs to fix CFWs that aren't working in other chain loaders (again). CBM9 can patch it in memory, of course, so I've already got that working with separate .ini files that directly launch GW and Puma. But I'm anticipating having this issue with other chain loaders. I know, I should probably just be like "you're using BootCTR9, because it just works" but my AIO packs have always been about providing choices (which is why I was hoping someone had coded an updated A9LH installer for B9S, looks like no such luck).

P.S. It's good to see that some developers actually care whether their .bin build works or not (maybe if said A9LH installer existed, more devs would check them).

 

[RednaxelaNnamtra]

Awesome release. Works great with Gateway. Surprisingly, it also gets Puma working too. You still need to point path.txt to a .bin copy to get reboot patches to work right, but, it works. Nice job. Now, if you could just figure out what Salt's hangup is, we'd have every A9LH payload working in B9S (well, I haven't tried converting Uncart or AGBSave9, but there's really no point). I know, Salt is currently dead because the author bricked his device. I'd offer to take it over, having a hard modded device and all, but I'm no coder. The closest I get are my non-keymapping AHK scripts for pseudo direct movement in non-import PC APRGs.

Just one question. If, say, I wanted to build a second copy that uses a different .ini file, what options would I use in firmtool? The example commands don't seem to work at all. In case you're wondering why, I'm using mini BootCTR9 configs to fix CFWs that aren't working in other chain loaders (again). CBM9 can patch it in memory, of course, so I've already got that working with separate .ini files that directly launch GW and Puma. But I'm anticipating having this issue with other chain loaders. I know, I should probably just be like "you're using BootCTR9, because it just works" but my AIO packs have always been about providing choices (which is why I was hoping someone had coded an updated A9LH installer for B9S, looks like no such luck).

P.S. It's good to see that some developers actually care whether their .bin build works or not (maybe if said A9LH installer existed, more devs would check them).

Currently the master source on github is not compatible. Since I have not cleaned up the source yet, I have not pushed the latest changes currently, but I will try to do it in the near future.
Also sorry for the late answer ^^'

 

[Marax]

My 3DS with Boot9Strap only Displays the Top display :c Help ?

 

[pietempgba]

My 3DS with Boot9Strap only Displays the Top display :c Help ?

that's how it's supposed to be bootctr9 can't display the bottom screen do to something

 

[MidgeThePidge]

When do you think we will be able to have an animation play on the bottom screen on boot9strap?

 

[Alex S]

@RednaxelaNnamtra would you be able to make a build for luma 8.1? I heavily depend on the fixes added in 8.1

 

[RednaxelaNnamtra]

@RednaxelaNnamtra would you be able to make a build for luma 8.1? I heavily depend on the fixes added in 8.1

this build should work, but it seams there was a issue with the cache, which sometimes caused the unsupported location screen. Should be fixed with the next release.

 

[Alex S]

this build should work, but it seams there was a issue with the cache, which sometimes caused the unsupported location screen. Should be fixed with the next release.

that build is the issue... its luma 8.0 and i cant use it because of that...

 

[RednaxelaNnamtra]

that build is the issue... its luma 8.0 and i cant use it because of that...

You could try his build, maybe it will work better, but im still within cleaning up the code, so there could be bugs ^^