Related
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!
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.
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...
All,
I followed the below instructions to change the Boot Animation on my Vibrant (using the qmp files, since i cant find a the same in bnootanimation.zip form), but have run into a problem. I see the Galaxy S logo swirling, but i also saw the MACNUT R14 bootanimation flashing in every frame.
I even deleted the bootanimation.zip but then see the ANDROID logo every other frame. I have attached my inti.rc file so tat maybe someone can see if i missed something? Please help if you can!
Changing Boot Animation:
1. Stock Android is Default!
2. If you wish to Change to Nexus boot or something else.. place the .zip into /system/media/bootanimation.zip
3. Changing Back to Stock Vibrant Boot Screen Do the Following.
3.1. Adb pull /system/init.rc
3.2 Find bootanimation & change to the Following.
#service bootanim /system/bin/bootanimation
# user graphics
# group graphics
# disabled
# oneshot
3.3 Next you need to Push samsungboot.qmp & samsungbootloop.qmp into /system/media
4. Push the edited init.rc back to /system/init.rc
5. All Done, Enjoy!
GameOver69 said:
All,
I followed the below instructions to change the Boot Animation on my Vibrant (using the qmp files, since i cant find a the same in bnootanimation.zip form), but have run into a problem. I see the Galaxy S logo swirling, but i also saw the MACNUT R14 bootanimation flashing in every frame.
I even deleted the bootanimation.zip but then see the ANDROID logo every other frame. I have attached my inti.rc file so tat maybe someone can see if i missed something? Please help if you can!
Changing Boot Animation:
1. Stock Android is Default!
2. If you wish to Change to Nexus boot or something else.. place the .zip into /system/media/bootanimation.zip
3. Changing Back to Stock Vibrant Boot Screen Do the Following.
3.1. Adb pull /system/init.rc
3.2 Find bootanimation & change to the Following.
#service bootanim /system/bin/bootanimation
# user graphics
# group graphics
# disabled
# oneshot
3.3 Next you need to Push samsungboot.qmp & samsungbootloop.qmp into /system/media
4. Push the edited init.rc back to /system/init.rc
5. All Done, Enjoy!
Click to expand...
Click to collapse
Android stores boot animations in two places, not just one. Go to data/local and you should see another bootanimation file in there. That is the stock android bootanimation. Delete that and it should run normally. That's why you're seeing the ANDROID logo every other frame.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant General
So, it's not really a problem, but I don't understand what's happening at all. I rooted my HD7 with Kindle Fire Aide, and used it for a long time. I then changed the boot animation by putting a zip in the system/media folder. It took a little while to shut down, but showed the new anim when it booted up again. I rebooted it again just to make sure. Then, I tried to change it again by doing the exact same thing, but it didn't change that time. (It booted using the 2nd boot anim) So then I discovered that the /data folder had magically populated, and that the boot anim had been copied to the /data/local folder. I replaced the boot anim zip with the one I wanted, and it works, but it only plays once, and then it's just black until the Kindle is on.
Does anybody know what happened with the /data/local thing? There was nothing in the /data folder before I did this.
Geckodudes said:
So, it's not really a problem, but I don't understand what's happening at all. I rooted my HD7 with Kindle Fire Aide, and used it for a long time. I then changed the boot animation by putting a zip in the system/media folder. It took a little while to shut down, but showed the new anim when it booted up again. I rebooted it again just to make sure. Then, I tried to change it again by doing the exact same thing, but it didn't change that time. (It booted using the 2nd boot anim) So then I discovered that the /data folder had magically populated, and that the boot anim had been copied to the /data/local folder. I replaced the boot anim zip with the one I wanted, and it works, but it only plays once, and then it's just black until the Kindle is on.
Does anybody know what happened with the /data/local thing? There was nothing in the /data folder before I did this.
Click to expand...
Click to collapse
the files in /data don't show up until you enable root setting for your file manager. not sure why the boot animation only plays once though. maybe it is something with the stock ROM.
zander78 said:
the files in /data don't show up until you enable root setting for your file manager. not sure why the boot animation only plays once though. maybe it is something with the stock ROM.
Click to expand...
Click to collapse
The other animations play more than once, so it might be something with the zip file. Idk.
Thanks for your info.