• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Incredible Boot Animation

If you are having problems follow this by the letter.
I did and It works......




Okay, the original instructions are great... provided you aren't a noob. I had to find a lot of stuff out on my own... so please amend the original instructions with these noob friendly additions.

First, you need the Android SDK. You can find that here: Android SDK | Android Developers

Extract the folder and run Setup. It will ask you to download files, do so.



Place this bootanimation.zip into the tools folder of the SDK. You can find the tools folder inside of the android_sdk_windows folder you extracted when you downloaded the SDK.

Connect your phone to your computer with USB. Mount your phone by clicking on the USB message in the notification bar. You will then need to run Debugging mode by going on your phone to: Settings > Applications > Development > USB Debugging. Make sure this is checked; you should get an exclamation mark icon in your notification bar.

Once you are connected, mounted, and in debugging mode, go to on your computer: Start > Run. Type in "cmd" and hit Ok. This will open command prompt.

You need to navigate to the android_sdk_folder from command prompt. If the folder is in your C drive and the letter next to your cursor is different, simply type: "c:" and it will switch to the correct drive. If you are on an XP machine and the folder is on your desktop, you will need to navigate to the tools folder by typing:

cd c:\Documents and Settings\user\Desktop\android-sdk-windows\tools

...where "user" is your login name. THIS IS NOT ALWAYS THE ADDRESS, you can see the full path at the top of the open tools folder. The "cd" before the directory path is necessary--it tells the command prompt to "change directory".

If you have correctly typed in the exact directory your tools folder is in, you should see the entire directory path displayed to the left of your cursor on the new line. Now, you need to push the bootanimation.zip folder to your phone by entering in this line of text:
adb push bootanimation.zip /data/local

Once you hit enter, a second should go by and you should see that a certain amount of data was added to the phone. When you see this, turn off your phone and reboot. You should now see the new animation! You may need to unplug your USB cable before you turn the power back on. In debugging mode, it may display weird menu text when you boot up if you are still connected to the PC.

I hope this helps, I know I was in the same boat as a lot of you, I had to scrounge around to find all this info, don't know why it's not all in one place.

you're the man!!!!!

Now I need sound! LOL
 
*disregard* root explorer needs a rooted ROM before it will allow mounting r/w...
*will this work?* EDIT: nope


delete post
 
I know maybe I'm slow, but can someone do a DIY with Youtube, or step by step for Mac?

(maybe I missed it, if so, very sorry for wasting time)
 
Alright guys, just had the same issue with no response to "adb devices"...did you try to reboot your PC?

Worked for me.

Also, once that's fixed, note there's a space after adb push bootanimation.zip

Bingo!! Uhh, THANK YOU Maverick. I went to bed last night after my last post earlier and woke up this morning hoping there would be someone who could help me :)
I have a laptop that I always leave on, so I did the re-boot and then re-attached the DI to the computer and issued the 'adb devices' command and it finally showed something! Yea!

Maverick/Bryn/Civic/Macdaddy - THANK YOU all of you for helping me. I'm sure your posts will help others here that have/will have the same problems I did.
 
So, one last post about this boot animation :) hahaha...

I haven't done the last 'adb' command to move the bootanimation over because I have two questions first that I hope someone can help with:

1: Once I do the bootanimation command, can I ever get to back the original VZW boot screen IF I wanted to? Is it just as easy as deleting the bootanimation.zip file from the /data/local folder on the DI drive? I assume the bootanimation.zip is "overriding" the stock VZW bootup?

2: If I want to keep playing around and experimenting with different users bootanimation.zip files, is it just as easy now to delete the current one in the /data/local folder and re-issuing the 'adb push bootanimation.zip' command over and over?

Thanks again!
 
YES and YES..

All you have to do is remove bootanimation.zip out of tools folder, put in new one

and re-do

same with audio
 
also should i do this, seeing it did copy files over but did't change anying ?

Reverting back to default boot animation

1.) Open an ADB Shell using:
Code:
adb shell
2.) Remove bootanimation.zip from /data/local using:
Code:
rm /data/local/bootanimation.zip
3.) On next boot you'll have the red VZW animation back.


Here ya go
 
Yes this is the one that I used

and I dont know where it says Android on the animation... ???

Weird, maybe I downloaded a different one, but I got the one with the smaller eye and set up with his sound. Tight work! Thanks for the reply!
 
I was bored, so I modified the "Retro Boot Animation" (XDA) to fit the Incredible.

I'm assuming it'll work, but I'll test it out in a minute.

Download: bootanimation.zip

retroincredible.gif


Bleh, didn't work. Guess I'll figure this out later.

Fixed.

Just put this on mine, shit looks GREAT. Thanks a lot.
 
I have USB debugging enabled on my DI

I have latest SDK and I have updated repository as well as followed with a restart of my PC.

My DI was plugged in with usb debugging enabled and I have moved my bootanimation.zip to the "android-sdk-windows\tools" directory

PROBLEM?

I ran the command C:\Documents and Settings\DUBUCC\Desktop\sdk\android-sdk-windows\tools> adb push bootanimation.zip \data\local
*daemon not running. starting it now *
*daemon started successfully *
error: device not found

^^^^what does this mean? did I do something wrong?
 
seems like it didn't find the device..

to tell it worked it will put the size of the file that was uploaded.

I heard a reboot of the PC helps..

that would i would do to see
 
seems like it didn't find the device..

to tell it worked it will put the size of the file that was uploaded.

I heard a reboot of the PC helps..

that would i would do to see


i did reboot after installing sdk- would another reboot help?

android-sdk-windows\tools> adb push bootanimation.zip \data\local now seems to only give the "error: device not found"

hmmm stumped

size of bootanimation.zip is 1,732kb
 
hmmm no same as before:

C:\Documents and Settings\DUBUCC\Desktop\sdk\android-sdk-windows\tools> adb push bootanimation.zip \data\local
*daemon not running. starting it now *
*daemon started successfully *
error: device not found

what else can I try? I've restarted my pc and my device multiple times...

*edit* ok so you guys are telling me its not seeing my device- and yet if I switch from charging to mount sdcard i get my removable hard drives coming up on my desktop...

should I select HTC sync? I assume thats only for contacts...

I guess what I'm trying to say is that my PC is recognizing the damn DI...
 
I have USB debugging enabled on my DI

I have latest SDK and I have updated repository as well as followed with a restart of my PC.

My DI was plugged in with usb debugging enabled and I have moved my bootanimation.zip to the "android-sdk-windows\tools" directory

PROBLEM?

I ran the command C:\Documents and Settings\DUBUCC\Desktop\sdk\android-sdk-windows\tools> adb push bootanimation.zip \data\local
*daemon not running. starting it now *
*daemon started successfully *
error: device not found

^^^^what does this mean? did I do something wrong?


is the sdk folder inside of another folder called sdk?


c:\documents and settings\dubucc\desktop\android-sdk-windows\tools

then try

adb push bootanimation.zip \data\local


from my little expericence, if you try to put a folder inside of a folder and then try to make something work it doesent work, idk, give it a try, maybe it will solve your problem
 
Here's a couple things I found that I didn't know until playing around or the nice help on here:

1: Make sure when you connect your DI to your computer via USB, the DI isn't only doing a 'Charge Only' connection. A couple times un-plugging and then plugging back in, I always had to make sure to click the 'Disk Drive' connection type on my phone.
If not, yea your F: drive will come up, but you/ADB cannot access it.

2: After you install the SDK, download your bootanimation.zip file and modify the USB .inf file for the Incredible, reboot your computer. It took me like an hour last night until someone posted to reboot and then issuing 'adb devices' showed me my phone! Weird....
Because I leave my computer on 24/7, I rarely reboot or didn't even think I needed to!

Got mine working this morning like Wayne's.. Love it!
 
Here's a couple things I found that I didn't know until playing around or the nice help on here:

1: Make sure when you connect your DI to your computer via USB, the DI isn't only doing a 'Charge Only' connection. A couple times un-plugging and then plugging back in, I always had to make sure to click the 'Disk Drive' connection type on my phone.
If not, yea your F: drive will come up, but you/ADB cannot access it.

2: After you install the SDK, download your bootanimation.zip file and modify the USB .inf file for the Incredible, reboot your computer. It took me like an hour last night until someone posted to reboot and then issuing 'adb devices' showed me my phone! Weird....
Because I leave my computer on 24/7, I rarely reboot or didn't even think I needed to!

Got mine working this morning like Wayne's.. Love it!

I have installed the sdk, updated repository, modified my usb.inf, rebooted...

so wait, what you are saying is, 'while my phone is plugged in, the phone should have the sdcard mounted and NOT on the "charge only" option' ? is that correct?

***EDIT****

I don't really know what I did different, all of a sudden the command worked and I got the file size at the end of the prompt... I guess that means I'm golden, I'm going to reset my phone, see if it comes up, *crosses fingers*
 
Back
Top Bottom