I been trying to change my boot animation and I cant seem to get it right
I have downloaded "Boot Animation Changer LITE" and tried to change it. Now i have a different Droid boot animation that I do not want.
How can I change my boot animation with out these apps??
Also how to i revert to my old boot animation, I have a backup
ps. Im rooted on the Droid X 2.2
Bump. I would like to know this as well. I wonder if it is the same as the first Droid. Just replacing the bootanimation.zip file. Can anyone second?
bump bump
I think the easiest way to do so is to flash an update.zip...
Point me in the direction of your original boot anim and I might be able to fashion up an update.zip for you.
Unless I'm missing something, the Droid X doesn't have read/write access to /system while the phone is on in Android...Is that still the case?
Here is the really cool DroidX/Incredible bootanimation. I could not install it, though.
I got permission denied.
Please do fashion an update.zip!!
And try this, maybe it works for you. It's supposed to work, but it didn't for me.
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
Maltadev, here are the two boot animations you requested. They are in the same order as you posted.
Tell me if it works for ya.
Just to be safe, do a Nandroid backup before you flash these. You could probably use ROM Manager too, but IDK.
http://www.mediafire.com/file/gq8w5whz17gnkk0/bootanimation1-signed.zip
http://www.mediafire.com/file/9unu01nddwm5eoc/bootanimation2-signed.zip
Thanks, I managed to get it running, on eclair 2.2, and it looks HELL cool
I did this:
1. Paste bootanimation.zip to sd card.
2. Open a terminal and put in these commands
su
mount -o remount ,rw /system/
rm /system/media/bootanimation.zip -f
cp /sdcard/bootanimation.zip /system/media
Click to expand...
Click to collapse
and reboot. Worked for me
I will flush those updates for you though, just to see if they work =)
I tried renaming it to androidupdate.zip, but when I select "Install Update" in the menu it keeps looking for an "androidupdate.tar", and says "File not found".
Could you recompress it to .tar?
In rom manager or clockwork recovery?
Ahh sorry I misunderstood you - I didn't install any 3rd party programs, I just put the file in /andboot folder and when I rebooted I held the centerdpad and hit "Install Update"...
Do you know how to boot into recovery? That is what I'm talking about.
These bootanimations should be flashable via recovery. You need to manually select and update.zip like bootanimation1-signed.zip and confirm. It shouldn't throw any errors. If it works, reboot and watch your new animation.
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.
LCARS boot animation replacement for SPRINT HTC EVO 4G ONLY
NEW METHOD USING SIGNED ZIP THANKS TO nebenezer
Download signed zip to sd and flash with recovery
Signed zip is in download section below.
NOW AVAILABLE FOR THE GALAXY TAB AS WELL, THANKS TO nobleskill
Link to Galaxy Tab thread here
OLD METHOD:
To install...
extract the zip file
reboot into recovery using rom manager
In the partitions menu select mount /system (or if using other recovery then manually mount /system through adb)
Code:
adb push [path to extracted bootanimation.zip] /system/customize/resource/bootanimation.zip
adb push [path to extracted SPC_animation_final.mp3] /system/customize/resource/SPC_animation_final.mp3
adb reboot
I use this on my own phone and love it.... I am happy to answer questions about installation if they come up, but feel the need to post the usual disclaimer of.... while there is no reason this should do anything negative to your phone as long as you follow the directions, should you brick your phone or cause your phone to act goofy, or drop your phone in the toilet, neither the lcars custom boot animation or myself are in any way shape or form responcible for it. If you don't like that then don't download it.
EDIT: Screen Shots as requested
Had to attach because i'm apperently not verified to post images
Can we get some screenshots?
works amazing and i can rub it in all my star wars fans faces
Oh I love it thank you.
These are probably noob questions.
Does this need root? Do I unzip to the root of the memory card? I'm going to guess a rom manager does need root. Is the code only for adb and not if you have rom manager?
jeffrimerman said:
Does this need root? Do I unzip to the root of the memory card? I'm going to guess a rom manager does need root. Is the code only for adb and not if you have rom manager?
Click to expand...
Click to collapse
Yes you need root because you have to write to the /system partition.
It is easiest to do with ROM Manager's recovery which is why i gave instructions for that.
You extract the zip to your computer and use adb to push to the phone in the correct location.
damn, wish i could flash this like a normal rom :-\
imneveral0ne said:
damn, wish i could flash this like a normal rom :-\
Click to expand...
Click to collapse
I would like to offer this as an update.zip, but i don't know how to sign them... if someone wants to email or pm me that information i will be happy to post it in an update.zip format
Process that I did and its not working
adb reboot recovery
Once the phone was in recovery I did
C:\Users\Tim\Desktop\Android root\tools>adb push bootanimation.zip /system/custo
mize/resource/bootanimation.zip
2584 KB/s (3253387 bytes in 1.229s)
C:\Users\Tim\Desktop\Android root\tools>adb push SPC_animation_final.mp3 /system
/customize/resource/SPC_animation_final.mp3
2402 KB/s (223929 bytes in 0.091s)
adb reboot
Nothing.
Dariuas,
Sounds like the system partition is not mounted...
jramz; said:
In the partitions menu select mount /system (or if using other recovery then manually mount /system through adb)
Click to expand...
Click to collapse
this is covered in the ROM Manager Menu which it sounds like you're not using so if you add
Code:
adb shell mount /system
once in recovery but before the file pushes you should be fine
Outstanding, it works. Now if I want to undo it? :O
Dariuas said:
Outstanding, it works. Now if I want to undo it? :O
Click to expand...
Click to collapse
Not sure why you'd want to....
But... if you do... just push these files the same way and you'll have the sprint 4g back
Nice!
I'm more of a TOS fan but this looks too nice for me to be picky.
I'm really new to Android. Is there a way to do this on the Mac? Thanks.
StormCell said:
I'm really new to Android. Is there a way to do this on the Mac? Thanks.
Click to expand...
Click to collapse
I don't use a mac, nor do i have any access to a mac... however since the android SDK is what gives you access to ADB and there is an Android SDK for mac... i'm assuming that you can do this by following the same steps using the android sdk for mac which you can get:
Here
Great job man, just pushed it to my Evo and its workin great. Thanks.
Pushed bootanimation.zip to Nexus One and it also works fine there.
This is SOOOOOOO awesome! Any chance of this becoming a theme?
jramz said:
I don't use a mac, nor do i have any access to a mac... however since the android SDK is what gives you access to ADB and there is an Android SDK for mac... i'm assuming that you can do this by following the same steps using the android sdk for mac which you can get:
Here
Click to expand...
Click to collapse
With some help I figured out how to do this last night pm me and I think i could get things working for you.
Flashed it and it's way awesome - I'd prefer it with no audio though. Can I just push a different mp3 or an empty file of the same name as the mp3?
I was messing around with root explorer and noticed that i was able to delete my boot animation with it when i was mounted as R/W so i thought i would try to copy one and it also works... so no need to push with adb shell.. here are the steps
1. take the boot animation make sure it is named bootanimation.zip and copy it to your SD card
2. then open root explore and mount R/W and then navigate to the file and press on file till the menu comes up and select copy
3. then navigate to data/local and paste the file in the local directory
and you are done, this can be done with the android_audio.mp3 file as well just paste it to the same place.
just thought this would make it easier for people instead of using adb shell
credit goes to yojoe600
Exactly what I was looking for, I'll give it a try, thanks.
The Animation worked but the Audio didn't, do you also need to put the Audio in a zip file?
I didn't think that you needed root to access /data/
So in that case, would need Root Explorer? Wouldn't any file manager do?
Yeah, you dont need root access at all for this.
just adb push bootanimation.zip /data/local/
palomosan said:
Exactly what I was looking for, I'll give it a try, thanks.
The Animation worked but the Audio didn't, do you also need to put the Audio in a zip file?
Click to expand...
Click to collapse
need to look at the text file in your bootanimations.zip and add the words android to the front of the text in that file
Ok here's one to all the ppl that didnt manage to get it to work like me (HTC desire). My phone is only rooted with revoked, no custom roms etc.
Ive read a lot of forums and i've seen a lot of people that didnt manage to get it to work. After spending nights trying to get it to work is was getting frustrated. All i read was about pushing the file to /system/media or /system/data, but after spending some time looking through all the folders with root explorer i found the actual default bootanimation.zip file.
IT WAS LISTED UNDER /system/customize/resource
so i rebooted my phone in recovery mode:
- mounts and storage
- mount /system
- in cmd: adb shell rm /system/customize/recource/bootanimation.zip
- in cmd: adb push bootanimation.zip /system/customize/resource/bootanimation.zip
note: for this exact command to work u need to have the bootanimation.zip in your androidsdk/tools folder. If not u need to change the push command to adb push <the location here(i.e. d:\downloads\bootanimations\bootanimation.zip)> /system/customize/resource/bootanimation.zip
(this didnt work if i had the file on the c drive of my pc and i would get an error, unless it was in the c:\androidsdk\tools folder, it would work on a 2nd partition, ext storage or whatever)
Only 1 thing... in that same file there prolly still is an audio file, cous when i boot i get my customized bootanimation, but still the standard boot sound. I will be looking in to this now.
If ppl could confirm this works for them aswell i would be happy
EDIT: the bootmusic is listed in the same folder as the bootanimation. It's named android_audio, so you probably wanna remove this aswell (using the command adb shell rm /system/customize/resource/android_music.mp3). Im not sure if you can change this, and since i didnt backup the default bootanimation.zip im dont know if there was someting diffirent about is that would make the music play. I would appreciate if someone could adb pull the original files for me and post em
another note, if you'r making your own bootanimation.zip's make sure compression is set to 0 (store or save)
on my dutch version of winrar its listed under 'ìnpakmethode' -> 'opslaan'
I'd really like to help you out and pull the plain bootanimation (there's no sound actually) from the (custom) rom I'm using but I just can't (see screenshot). If you give me some guidance I can do that, but I do wanna wipe my current one! Please note I recently got S-Off and I'm in Recovery with /system mounted (it says "click to unmount" so it should be good, shouldn't it? Anyway I tried the other way and it's the same... )
well yours might be in the /system/media or /data/local folder. You can always use a file explorer on the phone to find out where yours is located or use adb shell ls /system and check folders if it actually is there.
i r still a noob with all this so i got no clue what s-off is
Ok I got to find and replace the bootanimation.zip file (the only one I could fine on the phone, anyyway) with different ones I got in the forums (Desire bios-like and Star Wars Droid) but I get no animation at all... I mean, I reboot and get the initial still image and the old nexus animation after that is gone, black screen instead, and then Android loads. Any thought maybe? And I'd really like to know how to completely wipe Google Maps/Brut from my phone (don't know the actual files, I got Gmail.apk and I succeeded but the jar's I found for maps weren't enough, I suppose, as I can't install the updated version from the Market, just like I had with Gmail before removing the apk and I solved doing that).
So your still getting the standard animation? Did you use the adb command with the phone in recovery mode to delete and push the new one in?
hy5eyhe5yh
hteherhyeyhey
not bad,i hood you
ToWi1989 said:
So your still getting the standard animation? Did you use the adb command with the phone in recovery mode to delete and push the new one in?
Click to expand...
Click to collapse
Actually I'm getting black screen, no animation... only the first still image (green HTC on white background, you know). And yes, I pulled the original, rm the old one and pushed the new one, in Recovery, with /system mounted.
did u try to make ur own and failed at compressing the .zip ? Or did u just download a standard one off the internet?
Also did u make sure the file u pushed actually is there, in the right folder?
First, I do not have an Infuse. I am probably not an expert at ROMing but pretty close. Done it so many times on my DROID, Fascinate, NookColor, and now my Thunderbolt. But every phone/device seems to have their own unique thing going on.
I am trying to look into the ROMing world of the Infuse and it all looks standard. But I am having trouble figuring out the 3e Recovery. What is this about? I know with my Fascinate, I could not use the newest ROM Manager CW because of Voodoo and other reasons. Is that part of the reason why with the Infuse you have to go through these extra steps outside of flashing CW from ROM Manager?
He is not in a position to pay for Root Explorer as of yet. It seems you can install the Modded 3e through Terminal Emulator, correct? And THEN Flash ClockWork (i9000) through ROM Manager and boot into recovery like normal?
The ultimate goal is to install the Infused ROM. I got all the steps down except the first one--and since he can't use Root Explorer as of now, it may be more complicated. Any pointers here?
From what I understand, the stock recovery image on the Infuse (3e) will not allow you to install/flash unsigned .zip files. Modding the 3e recovery removes the requirement that zips be signed, letting you flash clockworkmod. I'm sure you've already seen this thread about installing modded 3e. If you aren't in a position to pay for root explorer, I'd suggest Super Manager instead. It worked fine for me when I modded my 3e. You don't need ADB or a terminal emulator either; there's an option in both root explorer and super manager to mount the system directory as read/write. Once you have the zip on your SD card, you shouldn't need your computer any more at all to finish installing modded 3e.
And yes, after that's done flash the i9000 CWM and it should be smooth sailing!
Thanks for helping out! That explains it perfectly.
Here is an issue I came across: We unzipped the recovery file and placed on SD card (I think it was like 307kb) and then I went and tried to copy it in /system/bin/ first with Terminal Emulator, then again with ADB. On the last step, I assume when I am pushing it to phone fromt he SD, it says it "cannot find" the recovery file.
Anyone come across something similar?
(I did download Super Manager and that seems like a nice option, I will see if that helps instead).
Eddog4DROID said:
Thanks for helping out! That explains it perfectly.
Here is an issue I came across: We unzipped the recovery file and placed on SD card (I think it was like 307kb) and then I went and tried to copy it in /system/bin/ first with Terminal Emulator, then again with ADB. On the last step, I assume when I am pushing it to phone fromt he SD, it says it "cannot find" the recovery file.
Anyone come across something similar?
(I did download Super Manager and that seems like a nice option, I will see if that helps instead).
Click to expand...
Click to collapse
Hm, that is odd. Dumb question, but are you sure you're pointing ADB/the terminal emulator to the right directory on the right SD card? Or is the recovery file properly named? Those are the only things I can think of.
Eddog4DROID said:
Thanks for helping out! That explains it perfectly.
Here is an issue I came across: We unzipped the recovery file and placed on SD card (I think it was like 307kb) and then I went and tried to copy it in /system/bin/ first with Terminal Emulator, then again with ADB. On the last step, I assume when I am pushing it to phone fromt he SD, it says it "cannot find" the recovery file.
Anyone come across something similar?
(I did download Super Manager and that seems like a nice option, I will see if that helps instead).
Click to expand...
Click to collapse
1) You must be root (e.g. rooted with SuperOneclick) to install the "modded 3e recovery"
2) Its permissions apparently must be EXACTLY the same as the original one for it to work - if it has MORE permissions than normal I've heard it may break!
3) I still haven't figured out why you need modded 3e recovery to flash CWM recovery - you should only need root to do so...
I forget my exact steps as I'm a bit of a Unix shell guru, but mine were something similar to:
1) SuperOneClick root
2) ADB shell into the phone
3) "su" within ADB (the superuser app will prompt on the touchscreen here)
4) in another terminal window on the PC (I'm a Linux guy... I can adb push while being adb shell'ed elsewhere), from wherever you have your modded recovery unzippped "adb push recovery /sdcard/recovery"
5) "cp /system/bin/recovery /system/bin/recovery.bak"
6) "busybox mount /system -o remount,rw" (for some reason, the default mount program is really crippled, gotta do busybox remount)
7) "cp /sdcard/recovery /system/bin/recovery"
8) "reboot"