Related
This tutorial will explain how to make a custom boot animation for your droid eris by replacing the stock verizon wireless animation.
Notes:
- We will be working with .png files so be prepared to convert a video-animation to a series of pngs.
- There are other stock animations such as the HTC one and it may be possible to add another animation onto the end of the verizon wireless one.
1) Create a video animation of 320x480 resolution in Adobe After Effects, another video animating software, or create a series of images for your animation.
2) Convert that video into a series of .png files with the names: 00.png 01.png ... etc ... to 25.png (I have not attempted to use more or less than 25 png files, it may or may not work)
3) Extract the stock bootanimation.zip (provided below) into a working directory, with the following file structure...
- /bootanimation
---- /android -> should contain (00.png -> 03.png) "HTC"
---- /last -> should contain (01.png -> 02.png)
---- /vzw -> should contain (00.png -> 25.png)
---- desc.txt
4) Copy and replace the png files in the vzw folder with the pngs you just created.
5) Choose 2 .png files to be shown after your animation has completed and copy them into your /last directory replacing 01.png and 02.png.
5) Create a new zip file with the folders and desc.txt at root. Make sure to use the Store as the compression method when creating a new zip file. See picture attached to this post.
6) Use adb to send your file to /system/media/bootanimation.zip on your phone.
7) Reboot, and enjoy your fresh boot animation.
I have included my bootanimation.zip as an example. Heres a video of mine:
{Need to be approved by moderator to post youtube link}
youtube -> /watch?v=geghwnIfKS4
This works on the non-rooted eris also
DarthMowzy said:
This works on the non-rooted eris also
Click to expand...
Click to collapse
Really?...
I thought you needed it to mount the system to RW and you can't do this until you have Root?
Also anyone willing to convert this animation from the G1 over to the eris? I really don't know anything about Photoshop or anything like that so I would really appreciate if you would convert these two animations for the eris if its possible.
http://www.4shared.com/file/209835047/9ae956d/bootanimation_boing.html
and this one
http://www.megaupload.com/?d=CY4DK79B
DarthMowzy said:
This works on the non-rooted eris also
Click to expand...
Click to collapse
How? Don't you need ROOT Acess to gain those folders
You need root to copy the zip here: /system/media/bootanimation.zip
but you dont need root to copy it here: /data/local/bootanimation.zip
Do the same steps but change the zip location and it will work.
What if the boot is WAAAAAAAAAAAAAAAAAAAAY longer than 25?? What do I do
Like this one: http://www.mediafire.com/?25notzfztgz
Plus, DarthMowzy in data there is no local folder do I make one
iloveandroid said:
What if the boot is WAAAAAAAAAAAAAAAAAAAAY longer than 25?? What do I do
Like this one: http://www.mediafire.com/?25notzfztgz
Plus, DarthMowzy in data there is no local folder do I make one
Click to expand...
Click to collapse
try it out, i heard a couple of people getting files with over 200 frames working
i3urn said:
try it out, i heard a couple of people getting files with over 200 frames working
Click to expand...
Click to collapse
Yea I can vouch that it works I have one that is 250+ and it works fine.
just a tip to help avoid hours of pulling your hair out..not that i did this or anything
zip up the folders within bootanimation folder, not the bootanimation folder and the folders. If you do, you end up with another directory and it won't load.
Please elp me with desc.txt
t2noob said:
Yea I can vouch that it works I have one that is 250+ and it works fine.
Click to expand...
Click to collapse
I see you guys are having good luck loading boot animations and I imagine your are not running as choppy as mine. all I did was replace the .png files from the example_bootanimation, and mine looks like crap. Can someone tell me what you used in your desc.txt file?
THanks
iloveandroid said:
What if the boot is WAAAAAAAAAAAAAAAAAAAAY longer than 25?? What do I do
Like this one: http://www.mediafire.com/?25notzfztgz
Plus, DarthMowzy in data there is no local folder do I make one
Click to expand...
Click to collapse
When using "adb shell" I can see the local dir. I didnt create it. It was already there.
What cool animations have you guys made
can you guys post some ani,mations you have made that you would not mind sharing. Mine is not that great but I would like to learn. In the mean time I would really like to find something cool to use.
Hi,
Just wondering if anyone has tried and tested the removal of bloatware apps from their Razr I XT890 running 4.12?
I'd be interested in cleaning the phone up a bit just to make it less crowded, I like to use real calc instead of stock calculator, go sms instead of stock messaging, zeam launcher instead of stock launcher etc etc.
I'm quite a novice when it comes to the technical side of things so would be too afraid to start deleting system apps incase they messed something up.
If anyone has seen a list compiled and could share, that would be great. Also, would it be Razr I specific, or would a general 4.12 safe removal list be safe to follow?
Any feedback appreciated
Here you can find answers.: http://forum.xda-developers.com/showthread.php?t=2223482
Read the forum.
Sent from my XT890.
Thanks a lot, have you any idea what to do with them zip files and how can I keep some of the google apps in the list? I'm not sure where to put the #?
cormie said:
Thanks a lot, have you any idea what to do with them zip files and how can I keep some of the google apps in the list? I'm not sure where to put the #?
Click to expand...
Click to collapse
I think that for you would be easier use Titanium Backup or SystemAppRemover (need root acces) to remove apps.
If you want use the zip file you have to unlock bootloader and flash CWM. In CWM you can install zip files. # you must put in front of the line where is written desired app. Updater-script you can fing in the zip file /META-INF/com/google/android/
Thanks again, I actually have my phone rooted and was able to apply the debloater, however I don't want to remove everything so will restore the backup I took before trying it, I tried install the zip file with the edited script (with the # in front of the ones I wanted to keep) but it failed to install via recovery so I must be doing it wrong
I extracted the script file, opened with wordpad, edited, closed and saved, put it uncompressed back into the zip and tried it.
that failed, so I tried open directly from the zip, edit, close and save and flash that too but that failed too the original unedited one doesn't fail.
The error I get is something referring to error in zip file.
cormie said:
I extracted the script file, opened with wordpad, edited
Click to expand...
Click to collapse
Do not use WordPad. Edify scripts require line endings to be linux style (LF only). Wordpad converts them to windows style (CR LF). Use another editor; I recommend notepad2-mod (set syntax highlighting, F12, to shell script)
See I edited and saved in wordpad and wasn't prompted to save in any other format, do you think it still saved in CR LF?
In the same script and another edit, I think I pasted something from somewhere else and went to save, but then it prompted me to save in the wordpad format itself (rtf I think it was) which I didn't, when I simply added a # or two, it just prompted to save without asking for format so it appeared to save as it was and not change anything? So you reckon it still changed it to the non-readable CRLF?
Would basic windows notepad be ok to edit it instead of having to download notepad 2?
Thanks for tyour help so far!
Maybe I'd be better just doing this via root explorer, of which I have some experience of. Is it just a case of locating each of the files listed in the script and deleting them or is there other hidden crap elsewhere that the script gets rid of which a simple root explorer delete won't?
cormie said:
See I edited and saved in wordpad and wasn't prompted to save in any other format, do you think it still saved in CR LF?
In the same script and another edit, I think I pasted something from somewhere else and went to save, but then it prompted me to save in the wordpad format itself (rtf I think it was) which I didn't, when I simply added a # or two, it just prompted to save without asking for format so it appeared to save as it was and not change anything? So you reckon it still changed it to the non-readable CRLF?
Would basic windows notepad be ok to edit it instead of having to download notepad 2?
Thanks for tyour help so far!
Click to expand...
Click to collapse
Try notepad++
I'm on 2 different AHD. 1 has CM 10.1 RC2/4.2.2 & the other has CM 10.2/4.3. I got the same custom boot animation on both. Its the red umbrella. Any way to add sound?
Sent from my MB886 using xda premium
cmdru1980 said:
I'm on 2 different AHD. 1 has CM 10.1 RC2/4.2.2 & the other has CM 10.2/4.3. I got the same custom boot animation on both. Its the red umbrella. Any way to add sound?
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
--------------------------------------------------------------------------------
(Credit Goes to Infantry667)
The apps:
First you will need a couple apps. You will need absolute system, root explorer and file converter. You can get them from the android market, just do a search for them. They're not free but if you know anything about root you probably already have root explorer and maybe even absolute system, but you will need file converter by ice cold apps.
The programs:
Again if you know anything or a decent amount about root you probably already have these programs but if not then download them. You will need 7Zip (preferably 7Zip) because as far as I know it is one of the only if not the only program that can zip files correctly WITHOUT compression which is mandatory because if there is any compression applied to the bootanimatiom.zip file OT WILL NOT WORK! You will also need either GVIM or Editor++ in order to properly edit the desc.txt file in the bootanimation.zip which we all know is what makes the boot animation work and if that is not configured correctly then, well, you're gonna be throwing things.
The method:
1.
Find the boot animation you want and download it using absolute system or from whatever source, whether it be from a forum thread or whatever. If you download it from a source other than absolute system you have to make sure before applying it you have to place it on the root of your sd card and make sure it is not named bootanimation.zip if there are other boot animations on your sd card because if they are named the same, obviously, they will overwrite eachother so name them however you want.
2.
Find the sound you want to use, it can be any sound file as long as it's short enough (or not) to play completely on boot. Download it, place it in your sd card and open the file converter app. Use file converter to find the file and once you've found and selected it select to convert it to .ogg. It MUST be converted to .ogg or it WILL NOT work. Once it is converted find the converted version ("sound".ogg or "whatever you named it".ogg) and use root explorer to move it to /sytem/media and leave it there for now.
3.
Plug your phone in to your computer, make sure USB debugging is enabled, and put your phone into USB mass storage mode once your phone is connected. Open up the files from your sd card on your computer and find the boot animation .zip you are going to change and move it to your computer. Next open up 7Zip and find the boot animation .zip file you just moved. Select the file and extract it to wherever you want to on your computer. Once you have extracted the .zip files with 7Zip go to the extracted files on your computer.
Note: (This next part will save the edited version as the orginal version so if you want to make a backup before you edit it just rename however you want or copy it into a separate folder named desc backup.)
4.
Right click on the extracted desc.txt file from the boot animation amd right click on it. Once you right click you will see an option that says either "edit with Editor++" or "edit with VIM" depending on which program you decided on (I prefer Editor++). Select the option and it will open up the desc.txt in your editor of choice. There may be a lost of guidelines in the desc.txt file for editing parts of the desc.txt but this is usually only in stock boot animations. Decide where you want the sound file to play and comment in the sound file you want to use by adding a line under the part you choose it to play at by typing "s 'sound'.ogg" DO NOT type what I wrote verbatim, the name 'sound' is just to give an example. Here is an example of a desc.txt file that has been edited to have sound:
(The red part is the sound line)
Quote:
# 540 wide, 960 tall 10 frames per second
540 960 10
# p means we're defining a part
# first number is repeat count, 0 means infinite
# second number is delay in frames before performing the next part
# so if you are playing 15 frames a second 15 would be... one second
# string defines the directory to load files from
# files will be loaded in order but names don't matter
# s defines a sound for a part
# sounds will be loaded from /system/media
# oggs with loop points will loop automatically
# only one sound will play at a time
# timing is driven by the part, not the sounds
# if you want no sound, leave blank
# droid
p 1 0 01_droid
s Fusion.ogg
# fusion
p 1 0 02_fusion
# mobility
p 1 0 03_mobility
# loop
p 0 0 04_loop
Notice the name of the sound in the desc.txt file is the same as the one I want to use. I hate to sound like I'm trying to make you feel stupid, which I am most definitely not, I just want to make sure this is detailed enough for anyone to follow.
4. Continued:
Once you have commented in the sound line, and you can add as many as you want just make sure you read the guidelines in the example desc.txt file above, save the file and exit your editor.
5. Open 7Zip and find the extracted boot animation files again with the edited desc.txt file. Make sure that the only files showing up in 7Zip are the boot animation files you extracted including the original desc.txt file that was edited and only that edited one, not the backup if you made one. In the menu bar on the 7Zip program click on "edit" and click on "select all" in the drop down menu that pops up. Next click "file" in the menu bar, move your cursor to the 7Zip option and when the drop down menu pops up click on "add to archive..." Then when the window pops up just change the name to whatever you want, select "zip" in the Archive format drop down menu, select "store" in the compression level drop down menu (you must select store or the boot animation .zip file you are creating will be compressed and as I mentioned above it won't work with compression) and then click "OK" to create the .zip file. Once it is created go ahead and move it onto the root of your sd card.
6. Unplug your phone from your computer and once the sd card is mounted open up absolute system. Go to boot animations and press menu and selct "boot animation editor." Press menu again and select "import from sd card." Find the boot animation you edited and slect it. Pres menu once it brings up the window with all the .png images and select "import" and when the window pops up prompting you to name the bootanimatiom just name it however you want and select "import." In order for the boot animation you edited to show up in your list of downloaded boot animations in absolute system you must first close absolute system and reopen it, go into boot animation editor again and it should be there. Select your edited boot animation and when it opens up the window with all the .png images press menu and select "desc.txt editor" which will open up the desc.txt file in absolute systems own editor. Scroll down untill you see the "s" line you commented in and press on it, this will open up a small window prompting you to choose the file from either /data/local or /system/media. Selct to choos from /system/media and there will be a list of .ogg files to choose from (if there are more than one you put in there). Select which one you want to play for that line. This is just to make sure the bootanimation.zip is using the right .ogg file and so your phone knows where to play it from on boot. You can change these if you want but you cannot comment lines in or out using absolute system. Once you have finished making changes or confirming the sound files press menu and select "save changes." Once it's done saving the changes press back.
NOTE: THIS NEXT PART IS VERY IMPORTANT AND MUST BE DONE EXACTLY AS I HAVE WRITTEN, IN THE EXACT SAME SEQUENCE I AM GIVING YOU.
7.Sorry for yelling hehe. Once absolute system is done saving the desc.txt file and you have pressed back to re-enter the .png images window in absolute system press home and open up root explorer. In root explorer go to /system/media where you placed your .ogg files and move them again into /system/media/audio/notifications and press home key again. Open absolute system and install the boot animation to /data/local by selecting change install location and selecting "/data/local" and reboot your phone. If the sound does not play, which it should, install the boot animation in BOTH /data/local AND /system/media using absolute system.
You should now have sound along with your boot animation. I hope you all have fun adding crazy sounds to your boot animations. The thanks button is always happy when you press it!
Rick1488 said:
--------------------------------------------------------------------------------
(Credit Goes to Infantry667)
The apps:
First you will need a couple apps. You will need absolute system, root explorer and file converter. You can get them from the android market, just do a search for them. They're not free but if you know anything about root you probably already have root explorer and maybe even absolute system, but you will need file converter by ice cold apps.
The programs:
Again if you know anything or a decent amount about root you probably already have these programs but if not then download them. You will need 7Zip (preferably 7Zip) because as far as I know it is one of the only if not the only program that can zip files correctly WITHOUT compression which is mandatory because if there is any compression applied to the bootanimatiom.zip file OT WILL NOT WORK! You will also need either GVIM or Editor++ in order to properly edit the desc.txt file in the bootanimation.zip which we all know is what makes the boot animation work and if that is not configured correctly then, well, you're gonna be throwing things.
The method:
1.
Find the boot animation you want and download it using absolute system or from whatever source, whether it be from a forum thread or whatever. If you download it from a source other than absolute system you have to make sure before applying it you have to place it on the root of your sd card and make sure it is not named bootanimation.zip if there are other boot animations on your sd card because if they are named the same, obviously, they will overwrite eachother so name them however you want.
2.
Find the sound you want to use, it can be any sound file as long as it's short enough (or not) to play completely on boot. Download it, place it in your sd card and open the file converter app. Use file converter to find the file and once you've found and selected it select to convert it to .ogg. It MUST be converted to .ogg or it WILL NOT work. Once it is converted find the converted version ("sound".ogg or "whatever you named it".ogg) and use root explorer to move it to /sytem/media and leave it there for now.
3.
Plug your phone in to your computer, make sure USB debugging is enabled, and put your phone into USB mass storage mode once your phone is connected. Open up the files from your sd card on your computer and find the boot animation .zip you are going to change and move it to your computer. Next open up 7Zip and find the boot animation .zip file you just moved. Select the file and extract it to wherever you want to on your computer. Once you have extracted the .zip files with 7Zip go to the extracted files on your computer.
Note: (This next part will save the edited version as the orginal version so if you want to make a backup before you edit it just rename however you want or copy it into a separate folder named desc backup.)
4.
Right click on the extracted desc.txt file from the boot animation amd right click on it. Once you right click you will see an option that says either "edit with Editor++" or "edit with VIM" depending on which program you decided on (I prefer Editor++). Select the option and it will open up the desc.txt in your editor of choice. There may be a lost of guidelines in the desc.txt file for editing parts of the desc.txt but this is usually only in stock boot animations. Decide where you want the sound file to play and comment in the sound file you want to use by adding a line under the part you choose it to play at by typing "s 'sound'.ogg" DO NOT type what I wrote verbatim, the name 'sound' is just to give an example. Here is an example of a desc.txt file that has been edited to have sound:
(The red part is the sound line)
Quote:
# 540 wide, 960 tall 10 frames per second
540 960 10
# p means we're defining a part
# first number is repeat count, 0 means infinite
# second number is delay in frames before performing the next part
# so if you are playing 15 frames a second 15 would be... one second
# string defines the directory to load files from
# files will be loaded in order but names don't matter
# s defines a sound for a part
# sounds will be loaded from /system/media
# oggs with loop points will loop automatically
# only one sound will play at a time
# timing is driven by the part, not the sounds
# if you want no sound, leave blank
# droid
p 1 0 01_droid
s Fusion.ogg
# fusion
p 1 0 02_fusion
# mobility
p 1 0 03_mobility
# loop
p 0 0 04_loop
Notice the name of the sound in the desc.txt file is the same as the one I want to use. I hate to sound like I'm trying to make you feel stupid, which I am most definitely not, I just want to make sure this is detailed enough for anyone to follow.
4. Continued:
Once you have commented in the sound line, and you can add as many as you want just make sure you read the guidelines in the example desc.txt file above, save the file and exit your editor.
5. Open 7Zip and find the extracted boot animation files again with the edited desc.txt file. Make sure that the only files showing up in 7Zip are the boot animation files you extracted including the original desc.txt file that was edited and only that edited one, not the backup if you made one. In the menu bar on the 7Zip program click on "edit" and click on "select all" in the drop down menu that pops up. Next click "file" in the menu bar, move your cursor to the 7Zip option and when the drop down menu pops up click on "add to archive..." Then when the window pops up just change the name to whatever you want, select "zip" in the Archive format drop down menu, select "store" in the compression level drop down menu (you must select store or the boot animation .zip file you are creating will be compressed and as I mentioned above it won't work with compression) and then click "OK" to create the .zip file. Once it is created go ahead and move it onto the root of your sd card.
6. Unplug your phone from your computer and once the sd card is mounted open up absolute system. Go to boot animations and press menu and selct "boot animation editor." Press menu again and select "import from sd card." Find the boot animation you edited and slect it. Pres menu once it brings up the window with all the .png images and select "import" and when the window pops up prompting you to name the bootanimatiom just name it however you want and select "import." In order for the boot animation you edited to show up in your list of downloaded boot animations in absolute system you must first close absolute system and reopen it, go into boot animation editor again and it should be there. Select your edited boot animation and when it opens up the window with all the .png images press menu and select "desc.txt editor" which will open up the desc.txt file in absolute systems own editor. Scroll down untill you see the "s" line you commented in and press on it, this will open up a small window prompting you to choose the file from either /data/local or /system/media. Selct to choos from /system/media and there will be a list of .ogg files to choose from (if there are more than one you put in there). Select which one you want to play for that line. This is just to make sure the bootanimation.zip is using the right .ogg file and so your phone knows where to play it from on boot. You can change these if you want but you cannot comment lines in or out using absolute system. Once you have finished making changes or confirming the sound files press menu and select "save changes." Once it's done saving the changes press back.
NOTE: THIS NEXT PART IS VERY IMPORTANT AND MUST BE DONE EXACTLY AS I HAVE WRITTEN, IN THE EXACT SAME SEQUENCE I AM GIVING YOU.
7.Sorry for yelling hehe. Once absolute system is done saving the desc.txt file and you have pressed back to re-enter the .png images window in absolute system press home and open up root explorer. In root explorer go to /system/media where you placed your .ogg files and move them again into /system/media/audio/notifications and press home key again. Open absolute system and install the boot animation to /data/local by selecting change install location and selecting "/data/local" and reboot your phone. If the sound does not play, which it should, install the boot animation in BOTH /data/local AND /system/media using absolute system.
You should now have sound along with your boot animation. I hope you all have fun adding crazy sounds to your boot animations. The thanks button is always happy when you press it!
Click to expand...
Click to collapse
For some reason when i try and use bootanimation editor with absolute system, it force closes and unroots my phone so, I gotta go to recovery and erase & restore. I've just been business ES for a explorer cause it does everything I need it to, I think but as far as 7-zip & store on a PC and put it back on card, I got that down.
Did you get it working? I know you don't have to use the programs they are requesting as I used what works for me so you can do the same. I will however say the boot sound annoyed me so In the end I removed it.
Rick1488 said:
Did you get it working? I know you don't have to use the programs they are requesting as I used what works for me so you can do the same. I will however say the boot sound annoyed me so In the end I removed it.
Click to expand...
Click to collapse
Naw. Never got it. I love music. I have 50,000 songs on a hard drive and I like to theme my phones to a certain artist, including splash and boot. I've got two AHD and was gonna do 2 different ones but, without the sound.....
Sent from my MB886 using xda premium
Rick1488 said:
Did you get it working? I know you don't have to use the programs they are requesting as I used what works for me so you can do the same. I will however say the boot sound annoyed me so In the end I removed it.
Click to expand...
Click to collapse
How'd you do it?
Sent from my MB886 using xda premium
Rick1488 said:
--------------------------------------------------------------------------------
(Credit Goes to Infantry667)
The apps:
First you will need a couple apps. You will need absolute system, root explorer and file converter. You can get them from the android market, just do a search for them. They're not free but if you know anything about root you probably already have root explorer and maybe even absolute system, but you will need file converter by ice cold apps.
The programs:
Again if you know anything or a decent amount about root you probably already have these programs but if not then download them. You will need 7Zip (preferably 7Zip) because as far as I know it is one of the only if not the only program that can zip files correctly WITHOUT compression which is mandatory because if there is any compression applied to the bootanimatiom.zip file OT WILL NOT WORK! You will also need either GVIM or Editor++ in order to properly edit the desc.txt file in the bootanimation.zip which we all know is what makes the boot animation work and if that is not configured correctly then, well, you're gonna be throwing things.
The method:
1.
Find the boot animation you want and download it using absolute system or from whatever source, whether it be from a forum thread or whatever. If you download it from a source other than absolute system you have to make sure before applying it you have to place it on the root of your sd card and make sure it is not named bootanimation.zip if there are other boot animations on your sd card because if they are named the same, obviously, they will overwrite eachother so name them however you want.
2.
Find the sound you want to use, it can be any sound file as long as it's short enough (or not) to play completely on boot. Download it, place it in your sd card and open the file converter app. Use file converter to find the file and once you've found and selected it select to convert it to .ogg. It MUST be converted to .ogg or it WILL NOT work. Once it is converted find the converted version ("sound".ogg or "whatever you named it".ogg) and use root explorer to move it to /sytem/media and leave it there for now.
3.
Plug your phone in to your computer, make sure USB debugging is enabled, and put your phone into USB mass storage mode once your phone is connected. Open up the files from your sd card on your computer and find the boot animation .zip you are going to change and move it to your computer. Next open up 7Zip and find the boot animation .zip file you just moved. Select the file and extract it to wherever you want to on your computer. Once you have extracted the .zip files with 7Zip go to the extracted files on your computer.
Note: (This next part will save the edited version as the orginal version so if you want to make a backup before you edit it just rename however you want or copy it into a separate folder named desc backup.)
4.
Right click on the extracted desc.txt file from the boot animation amd right click on it. Once you right click you will see an option that says either "edit with Editor++" or "edit with VIM" depending on which program you decided on (I prefer Editor++). Select the option and it will open up the desc.txt in your editor of choice. There may be a lost of guidelines in the desc.txt file for editing parts of the desc.txt but this is usually only in stock boot animations. Decide where you want the sound file to play and comment in the sound file you want to use by adding a line under the part you choose it to play at by typing "s 'sound'.ogg" DO NOT type what I wrote verbatim, the name 'sound' is just to give an example. Here is an example of a desc.txt file that has been edited to have sound:
(The red part is the sound line)
Quote:
# 540 wide, 960 tall 10 frames per second
540 960 10
# p means we're defining a part
# first number is repeat count, 0 means infinite
# second number is delay in frames before performing the next part
# so if you are playing 15 frames a second 15 would be... one second
# string defines the directory to load files from
# files will be loaded in order but names don't matter
# s defines a sound for a part
# sounds will be loaded from /system/media
# oggs with loop points will loop automatically
# only one sound will play at a time
# timing is driven by the part, not the sounds
# if you want no sound, leave blank
# droid
p 1 0 01_droid
s Fusion.ogg
# fusion
p 1 0 02_fusion
# mobility
p 1 0 03_mobility
# loop
p 0 0 04_loop
Notice the name of the sound in the desc.txt file is the same as the one I want to use. I hate to sound like I'm trying to make you feel stupid, which I am most definitely not, I just want to make sure this is detailed enough for anyone to follow.
4. Continued:
Once you have commented in the sound line, and you can add as many as you want just make sure you read the guidelines in the example desc.txt file above, save the file and exit your editor.
5. Open 7Zip and find the extracted boot animation files again with the edited desc.txt file. Make sure that the only files showing up in 7Zip are the boot animation files you extracted including the original desc.txt file that was edited and only that edited one, not the backup if you made one. In the menu bar on the 7Zip program click on "edit" and click on "select all" in the drop down menu that pops up. Next click "file" in the menu bar, move your cursor to the 7Zip option and when the drop down menu pops up click on "add to archive..." Then when the window pops up just change the name to whatever you want, select "zip" in the Archive format drop down menu, select "store" in the compression level drop down menu (you must select store or the boot animation .zip file you are creating will be compressed and as I mentioned above it won't work with compression) and then click "OK" to create the .zip file. Once it is created go ahead and move it onto the root of your sd card.
6. Unplug your phone from your computer and once the sd card is mounted open up absolute system. Go to boot animations and press menu and selct "boot animation editor." Press menu again and select "import from sd card." Find the boot animation you edited and slect it. Pres menu once it brings up the window with all the .png images and select "import" and when the window pops up prompting you to name the bootanimatiom just name it however you want and select "import." In order for the boot animation you edited to show up in your list of downloaded boot animations in absolute system you must first close absolute system and reopen it, go into boot animation editor again and it should be there. Select your edited boot animation and when it opens up the window with all the .png images press menu and select "desc.txt editor" which will open up the desc.txt file in absolute systems own editor. Scroll down untill you see the "s" line you commented in and press on it, this will open up a small window prompting you to choose the file from either /data/local or /system/media. Selct to choos from /system/media and there will be a list of .ogg files to choose from (if there are more than one you put in there). Select which one you want to play for that line. This is just to make sure the bootanimation.zip is using the right .ogg file and so your phone knows where to play it from on boot. You can change these if you want but you cannot comment lines in or out using absolute system. Once you have finished making changes or confirming the sound files press menu and select "save changes." Once it's done saving the changes press back.
NOTE: THIS NEXT PART IS VERY IMPORTANT AND MUST BE DONE EXACTLY AS I HAVE WRITTEN, IN THE EXACT SAME SEQUENCE I AM GIVING YOU.
7.Sorry for yelling hehe. Once absolute system is done saving the desc.txt file and you have pressed back to re-enter the .png images window in absolute system press home and open up root explorer. In root explorer go to /system/media where you placed your .ogg files and move them again into /system/media/audio/notifications and press home key again. Open absolute system and install the boot animation to /data/local by selecting change install location and selecting "/data/local" and reboot your phone. If the sound does not play, which it should, install the boot animation in BOTH /data/local AND /system/media using absolute system.
You should now have sound along with your boot animation. I hope you all have fun adding crazy sounds to your boot animations. The thanks button is always happy when you press it!
Click to expand...
Click to collapse
what if i use notepad++?
what i got using notepad++ in dsc.txt file was just these things
320 480 12
p 1 0 part0
p 0 0 part1
what is that?
please help..i really like to have sound with bootanimation.
the hellboy said:
what if i use notepad++?
what i got using notepad++ in dsc.txt file was just these things
320 480 12
p 1 0 part0
p 0 0 part1
what is that?
please help..i really like to have sound with bootanimation.
Click to expand...
Click to collapse
Notepad ++ is perfect for this job.
The P means we're defining a part
S defines a sound for a part.
So, what you have there is a boot logo with no sound.
I wish I could help you further, but you need to read the tutorial and post your issue if any and I'll help...
Let me give you a tip 4.11 stock rom's boot logo comes with sound so all I did was edit it with a new boot logo and my own sound. I guess this might be lazy, but it was fast and simple and I ended up dumping the sound about a week later. Annoying!
Rick1488 said:
Notepad ++ is perfect for this job.
The P means we're defining a part
S defines a sound for a part.
So, what you have there is a boot logo with no sound.
I wish I could help you further, but you need to read the tutorial and post your issue if any and I'll help...
Let me give you a tip 4.11 stock rom's boot logo comes with sound so all I did was edit it with a new boot logo and my own sound. I guess this might be lazy, but it was fast and simple and I ended up dumping the sound about a week later. Annoying!
Click to expand...
Click to collapse
thanks for the reply bro..
yes i did go through the tutorial and i ended up with that i quoted before..
i want to have sony make.believe bootanimation with sound..
but i failed..
so where in desc.txt file edit or put sound?
i mean how do i need to edit those parts..if i wanted to put the audio named bootanim?
please help?
and at last is this just for stock roms or even can work in aosp based roms..
i am running 4.3 legacy xperia latese nightly build right now..
any suggestions or help would be appreciated from bottom of the heart..
Hellboy, if you want you could upload your failed boot animation and I'll fix it for you. Sound good? Oh and for your other question this works for all rooted ROMs.
Sent from my MB886 using Tapatalk 4
I did all that and still no sound AND blank screen during part1. I was just using a 2 part bootanimation.
Sent from my MB886 using xda premium
OK, I'm using OSE ROM now and I did everything except for using absolute system. Mine goes
p 0 0 part0
s att_pu.ogg
att_pu.ogg is what I named my sound and both bootanimation.zip & att_pu.ogg are in /system/media/. Still no sound.
Sent from my MB886 using xda premium
I open this up to the broader community for discussion: Where do you think custom bootanimations should be stored on Lollipop devices?
Android 5.0 introduces a new /oem partition, that allows for a /oem/media/bootanimation.zip file that seems to take precedence over a system/media/bootanimation.zip file (although I haven't checked AOSP source yet to confirm the exact logic). So far only AT&T+Motorola has utilized this functionality on the AT&T-branded Nexus 6, although I imagine many more OEMs will follow, given the added simplicity it provides.
Given this new option, I humbly suggest that the bootanimation community collectively decide to start placing their bootanimations in oem/media/ (via manual directions and flashable zips) for Lollipop devices, for a number of reasons:
- If a device has a pre-loaded /oem/media/bootanimation.zip, the current flashable zips and manual directions to place at /system/media/bootanimation.zip simply will not work (/oem takes precedence)
- Placing the animation on the /oem partition will persist through an OTA update, ROM update, etc.
- Placing the animation on the /oem partition preserves the ability to receive OTA updates, while placing on the /system partition causes Android 5.0+ updates to fail
Ideally, all flashable zips would contain an updater-script that is more thoughtful than all that I've seen to date; specifically testing for an /oem partition and reacting appropriately.
I haven't looked at source yet, but it's interesting to note that /oem/media/bootanimation.zip seems to supercede /system/media/bootanimation.zip (if /oem is present, then only /oem matters), however /oem/media/audio is additive (ringtones and notifications from both /oem and /system are available to the user).
there are only 2 places to boot a boot animation into.. 1st is /system/media/, but its temporary there, and will get replaced when you flash a rom. 2nd place is /data/local/, there it will not get replaced if you flash a rom.
DA6030 said:
I haven't looked at source yet, but it's interesting to note that /oem/media/bootanimation.zip seems to supercede /system/media/bootanimation.zip (if /oem is present, then only /oem matters), however /oem/media/audio is additive (ringtones and notifications from both /oem and /system are available to the user).
Click to expand...
Click to collapse
That's because audio is selected out of a picklist whereas you cannot choose a boot loader.
Its always been the case that boot animation in /data/local will take over /system/media.
rootSU said:
Its always been the case that boot animation in /data/local will take over /system/media.
Click to expand...
Click to collapse
D'oh, I had forgotten about /data/local. So, that means there are three locations now.
/oem/media is documented in the AT&T Nexus 6 thread, although I'm not sure anyone's checked source to see how it's implemented, nor tested to see where it falls in precedence to /data/local.
http://forum.xda-developers.com/showpost.php?p=56942290&postcount=11
And for reference, looking at the Shamu build.prop, it looks like the oem.prop items are imported explicitly into the build.prop, so the precedence there is clear.
DA6030 said:
D'oh, I had forgotten about /data/local. So, that means there are three locations now.
/oem/media is documented in the AT&T Nexus 6 thread, although I'm not sure anyone's checked source to see how it's implemented, nor tested to see where it falls in precedence to /data/local.
http://forum.xda-developers.com/showpost.php?p=56942290&postcount=11
And for reference, looking at the Shamu build.prop, it looks like the oem.prop items are imported explicitly into the build.prop, so the precedence there is clear.
Click to expand...
Click to collapse
you cant just add it there after manually. and theres another place to put the boot animation, but only when building a rom. i dont remember the location, but you can see it yourself, if you delete the boot animations from /system/media/ and /data/local it will appear. this one just says android
simms22 said:
you cant just add it there after manually. and theres another place to put the boot animation, but only when building a rom. i dont remember the location, but you can see it yourself, if you delete the boot animations from /system/media/ and /data/local it will appear. this one just says android
Click to expand...
Click to collapse
It used to be compiled into the frameworks I think.. Not sure if thats still the case.
Heads UP
Don't know if this is actually what caused my bootloop... but I figured I'd mention it here.
I was trying to get rid of the AT&T boot animation on my N6 and while i was renaming to .bak thought to myself, "why don't I just do my own?" Grabbed another one online, put it in /oem/media/ and bam. No boot.
The worst part is I can't fix it without full restore to stock, because I can't seem to access or even view the /oem/ folder at all through recovery. Is it only mounted after boot?
Don't kow if this means anything to y'all, but I figured someone would find this information interesting.
I have tried several times to make use of the /OEM partition with no success. Every time I reboot the contents disappear.
i tried /data/local to see if it still worked and it didnt work for me....
cmh714 said:
i tried /data/local to see if it still worked and it didnt work for me....
Click to expand...
Click to collapse
i just tried myself, you are right. not working here as well.
simms22 said:
you cant just add it there after manually. and theres another place to put the boot animation, but only when building a rom. i dont remember the location, but you can see it yourself, if you delete the boot animations from /system/media/ and /data/local it will appear. this one just says android
Click to expand...
Click to collapse
It is within framework-res.apk/assets/images/ . . there are two images.
android-logo-mask.png
android-logo-shine.PNG
The mask is a static image with partial transparency. The shine scrolls from left to right behind the mask in a loop, shinning through the mask transparency. It is actually a pretty cool way to do it and I know @rascarlo uses it in rastapop instead of the traditional bootanimation.zip
hlxanthus said:
I have tried several times to make use of the /OEM partition with no success. Every time I reboot the contents disappear.
Click to expand...
Click to collapse
I have also tried (only on stock Google builds), and had the same experience.
OEM partition unformatted on non-ATT devices
hlxanthus said:
I have tried several times to make use of the /OEM partition with no success. Every time I reboot the contents disappear.
Click to expand...
Click to collapse
I just realized that on my device (not AT&T-branded), the /oem partition has always been RAW. So, I flashed the oem.img partition from AT&T firmware (although "fastboot format ext4 oem" would probably be good enough) the partition is now formatted correctly, and now I can use it for storing personalized ringtones, bootanimations, etc. that persist through a factory reset.
DA6030 said:
I just realized that on my device (not AT&T-branded), the /oem partition has always been RAW. So, I flashed the oem.img partition from AT&T firmware (although "fastboot format ext4 oem" would probably be good enough) the partition is now formatted correctly, and now I can use it for storing personalized ringtones, bootanimations, etc. that persist through a factory reset.
Click to expand...
Click to collapse
Okay, I gotta ask. I haven't been able to find the OEM.IMG in any of my searches, just the contents found there. I wasn't aware of any att specific factory images . . got a link you can share? If you don't remember, could you upload the IMG?
hlxanthus said:
Okay, I gotta ask. I haven't been able to find the OEM.IMG in any of my searches, just the contents found there. I wasn't aware of any att specific factory images . . got a link you can share? If you don't remember, could you upload the IMG?
Click to expand...
Click to collapse
There are definitely firmware repositories other than the official Google Developers site. The one I'm thinking of hosts the full .zip file they apply using mfastboot at the factory, which includes the signed oem.img, as well as radio parameters (e.g., SIM lock/unlock for subsidized phones). I can't remember XDA's policy on linking to other sites, so I'll leave it to say that if I search for "Motorola Firmware" (incognito, to avoid personalized search results) it's the 3rd and 4th link right now. The specific file you're looking for is SHAMU_LMY47D_release-keys_subsidy-ATT_CFC.xml.zip. I want you to find it, so if that's not helpful, let me know.
DA6030 said:
There are definitely firmware repositories other than the official Google Developers site. The one I'm thinking of hosts the full .zip file they apply using mfastboot at the factory, which includes the signed oem.img, as well as radio parameters (e.g., SIM lock/unlock for subsidized phones). I can't remember XDA's policy on linking to other sites, so I'll leave it to say that if I search for "Motorola Firmware" (incognito, to avoid personalized search results) it's the 3rd and 4th link right now. The specific file you're looking for is SHAMU_LMY47D_release-keys_subsidy-ATT_CFC.xml.zip. I want you to find it, so if that's not helpful, let me know.
Click to expand...
Click to collapse
Found it, thanks!
Edit: for the record fastboot format didn't work on OEM as it won't work on raw partitions. Extracted and flashed it just as you suggested and now have the crazy att boot animation . . which I will be deleting right now. Thanks a bunch. I will likely post something soon for people who wish to do this themselves.
For those interested in this, here is the OEM.IMG. Once I play with it some more I will open a dedicated thread on how to make use of this partition.
As a little teaser, as expected you can place and set default ringtone, alarm and notification tones. Or add a bootanimation.zip. What I expected to work though did, adding user apps to it. Simply create a directory of /app within the oem partion and place your apps in there. It should be noted there is only about 50mb of space in there. I simply used a file manager to go to the /data/app and copy the desired app folder to the oem partition.(not sure you have to but I simply mirrored the file structure used there). In my case I added a copy of Root Explorer and Titanium Backup in there so they are present for all new rom installs.
Download - SHAMU_subsidy-ATT_OEM.zip
hlxanthus said:
Edit: for the record fastboot format didn't work on OEM as it won't work on raw partitions. Extracted and flashed it just as you suggested and now have the crazy att boot animation . . which I will be deleting right now. Thanks a bunch. I will likely post something soon for people who wish to do this themselves.
As a little teaser, as expected you can place and set default ringtone, alarm and notification tones. Or add a bootanimation.zip. What I expected to work though did, adding user apps to it. Simply create a directory of /app within the oem partion and place your apps in there. It should be noted there is only about 50mb of space in there. I simply used a file manager to go to the /data/app and copy the desired app folder to the oem partition.(not sure you have to but I simply mirrored the file structure used there). In my case I added a copy of Root Explorer and Titanium Backup in there so they are present for all new rom installs.
Click to expand...
Click to collapse
That's a great discovery! Would you consider submitting this as a feature request to Titanium Backup ("move app to oem partition")?
Such a pity the partition can't be formatted from fastboot. Did you try including all the option parameters (ext4 and size)? Do you think it could work from the terminal in recovery (and therefore flashable zip)?
DA6030 said:
That's a great discovery! Would you consider submitting this as a feature request to Titanium Backup ("move app to oem partition")?
Such a pity the partition can't be formatted from fastboot. Did you try including all the option parameters (ext4 and size)? Do you think it could work from the terminal in recovery (and therefore flashable zip)?
Click to expand...
Click to collapse
Alas, I tried just a few variables with fastboot format and gave up and just flashed the OEM.IMG. But fastboot did throw an error stating it could not use the format function on a RAW partition, so I don't know if there is some variable that may have worked.
Only real problem is now that I have it formated I can no longer really test what may or may not work. I can play with it some and see if OEM is accessible via recovery (it is not shown in twrp file manager, that I do know). I have a few shamu guys I can call upon to test, so if I think something might work I will give it a shot.
As for any official TiBu support I doubt it would be accepted, the partition is only 50mb so not a lot of room for stuff.
hlxanthus said:
I can play with it some and see if OEM is accessible via recovery (it is not shown in twrp file manager, that I do know). I have a few shamu guys I can call upon to test, so if I think something might work I will give it a shot.
Click to expand...
Click to collapse
Oh, really good point - TWRP support (at minimum ability to for AT&T customers to wipe the partition, but also file manager) is a way better idea. If your shamu guys are able to format /dev/block/platform/dw_mmc.0/by-name/oem from RAW to ext4 using the appropriate updater-script or recovery terminal command, that would be great to point that out to the TWRP team, to add support for format and file manager. Worst case, I would think TWRP could implement wipe (for AT&T customers) using a delete_recursive. And if format is entirely off the table, one could accomplish the same thing with a flashable zip that flashes the AT&T oem.img and then does a delete_recursive.
By the way, have you tried the format commands in any of fastboot, updater-script or recovery terminal to format your ext4 partition back to RAW?
I've updated my device today to 6.0.1 and rooted, however I can't seem to change the boot animation (yes, I have searched for answers and tried quite a few fixes).
Root Explorer tells me I have renamed the old file and copied the new file, however once I leave the directory and go back the old file is still there.
I have used the file explorer in TWRP and managed to delete the stock boot animation, but get a FAILED message when I try to copy the new file.
I used the terminal in TWRP and tried to copy the file manually, and receive a "No space left on device" message.
I've also tried mounting the /system as rw in adb. I can delete the bootanimation.zip file from there, and df -h shows 3mb free. Shouldn't the system partition have more space available than that?
Am I missing something, or has something changed with the new android versions?
Google has filled the system partition up to the brim. Also you can't remount system as rw while Android is running.
But the direction is right, go to TWRP, mount system, delete the old bootanimation. If the new one is not that much bigger then you could just copy it there, set permissions to rw-r--r--. But if the new animation is significantly bigger, you'll have to delete some bloatware first.
Thanks for that. The odd thing is, when I run DF in the terminal, it shows I have 20mb free. The boot animation file I am trying to copy is 6mb.
I'll keep poking around. If it doesn't work, it doesn't. It's not hugely important