You need adb working.
Download http://www.multiupload.com/SVHPN9AINF into your tools dir of your sdk (/home/jcase/android-sdk/tools/ - c:\android-sdk\tools\ something like that)
go to command line, and change your dir to the tools dir of your sdk
cd /home/jcase/android-sdk/tools - or something like that
run adb push
adb push bootanimation.zip /data/local/
reboot phone. This will override the boot animation in /system/media
Enjoy.
-jcase
yay! first post
and install. works. +1 rep.
Thanks Jcase will try when I get home
Any way to backup the original incase I would like to go back?
adb shell rm /data/local/bootanimation.zip will do it.
the boot process looks in /data/local/ THEN in /system/media. So, if you remove the one you put in /data/local, the original is STILL in /system/media, and is displayed.
Would this work for the Nexus boot animation as long as we change the name of the zip to bootanimation.zip ?
here's the link to the nexus one: sendspace.com/file/0qwx4v
why is it that enevthough I am rooted i get this error when attempting to copy to /system/media?
C:\Users\Derek\Documents\Droid root\android-sdk-windows\tools>adb push bootanimation.zip /system/media
failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': Read-on
ly file system
mattoxic,
if its in the right format it should
derekm2j,
mount it as read/write
mount -o rw,remount /dev/block/mtdblock3 /system
or push to data/local
jcase said:
mattoxic,
if its in the right format it should
derekm2j,
mount it as read/write
mount -o rw,remount /dev/block/mtdblock3 /system
or push to data/local
Click to expand...
Click to collapse
thanks a million my linux is a little rusty. now why would it say no space left on device? I know I dont have to do it this way but the blasted thing is telling me no. Therefore, i want to do it this way.
Ok, this must be for 2.1. Cause I am on 1.5 and it will not work. I keep getting the same boot screen.
Chev, not rooted yet?
Nope, just a little chicken$hit. If there was a way to go back I would.
I have a way back to 1.5 if needed, but it doesnt replace the bootloader.
jcase said:
I have a way back to 1.5 if needed, but it doesnt replace the bootloader.
Click to expand...
Click to collapse
You have my attention .
I will post details
Where can I get different boot animations? I'm not sure if i like the Nexus one boot animation much.
Thank you! Works for me!
Question-
Can something like this be done for the Lockscreen?
Chevelle1768 said:
Any way to backup the original incase I would like to go back?
Click to expand...
Click to collapse
The original bootanimation.zip is under /system/media. You dont really need to back it up if you are doing this the non-root way. Just delete /data/local/bootanimation.zip to revert to the original boot animation.
jadesdan said:
Thank you! Works for me!
Question-
Can something like this be done for the Lockscreen?
Click to expand...
Click to collapse
Nope. Need r/w access to /system for that. Need root.
here's a great site with a ton of boot animations for this way
droidboots.com/downloads/boot-animations/
I'm using the nexus one now and it works great.
Related
So Froyo update came with an Android bootanimation but the nexus one is in /system/media anyone know where the Android one is hiding? I use rootexplorer and looked but can't find it. Thanks!
I am pretty sure froyo has the same boot animation. I had a custom one and when i installed froyo it changed it back to the nexus one. To change it back i adb'd it back to the /system/media/ location and its back to custom.
MKVFTW said:
I am pretty sure froyo has the same boot animation. I had a custom one and when i installed froyo it changed it back to the nexus one. To change it back i adb'd it back to the /system/media/ location and its back to custom.
Click to expand...
Click to collapse
delete the bootanimation.zip then reboot.. you'll see the Android one...
I thought you can just copy your own by doing:
Code:
adb push bootanimation.zip /data/local/
Then when you want it gone, just delete it, and the stock animation will be there.
It's what I do...and it works.
techlogik said:
I thought you can just copy your own by doing:
Code:
adb push bootanimation.zip /data/local/
Then when you want it gone, just delete it, and the stock animation will be there.
It's what I do...and it works.
Click to expand...
Click to collapse
i know this and i have made my own bootanimations.. but thats not my question... i want to know where the Froyo Android animation is hidden!...
hks18psigst said:
i know this and i have made my own bootanimations.. but thats not my question... i want to know where the Froyo Android animation is hidden!...
Click to expand...
Click to collapse
That makes more sense...not sure. Would like to know myself.
Did you try /system/media?
That's where mine is (but mine is CM Eclair, not Froyo, not stock - might make a difference).
Jack_R1 said:
Did you try /system/media?
That's where mine is (but mine is CM Eclair, not Froyo, not stock - might make a difference).
Click to expand...
Click to collapse
I have the same. CM base with Pauls Froyo overlay.
/system/media it is.
so what you need to type in adb is:
adb remount
adb push bootanimation.zip /system/media
http://www.myhangoutonline.com/tutorials/nexus-one/12-change-your-boot-screen-on-n1
Ersdal said:
I have the same. CM base with Pauls Froyo overlay.
/system/media it is.
so what you need to type in adb is:
adb remount
adb push bootanimation.zip /system/media
Click to expand...
Click to collapse
No one is listening.. if you are on froyo remove bootanimation then reboot there will still be an animation that is from the froyo update Cyanogen or Paul have put the nexus one into there builds I want to know where the froyo Android animation is hidden
I've read a couple boot animation threads so far, I have a bootanimation.zip file I want to try out. For whatever reason I cannot understand how I am supposed to get it on my phone. My eris is rooted but I'm not sure what next. Do I need adb? can I run these .bat files floating around here from my sd card? For some reason I can't wrap my head around this and it is frustrating, can anyone clarify what a rooted user needs to have/ what commands to run?
Thanks
The easiest way would be to download EStrongs File Manager from the Market. Put the boot animation on your SD card, then open EStrongs and move the zip into the /System/Media folder. Make sure you only have 1 boot animation in the there. Enjoy.
es0tericcha0s said:
The easiest way would be to download EStrongs File Manager from the Market. Put the boot animation on your SD card, then open EStrongs and move the zip into the /System/Media folder. Make sure you only have 1 boot animation in the there. Enjoy.
Click to expand...
Click to collapse
This does not work. It is not possible to copy from the sd card and put a file in my system folder
**edit, I see I needed to give estrong SU permissions. I got it to work just fine. Thank you.
Glad you got it to work, and you're welcome.
shatterpoints said:
This does not work. It is not possible to copy from the sd card and put a file in my system folder
**edit, I see I needed to give estrong SU permissions. I got it to work just fine. Thank you.
Click to expand...
Click to collapse
or u can use terminal emulator
su (enter)(to get root permisions)
cp /sdcard/(wherever your bootanimation.zip is) /data/local (enter)
reboot (enter)
shatterpoints said:
It is not possible to copy from the sd card and put a file in my system folder
Click to expand...
Click to collapse
You were so sure of yourself though! LOL
Bit of a noob to all this, so work with me please...... I'm trying to replace the Cyanogemod boot animation that came with CELB froyo 2.6 rom. I have a new bootanimation.zip copied to my SD card. I'm using ES File Explorer with SU permissions and it wouldn't let me copy new zip file to: /system/media. Says copy failed. If I try to delete the bootanimation.zip in /system/media, it says file can't be deleted.
So then I went to my terminal emulator and typed:
su (enter)
cp /sdcard/bootanimation.zip /data/local (enter)
reboot (enter)
And now I have not boot animation at all. It shows the bootscreen (3 skateboarding droids) then black screen, then lock screen
Where did I go wrong??
Update: removed bootanimation.zip and there was also a bootscreen.zip from /data/local. REbooted and cyanogemod boot screen came back.
I retried the terminal emulator and it worked!
junk74 said:
Bit of a noob to all this, so work with me please...... I'm trying to replace the Cyanogemod boot animation that came with CELB froyo 2.6 rom. I have a new bootanimation.zip copied to my SD card. I'm using ES File Explorer with SU permissions and it wouldn't let me copy new zip file to: /system/media. Says copy failed. If I try to delete the bootanimation.zip in /system/media, it says file can't be deleted.
So then I went to my terminal emulator and typed:
su (enter)
cp /sdcard/bootanimation.zip /data/local (enter)
reboot (enter)
And now I have not boot animation at all. It shows the bootscreen (3 skateboarding droids) then black screen, then lock screen
Where did I go wrong??
Update: removed bootanimation.zip and there was also a bootscreen.zip from /data/local. REbooted and cyanogemod boot screen came back.
I retried the terminal emulator and it worked!
Click to expand...
Click to collapse
Just an fyi Sometimes you need to re assign SU permissions to estrongs. Just uncheck and then check the mount syst directory as writeable and it will work. Its kinda like re shareing a folder in windows. Sometimes shares drop for no reason or just need to be re shared.
ps. I dont like using the terminal but thanks for the simple commands, I've seen way to many different ways to change the animation. The above cmd's are simple and easy.
Ok i managed to get the stock lockscreen if you all want to use it.
There is a possibility that the file i signed has a different signature, but i dont think it will.
Remember make a backup! always.
If your phone gets messed up it is not my fault.
I have warned you, so here you are. EDIT: Unzip the file then push the one inside of the zip.
put the file i uploaded in /system/framework ............. let me know what you think!
Thank to : Ateisti for giving the info on how to modify it.
If you want to go back to your old lockscreen download the enable_glass_lock.zip, unzip it, and push the enable_glass_lock to /data/local
If your signature is different it will get stuck on the samsung, you can then restore your backup.
and if you want it then run these instructions:
You need to use adb not rootexplorer
DO this while in cwm recovery
1. Rename the file you downloaded to patched.odex
2. adb push it to your /system/framework
3. adb shell then cd into /system/framework
4. run this
dd if=android.policy.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
5. exit shell
6. adb pull the android.policy.odex for backup
7. adb shell cd /system/framework
8. rm android.policy.odex
9. mv patched.odex android.policy.odex
reboot and you should have stock lockscreen.
You are the ****ing man!
How well does this work with the alarm silencing and incoming calls? Thanks!!!
EDIT: Never mind...testing it out.
wasupwithuman said:
Ok i managed to get the stock lockscreen if you all want to use it.
There is a possibility that the file i signed has a different signature, but i dont think it will.
Remember make a backup! always.
If your phone gets messed up it is not my fault.
I have warned you, so here you are.
put the file i uploaded in /system/framework ............. let me know what you think!
Thank to : Ateisti for giving the info on how to modify it.
Click to expand...
Click to collapse
I'm a little confused... do we need to just change the file to android.policy.jar or leave it the name that it is and just move it to /system/framework
thanks!
taypotts said:
I'm a little confused... do we need to just change the file to android.policy.jar or leave it the name that it is and just move it to /system/framework
thanks!
Click to expand...
Click to collapse
Keep the name and adb push it to /system/framework (you might want to backup your old one) you can backup by "adb pull /system/framework/android.policy.jar"
You can also install it using root explorer if you want.
wasupwithuman said:
Keep the name and adb push it to /system/framework (you might want to backup your old one) you can backup by "adb pull /system/framework/android.policy.jar"
You can also install it using root explorer if you want.
Click to expand...
Click to collapse
See I'm still confused, cause there is no file named android.policy (samsung fascinate) in the folder "framework" but there is android.policy.jar
Should I unzip the downloaded file then push that?
taypotts said:
See I'm still confused, cause there is no file named android.policy (samsung fascinate) in the folder "framework" but there is android.policy.jar
Should I unzip the downloaded file then push that?
Click to expand...
Click to collapse
yep, unzip first...
Quick question, does this take away the option for the other two lockscreens, ie glass and puzzle? If not I can throw this in my theme port (with your permission of course) and also theme this lockscreen as well.
frostman89 said:
Quick question, does this take away the option for the other two lockscreens, ie glass and puzzle? If not I can throw this in my theme port (with your permission of course) and also theme this lockscreen as well.
Click to expand...
Click to collapse
Your more then welcome to use it, but It does not give an option. So you would have to create a seperate theme for people who would just want the stock lockscreen.
I've tried installing this twice with root explorer, and both times my phone gets stuck on the Samsung logo when I reboot.
To install the file, I unzip the download and then place the .odex file in /system/framework. Any ideas on what I'm doing wrong?
Sent from my Fascinate using XDA App
tiger4life said:
I've tried installing this twice with root explorer, and both times my phone gets stuck on the Samsung logo when I reboot.
To install the file, I unzip the download and then place the .odex file in /system/framework. Any ideas on what I'm doing wrong?
Sent from my Fascinate using XDA App
Click to expand...
Click to collapse
your signature isnt the same as my file. you can try to do this but you need to use adb not rootexplorer
DO this while in cwm recovery
1. Rename the file you downloaded to patched.odex
2. adb push it to your /system/framework
3. adb shell then cd into /system/framework
4. run this
dd if=android.policy.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
5. exit shell
6. adb pull the android.policy.odex for backup
7. adb shell cd /system/framework
8. rm android.policy.odex
9. mv patched.odex android.policy.odex
reboot and you should have stock lockscreen.
hey man, i'm new to all this i've done all that u said, but what is the command to pull the android.policy.odex from the phone? I think i'm putting the wrong directory in the command because I keep getting "remote object '......android.policy.odex' does not exist" thanks for this, btw i really dislike that puzzle piece unlock bs.
nevermind, I wasn't in cwm when doing it the first time. Thanks again.
I like this, can't wait to try it.
wasupwithuman said:
your signature isnt the same as my file. you can try to do this but you need to use adb not rootexplorer
DO this while in cwm recovery
1. Rename the file you downloaded to patched.odex
2. adb push it to your /system/framework
3. adb shell then cd into /system/framework
4. run this
dd if=android.policy.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
5. exit shell
6. adb pull the android.policy.odex for backup
7. adb shell cd /system/framework
8. rm android.policy.odex
9. mv patched.odex android.policy.odex
reboot and you should have stock lockscreen.
Click to expand...
Click to collapse
That did the trick. Thanks for the help!
Sweet, put that file in the xultimate and deodex'ed and got it working.. Thanks
Followed step by step from adb, and got stuck with the Samsung screen.
DUNC4N said:
Followed step by step from adb, and got stuck with the Samsung screen.
Click to expand...
Click to collapse
hmm... you used the file i attached and did eveything in adb? try again, i'd like to help more, but if you did everything step by idk...
You did it in cwm recovery right?
Thanks for the reply.
Yes I did it in clockwork recovery. I may of had some confusion on the second to last step. I'll try again when I get home.
Two questions: Is the silent slide functional, and are the last two steps verbatim.
Thanks again.
Sent from my SCH-I500 using XDA App
DUNC4N said:
Thanks for the reply.
Yes I did it in clockwork recovery. I may of had some confusion on the second to last step. I'll try again when I get home.
Two questions: Is the silent slide functional, and are the last two steps verbatim.
Thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
not sure about the silent slide....i don't use this lockscreen. i just made it for you guys... and yes follow the last two steps exactly how i have them.
Silent mode is functional.
can anyone post a link for the default galaxy s boot screen? the one with the shiny big S logo. thks
It will be in the rom kitchin.
http://forum.xda-developers.com/showthread.php?t=817703
Buts its also on your phone unless you removed the files . Delete boot animation file if you have custom boot .
jje
thks for the link, but i need to create the entire rom just to get the default boot screen? anyways to just get the file for the bootscreen and just flash it? i m on darky's rom.
delete or rename the bootanimation.zip in system/media and the stock will work
yeh i know all that, but the prob is tat my stock animation is with my phone subscriber's animation.
sn0wjie said:
yeh i know all that, but the prob is tat my stock animation is with my phone subscriber's animation.
Click to expand...
Click to collapse
How is that possible, darkys rom has:bootsamsungloop.qmg and bootsamsung.qmg and they are the glowing S, they should overwrite yours or?
hmm, i cant seem to delete the bootanimation.zip as it prompts error, and also renaming it prompts insufficient permission. any idea?
You need to mount system as r/w.
hmm. its confusing how to mount the thing to rw.
everyttime i does the typing (mount -o rw,remount /system) in terminal emulator, it wil prompt this: Usage: mount [-r] [-w] [-o options] [-t type] device directory.
and i dunno wat it means. i watch vid on youtube, and after they type in the mount command, there isnt any prompt after that. I wonder did i miss out any steps.
enlighten me pls =D
mount it with sgstoolbox or use root explorer
sewe said:
mount it with sgstoolbox or use root explorer
Click to expand...
Click to collapse
tried your sgs toolbox method, change the option to (rw), but when i access system\media thru astro, the file is stilled label as (r).
haven try the root explorer method though as it needed $ for the app. =D
I tried to change the boot animation, running M Preview 3, and despite the fact that the flash claims to have performed successfully, it did not. I'm trying to flash the Marvel boot from the Themes and Apps section, and I know the flashable file worked on 5.1.1. It didn't overwrite the bootanimation.zip in /system/media. At one point, I was able to manually move the file there myselfusing Root Explorer, but I did not realize that the /system partiton did not have enough space to hold the entire zip file, so it was a corrupted zip at that point, and now my boot animation is just "android" in gray lettering. I cleared up enough space to hold the entire zip file of the marvel boot, but now I cannot move the file there, ES File Explorer and Root Explorer simply say it failed to copy.
I just tried to use adb to push the zip file from my computer, but it fails because /system is a read-only file system. So, I tried to remount with a shell as read-write, after some initial issues with apparently /system/xbin/mount not working properly, it did remount as read-write when using /system/bin/mount. But, adb push still fails because /system is a read-only file system.
Code:
mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
But, as you can see, it's mounted as read-write.
I, also, just tried to move the file as root in an adb shell, with no luck. A bootanimation.zip shows up in /system/media, but apparently it is corrupt because I cannot open it with root explorer, or in Windows when I pull it. When I try to move the boot animation that I want, the shell reports that there is not sufficient space, which is true now. The bootanimation.zip takes up 40MB of the 55MB of free space in the /system partition. Any time I try to delete the zip, it is automatically recreated before I have a chance to move anything in it's place, even when I do:
Code:
rm /system/media/bootanimation.zip | mv /storage/emulated/0/Download/marvelboot/system/media/bootanimation.zip /system/media/bootanimation.zip
So, what am I missing? Is it even possible to change the boot animation on Android M? Am I doing something wrong, or not doing something I need to?
why flash it? its a boot animation.. extract it from the zip, then pkace the bootanimation.zip into /system/media/ then just reboot. thats all it takes.
edit.. i didnt read ypur whole post and realuze that yoh have other issues.
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
cappiez said:
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
Click to expand...
Click to collapse
no, no problem here. do you have full root? i mean do you have the ability to edit anything in /system/?
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
cappiez said:
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
Click to expand...
Click to collapse
so you fo have full root. i use root explorer to put animations into /system/meda/, havent had any issues. does that animation work on a n6?
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
cappiez said:
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
Click to expand...
Click to collapse
nope. im on m preview 3, and it works fine here.