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.
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.
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?
Got root, then su binary installed need some help backtracking a few things. If someone is up for it?
I guess the first thing first is. The first time I adb shell'd I got promted with root user: ( does this happen right off the bat for anyone else? I did a few things before this with modstrings and busybox. But, didn't try adb till after)
Code:
adb shell
[email protected]:/ #
Once I noticed I had root on shell I simply found the system mount at /dev/ubui0_0 and I mounted it rw.
Code:
[email protected]:/ # mount -o remount, /dev/ubi0_0
moved the su binary over to the sdcard. wrote it to system/xbin link named to /system/bin. gave permisions.
Code:
adb push su /sdcard/
[email protected]:/ # cat /sdcard/su > /system/xbin/su
[email protected]:/ # ln -s /system/xbin/su
[email protected]:/ # chmod 6755 /system/xbin/su
[email protected]:/ # su
[email protected]:/ # :D
Off I went. I need to update the binary, but as of right now Superuser shows root as 'allow', SuperSU deny (think it old binary).
If you guys are not getting root after adb shell on this device, I think I can backtrack the modstrings and other stuff I did.
I really don't know where this device sits on getting rooted. It seems like some windows programs did it before an update that happened at some point, but not anymore? I don't have access to windows so I don't keep up with those methods.
Thanks! Hope someone can help me out.
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.
Hi,
I've changed my build.prop and now my phone won't boot, it stay on the boot logo.
I've installed supersu on the phone , it is rooted as I have root access using phone interface.
But now I'm stuck on boot logo and try to access the phone via adb shell :
But the su Command in adb shell doesn't give root access, it stays in "shell" user.
I never used it as my phone was well and running so I didn't allow su to get root access in a shell in the supersu apk.
How can we override this ?
adb root doesn't work neither.
Any idea ?
Thanks
My phone : honor 6, Android 4.4.2, SuperSu
C:\Users\U403774\Downloads\Honor6\HONOR 6 Multi-Tool>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o remount,rw -t ext4 /dev/block/platform/ff1fe000.dw
mc0/by-name/system /system
dev/block/platform/ff1fe000.dwmmc0/by-name/system /system <
mount: Operation not permitted
255|[email protected]:/ $
255|[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011
(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),
3006(net_bw_stats) context=u:r:adbd:s0
[email protected]:/ $
Saved, thanks to TWRP recovery file manager !!
But I still be curious , and if someone knows , I'd like to get the answer to my first question.
"But the su Command in adb shell doesn't give root access, it stays in "shell" user.
I never used it as my phone was well and running so I didn't allow su to get root access in a shell in the supersu apk.
How can we override this ?"
thanks