Homebrew [RELEASE] BootAnim9 - Custom boot animations for your 3DS!

  • Thread starter Thread starter Wolfvak
  • Start date Start date
  • Views Views 329,216
  • Replies Replies 1,434
  • Likes Likes 75
Status
Not open for further replies.
One more thing: I accidentally deleted the anim folder from my sd card, and whenever I boot, it says this: "No payload detected. Make sure you have /anim/arm9payload.bin" How do I fix this?
 
One more thing: I accidentally deleted the anim folder from my sd card, and whenever I boot, it says this: "No payload detected. Make sure you have /anim/arm9payload.bin" How do I fix this?
remake the anim folder, put the arm9loaderhax.bin file from the latest luma release inside the anim folder, then rename it to arm9payload.bin.
 
What happens if you boot without any animations installed? Will it boot normally?
I think yes...

Just go to the root of your memory card and look for the "arm9loaderhax.bin" then rename it to "arm9payload.bin" and transfer it to anim folder. Now, the "arm9loaderhax.bin" that is with the BootAnim9 folder rename it to "arm9loaderhax_si.bin" and put it in the root of your memory card. you will have now this directory structure:

SD Card/arm9loaderhax_si.bin

SD Card/anim/arm9payload.bin

for the boot screen

SD Card/anim/0/(your boot screen files)
This work on my 3ds en 11.2, thanks a lot :)
 
Just go to the root of your memory card and look for the "arm9loaderhax.bin" then rename it to "arm9payload.bin" and transfer it to anim folder. Now, the "arm9loaderhax.bin" that is with the BootAnim9 folder rename it to "arm9loaderhax_si.bin" and put it in the root of your memory card. you will have now this directory structure:

SD Card/arm9loaderhax_si.bin

SD Card/anim/arm9payload.bin

for the boot screen

SD Card/anim/0/(your boot screen files)
And where do I put my other payloads in? Like Decrypt9 and so on. (Sorry if I made any mistakes, I'm not English.)
 
After updating to Luma 7.0.1, my boot animations stopped loading. Can anyone tell me what I need to do to get them functioning again properly?
 
After updating to Luma 7.0.1, my boot animations stopped loading. Can anyone tell me what I need to do to get them functioning again properly?
You accidentally overwrote BA9's executable. Move Luma's arm9loaderhax.bin to /anim/arm9payload.bin and put BA9's executable instead (can be found in the download zip).
 
  • Like
Reactions: lonewolf08
Tried everything but I couldn't get it to work. I put in BA9's a9lh.bin, moved my luma a9lh.bin to /anim and renamed it to arm9payload, and put animations in their directories and it booted with a black screen. Can someone please tell me what I'm doing wrong?
 
Tried everything but I couldn't get it to work. I put in BA9's a9lh.bin, moved my luma a9lh.bin to /anim and renamed it to arm9payload, and put animations in their directories and it booted with a black screen. Can someone please tell me what I'm doing wrong?
Yes, bootanim9 payload should be renamed to arm9loaderhax_si.bin on the root and luma payload should be renamed arm9payload.bin in anim folder.
Root:
arm9loaderhax_si.bin----------bootanim9 payload
- anim/---------folder
- 0/----------folder inside anim
- anim
- bottom_anim
- config​

- 1/-------another folder if you have more
- anim
- config​
Arm9payload.bin----------lumas payload inside anim folder​

And no you don't need to update luma if you don't want a9lh not the same as luma, luma is just the cfw

Is your file structure the same as above? If it is try redownloading the animations to make sure it isn't corrupt.
Edit: each animations will have its own folder my example stops at two but if you have say 4 then you need 4 folders inside anim named 0,1,2,3,4 you can't leave one folder empty meaning you can't jump numbers. Try without the config file. That's all I can think off at the moment.

I don't think that's necessary but the steps for troubleshooting should be:
  1. Make sure folders and files are in right place and named correctly meaning no .bin.bin etc
  2. See if naming bootanim9 to arm9loaderhax works.
  3. If above don't work try arm9loaderhax_si
  4. Download the animations again maybe they got corrupt.
  5. Download payloads again maybe they got corrupt
  6. If none of the things work than you have super old a9lh that doesn't have screen init and need to update a9lh
I don't think you need to do the last one since your screen flashed and most likely has to do with your animation files/structure.

Edit: the config file usually comes with the animations some won't have it though.
 
  • Like
Reactions: Wolfvak
I assume by using this you can no longer use Luma Updater since it will update the arm9loaderhax.bin instead you would manually update Luma by getting its latest arm9loaderhax.bin from github each time theres an update and changing it to arm9payload.bin right?
 
I assume by using this you can no longer use Luma Updater since it will update the arm9loaderhax.bin instead you would manually update Luma by getting its latest arm9loaderhax.bin from github each time theres an update and changing it to arm9payload.bin right?
You'd be correct. You have to manually update Luma each time and rename it.
 
I assume by using this you can no longer use Luma Updater since it will update the arm9loaderhax.bin instead you would manually update Luma by getting its latest arm9loaderhax.bin from github each time theres an update and changing it to arm9payload.bin right?
Read this, especially part 3. Your path would be /anim/arm9payload.bin, but I suppose you already knew that. Just putting it out there for posteriority.

You'd be correct. You have to manually update Luma each time and rename it.
I find it pretty amusing how nowadays, where we have multi-core CPUs and gigabit internet connections people don't bother doing a quick google search.
 
Last edited by Wolfvak,
this thread still alive, whenever i put my animation into folder called "0" my 3ds can't even boot in but when i delete it boots normally i got 03ds

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

this thread still alive, whenever i put my animation into folder called "0" my 3ds can't even boot in but when i delete it boots normally i got 03ds


o3ds*
 
@Wolfvak So with Sighax, I can covert the arm.bin files to .firms but what should I do with them? Or will this require an update itself?
In theory, I just want to convert both the "bin" files, but I'm sure the Bootanim9 payload only searches for the arm9payload.bin to load properly? I'm guessing it would need to be changed to look for .firm instead?
 
So, with this, can I replace the animated Nintendo 3DS logo that pops up as I boot up a game or app?

Sent from my SM-T280 using Tapatalk
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum