when i type
adb devices
adb shell
or
adb remount
i get starting daemon
failure to start daemon
please help
i just had the same problem.
i unistalled the phone drivers and i installed htc sync
http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
make sure you delete your drivers!
i used USBDeview
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
Related
I've searched a lot, but did not find a solution.
When I connect my HTC Kaiser with Android Ion 1.5 on the top to my Linux box (all UDEV settings are as recommended), the adb utility (launched as root) does not recognize it correctly. It shows a set of questionmarks instead of the device name:
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? device
adb basic commands (pull/push/install/shell) work, though, but DDMS does not work and I can't debug my application when the device is attached.
Does somebody have a solution?
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
it is root
Super Jamie said:
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
Click to expand...
Click to collapse
Like I mentioned in my question - I do run adb as root.
When it's launched not as root, I can not even do "adb shell" and
"adb devices" shows:
"????????????? Permission denied". So, it is root, I assure.
BTW, on my work Windows 2k3 machine I can use ddms, but
"adb devices" still shows some garbage letters instead of the device name.
Sorry for my English, if my explanation is not clear.
I had my adb working with my Droid now when i try to enter
adb shell or adb remount
(Yes i have USB Debugging Enabled, and my sdk is added to my path)
this is what happens
* daemon not running. starting it now *
* daemon started successfully *
error: insufficient permissions for device
not sure if this is because we don't have root. any help would be appreciated.
you are unable to 'adb shell'?
I have shell access, but not remount.
No I cannot get into shell
I have found a fix.
Seems to be that i need to run adb usb as root in Linux.
so for me my path to my sdk is
~/Desktop/androidsdk/tools
so i have to run "sudo ~Desktop/androidsdk/tools/adb"
then adb shell works as does ddms for logcats and screenshots.
cool, if adb is working then maybe I can install the old mail.apk on my incredible as a non-system app.
Hrmmm.... I don't need to use sudo on the mac or linux. What are the permissions on adb?
Sent from my ADR6300 using the XDA mobile application powered by Tapatalk
jrebeiro said:
Hrmmm.... I don't need to use sudo on the mac or linux. What are the permissions on adb?
Sent from my ADR6300 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
I chmodded 777
permissions are
rwxrwxrwx
This is weird, I had adb working just fine (without doing anything different) on ubuntu 9.10, then I upgraded to 10.04 and I have no permissions, even when I run it using sudo... ugh..
try re installing the sdk, thats what i had to do
is it possible to use adb from the transformer, to connect to an other adb device? (that would be my phone)
when I connect my phone to the usb port of my tf (on the dock) and then I type adb devices in a shell here is what I get:
[email protected]:/ $ adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
[email protected]:/ $
I've done it before. Not sure why it isn't working for you. Double check that debugging is enabled on your phone. You also may need to be root to use adb on the TF. Type "su<enter>" to get root in your terminal, then try adb.
If your TF isn't rooted, then you need to do that first.
never mind, I just needed to adb kill-server after getting root
it works now
Hello, recently I've ran into a stupid problem after unlocking bootloader on my M7. Here is what happened, after unlocking I was not able to use my phone in debugging mode, the authorization pop-up didn't show up wherever I connected my phone to PC in ADB mode. This was not Drivers fault I just lost RSA Key, I managed to get it back, I hope it will help you also.
To get RSA keys you need to do next thing.The trick is to create the .android directory elsewhere, for example on the SD Card:
You need Android Terminal Emulator and Root for this operation. ( Link to Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en )
Open Android Terminal Emulator and write:
adb kill-server
HOME=/sdcard adb start-server
At this point you should have /sdcard/.android and the 2 keys in it.
Then just copy adbkey from your phone to your computer into C:/Users/YOURNAME/.android then write in terminal.
stop adbd
start adbd
Then connect you phone in ADB mode Wifi or USB and check again:
adb kill-server
adb start-server
adb devices
Now authorization prompt should pop up!
This issue is also known as Unauthorized device in ADB mode.
Good luck!
I'm trying to sideload a pandora apk and i'm running into an adb error that i don't understand.
Steps taken:
adb installed on PC
drivers installed on PC
phone has USB debugging ON
phone connected via USB to PC
adb devices: shows my device attached properly
adb shell generates a prompt: "OnePlus6T:/$
pm install -i "com.android.vending" -r /sdcard/download/pandora.apk
The last command to install generates the following error: <avc: denied (read) for scontext=u:r:system_server:s0... (see attached screenshot).
I've tried different locations such as /sdcard/pandora.apk and tried different apk files with the same result.
Thoughts?