So, I got my nexus one yesterday, and right away got to rooting it. I'm running Windows 7 x64 ultimate, so I downloaded the drivers, set the phone to usb debugging, plugged it it and started to install the drivers manually.
I always get the same error message when installing them, "The style of the INF is different than what was requested". No one else seems to have that problem, and it's not the drivers (I tried with three different sets from different sources, including the Android SDK). So, oh great community, what is my problem, and what may my solution be?
HI,
I've had success installing my other android devices on my windows 7 x64 computer, have even used my (ADB) Nook Colour on a windows 7 32Bit laptop fine.
Problem: Android Composite ADB Driver wont install/ isn't found, Device is Auto Nootered on 1.1 using rooted stock firmware.
Tried:
I have the .android folder in my user profile dir with the device ID in it
Followed various wikis and guides (that worked for the 32Bit version)
Watched the driver load/unload in device manager as I tick 'Development Mode (enable ADB)'
Tried various driver packs from here and googles latest offering, still only matches up with Android ADB Driver not the Composite (wont even show me the composite one)
Wireless ADB works and is disabled, worried about installing CWM using wireless for some reason USB feels safer to me
Thinks I noticed:
Hardware ID is listed as USB\VID_2080&PID_0002 which matchs up with %SingleAdbInterface% in the ini file for the driver, composite aka %CompositeAdbInterface% has &MI_01 on the end. Not sure if that means its not getting the right hardware ID from the device when ADB/ Development mode is enabled of if having the wrong driver loaded on it shows up the wrong Hardware ID.
Things I havent tried, enabling ADB on the Nook using sqlite3 method, but if it works on another coputer didn't think it would be a good idea.
Plan:
Install CWM, flash CM7 or similar to device.
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
ouldsmobile said:
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
Click to expand...
Click to collapse
Same here!
This one is weird...
I'm on win7x64 and I *have* got adb to work at times. When I was first rooting my new NC (1.1.0), I fiddled with it and I had it running over usb fine. But now, when I plug in the usb and I either get that the device is unrecognized or it goes into usb sync mode. Haven't quite figured that out...
But, ultimately, I just use adb wireless for any adb stuff, although it's "not recommended". It's worked perfect for me all along.
Check this link
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
loupnook said:
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
Click to expand...
Click to collapse
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
UR Welcome and USB Automount?
NewZJ said:
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
Click to expand...
Click to collapse
Glad to help. What do you mean USB Auto Mount? I kind of thought that should happen?
My goal for getting adb working was to get su, which i got here http://forum.xda-developers.com/showthread.php?t=953110 with a bit of trouble but seems to work, so that i could drag items from my pc onto HC. I'm using http://forum.xda-developers.com/showthread.php?t=952456 to mount the media directory. I now seem to have su installed and the USM app is working. i only see my BN media directory from my pc now (yay) but i can't browse that directory from my nook HC (boo). So i can't share files between eggclair and HC. I'm a noob to nook and newbe to linux, so i'm assuming it is a permissions issue but don't have enough knowledge on how to change them yet.
I've installed DropBox but it keeps asking for an SD card, which isn't a big issue, just i haven't found the time to go buy one. Is there a way to use db without an SD card?
unfortunately no, db requires external storage. if you opened the apk to recode its default directory maybe but im not sure its possible
usb auto mount I can disable in nook tools but its a persistant system that defaults every reboot, I dont like to see it popup while using the nook when I plug it in just one of many peeves
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
GateheaD said:
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
Click to expand...
Click to collapse
I thought that as well and flashed back to the EC 1.0.1, sideloaded 1.1 update and repartitioned, used cw to add HC back and all that, and still had the same issue. Came down to the ini file not having a NookColor section.
Did you check the link http://forum.xda-developers.com/showthread.php?t=987409
I'm no stranger to drivers, I could force it to use the driver by changing the ini files but it still wouldn't appear in ADB Devices.
Flashed Nooky FroYo and now the device driver states the hardware ID has the missing '&MI_01' which means the composite driver works out of the box.
I used IOMonsters Easy USB installer and it seems to have installed the drivers for Windows 7 64Bit Fine
After running the install .exe I also had to execute the Inst64.exe
so i have a problem installing the wp7 sdk and developer tools. my system is windows 7 x64, a fresh install. I cant install the dev tools fully. i have tried the file from the msdn site, and it seems to install ok, but it does not install all the components and i am missing the wp7 dev tools. there is no error message or anything else to indicate a problem. after a few reboots, uninstalls and reinstalls, i tried the minisdk, and the setup runs and says 'gathering required information' then closes and nothing more happens.
I have tried hard resetting the phone, and have re-flashed it today
bump
still have this issue. on windows 7 32bit, it installs fine, so maybe it isnt compatable with 64 bit?
-Running windows 8.1
-Installed latest motorola device manager
-tried several usb ports
-using minimal adb
-moto x set to usb debugging
any help?
Try installing PDANet - http://pdanet.co/
The amount of times I've had driver problems (not just with Moto X) in the past, this thing always works. Once the driver's installed, you should just be able to uninstall the software, and the phone drivers should still be there.
If that doesn't work, follow this guide -> http://mark.cdmaforums.com/ADB.htm to install and configure ADB, and make sure you have the most up to date versions. Consider also installing the latest Google USB driver when doing so.
Also keep in mind, unfortunately there have been many with Windows 8/8.1 that have run into issues using ADB.
Please be sure to post back exactly what fixes/helps you so it can help others that might run into this issue.
Thanks all for the suggestions.
Looks like I fixed it by going in device manager and uninstalling the drivers. I uninstalled the ADB drivers (by showing hidden devices in device manager) and also the Motorola device.
Then I rebooted, and reinstalled motorola manager.
Windows 8.1, Rooted 4.4.4
I have recently done a factory reset and at some point my computer stopped recognizing my phone. If I let windows run through its own attempt at installing the driver, its recognized as a generic Samsung android device which Windows lists as a modem.
I have read the other xda threads, downloaded drivers from samsung site, kies, installed, uninstalled, rebooted, checked, unchecked options including USB debugging (which is not even what I'm trying to do), deleted all non-working driver instances in Device Manager, changed usb cord & port, tried other PC, removing microSD, all to no avail.
I have double-checked what I have frozen in Titanium Backup, but no relevant apps are affected. I tried wiping the cache/Dalvik cache, just because I thought it might help somehow. I'm thinking it must be a phone-side issue because nothing in windows is getting me anywhere. Has anyone here any ideas of what could be the culprit?
Did you try to connect to a different PC?