Develop Bugs

Can no longer connect via ADB

I had it all set up correctly and it worked fine both by USB and TCPIP. At some point in the last day or two this stopped working. I've done a complete reinstall of the SDK on my desktop and followed the instructions here https://devs.ouya.tv/developers/docs/setup
When I do adb devices I just get nothing. adb connect xx.xx.xx.xx gives nothing as well.
When I try to run adb from a terminal emulator on the unit I can start or stop the server but any other adb command results in a 'device not found' message. This message is preceded by some two or three digit word but since my TV crops the image I cannot tell what it says. so it is something like '##r: device not found'
Does anyone have any idea on what I need to do to get ADB working again?

Look in your system settings and make sure the ouya is still being recognized. I haven't used adb since the recent updates, but perhaps something changed causing your computer to no longer see it or caused the drivers to fail.
Sent from my SCH-I535 using Tapatalk 2

TadeoNYC said:
Look in your system settings and make sure the ouya is still being recognized. I haven't used adb since the recent updates, but perhaps something changed causing your computer to no longer see it or caused the drivers to fail.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
There aren't any drivers involved here yet. Nothing happens at all when I plug the system in. No devices are detected, correctly or otherwise.
I'm starting to think the micro usb port is just physically broken. I've tried multiple cables, restarting. Connecting other android devices to my desktop which work fine.

could be the port. I have a heck of a time plugging mine in sometimes. it's like the hole in the casing is just a bit bigger than the actual plug, and I have to fumble around for it. I mostly leave the microusb connected all the time now.

Oh!lol.
That happened to me as well. The micro usb port is deeper than normal. My Samsung plugs did not work,I was able to use one from my Kodak pocket video cam.
Sent from my SCH-I535 using Tapatalk 2

Ok, so I'm trying to just adb tcpip working now to bypass the usb issue. I installed an SSH server and I'm getting this
[email protected]:/ $ adb kill-server
[email protected]:/ $ adb tcpip 5555
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $

Found this
setprop service.adb.tcp.port 5555
stop adbd
start adbd
no luck, still can't connect.

beowolfschaefer said:
Found this
setprop service.adb.tcp.port 5555
stop adbd
start adbd
no luck, still can't connect.
Click to expand...
Click to collapse
If you have wireless adb enabled the way to control it so it does not shut down the micro usb port debugging , find the wireless adb .Apk here on xda in the nook color general section and install it then you will beable to open the app and toggle it back and forth to get micro usb debugging back.

My Ouya has done the same thing. Its not hardware but factory reset does not seem to do anything. I have tried several cables , 2 pcs and its the same story all across. MTP connection works fine. ADB , the Ouya thinks its in ADB but nothing is recognized by the pc. Not failed driver install. As soon as you turn debugging on, the Ouya effectively vanishes from the pc.
Alas I did not get as far as putting a file manager on so can not side load anything. Without ADB as well. Well i'm screwed. Not keen on trying to send it back as already got hit for an extra £16.64 by customs, and with the launch the teams are going to be swamped.
I'm convinced its a file permission issue of some sort. But no CWM, ADB , File Manager or Recovery that I have manged to find yet. Well for now at least im stumpped.
Any ideas?

Broomfundel said:
My Ouya has done the same thing. Its not hardware but factory reset does not seem to do anything. I have tried several cables , 2 pcs and its the same story all across. MTP connection works fine. ADB , the Ouya thinks its in ADB but nothing is recognized by the pc. Not failed driver install. As soon as you turn debugging on, the Ouya effectively vanishes from the pc.
Alas I did not get as far as putting a file manager on so can not side load anything. Without ADB as well. Well i'm screwed. Not keen on trying to send it back as already got hit for an extra £16.64 by customs, and with the launch the teams are going to be swamped.
I'm convinced its a file permission issue of some sort. But no CWM, ADB , File Manager or Recovery that I have manged to find yet. Well for now at least im stumpped.
Any ideas?
Click to expand...
Click to collapse
Did you set up adb over wireless?

tcollum said:
Did you set up adb over wireless?
Click to expand...
Click to collapse
I had done but. But it stopped working some time after, and I have not managed to get it going since. Would it stop wired at the same time? Even so would it not have been reset by the factory reset?
Either way, Ill set it with an ethernet cable and see if the flaky wifi was why adb over wifi did not work.
I'm sure a workable solution will turn up. Just disappointed.
Ill report back.
Thanks
Update: Thanks for your help. I tried over wifi and no joy. But ethernet is working. So just got to sort out the flakey wifi now.
Thanks again.

Some people report having better luck connecting Wi-Fi with the native android settings found in the manage area.
Sent from my GT-P3113 using Tapatalk 4 Beta

For anyone who committed to wireless ADB method, and currently stuck without ADB access or su priveledge, the Play Store has a wireless ADB app called "ADB Wireless (no-root)" by Sherdle. Sideload this puppy and you'll be able to toggle the wireless/wired ADB connection!

HaYNigloo said:
For anyone who committed to wireless ADB method, and currently stuck without ADB access or su priveledge, the Play Store has a wireless ADB app called "ADB Wireless (no-root)" by Sherdle. Sideload this puppy and you'll be able to toggle the wireless/wired ADB connection!
Click to expand...
Click to collapse
It's also available through the f-droid app.
Sent from my GT-P3113 using Tapatalk 4 Beta

TadeoNYC said:
Some people report having better luck connecting Wi-Fi with the native android settings found in the manage area.
Sent from my GT-P3113 using Tapatalk 4 Beta
Click to expand...
Click to collapse
My wifi works great. unless i try to login to google.

Look here: https://devs.ouya.tv/developers/docs/setup
They changed the device ID, you need to do step 5-6.
More info here: http://www.ouya.tv/devnews.html

[Q] Can't connect with ADB

I can't seem to connect through adb. This is the first time I'm doing it on the G3.
I have rooted, and got USB Debgging switched on, but all I'm getting is this everytime:
C:\Program Files\Android\android-sdk\tools>adb remount
adb server is out of date. killing...
could not read ok from ADB Server, error = 109
* failed to start daemon *
error:
C:\Program Files\Android\android-sdk\tools>
Am I doing something wrong for the first time I'm connecting? I've checked on the phone when the PC is connected, it is on USB Charge only, the USB debugging menu option is greyed out and that's it.
Any know how to connect up correctly and how?

Try to change from Charge Only to Send images (PTP)

zi0m3k said:
Try to change from Charge Only to Send images (PTP)
Click to expand...
Click to collapse
Tried that, now it says:
C:\Program Files\Android\android-sdk\tools>adb remount
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Program Files\Android\android-sdk\tools>adb shell
adb server is out of date. killing...
could not read ok from ADB Server, error = 109
* failed to start daemon *
error:
Seems to not work either?

I haven't done anything special to the phone apart from rooting it, so I'm not sure why I can't adb to it.
How is everyone else getting adb to work?

Anybody know how to connect up to adb reliably? I've only done what I've said in the above post?

I got it to work after I installed the LG g3 drivers on my PC twice.

galt said:
I got it to work after I installed the LG g3 drivers on my PC twice.
Click to expand...
Click to collapse
I tried installing the LG PC suite twice - then three times, each time it keeps failing to adb.
Do you have the drivers separately? If so can I have a copy please?

I'm pretty sure I used the ' LG G3 Drivers for Windows [Ver.3.11]' file downloaded from this site: http://www.mylgphones.com/download-and-install-the-usb-drivers-for-lg-g3-on-windows-and-mac.html
Sent from my LG-D851 using XDA Premium 4 mobile app

Your error is a PC side error not a phone side error

galt said:
I'm pretty sure I used the ' LG G3 Drivers for Windows [Ver.3.11]' file downloaded from this site: http://www.mylgphones.com/download-and-install-the-usb-drivers-for-lg-g3-on-windows-and-mac.html
Sent from my LG-D851 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Should I uninstall the LG PC suite before I install the drivers then? Would that make it work better?

Lennyuk said:
Your error is a PC side error not a phone side error
Click to expand...
Click to collapse
I'll reboot and give it another try then.
EDIT: Rebooting and trying again didn't work, trying the driver link given above. Thanks for the suggestion though.

zi0m3k said:
Try to change from Charge Only to Send images (PTP)
Click to expand...
Click to collapse
That's exactly what I had to do. Thank you.

I am having trouble too. When I switched from Media (MPT) to Send images (PTP) my laptop responded. What ADB are you running?

[HELP][ZE500KL][ADBERROR] Blocked trying to connect phone to computer

Hey everyone! I have tried downloading several drivers from several posts but each time I open a command line and enter "adb devices" it says :
" *daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error"
For info, I have followed the instructions of these posts/sites:
https://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
https://forum.xda-developers.com/ze...-zenfone-2-t3114063/post60872347#post60872347
https://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/

Try, when getting this error, going into task manager and killing any adb processes you find. Then running it again
Sent from my ASUS_Z00A using Tapatalk

Thanks!

kenbo111 said:
Try, when getting this error, going into task manager and killing any adb processes you find. Then running it again
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Now I have :
List of devices attached
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
** daemon still not running
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error

SpacedSyd said:
Now I have :
List of devices attached
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
** daemon still not running
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error
Click to expand...
Click to collapse
Do you have adb debugging turned on on your phone? Also try using command line with administrative privileges.
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
Do you have adb debugging turned on on your phone? Also try using command line with administrative privileges.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Do you mean the USB debugging option? Or is there an app I must download?

SpacedSyd said:
Do you mean the USB debugging option? Or is there an app I must download?
Click to expand...
Click to collapse
Sorry, yes I meant USB debugging. ?

kenbo111 said:
Sorry, yes I meant USB debugging. ?
Click to expand...
Click to collapse
It doesn't work with administrative privileges

android tv detected as adb device by pc

Hello
my android tv box is detected as android device by my pc, and it cause me problem with adb command
I've disabled usb debugging and close developpement settings but it still connected by adb via wifi
F:\platform-tools>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
192.168.100.7:5555 device
Click to expand...
Click to collapse
can you help me please to resolve this problem please ?

Go to dev option and click on revoke.

Running ADB on MacOS with Note 10

Greetings,
I am attempting to run Tasker with AutoApps on my Note 10.
I get the following message when I run ADB from my MacBook.
adb: no devices/emulators found
I have USB Debugging enabled, and I installed Android File Transfer and also tested with Samsung Smart Switch. Both applications make successful connections with my Note 10, but I am confused as to why ADB does not detect my device. Any help is greatly appreciated.
I also ran...
/adb kill-server
./adb devices
and receive the following...
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
There is no device listed.
Any assistance would be greatly appreciated.

Did you try ./adb devices again after daemon had started?