Manual installation of the ADB driver

I want to share with you a simple way to install the ADB driver under Windows. This article will be needed for those who do not install this driver at all, or install it, but adb still doesn’t see the device (it was mine), or you didn’t find this driver. So all those who have / had similar problems, or who are just interested, please under the cat.

I'll start with the background. I decided to buy an inexpensive tablet on Android for reading books (DJVU / PDF), and the choice fell on a Russian-made device of course Chinese-made TeXet TM-7025 . Toad pressed to buy something expensive, but for a simple reading of books, some super-characteristics are not required. Later, I discovered that most of the toys are good for him, it is convenient to climb in the internet while you are sitting in da kabin , etc. And since I was learning about Android before me, I decided that it would be very convenient to use an iron device for this instead of anguish with emulators .

And here I was waited by an unpleasant surprise - whether the native driver turned out to be crooked, or Windows, or the wire ... in general, the driver then got up, the Windows device manager reported on the device’s full functionality, but I received an empty list on the adb devices request and Naturally, the test application on the tablet failed.

I wrote a request to the TeXeT support service, they even answered me with a link to the driver itself, which, as I have already seen, did not work. I started looking for an answer on the Internet and found a bunch of different assemblies of this driver and manuals, but still none of them started up as it should, and even the native driver from the SDK didn’t get anyway at all, which discouraged me ... but not despair.
')
It was here that I decided to try my hand at writing drivers using the good old method of scientific typing and opened the driver inf-file. The hope was given to me by the understanding that the software part of the adb interface on the tablet side should be identical for all devices, and the USB worked anyway. And so, after several unsuccessful samples of manual editing of the inf-file, I found a recipe for treating the seasoning of the inf-file so that it was set up and, most importantly, worked.

So let's get started.

Step 1. Download the driver. If you haven’t already done this, open the Android SDK Manager, find the Extras section, tick off the Google USB Driver and click Install Packages. It's simple. Wait until it loads.

Step 2. Find the driver and make a copy of it in a separate folder. Go to the% android-sdk% \ extras \ google \ folder and you will see the cherished usb_driver daddy there. Copy it somewhere, and in the same place we will carry out further manipulations. In principle, you can edit the "original", but I preferred to keep the original intact for every fireman.

Step 3. Edit the inf-file. In the daddy, open the android_winusb.inf file and look for lines like this:

;Google Nexus One %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01 

We make a copy of these lines, replace Google Nexus One with % your_device_device_name% for identification in the future and ... open the Windows Device Manager. We are looking for our device there ( Android , Android Composite ADB Interface or something in this style). Open the properties of the device, the tab “Details”, select the item “Equipment ID” in the list and see the following picture.

Copy the line that is most similar to the one shown in the figure (It is, in theory, just a little shorter), and paste it into our inf-file.

 ;TEXET TM-7025 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01 

In% SingleAdbInterface% we delete the end of the line, as we see, in% CompositeAdbInterface% we insert the whole. It’s probably not necessary to repeat everything twice, but I’m already worth it and I’m too lazy to experiment :)
We remain (be careful - in some cases, for this you need to run a notepad with administrator rights, since in the user mode you will not be allowed to overwrite the inf-file).
Step 4. Install the driver. Now that everything is ready, we return to the device manager and remove all previously installed adb drivers (if any). We update the list of devices and see our device without drivers. Open its properties and select "update drivers", select the installation from the folder, specify the folder with the corrected inf-ohm and start the installation - our driver is instantly located, but during the installation it can swear about incompatibility with the question "Do you want to continue nayannek?". We continue. Everything, the driver is installed.
Step 5. Final. For accuracy, we take out the USB port, wait until everything is detected, open the console (Win + R, enter cmd ) and write adb devices . If everything went well - we see the cherished list item, indicating that adb now sees our device.

From this point on, you can safely run eclipse and build programs, enjoying the convenient automatic build, installation and debugging right on our device.

If the adb command doesn't work for you at all. Computer -> Properties -> Environment Variables. We are looking for the Path variable and at the end we write (in no case do not overwrite) the semicolon at the end, and then the address of the folder where adb lives (usually% android-sdk% \ platform-tools \). After a reboot, it should work.
Sometimes adb does not start automatically at system startup. Run manually.

What was it?
In fact, everything is simple. For some reason (Windows Mastday / Prog Hand Curves / Google Inf file was written only for native Google devices / Your computer was spoiled by Higgs bosons) Windows does not want to eat Google driver for non-Google devices that are not recorded in the inf file. Apparently, everything there is just tied to these ID-equipment. But after all, the software part on the vast majority of Android devices in the debugger connector to the PC is identical, because the driver must communicate normally with any Android device. Our task is to trick Windows and force it to take the device as “driver-suitable”, which we did by writing its ID in the driver's inf-file.

I hope that this manual will help someone to get their Chinese or other device, for which they forgot to make a normal adb driver when building the system, or those who are asked to download the official driver from the device manufacturer (this happens so much that it’s faster I was so with the driver for the phone LG E510).

PS I did not conduct mass testing of this method, so I can not guarantee that it will work 100% in all cases. But he earned it from me on Windows 7, and after that on Windows 8. The file had to be edited separately for each time, but I do not think that this is such a problem.