..but this morning after a normal turn off of the phone, "SONY ERICSSON" in my mini pro display don't disappear..
From adb I get:
Code:
C:\android\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ su
su
link_image[1722]: 1350 could not load needed library 'libandroid_runtime.so' for 'su' (link_image[1722]: 1350 could not load needed librar
y 'libdvm.so' for 'libandroid_runtime.so' (reloc_library[1245]: 1350 cannot locate 'open_memstream'...))CANNOT LINK EXECUTABLE
$
HELP! What can I do???
UNBRICKED !!!!!
Using SuperOneClick and another adb shell I got root (I did not believe to see "UID 0" after a whoami command )
So, I could replace libdvm.so with a fresh copy
now, it's ok!
Related
Hi all!
I was using Modaco 2.9 before and it was amazing stable.
Later on I tryied [email protected] worked well, but not as stable as the modaco, so I thought lets change to the 3.0. Since that I have al lot system crashes, so I thought I need to do "deldalv and/or ext_wipe" with the RA-recovery-1.2.3
Figured out that it didnt work, it says I should use "adb deldalv"
I couldnt get the adb to run on my ubuntu linux, so I tried to find an update for the RA-recovery.
And there is RA-recovery-1.5.1 and I can just install it (cause I have a previous version) via adb.
Now My Question:
How does it work?!?
Code:
[email protected]:~$ adb usb
error: insufficient permissions for device
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
[email protected]:~$ adb kill-server
[email protected]:~$ adb start-server
* daemon not running. starting it now *
* daemon started successfully *
[email protected]:~$ adb usb
error: insufficient permissions for device
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
Code:
[email protected]:~$ cat /etc/udev/rules.d/50-android.rules
#Bus 001 Device 005: ID 0bb4:0c02
SUBSYSTEM=="usb", SYSFS(idVendor)=="0bb4",MODE="0666"
How do I connect the device then, if not like that?
How can I test if everything works?
Thanks in advance
Unicate said:
How do I connect the device then, if not like that?
How can I test if everything works?
Thanks in advance
Click to expand...
Click to collapse
afaik this looks good, try starting adb as root. this is what adb devices says for me:
Code:
[email protected]:~$ adb devices
List of devices attached
HT98XXXX427 device
Code:
./adb start-server
./adb shell
works for me (with root ofcourse )
I set up my system so that the adb deamon starts at boot.
Created a script in the /etc/init.d directory called adb:
Code:
#! /bin/sh
case "$1" in
start)
/home/joeblow/AndroidSDK/tools/adb start-server
;;
stop)
/home/joeblow/AndroidSDK/tools/adb kill-server
;;
*)
echo "Usage: $0 start|stop" >&2
exit 3
;;
esac
Created a link to it in /etc/rc2.d:
Code:
lrwxrwxrwx 1 root root 13 2010-01-09 19:17 S10adb -> ../init.d/adb
Off Topic...
Am sorry to be a little off topic.. I just got my Hero and was trying to figure out all the stuff about it here on XDA.. Can anybody tell me what is ADB ??.. Whats it used for ??.. As far as I have understood, I think its some sorta software to connect hero to the computer to transfer files and stuff.. Is it right ??.. If yes.. Then what is the difference between this and HTC SYNC ??.. Thanks in advance.. Cheers !!!
if You want only transfer files, You don't need ADB.
htc sync is for synchronizing phone (contacts, calendar, etc) with PC (i guess, i don't use it ) and for upgrading SW.
whats the android command to restart sevices from terminal or adb shell? i want to stop and start adbd from the phone. ive tried the linux service adbd restart to no avail.... also would like to start /stop / restart networking etc...
toy4x4xda said:
whats the android command to restart sevices from terminal or adb shell? i want to stop and start adbd from the phone. ive tried the linux service adbd restart to no avail.... also would like to start /start networking...
Click to expand...
Click to collapse
$ adb kill-server
$ adb start-server
Click to expand...
Click to collapse
Requires you've got the adb binary on you device, though.
Well that's not quite what I am looking for...
That only kills/starts the adb binary not the adb daemon that runs on my phone. I would like to be able to restart services / daemons like on other distros of linux. As seen here: http://theos.in/desktop-linux/tip-that-matters/how-do-i-restart-linux-network-service/
[email protected]_targa:/# ps |grep adb
ps |grep adb
root 280 1 3452 188 ffffffff 00008294 S /sbin/adbd
[email protected]_targa:/# adb start-server
adb start-server
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
[email protected]_targa:/# ps |grep adb
ps |grep adb
root 280 1 3452 188 ffffffff 00008294 S /sbin/adbd
root 22683 1 3936 396 ffffffff afd0b8d4 S adb
[email protected]_targa:/# adb kill-server
adb kill-server
[email protected]_targa:/# ps |grep adb
ps |grep adb
root 280 1 3452 188 ffffffff 00008294 S /sbin/adbd **********Daemon still running as same pid and adb connection never reset.
[email protected]_targa:/#
Wow I couldn't find this anywhere for some reason but I tried start / stop commands and they worked ...
stop adbd
start adbd
restart adbd - otoh fails with: -- as does restart with other services such as restart mboxd
restart: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
C:\ADBTOOLS>adb devices
List of devices attached
da4d4717 device
C:\ADBTOOLS>adb shell
[email protected]:/ $ su
su
[email protected]:/ # adb devices
adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
[email protected]:/ #
my device connects to adb,
however as soon as I go into adb shell, the device is no longer found.
What is going on here?
mdelaney1986 said:
C:\ADBTOOLS>adb devices
List of devices attached
da4d4717 device
C:\ADBTOOLS>adb shell
[email protected]:/ $ su
su
[email protected]:/ # adb devices
adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
[email protected]:/ #
my device connects to adb,
however as soon as I go into adb shell, the device is no longer found.
What is going on here?
Click to expand...
Click to collapse
Of course that happens when you run adb shell you are entering in your phone using the debbuging shell. You are in your phone. This happens to me also when i am using adb shell no devices will be shown. If you can run any command from adb shell then your device is there. Nothing to worry about. It is normal.
If you disconnect your device when in adb shell you will see it will automatically exit the shell!
Hit Thanks if i helped you!
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
Hello,
my phone (I think it is not rooted because adb shows the dollar character) is stuck into the recovery for an unknown reason. Is there a way to access the phone folders through ADB / shell commands?
I'm a newbie and I tried to do by myself but unfortunately I cannot reach my objective.
for example, I (think) I successfully reached the sdcard (is this the android folder name where all the personal data si saved?) but when I try the command adb pull -p It doesn't work. Here what it happens:
1|[email protected]:/ $ cd sdcard
[email protected]:/sdcard $ adb pull -p
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/sdcard $
Any Idea? Thanks
Howl55 said:
Hello,
my phone (i think it is not rooted because adb shows the dollar character) is stuck into the recovery for an unknown reason. Is there a way to access to phone folders through ADB / shell commands?
I'm a neewbie and I tried to do by myself. Unfortunately I cannot reach my objective.
for example, I (think) I successfully reached the sdcard (is this the android folder name where all the personal data si saved?)
but when I try the command adb pull -p It doesn't work. Here what it happens:
1|[email protected]:/ $ cd sdcard
[email protected]:/sdcard $ adb pull -p
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/sdcard $
Any Idea? Thanks
Click to expand...
Click to collapse
Is there someone who could help me???