Hello! I have been reading from this forum, and installing various android roms to the Nand - and so far, no problems. Right now I am using myn's latest warm donut build for my htc kaiser and it works awesome.
Problems started when I made up my mind that I wanted a custom boot screen.
I found one and downloaded it. It was called bootanimation.zip.
I tried searching everywhere on google on how I can copy(or push) this file to
/system/media or/data/media (depends on rom) and you should have your own working custom boot animation.
Click to expand...
Click to collapse
Is there a way to do this? I have tried copying the file to my sd card, then tried pasting it to system/media with astro file manager, but "paste" is disabled.
I am really new to this, and after hours of searching I found out it has something to do with rooting the phone, but none of the instructions I found worked
Could somone with more experience than myself tell me how I could do this? Sorry if this has been asked before - I did not find it. And as I said I am quite new so if I said something stupid, take it easy, ok?
Thank you for your help!
Instructions
1. Download bootanimation.zip
2. Put it on the root directory of your SD card
3. Open the terminal app and enter:
su
cp /sdcard/bootanimation.zip /data/local/
reboot
Click to expand...
Click to collapse
After more searching, I found these instructions, on the forum itself (oops!) but they dont work.
It keeps saying "sdcard/bootanimation.zip": Permission Denied.
Click to expand...
Click to collapse
I am SURE I typed it right.
I tried this 10 times over, same result :S
Can anyone help?
Bootanimation.zip is an Eclair+ implementation. Warm Donut is a donut build and does not support this unfortunately.
Thank you for your reply! It was very much appreciated.
Related
I'd been trying to figure out how to set up a few simple things in my rooted, post-MR, but otherwise stock CDMA Hero. Namely, ADB Remount permissions (/default.prop file), set up Superuser to properly manage permissions for apps that require root, and install Busybox. Ideally, I wanted to set these up manually. Turns out it's not as simple as one might hope. ADB Remount, for example, requires that you modify and repackage the boot.img/recovery.img.
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console. Nothing crazy, it's just MoDaCo's ROM 1.1, but with everything taken out except for the aforementioned items. Once you patch your phone, just these items will be configured and your phone will still look, run, etc. the same as before. Also, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
In any case, here it is. It's working well for me. Hope it helps some of you out too.
****
Thanks goes to Paul of course (MoDaCo) camalot (Droid Explorer) and dagnasty for telling me about the auto-sign plugin that's available in Droid Explorer.
Instructions for manually installing Busybox over here:
http://forum.xda-developers.com/showthread.php?t=591303
****
I responded on ppcgeeks:
mercado79 said:
IAlso, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
Click to expand...
Click to collapse
Yup. It's a script that was added to the boot.img-ramdisk that copies all of your apps to your sd when apps2sd's requirements are met.
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Smacky55 said:
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Click to expand...
Click to collapse
"Correctly" is relative. If there is no EXT partition on the sdcard, then the ROM won't try to move your applications to it. But the script runs regardless.
Sorry, meant if sdcard isn't partitioned at all. Thanks for the answer.
flipzmode told me in another thread that even though this script is included, that doesn't mean that the update.zip i posted will enable apps2sd for anyone. there's more required in order to get it to work (i stripped most everything out).
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Thanks for this. worked out great.
willy900wonka said:
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Click to expand...
Click to collapse
sorry willy man. not sure what i can tell you. i'm pretty close to being a newbie myself. i never fully understood what the script was doing. i simply took the original modaco update and compared it to another script paul had posted on his forums last fall.
if you unzip the file, you should be able to see everything that's going on. the file structure is super simple, so modify it to suit your needs and give it a try. worst case, you'll need to revert to a nandroid backup. oh, and don't forget you'll need to sign the file and zip it back up in order to flash it onto the phone.
come to think of it, i guess maybe i should update the script using the latest modaco rom, though i'm not sure how helpful it'd be for everyone. to be honest, i've since bitten the bullet and moved on to flipz's rom and the gumbo kernel. runs beautifully!
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
partylatino420 said:
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
Click to expand...
Click to collapse
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
I think the problem is that a recovery boot image was not previously installed. A green screen with a set of options should've appeared.
http://forum.xda-developers.com/showthread.php?t=596879
I prefer 1.2.3
mercado79 said:
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
Click to expand...
Click to collapse
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=596879 explanation
code from : http://forum.xda-developers.com/showthread.php?t=583291
13:
Code:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
http://tinyurl.com/yc96j2z
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
Your google search didn't turn anything up on "recovery council" because the operative use would have actually been "recovery console"..
that did it!! Thanks guys!!!
um, what???
mercado79 said:
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console.
Click to expand...
Click to collapse
Apply via the recovery console? Sorry, still very new to this. Thanks!
Recovery Console
Go to the recovery console by holding down home when you power your Android. In that menu, you should see something that says 'flash update from SD card'... or something like that... then you choose the .zip that he has so kindly provided us.
Oh, and you have to put the .zip file that he provided on the SD card if that isn't already obvious :/
I also renamed it update.zip once I copied it to my SD card. Hope this clears it up a little. I just rooted my Hero yesterday.. so I am on the same NOOB level.
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
fallonjp said:
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
Click to expand...
Click to collapse
You shouldn't need to wipe your phone; however I really don't think it's a good idea to use this. I put this together last year when we were still running Android 1.5 so it's WAY out of date. Just go with Nfinite's ROMs. He keeps them almost completely stock (depending on which you choose) and they can serve as great back-up / go-to ROMs.
Ive seen a few threads about boot animations, but none of them with a simple yet detailed guide on how to install/get a new boon animation to work on my Xperia x10 2.1.
I'm no computer genius, but I'm no new to computer either, if someone could point me in the right directions I would love it, Thread I didn't find, a PM or a reply, thanks.
i just use root explorer to copy/paste the file and then set its permissions before rebooting. Just did it and it worked fine on my rooted 2.1 x10a
Tralerprktrash said:
i just use root explorer to copy/paste the file and then set its permissions before rebooting. Just did it and it worked fine on my rooted 2.1 x10a
Click to expand...
Click to collapse
I got root explorer, I took the bootanimation.zip, ive made my own images, ive re ziped it, put it on my SD card and im trying to copy/replace the current bootanimation.zip in System/Media but its just not working :/
I post a working custom boot logo here maybe if you look at it you know wat you did wrong
http://forum.xda-developers.com/showthread.php?t=832315&page=2
Im trying to install a custom boot animation on the recently-developed Cyanogenmod 9 ICS beta ROM (4.0.3) by Lupohirp (for my Optimus T) and I used ES file explorer to navigate to the either the /system/media directory or the /data/local directory and are having problems getting it to work.
Is it a ROM dependant issue why it won't show the custom boot animation?
Because when I put the bootanimation.zip file in the /system/media folder, it still defaults to the vanilla Android flashy logo.
If I try to paste it to the /data/local folder, it will come up with an error saying "bootanimation.zip paste failed!"
MDA400 said:
Im trying to install a custom boot animation on the recently-developed Cyanogenmod 9 ICS beta ROM (4.0.3) by Lupohirp (for my Optimus T) and I used ES file explorer to navigate to the either the /system/media directory or the /data/local directory and are having problems getting it to work.
Is it a ROM dependant issue why it won't show the custom boot animation?
Because when I put the bootanimation.zip file in the /system/media folder, it still defaults to the vanilla Android flashy logo.
If I try to paste it to the /data/local folder, it will come up with an error saying "bootanimation.zip paste failed!"
Click to expand...
Click to collapse
you need to make sure it's going in the right folder, some ROMs point to different places.
you also need to make sure you've given ES root and r/w mount privilege so it can paste stuff where you want.
orangekid said:
you need to make sure it's going in the right folder, some ROMs point to different places.
you also need to make sure you've given ES root and r/w mount privilege so it can paste stuff where you want.
Click to expand...
Click to collapse
It'll take me a bit to ask the creator of the rom since i need 10 posts, but I thought it could be a reason for where the ROM looks for the boot animation.
As for the root and read/write privlieges, i have set ES to request root from SuperUser and know which privileges i need to set (rw-r--r--) as informed by the creator of the boot animation.
Have you tried a boot anim utility?
-------------------------------------
Sent from my Dell Streak 7
Hooride707 said:
Have you tried a boot anim utility?
-------------------------------------
Sent from my Dell Streak 7
Click to expand...
Click to collapse
No, but as soon as you posted that, i googled it and its an actually app. thats pretty cool ill try that.
Note: i tried again yesterday to get a boot animation to work and finally got it to paste into /data/local with rw-r--r-- permissions and even tried pasting it into /system/bin, but it wont work. Just boots up with the white LG logo on a black background, then to the lockscreen.
EDIT: Apparently there is no support for boot animation in this ROM for now, and its clear why it doesn't show one anymore at start up. i guess it did before, but now it doesn't.
Ill just wait to see how its updated in the future, but for now, thread resolved.
Hi. I tried changing the boot up (and down) animation on my One S (S3). And it just doesn't seem to work. I don't get how. Here's all the things I did:
1. Copied the zip file to my phone, through USB. Renamed it to hTC_bootup_one.zip (as mentioned here: http://forum.xda-developers.com/showthread.php?t=1637870). Then moved it to /system/customize/resource using ES file manager.
2. Copied it to my phone. Booted into TWRP recovery. Moved the file from there.
3. Tried replacing the bootanimation.zip and hTC_downanimation.zp with the same zip file.
All three times, it moved the file just fine. ES asked me everytime if I wanted to replace the original file. And after I replaced it, I went into the zip file with the archive viewer, and checked the files, and they were the right ones.
But every time I shut down and restart, I still get the original animation. What am I doing wrong? Is it the wrong location? Please, please help!
I'm running TrickDroid v5.0.0. Could this be the issue?
Finally, this is the file I'm trying to use: http://forum.xda-developers.com/showthread.php?t=1732732
Did you set the permission correctly?
Goatshocker said:
Did you set the permission correctly?
Click to expand...
Click to collapse
Sorry, but what exactly do you mean? Permission for the zip file? Or permission to write onto the system folders? I've got the latter covered. I do have permission to write in the root folders. But if you're talking about permission for the zip file itself, I'm not sure how to do that!
Im talking about the step "- Set permissions to rw-r--r--"
Its done through a terminal or adb shell witrh the command 'chmod'. Im not sure what number rw-r--r-- translated to though, maybe 766 or something.
Goatshocker said:
Im talking about the step "- Set permissions to rw-r--r--"
Its done through a terminal or adb shell witrh the command 'chmod'. Im not sure what number rw-r--r-- translated to though, maybe 766 or something.
Click to expand...
Click to collapse
I just checked that. And yep, it's set to the correct permissions. rw-r-r. The odd thing is though, the original boot animations aren't even there anymore. Since I replaced them with the new one. So how it it even showing me the original one still? Am I doing this in the right location for the One S (S3)? /system/customize/resource?
No idea where its located actually... Try a search for the file and see if it pops up elsewhere (ES Fileexplorer can search, other explorers can probably too)
Goatshocker said:
No idea where its located actually... Try a search for the file and see if it pops up elsewhere (ES Fileexplorer can search, other explorers can probably too)
Click to expand...
Click to collapse
Right so I gave up, relocked, reflashed stock recovery, got the official JB update, unlocked, flashed TWRP, and viola, boot animation works. So basically the problem was with TrickDroid. I'm not sure what. But, there you go. Thanks anyway.
I updated 4.4.4 --> 5.1, yesterday. I am stock/rooted. I have only encountered one issue, so far. I can't change the boot animation.
When I try to use Root Explorer to copy or move the bootanimation.zip to /system/media from my storage, it says, "Copy (or move) unsuccessful."
Then, I tried the bootanimation installation tool in ROM Toolbox Pro. RT Pro reports a successful installation -- but I've still got the stock 5.1 animation.
Is this a new feature of 5.1? Can anyone suggest a work-around?
Thanks!
(arrived from a Google search) I'm seeing the exact same thing on my device (Samsung Galaxy S2), looks like it's some sort of a 5.1 limitation.. :/
victhor1982 said:
(arrived from a Google search) I'm seeing the exact same thing on my device (Samsung Galaxy S2), looks like it's some sort of a 5.1 limitation.. :/
Click to expand...
Click to collapse
Try putting the bootanimation in /data/local
Sent from my Nexus 5 using XDA Free mobile app
Thanks for the tip, but it didn't worked for me (same original boot animation).
Side note: applying boot animation with the theme engine DOES work, when I get more time I'll do some research on how to replace the boot animation of each theme...
victhor1982 said:
Thanks for the tip, but it didn't worked for me (same original boot animation).
Side note: applying boot animation with the theme engine DOES work, when I get more time I'll do some research on how to replace the boot animation of each theme...
Click to expand...
Click to collapse
Out of curiosity, did you use the correct permissions when you put it in /data/local, rw-r-r? When the device boots it looks in /data/local first then goes to /system/media
Sent from my Nexus 9 using XDA Free mobile app
Indeed, permissions were right, but still no luck. Before last couple of (ROM) updates I was easily able to change it on the fly, now it's strangely resisting.. ("unable to perform action" "insufficient space" and that sort of errors..)
OK... I'm the one who started this thread a while back -- and it just sat -- as did I.
Recent posts have encouraged me to try again -- successfully.
Here's what I did this time.
1) Moved new bootanimation.zip to /data/local. Permissions rw-r--r-- Reboot. No luck.
2) Copied new bootanimation.zip from /data/local to /system/media. Renamed old bootanimation to bootanimation.zip.bak Reboot. NOW it works.
Don't ask me why...
moseso said:
OK... I'm the one who started this thread a while back -- and it just sat -- as did I.
Recent posts have encouraged me to try again -- successfully.
Here's what I did this time.
1) Moved new bootanimation.zip to /data/local. Permissions rw-r--r-- Reboot. No luck.
2) Copied new bootanimation.zip from /data/local to /system/media. Renamed old bootanimation to bootanimation.zip.bak Reboot. NOW it works.
Don't ask me why...
Click to expand...
Click to collapse
Me either. But I'm glad you got inspired to try again
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Me either. But I'm glad you got inspired to try again
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Well, thank you, Minnesota brother. Your post brought me to /data/local -- which I'd seen somewhere else lately, too.
That didn't work. But, for some reason, I could move the bootanimation from there to /system/media -- which I had been unable to do directly from storage.
EXACTLY the sort of work-around I had hoped to find. Uff da!
Well, I solved it too, but through a whole different way: the error message said that there was not enough space (¿?), so I deleted some ringtones found in one of the sub folders and THEN it let me paste the new bootanimation.zip .
Turns out that the message was not so unrelated after all. There was free space on the internal storage, but there seems to be a folder limit for System /media.. (¿?)
Apparently this is something very specific to this build/ROM, in the past I used zips way over 15mb and never was a problem.