i am trying to mount /system as rw, but keep running into errors. my tab is rooted and i have superuser elite installed. i have tried from a terminal app from the su prompt (#mount -o remount,rw /system and variations of), from adb shell, and using adb remount, but always get an error. (permission denied, are you root?)
any suggestions?
secondly, i messed up my permissions on both /system and /etc, as i had a similar issue with permissions when i was trying to get root, but forgot to note what they were previous so that i could set them back. i set them both to 755 for now, but if someone could tell me what they are suppose to be that would be appreciated.
Rusty_Gunn said:
i am trying to mount /system as rw, but keep running into errors. my tab is rooted and i have superuser elite installed. i have tried from a terminal app from the su prompt (#mount -o remount,rw /system and variations of), from adb shell, and using adb remount, but always get an error. (permission denied, are you root?)
any suggestions?
secondly, i messed up my permissions on both /system and /etc, as i had a similar issue with permissions when i was trying to get root, but forgot to note what they were previous so that i could set them back. i set them both to 755 for now, but if someone could tell me what they are suppose to be that would be appreciated.
Click to expand...
Click to collapse
Hi,
Try :
adb shell
su
mount -o rw, remount /system
It work fine for me on adb shell and terminal emulator
The command adb shell remount doesn't mount /system as rw
thanks, that put me on the write track. turns out i was getting rw the whole time, but i didnt have write permissions. did chmod 777 /system and it worked, and when i was done i put it back to chmod 755 /system
if anyone has a similar problem, the command 'mount | grep /system' is a great way to check to see if you actually have it mount as rw or not.
before this i tried a couple of the remount apps, as well as the mount as 'rw' option in es file explorer and they always fail to mount, presumably they aren't failing to mount but are running into the same permission issue and can't write
Related
Hi there,
I've got the Hero with a fully functioning 'Fresh' ROM (0.4) on (not using Apps2sd).
My question is how to push additional notification tones and ringtones to the phone in the following folders respectively:
/system/media/audio/notifications
/system/media/audio/ringtones
The reason I want to do this is to try and remove the need to have the following folders present on the sdcard:
/media/audio/notifications
/media/audio/ringtones
When I try to push the files to the phone using ADB, I get a 'failed to copy:....permission denied' error
(FYI, the command I used was: adb push /XXX.wav /system/media/audio/notifications/XXX.wav
Prior to pushing, I did issue the following commands:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system
chmod 777 /system/app
exit
exit
Tried to give as much detail as possible...appreciate any help!
dom2114 said:
Hi there,
I've got the Hero with a fully functioning 'Fresh' ROM (0.4) on (not using Apps2sd).
My question is how to push additional notification tones and ringtones to the phone in the following folders respectively:
/system/media/audio/notifications
/system/media/audio/ringtones
The reason I want to do this is to try and remove the need to have the following folders present on the sdcard:
/media/audio/notifications
/media/audio/ringtones
When I try to push the files to the phone using ADB, I get a 'failed to copy:....permission denied' error
(FYI, the command I used was: adb push /XXX.wav /system/media/audio/notifications/XXX.wav
Prior to pushing, I did issue the following commands:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system
chmod 777 /system/app
exit
exit
Tried to give as much detail as possible...appreciate any help!
Click to expand...
Click to collapse
I'm a noob, just learning the ropes of Android, but something I learned today is that you will probably need to do a chmod 777 commands to those media directories in order to get r/w access to them, that's what I would try, I hope it helps, you will want to do a chmod for media, audio, ringtones and notifications I'm guessing.
i rooted my verizon galaxy tab and i can run Root apps, but i cant move a wpa_supplicant file to my /system/root using Astro.
Is this a root issue or do i need something better than Astro? I also tried OI file manager but it just says "cannot move file here".
By default, /system is (usually) mounted read-only. You probably need to remount it read-write.
Code:
adb remount /system
adb push [path-to-file] /system/bin
If remount doesn't work, try
Code:
adb shell mount -t yaffs2 -o rw,remount /dev/block/mtdblock3 /system
I'm having trouble mounting the /system directory on my Captivate. When I try an "adb remount" I get
Code:
remount failed: no such file or directory
When I try to push my framework, I get
Code:
failed to copy 'framework-res.apk' to '/system/framework/framework-res.apk': Read-only file system
I've tried
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
and this and get "Permission Denied."
It is confusing, because before when I had this problem, the fix I linked to worked for me. Now I can't get it. Also, I can pull from the /system just fine, but can't push.
I'm definitely rooted, and have Busybox installed.
Thanks in advance!
Bump?
I have read throug tons of guides, but nothing seems to be working. I went back to stock and flashed my rom again, but no luck. Any ideas would be appreciated.
Did you type su first? It acts as if you're not root. /system is readable by everyone so you can pull, but it's only writeable by root so you can't push to it unless you're logged in as root.
I've only used adb once to root my phone so I'm not entirely sure how it should be typed in, but in a terminal you'd just type su and hit enter, then type in your remount command.
Also, for what it's worth, you can shorten it to just: mount -o rw,remount /system
Your method is fine, it's just not necessary to type it all out.
fubaya said:
Did you type su first? It acts as if you're not root. /system is readable by everyone so you can pull, but it's only writeable by root so you can't push to it unless you're logged in as root.
I've only used adb once to root my phone so I'm not entirely sure how it should be typed in, but in a terminal you'd just type su and hit enter, then type in your remount command.
Also, for what it's worth, you can shorten it to just: mount -o rw,remount /system
Your method is fine, it's just not necessary to type it all out.
Click to expand...
Click to collapse
Thanks for the reply.
If I type su in the terminal, this is what I get.
Code:
C:\Android\tools>su
'su' is not recognized as an internal or external command,
operable program or batch file. C:\Android\tools>
However, when in shell, I can get it to recognize su, but it still doesn't like to mount.
Code:
C:\Android\tools>adb shell
$ su
su
# mount -o rw,remount /system
mount -o rw,remount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#
I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now and tried all kinds of syntax, and now I'm here. What am I doing wrong? Thanks
Try:
mount -o remount,rw /system
The remount option automatically looks up the info for /system so you shouldn't have to bother with the details.
Hmm, I tried that thanks, and I still got 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'
Hmm, I can't think of any reason that wouldn't work but it sounds like your phone is locked down pretty tight. Do you know if others have been able to remount /system?
What version of busybox do you have? Maybe you could try updating it. There are one or two free busybox updater apps on the market, if you can use them.
Have you tried just 'adb remount'?
Does the mount command require busybox? Do you have that properly installed?
That requires adbd itself to be run in root mode (this is different from being rooted on the phone) & you could do that only on insecure boot image. mount/unmount both happen to come from the busybox package. It would be hard to contemplate that Motorola actually changed that but nothing would stop them from. You could try updating the busybox utility onboard your phone. There is nothing with your usage of the command - it would work the same way on my Nexus S
I do have Busybox in /system/xbin. Thinking that maybe the xbin directory may need to have the rewrite permissions, I changed its permissions to 777 using the chmod command in phone Terminal. I did the remount command 'mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system' in shell on the phone, and I THOUGHT I BRICKED! Haha, but it just turned off, and I rebooted to find that my button backlights were turned off...which I fixed with the brightness file.
Anyhow, I think I'll just use the chmod command because that seems to work. NeoA, I think you are right about the adbd to run in root mode, because I've seen discussions about that before.
Thanks for the feedback guys! At least I know I wasn't having syntax errors to say the least
So did it remount it as rw? The mount command was running before, just giving errors, but if it's running that should mean the permissions were ok.
try
Code:
busybox mount -o remount,rw /system
Fr4gg0r said:
try
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
"mount: can't find /system/app in /proc/mounts"
but
Code:
busybox chmod 777 /system
is good enough for me, for now
marlasinger said:
Code:
busybox chmod 777 /system
is good enough for me, for now
Click to expand...
Click to collapse
Using chmod to change permissions won't actually give you rw access to the system partition since it won't change whether it's mounted as read-only or r/w. To be able to run the chmod command, the system must already have been mounted as r/w or you would have received a "Read-only file system" error. It must have gotten mounted as read/write when the remount command caused a reboot. You can see how /system is mounted by just typing "mount" in adb shell which will list all of the mounted partitions.
I have a rooted ASUS Transformer running Revolver 2.1.1 (Android 3.2).
I am a programmer and want a simple programming environment for my Transformer. I purchased an app called c4droid the other day and have had issues compiling c++ code using the g++ compiler.
When I try to compile/run code, I get the messages below:
C4droid has been granted superuser permissions
Click to expand...
Click to collapse
Then....
sh: /sdcard/Android/data/com.n0n3m4.droidc/files/gcc/compile-g++.sh: Permission Denied
Click to expand...
Click to collapse
How can I get this to work? Did I root wrong?
If you face these issues, click on the link below -
http://forum.xda-developers.com/showpost.php?p=16604606&postcount=6
What about trying this:
$su
#chmod 755 /sdcard/Android/data/com.n0n3m4.droidc/files/gcc/compile-g++.sh
I'm not sure what type of FS /sdcard is on the TF, so I don't know if those permissions will a) be allowed to be set, and b) work, but I doubt if any shell script will give anything but a permissions error without having +x permissions.
By the way:: If you can't do a chmod and that is due also to a permissions error, then I'm guessing you're not really rooted or not correctly rooted.
Good luck.
hachamacha said:
What about trying this:
$su
#chmod 755 /sdcard/Android/data/com.n0n3m4.droidc/files/gcc/compile-g++.sh
I'm not sure what type of FS /sdcard is on the TF, so I don't know if those permissions will a) be allowed to be set, and b) work, but I doubt if any shell script will give anything but a permissions error without having +x permissions.
By the way:: If you can't do a chmod and that is due also to a permissions error, then I'm guessing you're not really rooted or not correctly rooted.
Good luck.
Click to expand...
Click to collapse
did.......
su then chmod 755 /sdcard/Android/data/com.n0n3m4.droidc/files/gcc/compile-g++.sh and it had no such error but if I ran both on the same line I got a "Permission Denied" error. Either way, it still provided me with the permission denied error through c4droid.
Also, I've used root checker to verify that it's rooted.
So is it a sure thing that the .sh file you're getting the error on is actually the problem or could it be something inside it that is also having a permissions error?
I guess you could easily test that by writing a single line test.sh script that does an ls or a ps command.
Code:
example:
--start of test.sh--
#!/system/bin/sh #or whatever the path is for your case
ls > /sdcard/ls.txt
-- end of file ---
# cd {pathoftestfile}
# chmod 755 test.sh
# ./test.sh
# more ls.txt # or cat ls.txt, etc.
If that doesn't give an error then something in your 'real' shell script is.
One other thing worth a shot, which I "think" I've noticed on droids in the past is to just test the script inside the /system FS and see if it does any better there. At least we know that scripts have no problems in for example, /system/xbin or /system/bin, so mount /system rw (mount -o remount,rw /system) and move the test.sh over there , fix permissions, (mount -o remount,ro /system) and cd to /system/*bin/ and ./test.sh.
You've probably tried all this already, but if not.
NOTE: Never mind: I just tested my stuff ^^ myself, and it just doesn't work in the /sdcard tree. I moved it to /system/xbin after mounting rw and it works fine without any change.
There might be some way past this, but I can't recall ever getting a shell script working while on the /sdcard share.
I tried making the shell script but I had no luck actually running it. I chmodded it without error and ran it without error but it didn't produce a .txt file so I guess it failed to run or didn't have permissions to create a file.
The app developer/creator specifies that the compiler I'm using should work fine on rooted phones. I don't have an android phone to test it. I've tried working out problems with the developer but he couldn't figure it out either.
Okay, the creator helped me out and we resolved it. Here are the steps I took to do it, for other users.-
Pre-requisites: You must have BusyBox, SuperUser, C4droid, GCC for C4droid, and a Terminal Emulator installed. You also need a rooted device.
1. Open Terminal emulator and type "su" and press enter. A superuser screen will pop up and you need to click allow.
2. Type the following lines into the terminal (one by one):
cd /Removable/MicroSD/
mkdir Android
mkdir Android/data
cp -r /sdcard/Android/data/com.n0n3m4.droidc/ /Removable/MicroSD/Android/data/
su
mount -o remount,rw,exec -t vfat /dev/block/vold/179:9 /Removable/MicroSD
/system/xbin/mount -o bind /Removable/MicroSD/Android/data/com.n0n3m4.droidc/ /sdcard/Android/data/com.n0n3m4.droidc/
3. Change the default compiler in C4droid to G++ + bionic (Root required)
4. Done
Congratulations!
I guess it was mainly the 'noexec' switch of the mount -o {} that kept things from being executable.
I didn't notice that and am glad you posted the solution and I also wasn't really aware of the use of the "mount -o bind" for dual-pathing as well.
-- Thanks.