I'm running roooted and on cm 11 nightly on my tmobile s 5
I am trying to load a custom boot animation, my issue is there is no folder for data/local like everyone says. What should I do and where can I locate my stock cyanogenmod boot animation?. I want to modify it, and play around with it. Thanks in advance.
webdork said:
I'm running roooted and on cm 11 nightly on my tmobile s 5
I am trying to load a custom boot animation, my issue is there is no folder for data/local like everyone says. What should I do and where can I locate my stock cyanogenmod boot animation?. I want to modify it, and play around with it. Thanks in advance.
Click to expand...
Click to collapse
I don't know for CM11, but on stock Touchwiz it's in /system/media. I'd look there.
Try this app:
https://play.google.com/store/apps/details?id=com.jrummy.apps.boot.animations&hl=en
Related
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.
I was trying to install cm6 on my phone so i could install cm7. I installed cm6 and now my phone only goes to the splash screen and just sits there.. i booted in to clockwork recovery and non of my back up will work just sits at the splash screen...
xXy3kXx said:
I was trying to install cm6 on my phone so i could install cm7. I installed cm6 and now my phone only goes to the splash screen and just sits there.. i booted in to clockwork recovery and non of my back up will work just sits at the splash screen...
Click to expand...
Click to collapse
What color is the text in your recovery screen?
oRANGE i flashed it to 3.00005 or what ever
Stock, CM6 and all Froyo (Android 2.2) based ROMs are incompatibile with CWM 3.x. That can only be used with Gingerbread (Android 2.3) ROMS like CM7. Install CM7, and you'll be good to go.
Take a look at http://forum.xda-developers.com/showthread.php?t=944681 from TrueBlue_Drew. It's a way of switching between the various versions of CWM. But it won't be useful until you have a working phone.
xXy3kXx said:
oRANGE i flashed it to 3.00005 or what ever
Click to expand...
Click to collapse
If you installed CM 3.x then you need to flash Cyanogen CM7. You'll get a working phone. Don't forget the g/apps either.
i downloaded cm_glacier_full-32.zip and the gapps the phone boots past the splach screen than keeps going through the boot animation
xXy3kXx said:
i downloaded cm_glacier_full-32.zip and the gapps the phone boots past the splach screen than keeps going through the boot animation
Click to expand...
Click to collapse
Try downloading 31, wiping the had set clean, and try a fresh start.
i can get the 32 build to boot with no gaps installed but when i install the gapps thats when i get the boot loop i downloaded gapps-gb-20110120
xXy3kXx said:
i can get the 32 build to boot with no gaps installed but when i install the gapps thats when i get the boot loop i downloaded gapps-gb-20110120
Click to expand...
Click to collapse
thanks for supplying the exact version of the g/apps. Did you by chance check the md5sum? should match 45e175c25a498c8945c543d92d92e782
and are you installing the G/apps pre or post installing the ROM?
Oops I had the wrong gapps file its all good now bro thank you for your time and help I'm very grateful for people like you!! Thanks braa
Sent from my Bubba kush device! ;/
I've reverted back to stock Kernel for the moment. But the Trinity boot animation still comes up. Trinity is definitely uninstalled, but the boot image is still there.
Thanks.
Logan_M said:
I've reverted back to stock Kernel for the moment. But the Trinity boot animation still comes up. Trinity is definitely uninstalled, but the boot image is still there.
Thanks.
Click to expand...
Click to collapse
its /system/media/bootanimation.zip. delete it or replace it with the bootanimation.zip of choice
Thanks!
I now realize that I was supposed to do a backup. Stupid me. Just having fun trying out different Kernels.
Hello XDA,
First time posting so I have to ask in Q&A rather than the thread for MultiROM itself. I've been to these forums quite a few times for rooting and unlocking other's devices, but now that I have a Nexus 7 myself, it's time to start messing around with it.
So the situation for my problem is that I have successfully installed MultiROM and was able to boot up my stock image fine, but when I installed Cyanogenmod 10.0.0, the screen automatically goes to the boot screen for Cyanogenmod rather than asking which ROM to boot and then just hangs on that boot screen forever.
I have not used the kexec hardboot patches for anything yet so it can be that I should be using those somewhere along in the process.
Also, how do I go about uninstalling MultiROM so that I can start all over again? Do I just go into TWRP and hit "install" and choose the stock image for 4.2.1?
destructo322 said:
Hello XDA,
First time posting so I have to ask in Q&A rather than the thread for MultiROM itself. I've been to these forums quite a few times for rooting and unlocking other's devices, but now that I have a Nexus 7 myself, it's time to start messing around with it.
So the situation for my problem is that I have successfully installed MultiROM and was able to boot up my stock image fine, but when I installed Cyanogenmod 10.0.0, the screen automatically goes to the boot screen for Cyanogenmod rather than asking which ROM to boot and then just hangs on that boot screen forever.
I have not used the kexec hardboot patches for anything yet so it can be that I should be using those somewhere along in the process.
Also, how do I go about uninstalling MultiROM so that I can start all over again? Do I just go into TWRP and hit "install" and choose the stock image for 4.2.1?
Click to expand...
Click to collapse
It's overwriting the kernel with one of its own... that's the only thing I can think of. Flash a kernel that has MultiROM support like m or motley.
Mac of York said:
It's overwriting the kernel with one of its own... that's the only thing I can think of. Flash a kernel that has MultiROM support like m or motley.
Click to expand...
Click to collapse
Does this mean that I should find a version of CM that has one of those kernels? Or do i simply flash the kernel by itself and that would overwrite the CM kernel so that the problem would be resolved?
Also I tried installing Kaos Droid and chose the option to install the M kernel before CM actually and I remember that it also would just boot to a completely black screen and nothing past that. So i'm not sure if it's the kernel. But i did just successfully go back to stock and rooted again so that I will try out your suggestions tomorrow. Thanks.
destructo322 said:
Does this mean that I should find a version of CM that has one of those kernels? Or do i simply flash the kernel by itself and that would overwrite the CM kernel so that the problem would be resolved?
Also I tried installing Kaos Droid and chose the option to install the M kernel before CM actually and I remember that it also would just boot to a completely black screen and nothing past that. So i'm not sure if it's the kernel. But i did just successfully go back to stock and rooted again so that I will try out your suggestions tomorrow. Thanks.
Click to expand...
Click to collapse
You can flash the kernel separately and it'll be fine.
Sent from my Nexus 7 using Tapatalk HD
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 ?