Hacking A9LH choose bin file to load?

[Keylogger]

Hello,

I don't want to autoboot my N3ds to Luma but I want a bootloader that let me choose wich .bin file to load from my SD card.

Is it possible to do that?

 

[Temptress Cerise]

Something like CTRBoptManager9? It has a GUI interface that lets you pick the file you want. I'd look into that and its many branches.

 

[Keylogger]

Something like CTRBoptManager9? It has a GUI interface that lets you pick the file you want. I'd look into that and its many branches.

I tried CTRbootmanager9 but I have a black screen on boot

 

[Temptress Cerise]

Are you using v2 A9LH? I have heard it breaks CtrBootManager9.

 

[Kyojin]

Are you using v2 A9LH? I have heard it breaks CtrBootManager9.

^ This... or a no screen init version of A9LH?

 

[Keylogger]

^ This... or a no screen init version of A9LH?

yes I'm using V2... Any alternative for V2?

 

[Kyojin]

yes I'm using V2... Any alternative for V2?

Did you install Aurora Wright's fork? She fixed that issue two days ago. If not, you'll have to use that, installing it with SafeA9LHInstaller v2.0.1.

Remember to use the "new" firm0, not the one used for the old A9LH version (if you want to be sure you are using the correct one, you can get firm0 and firm1 from the data_input_v2.zip file from Plailect's guide, part 5).

 

[Urbanshadow]

Luma has it's own bootloader integrated. just name your payload "start_<anyname>.bin" and put it in the Luma/Bootloader folder.

if you Start+boot it should automatically boot that. Luma initializes the screen so you could use that to boot ctrbootmanager9 in boot menu mode and should work.

 

[Keylogger]

Did you install Aurora Wright's fork? She fixed that issue two days ago. If not, you'll have to use that, installing it with SafeA9LHInstaller v2.0.1.

Remember to use the "new" firm0, not the one used for the old A9LH version (if you want to be sure you are using the correct one, you can get firm0 and firm1 from the data_input_v2.zip file from Plailect's guide, part 5).

I installed the aurora wright's fork! Strange because if I put ctrbootmanager9 in SD:\luma\payloads and rename it to start_ctrboot.bin , it boots when I press START at boot.
But if I want to autoboot it so I put it as arm9loaderhax.bin is the SD root, I won't boot and I have a black screen

 

[Kyojin]

I installed the aurora wright's fork! Strange because if I put ctrbootmanager9 in SD:\luma\payloads and rename it to start_ctrboot.bin , it boots when I press START at boot.
But if I want to autoboot it so I put it as arm9loaderhax.bin is the SD root, I won't boot and I have a black screen

Then you installed the noscreeninit version.

EDIT: it means that if the ARM9 binary you are trying to load does not init the screen, you won't see anything displayed (hence the black screen). Luma3DS, on the other hand, initializes the screen and that's why CTRBootManager9 works when chainloaded from Luma.

If you want to be able to use it, you'll have to flash the screeninit version instead.

 

[Keylogger]

Then you installed the noscreeninit version.

EDIT: it means that if the ARM9 binary you are trying to load does not init the screen, you won't see anything displayed (hence the black screen). Luma3DS, on the other hand, initializes the screen and that's why CTRBootManager9 works when chainloaded from Luma.

If you want to be able to use it, you'll have to flash the screeninit version instead.

I installed the screeninit version! My screen flashes for a second when powering ON but then the screen stays black :/

 

[Kyojin]

I installed the screeninit version! My screen flashes for a second when powering ON but then the screen stays black :/

Oh... And if you set Decrypt9 or Hourglass9 as your arm9loaderhax.bin, does it load or does it stay on a black screen too?

 

[Keylogger]

D9, emunand9 load fine. Only CTRbootmanager and GW won't boot (black screen)

 

[Temptress Cerise]

v2 A9LH broke some stuff. Either wait for those payloads to update to support v2 or switch to v1 A9LH.

 

[Keylogger]

v2 A9LH broke some stuff. Either wait for those payloads to update to support v2 or switch to v1 A9LH.

Yeah I want to switch to V1, do you know where can I found payload_input and data_input v1 files? They are updated in the Plailect guide

 

[Temptress Cerise]

Yeah I want to switch to V1, do you know where can I found payload_input and data_input v1 files? They are updated in the Plailect guide

Use an older revision of the guide to find the files.
Link: https://github.com/Plailect/Guide/wiki/Part-5-(arm9loaderhax)

At the top, under the title, you'll see "xxx revisions" with xxx is being the number of past revisions made. Then, it'll take you to it's history page of past revisions, then look for one that has the v1 payloads.

Be sure to use the proper SafeA9LHInstaller for v1 files, and make sure you have everything you need to use said installer. I take no responsibility if you brick.

 

[Kyojin]

Yeah I want to switch to V1, do you know where can I found payload_input and data_input v1 files? They are updated in the Plailect guide

About going back from v2 to v1 (read from bottom to top):



Did you already ask in the CTRBootManager9 thread to see if it is a systematic issue?

If you are 100% sure that you installed Aurora's screeninit version from 3 days ago, and unless you really NEED to use CTRBootManager9, you could open up an issue either on Aurora's repo, or on CTRBootManager9's repo to notify about this and investigate.

EDIT: there is already an open issue, and also a temp fix.

 

[Temptress Cerise]

About going back from v2 to v1 (read from bottom to top):

View attachment 52657

Did you already ask in the CTRBootManager9 thread to see if it is a systematic issue?

If you are 100% sure that you installed Aurora's screeninit version from 3 days ago, and unless you really NEED to use CTRBootManager9, you could open up an issue either on Aurora's repo, or on CTRBootManager9's repo to notify about this and investigate.

EDIT: there is already an open issue, and also a temp fix.

Ah, thanks for that info.

Then one needs to go back to a Clean 9.0-9.2 sysNAND backup, then flash v1 A9LH from there, right?

So OP needs to use Decrypt9 and flash that clean backup, then install v1 A9LH.

Or try using the unofficial v7/v8 CTRBootManager9 if they don't want to go through that.

Anyways, GW's a9lh.bin is also broken on v2, so I am not upgrading to v2 anytime soon.

 

[Kyojin]

Ah, thanks for that info.

Then one needs to go back to a Clean 9.0-9.2 sysNAND backup, then flash v1 A9LH from there, right?

So OP needs to use Decrypt9 and flash that clean backup, then install v1 A9LH.

Or try using the unofficial v7/v8 CTRBootManager9 if they don't want to go through that.

Anyways, GW's a9lh.bin is also broken on v2, so I am not upgrading to v2 anytime soon.

Yes, going back to 9.2 on a pre-A9LH backup should do the trick. And same, not updating until it's really worth it.

 

[The Real Jdbye]

Ah, thanks for that info.

Then one needs to go back to a Clean 9.0-9.2 sysNAND backup, then flash v1 A9LH from there, right?

So OP needs to use Decrypt9 and flash that clean backup, then install v1 A9LH.

Or try using the unofficial v7/v8 CTRBootManager9 if they don't want to go through that.

Anyways, GW's a9lh.bin is also broken on v2, so I am not upgrading to v2 anytime soon.

I hear GW works with delebile's a9lh version but the install process is a bit different to SafeA9LHInstaller so I haven't bothered. Nothing wrong with staying on V1 for now.