ADB Install over USB in Windows

Not intending to provide an answer, just a comment from link I found.

I found next link when searching for other information, it should help to check to use correct values,

http://processors.wiki.ti.com/index.php/XDS100#Q:_How_can_I_check_if_the_VID.2FPID_for_the_EEPROM_are_programmed_correctly.3F

other could be to download latest drivers for both, Android USB,  I think Android USB information is in next links. Try to update Eclipse plugins and Android SDK code if you are using either or both of them, sometimes code change between Android releases there is backwards compatibility.

http://developer.android.com/tools/extras/oem-usb.html

http://developer.android.com/sdk/win-usb.html

in the first link there is a troubleshooting section, don't follow update or programming instructions unless you check that it is needed, first link shows how to check the values, that is the same information provided from second link about it.

I updated all the plugins and drivers. I also corrected the FTDI issue, by using Mprog and the FT2232H.ept file. Now I have the following ports showing: 

TI XDS100 Chanel A

TI XDS100 Chanel B

Universal serial port (com10)

On the channels I have VID_0406 and PID_A6D0 which I think are the correct ones. But still after adding the 18D1 to the adb_usb.ini and then going to select the driver gives the same error: "The specified location does not contain information about your hardware"

You mentioned using ADB for ICS, could you try moving to ADB for JB? some USB drivers can be found in the Android SDK downloaded from http://developer.android.com/sdk/index.html.

By following AM335x Starter Kit and USB driver,

In link

http://processors.wiki.ti.com/index.php/Sitara_Linux_Software_Developer%E2%80%99s_Guide

or

http://software-dl.ti.com/dsps/dsps_public_sw/am_bu/sdk/AM335xSDK/latest/index_FDS.html

sitara-linuxsdk-sdg-05.07.00.00.pdf

it mentions a modification for Beaglebone, read from page 3 in the table they show what values to use for this case when installing the SDK.

In this same document and next link it is mentioned to use FTDI driver, I tried to find a reference to FTDI driver in specific for AM335x, I mean to find what version of FTDI driver to use VCP or D2xx but I cannot find which one to use, only the reference to use a FTDI driver in previous 2 links.

Check to use correct FTDI driver?

The ADB comes as the part of the SDK and I have the latest API 17 and the latest USB driver rev 7

And I'm also using the correct FTDI.ept as that issues was resolved in the following link: 9th post

http://e2e.ti.com/support/arm/sitara_arm/f/791/t/234074.aspx

The pdf you referred me to is for a Linux host based serial connection using the Linux sdk and I think it is old as it says that the camera application is not available on the  AM335x which is not the case. 

Any other suggestions? 

I really think that the issues lies within the USB driver, may the VID or PID.  

From my side I have no other suggestions.

I Upgraded my phone to Jelly Bean today to see if there is an issue with the ADB but it showed up on the list of available devices. 

I have to present my application, is there any way I can push my apk to the device. Please help. 

One way is to select "unknown sources" option from Security menu in settings, this to allow the application to run without signing, and you can use adb push to /system/app or you can use adb install to install it correctly, it gives you some options to reinstall it in case of needed. If you don't select "unknown sources" using adb install will not success, and if you manage to use adb push apk will not run. From ICS it is possible to install APKs from SDCard too, but it requires to change some settings too if it is not enabled by default.

From Eclipse you can click run it will upload and install it to the found device, you can debug it too, the debug perspective will be activated when clicking it.

For other uses when needed there is a signing procedure that you can access using Eclipse and Android SDK giving right click in project window over project and then look for signing option, or you can use signing procedure from http://developer.android.com/tools/publishing/app-signing.html.