Related
I've found some commands to use but I am not sure if I've done them correctly. I was able to get a file out of the commands (a .apk file) but it seemed to be created as a document rather than a unix executable file. The icon appears as a sheet of paper rather than that black box of other executable files. I am on a mac right now so anyone familiar with it on a mac would be a great help.
What about just adding the .apk extention? cp /filepath/ /sdcard/app.apk then mount the sdcard and pull it over if you can't work out adb.
evilkorn said:
What about just adding the .apk extention? cp /filepath/ /sdcard/app.apk then mount the sdcard and pull it over if you can't work out adb.
Click to expand...
Click to collapse
When I change a file name and save it as a .apk, it doesn't seem to truly save it as a .apk. Normally, on a mac, .apk's are seen as a unix executable file and the icon is a little black square. If I change a files extension to <filename.apk> it just sees it as a document with the name <filename.apk>, NOT <filename>.apk. It doesn't recognize the file as a true .apk. I'm not sure if that makes sense but its a much more difficult process on a mac than it is on a PC. If i save a file with .apk at the end then try to sign it, an error comes up saying that the file is not a file.
apk's are just zip files with a signing signature, they "unpack" like a zip/rar archive. There is no reason to open them with terminal. They are either damaged or you didn't copy them off your phone correctly, see the second sentence of my post.
I know what you mean and I know how they work, I'm just not explaining myself correctly...I think I have it figured out though.
Here's a tutorial for those wanting to make their own (animated) bootscreen for the HTC Hero. Decided to write it after I'd seen a couple of posts from people asking about this, and some encouragement from yet another. I've tried to write this in greatest detail possible, so everyone can have a go at doing this.
Tools
It's really quite simple, if you have the proper tools for the job:
SignAPK.jar + testkey.pk8 + testkey.x509.pem
SignAPK.cmd (batch file written by me to facilitate signapk.jar use)
Graphics editor that can work with animated GIF files (Adobe Photoshop or Fireworks recommended)
a plain text editor capable of editing UNIX files (if you're unsure about this, use the free, and open source Notepad++. You can get the Installer.exe here.)
These aren't required, but make things easier:
Android SDK Tools installed (working adb.exe at the very least)
Hero's stock bootscreen to start from)
I have attached two stock Hero bootscreens (one with and one without the HTC startup sound), as well a zip file with the signapk files.
Setting up SignAPK
First, make sure you have Java installed. If not go to www.java.com to install it.
Second, I recommend to unzip the SignAPK_xda.zip file to C:\SignAPK.
Lastly, add the signapk folder to your PATH environment variable:
[*]Go to Control Panel, System
[*]Click on "Advanced" (or "Advanced System Settings")
[*]Click the button "Environment Variables..."
[*]Locate the PATH variable under "User Variables" (or "System variables" if you want to use SignAPK under other user accounts) and double-click it to edit
[*]In the "Variable Value" field, at the end of the line, type a semi-colon and the path to the signapk files ;C:\SignAPK
[*]You could also add the path to your java.exe file here if you have troubles with running signapk.​
A note on signapk.CMD
I wrote this batch file so it's possible to sign a zip file from a command line with the least amount of typing (saves time and less chance of a typo). It will check for java.exe and if it doesn't find it in your %PATH% it will let you know and try anyway. It will also prompt you to overwrite or not, if it finds the signed destination file already exists. Open in notepad to find out more.
Contents of bootscreen_stock.zip
You can delete the following three files, as they are created by the signing process:
META-INF\CERT.RSA
META-INF\CERT.SF
META-INF\MANIFEST.MF
This file contains the command to copy the files to the SYSTEM: volume on your device - you never need to edit this:
META-INF\com\google\android\update-script
This file tells Android how and which files to display - open in Notepad++:
system\media\bootscreen\boot_animation.xml
Then we have the actual bootscreen files:
system\media\bootscreen\boot1.gif - shown first, and plays only once
system\media\bootscreen\boot2.gif - shown after first ends, and loops forever (i.e. until end of boot sequence)
system\media\bootscreen\boot_bg.gif - optional file, this file is used as background during entire boot sequence if the 2 aforementioned files are smaller than Hero's screen
system\media\bootscreen\boot.mp3 - optional sound file, played once during boot
boot_animation.xml file contents
Code:
<?xml version="1.0" encoding="utf-8"?>
<!--
* Copyright (C) 2008 HTC Inc.
*
-->
[COLOR="Red"]<!-- For new bootup animation
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
image2="/system/media/bootscreen/boot2.gif" (optional)
image3="/system/media/bootscreen/boot3.gif" (optional)
screenX="100" (optional)
screenY="130" (optional)
image_bg = "/system/media/bootscreen/boot_bg.gif" (optional)
useAudio="1" // 1: true ; 0:false (optional)
/>
</BootConfiguration>
-->
[/COLOR]
[COLOR="Green"]<!-- For cropped version -->
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
image2="/system/media/bootscreen/boot2.gif"
image3="/system/media/bootscreen/boot2.gif"
loopimage="/system/media/bootscreen/boot2.gif"
image_bg="/system/media/bootscreen/boot_bg.gif"
audio="/system/media/bootscreen/boot.mp3"
screenX="10"
screenY="180"
useAudio="1"
/>
</BootConfiguration>
[/COLOR]
[COLOR="Red"]<!-- For full screen version -->
<!--BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
useAudio="1"
/>
</BootConfiguration-->[/COLOR]
This is the file included with the stock bootscreen. This file actually contains 3(!) configurations, however the first and third (red-colored) have been commented out. In short, edit the middle (green-colored) "BootConfiguration" section.
Delete the line that begins with image3= as you won't need it.
If you do not wish to include a startup sound, delete lines starting with:
audio=
useaudio=
Alternatively, simply set useAudio=0
If you boot1.gif and boot2.gif files are both 320x480 pixels, delete lines starting with:
image_bg=
screenX=
screenY=
Alternatively, simply set screenX=0 and screenY=0
If you delete the audio= and image_bg= lines, you can ofcourse delete the files audio.mp3 and image_bg.gif to keep the update.zip as small as possible.
ScreenX and ScreenY are coordinates in pixels, that tell Android where to place the GIF files on the screen. Top-left of the screen would be ScreenX=0 and ScreenY=0; bottom-right would be ScreenX=320 and ScreenY=480. This means that if you make a GIF file that is 200 px wide and 180px high and you wish to center this on the screen, you'd use ScreenX=60 and ScreenY=150 (i.e. ScreenX=320-200=120/2=60 and ScreenY=480-180=300/2=150). If your GIF files are exactly 320x480 pixels, you can set ScreenX and ScreenY both to 0, or leave those two lines out entirely.
Creating a GIF animation from scratch
(boot1.gif and boot2.gif)
Using Adobe Photoshop CS4 (cannot speak for older versions, I think you'd need the now discontinued Adobe ImageReady instead):
Create a layer for each frame of your animation (yes, I didn't say creating an animation from scratch wouldn't be a lot of work)
Click Window -> Animation to show the Animation panel
Click the panel menu (top right icon in panel) and choose "Make Frames from Layers"
If the frames are loaded in reverse from what you intended, choose "Reverse Frames" from the Animation panel menu
From the panel menu, choose "Optimize Animation" and UNtick both "Bounding Box" and "Redundant Pixel Removal"
Finally, go to File -> Save for Web & Devices, UNtick "Transparency" and play with some of the options to reduce file size.
To (re-)open an animated GIF file in Photoshop CS4, go to File -> Import -> Video Frames to Layers and type in the file name box *.gif then hit the Enter key so you can see GIF files, browse to it, select and click Load.
Using Adobe Fireworks CS4:
Make sure the "States" panel is visible, via Window -> States
Create a new "State" for each frame of your animation
To set frame delays, or basically set how long each frame will be shown for, in 100ths of a second, select one or more states and right-click, choose "Properties"
Make sure you do not use transparency (this gave me problems)
To save, go to File -> Save As, set "Save as Type" to "Animated GIF (*.gif)" and "click Options"
Do check "Dither" for better looking gradients and transitions
Play with the options on the first tab to reduce file size
On the "Animation" tab, UNcheck "Crop each state" (don't do this and get some crazy glitchy results in your bootscreen)
Creating a GIF animation by converting a G1 bootscreen animation to Hero format
(boot1.gif and boot2.gif)
You can also import a bunch of PNG files as layers (and subsequently frames) from, for example, a G1 bootscreen.
The fastest way in my experience is simply using Fireworks' File -> Open dialog, make sure all files are in one directory, select them all, do check the "Open as Animation" checkbox and click "Open". This will open each file into its own state in one big file. Then use instructions above to set frame delays and proceed to save as animated GIF.
You can also do it in Photoshop, but this method is very slow, via File -> Scripts -> Load Files into Stack (UNtick "Create Smart Object after loading layers"). Then follow the steps above to create an animated GIF file.
Compiling your bootscreen
If you have the files you want, it's time to zip them and then sign the zip file.
Make a folder "mybootscreen" and unzip the stock bootscreen into that, so it looks like this:
META-INF\CERT.RSA
META-INF\CERT.SF
META-INF\MANIFEST.MF
META-INF\com\google\android\update-script
system\media\bootscreen\boot_animation.xml
system\media\bootscreen\boot1.gif
system\media\bootscreen\boot2.gif
system\media\bootscreen\boot_bg.gif
system\media\bootscreen\boot.mp3
Delete those first 3 files, edit the XML file as needed and replace the GIF files with your own (see my explanations above).
Use for example 7-zip to select the 2 folders META-INF and system and click "Add" (to create new archive)
Make sure you set "Archive Format" to ZIP
Open a Command Prompt window (click Start, Run, type cmd and click OK, or if you have Vista or Windows 7, click Start, type cmd and hit Enter key)
Use this command to go to the directory with your zip file: CD /D C:\path\to\your\file
Type signapk mybootscreen.zip and hit Enter key
Barring any typo's you should now have a file named mybootscreen_signed.zip. You can copy that to the root of your SDCARD and flash it via your recovery image, or use DroidExplorer's flash function.
If this tutorial was of any use to you, or you have ideas to make it better, please reply and let me know. Thanks for reading!
EDIT (2010-04-11): updated SignApk_xda_v20100411.zip. Fixed a couple of forgotten quotes in signapk.cmd that made signing files with spaces in their filenames impossible. New zipfile attached.
wooooo THANKS!
THANKS A LOT! I have made the animated gifs and the sound, but I was insure how to sign and create the signed zip. I'll be trying this ASAP when Ive finished work. Ill keep you posted....
Thanks again m8.
Great guide, I have made my own bootscreen for the Villain rom, but for some reason, when i flash it to my hero, on boot, it plays less than a second of it, ad then messes up completely and displays random static like on an old tv, and then just a black screen for the remainder of the boot time
Help!! my gifs are not that big, i made sure of that (only slightly more than the stock) and i made them in photoshop CS4 with the animations panel, and followed your instructions to the letter.
Gifs are bellow, please help, as i would really like to release these, as i think they are really nice.
Boot1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot2
Hey, very nice work! Try the zip I've attached. I think it came out great.
It boils down to a few small problems. Here are some steps I took to correct them:
Imported your files into PS as I described in the tutorial using "Video frames to Layers"
Edit -> Convert to Profile -> sRGB IEC61966-2.1 (UNcheck "Flatten Image")
For just boot1.gif in Animation Panel, bottom left, set looping to "Once"
For just boot1.gif via Image -> Image Size... -> Width:320px, Height:480px, Resolution:72dpi, Check Resample Image and set to "Bicubic"
File -> Save for Web & Devices, with these settings: Selective, Diffusion, UNcheck transparency, UNcheck interlaced, Colors:64 (as this is a grayscale animation, it looks fine), Dither:100%, Matte:none, Web snap:0%, Lossy:0, Metadata:none.
The end result is bigger files, but they work. The XML was fine.
Great! thanks a lot for your help, and your original guide, I might do a few more boot screens now as it looks really good (in my opinion)
mattyyey said:
THANKS A LOT! I have made the animated gifs and the sound, but I was insure how to sign and create the signed zip. I'll be trying this ASAP when Ive finished work. Ill keep you posted....
Thanks again m8.
Click to expand...
Click to collapse
How'd it come out? Would love to see your results!
Really interessant, this is exactly what I was looking for! Thanks for this How-To!
For the signing process I haven't use your "signapk.cmd" (since I'm a linux user)But I have a question: testkey.x509.pem & testkey.pk8 you provied are only to sign app for the Hero? or is it a standard Android singning process? I mean... where are those key from?
For now i've just "resign" the stockbootscreen for "educational purpose", soon I'll try to create something, I hope
EDIT: Okay I was able to resign the original one correctly since I was able to flash it, BUT my bootscreen is still this nexus one animated. So maybe I don't understand wich bootscreen we actually modifing. I know this is not the really first one (this one is fine: spend one day to find that we need a custom SPL to change my ex horrible T-mobile first bootscreen to a Hero one) So why can't I remove the nexus one coming with aHero ROM?
EDIT2: using
Code:
./adb pull /system/media/bootscreen/boot.gif ./Desktop
I get the right image... that mean the files are correctly flashed on my ROM but nothing change so that mean aHero is using a different path for the 2nd bootscreen ???
Thanks for any hint
carbonyle said:
Really interessant, this is exactly what I was looking for! Thanks for this How-To!
Click to expand...
Click to collapse
You're most welcome!
carbonyle said:
For the signing process I haven't use your "signapk.cmd" (since I'm a linux user)But I have a question: testkey.x509.pem & testkey.pk8 you provied are only to sign app for the Hero? or is it a standard Android singning process? I mean... where are those key from?
Click to expand...
Click to collapse
The signapk files (except signapk.cmd) came from a 5MB file named "AndroidMod.zip" that floats around the internet, so to speak. It also contains 3 img files, part of a tutorial I guess, which are not needed for signing. The testkey certificates were created by whomever made that zipfile. The credentials for those files are quite anonymous ("Android" and "[email protected]", etc), so they should be fine to use. You could use openssl to generate your own key files. I tried, and they generated okay, but zips signed with my own certificate wouldn't flash. Recovery (Amon RA) kept saying the files weren't signed. So if you figure out how to properly generate your own certificates, I'd love to hear it.
carbonyle said:
For now i've just "resign" the stockbootscreen for "educational purpose", soon I'll try to create something, I hope
EDIT: Okay I was able to resign the original one correctly since I was able to flash it, BUT my bootscreen is still this nexus one animated. So maybe I don't understand wich bootscreen we actually modifing. I know this is not the really first one (this one is fine: spend one day to find that we need a custom SPL to change my ex horrible T-mobile first bootscreen to a Hero one) So why can't I remove the nexus one coming with aHero ROM?
EDIT2: using
Code:
./adb pull /system/media/bootscreen/boot.gif ./Desktop
I get the right image... that mean the files are correctly flashed on my ROM but nothing change so that mean aHero is using a different path for the 2nd bootscreen ???
Thanks for any hint
Click to expand...
Click to collapse
I don't know I'll download aHero and have a look.
EDIT: Okay, just had a quick look in "aHero07-signed.zip" and it appears Android 2.1 uses a different bootscreen format. Do this:
adb shell
cd /system/media
ls
Instead of a bootscreen directory you'll see a file "bootanimation.zip". Instead of 2 animated GIFs, it contains 2 directories. Each directory is an animation, with a bunch of PNG files for frames. A text file describes which dir is what animation (order of playback) and the delay between frames. If you want to convert a 1.5/1.6 bootscreen from GIFs to seperate PNGs for use in this new format, just open the GIF file in Photoshop (or GIMP I guess) as described and save each frame as a seperate file (Photoshop has a function or script for that, maybe GIMP does too).
Maybe you'll find more information in this thread. I got the Supernova bootscreen graphics (see my sig) from there, which I converted into a bootscreen for Cupcake.
Well, my experience from running 2.1, you can use the bootanimation.zip, or if you delete it and create the bootscreen folder, it also works.
I have the same problem though, when I load up my gif, using the old method, it looks like hells just got unleashed on the gif. Nothing in place, static, etc... I followed your tutorial, tried a couple things, nothing has been working so far...
EDIT: Nvm, found another program to remove the transparency, works now! Got bored, haven't seen any terminal style logins - this works great for my phone, the timing might be different for others though.
To get it working, just delete your bootanimation.zip and flash the zip as usual.
Boot1
Boot2
http://groups.google.com/group/admin-panel-dev/web/terminal_signed.zip
Great tutorial! And nice work that one is Warhawk
I have a problem. I made one by screen capturing some video. Converted it to .gif fine. I can play it in windows fine, but when flashing to android the image just gives a black screen (its only the gif area of the screen cos the animation is only 300x120.
I have provided the .gif above, if anyone can help.
Thanks
I went ahead and removed the transparency from the gif, it showed up on my Hero just fine when I zip/signed it.
Aaah Thanks so much buddy. I swear i tried that though (maybe i made a mistake)
Cheers so much!
I am getting an error after flashing. My installation aborts.
...
Verifying update package...
Installing update...
E:Can't find update script
Installation aborted.
...
Can you help??
quan_one said:
I am getting an error after flashing. My installation aborts.
...
Verifying update package...
Installing update...
E:Can't find update script
Installation aborted.
...
Can you help??
Click to expand...
Click to collapse
Upload your update.zip. Some-one should be able to help.
Did you include the update-script to: \META-INF\com\google\android
Hey guys I created my own boot screen but I am failing to see why my gif will not display on my hero. I have created it from scratch being careful not to include any transparent images or layers but it still displays as a black screen. I am not sure what would cause my gif not to play on my phone other than a transparency issue.
Any help would be more than welcome.
(I am able to sign my zip and flash it no problem)
(edit: The image was my actual .gif but after upload it turn into a jpeg. I will host the file and upload from there.)
My stuff can be found here at mediafire : http://www.mediafire.com/?sharekey=43b651ad9cd91774e7c82ed4b8f0c380e53d1e35008d24d5d8c7c6998cb4ca21
.psd
signed zip
Thanks again!
rejectedkid said:
Hey guys I created my own boot screen but I am failing to see why my gif will not display on my hero. ...
Click to expand...
Click to collapse
You need to go into mybootanimation_signed.zip\system\media\bootscreen and edit your boot_animation.xml.
phaelox said:
...ScreenX and ScreenY are coordinates in pixels, that tell Android where to place the GIF files on the screen. Top-left of the screen would be ScreenX=0 and ScreenY=0; bottom-right would be ScreenX=320 and ScreenY=480. This means that if you make a GIF file that is 200 px wide and 180px high and you wish to center this on the screen, you'd use ScreenX=60 and ScreenY=150 (i.e. ScreenX=320-200=120/2=60 and ScreenY=480-180=300/2=150). If your GIF files are exactly 320x480 pixels, you can set ScreenX and ScreenY both to 0, or leave those two lines out entirely...
Click to expand...
Click to collapse
The difficult thing is that you have two .gifs that are diff sizes so not too sure what to do.
On the one I made, my .gifs are both the same resolution so the value I set for ScreenX and ScreenY work for both.
Look at some other people's .xml files and hope you find someone elses that also uses two different resolution .gifs.
ah. thanks for your input
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
And just because there are no transparent images that you can see or know you put in, doesn't mean that they aren't in there. For some reason, even if I untick Transparent layers in PS, I still get them. I went and got Animation Shop 3, optimized the gif after making it in PS, then re-wrote the file, and everything works fine.
Hope everything is working
Hi !
I have 2 questions :
First one :
To ddotpatel : Your bootscreen is really nice ! Is it working on any 2.1 rom or do I have to change it ? On which rom did you create it ?
And the second one, that tuto is working on 1.5 and 2.1 roms ? Because I heard that it was different to make an 1.5 bootscreen and an 2.1 one...
Thanks for your answers
Ok, I must have posted this question somewhere but I would like to know the answer cause no one has answered it. "how do I get the stock phone app to modify?. How would I get it and put it back into my phone? please I would like to know.
38 views and no response?
the .png files for the phone are actually in the contacts.apk.
Are you asking how to modify the apk, or just specifically where are the phone images?
To copy the app from your phone just do: adb pull /system/app/Phone.apk
That will put a copy of the file in your "tools" directory in the android sdk folder
Then when you want to put it back on you should be able to overwrite it with: adb push /system/app/Phone.apk
What exactly are you planning on doing with this file?
Thank you. I want to create my own images to make it look different then the stock colors.
There are 2 apks that contain dialers, one is the Contacts.apk as stated bfore that brings up the phone when the phone icon is pressed the second is in the Phone.apk appears once a call is placed, and the persons picture appears of the person you are calling.
I don't know how to do a adb pull. can you explain?
johnny quest said:
I don't know how to do a adb pull. can you explain?
Click to expand...
Click to collapse
In terminal or command prompt, navigate to the tools directory in the android SDK and run the following commands:
Code:
adb remount
adb pull /system/app/Phone.apk
That will dump the file in you tools directory.
If you are having trouble with this, let me know what operating system you are using and if you have the android SDK installed.
synesthete said:
In terminal or command prompt, navigate to the tools directory in the android SDK and run the following commands:
Code:
adb remount
adb pull /system/app/Phone.apk
That will dump the file in you tools directory.
If you are having trouble with this, let me know what operating system you are using and if you have the android SDK installed.
Click to expand...
Click to collapse
This is confusing. I didn't think it would be so hard. I do UI's for iphone and ipod touch and this is way different. There are so many different things. Its discouraging in some ways. Sorry. I would love to create an app but of course its different. So, I stick to creating themes.
I would love to take a ROM and mod it myself or even modifying Launcher pro but it has that 9.pngs which makes it hard.
Ok, I have the Eris 2.1 rooted with Tenzo Rcmix2.0 installed. I have the SDK installed but don't know what to do with it. I appreciate you taking the time to help me out. I really want to create and mod lots of apps.
this is what I've done to a phone app I downloaded from the market:
-I created my images through Photoshop and saved them to a folder with its correct name used.
-I opened draw9patch and saved the images with the correct name again to a folder.
-I named the folder drawable-hdpi that belongs in the Res folder
-took the files and folder and created a zip out of it.
-opened the AvaboxV2 and signed it.
-loaded to my phone and changed the name to the correct name and installed it
but it keeps saying application not install, I just don't get it. What step did I messed up on?
Anybody? anybody?...............................
This is what you need to do:
1. Open Contacts.apk in 7-zip
2. Copy the images over top of the original images in drawable, drawable-mdpi, and drawable-mdpi-finger (notice I didn't say anything about hdpi)
3. Close the archive.
4. Copy it back onto the device with:
Code:
adb remount
adb push Contacts.apk /system/app
Your phone may not appreciate you pushing Contacts.apk while it is running, so it may become unstable at this point. I would recommend restarting.
icbeer said:
This is what you need to do:
1. Open Contacts.apk in 7-zip
2. Copy the images over top of the original images in drawable, drawable-mdpi, and drawable-mdpi-finger (notice I didn't say anything about hdpi)
3. Close the archive.
4. Copy it back onto the device with:
Code:
adb remount
adb push Contacts.apk /system/app
Your phone may not appreciate you pushing Contacts.apk while it is running, so it may become unstable at this point. I would recommend restarting.
Click to expand...
Click to collapse
thank you but I'm trying to understand what you mean by push ADB. is that the one in the sdk folder? if so, I open it and it just flashes for a few seconds then closes.
ADB is a command line program that allows you to debug and move/edit files on your phone. You need to run those commands from a command prompt (should be a link in the Accessories folder on the Start menu if you can't right-click on the sdk folder and open one). Navigate to the tools folder, then run the remount and push commands like icbeer said to get your modified .apk on your phone:
Code:
C:\users\brtnbrdr> cd c:\android-sdk-windows\tools
C:\android-sdk-windows\tools> adb remount
C:\android-sdk-windows\tools> adb push Contacts.apk /system/app
I know there are other methods out there for achieving the same thing. And I have touched on a few "after thoughts" in the actual process of loading the image to the phone. If these can be confirmed, please feel free to update these instructions. After browsing many, many pages in forum after forum I was unsuccessful in finding anything detailed enough from start to finish. So I decided to write this up!
These instructions work for anyone who rooted using the "UnrEVOked" method such as that given at HTCEvoHacks.com. I have not tested these instructions with any other root method out there.
With a bit of practice, this method can be mastered and done in about 20 minutes (depending on how long you spend creating your splash image in PhotoShop)
For the sake of these instructions, all references and instructions dealing with PhotoShop are assuming you are using PhotoShop CS5. Commands may be slightly different on older versions of PhotoShop, so it may take a few extra clicks to find what you're looking for.
1. You can download custom boot images from the web, or create your own in PhotoShop using ANY sort of photo, graphics, text, or combination. You MUST make sure that the image size is set as the same for the EVO's screen resolution (480x800). For this reason, I would double check any image file you try to use prior to converting it for use with your phone.
2. Open your image file in Photoshop and make whatever tweaks or enhancements you like. Remember to "flatten" the image prior to saving it out if you have multiple layers in your file. You can use the next step to re-size the image first if you like, but depending on your current settings in PS it should not matter.
3. Right click the file window (the one that contains your image) and set the "Image Size" settings to a width of 480, and the height to 800. These measurements MUST be in pixels as well. If you have the "Constrain Proportions" box checked, you may not be able to tweak these individually without affecting the other. So uncheck that box and change the size settings. Click ok to close the box and the image will re-size within Photoshop.
4. After you have finished creating your custom image, flattening the image, and resizing it to fit on your phone's screen, it is time to save the file. Navigate to the "file" menu and click "save as". Here, you can choose where to save it, name it, and choose the file format. It's probably easier to go ahead and save it as "splash" now, so that you wont have to rename it later. Either way, this file MUST be named "splash" when we are in the final stages. Save it as the "BMP" format, and you will get a pop-up window for the BMP options. "File Format" should be set to Windows... and choose the depth option of 24 Bit. The "compress" and "Flip row order" boxes should be unchecked, and you do not need to go into any advanced settings. Once you have saved the file, You can close PhotoShop.
Now the File needs to be converted from the BMP format into an IMG file. This is so that the boot loader in your phone will see it when you flash it to your phone.
There are a few conversion tools out there, but I have found Splash Screen Creator to be the EASIEST way to convert the file with a few clicks.
The link to download this small program is here... http://www.addictivetips.com/?attachment_id=43073 ... and it is FREE!!! (I did not create this program)
1. Download the .zip package from the link above.
2. Extract the files. I found that creating a folder on my desktop to secure these files (and these files only) to be less of a headache.
3. After you have extracted the files, you are ready to convert your "splash.bmp" file. You MUST move this file into the same directory that you unzipped the Splash Screen Creator to. It will only find the bmp file in the same directory, which is why having its own folder is easier. Move your "splash.bmp" file to the same folder and open "RUN THIS ONE". This will open the program in a command prompt.
4. Choose option 1 to convert your existing .bmp file into the required .img file. The next option will ask if you would like to flash the file to your phone. This option is not necessary for these instructions, but I have read of others being successful. You can try this option, but if it fails, go on to the remaining steps.
5. Go ahead and close the program by pressing another key to exit. You should see your new "Splash.img" file in this same directory. Rename this as "splash1.img"
Now that I think of it, naming the BMP file to "splash1" prior to converting to the .img format may solve the error when trying to flash the file to the phone
within Splash Screen Creator. The img file MUST be name "splash1" prior to updating it in the boot loader in the next steps so it makes sense that the program would come up with an error at this point. I have not tested this theory at this time, but you are welcome to. If someone does test this, please update these instructions
to save from many unnecessary steps below!
Your next steps require access to your original "PC36IMG.zip" file that you used during your root process. If you do not have your original "PC36IMG.zip" file, you
can try to download one here... http://forum.xda-developers.com/showpost.php?p=8913849&postcount=156 ... I have not tested this file yet, but worth a shot if you dont have it.
1. Make a COPY of your "PC36IMG.zip" file and move it to your directory where you have worked with the custom splash files. This saves from getting confused between files and flashing the wrong one to your phone. You're also making a copy so that your original "PC36IMG.zip" file is NOT altered.
2. DO NOT unzip the file! Simply drag your "splash1.img" file over to your zipped "PC36IMG.zip" folder and copy it in there. If you get a prompt to overwrite an existing "splash" file, go ahead. Afterall, you are working with a copy of the PC36IMG.zip.
3. After you have added the "splash1.img" file into the "PC36IMG.zip" folder, you can now move the zipped folder over to your sd card. Make sure that it is the ONLY copy on your sd card, and that you have not placed it in any other directories. BOOT LOADER WILL NOT FIND IT IF IT IS IN ANOTHER FOLDER!!!
4. AT THIS POINT YOU WANT TO BE SURE YOU HAVE BACKED UP YOUR ROM!!!! YOU WILL LOSE YOUR CURRENT ROM AND DATA AFTER THE NEXT STEP!!!!
5. Reboot the phone into Boot loader by holding the volume down button and pressing power. The boot loader will find your "PC36IMG.zip" and ask you if you want to update. Press the volume up button to say YES! Grab a coffee, chug a beer, or take a piss, cause this step takes a few minutes.
6. Once the boot loader has finished it's update, reboot your phone. it will now display your new custom splash screen!!! (but you're not done yet)
Because you updated your "PC36IMG.zip" files in the boot loader, you have in effect re-flashed the stock rom (rooted of course) back to your phone.
Allow a few minutes for your phone to boot up, log into your g-mail account (so that you have access to the market), and download Rom Manager (or your favorite backup manager), and restore back to your rom!
Like I said before, I have only done this on the HTC EVO that has been rooted using UnrEVOked through the process explained on HTCEVOHacks.com. I have no idea if this process will work with other configurations, and I accept no responsibility for the outcome of your actions!!!!
cool bro thanks
Thanks very helpful
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