hi
I was suffering from the adb problems these days. I had installed the drivers ok and adb worked well once. But later, when I plug off my ADP1 and replug in, windows can recognize hardware installed, but "adb devices" list empty.
I tried reinstall all kinds of versions driver, but it still doesn't.
even with the new sdk1.5 driver.
I tried it in another computer, initially, it works fine.
But later, without any changes, it doesn't work. It's really confusing. This time even worse. When I tried to reinstall ADB COMPOSITE DRIVER, windows can not install it properly.
It seems many people have these problem when I googled it. But no solution works for me.
I am using windows xp32 sp3 and adp1.
I tried drive from sdk1.0 r1 r2 1.1r1 1.5pre.
I also tried converting androidusb.inf into DOS format.(some post said that), still doesnt work.
however, it works in my ubuntu 8.10 well.
I hope someone can help me
Thanks!!!
hi sorry but im not gonna post a solution cuz im having the same prob with XP. With Vista on my laptop, it works fine (not always that XP better than Vista)
Are you opening up command prompt/dos window as Administrator... and in Vista and Win 7 you have to make sure Digital Driver Signing is disabled at boot by hitting the F8 key directly after you select Windows OS Menu and then scrolling down and selecting the option in Advanced Boot menu.
i'm having the same problems in vista but hitting f8 doesnt do anything for me.
Related
Hey, I need some help plz.
When I am trying to use the adb command with push/pull/install agruments Windows crash.
I installed the usb drivers and the USB debuging option is enabled in the G1.
I tried it on 2 diferent machines (Win XP and Win2k3).
Does anyone know why it happen and how can I fix this?
btw how can I make my linux box (Fedora 8) recognize the G1 in order to use the adb command from my linux machine?
I don't know what's causing your issue, but recently someone here (the person who made the x64 adb drivers, thanks by the way) posted a copy of adb.exe that was "fixed" for people who were having trouble with it crashing. I don't know if it'll help but give it a try and tell us the results.
Tommy
10x alot
10x alot i will try this and update u
I think I have and idea what can cause this issue.
I tried again to use adb but this time on brand new Win Xp with SP3 and it worked just fine.
earlier I tried it on Win Xp with SP2 and Win2k3 maybe there is something in SP3 that adb need in order to run.
Hi guys,
I've just installed the Windows 7 ultimate RC on my PC and am now unable to sync my Raphael. I've installed Windows Mobile Device Center, but when I plug in my phone I get a message saying 'USB Device not recognized'.
I've tried both the stock rom and the Energy 3.0 ROM.
Anyone experiencing this also? Any solutions?
Thanks!
Same problem. But I couldnt even install the WDC? Which version did you install?
Weird
I'm using Windows 7 RC 1 (build 7100) and it works flawlessly with my TP. Installed WMDC 6.1 without difficulties.
PROBLEM FIXED for me
zonez said:
Hi guys,
I've just installed the Windows 7 ultimate RC on my PC and am now unable to sync my Raphael. I've installed Windows Mobile Device Center, but when I plug in my phone I get a message saying 'USB Device not recognized'.
I've tried both the stock rom and the Energy 3.0 ROM.
Anyone experiencing this also? Any solutions?
Thanks!
Click to expand...
Click to collapse
Try deleting this via regedit
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SQMClient\Windows\DisabledSessions
I'm using Windows 7 build 7077 and everything is going fine
Could you specify as to whether that key is located in Windows 7 or your phones OS?
brycestejskal said:
Could you specify as to whether that key is located in Windows 7 or your phones OS?
Click to expand...
Click to collapse
Sorry.In Windows 7
uh oh. i'm thinking of wiping vista from my machine and just using rc1. should i hold off on doing this?
Happened to me not 5min ago
1. Find the device in “Device manager” and remove it
2. Re-Plug in the device
3. A windows should try to install the software (Little popup in the task bar)
4. Click on it when it fails and tell it to check windows update to find drivers
I just installed RC1 last night. TP syncing just fine.
running windows 7...wmdc installed fine...
IF YOU ARE HAVING PROBLEMS SYNCHING!!
make sure to go into your phone settings
-go to connections
-go to usb to pc
-uncheck enable advanced network functionality
k thanks for the help guys, can't wait to get rc installed!
Thanks for the replies!
I tried all suggestions posted here, but none work.
The funny thing is that even when I put my phone in USB Drive mode, it still isn't recognized.
Updating the driver through windows update still results in 'An unknown device, your drivers are up to date'.
Syncing works without problems on my WindowsXP laptop..
The Muffin Man said:
Happened to me not 5min ago
1. Find the device in “Device manager” and remove it
2. Re-Plug in the device
3. A windows should try to install the software (Little popup in the task bar)
4. Click on it when it fails and tell it to check windows update to find drivers
Click to expand...
Click to collapse
This really worded for me. I installed Windows 7 the first day it was available and I was never able to figure it out how to make it worked until today. Thank you "The Muffin Man"
Running windows 7 RC and first few days when plugged phone in nothing happened. Was in no rush to get sync working as dual booting with Vista and was just plugging to charge phone. Other day I got a prompt to install device centre 6.1 and never done anything to initiate this. Wonder if an auto update may have caused this?
Works perfectly for me and tried with both Energy 3.0 and Elite RC4 (WM6.1 and WM6.5 ROMS).
In Vista atm so don't have W7 build number to hand.
I had a similar issue a few weeks back on my xp rig. Turns out I just needed to re seat my micro sd card, worked instantly.
nhshah7 said:
uh oh. i'm thinking of wiping vista from my machine and just using rc1. should i hold off on doing this?
Click to expand...
Click to collapse
go for it.. everything works great.. love the device support! plug in ur printer and thats pritty much it
Uninstall the "Windows Mobile Device Center" in your Control Panel, and plug your phone in again
Well i'm one step closer to fixing this..
I went into my bios and disabled USB2 (switching back to USB1).
After reboot my device was recognized and synced without problems.
As soon as I enabled USB2 again the device was undetectable again, even though Legacy USB support was enabled.
All other USB devices work, both in USB2 as USB1 mode.
Needless to say I don't want to run in USB1 mode.
Since I didn't have any of these problems with WinXP I assume it's a windows 7 issue.. Anyone knows where I can report this?
zonez said:
Well i'm one step closer to fixing this..
I went into my bios and disabled USB2 (switching back to USB1).
After reboot my device was recognized and synced without problems.
As soon as I enabled USB2 again the device was undetectable again, even though Legacy USB support was enabled.
All other USB devices work, both in USB2 as USB1 mode.
Needless to say I don't want to run in USB1 mode.
Since I didn't have any of these problems with WinXP I assume it's a windows 7 issue.. Anyone knows where I can report this?
Click to expand...
Click to collapse
Sounds like a driver support issue with your USB device (Motherboard).
I just installed WMDC and it worked without any problems.
I recently crashed my vista hard drive and decided to give windows 7 a try, its working wonders right now. The only problem is that I'm trying to put Nandroid back up on my computer again. I am at the step of trying to get the fastboot loader. It worked on Vista, but now it is saying that the "Driver is not intended for this platform." Is that due to windows 7? Is there a work around for this? Any help would be amazing, thanks.
I used Fastboot on Win7 7100 build yesterday, and it worked fine. Did you set everything up according to this post:
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2
This is all that I did, and everything worked flawlessly. Good luck.
hmm..yeah, i did do everything according to the tutorial exactly, do you have email, aim, gmail, etc? could you help me?
use the newest driver in this SDK..
http://developer.android.com/sdk/1.5_r1/index.html
If you dont see the ADB Device or whatever its called in the device manager you need to delete a generic volume and scan for hardware changes.... HTC talks about it here. I had to do it also...
http://www.htc.com/www/support/android/adp.html
Troubleshooting
fastboot.exe (on Windows) doesn't detect the ADP device properly
In some cases, Windows detects the ADP1 bootloader as a USB mass storage device, preventing fastboot.exe from accessing it. To resolve the issue, you can dissociate the USB Mass Storage driver from your ADP1 on your Windows machine and install the proper driver instead, as described in the steps below:
1. Boot the device into fastboot mode, as described above, and connect the device to your machine over USB.
2. Navigate to Start > Control Panel > System > Hardware > Device Manager > Universal Serial Bus Controllers. Observe that the ADP device is listed as a USB Mass Storage Device.
3. Right-click USB Mass Storage Device and select Uninstall. Windows then prompts you with a "New Hardware Found Wizard" message. If Windows doesn't prompt you, you can manually re-detect devices by selecting Action > Scan for hardware changes.
4. Install the USB driver included in the Android SDK, as described in Setting up a Device for Development on the Android Developers site.
thanks southsko, i'll try this and let you guys know how it works.
I tried your method Southsko, but it didnt work for me. I think the problem is that windows 7 refuses to install the driver for the htc dream, because its not "intended for this platform" is there a way to force it to install the driver? or manually install the driver?
When I wrote that tutorial it was using Windows 7 beta. I have also used it since I upgraded to Win7 RC, so I know that it can work. Did you make sure to install driver when the phone is connected and booted to the boot loader screen? Windows sees the phone as a different device when connected normally and at the boot loader. When I installed the driver It popped up with the message that it was for a different version, but it gave me an option to install it anyway. Are you logged in to Windows with admin rights?
i had the same problem earlier tonight, i figured since i was running win7 i might as well try using the virtual xp out. I started the VM up and the attached the phone using the drop downs and it worked flawlessly.
yup .. it's working fine for me too.. if you are using 64 bit version ... u need to use the 64 bit usb driver too... u can get it here
http://forum.xda-developers.com/showthread.php?t=446274
Also you may have trouble installing it in Windows 7 unless you turn off driver signing at boot menu. Hit F8 and select no driver signing and you should be able to install it no problem... u will also have to disable driver signing each time you plan on using adb/fastbboot
foxlin said:
I tried your method Southsko, but it didnt work for me. I think the problem is that windows 7 refuses to install the driver for the htc dream, because its not "intended for this platform" is there a way to force it to install the driver? or manually install the driver?
Click to expand...
Click to collapse
When choosing the driver software, make sure you select the "x86" folder instead of usb_driver or any parent folder. This is because the wizard search sub directories in alphabetical order, and will stop when it find the driver for x86-64(amd64). Then it will simply tell you "not intended for this platform" without looking in the x86 folder.
Also, you do not have to disable driver signing for this to work.
trmacdonal said:
When I wrote that tutorial it was using Windows 7 beta. I have also used it since I upgraded to Win7 RC, so I know that it can work. Did you make sure to install driver when the phone is connected and booted to the boot loader screen? Windows sees the phone as a different device when connected normally and at the boot loader. When I installed the driver It popped up with the message that it was for a different version, but it gave me an option to install it anyway. Are you logged in to Windows with admin rights?
Click to expand...
Click to collapse
I am in bootloader mode, and I am an admin. It didn't give me the option to install it anyways. That is interesting. I am currently still using the windows 7 beta. I have tried manually selecting the specific driver files. It is still not working, any other ideas?
I finally got it! thanks everyone. The solution was instead of having it search through the files, there is actually an option below it to pick the driver from a list, the list wasnt the right one originally, then i manually changed the directory and it worked. Thanks for the help everyone!
billc.cn said:
When choosing the driver software, make sure you select the "x86" folder instead of usb_driver or any parent folder. This is because the wizard search sub directories in alphabetical order, and will stop when it find the driver for x86-64(amd64). Then it will simply tell you "not intended for this platform" without looking in the x86 folder.
Also, you do not have to disable driver signing for this to work.
Click to expand...
Click to collapse
How come when I installed this on Beta I got the message that I could not install a non-digitally signed driver? I was not able to install it myself until I disabled it at boot... maybe the 32 bit version is signed.
Has anyone else using XP had any issues installing the USB Driver for the Magic? I've tried every possible method to get it to work and it just will not install. A method that appears to work for some is in this link-
http://www.mail-archive.com/[email protected]/msg09692.html
Although this did not work for me. There was also a suggestion of copying the inf file and renaming certain strings by one digit. Any suggestions?
I used the latest SDK with the included driver. Set the environment paths. Nobody has any other suggestions?
renaming the inf file solve the prob for me.
radonsg said:
renaming the inf file solve the prob for me.
Click to expand...
Click to collapse
What did you rename it to? I renamed it to android_usb_Magic.inf like the linked post said.
Hi Gimpeh
This worked perfectly for me. The issue was once it installed the Windows drivers there was no way back. However, follow this
So you plugged your Android phone into your Windows machine having forgotten to switch on USB debugging…
Menu > Settings > Applications > Development > USB debugging
Then Windows detected your device as a USB-Mass storage device and won’t change the settings, regardless of how many times you uninstalled the device. Thread on it here.
This solution worked for me and didn’t require editing the registry settings (I don’t know if the reboot is unnecessary).
(1) Plugin phone
(2) Uninstall any drivers that mention “HTC Android Mobile USB Device”
(3) Unplug phone and restart
(4) Install and run USBDeview
http://www.nirsoft.net/utils/usb_devices_view.html
(5) Using USBDeview find the Android device (for some reason Windows hides uninstalled drivers instead of deleting them), right click on it and uninstall.
(6) Follow the official instructions to the letter this time.
http://developer.android.com/guide/developing/device.html
Click to expand...
Click to collapse
http://blog.zedray.com/2009/06/16/when-adb-won’t-detect-your-android-phone…/
Good luck!
This is pretty close to the instructions I followed earlier. No resolution. All HTC device drivers have been removed. Although there is a composite USB device installed (not labeled HTC). I know sometimes if windows does not recognize a device it will show it as a composite.
Install HTC Hotsync - http://www.htc.com/sea/SupportViewNews.aspx?dl_id=573&news_id=169
Have your phone plugged in first then install the app. You don't need the additional drivers it list. Just the Hotsync program.
That did the trick for me.
edit the inf file under the x86 folder inside the usb driver.
replace the vid_0bb4&pid_0c02 with vid_0bb4&pid_0c03
cos somehow my htc is recongnise as vid_0bb4&pid_0c03 instead of vid_0bb4&pid_0c02.
Hotsync didn't work and neither did replacing the string from 02 to 03. I got it to recognize at work on a Vista machine but since then it will not recognize on my home XP or any other Vista machine. When I select Have Disk and select the INF file it says something to the effect of There is no driver information for this device.
Additional Note: Although the device was recognized on that one vista machine, it would not recognize when it was in HBOOT mode.
try to search your registery using the string "vid_0bb4&pid_0c0"
and c wat is your system detecting it as and edit the inf accordingly.
radonsg said:
try to search your registery using the string "vid_0bb4&pid_0c0"
and c wat is your system detecting it as and edit the inf accordingly.
Click to expand...
Click to collapse
CTRL+F Put in that key and found nothing.
I also have the same problem, just with Vista. Happened after I plugged in the phone the first time without the USB dev debug enabled. I tried a lot of things such as the mentioned USBDeview software and so on. None of the methods have worked. So I am using my Linux laptop to do stuff on the phone.
I guess the only sollution is to reinstall the OS, Windows is very strange a lot of times.
Cheesebaron said:
I also have the same problem, just with Vista. Happened after I plugged in the phone the first time without the USB dev debug enabled. I tried a lot of things such as the mentioned USBDeview software and so on. None of the methods have worked. So I am using my Linux laptop to do stuff on the phone.
I guess the only sollution is to reinstall the OS, Windows is very strange a lot of times.
Click to expand...
Click to collapse
How would you go about flashing the recovery.img in Ubuntu. I didn't see any drivers for linux.
Driver
http://developer.android.com/sdk/1.5_r2/index.html
Additional work for linux(add rules)
http://developer.android.com/guide/developing/device.html
I finally figured the damn thing out. For some reason windows recognized the ION as a Video device and installed it as such. I figured it out after I got irritated and just uninstalled everything that wasen't plugged in.
woa.
TT is strange. Which version of windows? vista or xp?
Its XP Home on a HP Mini. I'm glad I finally have it figured out. I've probably spent 20 hours on this issue alone. I even went to Ubuntu since Windows was being...well windows.
I'm trying to connect my device under Android and I'm having problems.
Windows 7 actually detects it and I select the right x64 drivers, but when it is installing them, the progress bar keeps going forever while it says "Installing the driver software...".
The only way to close that window is to unplug the device. Then, the driver appears to be installed, but it's not.
What up with the driver?
Have you tried modify driver from G1 post for example, I remember i used modify version.
imfloflo said:
Have you tried modify driver from G1 post for example, I remember i used modify version.
Click to expand...
Click to collapse
After days of trying a lot I'm almost crazy because of this issue!
I don't know what the problem is, but I discovered that the my Polaris, when it's connected under Android, prevents the system from shutting down! I mean, if I choose to shut down my Windows 7 x64, it doesn't shut down until I disconnect my Polaris.
It happens the same when I boot my computer: it I have my Polaris connected, it doesn't boot. When I remove it, it boots as usual.
I switched the USB cable, the USB socket, and it's the same. But under Windows Mobile, it works like a charm
My Android OS is this one: http://forum.xda-developers.com/showthread.php?t=591104 (updated yesterday).
So, the problem is not the drivers, it's Android itself!
Hi
have you tried installing "PdaNet for Android" just (follow those steps)