I have a rooted T-Mobile Nexus S. In order to get the Google video app working, I needed to change the name of the "su" app to "mu". I did that by going into root explorer, telling it to make /system readable & writeable, and then renaming "su" to "mu". That worked, but now I want to go back. But I can't use the root explorer approach, since it is looking for an app named "su" to allow me to set /system to readable & writeable.
So I opened terminal emulator on my phone and and tried typing this:
mu
mount -o rw,remount /system
mv /system/bin/mu /system/bin/su
But I get the following message back after the second line:
Usage: mount[-r] [-w] [-o options] [-t type] device directory
I also tried rearranging it to the following command, but it didn't work:
mount -o remount,rw /system
I event tried the following, which still gave me the same error message:
mount /system
Any suggestions?
Related
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.
So, never really used my contacts app that much.. just pick and choose in text or in dialer. Now, I just went to try to add a phone for a buddy of mine and it force closes. I can see my list of contacts and scroll through them, but once I try to click on a name, bam, gone. If I try to add a contact, bam, gone.
Anyone know what this may be? I have deactivated google contacts sync and anything I had synced to contacts but, it still does it.
Anyone have the stock APK I can just remove or replace the old one? Or is there another fix for this?
thanks
http://forum.xda-developers.com/showthread.php?t=1396161
ok, I have all the files I need. I am having an issue trying to push from my computer the files.
Every command I try to mount the /system/app/ folder it says:
C:\android-sdk-windows\platform-tools>adb shell mount /system/app/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I have spent last 55 minutes looking on ways to do the permissions. I've done it before but I don't remember.
I need to push all the files using adb, to my phone in /system/app/. Can someone push me here?
Thanks
I've tried this:
Code:
adb shell remount rw
adb push <application_name>.apk /system/app
adb chmod 644 /system/app/<application_name>.apk
adb shell remount ro
and this under adb shell:
Code:
- open Terminal emulator:
$ su
# mount -o remount,rw /system
and this:
Code:
C:\android-sdk-windows\platform-tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\platform-tools>
and all this:
Code:
C:\android-sdk-windows\platform-tools>adb shell
[email protected]:/$ su
su
[email protected]:/# remount
remount
remount: not found
[email protected]:/# mount -o rw /system
mount -o rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[email protected]:/# mount -rw /system
mount -rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[email protected]:/# mount -rw
mount -rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[email protected]:/# mount -o rw,remount /system/app
mount -o rw,remount /system/app
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[email protected]:/#
What am I doing wrong? Thank you.
Here is what you need to do:
Code:
adb push filename.apk /data/local
adb shell
su
mount -o remount, rw /system
cd /data/local
cp filename.apk /system/app/
chmod 440 /system/app/filename.apk
Thanks Jim. Did as you say. All files are there. Contacts I can still see but when I try to add, edit or open one up it just force closes. I guess I am gonna have to just do a set back to factory.
Here are the files I pushed:
blur_yahoo.apk
YahooContacts.odex
YahooContacts.bfz
YahooContacts.bfzo
any suggestions before I restart my phone?
going back to stock.. nevermind...
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