android - ADB Crashing in Eclipse -


This question is related, although there is no answer to that thread, so it is not technically duplicate.

I have running ADB 1.0.26, running on my Windows 7 x64 and Eclipse SDK 3.6.2 ADT 10.0.1 SDK tool R10, and I have all Android SDK versions installed .

When I connect my phone to the computer in debug mode, and type adb devices in the command prompt, my phone shows it is a motivation 4g < Code> adb shell in the device and ls , so I'm assuming that the ADB / driver / phone part of the series is working properly.

Now, if I connect my phone and go into eclipse, then I get:

[2011-03-28 17:46:33 - Devices Monitor] ADB Connection Error: An existing connection was forcibly closed by remote host

[2011-03-28 17:46:34 - Device Monitor] Connection attempt: 1

[2011-03-28 17:46:36 - Device Monitor] Connection attempt: 2

[...]

[2011- 03-28 17:47:53 - Device Monitor] Connection attempt: 10

[2011-03-28 17:46:54 - Device Monitor] Connectors Trial of Action: 11

[2011-03-28 17:47:00 - ADB]

[2011-03-28 17:47:00 - ADB] This application has Requested to end the runtime abnormally. [2011-03-28 17:47:00 - ADB] Please contact the application's support team for more information. [2011-03-28 17:47:04 - Device Monitor] ADB Connection Error: An Existing Connection Was Forcibly Closed By Remote Host

[2011-03-28 17:47:05 - Device Monitor] Connection attempt: 1

[2011-03-28 17:47:07 - Device Monitor] Connection attempt: 2 < P> etc, etc ... it forever loop. If I start eclipse and then connect to the phone, or if I connect to the phone and then start eclipse then it does not make any difference.

I do not think this should be the case, but my phone is an inspiration 4G. Originally Revolution 4G 3.2 is running

This patch ADB version worked fine for me (HTC Desire HD):

Comments