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
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 have just put Leedroid 2.0 on my DHD and everything was fine but after looking round I decide last night that I would go to 2.3, so I dwnlded it and put it onto my SD card with the md5 file no problems. I then used clockwork mod to wipe my old Rom for a fresh start still no problem. When I went to install the new Rom it kept saying error which had alarm bells ringing in my ear I powered odd and removed the SD card and put the old 2.0 zip file on there and removed the error file and inserted it into the phone. This gave me a flashing Orange light and not able to power on so I removed the battery and waited for ten seconds and put it in and powered up the phone. Now I thought could just install the zip from there but the phone booted up (took ages for first boot but I waited) and followed the on-screen instructions for setting up the phone and then I used titanium backup to reinstall my apps.
The version of leedroid is the same but it boots up differently without the r2d2 sounds and different boot up screens
Not sure what I did seeing as I never installed from the zip file it has installed from somewhere.
I think I will do it again but just wanted any thoughts as to what actually happened with the install and what is the latest leedroid Rom because I can't seem to find it anywhere I look I keep getting different numbered versions.
Thanks
Sent from my Desire HD using XDA App
TheKaptone said:
I have just put Leedroid 2.0 on my DHD and everything was fine but after looking round I decide last night that I would go to 2.3, so I dwnlded it and put it onto my SD card with the md5 file no problems. I then used clockwork mod to wipe my old Rom for a fresh start still no problem. When I went to install the new Rom it kept saying error which had alarm bells ringing in my ear I powered odd and removed the SD card and put the old 2.0 zip file on there and removed the error file and inserted it into the phone. This gave me a flashing Orange light and not able to power on so I removed the battery and waited for ten seconds and put it in and powered up the phone. Now I thought could just install the zip from there but the phone booted up (took ages for first boot but I waited) and followed the on-screen instructions for setting up the phone and then I used titanium backup to reinstall my apps.
The version of leedroid is the same but it boots up differently without the r2d2 sounds and different boot up screens
Not sure what I did seeing as I never installed from the zip file it has installed from somewhere.
I think I will do it again but just wanted any thoughts as to what actually happened with the install and what is the latest leedroid Rom because I can't seem to find it anywhere I look I keep getting different numbered versions.
Thanks
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
If you wiped, and can now boot, you MUST have flashed the zip otherwise you would have nothing to boot into, does phone info not tell you what version of leedroid your running?
Yeah it days Android 2.2.1 and leedroid 2.0.0 which is what I thought I had but it seems a little different
Sent from my Desire HD using XDA App
so what is the latest version of Leedroid and is there a link direct to it
Thanks Again
TheKaptone
TheKaptone said:
so what is the latest version of Leedroid and is there a link direct to it
Thanks Again
TheKaptone
Click to expand...
Click to collapse
Go to the Development thread, it's one of the top ones there called LeeDroid.
First post in that thread has download links.
latest version 2.3 is a beta. yuu should back to 2.2.2 again if there is so much problem!
dont forget,
2.2.2 is based on the current 2.2 version.
2.3.x is based on the leaked 2.3 version.
2.2.2 is great.. use it myself and love it.
havent tried 2.3.x but i would sugest reading the posts to see if there are any bugs ect.
i also had the issue that my boot screen looked stock again.
this happened after messing around with flashing the roms..
after i flashed it again the normal way.. it got back to the fancy boot screen.
dont forget to use clockwork 2.x.x.x not the clockwork 3.x.x.x
thanks for that I have done it again and it is now 2.2.2 and is grrrreat , watching closely the 2.3 thread and nearly ready to make the jump
everytime i flash a rom, it gets stuck at the bootanimation or the setup wizard any suggestions? i used to flash roms before but it started happening recently and i cant pinpoint why it freezes
My friend had that issue too. It turned out he wasn't wiping /system before he flashed. Too much crap built up in there from too many ROMs.
estallings15 said:
My friend had that issue too. It turned out he wasn't wiping /system before he flashed. Too much crap built up in there from too many ROMs.
Click to expand...
Click to collapse
I use 4ext app and do a ext 4 wipe and it seems to work okay for me. sometimes ill manually wipe all partitions but usually dont need to.
Yeah I tried wiping everything
I did factory and cache
Then dalvik
Then under mounts and storage I format system,data,and cache
Maybe I'll try 4 ext
Look at the logcat.
If you have clockworkmod lower than v3, and you flash a gingerbread rom, it naturally get s stucked by bootanimation. But if you have the latest one of the recovery, which supports ext4, and it stuck at the bootanimation (not the white splash screen), then you must wait until the drivers are initialized.
Sent from my Black Ice'd Glacier using XDA App
My cwm is the latest one I believe (5.0.2.0 or something like that)
I tried loading zipnets ice rom and it hangs at the clock animation
I tried the new sense 3.6 rom. (Forgot name) and sometimes it freezes at the bootamimation,setup, or at the home screen
What do you mean wait for drivers to install?
Sent from my Transformer TF101 using XDA
The first start after a rom install is always the longest one. That is usual. Try to wait about three - five mins and then it is done. After that you can use it.
Sent from my Black Ice'd Glacier using XDA App
Also after it boots, give it a few minutes to settle in and turn on mobile netowork ect.
Sent from my Sense 3.6 Glacier using XDA Premium.
How long should I wait? Last time I waited 20 mins and it was still frozen
edit: ok i tried 4ext and used the format everything except sd card and still get a frozen boot animation any other suggestions?
Did you follow Jack_R1's suggestion and run logcat?
so after hours of tinkering around these boards and through everyone's help, i found out i have the bad emmc which is what im assuming the problem is but why was i able to flash roms before? or was it just luck?
Hey all.
So, I'm running Audacity B2 on my G2, and I've attempted to load up this modified services.jar file here, using both methods. I'm technical myself, so I tried the manual way first. Followed the steps exactly, and when I rebooted, I never (well, at least not for about 10 minutes that I waited!) got past the flying blocks of color boot screen for Audacity. Seemed to be stuck.
So I tried the CWM zip install method as well, same result. /Sigh. I really didn't expect this to be where I got stuck! Anybody have any thoughts as to what possibly is going on?
The only way I can get back to a working phone is to re-flash Audacity B2, then it will boot. Really wanting to try out V6 Supercharger, but can't get past this first step, which should be the easy one.
Thanks for any insight.
I had this issue today too. I reflashed B2 and gapps, booted, set up google account and apps, flashed new services.jar and after that everything works.
Interesting! So by "flashed new services.jar", I take that to mean you used the zip install via recovery, not manually moving the file?
I'll give that a shot and see what happens....
Thanks!
If you manually move the file make sure you set the proper permissions and ownerships. Also make sure you check the MD5sum of each download with what the site reports.
Either of those may cause issues that will likely boot loop you.
Sent from my HTC Vision using xda premium
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?
..................