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

  • Thread starter Thread starter Wolfvak
  • Start date Start date
  • Views Views 332,326
  • Replies Replies 1,434
  • Likes Likes 75
Status
Not open for further replies.
This may sounds dumb, but you've said that you copied my files with the files you already had. Can you post a picture of the directories, including anim?
I can't screenshot them right now (installing something on the 3DS) but first I tried to do it myself, then I saw your files and tried it, then I tried mine again after updating A9LH.
 
I can't screenshot them right now (installing something on the 3DS) but first I tried to do it myself, then I saw your files and tried it, then I tried mine again after updating A9LH.

And now the issue is done for?
 
Cobj2DY.png

bcS6CDe.png

I know my SD is a mess, but I don't know what I need :P
 
Last edited by sniper_x002,
Hmmm. Why your arm9loaderhax.bin has 66kb of size? If using the recent BootAnim9, it should be less, like 20kb. And also, try to remove the .bak file.
Oh, I reverted to what worked so I could boot my 3DS. Yeah the one for this program had the small thing bin.
 
Oh, I reverted to what worked so I could boot my 3DS. Yeah the one for this program had the small thing bin.

Other things: Try to erase the 1,2 and 3 folders inside anim folder (backup them before erasing) so you keep only the 0 folder.
 
Other things: Try to erase the 1,2 and 3 folders inside anim folder (backup them before erasing) so you keep only the 0 folder.
Already did that, when I did I just used your 0 folder and left all of mine out.
 
Already did that, when I did I just used your 0 folder and left all of mine out.

Well, for the sake of proper testing do this:

1.- Backup ALL your files.
2.- Erase All the content of the SD.
3.- Copy the content of this .rar file so is the only content you have on the SD.
 

Attachments

Well, for the sake of proper testing do this:

1.- Backup ALL your files.
2.- Erase All the content of the SD.
3.- Copy the content of this .rar file so is the only content you have on the SD.
I'd rather not. I have around 80GB~ of files so that would take a long time.
 
I'd rather not. I have around 80GB~ of files so that would take a long time.

I'm thinking that some file(s) are interrupting the proccess somehow. But since you stated that the systems boots normally with the payloads you have, then technically shouldn't be a problem using BootAnim9.

Is kinda interesting, but i'm trying to figure out what other thing could trigger such behavior.
 
I'm thinking that some file(s) are interrupting the proccess somehow. But since you stated that the systems boots normally with the payloads you have, then technically shouldn't be a problem using BootAnim9.

Is kinda interesting, but i'm trying to figure out what other thing could trigger such behavior.
I used the new OTP-less method to install A9LH the other week if that means anything.
 
I used the new OTP-less method to install A9LH the other week if that means anything.

That shouldn't be an issue since you can already run Luma CFW. But for being curious, can you run payloads as Hourglass9 (by holding START before turning on the console)?
 
That shouldn't be an issue since you can already run Luma CFW. But for being curious, can you run payloads as Hourglass9 (by holding START before turning on the console)?
Yeah I have Hourglass9, Decrypt9, and Godmode9 I can all run from start. (sd\luma\payloads\)

Edit: Well thanks for trying anyway. I probably won't respond for a bit (Running Moflex multicore encoder usually locks up my computer while it's doing it's thing)
 
Last edited by sniper_x002,
  • Like
Reactions: Autz
Yeah I have Hourglass9, Decrypt9, and Godmode9 I can all run from start. (sd\luma\payloads\)

This issue is interesting, but at first glance can be anything. Let's not forget that you stated:

Edit 2: Okay it only shuts down immediately if I'm using arm9loaderhax_si.bin instead of just arm9loaderhax.bin

Another small test: Change the name of your Luma payload (the one on the root you normally use to run CFW) to arm9loaderhax_si.bin and say what happend.
 
  • Like
Reactions: sniper_x002
This issue is interesting, but at first glance can be anything. Let's not forget that you stated:



Another small test: Change the name of your Luma payload (the one on the root you normally use to run CFW) to arm9loaderhax_si.bin and say what happend.
I'll try it after I'm done installing something (Just finished injecting my first movie! hopefully more to come)

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

Works the same when I add _si
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum