Homebrew ARM9Loader -- Technical Details and Discussion

[Billy Acuña]

Anyone tried to run rxtools with the bootloader?

 

[Supster131]

Anyone tried to run rxtools with the bootloader?

It won't work. The bootloader will only work with things that natively support A9LH.

 

[DQScott95]

Now that I think about it, since it's possible to prevent Native FIRM updates, shouldn't it be possible to redirect and write the new udpated Native FIRM onto the SD card so we wouldn't have to manually update it when that happens?

It patches the FIRM1 and FIRM0 not the Native_FIRM

 

[Mrrraou]

It patches the FIRM1 and FIRM0 not the Native_FIRM

AuReiNAND patches FIRM0/FIRM1 partitions updating*

Anyone tried to run rxtools with the bootloader?

Won't work, MPU settings aren't updated yet, IIRC. However, the Pasta team is working on it.

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

I don;t get this. Doesn't running Aureinand cfw with arm9lh enable sig patches on sysnand?

It does: you have to edit Spider to have the same TID and version as Skater.

 

[max_505]

I configured BootCTR already so I can automatically boot to emunand or hold R and boot Decrypt9, but for some reason sysnand doesn't load anymore when I hold L (sysnand loads again as long as I don't use BootCTR and the config_ini file, so that must be the cause). What might be the cause?

Here's what I typed on my config_ini file:

[DEFAULT] path = /rei/arm9loaderhax.bin delay = 0 offset = 0 payload = -1 screenEnabled = 0

[KEY_START] path = /A9LHpayloads/Decrypt9WIP.bin delay = 0 offset = 0 payload = -1 screenEnabled = 0

 

[Mrrraou]

I configured BootCTR already so I can automatically boot to emunand or hold R and boot Decrypt9, but for some reason sysnand doesn't load anymore when I hold L (sysnand loads again as long as I don't use BootCTR and the config_ini file, so that must be the cause). What might be the cause?

Here's what I typed on my config_ini file:

[DEFAULT] path = /rei/arm9loaderhax.bin delay = 0 offset = 0 payload = -1 screenEnabled = 0

[KEY_START] path = /A9LHpayloads/Decrypt9WIP.bin delay = 0 offset = 0 payload = -1 screenEnabled = 0

BootCTR

Really, you shouldn't use BootCTR yet. It's still really buggy. I think that the issue is that it can't find a KEY_L entry, so it fails.

 

[roflpwnt]

I configured BootCTR already so I can automatically boot to emunand or hold R and boot Decrypt9, but for some reason sysnand doesn't load anymore when I hold L (sysnand loads again as long as I don't use BootCTR and the config_ini file, so that must be the cause). What might be the cause?

Here's what I typed on my config_ini file:

[DEFAULT] path = /rei/arm9loaderhax.bin delay = 0 offset = 0 payload = -1 screenEnabled = 0

[KEY_START] path = /A9LHpayloads/Decrypt9WIP.bin delay = 0 offset = 0 payload = -1 screenEnabled = 0

Change delay to 200?

 

[GinkREAL]

Anyone tried to run rxtools with the bootloader?

Yes it works for me, but the beta 2 version on github doesnt. Not sure what version of rxtools mine is though, I just used whatever was already installed

 

[capito27]

Yes it works for me, but the beta 2 version on github doesnt. Not sure what version of rxtools mine is though, I just used whatever was already installed

this is litterally impossible, so if you think otherwise, please send me a copy of your arm9loaderhax.bin and rxtools folder per pm, otherwise stop

 

[DQScott95]

I configured BootCTR already so I can automatically boot to emunand or hold R and boot Decrypt9, but for some reason sysnand doesn't load anymore when I hold L (sysnand loads again as long as I don't use BootCTR and the config_ini file, so that must be the cause). What might be the cause?

Here's what I typed on my config_ini file:

[DEFAULT] path = /rei/arm9loaderhax.bin delay = 0 offset = 0 payload = -1 screenEnabled = 0

[KEY_START] path = /A9LHpayloads/Decrypt9WIP.bin delay = 0 offset = 0 payload = -1 screenEnabled = 0

I am pretty sure you need the KEY_L entry for it to work if you are using bootctr, just point it to the rei/firmware90.bin (assuming your sysNAND is on 9.2)

 

[Mrrraou]

I am pretty sure you need the KEY_L entry for it to work if you are using bootctr, just point it to the rei/firmware90.bin (assuming your sysNAND is on 9.2)

Nope ! that won't work! A FIRM isn't a Brahma/ARM9 payload.

 

[DQScott95]

Hmm thats odd then because I am using Bootctr right now and it autoloads emuNAND, load sysNAND on L hold, and boots decrpyt9 on A hold.

Edit: I guess I dont even have a KEY_L entry in mine and it still works

[DEFAULT]
path = /rei/arm9loaderhax.bin
delay = 2000
offset = 0
payload = -1


[KEY_R]
path = /arm9loaderhax.bin
delay = 2000
offset = 0
payload = -1


[KEY_A]
path = /Decrypt9WIP.bin
screenEnabled = 1
delay = 100
offset = 0
payload = -1

 

[AkGBA]

Seeing that, with L, that's aureinand booting, not bootCTR.

 

[Ekaitz]

Really strange, I use BootCTR9 with a 0ms delay and it works well for everything. (Booting sysnand/Emunand/Decrypt9/update.bin (to update the A9LH payload))

 

[DQScott95]

Really strange, I use BootCTR9 with a 0ms delay and it works well for everything. (Booting sysnand/Emunand/Decrypt9/update.bin (to update the A9LH payload))

May I ask what the update.bin used to update the a9lh payload is from? I never saw it mentioned in the original guide when I installed my a9lh and then updated it using the installer.bin

 

[Ekaitz]

May I ask what the update.bin used to update the a9lh payload is from? I never saw it mentioned in the original guide when I installed my a9lh and then updated it using the installer.bin

It is available on Arm9LoaderHax thread, it allows people to update from the first payload to the payload that have screen_init. I kept the entry in my boot config, thinking that it might be useful again in the future.

 

[Mrrraou]

It is available on Arm9LoaderHax thread, it allows people to update from the first payload to the payload that have screen_init. I kept the entry in my boot config, thinking that it might be useful again in the future.

It actually updates the stage2 payload on NAND with the file "stage0x5C000.bin" from the SD.

 

[DQScott95]

It is available on Arm9LoaderHax thread, it allows people to update from the first payload to the payload that have screen_init. I kept the entry in my boot config, thinking that it might be useful again in the future.

Could you possibly link me to one of the new compiling guides so i can recompoile an updated a9lh.3dsx? I am thinking about switching to sysNAND and just need to have and updated arm9loaderhax installer with screen init and all that. And I guess there are a bunch of forks so i dont know which one to use xp

 

[Mrrraou]

Could you possibly link me to one of the new compiling guides so i can recompoile an updated a9lh.3dsx? I am thinking about switching to sysNAND and just need to have and updated arm9loaderhax installer with screen init and all that. And I guess there are a bunch of forks so i dont know which one to use xp

The original arm9loaderhax repo (delebile's repo) now has @dark_samus3's screen init.

 

[DQScott95]

The original arm9loaderhax repo (delebile's repo) now has @dark_samus3's screen init.

When I used that one to compile it didnt finish because it couldnt find the new3ds90 file in the data_input folder. I dont understand why they werent included in this package, should I just copy them to the input folder in the new package from my old one?