Hello
I install "better terminal emulator pro" app and from preferences i set shell to bash.
After download some data i restart app and try use bash shell.
But i get permission denied error!
I am sure that my phone is rooted (by CF-Auto-Root).
Default shell is work in root mode.
But bash is not work.
How can i fix it?
Related
I rooted my phone and I was able to install Superuser and Titanium Backup and both appear to be running successfully. My question is when I run adb shell from my PC and I get the $, I get permission denied when I type SU or whoami? Did I miss something?
C:\>adb shell
$ su
su
Permission denied
$ whoami
whoami
whoami: permission denied
$
just wondering why you need to use superuser when you use adb shell
OK, so why the permission denied response from the OS?
http://forum.xda-developers.com/showthread.php?t=1002203
that prob has something to do with it, push that kernel and try again
OK thanks, I will keep that in mind if I run into issues. Everything else is working fine otherwise, so I will well enough alone for now, while I read the docs on the Android Dev site.
i gotta question. is adb shell and terminal emulator the same thing? and am i right getting into adb shell with the CMD from windows when having my phone via usb connected in debugging mode? and can someone tell me where i can get a list of commands?
thx
X10mini miniCM7 2.0 using XDA Premium App
freebordjunky said:
i gotta question. is adb shell and terminal emulator the same thing? and am i right getting into adb shell with the CMD from windows when having my phone via usb connected in debugging mode? and can someone tell me where i can get a list of commands?
thx
X10mini miniCM7 2.0 using XDA Premium App
Click to expand...
Click to collapse
adb shell and Terminal Emulator are not the same thing. One is an shell environment (adb shell) and the other is a tool to access that environment (Terminal Emulator).
adb shell is native to the phone and allows for Linux shell access. Terminal emulator will allow you to run adb shell ON the phone directly to access that shell environment.
Secondly, yes you are correct, in that you can use the Command Prompt (CMD) to access adb shell. Also, your phone must be in debugging mode as you stated.
To get a list of commands -- you type: adb, while in the androidsdk\tools folder and it'll display the default set of commands available to you.
Though, the most common commands you'll run are as follows:
adb shell -- Gives you shell access, best used with root access
adb remount -- Mounts the phone for r/w (read-write) access; this
needs to be done if you plan to run the next two commands, but only once.
adb push -- Push's/Move's a file to the specified dir, usually system/app
adb pull -- Copies a file from a specified dir, usually system/app
adb shell reboot -- Reboots your phone from the command line
Hope that helps.
thank you very much
X10mini miniCM7 2.0 using XDA Premium App
Sure, no problem.
pseudoremora said:
Sure, no problem.
Click to expand...
Click to collapse
Hi there, Im new to TE and ADB as well.
1) From what it looks like why would you ever use ADB if you didnt need to exchange files with the computer?
TE seems a lot easier to use without having to install the sdk, different exes etc.
2) I've also stumbled upon the ADBD insecure by chainfire, from what I've gathered, this app gives you root access to stock kernels that otherwise wouldn't have given you that. and saves you from typing long command lines.
But what lines is it saving you from typing? Just "su"?
Adb pull or push DOES NOT work with Terminal Emulator as they are not found as commands. What to do to use them with unrooted phone?
pseudoremora said:
adb shell and Terminal Emulator are not the same thing. One is an shell environment (adb shell) and the other is a tool to access that environment (Terminal Emulator).
adb shell is native to the phone and allows for Linux shell access. Terminal emulator will allow you to run adb shell ON the phone directly to access that shell environment.
Secondly, yes you are correct, in that you can use the Command Prompt (CMD) to access adb shell. Also, your phone must be in debugging mode as you stated.
To get a list of commands -- you type: adb, while in the androidsdk\tools folder and it'll display the default set of commands available to you.
Though, the most common commands you'll run are as follows:
adb shell -- Gives you shell access, best used with root access
adb remount -- Mounts the phone for r/w (read-write) access; this
needs to be done if you plan to run the next two commands, but only once.
adb push -- Push's/Move's a file to the specified dir, usually system/app
adb pull -- Copies a file from a specified dir, usually system/app
adb shell reboot -- Reboots your phone from the command line
Hope that helps.
Click to expand...
Click to collapse
I tried the following from powershell, on windows:
Code:
.\adb.exe shell cmd overlay enable com.android.internal.systemui.navbar.gestural
and it worked.
I tried the same from the terminal emulator, and it said
cmd: service not found: overlay
Click to expand...
Click to collapse
Why is it that it works one way, and not the other way? Aren't they interacting with the same shell enviromnent? Is there a permission difference?
Hey everyone I got a very technical question
I am trying to set a custom prompt for the shell on an android device running bourne shell (sh), I have suceeded in setting it for a login shell (sh -l) but I would like to make this default for non login like adb or ssh through connectbot @localhost. Normally on linux I could do this by editing /etc/profile but for some reason on my android sh does not read /etc/profile unless it is a login shell. I tried moving the sh binary and replacing the sh binary in /system/bin with a shell script that executes sh -l but I loose superuser access ( shell reports su command not found) so I moved sh back to /system/bin/sh. Does anyone have any Idea which file is read in by sh at launch?
Alright...I got al the way through to he point of having adb access. I had to use shell with su to copy superuser.apk, busybox and su to tablet. I went on table and installed the .apk
now when I go in to adb shell and type "su" I get "Warning: Generic atexit() called from legacy shared library" and then I get
255 :[email protected]:/ $
Anybody know how I can get back to
[email protected]:/ #
I have tried uninstalling the superuser.apk, I have killed and started the server...restarted the tablet???
Help!
Update
[email protected] said:
Alright...I got al the way through to he point of having adb access. I had to use shell with su to copy superuser.apk, busybox and su to tablet. I went on table and installed the .apk
now when I go in to adb shell and type "su" I get "Warning: Generic atexit() called from legacy shared library" and then I get
255 :[email protected]:/ $
Anybody know how I can get back to
[email protected]:/ #
I have tried uninstalling the superuser.apk, I have killed and started the server...restarted the tablet???
Help!
Click to expand...
Click to collapse
I have uninstalled the superuser.apk and deleted the files from the sdcard. I killed and restarted the server and now when I type su in adb shell I get
su
permission denied
255 :[email protected]:/ $
**************************************SOLUTION********************************
I HAD TO RE-RUN "IMPACTOR" TO RESET SU ON PHONE. NOW EVERYTHING WORKING WELL AGAIN.
Hi all! I have a Chinese tablet that I need to root in order to run some applications. It mounts a 4.4.2 Android version and I can access via adb by opening an adb root shell. The table is called letine lt707a .
This is what I did:
Code:
adb shell mount -o remount,rw /system
adb push su /system/xbin
adb shell busybox chmod 6755 /system/xbin/su
Then I installed a version of Superuser.apk. When I open a terminal emulator app from the device, if I write "su" I obtain a "Permission denied" message.
Where is the problem? Maybe I have an old binary su?
I also tried with SuperSU without any results.
Thank you for your help!
I have just to push the correct su in the folder, but I don't know where to find it. After that in case of error I must undersand how Superuser communicates with the su. Anyone?
I think the problem is with kit kat. I pushed the su binary that came from superSU, but when I open a terminal emulator to write su I obtain a number zero as output.
If I start superSU I obtain a warning message: the program doesn't find the su binary.