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.
Related
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.
As I was following the guide to improve the galaxy's quadrant score, I messed on one of the lines and overwrote the playlogos1 file that was meant to be renamed to playlogosnow.
I'm currently running JM5; do I need a file from the same version or can I take it from something like froyo which I found?
Or will this require me to reflash, and is it safe to do so without the file?
you need this file only to play the startup animation. if you don't care for the animation you can just delete it or replace it with a script (as you did, i suspect?!).
anyway, you can take this file from any firmware to replace your's...
Ah damn. Just to be on the safe side as I had no idea of the file's importance, I've just finished reflashing the firmware to restore it.
Thanks anyway.
SYUNIXT said:
Ah damn. Just to be on the safe side as I had no idea of the file's importance, I've just finished reflashing the firmware to restore it.
Thanks anyway.
Click to expand...
Click to collapse
you'r welcome ... if you want to do the fix again:
the playlogos1 file ist just the binary that play's the animation. it will be started with root-permissions, so you can replace it to run custom commands as root. in our case we want it to
*) make the loop device and set it up
*) mount the ext2.data file
to make the fix permanent.
mine looks like (you have to make the ext2.data file, format it, copy the data and relink before!!!!):
busybox mknod /dev/loop0 b 7 0
busybox losetup /dev/loop0 /data/ext2.data
busybox mount -t ext2 -o noatime,nodiratime /dev/loop0 /data/ext2.data_mp
and if you want your sgs to play the startup animation. you have to rename playlogos1 to something else and start it from the script...got it?
but again, if the file is not there (eg. you deleted it) nothing bad will happen, you will just not see the animation. the sound will still play and everything else will be fine
Can anyone provide me with the playlogos1 file, or somewhere that I can get it? I updated my rom and it somehow was erased.
ayinyesh said:
Can anyone provide me with the playlogos1 file, or somewhere that I can get it? I updated my rom and it somehow was erased.
Click to expand...
Click to collapse
Try OCLF from the market - it used to have a restore playlogo script.
http://www.youtube.com/comment?lc=8KNWgMta4EvqAcKfdwk-z2flON7mZ3RxQDynukPTSjk
Fix boot screen after one click lag fix:
1: Download playlogosnow megaupload. com/?d=M1N9RFMM
2: place the file on your internal sd.
3: replace (copy past) the file using a root manager in /system/bin
4: reboot
Should have posted this in Q&A....
jodue said:
you need this file only to play the startup animation. if you don't care for the animation you can just delete it or replace it with a script (as you did, i suspect?!).
anyway, you can take this file from any firmware to replace your's...
Click to expand...
Click to collapse
You better not advice people to brick their phones. Missing playlogo1 causes your sgs wont boot because it freezes trying to load playlogos1. Thanks for the advice, now i have bricked phone.
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.
I've updated my device today to 6.0.1 and rooted, however I can't seem to change the boot animation (yes, I have searched for answers and tried quite a few fixes).
Root Explorer tells me I have renamed the old file and copied the new file, however once I leave the directory and go back the old file is still there.
I have used the file explorer in TWRP and managed to delete the stock boot animation, but get a FAILED message when I try to copy the new file.
I used the terminal in TWRP and tried to copy the file manually, and receive a "No space left on device" message.
I've also tried mounting the /system as rw in adb. I can delete the bootanimation.zip file from there, and df -h shows 3mb free. Shouldn't the system partition have more space available than that?
Am I missing something, or has something changed with the new android versions?
Google has filled the system partition up to the brim. Also you can't remount system as rw while Android is running.
But the direction is right, go to TWRP, mount system, delete the old bootanimation. If the new one is not that much bigger then you could just copy it there, set permissions to rw-r--r--. But if the new animation is significantly bigger, you'll have to delete some bloatware first.
Thanks for that. The odd thing is, when I run DF in the terminal, it shows I have 20mb free. The boot animation file I am trying to copy is 6mb.
I'll keep poking around. If it doesn't work, it doesn't. It's not hugely important
The custom rom I am using on my device for some reason doesn't have logcat. After a bit of digging up in the root folder, I found out that it was missing logd file which should be present under /system/bin and is necessary for logcat to work. Already tried to copy it from the official rom of my device (I extracted it from system.img) but pasting it manually (tried both a root explorer and adb) in /system/bin won't do anything as any changes made to /system/bin get reverted back automtically after reboot.
So I thought of a method about hooking Runtime.loadLibrary with xposed and redirecting it to logd on my internal storage when it's requested. Isn't that possible ?
Otherwise, do you suggest any other solution?
Do you think I should move the file with twrp if this doesn't work ? (I am avoiding the use of it because it's still unstable for my device and bootlooped a few times.).
Or should I edit the custom rom's system.img and repack it (I'm afraid if it's size changes my device won't boot)
I will be very grateful if someone helps me out
if you copy a file you must set right permissions and ownership