Database Develop

ADB Drivers

Hey everyone,
I have been happily using android on nand for quite sometime, and everything has been going well. However, I must have the wrong adb driver installed on my windows 7 computer and can't seem to remove it fully or install the proper one ever. Every time I remove it from device manager, and plug it back in, windows finds it as an HTC composite device, and adb through command line can't find any devices, ever! I would really like to be able to use this feature for things like tethering and what not.
Also, if anyone has any information on how to tether using any OS, windows, mac or linux, I would greatly appreciate it, along with any applications that might be helpful! I have done proxoid in the past and it worked well, pdaNet looks like it might work, but again I don't have a connection to my windows computer!
Thanks in advance for all of the help!

I am using the android SDK usb driver for ADB, you just have to edit a file and add the vendor ID. I can do things like adb logcat, adb shell gives me odd characters in directory listings,I get a ? from adb devices, not sure what that is about.
C:\Documents and Settings\Administrator\.android\adb_usb.ini
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x0e79
0x0bb4
The 0e79 is for my Archos tablet, works fine there. 0bb4 is what showed up in device manager when I plugged in the phone.

I tried to install that driver for my Polaris and it doesn't work.
It shows "Installing Android Phone" while I have my device plugged in. It takes forever and seems that the USB connection hangs the driver install process, but as soon as I disconnect my device, Windows shows me an error message.

Instructions for Vista\Windows 7
For WinVista/Win7
These OS will install Android as a mass storage device. You must uninstall the driver and update to the android driver model.
Instructions:
1) Unplug all removable devices(thumb drive, sdcards, etc) beside the Android phone.
2) Locate "Device Manager", usually under "control panel"
3) Select "Universal Serial Bus Controllers"
4) Select USB Mass Storage Device.
Note: to check if you have the correct device, click on the details tab and select "compatible ids" under properties. There should be three items listed under value.
5) Select uninstall driver
6) Close the window. Now in device manager a new "Android Phone USB device" with a yellow! will appear... If not, Unplug your android device or select Action -> Scan.
Note: view optional steps below if you still have problem with the your windows automatically installing drivers.
7) Click on the "Android Phone USB device"
8) Select "browse my computer to driver software"
9) Under "search this location for driver", Browse for the location that you have unzip the android_usb_windows and select the corresponding folder for your system(AMD64 for 64bit systems or x86 for 32bit systems. Right click -> properties on "My Computer" to check which system you have)
The driver is now installed and is ready to use.r
***Optional.
1. Go to System under Control Pandel.
2. Click on Hardware Tab and Under "Device Installation" select “Never search windows update for drivers”, then OK.
3. Go to Enable debugging on your phone. (Settings->Applications->Development->USB debugging).
4. Run USBDeview and remove all instances of Android Phone
5. Unplug your phone, and plug it in again.
7. Continue on step 7) above.
To turn off search windows update in windows 7, use this link below
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/
To turn off automatic driver installation in windows 7, use the link below
http://www.addictivetips.com/window...tomatic-driver-installation-in-windows-vista/

Unfortunately, it doesn't work for my Polaris. The whole driver installation process hangs while my device is connected. As soon as i disconnect it, it continues, but it then complaints about it being disconnected.

SuperJMN said:
Unfortunately, it doesn't work for my Polaris. The whole driver installation process hangs while my device is connected. As soon as i disconnect it, it continues, but it then complaints about it being disconnected.
Click to expand...
Click to collapse
mine hung as well, what i ended up doing was turnng off the automatic installation. Then uninstalled the adb interface driver that was already installed. Then turning back on automatic installation. Then plugging phone back in and as it was installing automatically, manually installing the adb interface driver at the same time. Eventally the automatic install would error out and the manual install would work. It took like 15 or 20 minutes for it to finish.
when i uninstalled the adb interface, it turned into ''android phone'' in device manager. That was the driver i manually installed while the phone was automatically installing. I know it dont make much sense but it worked for me.

It looks like that will be my fate as well. It also says, that when I do the manual install of the ADB drivers that I already have the most current version installed!!! OH well, keep trying!

Same behavior on my pc with windows 7 32-bits.
When I have lucky the adb driver is connected (working correctly) for a few minutes and then it's disconnected.

i've tried various things to install adb driver, since last night but i've got nothing. i can't install adb driver for my xperia arc.
i installed sdk manager and usb driver. but when i try to install or update driver, i always see this message like "you're using the latest version". So i can't install it.
and also i've tried to uninstall driver and unplugged / plugged my device. then w7 automatically install driver. so i can't install adb driver again.
i want to root my phone, using this way at this link http://forum.xda-developers.com/showthread.php?p=18805560#post18805560
so i must install adb driver, please help me.
thanks everybody
edit: i've windows 7 home premium, 64-bits

[Q] Driver problems

Struggling with getting any computer to recognize my I9000. Both XP and Win7 fails to load MTP USB device. That said XP is not complaining, it loads something that seems generic, "MTP Device" along with Samsung Android USB Modem and Samsung Android USB Composite Device
MTP Device uses files wpdusb.sys and wudfrd.sys . Is this right, or should the device look for diffrent drivers and what files SHOULD it use?

On win7 it displays "Android MTP" as opposed to "I9000" the few time it used to work.
Tried the alternative drivers.
Tried the long file extensions tips.

Did you try disbaling launcher pro / launcher pro? So stock tw launcher is working? And wiping the internal sd? Had issues, but this worked first time on win7
Sent from my GT-I9000 using XDA App

TWlauncher/Launcherpro is checked from the list many days ago yes, had it working with Kies only a few days ago (granted after a lot of "tricks" and then suddenly working for no obvious reason).
Been holding off the internal sd format and factory reset. Thats my next step.

No luck. In XP it shows up as "MTP Device" under "Portable devices". Is this how its supposed to look like, or should it be recognized as "I9000"?

And finally. Trick this time was to have Kies running (win 7), also battery where taken out once (telephone locked trying it in XP). Internal SD unmounted, formated, remounter and then factory reset in "privacy".

Snuble said:
No luck. In XP it shows up as "MTP Device" under "Portable devices". Is this how its supposed to look like, or should it be recognized as "I9000"?
Click to expand...
Click to collapse
Just finally solved the same problem for Windows XP. Here the solution:
- uninstall MTP device driver
- I don't know if necessary but I did - remove from windows all related files : wpdmtp*.*
- !!! download Windows Media Player version 11. It contains updated drivers.
- install the player
- connect your device
Now it's recognized in the Device Manager as GT-I9000. And Kies immediately connects to it.

For future reference, how did you uninstall MTP device drivers?
We wont be the last to have trouble with this procedure...

while device is connected you can click right mouse button on it and choose "uninstall"

[Q] Can't Get ADB To Install On Nook HD+

Well, here we go.
First of all, I'm hardly new to the world of ADB. I've got a Nexus 7 and a Kindle Fire. I've set up ADB successfully on those devices (even though The Kindle Fire was a pain). Hoiwever, I'm completely flummoxed by the NookHD+. I'm running Windows 8 x64, I've disabled Driver Signature Enforcement (twice, to be on the safe side), followed the steps on the Nook Developers website to the letter, but keep hitting a dead end. I've verified I've got the correct drivers (downloaded from the Nook Developers site), I've got Android SDK installed, I've verified the Vendor ID as 0X2080 in the adb_usb.ini file, and even have the Nook SDK installed. Hoiwever, when ever I try to update the drivers in Device Manager, it displays "MyNOOK," and if I try to update the driver, I receive the following message:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work for Windows with x64-based systems."
I've uninstalled and reinstalled the drivers, rebooted my system multiple times, disconnected and reconnected my device, tried different cables and ports, and still, nothing.
Any help would be greatly appreciated.

Anyone figure this out?

abarax said:
Anyone figure this out?
Click to expand...
Click to collapse
I don't know if I can help but I did succeed in installing the driver in win 8 x64. I got the B&N driver zip file from leapinlar's tips thread and followed the instructions from the B&N site. Nothing deviated much from their instructions except that I had to view hidden drivers in the windows device manager before I found "Other devices" and when I updated the driver I had to identify it as a Portable Device. I didn't connect the cable until the driver was installed. I do have certain developer options enabled on the Nook itself. I had previously gotten wireless adb working. For adb itself I needed to extract files from the most current Android SDK (leapinlar's older versions didn't work, at least not with CM 10.2).
BTW, I am totally new to adb.
Edit: Also, mine didn't say MyNOOK anywhere. It showed the device name in device manager, something like BN Nook HD+.
Sent from my Nook HD+ running CM 10.2 from SD card

[Q] Nook usb problems

Hey, I'll just get to the problem:
I got the last 10.2 on my nook hd+ (MBG4GA) with trim on (flashed the kernel trim zip)
I wanted to try the android Supercharger from this thread: http://forum.xda-developers.com/showthread.php?t=991276
I ended up unistalling the nook usb drivers (from device manager, MY NOOK, unistalled) and installing the google usb drivers to have a .bat script recognise the device from pc through usb. Unfortunately it didnt go as planned, so I decided to do it manually (getting the script on the nook and running it there from the script manager).
But unfortunately my pc does not see the device anymore. If I plug it in and disable debugging mode the computer plays the classic sound but it doesnt detect the storage, whereas before my "messup" it detected "MY NOOK", that had the 32GB mass storage and micro sd icons. So I can't put any file in there anymore.
In the device manager I only see "Android Phone", and, under this voice, lies "Android Composite ADB Interface".
How can I make my pc detect the device as before?

bump

Nolfer said:
In the device manager I only see "Android Phone", and, under this voice, lies "Android Composite ADB Interface".
How can I make my pc detect the device as before?
Click to expand...
Click to collapse
Try uninstalling those two devices and start fresh.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
Try uninstalling those two devices and start fresh
Click to expand...
Click to collapse
Thanks! that worked

Please Help: Device Enumeration Failed Windows 10

This is actually a whole issue other then that. I should start by saying I'm usually very good at flashing roms to stock but I recently screwed up. I'm running windows 10, my HBoot is 1.44, Cingular HTC One M7. I recently sold the phone, and upgraded to the newest version of Android Revolution. Everything was running great, moved my pictures to my computer.
The next part is where I guess I screwed up? My computer was reading the phone until I went into TWRP and formatted the Internal Storage trying to rid the rest of the files on my device before I ship it. I've done this before on my Nexus 6 with no issues.
Next thing I know the phone won't boot past the HTC screen, not a boot loop per say just stuck on the screen. Windows is reading the device and saying the "Device Enumeration Failed" thus making it so I can't sideload through ADB or run a RUU file or anything. Can boot into TWRP, can boot into fastboot and bootloader. I have tried uninstalling and reinstalling drivers to no avail.
If anyone can help me I'd appreciate it greatly.

EasyTiger6x13 said:
This is actually a whole issue other then that. I should start by saying I'm usually very good at flashing roms to stock but I recently screwed up. I'm running windows 10, my HBoot is 1.44, Cingular HTC One M7. I recently sold the phone, and upgraded to the newest version of Android Revolution. Everything was running great, moved my pictures to my computer.
The next part is where I guess I screwed up? My computer was reading the phone until I went into TWRP and formatted the Internal Storage trying to rid the rest of the files on my device before I ship it. I've done this before on my Nexus 6 with no issues.
Next thing I know the phone won't boot past the HTC screen, not a boot loop per say just stuck on the screen. Windows is reading the device and saying the "Device Enumeration Failed" thus making it so I can't sideload through ADB or run a RUU file or anything. Can boot into TWRP, can boot into fastboot and bootloader. I have tried uninstalling and reinstalling drivers to no avail.
If anyone can help me I'd appreciate it greatly.
Click to expand...
Click to collapse
What is your HTC listed as in Device manager when connected to your pc?
It may just be that you borked the drivers when you formatted the phone. In which case reinstalling the drivers won't help. You need to point device manager the driver you want it to use.
Try this
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install the latest :good:
Sent from my HTC One using Tapatalk

Danny201281 said:
What is your HTC listed as in Device manager when connected to your pc?
It may just be that you borked the drivers when you formatted the phone. In which case reinstalling the drivers won't help. You need to point device manager the driver you want it to use.
Try this
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install the latest :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. It comes up as Generic USB Device or something similar, I'm not home right now to check honestly. I've tried uninstalling all HTC drivers and reinstalling and plugging my phone back in and pointing it to the location of the "Updated" drivers I've found on the forum but it still reads Device Enumeration Failed. A warning message does come up when I plug the phone in saying the device has malfunctioned and can't be read or something along those lines as well.

Okay so I got the device to boot into the ROM but bow system UI keeps crashing and I'm not able to access the internal SD card to transfer files to it. Any suggestions?

EasyTiger6x13 said:
Okay so I got the device to boot into the ROM but bow system UI keeps crashing and I'm not able to access the internal SD card to transfer files to it. Any suggestions?
Click to expand...
Click to collapse
Have you any experience with Linux? That should cure the device enumeration error, since Linux doesn't require drivers for android devices.
Then you can use adb in recovery to repair the sd storage.
You can also do Format Data in twrp. But this will wipe the entire device including the Rom, so you will still need to sideload or something to get a Rom installed.
Sent from my HTC One using Tapatalk

Please consider this post : http://forum.xda-developers.com/showpost.php?p=69234983&postcount=6