Root Cannot copy Boot Animation to System/Media

[sprocket28]

Hi. I'm running CM7 nightly build 109 on HTC desire. I downloaded a new boot animation zip file and i am trying to copy it to system/media using root explorer, but when i try to paste, it just says "paste in progress" for a couple of seconds, disappears, and just does nothing after that. r/w is mounted.

anyone got any idea what might be going wrong?

p.s. when i look at root explorer in manage applications, its says that the permission that it requests is write external storage. it doesnt say anything about system storage. i would think that it would request permission to write to system folders aswell.

 

[B2L]

That's really odd, i frequently copy new boot animations over with Root explorer and i have never had the problem. Have you tried just moving the file instead of copying? As long as R/W mounted it should work fine.

 

[sprocket28]

yeah i tried just moving it instead and no joy. i also tried giving the maximum amount of permissions to both the SD card and to the system folder by long pressing each and selecting permissions, but still no joy.

 

[shauny13]

mine goes in data/local (running GV)

 

[shauny13]

ps, take it your s-off? or u cant do it with root explorer?

 

[Howard Hopkinson]

ps, take it your s-off? or u cant do it with root explorer?

That's odd because I did it with RootExplorer without being s-off.

I simply renamed the existing bootanimation.zip in data/local to bootanimation.zip.old, then copied and pasted the new bootanimation.zip and it worked just fine.

If I remember correctly, I was running the Insert coin rom at the time.

 

[shauny13]

well from my understanding, you cant write to the android system when it's running unless your s-off, maybe i'm wrong then.

 

[sprocket28]

well in that case id say that is the problem. cause im not s-off. im gonna go look for tutorials on how to do it. any of u got any handy links for s-off'ing a desire?

 

[shauny13]

I'm sure someone here more knowledgable will put me right.

 

[SUroot]

I'm sure someone here more knowledgable will put me right.

As you said, you cant mount /system r/w whilst android is running without s-off. The security flasg in radio NVRAM prevents it. Thats what S-off is all about.

Most custom roms allow data/local as an alternative boot animation location, otherwise adb push it from recovery

 

[Rastaman-FB]

That's odd because I did it with RootExplorer without being s-off.

I simply renamed the existing bootanimation.zip in data/local to bootanimation.zip.old, then copied and pasted the new bootanimation.zip and it worked just fine.

If I remember correctly, I was running the Insert coin rom at the time.

you dont need s-off for data/local
however he was trying system/media which does

 

[sprocket28]

i got it sorted. i installed the android sdk and adb to my computer and copied the files while in recovery mode. thanks for the help folks.

s-off is a bit too adventurous for my level of experience.

 

[tech guy3]

i got it sorted. i installed the android sdk and adb to my computer and copied the files while in recovery mode. thanks for the help folks.

s-off is a bit too adventurous for my level of experience.

can give me step by step procedure
plz every single step
I m having the same problem

 

[Hadron]

The last post in this thread was 4 years ago, and sprocket28 hasn't posted since 2012, so I don't think you'll get a reply.

If you visit the FAQs section of the forum (near the bottom of the forum homepage) you'll find a thread with instructions for setting up ADB on your computer.

If you have a custom recovery that should include an ADB daemon, so then you just boot into recovery, connect the phone to the computer via USB, check that ADB is working (the command "adb devices" should confirm that), then use the command "adb push" to push the file from your computer to where you want it on the phone ("adb push whatever_your_animation_is_called.zip /system/media/bootanimation.zip"). Personally I'd take a copy of the current bootanimation.zip before doing this, in case your new one doesn't work.

Take a nandroid backup first because you are altering system files, and it's always recommended to have an up-to-date backup before doing that, however trivial the change.