I have been searching for several hours, and I am absolutely unable to get ADB to recognize my phone using Windows XP 64 bit. I have uninstalled and re-installed the Unrevoked modified drivers several times to no avail. All I get is "Error: Device Not Found". Does anyone know a trick to getting ADB working on XP 64? I appreciate any and all help.
Thanks!
EVO HW 0003
HBOOT 2.10
MIKFROYO 4.4
Make sure the rom your using has adb functionality included/enabled in the rom.
And make sure usb debugging is enabled under settings/applications
Swyped from a galaxy far far away......
I have connected to the same phone with another computer. All settings are confirmed correct on the phone itself.
I know a trick, but I haven't tried it with the Evo or XP! I bet it works though. I used it to get my hero working with win7 last march, and it worked great.
install PDAnet.
It is a tethering program and has the ADB drivers, should set them up for you.
Also installing HTC sync is supposed to get the drivers working.
Thanks I will give that a shot and report back.
PDANet didn't work but I found an HTC driver for 64 bit windows 7 that did the trick.
Thanks for your help.
Windows sucks and 64 bit XP is a pain in the ass. You need a usb driver or linux.
sixspeeder said:
PDANet didn't work but I found an HTC driver for 64 bit windows 7 that did the trick.
Thanks for your help.
Click to expand...
Click to collapse
can u post the driver.?
Here it is. Be sure to uninstall any other drivers. I used USBDeview to uninstall the old drivers. Extract this zip and use the driver inside for Android 1.0 when prompted. It will not show up as Android ADB in Device Manager (showed up as My HTC Phone or something on mine) but ADB connected immediately once I installed this driver.
I doubt that it will work
Works for me!
Been looking at this for two hours now...
Running 64-bit XP - Installed the drivers manually by connecting the device, then selecting not now.... navigated to the drivers, installed BOTH .ini files - not sure if was really two different drivers or not - restarted, reconnected and device showed up.
The name my device function says "Desire" but it seems to work so far (only one sync)
Hello
I am really struggling with trying to get the KF drivers installed on ANY Windows 7 x64 computer.
I have access to a Windows 7 32-bit computer at work. The drivers from the KFU installed absolutely fine on that without issue, first time.
But at home, I only have Windows 7 or Windows 8 64-bit computers. I have tried searching XDA up and down, edited inf files, tried to manually install drivers, even wasted an hour installing JDK / SDK as suggested on some forums.
Nothing works.
If anyone has come up against this and solved it, I'm all ears.
TIA
Loobster said:
Hello
I am really struggling with trying to get the KF drivers installed on ANY Windows 7 x64 computer.
I have access to a Windows 7 32-bit computer at work. The drivers from the KFU installed absolutely fine on that without issue, first time.
But at home, I only have Windows 7 or Windows 8 64-bit computers. I have tried searching XDA up and down, edited inf files, tried to manually install drivers, even wasted an hour installing JDK / SDK as suggested on some forums.
Nothing works.
If anyone has come up against this and solved it, I'm all ears.
TIA
Click to expand...
Click to collapse
I couldn't help you much on the Windows side of things, but have you looked into creating a Linux LiveUSB and running SoupKit to get ADB and fastboot working?
Loobster said:
Hello
I am really struggling with trying to get the KF drivers installed on ANY Windows 7 x64 computer.
I have access to a Windows 7 32-bit computer at work. The drivers from the KFU installed absolutely fine on that without issue, first time.
But at home, I only have Windows 7 or Windows 8 64-bit computers. I have tried searching XDA up and down, edited inf files, tried to manually install drivers, even wasted an hour installing JDK / SDK as suggested on some forums.
Nothing works.
If anyone has come up against this and solved it, I'm all ears.
TIA
Click to expand...
Click to collapse
This is due to driver signature enforcement on x86-64 versions of Windows 7 & 8.
The way around this is to disable that feature.
This is what you'll need to enter into an administrator cmd session:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Note, that does come with some security risks of course since unsigned drivers can then be installed, but in all honesty if you have your system secured properly otherwise it's not much of an issue.
That will allow the drivers to be installed. Note this is just for Windows 7. Windows 8 is an entirely different beast in how to handle this scenario.
Edit - No that's not a typo in the lines above about the DDISABLE part. It's meant to have both D's there.
Morpheus Phreak said:
This is due to driver signature enforcement on x86-64 versions of Windows 7 & 8.
The way around this is to disable that feature.
This is what you'll need to enter into an administrator cmd session:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Note, that does come with some security risks of course since unsigned drivers can then be installed, but in all honesty if you have your system secured properly otherwise it's not much of an issue.
That will allow the drivers to be installed. Note this is just for Windows 7. Windows 8 is an entirely different beast in how to handle this scenario.
Edit - No that's not a typo in the lines above about the DDISABLE part. It's meant to have both D's there.
Click to expand...
Click to collapse
Thanks Morpheus. I'll try that later. And I am wanting to use my Windows 7 laptop.
I'll feed back if it works or not.
No dice.
I don't think it's that the driver isn't signed, it just says no driver found for the Kindle Fire when I connect it up.
It searches WU and doesn't find anything. Then if I manually try and update the device in device mangler, it tells me there is no driver in the drivers folder in the KFU folder.
I have an image of the drive before I ever connected the KF, and before I installed the KFU.
I wonder if I ghosted back to that image, then turned off unsigned driver blocking, then installed KFU, if it would work.
Loobster said:
I have an image of the drive before I ever connected the KF, and before I installed the KFU.
I wonder if I ghosted back to that image, then turned off unsigned driver blocking, then installed KFU, if it would work.
Click to expand...
Click to collapse
Go ahead and roll it back. Then...
In the install_drivers.bat that comes with KFU (right click, select edit), there is a line that says:
Code:
start .\drivers\dpinst64.exe
Change it to say:
Code:
start .\drivers\dpinst64.exe /lm
(obviously for a 32 bit system you would change the "dpinst32" line)
Save the file and run it with the Kindle Fire unplugged.
Next, open a command window and enter the following (you may have to run the command window as admin):
Code:
mkdir .android
Open your user directory and confirm there is a folder named ".android", then copy the "adb_usb.ini" from the Kindle Fire Utility folder into that ".android" folder. Plug your Kindle in, select "disconnect" and you should be able to send adb commands or use the KFU with no problem.
Nope.
I don't get a 'disconnect' option (I take it I should be seeing that on the Kindle Screen?).
I realize though that I omitted some information (sorry) that may make a difference. The KF I am using to connect at home is one that has already been rooted and has the bootloader and Jellybean installed. I guess I might get the 'disconnect' option if I still had the stock Kindle ROM installed.
I don't know why that would make a difference as to why the driver won't install though. I just get the same thing ..... Windows searches WU, doesn't find a driver, and reports driver not installed on the second Kindle item.
I have one item which is installed properly and called 'Amazon Kindle Fire' and is under 'Portable Devices' in Device Mangler. The one that has no driver is under 'Other Devices' and is also called 'Amazon Kindle Fire'. From what I remember of the installation on 32-bit Windows, it seems that this is the version that relates to ADB.
I am about ready to give up on this nonsense and load up a spare HDD with Windows 7 32-bit just for when I want to root these devices and do general tasks with them. I could just swap the HDD in when I need to. A pain, but I'm losing the will to live with this ridiculous driver issue.
Thanks for your help guys.
Ok, so maybe it's not Windows 7 x64.
I installed 7 x86 on a spare disk in the laptop, and it does EXACTLY the same thing, and I cannot use the KFU.
I have no idea what is different about my work Windows 7 32-bit laptop, but apparently it's the only computer I can get the drivers to install to, and get KFU to work on. I've tried four Windows 7 x64 builds and two Windows 7 x86 builds. Only my laptop at work, works.
<sigh>
Loobster said:
I realize though that I omitted some information (sorry) that may make a difference. The KF I am using to connect at home is one that has already been rooted and has the bootloader and Jellybean installed.
Click to expand...
Click to collapse
Yes, it would've been helpful to know this ahead of time.
Do you know what ROM is installed? Look under "About Tablet" in the Cyanogenmod or AOSP Version.
It's Hashcode's release, of 4.2.2.
Kernel Version
3.0.50+
[email protected] #5
Tue Feb 12 23:04:41 PST 2013
Build Number
full_otter-userdebug 4.2.2 JDQ39 eng.hashcode.20130212.152604 test-keys
Loobster said:
It's Hashcode's release, of 4.2.2.
Kernel Version
3.0.50+
[email protected] #5
Tue Feb 12 23:04:41 PST 2013
Build Number
full_otter-userdebug 4.2.2 JDQ39 eng.hashcode.20130212.152604 test-keys
Click to expand...
Click to collapse
Different ROMs and different recovery builds can have different hardware IDs. When you plug your device into USB, you need to go to the device manager and check the hardware ID of that particular build by right-clicking on the device and selecting properties. Under the details tab, there is a drop down menu...select "Hardware Ids". You should see something similar to the following:
Code:
USB\Vid_1949&Pid_0007&Rev_0216&MI_01
USB\Vid_1949&Pid_0007&MI_01
In the KFU drivers folder, there will be a file called "android_winusb.inf" that needs to be edited to accommodate the hardware ID listed for your particular build. Since you are on a 64bit system, you need to add to the Kindle section under "[Google.NTamd64]". For the above example, you would add the following to the "android_winusb.inf", and save it.
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
Your hardware ID may be different so pay attention to what you are doing. Then go back to the device properties, select the driver tab and update your drivers. From here you should be able to manually install the "android_winusb.inf" by selecting "choose what drivers to install", "Have disk", or however it's laid out on Win7. You may need to do the same for any new ROM you install and you may need to do it for custom recovery also.
I see.
So when a KF is flashed with a different ROM, it presents to the PC as a different hardware string in device mangler, even though it's the same physical device.
That makes sense now since I've rooted two different KFs on the work laptop without any issue, using the same [or very similar] ROM.
I guess that also means that if I attached a KF with a stock Amazon ROM installed, it may well just work fine. I don't know if it's possible to roll back to the stock Amazon ROM. I did take a backup with TWRP before installing the custom ROM.
I will editing the files with the new hardware IDs on the laptop at home and see what happens.
Thanks!
Loobster said:
I see.
So when a KF is flashed with a different ROM, it presents to the PC as a different hardware string in device mangler, even though it's the same physical device.
That makes sense now since I've rooted two different KFs on the work laptop without any issue, using the same [or very similar] ROM.
I guess that also means that if I attached a KF with a stock Amazon ROM installed, it may well just work fine. I don't know if it's possible to roll back to the stock Amazon ROM. I did take a backup with TWRP before installing the custom ROM.
I will editing the files with the new hardware IDs on the laptop at home and see what happens.
Thanks!
Click to expand...
Click to collapse
Just keep your android_winusb.inf and append new hardware IDs every time you switch to a different ROM or device, then manually install it again.
It worked! Thanks a lot Soupmagnet. KFU sees the KF as online and all is well.
I learned something about driver installation and hardware IDs also.
Hopefully this thread will help others coming up against the same issue.
Had a scare tonight, my KF would not turn on! I thought it had failed right at the point when I had an answer. I did the holding down the power button for 30 seconds things, and it powered on with the next press of the power button.
Thanks again all who contributed to the thread.
I had the same trouble
But here is how I got it working- http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Hi All,
I have been unable to get my oppo n1 (CM edition) to connect to my home PC (win8 x64). This is annoying as my work PC (also win8 x64) detected and interacts fine with the MTP end point on the phone when connected via USB cable.
Could someone take a look at their drivers when their phone is connected and if possible zip them up for me? i would grab the ones from my work place but it just when friday afternoon and i cant believe this is such a hassle for me.
for the record, my home system currently detects the oppo as USB\VID_22D9&PID_2764\58E10EA
all the other drivers i have found are either for the ADB end point or some other PID.
no, secure boot is too much hassle as wrangling inf files can wait till monday i guess.
TIA to anyone that responds.
ms_comp_mtp
welp i think i have traced this down to a strange fault in just my own PC.
tested my oppo on a win7-x64 machine - installs fine.
I am comparing the setupapi logs to see any divergences and have found one.
my win8 box windows is not "seeing" the usb\ms_comp_mtp "compatible ID" (this is the magic that allows one driver to match many different VID/PIDs, thus a generic MTP driver should work for anything that advertises it self as MTP).
Now for the hard question of why that isnt being sent/seen by my box...
also to add to the mystery - PTP mode works fine, just MTP gives me grief.
While my own journey is far from over, ive learnt the C:\windows\inf\setupapi.dev.log file is quite useful for assisting in figuring out what isnt working when it comes to device driver installations.
I am happy to have a mod close this off, given this problem appears isolated to just my machine.
Has anybody gotten the Sony's official usb drivers to work? Its somewhat mandatory for xperifix et all.
I tried it on 2 completely different machines.
On win7 x64 box the driver complains about Error 10 - This device cannot start.
On a win10 enterprise thinkpad the error is similar:
"This device cannot start. (Code 10)
The specified request is not a valid operation for the target device."
I am starting to suspect that the drivers are faulty. FWIW the thinkpad has NEVER seen *ANY* adb/android/sony drivers before.
This is the "Sony sa0118 ADB Interface Driver" btw. Installed as a legacy device as per Sony's instructions. Driver is already not working before a device is connected. Device is subsequently also not recognized. Device works perfectly fine in flash mode on my Linux notebook, just not both windows boxes Ive tried (sadly Windows is required for Xperifix)
You use the drivers that comes with flash tool? Those are working for me without any trouble on Win10
juandiazmora said:
You use the drivers that comes with flash tool? Those are working for me without any trouble on Win10
Click to expand...
Click to collapse
tried these and they got me a little further - but not very. On first connect of the xz2c in "blue" mode Windows said something along the lines of configuring new device: Android. So far so good. Then started xperifix, which found the device and started to get device information during which it crashed (program got stuck, no .NET exceptions or anything). Now even 2 reboots later the phone is no longer recognized, I assume xperifix somehow borked up the fastboot drivers?
PS: the constant more often than not non-working recaptchas are getting a little annoying..
The drivers have to be installed in testmode on Windows 8-10. In Windows 7 it should work "out-of-the-box". And yes, I know I'm answering to one year old question, but it could be helpfull to someone one day. Maybe.
Hi, I am trying to connect my 1P7T to Windows 7 and 10, both in Virtualbox guests. But I cannot get the prompt to come up on the phone. It connects just fine to the Linux host, but not to Windows, it has worked before when I had my system on a different version of Linux but not now. Unless there is some better way to run fastboot commands on my phone in Linux, I am all ears. But I would really like to just use the All in one tool in windows.
Thanks
Got it all figured out, first I had the wrong Virtualbox extension pack installed. I still could not get it to work when set to USB 3.0. I set it to USB 2.0 and the phone is now connected and authorized.
Glad I figured it out on my own, but also good for someone else to know.