I'm not able to see my PH-1 in ADB on my new Chromebook, and I'm hoping there's a fix available.
I'm in Dev mode, open a terminal, get into shell, type "ADB devices," and the list of devices is blank. No unknown devices, nothing.
I can see it in ADB on the Windows laptop I'm trying to replace, just not on the Chromebook, in Chrome OS, or by using Crouton.
Anyone overcome a similar issue?
Related
I am trying to access my phone through ADB to register w/o data. My device center and device manager both see the phone ("Android Phone" in DC, and "ADB Interface > HTC Dream" in DM). However, when I run ADB from the command line it cannot find my device. I have tried reinstalling drivers, killing and starting the ADB server, and even re-flashing my phone.
Note: When booting the phone from a fresh flash I DON'T have to enter "<enter>setprop persist.service.adb.enable 1<enter>" to initialize ADB. It is automatically seen as an ADB device, and after entering the command it is only seen as a storage device.
Thanks in advance.
(unlocking a Dream on Windows 7 x64)
Solved it by installing the drivers from here: http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
Has anybody tried this? having Lynx accessible via adb shell would be - imo - very handy. For example, my work terminal has no internet access, but I can install the USB driver for my Galaxy S and access the shell that way.
Of course, since I'm not allowed to play with my phone while working, it would be very nifty to open up a cmd window and just type "adb shell lynx" and have at it if I need to.
Has anybody tried this? I'm no coder by any stretch of the imagination, otherwise I'd be having a go at it now..
I tried installing multiple drivers to my LG G Watch but always appears offline on ADB (cmd)
I made sure I enabled adb debugging and bluetooth and I tried both methods and I cant get it to work....
can anyone help me? I really want to install wear messenger :fingers-crossed:
Are you using adb.exe from the latest SDK?
Have you already forwareded with the adp ?
If not just type this in the console
adb forward tcp:4444 localabstract:/adb-hub
After that type this:
adb connect localhost:4444
It should work on this way to set the state to online
Sent from my SM-N9005 using XDA Free mobile app
Trying to run adb results in the USB notification to cycle off/on on the new Moto G5 Plus. I've tried multiple cables, computers, and a factory reset of the phone (both times with the factory image).
Has anyone encountered such an issue?
Basically, I can enable debugging mode and connect my computer, but the moment I issue `adb start-server` the USB notification on the phone begins to cycle. There is no message to authorize the device or anything. For what it's worth, this computer works fine with another device (as does the other). I've deleted the .android directory and saw no change, too.
badhat said:
Trying to run adb results in the USB notification to cycle off/on on the new Moto G5 Plus. I've tried multiple cables, computers, and a factory reset of the phone (both times with the factory image).
Has anyone encountered such an issue?
Basically, I can enable debugging mode and connect my computer, but the moment I issue `adb start-server` the USB notification on the phone begins to cycle. There is no message to authorize the device or anything. For what it's worth, this computer works fine with another device (as does the other). I've deleted the .android directory and saw no change, too.
Click to expand...
Click to collapse
I'm confused... What are you trying to do? I've never used that command...
acejavelin said:
I'm confused... What are you trying to do? I've never used that command...
Click to expand...
Click to collapse
The `start server` command just begins to run the adb daemon. It is run without explicitly issuing this command if you run something like `adb devices`. It's like setting up the environment without actually querying anything on the device.
badhat said:
The `start server` command just begins to run the adb daemon. It is run without explicitly issuing this command if you run something like `adb devices`. It's like setting up the environment without actually querying anything on the device.
Click to expand...
Click to collapse
I tried this just out of interest... revoked all ADB authorizations, rebooted my phone and PC, and connected and did a "adb start-server". It popped up the authorization windows like normal, I approved it and it worked like normal. Subsequent kill-server and start-server commands had no unusual effects either after revoking authorizations or not.
acejavelin said:
I tried this just out of interest... revoked all ADB authorizations, rebooted my phone and PC, and connected and did a "adb start-server". It popped up the authorization windows like normal, I approved it and it worked like normal. Subsequent kill-server and start-server commands had no unusual effects either after revoking authorizations or now.
Click to expand...
Click to collapse
OK, I tried using a different Android SDK (grabbed from https://dl.google.com/android/repository/platform-tools-latest-linux.zip) and now it's working. There must be something about the one my distribution packaged that is broken.
Code:
$ adb version
Android Debug Bridge version 1.0.39
Revision 8.0.0_r11
$ LD_LIBRARY_PATH=$PWD ./adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
Installed as /home/badhat/Downloads/adb/platform-tools/adb
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Did you get permissions on your phone when popup appears?
No. The phone doesn't pop up the permission question. But I don't know why.
Don't know but as long as you don't give permission you can't sideload
Euclid's Brother said:
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Click to expand...
Click to collapse
Try the usb driver and SDK platform tools directly from Essential website:
https://www.essential.com/developer/current-builds
I am using the drivers from Essential website. However, I was using the lastest Unified Android Toolkit for the adb command. Looks like it may be outdated, as the adb.exe and it's dll's in the link from Essential website is newer. I will try the platform tools from there and see if there is a difference.
Thanks!
Is USB debugging enabled in Developer settings?
Are you in Fastboot? Did you try "fastboot devices"?
ADB devices returns your device is offline?