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
Related
I'm using the adb.exe command directly from the Android SDK to connect to my Xperia X10's file system. Here are the commands I issued:
D:\android_sdk\tools>adb shell
$ cd data/app-private
cd data/app-private
$ ls
ls
opendir failed, Permission denied
$ su
su
pwd
pwd
ls -l
ls -l
Permission denied
$ /data/app-private
$ opendir failed, Permission denied
$ exit
exit
D:\android_sdk\tools>
Two questions: 1) Why is it commands entered after typing "su" are echoed? 2) How come I can't browse the app-private directory even after entering su?
Thanks.
Have you rooted your X10 ? (think not)
A # prompt indicates superuser privileges, you did not get to be a superuser.
Why you get an echo I don't know.
mattiL said:
Have you rooted your X10 ? (think not)
A # prompt indicates superuser privileges, you did not get to be a superuser.
Why you get an echo I don't know.
Click to expand...
Click to collapse
Yes the phone is rooted. I have the AT&T branding, but used the one-click exploid to root the phone, and it works as Titanium Backup when running tells me it gained Superuser priviledges. I don't know what I'm doing wrong. This is from an MS-DOS prompt in Windows.
When you use SU for the first time, you need to have the phone screen on and unlocked. It will ask for superuser permissions. Then it will work.
naplesbill said:
When you use SU for the first time, you need to have the phone screen on and unlocked. It will ask for superuser permissions. Then it will work.
Click to expand...
Click to collapse
Ha, thanks, it worked. The key was typing SU just before I unlock the phone, then it asks me on the phone that "Unknown" wants superuser access. Thanks again.
I was finally able to apply the 'Enable Non-Market apps' fix via adb thanks to this little tip
I'm learning- slowly...
How exactly do I run scripts on this phone when connected to a PC?
Code:
C:\android_sdk\tools>adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
# cd sdcard
cd sdcard
# ls -l testscript.sh
ls -l testscript.sh
----rwxr-x system sdcard_rw 54 2010-10-06 10:52 testscript.sh
# sh testscript.sh
sh testscript.sh
: not foundsh: ■#!/bin/sh
: not foundsh: /sh
: not found
mkdir <target>
#
Any ideas?
If anyone told me "You should save your files in UNIX format where each text line ends in 0x0A, and not 0x0D 0x0A as in Windows, it will work" ... you'd be right. UNIX doesn't like carriage return & line feed pairs when trying to run a shell script.
Trying to install Clockwork recovery mod on my LG Optimus V and I am running into a few problems. The version of ROM Manager that I got from the market does not list my phone as a model to choose from when the Confirm your phone window appears. So, to get around this, I decided to try and install another recovery (such as Amon's) using an adb shell. Anytime I try to type a command while in the adb shell it returns the command and says "permission denied" next to it. The $ is there, my phone is rooted, the SD card is unmounted and USB Debugging ot turned on.
I can view my phone from adb devices and even look at the log of its activity with adb logcat.
The first command I type in is "adb shell mount -o rw,remount /dev/block/mtdblock3 /system". After I hit enter, it says mountperation not permitted.
I also can't boot into recovery mode at the moment because I had to choose a phone that is different from mine when I tried to flash Clockwork Recovery mod.
I'd greatly appreciate any help, I'll get some sleep and check back in a few hours.
ironpirat3 said:
The $ is there, my phone is rooted
Click to expand...
Click to collapse
The $ is normal user and not root (#).
Code:
> adb shell
$ su
# mount -o rw,remount /dev/block/mtdblock3 /system
Turns out I wasn't looking at my phone and allowing the su command through Superuser (feel really dumb now). Still, whenever I try to run a command starting with adb shell from the command prompt it says Operation not permitted.
Code:
>adb shell mount -o rw,remount /dev/block/mtdblock3 /system
mount: Operation not permitted
On a side note, how do I get out of my phone and back into command prompt after using the adb shell command?
ironpirat3 said:
Turns out I wasn't looking at my phone and allowing the su command through Superuser (feel really dumb now). Still, whenever I try to run a command starting with adb shell from the command prompt it says Operation not permitted.
Click to expand...
Click to collapse
Code:
>adb shell mount -o rw,remount /dev/block/mtdblock3 /system
mount: Operation not permitted
No. You run adb shell only, and then su, and then remount from the phone shell, NOT via adb. Clearly written in the example above.
To exit a shell, type exit.
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.
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.