Database Users

Captivate Boot Animations and Sounds

Wanted to get rid of the stock startup animation and sounds here is how I did it.
/system/etc/PowerOn.wav
/system/media/bootsamsung.qmg
/system/media/bootsamsungloop.qmg
I renamed those 3 files and thats all it took, killed the two boot animations and sounds. So now I get the Initial white AT&T screen a long black period followed by the lock screen.
Now if someone would decipher how to manipulate these QMG files. It looks like others have found a way around them possibly ( http://forum.sdx-developers.com/themes/bootanimation-zip-(testers-needed)/ ), not too sure.

Anyone have the stock startup and shutdown animations from the Galaxy S? I want to de-brand this as much as I can.

More data from inside the /system/bin/bootanimation2nd
debug.sf.nobootanimation 0 BootAnimation boot animation disabled %0 80 /data/local/bootanimation.zip /system/media/bootanimation.zip desc.txt descMap is null %d %d %d p %d %d %s images/android-logo-mask.png images/android-logo-shine.png SurfaceFlinger died, exiting... linkToComposerDeath failed (%s)
So it looks like we have some tinkering to do.

ok if you take the bootanimation zip files from the other forum and place them in /system/media and chmod to 644 and chown to root you can launch the bootanimation file in /system/bin remotely with adb and the animation shows on the screen of the phone. So we are on the right path. Rebooting the phone does not cause the animation to play however. Anyone who wants to lend a hand is welcome!

LOCATIONS OF SOUNDS AND ANIMATIONS
Startup sound;
/system/etc/PowerOn.wav
Startup animation;
/system/media/bootsamsung.qmg
/system/media/bootsamsungloop.qmg
/system/bin/bootanimation
/system/bin/bootaniamtion2nd
Shutdown sound;
/system/media/audio/ui/shutdown.ogg
Shutdown video (directory of .pngs);
/system/media/shutdown/
THIS IS WHAT I FOUND ON ANOTHER SIGHT
You can just delete all other files and folder so you only have fx if your bootscreen is placed like this: META-INF and system system> customize> resource>bootanimation.zip
That should be your only files and folders. Of course if you your bootscreen is placed in data/local/bootanimation.zip then that should be your only directories and files
THIS IS HOW I DID IT WHEN I HAD AN ARIA( not sure but seems like it should be same?)
1. Copy the NEW bootanimation.zip of your choice in SDK Folder
2. Open up CMD
3. cd C:\AndroidSDK\tools (or were ever you SDK files are)
4. adb remount
The filesystem is mounted read only. You need to mount it read/write.
5. adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
6. adb push bootanimation.zip /system/media/bootanimation.zip
7. adb push bootanimation.zip /data/local/bootanimation.zip
To return to read only,
8. adb shell mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
9. Reboot and there you go
HOPE this helps

I've renamed some of the files to see if they do anything also executed a few of the BINs.
/system/bin/bootanimation -- Displays "ANDROID" with a shine going across the text. This animation is not seen at any point during boot, renaming the file did nothing.
/system/bin/bootaniamtion2nd -- Displays "ANDROID" in plain android font. This animation is not seen at any point during boot, renaming the file did nothing.
/system/bin/playlogo -- Executing this file (atleast via the adb shell, although it does output "=============> 1" the exits after a few seconds.) did not appear to do anything. Renaming this file did not appear to change anything in the boot process.
/system/bin/playlogos1 -- Executing this file via the adbshell caused the 2 boot videos (not the "AT&T World Phone" BIOS splash image, just the ATT bars with fire balls and the galaxy S animated logo) to play. This cause similar out put to playlogo in the adb shell, except it counted to 5 and never exited. A Ctrl+C in DOS forces the adb shell to quit which causes the bin file to halt execution also.
I'm going to try and open the playlogos1 file and/or try to find a qmg player, we may just have to replace the qmg files to MOD the boot animation.

Some relevant source ( http://github.com/Dieken/SurfaceFli...rks/base/cmds/bootanimation/BootAnimation.cpp ). Its starting to look like the qmg files are raw frame buffer information.

I went through the playlogo and playlogos1 bin files again with bvi (linux app for viewing binary files) one of the legible sections before the part that points to the *.qmg file loads a decoder. The qmg files appear to be Qmage files.
See quramsoft.com/solution_e/qmage.asp
sorry cant post links yet.

kenjindomini said:
I went through the playlogo and playlogos1 bin files again with bvi (linux app for viewing binary files) one of the legible sections before the part that points to the *.qmg file loads a decoder. The qmg files appear to be Qmage files.
See quramsoft.com/solution_e/qmage.asp
sorry cant post links yet.
Click to expand...
Click to collapse
You may have nailed it on the head which is a good find, but unfortunately it looks like we will never be able to edit one of these.

So I take it no one has yet attempted to use a bootanimation.zip like on the Samsung moment http://forum.sdx-developers.com/themes/(how-to)-bootanimation-zip/
I might give this a try later today:
Rename playlogos1 -> playlogos1.orig
find sexy bootanimation.zip on the interwebs and load it into /system/media
I'll report back with my findings, even if they're depressing.

kenjindomini said:
So I take it no one has yet attempted to use a bootanimation.zip like on the Samsung moment http://forum.sdx-developers.com/themes/(how-to)-bootanimation-zip/
I might give this a try later today:
Rename playlogos1 -> playlogos1.orig
find sexy bootanimation.zip on the interwebs and load it into /system/media
I'll report back with my findings, even if they're depressing.
Click to expand...
Click to collapse
Yes I have tried several, and while you can launch them manually they do not trigger on reboot.

Yeah
I even tried to chmod the file in both data/local and system/media to mode 777 and still just a black screen.
Looks like we are waiting for a hacked kernel.
Sent from my SAMSUNG-SGH-I897 using XDA App

kenjindomini said:
Yeah
I even tried to chmod the file in both data/local and system/media to mode 777 and still just a black screen.
Looks like we are waiting for a hacked kernel.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
In the meantime I am looking to see exactly how/where these are being called in the boot process.

Ok since things just didnt seem to be working here is what I did. I renamed the playlogo and playlogos1 file and replaced them respectively with renamed copies of
/system/bin/bootanimation
/system/bin/bootaniamtion2nd
then put a bootanimation.zip in both /system/media and /data/local then when I rebooted I get the plain white at&t screen. followed by a short black screen, and then the bootanimation.zip.
So this works it just has a 7 second or so black screen.

Ok, something weird is happening. I'm trying to rename /system/etc/PowerOn.wav to PowerOn.wav.bak because I have downloaded the Bootsamsung.qmg, Bootsamsungloop.qmg and PowerOn.wav from the I-9000 but every time I rename /system/etc/PowerOn.wav to *.bak using root explorer it says its renamed successfully but then if I do a view refresh, its right back to how it was originally. Same thing if I just go and try to outright delete it, it looks like its deleted until I do a view refresh then its right back there. Like I cant get rid of it at all. Anybody know whats going on??
On another note I copied the Bootsamsung.qmg and bootsamsungloop.qmg from the I-9000 to the folder /system/media and just let it overwrite the orignals. Now the flying att 3G antenna stuff is gone. It goes from the white world phone screen to a black screen then to the Galaxy S animation. But its still playing that super loud whoosh sound because I cant get rid of the original PowerOn.wav file to save my life.
The PowerOn.wav from the I-9000 is 5 seconds long, its the same as the AT&T one except it doesnt have the first two seconds that contains the really loud and annoying "Whoooosh".

I had this problem at first. Make sure you are mounted r/w. If that doesnt work move the file out of the folder. I seem to recall that one file was a pita for me too.
If you get it working let us know!

rahlquist said:
I had this problem at first. Make sure you are mounted r/w. If that doesnt work move the file out of the folder. I seem to recall that one file was a pita for me too.
If you get it working let us know!
Click to expand...
Click to collapse
HaHa, that worked great. Thanks.
I was mounted as r/w in root explorer. I tried renaming and deleting dozens of times with no success, never really thought about move. It let me move it right out of /system/etc. Then I was able to copy in the new PowerOn.wav from my sdcard. Then I could rename the original to PowerOn.wav.bak, then move it back to /system/etc just in case for the future. So now I dont hear that really loud and annoying "whoosh".

Is the /video/shutdown folder with the 60 frames of .pngs the same as the startup animation perhaps played backwards? I'm thinking of making my own custom animation and replacing those files to see how it looks.

rahlquist said:
In the meantime I am looking to see exactly how/where these are being called in the boot process.
Click to expand...
Click to collapse
If you look in the init.rc there is BOOTCLASSPATH line and it lists framework files, they are compiled java code (*.JAR) one of these files or a modified version of the android kernel would be responsible for executing the playlogos1 bin file. playlogos1 is the only file on the of the 4 in that directory that we have talked about that does anything during boot on the captivate. playlogo seems to be remnant from the older samsung androids (E.G the moment). The 2 bootanimation bin files just display the word android in green android style font 1 with a shine and 1 plain.
I've looked through almost every system file and I can think of, there is no reference to the playlogs1 file that can be viewed in plain text. It would be the very first thing to be called soon as linux begins to load. The ATT world phone splash image I would assume, just like on a pc, hides the BIOS/POST output and the boot animation is hiding all of the linux init output. though it does sadden me that renaming the files the play the boot animation does not cause all the boot text to display.
Darkeligos said:
Is the /video/shutdown folder with the 60 frames of .pngs the same as the startup animation perhaps played backwards? I'm thinking of making my own custom animation and replacing those files to see how it looks.
Click to expand...
Click to collapse
This is not the case. the playlogos1 bin file, the file responsible for launching the boot animation, loads a QMAGE decoder before loading the 2 *.QMG files. If look back to my previous post on the first page there is a link to the developer of QMAGE and its a compressed library of images that get decompressed on-the-fly.
@the guy with the I9000 boot animations and audio, Dude where did you get those? i9000 forum? link us? Attach here? Please?

kenjindomini said:
@the guy with the I9000 boot animations and audio, Dude where did you get those? i9000 forum? link us? Attach here? Please?
Click to expand...
Click to collapse
Yes, this needs to be mandatory - if you've got something good working that gets rid of the AT&T JUNK sounds and animation, then you gotta attach them on this thread and tell us the steps you took to get it going! Thanks in advance!

[Q] Droid 2 Boot Animation

Hello everyone,
I have recently been messing around with my droid 2 and was able to change the boot screen successfully by doing the following commands:
PHP:
adb push bootanimation.zip system/media/
After running this command I had the new animation and that works great. My question is if anyone know how to incorporate a boot up sound with this. I have tried creating a bootscreen folder and having the boot_animation.xml in both the system/media path and the system/media/bootscreen path, however to no success. It is to be noted that when I removed the bootanimation.zip from the system/media folder, it defaults to the original blue android loading animation as if it were not seeing a bootscreen folder.

theecho said:
Hello everyone,
I have recently been messing around with my droid 2 and was able to change the boot screen successfully by doing the following commands:
PHP:
adb push bootanimation.zip system/media/
After running this command I had the new animation and that works great. My question is if anyone know how to incorporate a boot up sound with this. I have tried creating a bootscreen folder and having the boot_animation.xml in both the system/media path and the system/media/bootscreen path, however to no success. It is to be noted that when I removed the bootanimation.zip from the system/media folder, it defaults to the original blue android loading animation as if it were not seeing a bootscreen folder.
Click to expand...
Click to collapse
What is the boot animation that you used and is is just as simple as removing the boot animation that is in the system media file and replacing it with another boot animation like what was done with the D1?

Yes it was pretty simple just do the following
PHP:
adb pull system/media/bootanimation.zip
This will pull you current boot animation. Move it somewhere to keep as a backup.
PHP:
adb push bootanimation.zip system/media/
This is assuming bootanimation.zip is located in you android sdk's tools folder. You can use any of the bootanimations that are an assortment of pngs.
Sent from my DROID2 using XDA App

I wonder what would happen if you had one in data/local

bump*
Anyone have any further info on this? I would really like a startup sound again.

theecho said:
Yes it was pretty simple just do the following
PHP:
adb pull system/media/bootanimation.zip
This will pull you current boot animation. Move it somewhere to keep as a backup.
PHP:
adb push bootanimation.zip system/media/
This is assuming bootanimation.zip is located in you android sdk's tools folder. You can use any of the bootanimations that are an assortment of pngs.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Ok if the boot animation is on the system media file like the D1 why cant we just take a boot animation and delete it out of the system media and replace it with a new one? Do you have to ADB push it?

The boot animation is kept in the system/media folder. If you can replace this by another means, it will work. I chose to use adb push as I was already in my command line due to an application i was writing.

help
hey guys, sorry for the noob question, but what r u guys using to zip your finnished product? (not a flashable zip) just the zip u can push or use root expor to just place in correct spot. i know you cant use anycompression, but ive tryed everything and i must be doing something wrong. to make sure my zip methods are not adding any compression, i pulled my orig bootanimation, which zipped is 6114kb, i unzipped, then rezipped, and i keep getting dif sized zip files.. if done right it should be the exact same size right?
using the following this is what i get
ok oring is 6114kb, heres what the others do, 7zip 6124kb(bigger) PC zip client 6086kb and winrar is the closest at 6119kb
any advice would be greatly apr

Does doing ADB push require you to plug the phone into the computer in PC mode?
Also, can you change boot animations on stock ROM, or only on custom ROM?
I downloaded a bootanimation.zip file that's 480x854 pixels, the same as the D2's screen. I also looked at the default bootanimation.zip file, which is 480x480. Does the resolution matter at all, or can the phone display it either way?
Tappin' and Talkin' with Tapatalk

theecho said:
Yes it was pretty simple just do the following
PHP:
adb pull system/media/bootanimation.zip
This will pull you current boot animation. Move it somewhere to keep as a backup.
PHP:
adb push bootanimation.zip system/media/
This is assuming bootanimation.zip is located in you android sdk's tools folder. You can use any of the bootanimations that are an assortment of pngs.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
No need, you can download Super Manager from Market, using file manager function and get root access to copy directly.
Have fun.

Since this is bumped anyway, for whatever reason sounds will not work on boot with the default Rom. MIUI and other Roms are necessary for this mod.

[TUT]Revive your(original) framework-res.apk when boot looping caused by modding

Hi all,
i often noticed people(including me) who tried to modificate their framework-res.apk resulting in boot loops(e.g. looping at white/green quietly brilliant screen).
So i tried to find out a fast way to get back to my(original) framework-res.apk without usage of recovery console each time my framwork-res.apk did not work as expected.
How it could help you:
It's a fast way to:
check out your moddings when doing numerous modifications in different versions of your modded framework-res.apk on your way to get it to work.
if you want to get back to your original/working framework-res.apk, even when it boot loops!
Click to expand...
Click to collapse
When you do numerous modifications on framework-res.apk and your modded apk leads to a boot loop you will be able to replace the current apk through e.g. the original apk.
At this boot point(boot loop screen) Android nearly finished booting and you have access on ADB commands.
What do you need to do this:
Download and extract/install QtADB from the link below:
QtADB
to replace the erroneous(current) framework-res.apk by the original or a fixed one.
Click to expand...
Click to collapse
There's no need to describe how to get a copy of your untouched framework-res.apk from device, since there are numerous tutorials around here.
Please check this tutorials to get a copy of your apk.
Please note before beating your device:
this probably will work with the most visual moddings of framework-res.apk - but i can't guarantee it works 100%.
It probably will not work when you play around with hardware or connections setting, other apk's or other stuff in other folders, so i am not responsible if it does not work.
always backup your current ROM/settings/whatever and save a copy of your untouched framework-res.apk
There is a little catch in it in comparsion with using recovery:
After you did like described, you have to set your background image and your (google) accounts anew.
But this is just a little work and it's not necessary until your framework-res.apk is doing the modded stuff correctly - or if you want to set the original framework-res.apk back.
Click to expand...
Click to collapse
So let's start to revive your original framework-res.apk.
(Of course you can use this method to push a modded to your device, to check out if your modding works):
Boot your device and let it load until you're at boot loop
(Download, extract,) run QtADB
Navigate in left window(Computer) to your copy of original framework-res.apk(e.g. in root directory of SD card, but i recommend a folder on your computer)
Navigate in right window(Phone) to device folder /system/framework/
Use in left window(Computer) context menu on your original framework-res.apk and select copy or drag&drop it to right window to copy the original framework-res.apk to your device
(just ignore that your device is doing strange stuff then, since it cannot access your framework-res.apk correctly at this point)
Then enter shell of QtADB(at left toolbar of QtADB) and enter the following commands to set the apk's prermissions:su
cd /system/framework/
chmod 777 framework-res.apk​
Reboot your device( e.g. by using top menu->tools-ADB->reboot)
Set your background image and your (google/HtcSense) accounts anew.
Hope it helps you a bit on modding,
Greetings, brush2(Stephan)

error
hey man, Im getting an error on this. I changed my transitions effects ( folder anim on framework-res.apk) using the app metamorph. well, now every time I open an app the phone ( xt920) reboot. I ask my friend that have the same phone to send me his framework-res.apk. I try to replace using this method but dont got. I draged and droped the new apk and when I would type the shell's code the last code dont work because it said that the file is a "read-only system". What can I do to have my phone back? Please help.
Thanks.

[Q] Sprint power-up 4g intro thingy... removal?

Ok, you know the 4G Sprint video you get when booting up, right before you actually get into the OS?
Is there anyway to get rid of that? It annoys me.
Can I replace it with a different animation?

James.Q.Campbell said:
Ok, you know the 4G Sprint video you get when booting up, right before you actually get into the OS?
Is there anyway to get rid of that? It annoys me.
Can I replace it with a different animation?
Click to expand...
Click to collapse
Probably check it out, it'll be somewhere in system/media. You have to be rooted of course
Sent from a truly Epic phone and a transparent XDA app

yeah ive been wondering if i can put my R2-D2 boot ani on here lol

I know we can replace it, but it does not seem to be in system/media. There are a few images in system/media/GPU, but it is not the entire boot animation. I did some brief searching, but am not finding it.

I'm pretty sure you'll find it in /system/customize/resource along with an mp3 that provides the boot sound.

cloverdale said:
I know we can replace it, but it does not seem to be in system/media. There are a few images in system/media/GPU, but it is not the entire boot animation. I did some brief searching, but am not finding it.
Click to expand...
Click to collapse
Yeah, I did the same thing. Searching around did give me the opportunity to scrap most of those annoying ringtones I never use though.
I searched around a bit more but didn't find anything. I did find a bootanimation.zip in data/local and replaced it with a boot animation I have, but it didn't change anything.

Lmao guys.
Code:
adb push bootanimation.zip /system/customize/resource
And your set
Sent from my PG06100 using XDA App

smp420 said:
I'm pretty sure you'll find it in /system/customize/resource along with an mp3 that provides the boot sound.
Click to expand...
Click to collapse
Ah, ok. Playing with it now. Will report back in a few.

James.Q.Campbell said:
Ah, ok. Playing with it now. Will report back in a few.
Click to expand...
Click to collapse
Ok, nevermind... I can't delete the stupid stock file.
Do I need ADB for this? I'm not familiar enough with ADB to know how to use it to delete the file and push the new one in.
Anyone with more experience with ADB want to lend a hand here?

bubby323 said:
Lmao guys.
Code:
adb push bootanimation.zip /system/customize/resource
And your set
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Well, that'll learn me to read back on the thread first.
Hey, I'm a noob. I'm learning.
Leave me alone...

bubby323 said:
Lmao guys.
Code:
adb push bootanimation.zip /system/customize/resource
And your set
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
adb push doesn't work (at least for me) have to figure out another way
however your location is correct.

Not 100% on this but if you adb while in recovery it may work. /system is mounted while the phone is running so you may be running into permission errors. Although I was able to adb pull mine while running.
Edit: not sure if it's just me but when I tried I get an error about the system being read only and apparently the busybox I have doesn't have a remount command.
Edit2: found the full remount command but it seems that the phone doesn't care for it much. Was able to push a new ani but got acore force closes on reboot the were not fixed by putting back the original (I didn't really expect them to be)
Edit3: Finally got it working. You just have to be in recovery with /system mounted. I should have tried that much earlier but I seem to like to try all the wrong steps first Any 480x800 animation should work. wouldn't suggest using the flashable zips since they probly copy to the wrong location. Have fun.

I built my own flashable zip using the old template from my Moment days...just had to edit the cleaner.sh and the update-script in the 'META-INF\com\google\android' folder of the zip file.
cleaner.sh contents:
#!/system/bin/sh
rm -rf /system/customize/resource/bootanimation.zip
rm -rf /data/local/bootanimation.zip
update-script contents:
show_progress 0.1 0
run_program PACKAGE:cleaner.sh
copy_dir PACKAGE:system SYSTEM:
set_perm 0 0 0644 SYSTEM:customize/resource/bootanimation.zip
show_progress 0.2 10
You also need to change the folder structure inside the flashable zip to 'system/customize/resource' for the location of the bootanimation.zip file.
I also included a new mp3 file in same folder as bootanimation and renamed it to 'VERSION11SAMELENGTH.mp3'.
Edit: Some things I noticed:
- need to resize the images and update that size in the 'desc.txt' file
- the animation plays faster even at the same frame rate than it did
on my old phone, so you may need to lower that
- the mp3 file is pretty loud so you may want to lower its volume
before including it in the zip...it also seems to be tied in some
manner to what the media volume (I think) is set to when the phone
is shut off/rebooted
Edit 2: If anyone sees any errors in my method, by all means speak up...I am mostly just winging this (with a recovery backup in case something goes wrong)

Stock ROM's bootanimation...

I have a special request. Is there a way to retain the bootanimation of the NookColor's 1.2 Stock ROM? Or at least can someone create a bootanimation.zip that has the Stock ROM's boot animation? I can provide you an original nandroid of the STOCK ROM if it's needed. I hope someone can do this.

Here... extract this zip file, remount /system/ rw and adb the bootanimation (NOT the zip) to /system/bin/ and you will have B&N's 1.2 stock animation.

DizzyDen said:
Here... extract this zip file, remount /system/ rw and adb the bootanimation (NOT the zip) to /system/bin/ and you will have B&N's 1.2 stock animation.
Click to expand...
Click to collapse
This. Is. Wicked. Thanks a lot!
UPDATE:
erm... it didn't work for me. Once I placed the content of the zip (bootanimation), in the system/bin it just gave me a blank screen then it went straight to my homescreen. What am I doing wrong? well maybe because I placed the file manually using root explorer. can you tell me how to do it using adb in windows and adb wireless on the nook? what commands should I put on the adb?
UPDATE 2:
I was able to push the file using adb. It still didn't work for me. Maybe we're missing some files? I remember when I'm putting custom bootanimations, I also place a bootanimation.zip in the /system/media directory of the nook...

les02jen17 said:
This. Is. Wicked. Thanks a lot!
UPDATE:
erm... it didn't work for me. Once I placed the content of the zip (bootanimation), in the system/bin it just gave me a blank screen then it went straight to my homescreen. What am I doing wrong? well maybe because I placed the file manually using root explorer. can you tell me how to do it using adb in windows and adb wireless on the nook? what commands should I put on the adb?
UPDATE 2:
I was able to push the file using adb. It still didn't work for me. Maybe we're missing some files? I remember when I'm putting custom bootanimations, I also place a bootanimation.zip in the /system/media directory of the nook...
Click to expand...
Click to collapse
I know most had a zip in /system/media.... but the stock 1.2 didn't have anything related.... looking through the file I posted, it references some .png files that also are not present... I assumed they were contained as data in the file itself... I will look some more and get this setup for you... Sorry for shorting the research on this one.

Maybe the way Root Tools works will show the way.
Similar discussion here.

I hope we can have an update on this one soon... :'(

les02jen17 said:
I hope we can have an update on this one soon... :'(
Click to expand...
Click to collapse
We will... sorry got busy with some stuff on the IMEI Generator... will track it down for you.

Is there some reason this needs to be done? Deviating from the CM7 code is bound to cause issues....

patruns said:
Is there some reason this needs to be done? Deviating from the CM7 code is bound to cause issues....
Click to expand...
Click to collapse
Just thought it would be cool to retain the stock bootanimation, that's all. The device is still a NookColor after all, even after installing a CyanogenMod ROM in it. It would be nice if the device would say 'NookColor' when it boots. Just my opinion, though.
Sent from my NookColor using Tapatalk

It needs to be in the correct format. If you can break it down, it will work:
http://nookdevs.com/NookColor_Boot_Animation_editing_and_replacement
So maybe play it in the SDK, and record the screen?
EDIT: Or try pushing it to data/local
Also, read through this: http://forum.xda-developers.com/showthread.php?t=863439

When all hope seems lost...
When I thought that all hope seems lost on my desire to get the NC's stock bootanimation, in my NC running cyanogenmod, I came across this amazing stock-that-has-been-rooted bootanimation in YouTube... I think it's fate. LOL.
Pretty neat stuff, courtesy of Suteru. On the YouTube page is a link to the bootanimation.zip
Yup, I installed the bootanimation and it's wicked cool. (^_^)

les02jen17 said:
Just thought it would be cool to retain the stock bootanimation, that's all. The device is still a NookColor after all, even after installing a CyanogenMod ROM in it. It would be nice if the device would say 'NookColor' when it boots. Just my opinion, though.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Put the bootanimation.zip file in the /data/local folder. It will override the bootanimation in the system/bin as long as it's there. If you delete it, the stock animation in /system/bin will show. FWIW, I like this animation from NookDevs which is a variation on the stock animation:
http://www.youtube.com/watch?v=apy-ZcdqZFA&feature=related