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
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?
..................
Okay so basically my Theme Engine doesn't work. I tried setting a Live Wallpaper and now my phone is stuck on boot looping. It'll suddenly pop up the lock screen then go back onto the cyanogenmod boot screen. Any solutions?
How to fix CyannogenMod M7 bootloop
[/B]Please note ! ,this step will earse your system /data files !
1.Hold down power and volume down.
2.Get into Recorvery Mode , CWM or TWRP.
3.Wipe Data / cache
4.(Wipe Cache try if it works)
5.Reboot system.
6.Resetup system ,
--------------------------------------------------------------------------------------------
WHY LIVEWALLPAPER,THEME CHOOSER DON'T WORK AT Nexus 4 ?
answer: M7 bulid is not offically for Nexus 4
Unless you flash their newly updated CyanogenMod OS that for Nexus 4.
Hope this may help you !
No thanks is needed ! it great to help people ! please spread to others if works , !]
Thank you and have a nice day !
Thanks for the help NexusCyanDEV, I already did those steps myself before you sent the post and my phone's working again. Theme Chooser as also working after doing factory reset from within my custom recovery menu.
ihsaan96 said:
Thanks for the help NexusCyanDEV, I already did those steps myself before you sent the post and my phone's working again. Theme Chooser as also working after doing factory reset from within my custom recovery menu.
Click to expand...
Click to collapse
Ur welcomed!
hi everyone I am new here so I do something wrong please tell me ....so I want to change my stock boot animation and put watch dogs instead ...(I can't place the link so I m gonna post the title of the website " how-to-install-a-custom-android-boot-animation" )is it gonna work on my lg g2 d802 running cloudyg2 ?? thank you all in advance....of I post it on the wrong place plz move it on the right section ....
You should probably move this to the 'help and troubleshoot' section
Sent from my LG-D802 using XDA Free mobile app
If you use this it must work. Just copy your stock boot animation to pc take backup and back up everything in your recovery. Here is the fixed stuff for that animation
http://forum.xda-developers.com/showpost.php?p=53446077&postcount=23
ceza1380 said:
If you use this it must work. Just copy your stock boot animation to pc take backup and back up everything in your recovery. Here is the fixed stuff for that animation
http://forum.xda-developers.com/showpost.php?p=53446077&postcount=23
Click to expand...
Click to collapse
thank you very much I appreciated I will post here the result if anyone else want to know .....
so I just flash the sounds via twrp and it worked now when I boot my phone I have watchdogs sounds and not lg s stocks....now for the animation it worked but first I recommend back up your stock animation ... you can find it by using es explorer and then you can paste the zip that you can find on the thread that ceza1380 post here then don't reboot you must change the permitions of your new boot animation you can do that by using again es explorer just long press on the new boot animation (it must have that name bootanimation.zip) and go to permitions and make them (rw r r ) you can be sure by taking a look to the stock boot animation s permitions ....so in conclusion you can install boot animations sounds and boot animation on cloudyg2 but first you must do all the steps from above ....another big thanks to @ceza1380 for posting the the thread !!! ???
panostheodorakis7 said:
so I just flash the sounds via twrp and it worked now when I boot my phone I have watchdogs sounds and not lg s stocks....now for the animation it worked but first I recommend back up your stock animation ... you can find it by using es explorer and then you can paste the zip that you can find on the thread that ceza1380 post here then don't reboot you must change the permitions of your new boot animation you can do that by using again es explorer just long press on the new boot animation (it must have that name bootanimation.zip) and go to permitions and make them (rw r r ) you can be sure by taking a look to the stock boot animation s permitions ....so I'm conclusion you can install boot animation s sounds and boot animation on cloudyg2 but you must do all the steps from above ....another big thanks to @ceza1380 for posting the the thread !!!
Click to expand...
Click to collapse
Lol thanks for your kind words. I'm glad that I help you. Have a good day my friend :highfive:
EDIT: Flashable zips from AndroidPolice (just flash from recovery) ----> http://www.androidpolice.com/2015/1...gs-android-6-0-marshmallow-nexus-ota-roundup/
Steps:
1) Backup apps and data
2) Make an Nandroid backup
3) Factory Reset (optional but recommended)
4) Download and install Android 6.0 factory image through adb https://developers.google.com/android/nexus/images?hl=en
5) Flash latest TWRP 2.8.7.0 recovery
6) Flash ElementalX kernel 5.0 for Marshmallow or stock rootable kernel from @zaclimon through TWRP http://elementalx.org/devices/nexus-7-2013/ or http://forum.xda-developers.com/showpost.php?p=63158038&postcount=210
7) Flash latest supersu 2.46 zip https://download.chainfire.eu/696/SuperSU
8) Reboot
Hope that someone creates a zip to flash...
My USB port is not reliable, and i'm kind of lazy.
Booting now... I'll report when it boots
Edit: First boot takes even longer than lollipop :/ (~10 minutes)
Just finished flashing the factory image. Waiting for it to boot also.
noahvt said:
Booting now... I'll report when it boots
Edit: First boot takes even longer than lollipop :/ (~10 minutes)
Click to expand...
Click to collapse
I waited about 8 mins. but nothing happend! No "optimising apps/system" message, so I wiped again....
Is that normal?
It booted !!! took what it felt like about 10-15 minutes (wasn't watching the clock, only my Flo's screen). Runing the Setup Wizzard now.
Feels snappy. I will be entertained for the next couple of hours
idCyber said:
It booted !!! took what it felt like about 10-15 minutes (wasn't watching the clock, only my Flo's screen). Runing the Setup Wizzard now.
Feels snappy. I will be entertained for the next couple of hours
Click to expand...
Click to collapse
I hope someone is already working on a custom kernel to support root lol
takes a long time to bootup first then its ok...all animationa re optimised and more of material animations are visible.. just enables system tuner (by pressing and holding settings icon until it spins on the notification tray and removed the aeroplane ,mobile data and torch mode).. i didnt find the restore from old nexus option.. but i did get sync data via bluetooth from existing android device...nice
Can someone test if there is kind of the multiwindow feature that we saw in the M Previews?
I have installed it using the app flashfire beta by chainfire. Still booting up but since it shows the android m boot animation, looks like a success
Installed fine for me, booted in what felt like a normal amount of time.
Problems may have begun trying to root though.
Use NRT... first problem: it didn't actually copy the root files over so when it rebooted into TWRP they weren't there. I just rebooted and manually copied them over, then back into TWRP and I was able to install them. But, now I'm sitting here at the startup animation for about 10 minutes now, far longer than after initial install, so I'm starting to think boot loop.
I'll give it a few more minutes and then re-flash the system partition, should get it working again. NRT naturally doesn't know about this version yet, using the *.*.* option, but I'm starting to get the feeling root isn't straight-up on M. I'll repost if it happens to start up, but anyone else try rooting yet? If so, how'd it go for you?
EDIT: Another thread seems to support the conclusion that root isn't working yet, someone else had a boot loop too (something to do with stock recovery replacing TWRP and TWRP trying to save itself, or some such).
moliverac8 said:
Can someone test if there is kind of the multiwindow feature that we saw in the M Previews?
Click to expand...
Click to collapse
Yes, not enabled by default:
pull build.prop from recovery and change release from user to userdebug
push build.prop
chmod 644 build.prop
reboot device and find it in dev options under drawing
my 32gb nexus7 is showing only 16gb of space...
i see this in other users when lollipop is out...
Flashed insecure boot.img, flashed root = bootloop So I REPEAT ROOT DOES NOT WORK
http://www.androidpolice.com/2015/1...es-are-live-for-the-nexus-5-6-7-9-and-player/
In the comments there are people saying that they're doing this:
"Unlocked bootloader + Change flash script to remove -w = Never wait for OTA again"
What is the remove -w? Apparently it makes it so it doesn't wipe userdata. that would be helpful but how would one accomplish that?
skyrocketeer said:
What is the remove -w? Apparently it makes it so it doesn't wipe userdata. that would be helpful but how would one accomplish that?
Click to expand...
Click to collapse
You just edit the batch file (.bat) or shell script (.sh) that comes with the factory image download with a text editor and remove the '-w' part from the fastboot line.
Waiting to try it using Multiboot (zip image and root)
Looks like we are not getting root until google decides to release the source code, what a bummer...
NO Gallery app as it was in Lollipop, now we need to use Photos ad main app for photos... :/, got old app drawer with black background scrolling is left-right not up-down. Shame they didn't add percentage battery too
Luk45z said:
NO Gallery app as it was in Lollipop, now we need to use Photos ad main app for photos... :/, got old app drawer with black background scrolling is left-right not up-down. Shame they didn't add percentage battery too
Click to expand...
Click to collapse
Hold settings icon in quick settings until it starts spinning and then release, system ui tuner will open, then enable show embedded battery percentage