Database Info

[Q] Help needed for bootanimation

Dear all,
I have my eee pad installed with the latest Revolver Rom. I would like to install a custom boot animation. I searched a bit and would like to use ES file manager to create a folder: \Data\Local.
Now, the Data folder is already there but when I try to create a folder, it tells me that I cannot create a folder. I can also not replace the bootanimation under \System\Media.
Is there any way I can get write access here?

You need to allow ES File explorer root access.
Both the data/local and system/media is already there, no need to create any folder. You could also ADB push the file to the location

You can also try an application called Root Explorer (from the market), which works for me. But I've never really used ES File explorer much (there was something I did not like about the UI), so I cannot compare.

Solved!
Thank you for the replies. Indeed, needed to give root access to ES File Eplorer through options in the program.
Cheers!

Question related to Android file permission

I used ES File Manager to edit a .ini file in data/data/org.gaeproxy (a proxy app) and then changed its permission from rw-rw-rw- to r--r--r-- after saving it.
After I opened the app, I checked the property of the .ini file using ES File Manager and was shocked to find the Last Modified field was updated to the right moment when I opened the app. And the editing I made to the file was gone. It seemed to me that the app had overrided the read-only permission of the file and edited its content.
But then I supprisingly found that I was able to modify the same file and save the change while it's still read-only. How is this even possible?
Both ES File Manager and the .ini file have been granted superuser permissions. Is this a possible cause? I've found this annoying problem across different devices and different ROMs. So I think there might be something I need to know about the file permission system in Android.
How can I make this .ini file truly read-only even to the app using it?

System "semi" Writable?

I recently Wiped my Phone completely and decided to Re-Flash Viper 1.2.1.
I noticed a problem prior to re-installing but thought nothing of if since it wasn't crucial at the time.
In Root explorer, I am able to delete [i normally delete boot animations] system files but not add where I need to add. Example, I wanted to add a ringtone to my system/media/ringtones folder. I normally [for the last six years] could just copy and paste such files using a root file manager.
However, when I any these files to for example /system/customize/resource/ it doesnt add it. BUT IT DOES rename the file and save it under a dif folder.
Example. Tried copying-copy to-moving to "androidtwirp.mp3" from sdcard to /system/media/notifications and a message pops up saying"notificationsandroidtwirp.mp3 successfully copied-moved to" and it saves notificationsandroidtwirp.mp3 to /system/media/ and it stays there. retrying from that location only results in "notificationsnotificationsandroidtwirp.mp3".
So not only does it rename the file but it saves it in the wrong location. I am at a loss for word. I tried the basics to tryand fix this but i cant seem to hit it on the head.
Thanks!
Edit: Not updating Super SU app, file explorer seems to have worked. Will attempt to duplicate problem to see what actually caused.it.

FOUND IT!
Updating my ES File explorer broke my system writing ability. DO NOT UPDATE is because when you do...
Any file you move, copy/paste to the system will not work properly.
This first happened when I tried to copy and paste a boot animation after I updated ES root explorer. It would rename whatever file i was trying to paste/move/copy over and save it under a sub folder.
example.
copying a ringtone [i.e. androidtwirp.mp3] from SDCard to System folder, the path is /system/media/audio/ringtones/ and it would rename it "ringtonesandroidtwirp.mp3" and save it under /system/media/audio/.
So basically not only was it renamed [which i didnt want it to be] but it would save it to the folder before the actual folder i needed it to be in, plus it would corrupt the file deeming it useless.
moving "ringtonesandroidtwirp.mp3" into the correct folder would only result in "ringtonesringtonesandroidtwirp.mp3"
this happened across the board with all files being moved around
The ES File Explorer version 1.2.1 comes with works flawlessly so don't update it.
I uninstalled ES [also any folders in SDcard related to it] and downloaded JRummy's root explorer and everything is back to normal except i have to reboot the phone to see files [like ringtones and notifications] that i added to the system.

I think it has something to do with our devices having an unlocked bootloaader, but still S-ON. There's S-OFF in the Dev section now if you really need to write to the system folder a lot.
I came from the Vibrant so I know what you're going through

Yeah, im on a low hboot so s-off might not be in my plans since I can practically flash what I want but it was ES file explorer, when I updated the apk the root permissions broke when writting to the system. I emailed the dev and they said they'd have it fixed on the next update.
echo en Android

[Solved] Cant copy .apk to system

Hey guys,
Im having issues copying apk files to the system/app folder, I have tried three different file managers(root browser, root explorer, file explorer). I mount system set it to r/w and when i try to copy or move the apk file i get operation failed/ cannot copy file. I tried copying the same apk (motogallery) to my nexus 7 (android 5.0) it worked fine. However with my nexus 5 its a no go. I'm running stock lollipop rom with root.
Thanks
edit: figured it out had to copy apk to priv-app folder instead of system/app. Strange on the nexus 7 file was copied to system/app and worked just fine.

[HELP] I need build.prop

I have a broken build.prop for my S6: can someone be so generous to send me this file from G920FXXU1AOE3_G920FITV1AODQ_G920FXXU1AOE3_HOME ? I'm not able to extract following this tutorial http://forum.xda-developers.com/showthread.php?t=2294909 (ext2explore wasn't able to open the system.img)

Use a root enabled file explorer like Root Explorer or ES File Explorer to open the rom.zip you are running. Go to /system and extract build.prop, then go to the folder where the file was extracted to (I use Root Explorer which extracts to /sdcard0/storage/SpeedSoftware/Extracted). Copy the extracted build.prop to your phone's /system and overwrite the existing build.prop. Make sure the permissions are rw-r--r-- and reboot.
Protip: After flashing a new rom, backup the original build.prop before making any changes or flashing any mods. Save it as "build.prop.original". That way, you will always have a backup copy of the original file. Some file explorers (like Root Explorer) will automatically backup files when you edit them, but they append ".bak" to the existing file. So if you edit build.prop more than once, your original "build.prop.bak" is overwritten, and the backup is no longer the original file. However, if you save the original as "build.prop.original", it never gets overwritten.

It works! Thank you!
Inviato dal mio SM-G925T utilizzando Tapatalk