[Q] Unable to save Language.xml - General Questions and Answers

I rooted my SGS3, and i am trying to add Hebrew (iw_il) language to Language.xml file, but i cannot save the file.
i am using ES Explore and i marked the Root Explore option.

Are you sure you got the superuser rights in ES Explore? To make sure you have them you can use a terminal emulator, if you don't know how to use it I can type the commands for you.

Superuser rights
I forgot to mantion that in ES Explorer i marked the superuser option.
i thought that this will grant me permission to modify the file.

Related

[Q] Why can't I save in /sdcard/ but can save in /mnt/sdcard?

I am a new user, and just ROM'd my Motorola Milestone XT720 using the cinci Bell's 2.2 froyo update. The major problem that I am encountering is that market aps are not downloading files correctly. For example I try to add a podcast into my que using "google listen" and I get the following error:
"Error (/sdcard/com.google.andriod.apps.listen/downloads/f09cfbe (Permission Denied)"
Now I go into supermanger's filesystem, and I notice that /sdcard/ has no permissions at all. I try to add them, but nothing happens when I do. Itself, /sdcard/ is empty.
When I plug the phone into my PC, it can access the SDcard fine. In super manager however, it appears that the directory it is accessing is /mnt/sdcard.
It seems that programs assume that the SDcard is going to be located at /sdcard/ but it is really located at /mnt/sdcard. Is there any way to redirect them?
The normal mount location is /mnt/sdcard, /sdcard is just a symlink for convenience.
Apps should use the android api to determine the sdcard location
Environment.getExternalStorageDirectory();
See http://developer.android.com/reference/android/os/Environment.html
You could readding a symlink from /sdcard to /mnt/sdcard.
Regarding you changing the permissions, do you have root? If not you won't be able to change the permissions or create a symlink.
Do I have root?
Thanks for replying Dark3n.
I think I have root access, but in supermanager explorer, the root directory reads "/(r/o)" - does that "(r/o)" mean read only?
That would make sense of my problem - since I cannot delete, rename, or change the permissions on /sdcard/.
However, I'm pretty sure I have root access. I never rooted my phone after applying the ROM. I just ran superoneclick again, and it said the phone was rooted. Supermanager explorer has superuser permissions. Am I missing something?
I have root
I just installed Root Checker by Joeykrim - it verified root access and a busybox installation.
yes r/o means read only
So what do I do about it? Is this a limitation of the file explorer I'm using or my permissions? I'm not sure how to gain more permissions than superuser.
It would be a huge help if you let me know what steps I need to take. Sorry for being a noob!
ive the same problem but it's with gscript folder.
So I downloaded ES File Explorer, then went into the settings. I turned on the root function, and then used the option below it that said something like "mount root to enable write." I clicked that. ES File Explorer didn't have a change permission feature, so I held down the home button and switched over to supermanager explorer. Now the root directory read "/(r/w)." I was then able to change the permissions for /sdcard/.
The podcasts from google listen at the NPR app I was using were still not downloading properly. I rebooted the phone. Strangely, the permissions that I had just set in the root directory, and the test directory I created in root, were both gone. I don't know how that happens.
I tried using BeyondPod, which works for downloading to /mnt/sdcard/. I wonder if that means Google Listen and the NPR app (DroidShogun) were coded to save to /Sdcard/ rather than prompting the API for a path.

[Q] Questions about Astro File Manager

I installed Astro File Manager and I have a few questions.
1) When I look in the /data directory in the phone, it shows as empty. When I do a nandroid backup, and untar the result, I find numerous folders and files in data.tar and even find the original .apk files from the Market (/data/apps)
2) I found out my phone (obtained second hand from ebay) already has a custom ROM (InsertCoin) and expect is should already be rooted. So I tried Astro File Manager to edit the /build.prop where it says "screen capture=false" to switch it to true. Astro File Manager, is claimed to have root capability in this article
http://www.freeyourandroid.com/guide...dit-build-prop
But I find the Save button disabled and cannot write out the file. Why?
Is it possible or likely to have InsertCoin and NOT be rooted? How do I tell if my device is rooted?
Try es file explorer I don't think astro can access root files. Es can root explorer can to. Just go into settings and check the root access and mount /system I think is what it is.
And yes with a custom Rom you should be rooted.
You can check by downloading terminal emulator from the market then type su if super user pops up and asks to allow your rooted
Sent from my HTC Sensation XE with Beats Audio using xda premium
another useful tool is called root checker. downloadable on the maret. one click and it will tell you if your rooted. also give you the best way to root for your device if you arent.
and yes es file manager is good for re-writing files.
wadill said:
Try es file explorer I don't think astro can access root files. Es can root explorer can to. Just go into settings and check the root access and mount /system I think is what it is.
And yes with a custom Rom you should be rooted.
You can check by downloading terminal emulator from the market then type su if super user pops up and asks to allow your rooted
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
I confirmed my device is rooted with the terminal emulator.
When I try to edit /system/build.prop (by choosing to use the text file editor) from es file explorer, it is still leaving the Save button disabled and I cannot write the file back out. I remembered to check root access and mount /system.
So, how do I edit /system/build.prop on a rooted device?
(And es file explorer shows me my /data directory.)
tk_xda said:
I confirmed my device is rooted with the terminal emulator.
When I try to edit /system/build.prop (by choosing to use the text file editor) from es file explorer, it is still leaving the Save button disabled and I cannot write the file back out. I remembered to check root access and mount /system.
So, how do I edit /system/build.prop on a rooted device?
(And es file explorer shows me my /data directory.)
Click to expand...
Click to collapse
I use Root Explorer, it has an easy mount r/w option.
If everything else fails use ADB and Notepad++ on the PC.
In essence:
adb pull /system/build.prop AN_UNEDITED_FILE
Notepad++ to edit it, making sure EOL is set to UNIX
adb shell, su, "mount /system as r/w", cd /system, cp build.prop build.prop-
adp push AN_EDITED_FILE /system/build.prop
The mount r/w comand is:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
I think that's it, I'm sure folks will correct me if I'm wrong.
tk_xda said:
I confirmed my device is rooted with the terminal emulator.
When I try to edit /system/build.prop (by choosing to use the text file editor) from es file explorer, it is still leaving the Save button disabled and I cannot write the file back out. I remembered to check root access and mount /system.
So, how do I edit /system/build.prop on a rooted device?
(And es file explorer shows me my /data directory.)
Click to expand...
Click to collapse
I just was able to change my build prop with es so I'm unsure why you cannot. I used the es note also and when finished I pressed the menu button and save was available.
Also this version of es file explorer I just used is brand new I've never used this update, it was included in the newest hd revolution sense 3.0.
I suggest just trying again. Possibly try another app or use the adb method if you think you can. Adb only looks hard really its just copy and paste.
I wish I had more advice but I can't replicate the same problem. Keep at it its just something simple were overlooking.
Sent from my HTC Sensation XE with Beats Audio using xda premium
wadill said:
I just was able to change my build prop with es so I'm unsure why you cannot. I used the es note also and when finished I pressed the menu button and save was available.
Also this version of es file explorer I just used is brand new I've never used this update, it was included in the newest hd revolution sense 3.0.
I suggest just trying again. Possibly try another app or use the adb method if you think you can. Adb only looks hard really its just copy and paste.
I wish I had more advice but I can't replicate the same problem. Keep at it its just something simple were overlooking.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
True regarding ADB, but it's guaranteed to work. The other thing is you can also do so much more with it.
As always YMMV.

[Q] /data/data appears empty in Tasker, how do I fix this?

Does this mean Tasker does not have root access? I'm trying to set up a project that copy/pastes files from one folder into another. So when I try to create the "file modified" context, I try to access /data/data to route the destination, but /data appears empty. I can access is in ES File Explorer no problem however. Apologies if I sound ignorant, this is my first android and I have a LOT to learn!
I'm using a rooted HTC One (SuperSU, not SuperUser if that matters), with 4.1.2.
SuperSU asked to give Tasker superuser permission, and I granted it. The /data folder still appeared empty, so I told SuperSU to "forget" the tasker permission. Since then Tasker hasn't ask for superuser permission....I'm not sure what the problem is here.
Having the same issue.
Did you find a solution?
Even when I copy the path from Total Commander, Tasker won't find a file in that folder.

ES File Manager - Root Access Problems or SuperSU Problems ?

I have installed this File Manager on my OnePlus One rooted and whit SuperSU 2.02 installed. On Setting i have activated the Root Explorer but no REQUEST appears from SuperSU.. it's normal ?
Whit the "Root Explorer" disactivates i can continue to navigate to root folder after click on "/"........ i thinks or it's a BUG or somewhere it's been crash on my SuperSU......
For Example i have installed other File Manager like Ghost File Manager and the Root Permission as been granded by SuperSu at every started.... like the original CM File Manager every time i start SuperSU give the access but no Es File Manger... WTF ?
Its normal, Root Explorer will ask for su access when you go into /system/ and press Mount r/w, a SuperSU option will appear afterwards.
To add to ZephiK, you don't need root access to browse the root folders. Only when you want to edit those files do you need the access.
Sent from my OnePlus One
Unless you want to browse /data, then you need root access.
Transmitted via Bacon
i thinks this "problems" like a bug it's been fixed in the recently updated version...... now the root access has beeb garanteed immediately at start of es file explorer..

Give root permission to an app by edit system/etc permission.

I want to know about something interesting.
How can I give superuser permission to any APK by make a .Xml file to give this apk root permission.
Something like this"android.permission.ACCESS_SUPERUSER – Allows an app to access ROOT"
Inside system_root/system/etc/permissions.
And then open xml and write some script and APK name.
Kindly some tell me please.
Because I cannot put my phone.
I have used all popular apps and magisk and superuser but none of them root it.
So I need this information please.

Categories

Resources