I would like some tips on getting read-write access on my nexus s /system/media directory.
Im using Windows 7 x64 and i have seen a lot of tutorials but im not sure if they are for the correct model, as i noticed
"ext3"
"ext4"
Any help would be appreciated and thanked !!
XDA_Badman said:
I would like some tips on getting read-write access on my nexus s /system/media directory.
Im using Windows 7 x64 and i have seen a lot of tutorials but im not sure if they are for the correct model, as i noticed
"ext3"
"ext4"
Any help would be appreciated and thanked !!
Click to expand...
Click to collapse
Root.
You can then either remount manually:
Code:
mount -o remount,rw /dev/mtdblock3 /system
or flash an insecure boot image and then you can use adb remount.
Alternatively you can use something like Root Explorer if you want a GUI
I will try that , thanks alot also i tried 'Root Explorer' but it would not paste the file i needed.
EDIT!!
I tried it manually and i got this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # mount -o remount,rw /dev/mtdblock3 /system
mount -o remount,rw /dev/mtdblock3 /system
mount: mounting /dev/mtdblock3 on /system failed: Invalid argument
~ #
XDA_Badman said:
I will try that , thanks alot also i tried 'Root Explorer' but it would not paste the file i needed.
EDIT!!
I tried it manually and i got this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # mount -o remount,rw /dev/mtdblock3 /system
mount -o remount,rw /dev/mtdblock3 /system
mount: mounting /dev/mtdblock3 on /system failed: Invalid argument
~ #
Click to expand...
Click to collapse
adb shell first. It looks like you are still in the terminal based on the ~ prefix
XDA_Badman said:
I will try that , thanks alot also i tried 'Root Explorer' but it would not paste the file i needed.
EDIT!!
I tried it manually and i got this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # mount -o remount,rw /dev/mtdblock3 /system
mount -o remount,rw /dev/mtdblock3 /system
mount: mounting /dev/mtdblock3 on /system failed: Invalid argument
~ #
Click to expand...
Click to collapse
adb shell first, then su. It looks like you are still in the terminal based on the ~ prefix You have root already, right?
krohnjw said:
adb shell first, then su. It looks like you are still in the terminal based on the ~ prefix You have root already, right?
Click to expand...
Click to collapse
Im sure i have root access,
1: I rooted it myself
2: I use root checker on my device
3: I was in 'adb shell' before, when i first tried it
But on 'Root Check' (on my device) it shows the following message in green colour text,
Congratulations! You have root access!
Standard su binary location:
ls:/system/bin/su: No such file or directory
Standard su binary location:
-rwsr-sr-x 1root root 26336 Aug 1
2008 /system/xbin/su
Alternate su binary location:
ls: /sbin/su: Permission denied
Root user id:
uid=0(root)
Root group id:
gid=0(root)
MODERATOR PLEASE DELETE
1: I forgot to change my root dir to /system/xbin/su
2: In root explorer i didnt see the 'Mount As' button lol
Related
I updated my rom and there are some omitted apps that I would like to get back into system/apps/ for example VoiceDialer.apk, but I cannot seem to get them back on. I am using Fresh Rom 0.4 and the phone is obviously rooted. maybe I am doing something wrong in adb shell but I keep getting one of 2 different erors. Either permission denied or adb not found. Thank you in advance for your help.
flaav8r said:
I updated my rom and there are some omitted apps that I would like to get back into system/apps/ for example VoiceDialer.apk, but I cannot seem to get them back on. I am using Fresh Rom 0.4 and the phone is obviously rooted. maybe I am doing something wrong in adb shell but I keep getting one of 2 different erors. Either permission denied or adb not found. Thank you in advance for your help.
Click to expand...
Click to collapse
1) Permission denied - make sure that when you do an adb shell, you're root (have the # prompt) and make sure you've mounted /system as rw (adb remount)
2) adb not found - make sure there's only one adb.exe on your computer and that it's the one from the SDK and that the SDK's /tools directory is in your path (to be safe, you can always just run adb from that directory)
jmanley69 said:
1) Permission denied - make sure that when you do an adb shell, you're root (have the # prompt) and make sure you've mounted /system as rw (adb remount)
2) adb not found - make sure there's only one adb.exe on your computer and that it's the one from the SDK and that the SDK's /tools directory is in your path (to be safe, you can always just run adb from that directory)
Click to expand...
Click to collapse
1. the procedure I used is this: from the cmd prompt in the androidsdk/tools/ directory:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system/app
# adb push VoiceDialer.apk system/app
but its a no go. Can't understand why.
BTW, I have the VoiceDialer.apk file in the androidsdk/tools folder just to make the push easier.
Ok, here is a screen shot from my command prompt window. I know someone knows what the hell I'm doing wrong. Just wanna get the damn voice dialer back on my phone. Please help, thank you.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Barry>cd \
C:\>cd androidsdk\tools\
C:\AndroidSDK\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# adb push VoiceDialer.apk /system/app/
adb push VoiceDialer.apk /system/app/
adb: not found
#
you cant do adb push while in shell ($ or #). Exit out and just try tying the adb push
goku14238 said:
you cant do adb push while in shell ($ or #). Exit out and just try tying the adb push
Click to expand...
Click to collapse
When I do that I get permission denied or something to that effect.
Yeah there's a post about this in the Fresh thread.
The most straightforward way is this:
Reboot to the recovery partition.
adb shell into the phone.
Issue the following command to mount the system partition:
mount -t yaffs2 /dev/block/mtdblock3 /system
Type exit to exit the shell.
Then do:
adb push c:\directory-with-the-apks /system/app
jonnythan said:
Yeah there's a post about this in the Fresh thread.
The most straightforward way is this:
Reboot to the recovery partition.
adb shell into the phone.
Issue the following command to mount the system partition:
mount -t yaffs2 /dev/block/mtdblock3 /system
Type exit to exit the shell.
Then do:
adb push c:\directory-with-the-apks /system/app
Click to expand...
Click to collapse
Thank-you, I will give it a try.
Can anyone guide me along with this I was able to successfully root my droid2 yesterday now i wanted to add the FMRadio capability and i need to remount but every time i try to i get the error message "remount failed: Operation not permitted" as you can see i have the admin but it still won't remount is there something I'm missing?
C:\sdk\tools>adb shell
$ su
su
# ^C
C:\sdk\tools>adb remount
remount failed: Operation not permitted
also tried this
C:\sdk\tools>adb remount r/w
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
I'm having the exact same issue. I'm trying to install superuser per their instructions though. adb says that the remount operation is not permitted.
Well I was able to root it and install superuser so you would think i could get back in and remount the thing.
I just had this problem. Remount it in the shell after you do the "su" command.
Like this:
C:\sdk\tools>adb shell
$ su (make sure your phone is unlocked during this part, it should pop up asking for Super User access)
# mount -o remount,rw /dev/block/mtdblock3 /system
now you are remounted and in read-write mode...when you are done, remount again but change the "rw" to "ro".
like this:
# mount -o remount,ro /dev/block/mtdblock3 /system
noob stuck as well until.
I am on day 6 of having my D2 after trying all the other posts on a whim I tried to Doroot again. was going slow as ???? then changed "PC Mode" to "Charge Only" mode...Everything worked great...FM Radio works well but Only Mono with not so great reception.
Good Luck.
I am newbie of Android user, my phone is Samsung Spica I5700 (firmware I570EXXJG2). I tried SuperOneClick 1.6.5 to root my phone and the result was OK, I could see Superuser in my phone, but some applications on the Maket that request root did not run correctly. I use ADB to mount the file system as read and write to change something. Here is result
adb devices
List of devices attached
57001541c892 device
adb remount
remount failed: No such file or directory
adb shell mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl6 /system
mount: Operation not permitted
adb shell mount -r -w -t rfs -o nosuid,nodev,xattr,check=no /dev/stl6 /system
mount: Operation not permitted
adb shell
$ su
Permission denied
$ mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl6 /system
mount: Operation not permitted
$ mount -r -w -t rfs -o nosuid,nodev,xattr,check=no /dev/stl6 /system
mount: Operation not permitted
So I can not do anything. Please indicate me how to use ADB to remount the file system as read and write.
Sorry for my English, I am from South East Asia.
Try remount in the market
zachsx said:
Try remount in the market
Click to expand...
Click to collapse
Thank you, but there are no apps on the market that can mount file system as read and write.
Any body can do that, please help.
Sorry for my English
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.
Hey, I installed BT5 arm on the Motorola Xoom wifi and i would like to know how to completely remove it from my device. My device is rooted and i have tried to delete the whole BT5 file with astro file manager and absolute file manager but neither of them worked. I was wondering if anyone knows another way of doing it.
I tried deleting it with commands in terminal emulator but its a read only file. Wouldn't chmod help with that? If so how would i use it?
jimmothycharles said:
I tried deleting it with commands in terminal emulator but its a read only file. Wouldn't chmod help with that? If so how would i use it?
Click to expand...
Click to collapse
Go read the backtrack 5 thread. There is a link on how to remove it. That really should be the first thing you check before asking
ok thanks, ill do that the next time i have a problem
I couldn't find it. I think it might be a tiamat BT5 img and i have the remover tool but im not quite sure how to use it. I just flashed it like i would do with a rom but it says installation failed. what would i do to fix that?
jimmothycharles said:
I couldn't find it. I think it might be a tiamat BT5 img and i have the remover tool but im not quite sure how to use it. I just flashed it like i would do with a rom but it says installation failed. what would i do to fix that?
Click to expand...
Click to collapse
Common knowledge - system must be set to RW
Here is an alternate route- manually
How To:
ADB Shell Folder Removal - (we will use BT5 as an example)
++++++++++++++++++++++++++++
1. Connect Xoom to pc
2. Boot into recovery
3. Toggle to internal storage as /sdcard
4. mount /data
Enter adb shell via pc
(cd to file location) in this case BT5, is in the sdcard directory
Code:
Code:
cd /sdcard #
(once typed, you will be at.... /data/media prompt)
if after the above command and you are not at the /data/media prompt start over)
Code:
Code:
rm -r BT5
(BT5 is the stubborn Folder)
*Side note ... This works for any other stubborn folder that you want to delete as well...
USE AT YOU OWN RISK - MAKE SURE YOU DO A BACKUP FIRST
If this was helpful Hit The Thanks!
it didnt work it said that rm failed for BT5, permission denied
jimmothycharles said:
it didnt work it said that rm failed for BT5, permission denied
Click to expand...
Click to collapse
Come on now, lol Your device must be set to rw. Google can guide you.
Mjamocha said:
Come on now, lol Your device must be set to rw. Google can guide you.
Click to expand...
Click to collapse
ok well this is what i got when i tried to do that.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd C:\Users\josh\Desktop\xoom files\BT5
C:\Users\josh\Desktop\xoom files\BT5>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ # cd storage/sdcard0/0/0/0
cd storage/sdcard0/0/0/0
[email protected]:/storage/sdcard0/0/0/0 # ls
ls
Android
BT5
Box
DCIM
Download
Evernote
Pictures
SELog.txt
Video
airdroid
goodies
goomanager
tmp
[email protected]:/storage/sdcard0/0/0/0 # rm -r BT5
rm -r BT5
rm failed for BT5, Permission denied
255|[email protected]:/storage/sdcard0/0/0/0 # rm BT5
rm BT5
rm failed for BT5, Is a directory
255|[email protected]:/storage/sdcard0/0/0/0 # cd
cd
[email protected]:/data # exit
exit
C:\Users\josh\Desktop\xoom files\BT5>adb shell
[email protected]:/ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
[email protected]:/ # cd storage/sdcard0/0/0/0
cd storage/sdcard0/0/0/0
[email protected]:/storage/sdcard0/0/0/0 # ls
ls
Android
BT5
Box
DCIM
Download
Evernote
Pictures
SELog.txt
Video
airdroid
goodies
goomanager
tmp
[email protected]:/storage/sdcard0/0/0/0 # rm -r BT5
rm -r BT5
rm failed for BT5, Permission denied
255|[email protected]:/storage/sdcard0/0/0/0 # rm -rBT5
rm -rBT5
rm failed for -rBT5, No such file or directory
255|[email protected]:/storage/sdcard0/0/0/0 # chmod 777 BT5
chmod 777 BT5
[email protected]:/storage/sdcard0/0/0/0 # rm -r BT5
rm -r BT5
rm failed for BT5, Permission denied
255|[email protected]:/storage/sdcard0/0/0/0 #
I looked up on google how to mount system rw and thats where [email protected]:/ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system came from. then i tried rm -r BT5 after that and it was still denied. so i tried to
do chmod 777 BT5 to give all permissions and then when i tried to remove it again it was still denied.
I looked up the permissions of the file and its set to rwxrwxr-x. so chmod apparently didn't work