Homebrew ARM9Loader -- Technical Details and Discussion

[nintendowii]

Is there any way to hide the text that flashes for a split second at the bottom screen when you boot using BootCTR9? I'm using the latest one (Arm9 bootloader v0.4.1 Alpha).

i've had the same problem and i use now the following settings at boot_config.ini. the second entry [KEY_L] with cakes.dat is for enter the menu, because if you set screenEnabled = 0 you can't see the menu of CakesFW.

[BOOTCTR9]
screenEnabled = 0
screenLog = 0
fileLog = 0
key_delay = 1000

[DEFAULT]
path = /a9lh/Cakes.dat
screenEnabled = 0
delay = 200
offset = 0x12000
payload = -1

[KEY_L]
path = /a9lh/Cakes.dat
screenEnabled = 1
delay = 200
offset = 0x12000
payload = -1

 

[max_505]

Don't enable the screen.

i've had the same problem and i use now the following settings at boot_config.ini. the second entry [KEY_L] with cakes.dat is for enter the menu, because if you set screenEnabled = 0 you can't see the menu of CakesFW.

Those worked. Thanks a lot! Now it doesn't look like it's hacked anymore

 

[RednaxelaNnamtra]

Here is a new BootCtr9 dev build
I added some softboot feature, like fast softboot to the latest selection(enableAutosoftboot), and the possibility to disable splashes at softboot(enableSoftbootSplash).

 

[Deleted member 373223]

Here is a new BootCTR9 dev build
I added some softboot feature, like fast softboot to the latest selection(enableAutosoftboot), and the possibility to disable splashes at softboot(enableSoftbootSplash).

i would like to know how to remove the log on the screen thanks

 

[RednaxelaNnamtra]

i would like to know how to remove the log on the screen thanks

If you use a newer bootctr9 version from github the log should be disabled, but you could also set "screenLog" = 0 in then "[BOOTCTR9]" section(see 3 posts before yours).

 

[Deleted member 373223]

If you use a newer bootctr9 version from github the log should be disbaled, but you could also set "screenLog" = 0 in then "[BOOTCTR9]" section(see 3 posts before yours).

oh, thanks" didn't know there was a new version! i were using the third version!

 

[RednaxelaNnamtra]

oh, thanks" didn't know there was a new version! i were using the third version!

The releases will mostly be done on github, and here in the thread announced atm. But when I think its ready for version 1.0, I will make a own thread for bootctr9

 

[Yudowat]

That means you aren't using a 9.0 FIRM.

What CFW are you using?

If AuReiNAND, press L when booting, then it should work.

going back to this, i just compiled mine again and a friends OTP, and neither have the SD auto shutdown thing, and my friend's was his first install of anything A9LH but i just got the latest master from dark-samus github. Both installs work completely fine otherwise however. And one more thing, my 3ds cannot boot while holding L for some reason. I dont use just one firmware.bin ive got both but i always end up blackscreened when holding L

 

[fr3quency]

Anyone got the updater to update a9lh using dark-samus's github commits?(all the latest ones)

 

[BurningDesire]

Anyone got the updater to update a9lh using dark-samus's github commits?(all the latest ones)

Updater? For what?

 

[PedroPVJ]

Anyone got the updater to update a9lh using dark-samus's github commits?(all the latest ones)

https://gbatemp.net/attachments/installer-zip.40329/

 

[peteruk]

https://gbatemp.net/attachments/installer-zip.40329/

what is the change with this one ?

 

[PedroPVJ]

what is the change with this one ?

it isn't a new version

 

[fr3quency]

it isn't a new version

What do you mean it's not a new version? Will I be able to update up to commit 1ee8d88?

 

[noctis90210]

What do you mean it's not a new version? Will I be able to update up to commit 1ee8d88?

are there any new updates on this new version?

 

[Supster131]

What do you mean it's not a new version? Will I be able to update up to commit 1ee8d88?

No, and it's not recommended to.
Dark Samus' fork is more so a testing fork. Internally lots of bricks have happened when using his fork.

It's recommended for the regular user to use Delebile's version.

 

[PedroPVJ]

What do you mean it's not a new version? Will I be able to update up to commit 1ee8d88?

all a9lh commits until now are supported by that same updater

No, and it's not recommended to.
Dark Samus' fork is more so a testing fork. Internally lots of bricks have happened when using his fork.

It's recommended for the regular user to use Delebile's version.

i'm using dark-samus's latest commit and it is working just fine

 

[Supster131]

all a9lh commits until now are supported by that same updater


i'm using dark-samus's latest commit and it is working just fine

It's a hit or miss really. Some builds are safe to update to (even though they probably don't add new features), while other builds are not so safe to update it.

 

[PedroPVJ]

are there any new updates on this new version?

"Latest commit 1ee8d88 6 days ago dark-samus fix SD card delay, and move screenInit() - Annon contrib."
Nothing practical

It's a hit or miss really. Some builds are safe to update to (even though they probably don't add new features), while other builds are not so safe to update it.

i'll be more careful then

 

[Serphirot]

all a9lh commits until now are supported by that same updater


i'm using dark-samus's latest commit and it is working just fine

@dark_samus3 him self wrote that you shouldn´t use his test version of a9lh if you don´t know what you are doing and how to fix it if you got an unusable build or something went wrong.
It is recommended to wait for @delebile ´s version because the tested and save stuff from dark samus gets integrated there.