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.
Related
I am going to bring this up to the group. I am looking for the method to block the OTA updates. I enjoy my rooted Evo phones. It is a freedom I enjoy and plan to protect.
I am getting tired of pressing cancel every day. If I want to update, I want to be the one to control it.
I have been looking for a method to disable the OTA update prompts. From the board, I was able to find this.
Thread 6450334
I have tried it on my Evo with no luck
adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
# cd /etc/security
cd /etc/security
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
# ls
ls
otacerts.zip
cacerts.bks
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
Anyone know why otacerts.zip is in use and cannot be renamed. I did some different methods, but no luck.
Has someone done this before or knows of a better method of blocking the OTA updates from Sprint. I am open for a solution.
check with chuckhriczko, he successfully completed what you are trying to do. Also check out his ROM...it already has this action implemented into the ROM
techie4971 said:
I am going to bring this up to the group. I am looking for the method to block the OTA updates. I enjoy my rooted Evo phones. It is a freedom I enjoy and plan to protect.
I am getting tired of pressing cancel every day. If I want to update, I want to be the one to control it.
I have been looking for a method to disable the OTA update prompts. From the board, I was able to find this.
Thread 6450334
I have tried it on my Evo with no luck
adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
# cd /etc/security
cd /etc/security
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
# ls
ls
otacerts.zip
cacerts.bks
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
Anyone know why otacerts.zip is in use and cannot be renamed. I did some different methods, but no luck.
Has someone done this before or knows of a better method of blocking the OTA updates from Sprint. I am open for a solution.
Click to expand...
Click to collapse
I am assuming you are in the system when doing this? If so, you need to back out into recovery and do it. We currently don't have write access to the system partition while Android is running. Only in recovery. Highly recommend you look up Rom Manager on the market and use that to install the "fake-flash" recovery. It's truly the best recovery we have atm.
But you are doing it correctly except you wrote cd /etc/security. It should be /system/etc/security. The following is all you need.
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
You can ls to make sure it worked but that should do it. Reboot and voila. Never press cancel again.
chuckhriczko said:
But you are doing it correctly except you wrote cd /etc/security. It should be /system/etc/security. The following is all you need.
Click to expand...
Click to collapse
from my brief experience last night with this, /etc is a symlink to /system, so /etc or /system/etc is the exact same thing, doesn't matter.
i took the build.prop in the PC36IMG.zip which shows itself with test-keys, removed those and used release-keys, and the OTA appeared when it hadn't before!
now it downloaded the OTA but verification failed. i had to copy over ota-certs.zip from a stock EVO and those allowed the OTA update to pass verification.
if you wanted to reverse the process and prevent OTA updates from downloading, you can manually change your build.prop to show you as already having .6 software package loaded and it won't show any OTA available anymore.
it might be better to actually load the .6 software though which will adjust the build.prop, but thats my personal recommendation and not related to your request. im also running PC36IMG.zip on .1 software and also get the OTA update prompt but i plan on loading .6 software soon.
another factor to consider is the radio version also ...
joeykrim said:
from my brief experience last night with this, /etc is a symlink to /system, so /etc or /system/etc is the exact same thing, doesn't matter.
i took the build.prop in the PC36IMG.zip which shows itself with test-keys, removed those and used release-keys, and the OTA appeared when it hadn't before!
now it downloaded the OTA but verification failed. i had to copy over ota-certs.zip from a stock EVO and those allowed the OTA update to pass verification.
if you wanted to reverse the process and prevent OTA updates from downloading, you can manually change your build.prop to show you as already having .6 software package loaded and it won't show any OTA available anymore.
it might be better to actually load the .6 software though which will adjust the build.prop, but thats my personal recommendation and not related to your request. im also running PC36IMG.zip on .1 software and also get the OTA update prompt but i plan on loading .6 software soon.
another factor to consider is the radio version also ...
Click to expand...
Click to collapse
Oh I didn't know about the symlink. Good call.
Good point. I forgot to mention I did change the build number in the build.prop to be .6 instead of .1 so maybe that helps.
chuckhriczko,
I first tried it in system and no luck, then I went to recovery. I figured the active system partition was the issue.
Now I know I was in the wrong place. I will get Rom Manager and take a look at your customized ROM.
Nice job on the ROM. Love to say goodbye to those Sprint Apps.
Thanks for the quick response.
C:\Program Files (x86)\android-sdk\tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount: mounting /dev/block/mtdblock4 on /system failed: Invalid argument
# exit
exit
C:\Program Files (x86)\android-sdk\tools>adb devices
List of devices attached
HT05VHL13839 recovery
C:\Program Files (x86)\android-sdk\tools>
I get stuck there. I am rebooted into recovery mode and properly attached as you can tell from the adb devices command. Any ideas?
Problem solved:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
chuckhriczko said:
But you are doing it correctly except you wrote cd /etc/security. It should be /system/etc/security. The following is all you need.
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
You can ls to make sure it worked but that should do it. Reboot and voila. Never press cancel again.
Click to expand...
Click to collapse
Will this work on the Incredible as well?
SteelH said:
C:\Program Files (x86)\android-sdk\tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount: mounting /dev/block/mtdblock4 on /system failed: Invalid argument
# exit
exit
C:\Program Files (x86)\android-sdk\tools>adb devices
List of devices attached
HT05VHL13839 recovery
C:\Program Files (x86)\android-sdk\tools>
I get stuck there. I am rebooted into recovery mode and properly attached as you can tell from the adb devices command. Any ideas?
Problem solved:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
Click to expand...
Click to collapse
So to reverse this could I use cmd
mv otacerts.zip.bak otacerts.zip
??
Thanks.
How about:
adb shell
su
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService\$Receiver
This should disable the OTA updates without removing any files from system.
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 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?
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