Okay, so after unlocking the bootloader & rooting I decided I wanted a custom boot animation and went to hit up the play store for aniboot. I first stumbled across an app under the name boot animation - aurora and decided to give it a go. I hit the first button by accident when the app came up (Change animation), so I decided what the hell, it's on there so lets check it out. I reboot to find that the animation is now set to a stock looking 'android' logo so I decided to continue on with JRummy's Rom Toolbox and aniboot for better luck. I sadly discovered that both tools would not install the animation simply within the app, it was always the same lame stock 'android' animation on the reboot.
I then checked within /system/media/ folder and placed the bootanimation.zip in there, but still no luck on the reboot. It was still the same stock animation.
This is when curiosity got the best of me and I stuck my nose into something I probably shouldn't have.
I went into /system/bin and found a file called bootanimation. My 'brilliant' thinking told me, hey let's copy this file into another folder (just in case) and then remove it from /system/bin/ and replace it with the bootloader zip from aniboot. When I rebooted, I found that now only the Google splashscreen would come up and there was no animation at all. Thankfully it still boots into jelly bean though. Even after trying to place the copy back into /system/bin/ I only get the splash screen now on boot ups.
I've decided this is where I stop trying myself and reach out for help before I end up bricking this thing or having to reflash everything back to stock. Can anyone provide some insight to my blunders?
..................
Related
Just a little curious...
I have a i9000m from Bell, and somewhere between applying some lag fixes, overclocking, a trying to get into recovery via buttons (fail, only adb works), my boot logo now changes from "GT-i9000m" to "GT-i9000" ("m" disappears) during boot. I assume that's from applying things that are made around a i9000? And also I have no more boot/off animation. Guessing both of these things are from doing Mimocan's lag fix? I since then undid his and changed to RyanZA's one click v1 (update.zip version), but it all remains.
Wondering if anybody out there has some wisdom to share
I'm not too too worried about these things, but Its kinda lame with no animation If anything, I would remove the startup sound, but only when I get my animation back.
My boot animation also doesnt show up anymore But you can hear the swoooosh sounds and so on...
not sure if this applies to your problem.
I had a similar issue after lag fix, noticed that playlogos1 and playlogosnow files were exactly the same. I got the original playlogos1 file from another galaxy and renamed to playlogosnow, then replaced the dodgy playlogosnow from my phone.... that fixed it for me. (files are located in \system\bin\)
The way I understand it, the lag fix renames the original startup animation from playlogos1 to playlogosnow, then copies a script called playlogos1 in its place which ensure the fix is applied after reboot, the script also calls the animation "playlogosnow".... in my case I screwed up and ran the lag fix twice, which resulted in both files being exactly the same and the original animation getting wiped.
Hope that makes sense.
The poster above me is spot on. Just flash more roms to fix it i guest
Sent from my GT-I9000 using Tapatalk
playlogos1 is the boot logo, the mount on boot script for lagfix renames the boot logo to playlogosnow.
Somewhere along the line one of the devs may have included a logo that is used instead of your stock one, specially when reverting. ( Prevents problems if you try reverting without actually doing the lag fix. )
Old thread bump
I have similar behavior to OP.
My boot screen shows GT-I9000M for a few seconds, then it turns to GT-I9000 before going to the animation (the M disappears).
I first noticed this about a week ago when i started using Doc's roms, currently I'm running Docs' JPA v7 with no lagfixes.
I'd like to get the correct boot screen back with the "M", is it just a matter of getting an original copy of a bell bootlogos1 file and dropping it into /system/bin (overwriting the current one)?
Doesnt OCLF have the option to restore boot animation\logo??
alferret said:
Doesnt OCLF have the option to restore boot animation\logo??
Click to expand...
Click to collapse
I'm not sure if OCLF had that option, ive only ever played with the lagfix options in Clockwork Manager. I don't see any options to restore boot ani/logos there.
I did a bonehead thing today...
I'm on a rooted 2.2 (OTA)... (not the bonehead part)
Using root explorer I replaced the droidsans and droid sans-bold.ttf files in the /system/fonts folder with a preferred font... All I got was the eternal boot loop.
I then did a factory reset, and could see the font perfectly, but after about 30 seconds it will restart and go back into the boot-loop...
I repeated the process and it baught me enough time to put the fonts back...
but the re-boot/boot-loop still exists.
(one wierd thing I noticed was after I mounted r/w made the edits i clicked r/o and nothing happened... for what its worth)
What are my options?
can I SPF the leaked 2.2 or to another ROM?
I can use the phone for about 30 to 60 seconds.
thanks for your help...
-ryan
First I flashed the new JK6 and then I flashed Eugenes latest kernel over this and it seems to run just fine except for now I have the standard samsung galaxy boot annimation but also flashing android logo on top of it. Anyone know whats going on there and how to get it back to only showing the Samsung animation? Im sure this is an easy fix so hopefully someone knows what is causing it.
I think that most custom roms support boot animation.zip try to put one of those in there if your using one click lag fix try to push the restore boot animation button see if that helps
Still flashing , thanks to odin & tw
the kernel is looking at a bootanimation file (there is no extension) while the other samsung stuff is booting the normal bootanimation files. you'll need to delete the
bootsamsung.qmg
bootsamsungloop.qmg
from your /system/media/ folder to get the dueling boot animations to stop.
geoffcorey said:
the kernel is looking at a bootanimation file (there is no extension) while the other samsung stuff is booting the normal bootanimation files. you'll need to delete the
bootsamsung.qmg
bootsamsungloop.qmg
from your /system/media/ folder to get the dueling boot animations to stop.
Click to expand...
Click to collapse
Ok this worked as far as not having 2 at once but is there a way to get the stock animation from the galaxy s? Right now I have the standard boring android logo. That means I would have to keep the bootsamsung.qmg right? If I could find android boot somewhere in the system maybe i could delete that instead? I thought it would be in system/media somewhere but its not.
Is there a bootanimation.zip of the stock galaxy s bootup? If not there should be.
since you flashed one of eugene's kernels, i think you've flashed the one that dosn't support .qmg booting, but only supports bootanimation.zip. so youre kinda sol.
About 6 months ago I flashed a bootanimation on CM7.1.0, which worked but got stuck on a loop. To fix it I must have restored a backup and everything went back to normal. Until I tried to flash a custom ROM earlier today (Creamed Glacier Beta 6.1). The bootanimation came back after flashing the new ROM! and as expected, it got stuck on a loop.
I deleted the .zip file months ago but the image must've stayed in the system and this newly flashed ROM triggered it, I need some guidance on how to remove it. Would flashing a custom cm7 bootanimation do the trick? Also I put some bootanimations in my phone before but I don't remember flashing them, it's the Nexus Prime animation, came on a .zip, I must've done something wrong since it didn't work, but I just care about being able to flash new ROMs. Thanks in advance guys!
First of all this is the first time I ever heard that collection of *.png caused any device to go in bootloop. Since you are using AOSP structure its located under /system/media/bootanimation.zip
Why don't you just download CWM supported flashable bootanimation.zip or if you have adb setup then just mount the /system and RM the current file and CP the old one.
Sent from my HTC Glacier
There is a superwope script posted in febycv ics forum.try it out.
Or try TDJ Miui or his sense 3.5 as they allow to flag superwipe script.
Or format your sdcard.
Sent from my HTC Glacier using XDA App
Are you rebooting after the device actually loads a ROM? This actually happens when you mount a boot animation file containing PNG above 130kbs. Don't ask me why it happens cause its a mystery to me. I wrote a high resolution boot ani for my touchpad ended up being 150kb per frame and continuously rebooted the moment the device went to sleep. And battery drain was in the insanity level 20% per hour. When I checked battery usage boot animation was actually showing as using battery.
To remedy the issue fixing permission under ROM manager seems to fix the issue. Also loading the boot ani under local/data should bypass the system/media file
Once again don't ask me why this happens or how.. just experienced it recently on a cm7 based from and wanted to chime in
Sent from my ICS Glacier using Tapatalk
I recently tried to change the boot animation but could not find any bootanimation.zip. The only thing close to it was a file called bootanimation in system/bin. When I changed my custom bootanimation.zip to bootanimation and changed bootanimation to bootanimation.bak the new custom boot did not work. When I tried getting back the original boot animation it by changing it from bootanimation.bak to bootanimation it did not work and still was showing a black screen. I've checked permissions and anything I could find online but couldn't find a solution. Any help would be appreciated. Much thanks!
mematuer said:
I recently tried to change the boot animation but could not find any bootanimation.zip. The only thing close to it was a file called bootanimation in system/bin. When I changed my custom bootanimation.zip to bootanimation and changed bootanimation to bootanimation.bak the new custom boot did not work. When I tried getting back the original boot animation it by changing it from bootanimation.bak to bootanimation it did not work and still was showing a black screen. I've checked permissions and anything I could find online but couldn't find a solution. Any help would be appreciated. Much thanks!
Click to expand...
Click to collapse
Stock Samsung don't work with boot animation.zip, but if you are with AOSP/Lineage based ROMs you find it in system/media folder.
Taivotat2 said:
Stock Samsung don't work with boot animation.zip, but if you are with AOSP/Lineage based ROMs you find it in system/media folder.
Click to expand...
Click to collapse
Oh, thank you very much then! Do you happen to have any idea how to retrieve the stock boot animation? It's just a black screen now. Thanks for your response!
did you find solution if yes let me know ?