This has been bugging me forever. I love the Ion ROM for its speed but I hate not changing the boot logo (not splash1, the boot animation). I've discovered why/how the Ion ROM is different and how to fix it (partway).
First off, Ion doesn't use the standard boot.gif & boot.mp3 files in /system/media. If you try to place the files there you will get no response. Instead Google, for whatever the reason, has changed it into framework-res.apk.
If you unzip framework-res.apk the files are inside (unzipped dir)/assets/images/. They are named android-logo-mask.png, which is the text that says Android on boot, and android-logo-shine.png, which is the white & blue shine that slides across the text as it boots. You can simply change these out and resign the apk with your method of choice to change the icon.
Now on to the sound, the ROM ships with 2 boot sounds that I can't seem to distinguish other than the names. They are located in framework-res as well, in (unzipped dir)/assets/sounds. They are named bootanim0.raw & bootanim1.raw. A good audio editor for opening .raw files is Wavepad Sound Editor by NCH Swift Sound. It works well and handles the files with ease and has a free version or a 30 day trial available.
For whatever the reason, the sound doesn't play on boot by default. I haven't had a lot of time to mess with it but I believe the problem lies in init.rc when it calls the boot image, I know thats how it works on other ROMs but I haven't looked into Ion init.rc yet. You can probably tweak the init.rc to call the bootanim0.raw file to play when the logo shows. I will play around with it.
Hope this helps anyone else with this problem and PM me or post in this thread and I will try to help with any problems you have
Geniusdog out.
This was already covered awhile ago in the Dream Themes and Wallpapers section.
Ok so after some brainstorming and a LOT rebooting, I finally figured out how the boot animation works on stock G3 ROMs.
I took the animation from the Nexus 9 factory image (which is the same exact one on the Nexus 6) and made some modifications so it runs like its supposed to. It would not finish before the boot has ended, neither will it be incomplete. No matter what you boot time is
(I tried it on d851 but should work on any variant with LG based ROM. Also should work on the LG based Lollipop ROM, but you tell me...)
Instructions: (you must be rooted)
-Download
-go to /system/media folder and rename bootanimation.zip to bootanimation.zip.bak
-move downloaded zip to /system/media folder and set 644 (rw-r--r--) permisions (no sticky permission needed)
-reboot and enjoy!
Let me know if there's anything going wrong or right...
So now for some technical explanation
It turns out that the ROM uses the first half of the folders in the bootanimation.zip for a different animation when booting with the Quickcircle case. No matter what they are named or the files, or what is in them; it will always do this. So I went ahead and created 6 more folders to the start of the list (part0_0 to part0_5) and just added an only image from the stock LG Quickcircle animation (if you use quickcircle case you would notice when booting up with the case).
After that I noticed that on the description file (desc.txt) you have to leave the way it is on the nexus devices: (c 1 0 part1_2) instead of (p 1 0 part1_2); because the way the Lollipop notification works is that it loops the folder "part1_3" in this case, so you see the particles until boot is complete and then it shows the "android" word and fade away before getting to the lockscreen. If I change it to (p 1 0 part1_2) it would never show the android word and would get to the lockscreen as soon as it finishes boot. If I use the "c" it tells it to complete the animation before getting to lockscreen. This is why the animation is not humongus in size, compared to other Lollipop animations for the G3 (no offense)
Next thing I did was to up the resolution, but I don't have to do it to every single image, I just set the resolution that I want in the description file, and that's it. I didn't set it to take the whole screen (side to side) because for me it didn't look that good, but if you want I can make it for you, and even set it to the stock Nexus resolution.
Also, if you want a different quickcircle animation, just send me the file and I'll see what I can do
Thanks for the great looking Lollipop Boot Animation! I tried it on the LG G3 vs985 Stock KitKat Rom and it works 100%.
Working great on D855 thanks.
My boot takes EXACTLY 1min and 20 sec every time why?
Hi,
I'm trying to change my Oppo Find 7's bootanimation but I haven't never succeed, I have the root and I've verificated it, and I tried this ways:
- I put the bootanimation.zip in the folder system/media but it didn't work.
- I put the bootanimation.zip in the folder data/local but it didn't work.
- I tried to flash the bootanimation by the gummy twrp but it didn't work.
- I tried some (like 5 apps) apps from the playstore but all of them says '' Installing done'' but I rebooted the oppo and I always viewed the Oppo's bootanimation.
Who can help me?
ps.: I'm italian so correct me if I did some mistakes, and I tried all this ways also with other downloaded bootanimation but it always didn't work.
Thank you so much
I had some good ideas of creating boot animations and so I looked up how to create one which led me to this guide. Before creating of my own, I had installed Android Wear boot animation from Boot animations app (Playstore) and I wanted to add some more frames after the boot-up completes. I copied and extracted it, added few frames to it, zipped it and replaced the one I had in system/media. The animation did not work. I had the warning sign till my phone booted. Help.
111MIndfreak said:
I had some good ideas of creating boot animations and so I looked up how to create one which led me to this guide. Before creating of my own, I had installed Android Wear boot animation from Boot animations app (Playstore) and I wanted to add some more frames after the boot-up completes. I copied and extracted it, added few frames to it, zipped it and replaced the one I had in system/media. The animation did not work. I had the warning sign till my phone booted. Help.
Click to expand...
Click to collapse
looks like you made 2 mistakes, 1st it's bootanimation, not bootlogo, those 2 are different. 2nd, the tutorial you use is for older version of Android. Started from lollipop, the loop parts was changed.
Hey, guys! I haven't really posted on here yet. Though once I got my Pixel 2 XL and root was achieved I immediately got to work on modding. I hadn't ever rooted a device before and it took so much trial and error. But I've gotten to a point where I'm relatively comfortable with my device except for one issue: restarting my phone causes that AWFUL bright, max brightness screen to be displayed. Most of my apps and such are dark if I can help it.
I've been trying to flash/move the file/alter my boot animation using substratum, system/media/ in solid explorer, etc. No dice thus far! Substratum just gives me an error.
I'm not able to modify/rename things in system/media/ and have only managed thus far to copy/paste a .zip renamed to "bootanimation.zip" into the folder and overwrite the original. It definitely overwrote it. But now I just get a black screen with Android across it for an animation. I assume that's the OS fallback.
Is it just not possible yet in Oreo? I can deal with it. But it's bugging me and I don't know if I'm just missing something.
No need to flash a new boot animation, just take whatever boot animation zip file you want to change it to and replace the original one. The location is in system/media, the name you need to use for the zip is bootanimation, and once your new boot animation is in the system/media folder, change the permissions of the file so that it reads rw-r-r-
The boot animations in substratum themes often do not work, but any properly assembled bootanimation of the appropriate size will work when replaced in the above described method.
Definitely sounds like a permissions issue. Make sure you change the permissions for the zip file when it is in the system/media folder other wise any file you paste into that folder will just revert back to -rw-rw---- which of course will not play during the boot and you will experience the black screen.
https://forum.xda-developers.com/showthread.php?t=1852621
This might help also. But what he said too.
jasonstackhouse said:
No need to flash a new boot animation, just take whatever boot animation zip file you want to change it to and replace the original one. The location is in system/media, the name you need to use for the zip is bootanimation, and once your new boot animation is in the system/media folder, change the permissions of the file so that it reads rw-r-r-
The boot animations in substratum themes often do not work, but any properly assembled bootanimation of the appropriate size will work when replaced in the above described method.
Click to expand...
Click to collapse
I just checked and it appears I do have the right permissions. Could it be the permissive thing, as mentioned below?
jasonstackhouse said:
Definitely sounds like a permissions issue. Make sure you change the permissions for the zip file when it is in the system/media folder other wise any file you paste into that folder will just revert back to -rw-rw---- which of course will not play during the boot and you will experience the black screen.
Click to expand...
Click to collapse
I have it set for rw-r-r- and it is still just the black "Android" animation.
Finally got it fixed! Ultimately I found that setting permissions in solid explorer wasn't enough. I downloaded Root toolkit by cpu82 on here, mounted system r/w, then I moved things around.
Renamed original bootanimation.zip to bootanimation.zip.bak, moved the new "bootanimation.zip" to the /system/media folder, set the permissions (as suggested on this post), then rebooted to test.
Other than the REALLY white Google splash screen with the unlocked lock icon, the boot animation is dark! I'm very pleased with it, as it now matches my system. Thanks for the help, guys! I just needed another way to make the system folder writable.
jgreen077 said:
Finally got it fixed! Ultimately I found that setting permissions in solid explorer wasn't enough. I downloaded Root toolkit by cpu82 on here, mounted system r/w, then I moved things around.
Renamed original bootanimation.zip to bootanimation.zip.bak, moved the new "bootanimation.zip" to the /system/media folder, set the permissions (as suggested on this post), then rebooted to test.
Other than the REALLY white Google splash screen with the unlocked lock icon, the boot animation is dark! I'm very pleased with it, as it now matches my system. Thanks for the help, guys! I just needed another way to make the system folder writable.
Click to expand...
Click to collapse
Does SafetyNet still pass when altering the boot animation in system?
ilal2ielli said:
Does SafetyNet still pass when altering the boot animation in system?
Click to expand...
Click to collapse
Yes mine does
ilal2ielli said:
Does SafetyNet still pass when altering the boot animation in system?
Click to expand...
Click to collapse
Mine does as well! It still has the white screen that shows the unlocked icon, but after that the boot animation kicks in.
jrbxx7 said:
Yes mine does
Click to expand...
Click to collapse
jgreen077 said:
Mine does as well! It still has the white screen that shows the unlocked icon, but after that the boot animation kicks in.
Click to expand...
Click to collapse
Thank you both for confirming. I had been waiting for someone to confirm, as I hadn't seen any information whether or not it would trip SafetyNet.