when qdl sends my streak to reboot it runs out of time, but the drivers are installed correctly, running streak droid 1.6
If adb is timing out then you have the incorrect adb driver installed or that USB port won't work for it. I would try other USB ports first then try the driver install again.
Sent from my Dell Streakdroid 1.6 0
Related
Hey,
Im having problems with the USB driver install in Windows XP, when ever i connect the phone via USB it detects the phone and installs the drivers, when its done it again detects the phone and installs the drivers all over, and it keeps looping that process untill I end it by pressing cancel.
I installed the drivers downloaded with r3 sdk
ive searched the forum for simmilar problem but only founde problems considering the phone never to be found.
any help is apreciated
1. Go to http://www.nirsoft.net/utils/usb_devices_view.html to download the usbdeview first
Using usbdeview to uninstall all USB driver of your magic.
Restart PC
Install your magic driver from r3 sdk
possibly silly question, seeing everyone is saying the rooting problem is something different(drivers(htc/pdanet/android sdk), sdcard, computer(OS)). you guys that have gotten ADB to successfully get the phone recognized in recovery mode:
Did the phone show up in the device manager for windows?
i feel like windows has to register the phone under a certain driver in order for ADB to pick it up(otherwise the OS doesn't recognize it like any other piece of hardware). maybe part of the problem is some people don't have a recovery driver?
just throwing it out there since I have tried every method on the forum except using the original sdcard that came with the phone(it's my my gf's phone at the moment and i haven't been able to get it from her)
also, does anyone know what eugene's setup is? OS, drivers, sdk version? or eugene if you see this, it would be wonderful if you could chime in.
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
What OS are you using? 32 or 64 bit? Do you have HTC Sync installed?
i've used winxp pro 32bit, win7 pro 64bit, win7 ultimate 64bit. i tried the htc drivers, the pdanet drivers and the sdk drivers. i just made a ubuntu boot drive, i think im going to try that later tonight.
and i think chrisinaz is trying to root his friends phone on the same computer he did his on if i'm not mistaken.
Using xp 32 bit and fedora 13. Neither work for his, both work for mine.
-------------------------------------
Sent via the XDA Tapatalk App
chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
Where it says android 1.0 this is the driver that you need to update. I used the PDANet driver to update it.
Ok, I'm having a problem here. I'm buzy on a ROM, and I have made something that I want to test. But when I try to access my phone via adb, it doesn't show up in adb devices. Just nothing. I reïnstalled adb, the drivers, rebooted the phone and computer, put on debugging mode, everything. The phone is showing in (windows) devices, but adb just don't recognize him. I'm on Windows 7 Home Premium. And on my phone Swiftdroid M5 (with ClockworkMod Recovery 3.2.0.1, which is working properly). Anyone knows what to do?
Anyone?
Sent from my GT540 using Tapatalk
Heres my solution ^^ adb worked for me some weeks ago but now i had your problem too lol:
first uninstall all the adb drivers from:
Start>devicemanager
then get this :
http://www.junefabrics.com/bin2/LGDriver.exe
original LG drivers
and install
then plug your phone(debugging on of course)
then it will show 7 (i think) installations
5 of them will be done fast but 2 won't finish installation
so just go to devices and printer
rightclick on android sooner single adb interface and select troubleshooting( marked with a yellow triangle)
then just let is solve the error
the last of the 7 drivers wont install but thats not a problem
EDIT: make sure u know on which port u were doing this
Oh of course you should reinstall the adb drivers. Btw i'm in linux you can use linux for building rom. What are you using?
Sadronis said:
Oh of course you should reinstall the adb drivers. Btw i'm in linux you can use linux for building rom. What are you using?
Click to expand...
Click to collapse
Windows 7 + Ubuntu 11.10
Sent from my GT540 using Tapatalk
is fastboot working now ?. and installed properly in device manager.
regisol said:
is fastboot working now ?. and installed properly in device manager.
Click to expand...
Click to collapse
Wrong topic
Sent from my GT540 using Tapatalk
Hello, I tried all of the above but my device still doesn't get recognized. Is there any other way to fix this? Thanks.
I've been in the same situation like this before. My phone wasn't recognized by adb. I though it was a driver problem so I reinstall the driver million times but it doesn't help. I tried on many other computer with various OS as well but adb still can't recoginized it. At last I flash another ROM and adb can recognized my phone again. so the problem is the SDSL ROM
I see. Thanks for the info ^_^
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Same thing happening with me, i want to re-lock my bootloader but when i am in bootloader mode windows does not want to recognize the device, i have tried everything too.
Did you install the correct drivers?
When connected and in the bootloader open the device manager in windows. You should see "android 1.0" near the top.
Update that driver. It should work.
Sent from my Nexus 7 using xda premium
Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Hey, As i said earlier i was having the same problem...try switching your usb cable then try. That is what fixed my problems.
ive done all mentioned above, even tried 3 different cables, no luck, anyone have suggestions
I dont know about what you want to do, but if you want to root and unlock use the wugfresh took kit. Its the bomb and as soon as I figure out where I can thank him and give a big kudos I will give thanks.
Sent from my Nexus 7 using xda app-developers app
I could be wrong, but I don't think adb works from bootloader, but the fastboot command should. I think you can also use Google's Composite ADB Interface driver too for it (I can't reboot my N7 atm or else I'd find out).
I don't have any other android-related drivers on my system either, only Google's USB driver from the SDK. I'm also on Windows 8, but I would assume Google's USB driver would work fine on Windows 7 too.
Also certain USB filter drivers may cause issues too, such as libusb, or even AMD's USB filter driver (however, I had no problems). Or if you want to wipe out any/specific USB drivers, I recommend getting: http://www.nirsoft.net/utils/usb_devices_view.html
When I plug in my phone to my PC the only thing that happens is it begins charging. Doesn't show signs of adb working, only thing that happens beside charging is my pc says it's an Unknown Device.
I tried all sorts of things, like USB Debugging on and off, MTP on and off, PTP on and off, I think even fastboot doesn't work. I tried to install all kinds of drivers (official, unofficial, uninstalling them afterwards if they didn't work ofc), I tried Wug's toolkit, nothing. I tried killing adb server then restarting it - nope. I even tried all of my USB ports, both 2.0 and 3.0. Also tried 3 different roms/kernels (L dev preview, Purity and Mahdi), didn't work aswell.
Things seem pretty hopeless at this point :/
Download wugfresh toolkit... look In the section of driver installation... They'll help you out
Sent from my Nexus 4 using XDA Free mobile app
driver installation...
As I said, I already tried the driver thing in Wug's Toolkit. Also my Windows allows unsigned drivers.
Bump :/
monitobeko said:
Bump :/
Click to expand...
Click to collapse
If it still says Unknown Device on your PC, its a driver issue. Personally I use the Google usb driver, that page also has instructions on how to install the driver. Try uninstalling whatever drivers you have installed right now, then install Google usb driver carefully following instructions. Fastboot needs bootloader mode, so make sure your phone is in that mode before trying a fastboot command. I use the Minimal adb installer to install adb/ fastboot tools.
venu123 said:
If it still says Unknown Device on your PC, its a driver issue. Personally I use the Google usb driver, that page also has instructions on how to install the driver. Try uninstalling whatever drivers you have installed right now, then install Google usb driver carefully following instructions. Fastboot needs bootloader mode, so make sure your phone is in that mode before trying a fastboot command. I use the Minimal adb installer to install adb/ fastboot tools.
Click to expand...
Click to collapse
Fastboot actually works, only ADB doesn't. I use the Android SDK to install adb/fastboot and I tried Google USB drivers and also Universal ADB. I tried the drivers from Wug's Nexus Toolkit and then LG drivers, same old story :/
Edit: I upgraded from Windows 8 to Windows 8.1 using clean install, still same problem.
monitobeko said:
Fastboot actually works, only ADB doesn't. I use the Android SDK to install adb/fastboot and I tried Google USB drivers and also Universal ADB. I tried the drivers from Wug's Nexus Toolkit and then LG drivers, same old story :/
Edit: I upgraded from Windows 8 to Windows 8.1 using clean install, still same problem.
Click to expand...
Click to collapse
Might be windows 8/8.1 giving you driver signature grief. Try the Universal adb drivers:
http://www.koushikdutta.com/post/universal-adb-driver