Without doing much talking I am just pasting the shell session:
Error is in red font
Code:
C:\Users\Downloads\one click root exploit>adb shell
# su
su
[COLOR="red"]# remount rw
remount rw
[: not found
[: not found
for mounting /system as read/write or read-only
usage: remount rw -or- remount ro[/COLOR]
# exit
exit
# exit
exit
C:\Users\Downloads\one click root exploit>
sunrocket said:
Without doing much talking I am just pasting the shell session:
Error is in red font
Code:
C:\Users\Downloads\one click root exploit>adb shell
# su
su
[COLOR="red"]# remount rw
remount rw
[: not found
[: not found
for mounting /system as read/write or read-only
usage: remount rw -or- remount ro[/COLOR]
# exit
exit
# exit
exit
C:\Users\Downloads\one click root exploit>
Click to expand...
Click to collapse
I'm not sure why that is happening, I didn't use a one click to root but you can always use the command: mount -t rfs -o remount,rw /dev/block/stl9 /system
to mount /system as read,write.
sunrocket said:
Without doing much talking I am just pasting the shell session:
Error is in red font
Code:
C:\Users\Downloads\one click root exploit>adb shell
# su
su
[COLOR="red"]# remount rw
remount rw
[: not found
[: not found
for mounting /system as read/write or read-only
usage: remount rw -or- remount ro[/COLOR]
# exit
exit
# exit
exit
C:\Users\Downloads\one click root exploit>
Click to expand...
Click to collapse
By the looks of that error I think busybox either isn't installed or not installed correctly.i am not positive but I think that its a busybox problem.
Yeah skeeter is right about busy box, whatever set up busy box didn't do it right
Sent from my SPH-D700 using Tapatalk
What do you guys think I should do?
I tried one click root again. The rooting is successful but still get the above error.
Most of the stuff that requires root (wifi tether, setcpu etc.) is working fine.
How to install busybox manually?
sunrocket said:
What do you guys think I should do?
I tried one click root again. The rooting is successful but still get the above error.
Most of the stuff that requires root (wifi tether, setcpu etc.) is working fine.
Click to expand...
Click to collapse
Sounds like you should just make sure busy box is installed properly. I would download the busybox installer from the market and install 1.17.1
You can't mount the filesystem tha way on the phone, you must use the other script (pita, I know). The remount command only works like that through adb (adb remount) and not from shell.
Sent from my SPH-D700 using XDA App
rufflez2010 said:
You can't mount the filesystem tha way on the phone, you must use the other script (pita, I know). The remount command only works like that through adb (adb remount) and not from shell.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Remount will work from a shell in connectbot if busybox is install correctly. My suggestion would be to flash a kernel with root and busy box in it. Just be sure to remove the joeykrim root exploit before you flash thr kernel.
Sent from my SPH-D700 using Tapatalk
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.
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.
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
Hi! My problem is that I want to mod /system/etc stuff. But problem is: I can't mount /system rw in adb shell!
I'm using CM11 20140622 Nightly
What i've tried:
- sysrw command(alias sysrw='mount -o remount,rw /system')
- by hand(mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system)
None of those commands produce output and they exit 0
- ES File Explorer and CM File Manager
I don't know how, but mounting rw in UI always works, but not over adb.
Can anyone tell me a solution how to mount /system rw successfully over shell?
mikroskeem said:
Hi! My problem is that I want to mod /system/etc stuff. But problem is: I can't mount /system rw in adb shell!
I'm using CM11 20140622 Nightly
What i've tried:
- sysrw command(alias sysrw='mount -o remount,rw /system')
- by hand(mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system)
None of those commands produce output and they exit 0
- ES File Explorer and CM File Manager
I don't know how, but mounting rw in UI always works, but not over adb.
Can anyone tell me a solution how to mount /system rw successfully over shell?
Click to expand...
Click to collapse
Code:
adb root
adb shell
mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
Sent from my Nexus 5 using Tapatalk
rootSU said:
Code:
adb root
adb shell
mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Still same thing, no rw, no output
mikroskeem said:
Still same thing, no rw, no output
Click to expand...
Click to collapse
Windows or Linux? Are you using an outdated adb?
That's definitely correct, I tested it.
rootSU said:
Windows or Linux? Are you using an outdated adb?
That's definitely correct, I tested it.
Click to expand...
Click to collapse
Linux, adb version 1.0.31
Yeah it's correct but problem is it doesn't work.
mikroskeem said:
Linux, adb version 1.0.31
Yeah it's correct but problem is it doesn't work.
Click to expand...
Click to collapse
remove and reinstall your adb
Works fine with that command on both windows and linux for me.
Does adb devices even work?
Can you screenshot the error?
rootSU said:
remove and reinstall your adb
Works fine with that command on both windows and linux for me.
Does adb devices even work?
Can you screenshot the error?
Click to expand...
Click to collapse
No error output, i'm in adb shell so "[email protected]:~ #" will appear
I run commands there.
adb itself works fine.
mikroskeem said:
No error output, i'm in adb shell so "[email protected]:~ #" will appear
I run commands there.
adb itself works fine.
Click to expand...
Click to collapse
Screenshot please
Of this:
Code:
H:\>adb root
adbd is already running as root
H:\>adb shell
[email protected]:/ # mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
platform/msm_sdcc.1/by-name/system /system <
[email protected]:/ #
rootSU said:
Screenshot please
Of this:
Code:
H:\>adb root
adbd is already running as root
H:\>adb shell
[email protected]:/ # mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
platform/msm_sdcc.1/by-name/system /system <
[email protected]:/ #
Click to expand...
Click to collapse
sorry can't make screenshot atm, but i copyed terminal contents to here: http://hastebin.com/dicuhiyema.hs
EDIT: 6th line is the mount command, it wrapped badly
mikroskeem said:
sorry can't make screenshot atm, but i copyed terminal contents to here: http://hastebin.com/dicuhiyema.hs
Click to expand...
Click to collapse
Ah yeah that's as good as a screenshot.
Theres no option in CM11 dev options for adb root is there? I have on in SlimKat where I must enable ADB root.
mikroskeem said:
EDIT: 6th line is the mount command, it wrapped badly
Click to expand...
Click to collapse
Yeah my ubuntu terminal does that too.
rootSU said:
Ah yeah that's as good as a screenshot.
Theres no option in CM11 dev options for adb root is there? I have on in SlimKat where I must enable ADB root.
Yeah my ubuntu terminal does that too.
Click to expand...
Click to collapse
There is actually and it's set to "Apps and ADB", but I might try out next nightly. It might doesn't have that problem anymore. Prolly some SELinux conflict or kernel blocks something
Now it works.
I think it was CM problem.
mikroskeem said:
Now it works.
I think it was CM problem.
Click to expand...
Click to collapse
At first I was thinking it was your computer but everything you were doing was right so I agree. It seems it was.
Sent from my Nexus 5 using Tapatalk
using bin/mount rather than xbin/mount
mikroskeem said:
I can't mount /system rw in adb shell!
What i've tried:
- sysrw command(alias sysrw='mount -o remount,rw /system')
...
Can anyone tell me a solution how to mount /system rw successfully over shell?
Click to expand...
Click to collapse
For posterity, I'm adding what worked for me on LolliKat (which is cm11) for doing this from the phone's console/shell: I had to use the command `/system/bin/mount` rather than just `mount`. Once that had been done once, the other methods would work fine until reboot. (I was doing this because somehow link2sd had lost its ability to "update mount scripts" and "integrate system app updates".
These all worked for me:
/system/bin/mount -o remount,rw /system
/system/bin/mount -o remount,rw -t yaffs2 /system
/system/bin/mount -o remount,rw -t yaffs2 /system /system
/system/bin/mount -o remount,rw -t yaffs2 /dev/block/mtdblock8 /system
More info (in my own context) here and here:
http://forum.xda-developers.com/showpost.php?p=61068974&postcount=3
http://android.stackexchange.com/a/110883/109855