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.
Related
Hi everyone, I recently installed this ROM here http://forum.xda-developers.com/showthread.php?t=2205516&page=73&nocache=1 (unfortunately I can't post questions on that thread yet). Superuser access works fine from apps and terminal emulator, but if I try to connect from adb with "adb shell su" I get "Permission denied" on my command prompt and a "Superuser denied to shell" toast on the phone.
I can't find a way to change this, apparently the shell user can't su. I tried from the terminal emulator too and here's what happens:
Code:
[email protected]: / $ whoami
u0_a14
[email protected]:/ $ su
[email protected]:/ # whoami
root
[email protected]:/ # su - shell
[email protected]:/ $ whoami
shell
[email protected]:/ $ su
Permission denied
1|[email protected]:/ $
Any help pwetty please?
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,
This one is confusing me, feels like I am missing something really stupid...
I am trying to get my brother's phone rooted for him, and he already used some online tools to get halfway there (Unfortunately I don't know what these tools did or how they did it).
So right now if I run "adb root && adb remount && adb shell" I get a full root shell wirh RW access to the /system dir. From here I can copy the su binary into /system/bin and set:
chown 0:0 /system/bin/su
chmod 6755 /system/bin/su
After this I can run su from the adb shell (so the binary does work), but if I try to use terminal on the device itself su claims to have insufficient permissions, and the SuperSU/ BusyBox installers won't play nice for obvious reasons.
What have I missed out on?
Thanks in advance
PS: This is a repost of a question I asked in kinda the wrong place. Sorry about that.
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.