I tried CTRbootmanager9 but I have a black screen on bootSomething like CTRBoptManager9? It has a GUI interface that lets you pick the file you want. I'd look into that and its many branches.
^ This... or a no screen init version of A9LH?Are you using v2 A9LH? I have heard it breaks CtrBootManager9.
yes I'm using V2... Any alternative for V2?^ This... or a no screen init version of A9LH?
yes I'm using V2... Any alternative for V2?
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.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
I installed the screeninit version! My screen flashes for a second when powering ON but then the screen stays black :/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 :/
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 guidev2 A9LH broke some stuff. Either wait for those payloads to update to support v2 or switch to v1 A9LH.
Use an older revision of the guide to find the files.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
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
Ah, thanks for that info.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.
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.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.