I used the post to install the one click root for the samsung epic 4g (sprint), and it appears to have worked. However - after entering root explorer, only some of the directories allow me to edit files. I click the remount as r/w button but nothing happens. Any thoughts?
sedric1 said:
I used the post to install the one click root for the samsung epic 4g (sprint), and it appears to have worked. However - after entering root explorer, only some of the directories allow me to edit files. I click the remount as r/w button but nothing happens. Any thoughts?
Click to expand...
Click to collapse
Are you sure you granted root permissions to root explorer when it first ran? Run the superuser app from the app drawer and see if root explorer is on the list of apps that are allowed root permission.
I just tried v2.17.2 and it works fine. I tried changing the permissions on /system/xbin/busybox, it said filesystem mounted ro, then I press the mount rw button and redid the permission change, this time it worked no problem.
Thanks for your response-
yes, when i ran root explorer it asked if i wanted to grant superuser and i said yes. some folders allow it to remount, but - say the /system/bin folder - it doesnt allow it at all.
for further background, i used the automated instructions here for my root:
http://forum.xda-developers.com/showthread.php?t=1342728
i did option A like 5 times and also did option C (as i have EK02).
When opening root explorer it tells me that i have super user permissions. one thing to note- if i go to /system/xbin, i do not see a busybox directory. is there something else i should be installing?
in fact, i cant mount anything under the system directory or sub directories, but above that, i was able to change to r/w mode. i could also mount the /vendor directory right beside the /system directory...
If you were able to remount "/" as r/w then the problem isn't with root. That is basicly an "I'm a little bit pregnant situation" Either you are or you aren't.
Now if you weren't able to get root in the first place, then I'd look at the root.
As to busybox, there is no directory. There should be a file /system/xbin/busybox Also there should be a bunch of symlinks from various apps it supports to busybox.
I see - yea i did validate that busybox is not allowing for a mount or any type of change on that file/directory including busybox but the file is present. any suggestions on what else may be locking down this system directory?
I don't know if root file explorer is implemented it's own concept of ro/rw to protect you from making mistakes or it is using the system facilities. If it is using the system facilities, then once you remount /system as rw, then everything under /system is automatically rw. It is all the same partition.
I would try it from "adb shell" (do not type $ or # symbols)
Code:
$ su
# mount -o remount,rw /system /system
# cd /system/xbin
# chmod 755 busybox
If it lets you do that with no errors, then you have remounted /system/xbin as rw and the problem is with root file explorer. For that, you'd have to check with them or someone more well-versed in why that might be failing.
i appreciate your help
I went off googling the adb stuff/installed it and java's jdk stuff. then figured out how to run that adb shell stuff and validated that it worked (permissions were changed in places that this app didnt allow). knowing that the problem is actually with root explorer helps a ton.. as I just assumed it was working
Related
Hi all,
couple of questions I hope somebody can answer for me ?
1. If I connect my Hero phone to my XP PC and run adb shell and then SU so I get the # prompt, what user am I logged in as ? is it root ? I tried whoami command but it was not a recognised command.
2. What is special about the system directory, because if I try and do
#chmod 777 system
I get this error: Unable to chmod system: Read-only file system
but no problem if I do same command to the sys directory. Both sys and system have same file permissions:
drwxr-xr-x root root 2009-08-27 03:51 system
drwxr-xr-x root root 1970-01-01 01:00 sys
so what makes the system directory a Read-only file system ?
I hope this makes sense, I'm only just starting to dabble with this linux stuff.
The answer to the first question is you are indeed logged in as root, su will(...should...) log you in as root for the entire session.
with # you are root. the id command works.
/system is the "rom" part, it should not be changed and therefore is usually mounted RO. you can remount it RW with the usual mount options or adb remount. why would you want to change the permissions of the folder? i don't think it's good idea tbh, you should not mess with system files unless you know what you are doing.
kendong2 said:
with # you are root. the id command works.
/system is the "rom" part, it should not be changed and therefore is usually mounted RO. you can remount it RW with the usual mount options or adb remount. why would you want to change the permissions of the folder? i don't think it's good idea tbh, you should not mess with system files unless you know what you are doing.
Click to expand...
Click to collapse
OK, thanks for explaining. tbh I was just seeing what I could and could not do, I will take your advice and not mess with the system files any more.
So the read only thing, is to do with mounting rather than file permissions from what you say. I think I need to read up on the subject.
Cheers
gudge said:
OK, thanks for explaining. tbh I was just seeing what I could and could not do, I will take your advice and not mess with the system files any more.
So the read only thing, is to do with mounting rather than file permissions from what you say. I think I need to read up on the subject.
Cheers
Click to expand...
Click to collapse
do whatever you like, i learned most of what i know by trial&error just be prepared to break it, never go without a backup...
Hi all, i've been trying to mount my filesystem as RW, but all the commands that i searched failed! Can anyone enlighten me?
commands i used:
Code:
ADB Remount
and i get operation not permitted
Code:
ADB shell
su
mount -o remount,rw ext4 /blah/blah/blah /system
this works, but i cannot push files from my mac to the phone! OMGOMGOMG.
Might be easier to use Root Explorer. It's basically a file explorer that lets you make system files rewritable.
aameerp said:
Might be easier to use Root Explorer. It's basically a file explorer that lets you make system files rewritable.
Click to expand...
Click to collapse
Yeah in the end i succumbed to UI and used ES to do it. But i wanna understand what went wrong! So someone, please tell me!
I went throught the process to root and install unlocked bootloader after upgrading from stock hc to stock 14 ics build. Everything seemed to work well untill trying to install CWM.
EVerytime I rebooted to try to get into CWM I got the old recovery. It seems I had to rename install-recovery.sh. However when I tried to rename with term emu apparently the easy root method no longer works and system remained ro. In order to resolve I had to mount -o remount, rw /system/ then rename install-recovery, then re-run the cwm script.
paronowitz said:
I went throught the process to root and install unlocked bootloader after upgrading from stock hc to stock 14 ics build. Everything seemed to work well untill trying to install CWM.
EVerytime I rebooted to try to get into CWM I got the old recovery. It seems I had to rename install-recovery.sh. However when I tried to rename with term emu apparently the easy root method no longer works and system remained ro. In order to resolve I had to mount -o remount, rw /system/ then rename install-recovery, then re-run the cwm script.
Click to expand...
Click to collapse
I'm confused. Even if the root script from ZN was installed successfully which I can confirm and many other members who have ran this rom have confirmed, you would still need to mount /system some how. Whether it is from rootexplorer, es file manager, or directly from the terminal emulator as you did. That script roots the tab and makes /system/ mountable in various apps it doesn't make /system/ RW constantly. I'm glad you got it taken care of though.
Yup that what I'm saying. I started with a freshly clean install. I tried running the an method several times. I was able to install unlocked boot loader howver I had no rw access to /system unless I manually remounted. Every time I reboot I have to remount again
Well I would think BEFORE updating to .014 you should remove bootloader.blob and anything else that relates to changing recovery from the .014 update before attempting to flash. Otherwise you would end up with a stock bootloader again.
don't forget to remove the installrecovery script from the etc folder too just a fyi
@paronowitz
You might want to try rooting again. I'm currently on Zeronull's release, and I can mount /system fine from root explorer without having to mount it first through terminal emu. I've gotten into the habit of re-rooting roms on the tab.
I had not problem accessing /system. I could not change or delete anything in is specifically the install_recovery.sh without remounting it rw
if memory serves me right the install package for twrp removed the install recoveryinstall script.
paronowitz said:
I had not problem accessing /system. I could not change or delete anything in is specifically the install_recovery.sh without remounting it rw
Click to expand...
Click to collapse
Well I apparently had no problems with root, until I tried to edit anything in /system. After re-rooting I could mount /system, AND edit/delete install_recovery.sh.
The OP had said he was renaming install-recovery.sh from the terminal emulator. Like I said in my post earlier the root script doesn't make /system/ rw constantly and the terminal emulator does not auto mount /system/ rw. So even if the script is working, you would have to use the same commands if you are using the termnal to rename. Also, by making /system/ rw you are making /system/etc rw, and this allows you to edit the file you were attempting to edit. So when I am referring to mounting /system/ as rw, we are talking about the same thing. /etc/ is a shortcut to /system/etc.
paronowitz said:
I went throught the process to root and install unlocked bootloader after upgrading from stock hc to stock 14 ics build. Everything seemed to work well untill trying to install CWM.
EVerytime I rebooted to try to get into CWM I got the old recovery. It seems I had to rename install-recovery.sh. However when I tried to rename with term emu apparently the easy root method no longer works and system remained ro. In order to resolve I had to mount -o remount, rw /system/ then rename install-recovery, then re-run the cwm script.
Click to expand...
Click to collapse
It sounds like you may want to just execute the commands by hand. The script will make assumptions that may not hold true for your current configuration.
Look HERE
Check out the Eew245's root method. It give you the most control since you do it by hand. If you don't have adb you can use the one supplied in the ZeroNull easy unlock package(careful to not run the scripts at the wrong time and such though). Anyway Im out of time today. It sounds like as others have said you probably just need to
su
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.BAK
Then reflash cwm if you overwrote recovery when you updated.
NoSudo said:
It sounds like you may want to just execute the commands by hand. The script will make assumptions that may not hold true for your current configuration.
Look HERE
Check out the Eew245's root method. It give you the most control since you do it by hand. If you don't have adb you can use the one supplied in the ZeroNull easy unlock package(careful to not run the scripts at the wrong time and such though). Anyway Im out of time today. It sounds like as others have said you probably just need to
su
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.BAK
Then reflash cwm if you overwrote recovery when you updated.
Click to expand...
Click to collapse
That's exactly what I had to do.
edit - miss-post
aruangra said:
This approach works with non-smart keyboards.
1. Install your preferred keyboards from Market
2. Use ES file explore (with Root feature and RW mount enabled in the advanced setting) or use Root Explorer to copy the keyboard .apk file from /data/app to /system/app
3. Reboot and select the keyboard by pressing and holding at any text input box.
4. (optional) Sideload and install "Nookcolor Tools" from http://forum.xda-developers.com/showthread.php?t=868366. You will have an option to set keyboards.
So far this method does not work with
- SlideIt
- Thumb keyboard (thanks fr4nk1yn)
Click to expand...
Click to collapse
I have neither a /data/app folder nor a /system/app folder... My KF is rooted (I'm successfully using the Google Play store, permanent Live Wallpapers and Avast Mobile Security Anti-Theft with root access) so I don't really understand why I am missing those folders. I can even create them without any complaints by Windows, there are no hidden objects. Did the 6.3.1 update change the folder structure?
Can anyone help me?
Okay, while I have still no possibility to access the root level via Windows, I managed to access it with the ES File Explorer (I had to change a setting to make the root level visible).
Now I have a /system/app folder and a /data folder - but unfortunately no /data/app folder; the /data folder is empty!
Furthermore I cannot copy APK-files in the /system/app folder. I get informed that the copy process failed, if I try to. Shouldn't normally a popup of the Superuser app show up with the option to grant root access?
I'm looking forward to any help! Thanks in advance.
I don't like to push threads, but... is there really no one able to help me?
When all else fails, reinstall the ROM.
Uhm, I did not install a custom ROM. Or do you mean, that I should reinstall the stock ROM?
Oh, in that case, I'm sure its your ES File Explorer that is messed up. If you have Terminal Emulator, you can check to see what directories you actually have. Enter:
ls /system
...and...
ls /data
I'll be willing to bet you they are still there.
$ export PATH=/data/local/bin:$PATH
$ ls /system
lost+found
app
bin
build.prop
etc
fonts
framework
lib
media
tts
usr
vendor
xbin
$ ls /data
opendir failed, Permission denied
$
That's what Terminal Emulator says...
How is it possible that I can open /system without having permission for /data?
Type :
$ su
$ ls /data
Envoyé depuis mon GT-I9000 avec Tapatalk
Thanks a lot! I now can see the contents of /data via Terminal Emulator.
But how can I grant superuser permission to ES File Explorer?
Hi guys :laugh:
I've successfully rooted my table, installed Supersu, TWRP and even tried the CM11 ROM in it.
The main problem is that I want to add/change some files on the /system/usr/keylayout folder so I can configure correctly my xbox 360 wireless controller (I'm having the spin buggy thing on some games).
But whenever I try to make changes in that folder using "ES File Manager" (granting it SU) It just pops up "Try again, this folder is read only"
I tried changing it through the Terminal Emulator through these steps:
su
cd /system/usr/keylayout/
mount -o remount,rw /system (or mount -o rw,remount /system its the same)
Didn't make any difference...
Can anyone help me really hard here?
Thanks guys :highfive: (and girls)
edit:
I'm now with the LG Firmware 50020D and android vers 4.4.2 (rooted)
up
anyone?
install ES File manager via Play store
You can activate Root browser in ES File manager. You need to click on the root browser settings within ES File manager, and mount /system/ as RW