Related
i have searched but cant find the ideal guide on how to change the boot animation AND mp3 sound. i see it all on youtube but its confusing the way they do it.
someone point me in the right direction?? thanks in advanced.
also do i need to have NAND unlocked??
I would purchase Root Explorer for $1 and do it through that app.
You basically need to find the thread located on this website with a collection of boot animations. Download the zip that's included and flash through recovery. If you wish to change the .mp3 sound for let's say the Dancing Droid boot animation you would want to go through Root Explorer and overwrite/place mp3 file in the correct formatted name.
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=708173
Cool thanks but root explorer is like $5 where do you get it for $1?
-On That Black Ops Status-
Oops my bad. I probably too it for another app. Try downloading ES File Explorer since it's free. I buy so many apps that I forget the price sometimes.
so it there any exact walkthrough?
im just not used to all the "experienced people should know what this means"
stuff..
like when u say recovery u mean hboot??
Recovery is when you power off your phone, hold volume down and boot on your phone while holding it down. You can then flash .zip from recovery by choosing "choose zip from sdcard" and finding the boot animation, confirming (as in yes) and installing.
if i mess up can i reflash my nand??
i already backed everything up..
Yes you can do a Nand restore.
cool thank you
gqstatus0685 said:
Recovery is when you power off your phone, hold volume down and boot on your phone while holding it down. You can then flash .zip from recovery by choosing "choose zip from sdcard" and finding the boot animation, confirming (as in yes) and installing.
Click to expand...
Click to collapse
didnt work in recovery.. i flashed and everything but no success.. same old one..
I've been trying to figure it out too?
Swyped From Eva Running Myn's RLS4.95 On The Now Network!
The boot animation is in /system/media put the file in there & replace the existing one. It must be named the exact same & be a .zip I suggest booting into recovery & wiping cache & dalvik after replacing it
Will try that hope it works
theultimatev said:
The boot animation is in /system/media put the file in there & replace the existing one. It must be named the exact same & be a .zip I suggest booting into recovery & wiping cache & dalvik after replacing it
Click to expand...
Click to collapse
Let me know if it works nuggy
-On That Black Ops Status-
Didn't let me overwrite my boot out said its read only. So my guess is I have to do it through adb?
xtrubambinoxpr said:
Let me know if it works nuggy
-On That Black Ops Status-
Click to expand...
Click to collapse
Swyped From Eva Running Myn's RLS4.95 On The Now Network!
Pushboot is the easiest way
Oh boy. Have you guys actually made a rom or flashed a boot animation? I don't think so. Here's a step-by-step tutorial.
1. NANDROID NANDROID NANDROID <--- Always do this when modifying your rom unless you like starting over.
2. Find the bootanimation that you want. Some come with the sound and some don't. I prefer ones without sound.
3. Get the Android USB drivers and ADB from the Android SDK if you haven't already and make sure the drivers are installed for your phone. If I have to explain that, then you shouldn't use technology.
4. Now, I would just do this the easy way and open up the zip file that the bootanimation comes in. If the bootanimation is named bootanimation.zip, then there's nothing to extract as that's the file we need. The sound file will be called SPC_animation_final.mp3. That's what the file names for the animation and sound must be.
5. Now, make sure that bootanimation.zip and SPC_animation_final.mp3 are in the same folder as ADB and open a command prompt. Make sure you Chdir to the same directory that ADB is and then type: adb remount
6. If you're rooted, you should see "remount succeeded" and you'll have read/write on your phone. If you don't see that message, you have to remount another way. The other way is to type: adb shell. Then, type: cat /proc/mounts. Look for the line that has an mtdblock in it and /system. You'll need that mtdblock number. The command I use is: mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system. Yours may be different if your partition setup is different. Yours could be 3, 5, 6, etc. If you aren't rooted, then leave this thread and go do that.
7. If you are still in adb shell, type exit to go back to the normal CMD. Otherwise, just go to step #8.
8. Next, type: adb push bootanimation.zip /system/customize/resource. It should copy it over without error.
9. Then, type adb push SPC_animation_final.mp3 /system/customize/resource. Again, it should copy without error.
10. Now, to test to make sure this worked, you can type adb shell bootanimation. Watch your phone and if you see your bootanimation, then it worked. If you don't, then it didn't copy right. Not sure if this test will play the animation sound as I don't use one.
11. If you really want to make sure it worked, type adb shell reboot and that will reboot your phone.
12. ???
13. Profit!
so everything is done through adb command..
-_- thats too difficult for me.. cuz if overtime i wanna change it again..
its a hassle..
xtrubambinoxpr said:
so everything is done through adb command..
-_- thats too difficult for me.. cuz if overtime i wanna change it again..
its a hassle..
Click to expand...
Click to collapse
what exactly is it that you want to do? I might help
basically want one of the animations from this page http://forum.xda-developers.com/showthread.php?t=708173
i really want the dancing android and a song of my choice but if its too complicated i dont think its worth it..
i use boot animation changer lite on my evo and it works fine..
maybe there is an easy way??
Running HaXspresso on my wife's MT3GS -- awesome ROM, and she really loves it!
...EXCEPT for the sound that goes with the boot animation.
I've tried installing different boot animation zip files into /system/media but it looks like this ROM uses some other location for the boot animation.
So I'm wondering if anybody has ideas on how I can disable that boot sound?
blacra said:
Running HaXspresso on my wife's MT3GS -- awesome ROM, and she really loves it!
...EXCEPT for the sound that goes with the boot animation.
I've tried installing different boot animation zip files into /system/media but it looks like this ROM uses some other location for the boot animation.
So I'm wondering if anybody has ideas on how I can disable that boot sound?
Click to expand...
Click to collapse
its under system/customize/resource/ its called TMO_Bootup_sound.mp3 if you have S-OFF you can just delete it using root explorer or some app like that, if not you can do this:
go into recovery, plug your usb cable and using adb type adb remount first, adb shell and then type cd system/customize/resource after that type rm TMO_Bootup_sound.mp3 (with the capitals and all, otherwise it wont delete it) and then reboot, it should be gone
I dont know if there is any easier way to do it (u can delete the file from the rom zip file, wipe and reflash it but you would have to do a backup of the apps and all that so xD) if anyone know an easier way please share it
Cool!
I just didn't know where the file was located to delete it.
I ended up running ADB shell in recovery, but it worked out just fine. No more boot sound to annoy my wife! Yay!
I have tried flashing damm near every Animated Boot Screen i have made flashable from XDA and none wanna work..
what am i suppose to do to get a diff boot animation screen on this device??
Adb:
adb remount
adb push bootanimation.zip /system/media
adb reboot
Root explorer:
enable r/w mode
move the bootanimation.zip file to the /system/media folder
I just got mine to work, only took a minute to do. If you go to root explorer do he following.
1. find the file in system/customize/resources named bootanimation.zip (it may have something else in front of it. Mine was spc_bootanimation.zip)
2. click at the top where is says r/w
3. find the boot animation you want to find and long press and choose mve
4. put it in the file system/customize/resources and paste it there
5. longress and change the permissions to match the origial one
6. change the name of the old one (i put a one at the end of bootanimation)
7. change the nam of the new anmation to what the original was
8. change back to r/o same way you changed to r/w
9. reboot nd enjoy.
Dboy352 said:
I just got mine to work, only took a minute to do. If you go to root explorer do he following.
1. find the file in system/customize/resources named bootanimation.zip (it may have something else in front of it. Mine was spc_bootanimation.zip)
2. click at the top where is says r/w
3. find the boot animation you want to find and long press and choose mve
4. put it in the file system/customize/resources and paste it there
5. longress and change the permissions to match the origial one
6. change the name of the old one (i put a one at the end of bootanimation)
7. change the nam of the new anmation to what the original was
8. change back to r/o same way you changed to r/w
9. reboot nd enjoy.
Click to expand...
Click to collapse
By the way, /system/customize/resource is for sense, aosp is /system/media.
Sorry I didn't specify, I thought that cm roms were all sense. Thanks for the info roxxorz, good to know if I ever go back to an aosp.
Dboy352 said:
Sorry I didn't specify, I thought that cm roms were all sense. Thanks for the info roxxorz, good to know if I ever go back to an aosp.
Click to expand...
Click to collapse
Just for future reference, if you ever say 'I thought CM was sense' someone of ignorance spots it, they'll flame you horribly.
But yea, CM = AOSP = No sense. So you have to push the bootanimation.zip to the correct folder,
Crap, I was confused I forgot I flashed from evo deck which was cm kernel and aosp, I'm now on misfits rc1 which is like a sense/gengersense mix, really nice, but not cm. I forgot I changed to misfit therefore te cm being sense lol. My own ignorence. Thanks for the info man. I'm still learning very slowly lol.
Hey JSmurfy, if you want a custom splash page and cant get it in adb I have the file you would need to flash it as well. I finally got mine changed using it since i can't us adb to push it to the phone. Just let me know.
Dboy352 said:
Crap, I was confused I forgot I flashed from evo deck which was cm kernel and aosp, I'm now on misfits rc1 which is like a sense/gengersense mix, really nice, but not cm. I forgot I changed to misfit therefore te cm being sense lol. My own ignorence. Thanks for the info man. I'm still learning very slowly lol.
Hey JSmurfy, if you want a custom splash page and cant get it in adb I have the file you would need to flash it as well. I finally got mine changed using it since i can't us adb to push it to the phone. Just let me know.
Click to expand...
Click to collapse
Well easy to get it confused because there are 'senseless' roms, which is htc sense removed, so it LOOKS like AOSP, with the vanilla [CM style lock screen]. You just have to make sure what the rom says in the features, ect.
If you can't/not good with adb, you can use root explorer [purchase or search through google] to move it to the correct folder.
Thats what I did, using root explorer and it works great. With adb I get it to find my phone but when I try to push something to it, it starts to go and then fails says no remote access or something like that. With some research everything I found saysit's because myhboot is 2.10 and with that hboot you can't flash but since my buil is the 40000 block build I cant downgrade my hboot so had to find a work around.
Dboy352 said:
Thats what I did, using root explorer and it works great. With adb I get it to find my phone but when I try to push something to it, it starts to go and then fails says no remote access or something like that. With some research everything I found saysit's because myhboot is 2.10 and with that hboot you can't flash but since my buil is the 40000 block build I cant downgrade my hboot so had to find a work around.
Click to expand...
Click to collapse
You can use adb with hboot 2.10, I do so all the time. Just when using adb, be sure to always enter in adb remount before doing anything. It would look like this:
adb remount
adb push bootanimation.zip /system/media
adb reboot
And you'd be done.
OMG where have you been. I have been searching for 3 freaking days and everyone says you cant with 2.10. You my just became my new bestfriend lmao.
Dboy352 said:
OMG where have you been. I have been searching for 3 freaking days and everyone says you cant with 2.10. You my just became my new bestfriend lmao.
Click to expand...
Click to collapse
I've been chillin' And whomever told you that needs to be slapped with a Swedish fish
And glad I could help.
Dboy352 said:
Crap, I was confused I forgot I flashed from evo deck which was cm kernel and aosp, I'm now on misfits rc1 which is like a sense/gengersense mix, really nice, but not cm. I forgot I changed to misfit therefore te cm being sense lol. My own ignorence. Thanks for the info man. I'm still learning very slowly lol.
Hey JSmurfy, if you want a custom splash page and cant get it in adb I have the file you would need to flash it as well. I finally got mine changed using it since i can't us adb to push it to the phone. Just let me know.
Click to expand...
Click to collapse
i have so many boot anims that i made flashable.. i tried everything i forgot i had asked this .. thanks to both of you for this,... im gonna try the root explorer now.. cause i hate the android logo.. its purdy and all but it aint my style..
teh roxxorz said:
You can use adb with hboot 2.10, I do so all the time. Just when using adb, be sure to always enter in adb remount before doing anything. It would look like this:
adb remount
adb push bootanimation.zip /system/media
adb reboot
And you'd be done.
Click to expand...
Click to collapse
adb on my linux pc aint workin.. but i still wanna thank you for the info
teh roxxorz said:
By the way, /system/customize/resource is for sense, aosp is /system/media.
Click to expand...
Click to collapse
ok.. final question.. do i have to move can i not just long press, copy, then paste.. i dont wanna move my file out of there.. for safe keeping.. cause i have all my folders in order and stuff
wooo hoo im convinced i have to be either the dumbest person on this site orrrrr im being over cautious.. when i went intothe system/media folder it said audio only.. no other file was in there just that folder which was a sub folder for alarms, notofications, ringtones, ui
am i missing somthing
One day, I made a uot theme for cm7 and instead of choosing cm7 for bootanimation, I chose sense. It worked. BUT when I flashed new themes with different bootanimations that I correctly chose cm7 for, it didn't work. It stayed on the sense one. Trying reflashing cm7 and then move files.with root explorer
A drop of Chuck Norris's semen was placed on Android OS. We now have CyanogenMod.
ok if i wasnt confused before.. now i definitely am.. HUHHHH
Go to system/customize/resource and delete bootanimation.zip and whatever the audio file is.. if there is one. Then try to flash your bootanimation
A drop of Chuck Norris's semen was placed on Android OS. We now have CyanogenMod.
Christ...
OK, look, for CyanogenMod-based ROMs, just put the bootanimation.zip in /data/local
No screwing around with /system, or anything. Plus, this way, you'll keep your boot animation even if you upgrade the ROM, like from 7.0.3.1 to 7.1.0.
So when it's all said and done, the ZIP file should be
Code:
/data/local/bootanimation.zip
Enjoy.
I do not know why you say this...
MOD EDIT: Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
***EDIT***
I have also tried on a HK 3g xoom (which shows MZ601 in MTP but MZ602 in fastboot). It works without any problem, and internal storage preserved untouched.
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
eddielo said:
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
Click to expand...
Click to collapse
How do you flash cwm if your device if locked? Also the purpose of the rooted boot.img is to allow you to mount your device for adb commands.
Sent from my PG86100 using Tapatalk
yeah no offense but this sounds a little sketch... I see you make a quote at the bottom asking people to report success if they try... I personally would not try this.
Unlocking and rooting is really not that hard and not very time consuming using current methods
Of course, for installing CWM, you have to unlock your device by using "fastboot oem unlock", but that will not brick your device anyway.
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Also, for the current rooting methods, it is not 100% work on some device (like the HK 3g version, which reported missing of internal storage after rooting with currently available method), I would like to see if this work on that.
Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
eddielo said:
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Click to expand...
Click to collapse
I think you missed my point. Rooted boot.img isn't used for rooting. Its used for adb commands like adb remount. Say i want to adb push a file to my xoom, ls a directory on my xoom, or adb rename system files. Those are all reason you need the rooted boot.img.
Sorry, this is not a rooting method. All what this is doing is flashing su, busybox and Superuser.apk.
There is more to rooting a device than this. You also need an insecure boot image.
I am sorry if I do not catch the real meaning of rooting a device.
What I think of rooting is to let my device, starting from everything stock, untouched, to a state that applications that need root, like Titanium backup or root explorer, works without problem.
I have tried on my two devices with this method, titanium backup works perfectly, root explorer can remount the system partition to rw and can successfully copy files and delete files from that.
The insecure boot.img image, as far as I know, provides everyone to use "adb remount" and make changes to the system directory. But my method do not need adb in copying the binaries and chmod them. You may call it flashing, but after that, su works without problem.
Please, try it first. If you think it is not a method of rooting, I am sorry about that.
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
roughneckboren said:
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Rooting has nothing to do with installing a rom. To install a rom, you just need to unlock and fastboot flash CWM. This guide in noway helps you flash a rom.
alias_neo said:
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
Click to expand...
Click to collapse
Without an rooted boot.img your recovery will get wiped out every time you boot the OS.
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
silvinoa said:
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
Click to expand...
Click to collapse
Yes and NO...
Yes this method will allow you to run titanium backup. But to use this method you have to unlock, which erases everything.
Hey guys,
I have done something stupid.
The phone.
GSM Galaxy Nexus - Android 4.0.2 (ICL53F)
Rooted. otherwise stock.
Current status - will not boot android. Will load fastboot/recovery
I was trying to change the bootanimation.
Could not do it with adb push.
So i tried by copying the .zip file to the phone.
Opened up file File expert (unsure how many use this) clicked on "internal Memory" and tried to mount for read/write.
Copied bootanimation.zip from sd card to /system/media would not paste.
Tried again. Did not paste but it did delete the stock bootanimation.zip file.
Unsure what i clicked but when i tried to open /system/media it try to "execute" it, stated that it could not find a program to do so.
Closed program.
Phone started to come up with differnt apps stating that they have stopped working.
turned off phone, reboot.
Will not load boot animation, just loads to recovery!
I think I will have to flash the stock rom to solve this.
Any help would be great.
Tiggerbits said:
Hey guys,
I have done something stupid.
The phone.
GSM Galaxy Nexus - Android 4.0.2 (ICL53F)
Rooted. otherwise stock.
Current status - will not boot android. Will load fastboot/recovery
I was trying to change the bootanimation.
Could not do it with adb push.
So i tried by copying the .zip file to the phone.
Opened up file File expert (unsure how many use this) clicked on "internal Memory" and tried to mount for read/write.
Copied bootanimation.zip from sd card to /system/media would not paste.
Tried again. Did not paste but it did delete the stock bootanimation.zip file.
Unsure what i clicked but when i tried to open /system/media it try to "execute" it, stated that it could not find a program to do so.
Closed program.
Phone started to come up with differnt apps stating that they have stopped working.
turned off phone, reboot.
Will not load boot animation, just loads to recovery!
I think I will have to flash the stock rom to solve this.
Any help would be great.
Click to expand...
Click to collapse
If this was my phone I'd find a nice rom, stock or not, and install it. I'd follow the dev's installation instructions to a "T".
You could also go this way: http://forum.xda-developers.com/showthread.php?t=1399210
Good luck.
Geezer Squid said:
If this was my phone I'd find a nice rom, stock or not, and install it. I'd follow the dev's installation instructions to a "T".
You could also go this way: http://forum.xda-developers.com/showthread.php?t=1399210
Good luck.
Click to expand...
Click to collapse
I've just flashed the stock image, luck i remembered that i did an adb back up not long ago. so just restoring that.
Than to root and flash cwm and start again. this time i'll be careful