SGT 2 7.0 , rooted it last night with the tutorial here, cm10
Root checker says its good and I can install root apps
I'm dieing to install a custom boot animation and the moving the zip file into system/media folder just isn't working. I believe the other suggestion was to move the zip file, it Root Explorer, into the data/local folder thats not working either
Someone help a poor noob? Hey, I'm not that bad, I got this far on my own
As far as I know, the kernel maker has to support this feature, and it's not in the stock ROM. You have to go CM or similar for this feature.
Posted from my Galaxy Tab with CM10
hmm
MultipleMonomials said:
As far as I know, the kernel maker has to support this feature, and it's not in the stock ROM. You have to go CM or similar for this feature.
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
I'm pretty sre I'm on Cm10
Sorry, didn't see that. Use ES file explorer for the copying, it has good error messages. Make sure to enable mounting system in ES settings. You may need to download "mount system rw" from Play Store. You could also download Rom Toolbox Pro, which will do it for you, but it costs something like $5.
Posted from my Galaxy Tab with CM10
meh
no luck there either and they make it look so easy haha. ah well, thanks anyways
donniegalaxy2 said:
no luck there either and they make it look so easy haha. ah well, thanks anyways
Click to expand...
Click to collapse
Okay this could be a couple of things...
First if your new animation is already named bootanimation.zip it won't let you overwrite the existing one. Delete the existing CM10 bootanimation.zip file in the system/media directory. Now you should be able to move the new animation file to the target directory.
If that doesn't work make sure ES File Explorer has the rights to make these changes.
Go to ES File explorer settings.
3rd from the bottom it says root settings.
Click on that and check all 4 things in the next menu.
Super User should prompt you allow access for ES File Explorer. Grant it.
Reboot.
Now you should be able to move the file you want to the media folder in the system partition.
After you put in the new file you may have to update the file permissions as well. I forget what they are supposed to be but I usually just check everything as read/write for all permissions options on bootanimations.
If none of that works...I dunno...come back with more specific errors you are encountering. Specific error messages, etc.
sheesh
I've done every instruction, followed them to the letter and the default boot ani won't even go away although i can find no hint of any boot ani files anywhere. it appears to function as it should, deletes the files, moves the new ones, file permissions are ok... there's just no change whatsoever, it's kind of baffling. my tablet may be possessed by he devil.
Waitwaitwait. You're saying there is NO bootanimation.zip in /system/media and it still has the stock bootanimation? Try doing a system-wide search for bootanimation.zip using CM file manager. If it does come up, note its location. If there is no bootanimation.zip in the correct folder, Android will play one hardcoded into the kernel, an image of flashing "android" text. So if there is no animation in the right place and you still see the stock CM one, you are putting it in the wrong place.
Posted from my Fascinate using XDA Premium
wowzers!
OK, so I realized that I didn't have cm file browser and did a search and finally did the nightly update. What a trip that was. It got stuck on the boot ani and wouldn't shut off or anything so I had to wait for the damn thing to run its battery dead. It starts and definatly has a different ani now. The whole new layout is messing me up bad, took me several hours just to get back online.
I have even more questions now.
BTW I'm on android version 4.1.4 now I believe.
For instance, apparently I still have all my apps installed because if I go to the store it says so and won't let me download them but I can't find them anywhere.
And some how I disabled that bar on the bottom that allows me to go back or switch windows and if I go into a program I can't get out of it because I can't switch windows.
HELP! AAAAAIIIIIIIIEEEEEEEEE!
ok
I got the window switcher bar back, it was extended desktop option. Still can't see these apps I supposedly have instslled.
Oops. Sorry about that.
Posted from my Galaxy Tab with CM10
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
If you have a titanium or cwm backup, wipe data and restore it.
Posted from my Galaxy Tab with CM10
Try using ROM Toolbox Lite, it's a free app. It worked for me.
In Lineage OS 13 it's possible...
Like mentioned above - in LOS 13 from AndroidAndi it's possible to change/overwrite the existing bootanimation.zip contained in system/media. Done here with a nice Aurora Borealis bootanimation
Related
I want this..
http://forum.xda-developers.com/showthread.php?t=1010748&highlight=Bios+animation
Where is my boot animation located on my SD card?
Help appreciated!
It is under /system/media/bootanimation.zip
You won't find it on your SDcard. You'll need an app like Root Explorer to access the file system.
You could also use ADB to push the files there if you're familiar with ADB.
dont have that.. i replace the ones in Bamf_Extras.. but it didnt work
Are you familiar with ADB?
honestly, no. I one click rooted. what can I do?
can i push using clockwork recovery?
Runn3rLogic said:
honestly, no. I one click rooted. what can I do?
Click to expand...
Click to collapse
I believe there is a free alternative to Root Explorer in Super Manager. It contains File Explorer (Root). It may allow you to copy the bootanimation.zip and mp3 file into the directory. I also am unsure if it will let you set the correct permissions on the files once they are copied. It may be something you can try.
---------- Post added at 06:41 PM ---------- Previous post was at 06:32 PM ----------
I went ahead and installed Super Manager. It will allow you to do what you need. You'll find the permissions button on the bottom menu bar if you scroll to the right.
You dont need any apps to do it for you, the bootanimation is in system/customize/resource folder you name it the name as the one in the folder and copy over it. Most if not all the developers name it bootanimation.zip the default Verizon is named VZW_bootanimation.zip I have helped people add sound to their boot animations as well this can be edited in the system/customize/CID folder in the file default. Must be edited with notepad++ or wordpad++ its one of those look near the bottom of the file for boot animation. I have become quite good at doing this by breaking it and fixing it. Things like this need to be learned the hard way.
Sent from my Thunderbolt using XDA App
Grnlantern79 said:
You dont need any apps to do it for you, the bootanimation is in system/customize/resource folder you name it the name as the one in the folder and copy over it. Most if not all the developers name it bootanimation.zip the default Verizon is named VZW_bootanimation.zip I have helped people add sound to their boot animations as well this can be edited in the system/customize/CID folder in the file default. Must be edited with notepad++ or wordpad++ its one of those look near the bottom of the file for boot animation. I have become quite good at doing this by breaking it and fixing it. Things like this need to be learned the hard way.
Sent from my Thunderbolt using XDA App
Click to expand...
Click to collapse
The correct file path is for BAMF Forever 1.0.6 is system/media/bootanimation.zip
There is also an audio file that you can replace in the same location.
I edited my CID file so it where I want it to be. I am used to default setting. Also you can copy over audio but you still need to change desc file and CID so it starts with correct animation. Should I roll my eyes back? Plus I never even said anything about BAMF forever....
Sent from my Thunderbolt using XDA App
Grnlantern79 said:
I edited my CID file so it where I want it to be. I am used to default setting. Also you can copy over audio but you still need to change desc file and CID so it starts with correct animation. Should I roll my eyes back? Plus I never even said anything about BAMF forever....
Click to expand...
Click to collapse
I assumed you were attempting to address the original posters questions about changing his boot animation on BAMF Forever 1.0.6. I didn't understand that you were merely randomly posting about how you like to edit this and that. You can roll your eyes back now!
Hey so I was hoping you could help me out. I had a bunch of stuff saved in my mini diary when I flashed 2.2 for Continuum. The new ROM didnt include this app and I lost it. I have the data saved with Titanium backup but it didnt save an apk.
If anyone has the apk that would be awesome.
download the EC07 Clean zip, unzip it and grab it out of there, along with any other stock app you need
Alright so I went out and got the apk from the EC07 clean however when I try installing it I get Application not installed.
I then tried putting it in system/apps which makes it show up however when I run the app it always force closes.
Help me out?
weird, ummmm, flash EC07-Clean? idk I've never used mini diary, just always deleted it first thing
You need to manually put it in /system/app of course, you need root for that
Sent from my SCH-I400 using xda premium
If its fc'ing on a manual push to system/apparel, id flash the clean Ron, back up the app with titanium backup, reflash Nickinson ember and restore. Just remember to wipe dalvik after each flash
I'm at war with the world, cause i ain't never gonna sell my soul. No matter what, I can't be bought or sold. - Skillet
Alright got it figured out. I noticed some of the permissions got changed when I copied it into system/app so I changed those and it now works! Thanks for the help everyone!
i'm having the same problem on my Samsung Galaxy S2 for T-mobile. I tried both ways to restore it, via Titanium Backup and manually moving the APK file to system/app. i got the same "App not installed" message.
What exactly did you change on the permission? Did you change it in Super Manager? Can you post it step by step. How do you even change the permissions? Sorry, i'm a noob here.
Thanks for any help.
I used root explorer to push it into the system/app folder. Upon pushing the apk the permissions were rwxrwxrwx
Once the apk was in the folder I change the permissions to rwxr-xr-x or
Owner: read write execute
Group: read execute
Others: read execute
To change the permissions in Root Explorer you just push/hold the apk in the system/app folder and then select permissions.
hmmm...... i did exactly as you did. changed permission the same as you had it. still no luck. i even turned off phone and rebooted. Can anyone help?
---------- Post added at 01:26 AM ---------- Previous post was at 01:21 AM ----------
i see a "MiniDiary.odex" file in my system/app folder. does that have anything to do with it?
mini diary works fine on my samsung vibrant. i just went straight to the system/app folder and copied the MiniDiary.apk and the MiniDiary.odex onto an external sdcard. inserted the sdcard into s2 phone and pasted it into the system/app folder of my samsung galaxy s2. am i doing something wrong?
Not sure if it has anything to do with it but my rom is deodexed
Sent from my SCH-I400 using XDA App
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'm pretty sure this problem could be common to all rooted devices, so I'm posting it in the general Q&A.
Basically, I would like to experiment with some build.prop tweaks I found around other XDA topics. I'm sure all of you know about the general tweaking of the said file, so I won't get into too much detail about it.
However, the changes just don't stick. They reset to default every time I reboot, as if the build.prop file never changed. So, how do I make them stick?
Phone details:
Phone: Xperia X8
ROM: FroyoPro v2.5
Kernel: Stock (can't unlock the bootloader, unfortunately)
Are you saving before exiting?
XperienceD said:
Are you saving before exiting?
Click to expand...
Click to collapse
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?
xWhiskey said:
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?
Click to expand...
Click to collapse
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.
sircrisp said:
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.
Click to expand...
Click to collapse
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed
xWhiskey said:
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed
Click to expand...
Click to collapse
I'm here to wake this thread up, because I'm having this same issue and I can't seem to find any duplicate build.prop file...
Anyone having a good suggestion for me please give it, all assistance is welcome.
Android version 4.4.4
Galaxy Note Edge
Sent from my SM-N915P using Tapatalk 2
me too have the same problem , please some dev or expert help with these problem
You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app
Are you setting the file permissions correctly as rw-r--r-- ??
[/COLOR]
flexton said:
You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
samsungrockz said:
Are you setting the file permissions correctly as rw-r--r-- ??
Click to expand...
Click to collapse
thank u for answering but sorry guys to say this , it's not the way of editing it , or the permission , when i make changes they are saved correctly and the device apply the changes in the start of the first boot after these changes are made , but during the boot (after applying the changes) the device restore the stock build.prop , so when the device finishes boot up the changes are applyed but the build.prop (i cheked it) is back to stock , this mean another boot & the changes are gone , :crying: :crying: no matter how many times or changes u do they are applyed only for the first boot after they are made
Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app
flexton said:
Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem
Kico.MMK said:
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem
Click to expand...
Click to collapse
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app
flexton said:
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
thanks for the advice , actually i did that but you know there is always something to be fixed :silly:
I have the same issue with my Vodafone Smart Ultra 6. I have root and system has read write access according to ES File Explorer. But any app that has root privileges, writes just fine without errors. However, if I close the app and load it again, or reboot, any changes are lost. So if I remove a system app using a root uninstaller it will say the app has been uninstalled. But it's still there. Drives me insane.
Exactly the same on the Smart Ultra 6.
Was hard enough to get it rooted but seems any changes to the system partition/file system just don't stick. Short of putting a custom rom on it I'm stuck for ideas.
I'd love to know what causes this behaviour.
Any updates here? I just started running into this after updating to the 7.1.1 January factory image on my 5x. The weird thing is when i reboot in TWRP it all looks fine but when I look at my system directory from Android the boot-from-recovery.p is still there and my build.prop changes aren't...push TWRP again, boot to recovery read build.prop and it's my edited version. wtf?
I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.
I have the same problem: after reboot all the changes are gone....
ashd63 said:
I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.
Click to expand...
Click to collapse
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.
ullie4404 said:
I have the same problem: after reboot all the changes are gone....
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.
Click to expand...
Click to collapse
Did you ever find the solution to this? I'm having the same problem..all changes reset with every reboot and the file's permission is like -rw-----
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.