Hacking BootAnim9 not working?

[ArviDroid]

Hi.
I´m trying to use BootAnim9 but I just can´t make the animation appear! I download the files, rename my "arm9loaderhax" to "arm9payload" and place it in the anim folder, place the downloaded payload at the root and acquire my boot animation named "anim" and put it in the anim folder and I create a folder within anim titled "0" where I put my animation. Could someone tell me what I´m doing wrong? I have an O3DS with Luma, fw.11.1. Help would be much appreciated.

 

[JCCG1989]

Is your arm9loaderhax installed with the SD-less version

 

[ArviDroid]

Is your arm9loaderhax installed with the SD-less version

I used Plailects guide. So no?

 

[JCCG1989]

Does your "Nintendo 3DS ReiNAND" banner shows at the start of the boot?

 

[ArviDroid]

Does your "Nintendo 3DS ReiNAND" banner shows at the start of the boot?

I don´t have ReiNAND
EDIT: No, even if I wouldn´t need to have it.

 

[Aletron9000]

I don´t have ReiNAND
EDIT: No, even if I wouldn´t need to have it.

Do you have screen-init a9lh installed?

 

[JCCG1989]

I don´t have ReiNAND
EDIT: No, even if I wouldn´t need to have it.

Dude, don't play the smartass to people trying to help you, if you used Plailect's guide then you have arm9lh and Luma and "Nintendo 3DS ReiNAND" banner is the common used by Luma.

If that banner does NOT show up it means you have a NO screeen-init arm9lh and thats the origin of your problem.

 

[ArviDroid]

Dude, don't play the smartass to people trying to help you, if you used Plailect's guide then you have arm9lh and Luma and "Nintendo 3DS ReiNAND" banner is the common used by Luma.

If that banner does NOT show up it means you have a NO screeen-init arm9lh and thats the origin of your problem.

I´m sorry, I didn´t mean anything bad by it. I´m a Noob so I thought that I didn´t have ReiNAND. I followed the guide which would mean that I have no screen-init, right? Once again, I´m sorry, I didn´t try to be a smartass. I think it was just a missunderstanding!

 

[JCCG1989]

I´m sorry, I didn´t mean anything bad by it. I´m a Noob so I thought that I didn´t have ReiNAND. I followed the guide which would mean that I have no screen-init, right? Once again, I´m sorry, I didn´t try to be a smartass. I think it was just a missunderstanding!

OK dude, feel free to ask... So... does the banner shows?

 

[ArviDroid]

OK dude, feel free to ask... So... does the banner shows?

Well, no. As far as I could see the screen was just black.

 

[hyprskllz]

Have you tried renaming arm9loaderhax.bin to arm9loaderhax_si.bin?

 

[ih8ih8sn0w]

Well, no. As far as I could see the screen was just black.

When did you follow the guide? And are you sure you installed screeninit a9lh?

 

[ArviDroid]

When did you follow the guide? And are you sure you installed screeninit a9lh?

I followed the guide in september. I'm 99% sure I used NO screeninit.

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

Have you tried renaming arm9loaderhax.bin to arm9loaderhax_si.bin?

I haven't tried that.

 

[hyprskllz]

I followed the guide in september. I'm 99% sure I used NO screeninit.

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


I haven't tried that.

You should try it to see if renaming works. If it's not working, then you have noscreeninit for sure.
After that, you can try updating a9lh with the merged build.

 

[ArviDroid]

You should try it to see if renaming works. If it's not working, then you have noscreeninit for sure.
After that, you can try updating a9lh with the merged build.

Okay, perhaps I'll try that! Thanks. Why would you want me to update A9LH though?

 

[el_gonz87]

Okay, perhaps I'll try that! Thanks. Why would you want me to update A9LH though?

Because no screen init and screen init A9LH got merged in October, the latest 2 releases are just 1 bin where screen init is controlled by filename "_si" suffix.

You will have to update to get it to work since your version is no screen init exclusively (i think June version had them as two separate forks). Follow the instructions on plailect section updating A9LH.

 

[ArviDroid]

Because no screen init and screen init A9LH got merged in October, the latest 2 releases are just 1 bin where screen init is controlled by filename "_si" suffix.

You will have to update to get it to work since your version is no screen init exclusively. Follow the instructions on plailect section updating A9LH.

Okay nice! Thanks! One more question: will you be able to use A9LH without a SD card?

 

[el_gonz87]

Okay nice! Thanks! One more question: will you be able to use A9LH without a SD card?

Yes latest version has the code to boot from CTRNAND partition, but you will have to inject Luma arm9loaderhax.bin into the root of CTRNAND using GodMode9 or FBI.

 

[ArviDroid]

Yes latest version has the code to boot from CTRNAND partition, but you will have to inject Luma arm9loaderhax.bin into the root of CTRNAND using GodMode9 or FBI.

One last question (hopefully). Are there any risks of bricking while updating A9LH?

 

[Aletron9000]

One last question (hopefully). Are there any risks of bricking while updating A9LH?

yes, such as corrupt payloads