Related
having trouble rooting.
I have installed all the drivers every guide has instructed me to do. I am able to command line my phone into "Fastboot Mode" but once I try and do a <fastboot oem unlock> it just sits there and says "waiting for device".
under my device manager it says "Android 1.0" drivers not installed. I have uninstalled and reinstalled all android and Samsung drivers 3 times including the entire Android SDK package. I cannot find any mention or link for Android 1.0 drivers on the net, this is super aggravating and I finally decided I need some help.
There were fastboot drivers floating around on another forum somewhere. Maybe droidlife. You should be able to use the adb drivers though. Device manager, update driver and choose manual option on bottom, show all devices and click have disk, choose the area you saved the drivers to. I had to do the same thing to get my fastboot to recognize my phone.
EDIT: It was here... http://forum.xda-developers.com/showthread.php?t=1392310
^ directions right there.
Under STEP 1 at bottom.. here is the other guide for your problem
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
DIRECT link to those drivers for the manual 1.0 install http://www.megaupload.com/?d=O6AVDE9B
thank you thank you thank you!
finally working. This is why I come to XDA! fast solutions to complicated problems
you guys are awesome!
Welcome
Just point people back to your thread if you see others struggling too
I'm going crazy here. I'm good with all this type of stuff but nothing is working. I want to return my phone to stock so I can exchange it for a new one at verizon. I keep getting the waiting for device error in fastboot. I had this problem a lot with trying to unlock it too. I'm not sure how I ever got it to work. I've downloaded and installed the drivers multiple times and still nothing. Can someone help me figure out what I'm doing wrong please?
I'm using windows 7 64bit. The drivers aren't right in device manager.
The drivers are fishy in windows 7 64bit. Download PDA net to your computer. It will install drivers correctly. Sounds weird but it works.
Sent from my Galaxy Nexus using xda premium
I've certainly noticed that they are pretty messed up on Windows 7. Unfortunately I've already done that and it still doesn't work.
Reboot your computer and plug the phone in and let the drivers try to install automatically, worked for me.
So I installed the driver a different way and it worked fine this time. I'm not really sure why I never tried that way before or why that way worked differently but it did! Thanks for the suggestions.
In what way did you install it? I'm having the same problem and it would be nice for search purposes.
i had issues with drivers on win7 64x, first, it would take for ever once the phone was plugged in, for windows to initially auto-install the drivers (after installing the ones from samsung)....a very long time. but, even after 3/4 of it installed correctly, i hadn't noticed that the Android 1.0 drivers didn't install at all. If you goto control panel->system->device manager, see if there is an alert next to 'Android', if so, open it, choose to manually install the drivers, but don't select a location on your hd, use the list of available drivers already on the computer, find 'samsung', and select the drivers that come up (again, had to download samsung drivers from their site and install that First)
this fixed the issue for me. and nothing like a good ol' reboot too to fix random windows issues : )
cancerouspete said:
i had issues with drivers on win7 64x, first, it would take for ever once the phone was plugged in, for windows to initially auto-install the drivers (after installing the ones from samsung)....a very long time. but, even after 3/4 of it installed correctly, i hadn't noticed that the Android 1.0 drivers didn't install at all. If you goto control panel->system->device manager, see if there is an alert next to 'Android', if so, open it, choose to manually install the drivers, but don't select a location on your hd, use the list of available drivers already on the computer, find 'samsung', and select the drivers that come up (again, had to download samsung drivers from their site and install that First)
this fixed the issue for me. and nothing like a good ol' reboot too to fix random windows issues : )
Click to expand...
Click to collapse
That is also what I did that finally worked.
cancerouspete said:
i had issues with drivers on win7 64x, first, it would take for ever once the phone was plugged in, for windows to initially auto-install the drivers (after installing the ones from samsung)....a very long time. but, even after 3/4 of it installed correctly, i hadn't noticed that the Android 1.0 drivers didn't install at all. If you goto control panel->system->device manager, see if there is an alert next to 'Android', if so, open it, choose to manually install the drivers, but don't select a location on your hd, use the list of available drivers already on the computer, find 'samsung', and select the drivers that come up (again, had to download samsung drivers from their site and install that First)
this fixed the issue for me. and nothing like a good ol' reboot too to fix random windows issues : )
Click to expand...
Click to collapse
thank you!
Hay guys, I think i'm being a noob here... but...
After rooting and s-offing my old HTC Desire with no problems at all and flashing countless ROMs every five mins with ease, I seem to have gotten stuck with the One X.
My problem is that fastboot nor adb finds my device, I have reinstalled the Android SDK + USB Drivers and HTC USB Divers ect, ect ,ect, but nothing gets listed under any of the commands "fastboot devices" or "adb devices". Looking into my PCs device manager when my phone is in fastboot it shows as "My HTC" with a yellow "!" next to it, the error message is shows is "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)", I have reinstalled the device drivers a few times and each time I get the same error message, however nothing says that the device has been stopped from working.
I'm running Windows 7 by the way.
Can any one help me? I bet its some thing really dum that I have overlooked.
try delete/remove the driver
I tryed doing so and reinstalling it, still didn't work.
Fixed, it seems the HTC sync download was corrupt, I little odd, but downloaded it again and it seemed to work.
Sent from my HTC One X using Tapatalk 2
Firstly, sorry for reviving an old thread. I have been searching for the answer to this problem for a while now. Whenever I try to use HTC Sync Manager, it shows the My HTC driver with a yellow ! triangle. I have tried many different things to try and get it to work, but it just won't install the driver. It is a Code 52 from Windows, saying the driver signature couldn't be verified. I just want to be able to use adb so I can tinker with the phone! Please help, it would be much appreciated.
Hi, I have a huge problem and I don't know what to do anymore. I try to access fastboot mode on my Xperia Play, so I can flash ICS kernel, I did usual stuff, followed the guides, watches few videos on youtube, now I am stuck on part where I have to install drivers manually.
So basicly I go to device manager, select S1boot, update, select driver... And after I do that, every single time it says that Windows could not find driver software for your device.
I tried downloading many different drivers, I tried many combinations in pointing them like:
C:\Users\T-N-Z\Desktop\Fastboot\fastboot\Drivers\x64
or just
C:\Users\T-N-Z\Desktop\Fastboot\fastboot\Drivers\
etc..
I am on Windows 8 RTM Pro. I had similar issue in Windows 7, but it fixed itself randomly :/
I also installed Android SDK and Android USB drivers from it..
I tried installing fastboot driver with flashtool, but I believe it installs wrong driver, S1boot gets renamed to SEMCFLASH or something called like that, and after that my Xperia Play won't stay in fastboot mode, so I can't do anything.
Please help me out, what am I doing wrong? Thank you.
T-N-Z said:
Hi, I have a huge problem and I don't know what to do anymore. I try to access fastboot mode on my Xperia Play, so I can flash ICS kernel, I did usual stuff, followed the guides, watches few videos on youtube, now I am stuck on part where I have to install drivers manually.
So basicly I go to device manager, select S1boot, update, select driver... And after I do that, every single time it says that Windows could not find driver software for your device.
I tried downloading many different drivers, I tried many combinations in pointing them like:
C:\Users\T-N-Z\Desktop\Fastboot\fastboot\Drivers\x64
or just
C:\Users\T-N-Z\Desktop\Fastboot\fastboot\Drivers\
etc..
I am on Windows 8 RTM Pro. I had similar issue in Windows 7, but it fixed itself randomly :/
I also installed Android SDK and Android USB drivers from it..
I tried installing fastboot driver with flashtool, but I believe it installs wrong driver, S1boot gets renamed to SEMCFLASH or something called like that, and after that my Xperia Play won't stay in fastboot mode, so I can't do anything.
Please help me out, what am I doing wrong? Thank you.
Click to expand...
Click to collapse
Click the link in my signature go to the unlock boot loader guide download Adb fastboot package.
Device manager
Right click
Update driver
I will choose
Install driver manually
all devices
Have disk/ browse
X86/X64 /usbwin.inf
Next
Please note you may need to disable driver signature enforcement. Google it
Sent from my R800i using Tapatalk 2
Ok, I have disabled driver thingie on Windows 8 and installed your package files. Now drivers says that I have Android ADB interface, but... When I boot into fastboot mode, after some time it just turns offs and phone starts charging process.
Maybe it needs to be fully charged or something before I can do anything or what?
It just started working for no reason again... Don't know what I've done differently this time but it works now. Thanks for help.
Let me say beforehand that I am a lifetime lurker. I would not be posting here if I hadn't already spent at least two days scouring the web for an answer.
My HTC Desire HD cannot connect to HTC Sync, but it can connect as a storage device, and can be seen by adb. Whenever it connects while in hboot/fastboot, it will flicker "USB" a few times before Windows tell me it's not recognized (Device failed enumeration code 43). This includes using the RUU wizard from HTC. That will just make it stick on "RUU" in the bootloader.
I have tried every driver download suggested on this site. I have switched USB cables three times (all htc cables). I have used two seperate computers (Windows 8 and Windows 8.1).
I'll admit I'm a nooby specifically to Androids. All I want to do is flash new ROMs/root my device. As far as I know this is step one, and I can't go any further until I've unlocked my bootloader.
EDIT: SOLVED
HTC Desire HD drivers really hates Windows 8 and 8.1. Installed Windows 7 32-bit and it worked just fine.
That error can be a pain in the ass. I have it as well. I believe disabling griver signature enforcement in win8 (it's your OS, isn't it?) should allow installing adb drivers, but I was too lazy to check it. As a workaround I instead flash the boot.img in bootloader by putting it to PD98IMG.zip
I can upload you a template, leave the txt in it and replace the boot.img with your desired one, choose store (none) compression level, then put the zip directly (don't use folders) in sd card
EDIT: I didn't fully read your post before. If you don't have S-OFF most probably you can't get away without adb drivers..
Turned off device signing. No effect.
Have you tried now manually installing drivers in device manager while the phone is in unrecognized state? Does it still say the drivers are incompatible?
If your OS is 64bit, you need these http://d-h.st/23V
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
I am getting a pop up saying that the device is failing to to start. It's not like other usb devices I might have plugged in and they just sit there in at least their correct category in device manager.
The part that ticks me off most, is that this exact problem on this exact model has been solved on three different forums, and each time the OP just said "nvm I fixed it" and never even bothered to explain how for the rest of us.
It's really hard not to curse right now.
in device manager update dialog goto
browse my computer --> let me pick --> have disk --> choose the .inf from the drivers path.
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
have you tried un-installing HTC SYNC?
SuperMechaCow said:
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
Click to expand...
Click to collapse
Nothing is wrong with your phone, same thing happens to me, I just thought disabling driver signing should fix it, like I said I was too lazy to check it since I found workaround for my needs.
TheJokah said:
have you tried un-installing HTC SYNC?
Click to expand...
Click to collapse
It is currently uninstalled.
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need. Also, I thought you could only change the S-Off if your bootloader was unlocked anyways?
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Sent from my HTC Desire HD using xda app-developers app
ammo12 said:
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Click to expand...
Click to collapse
It appears to be the same device/drivers when powered off or when in the Android environment. While in the bootloader, it shows as an unknown device.
I also noticed that only when I am trying to update via RUU, it says instead "Device Descriptor Request Failed"
SuperMechaCow said:
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need.
Click to expand...
Click to collapse
The boot.img is in the ROM-zip-file packed. But I think, if its a RUU it is called PD98...img
Try this, I know its from Samsung, but this installs fastboot drivers and drivers used for ADB access
https://www.dropbox.com/s/vqfuv8fifmrkkxt/SAMSUNG_USB_Driver_for_Mobile_Phones.zip
For the set of Google Drivers, go here too http://d-h.st/23V
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
SuperMechaCow said:
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
Click to expand...
Click to collapse
Did you browse to the folder where the manual driver files reside?
Sent from my Desire HD using Tapatalk 4
SuperMechaCow said:
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Click to expand...
Click to collapse
SuperMechaCow said:
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
Click to expand...
Click to collapse
To be exact I have:
Tried HTC Sync
Tried HTC Drivers Installer
Tried to Automatically search for drivers
Tried to install drivers by using the inf Install option
Tried to manually select drivers by pointing to the folder the Win7 64x drivers were placed
Tried to manually install by picking out the exact inf files
Tried to install from device drivers list, were they were not listed
Tried these steps with driver signing turned off
Tried all of these steps with another PC
I still think the issue is related to the fact that it only has problems in the bootloader menu
Ok, like u know I had this issue. Now I randomly managed to fix it when I needed adb drivers for my new toy (Sanei tablet for 40$ lol)
The mistake I was making is that I was trying to install the drivers while device was in fastboot, but apparently you can get away with casual "My HTC" drivers which can be installed when DHD is booted into Android. It looks likethe phone is not being detected from bootloader (it doesn't like any of the drivers I had tried), but I can fully use ADB while it's in recovery or starting/trying to boot OS, so it should be enough for rooting/unlocking bootloader.
I remember with HTC Wildfire I had drivers package with seperate drivers for Android and fastboot, so I had to install different driver after rebooting to fastboot, but with these new drivers and win8 it doesn't work out this way.
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Similar issue
SuperMechaCow said:
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Click to expand...
Click to collapse
I am facing the same problem and I too have tried different methods like you did. Am using Windows 8.
Gotta try on Windows 7. Shall update if that solves my problem too.