Database Users

[HOW-TO]--Stock Bootscreen w/ Sound

Well here we go, this will revert your bootscreen to the Stock Verizon Android Bootscreen with Sound.
(Verizon animation then waving droids, followed by the HTC animation)
!!!! THIS IS FOR ROOT USERS ONLY !!!!
This has not been tested with any Non-Root ROM!
This HOW-TO was put together on a Windows Machine, Please adjust your syntax if you are using linux.
This has been tested on the Plain Jane ROM (Thanks Jcase!!) And confirmed working on Ivan's ROM (Thanks pkopalek)
EDIT [6/9/10 @ 3:39pm EST]: THIS WORKS ON Eris-based ROMs ONLY at this time. I will be experimenting with other ROM's and will post my findings.
This Bootscreen was pulled from the Downgrade.zip included in this post:
Android Fourms
Please give credit where credit is due. All i did was get all together and write this HOW-TO.
1. Download this zip ... bootscreen_Stock_Sound
And Extract to any location on you computer. You should have a folder named bootscreen with some xml,mp3,and gif files.
2. if you have pushed a bootscreen to /data/local, delete it.
Code:
adb remount
adb shell rm /data/local/bootanimation.zip
3 Enter the adb shell and cd to /system/media and list contents.
Code:
adb remount
adb shell
cd /system/media
ls
Back up the bootanimation.zip located here.
Code:
cp bootanimation.zip bootanimation.bak
or delete it.
Code:
rm bootanimation.zip
Exit shell
Code:
exit
4. Now to push the animation to /system/media
<your-save-path-here> is where you extracted the RAR. When extracted you will have folder named bootscreen_Stock_Sound with a nested folder named bootscreen.
I downloaded the rar to the desktop on Win 7 so my path would be:
C:\Users\Lostbytes\Desktop\bootscreen_Stock_Sound\bootscreen
NOT: C:\Users\Lostbytes\Desktop\bootscreen_Stock_Sound\bootscreen\
as this will nest the folders.
Code:
adb push <your-save-path-here>\bootscreen /system/media/bootscreen
Wait for it to finish.
EDIT:For those having problems with a black boot screen, please enter the following to set the permissions on the bootscreen folder.
Code:
adb remount
adb shell chmod 775 /system/media/bootscreen
5. To Test.
Code:
adb remount
adb shell
bootanimation
PRESS Ctrl-C to return to the shell.
Now a creative person with the inclination, should be able to modify the contents of the bootscreen xml file to use custom sounds and animations. Have Fun All
TO THE DEVS:
Thank you for all your hard work day in and day out. Without people like you, this scene would not exist.

Have Fun
Have Fun Everyone!!!!!!

I've been thinking about this bootscreen for a long time.
Thank you for this.

And for what it's worth, with all the files in place,
my Evil Eris boot animation is just a blank, black screen.
Hmm..... I'm missing something.

I thought this had to be in a ZIP format...
After downloading ..it is a RAR file...

bukada said:
I thought this had to be in a ZIP format...
After downloading ..it is a RAR file...
Click to expand...
Click to collapse
This is not the common Bootanimation.zip!!!
Please read the directions, this is the old Style bootanimation format. (using a XML instruction sheet, NOT the desc.txt file w/ png in zip format) This allows much more control. You mush first back up or remove any and all Bootanimations on your phone.

pkopalek said:
And for what it's worth, with all the files in place,
my Evil Eris boot animation is just a blank, black screen.
Hmm..... I'm missing something.
Click to expand...
Click to collapse
Did you back up or remove the bootanimation in
/data/local
/system/media
also if /system/media already has a bootscreen folder delete it and replace it with the one from the RAR.
Bootanimation formats as far as i know are:
/data/local/bootanimation.zip
/system/media/booanimation.zip
/system/media/bootscreen/<XML,Gif,MP3 files>/
This bootscreen is the last format. It works on a ERIS running Plain Jane, Will post vid soon.

pkopalek said:
And for what it's worth, with all the files in place,
my Evil Eris boot animation is just a blank, black screen.
Hmm..... I'm missing something.
Click to expand...
Click to collapse
Same here. Followed the instrucations and only have a blank screen now during boot up. Is a step missing?

lostbytes said:
Did you back up or remove the bootanimation in
/data/local
/system/media
also if /system/media already has a bootscreen folder delete it and replace it with the one from the RAR.
Bootanimation formats as far as i know are:
/data/local/bootanimation.zip
/system/media/booanimation.zip
/system/media/bootscreen/<XML,Gif,MP3 files>/
This bootscreen is the last format. It works on a ERIS running Plain Jane, Will post vid soon.
Click to expand...
Click to collapse
All checkpoints check.
This is also pretty standard for all of Android, so I am baffled as to why we're getting black bootscreens!

pkopalek said:
All checkpoints check.
This is also pretty standard for all of Android, so I am baffled as to why we're getting black bootscreens!
Click to expand...
Click to collapse
I will recreate the procedure from the beginning . All i did was pull the original boot screen from Android 1.5 and push to my phone, Maybe i missed documenting something.....But it is a simple operation. Will post again soon.

Yeah, I see.
I even pulled apart downgrade.zip (which I have on my computer) and looked at it myself, just in case a file got corrupted or something.
I can't figure it out!
Maybe this needs to be turned into a bootanimation.zip for some ROMs?

pkopalek said:
Yeah, I see.
I even pulled apart downgrade.zip (which I have on my computer) and looked at it myself, just in case a file got corrupted or something.
I can't figure it out!
Maybe this needs to be turned into a bootanimation.zip for some ROMs?
Click to expand...
Click to collapse
Its possible, I will look into it some more, What baffles me is that works for me!!! It may be ROM dependent but i am just recreating the file structure with no modifications from the original. So, in theory the ROM should not matter.

I tried grabbing the /system/bin/bootanimation file from another ROM (so that the 'bootanimation' command would maybe work?) to see if that makes the difference, but it doesn't seem to.
It seems like something silly is missing! I even did a Root Explorer search for anything with the word 'boot' in it to see what could be causing the trouble, but I don't see anything at all! The only things with 'bootscreen' or words like it is in the /system/media/bootscreen/ folder that is there (because I put it there).
Baffling!

Here are screens of what i did, I recreated the whole process and it worked fine for me. Again i am running the Plain Jane ROM (Thanks to Jcase) if that matters.
link To Screen
Hope this helps!!!

I confirmed this DOES seem to work on normal Eris-based ROMs like yours (Ivan's 1.0, in my case)
but NOT on EvilEris.

pkopalek said:
I confirmed this DOES seem to work on normal Eris-based ROMs like yours (Ivan's 1.0, in my case)
but NOT on EvilEris.
Click to expand...
Click to collapse
Would you like me to post the bootanimation file from /system/bin?
maybe replacing this file with mine might solve the issue...
File located here........... Bootanimation
Please let me know if this resolves the issue. If not i will install EvilEris and try to recreate.

Same exact success rate.
I also had to chmod your 'bootanimation' to make it work, but that may or may not be related to me downloading/pushing it from a Windows machine.
Neither here nor there, just a black screen.
Blah.

pkopalek said:
Same exact success rate.
I also had to chmod your 'bootanimation' to make it work, but that may or may not be related to me downloading/pushing it from a Windows machine.
Neither here nor there, just a black screen.
Blah.
Click to expand...
Click to collapse
pkopalek, Would you please, in root explorer, goto /system/media/bootscreen and list its contents? there should be a bunch of files and NO folders. I thinks my code was nesting the files in a second bootscreen folder.

lostbytes said:
pkopalek, Would you please, in root explorer, goto /system/media/bootscreen and list its contents? there should be a bunch of files and NO folders. I thinks my code was nesting the files in a second bootscreen folder.
Click to expand...
Click to collapse
Nope. Exactly the contents it should have.
android_audio.mp3, android_audio.mp3_, boot.gif, boot.mp3, boot_animation.xml, etc etc etc.
Certainly no folders in here. Exactly the contents it should have.
/system/media/bootscreen
same contents as C:\Documents and Settings\Administrator.PAULSTERM1\Desktop\android\downloads\bootscreen
which is where I extracted the bootscreen contents (twice, once from your download, once from my own downgrade.zip. same results.)

pkopalek, Would you please, in root explorer, goto /system/media/bootscreen and list its contents? there should be a bunch of files and NO folders. I
Click to expand...
Click to collapse
Nope. Exactly the contents it should have.
android_audio.mp3, android_audio.mp3_, boot.gif, boot.mp3, boot_animation.xml, etc etc etc.
Certainly no folders in here. Exactly the contents it should have.
/system/media/bootscreen
same contents as C:\Documents and Settings\Administrator.PAULSTERM1\Desktop\android\downloads\bootscreen
which is where I extracted the bootscreen contents (twice, once from your download, once from my own downgrade.zip. same results.)
Click to expand...
Click to collapse
This may be obvious, but make sure to check the permissions on the folder itself.
Try this, then reboot.
adb remount
adb shell chmod 775 /system/media/bootscreen
-------------------------------------
Sent via the XDA Tapatalk App

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!

Custom Boot Animation for Non-Rooted X Users?

So I'm confused. On previous phones such as the Droid Eris and Droid 1, users were able to use custom boot animations without being rooted. All you had to do was push the new file to the boot animation location and it would over ride the old one. I really want custom boot animations on my X but am not rooted. Does anyone know a solution to this other than rooting and how to install without being rooted?
Thanks in advance,
IRM

Its really easy just put the bootanimation.zip in the tools folder in android sdk folder and then type in-
:adb push bootanimation.zip /system/media
:adb reboot

Can anyone vouch for this? I don't want to brick my phone as I just received my replacement. This works for NON-ROOTED stock right?
Thanks again,
IRM

/system/media ??? really i thought its was on /data/local

Its in system/media
Sent from my DROIDX using XDA App

putting it in /data/local works on the X, and I read somewhere that it looks there first for the boot animation before grabbing the one in /system/media. plus to push it to /system/media you would have to mount it rw first, which would require su...

[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.

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