Related
I just got a dell streak and I am trying to install the fastboot drivers in windows xp. I boot the phone into fastboot and select the fastboot option. Then I wait 10 seconds and plug in the usb cable into the streak. The computer tried to install the driver and I go to device manager, right click, update driver and try to manually install the driver, but when I select google, inc the only drive that i have available is android composite adb interface. I dont get the option for android boot loader interface. I must be doing something wrong.
On my dell streak screen it says wait for usb fastboot detect. after 10 seconds it still says this. is it suppose to say fastboot or is that after you install the drivers?
Ive spent all night and cant seem to get windows to recognize my streak in fastboot. Now when I plug the streak in on the wait for usb fastboot detect my streak shows up in windows as 'usb device'. it doenst even show up as android device, just usb device.
I really hope someone can help me.
I think it has to do with my android_winusb.inf. Can someone open their android_winusb.inf and copy/paste it here? I have this string in mine:
; Dell Mini5
%SingleAdbInterface% = USB_Install, USB\VID_413C&PID_B007
%CompositeAdbInterface% = USB_Install, USB\VID_413C&PID_B007&MI_01
I am guessing there should be a %SingleBootLoaderInterface% string in there also that would allow the bootloader driver to show up when i try to manually select the drivers.
Looks like you have not got the drivers installed download the dell suite from dell look around the forum their is a way to tell u how to find the drivers on ur PC. If u cannot do it or no one has posted how to do it when I am at the PC later I will tell u
Sent from my Dell Streak using XDA App
Yes the dell pc suite is installed. I installed the one that was on my streaks internal card and I also tried one from dells site. I also followed the guide to manually install the drivers but shipping will the boot loader driver wont show up. Ive tried pointing windows to the dell programs folder to look for the driver as well.
Sent from my Dell Streak using XDA App
Can someone who has fastboot working please paste the text inside their android_winusb.inf so I can get the correct codes.for the streak?
Sent from my Dell Streak using XDA App
I could never get mine to work in fast boot either. I was not able to send commands through fast boot. It took me days to figure out how to get my Streak running 2.2 but I did and without FB.
Now I am having constant problems with my Streak rebooting and was advised to go back to 1.6 and start all over
Well no luck so far and nobody has posted what I believe will solve my problem. I just had to exchange my streak because of a dead pixel. I would like to get this working hopefully someone can help.
Sent from my Dell Streak using XDA App
Another solution if you still cant find the drivers Go to device manager Right click Android 1.0 Select Update Driver Software Select Browse my computer.... Select Let me pick Select All Hardware Scroll down to Google INC Select Bootloader and you should be good to go
I did that already. Doesnt show the bootloader driver. That is the problem. Only shows the composite adb driver.
Sent from my Dell Streak using XDA App
When I tried searching, Google never showed anywhere and that was after waiting for a few minutes for it to appear.
It was/is so frustrating! The instructions are easy to follow but when a pc doesn't give the optioons listed in the instructions, its irritating. I would still like to be able to do it the way everyone one does but I cannot get it to work that way.
Sent from my Dell Streak using XDA App
ok here is what worked for me..... Make sure you have the dell software installed - Then go to fastboot on the streak wait 10 seconds plug it in - don't worry about installing the drivers when the popup stuff comes up - go to device manager - there should be that caution crap next to the android device - right click on it to update the driver - chose pick from list - you will see android something and android phone (click on android phone) something will popup saying it ain't right blah blah blah - push continue and ok and let it install - look at your phone it should be in fastboot mode and Flash till your heart's Happy
Ok everyone keeps telling me to do what I have already tried. Can someone go to their C:\Program Files\Dell\PC Suite\Drv folder and open the file android_winusb.inf in notepad and paste it here for me? Someone who has a working fastboot.
And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf
Laaf2005 said:
Ok everyone keeps telling me to do what I have already tried. Can someone go to their C:\Program Files\Dell\PC Suite\Drv folder and open the file android_winusb.inf in notepad and paste it here for me? Someone who has a working fastboot.
And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf
Click to expand...
Click to collapse
Curious if you and I are having identical problems... My Streak does show fastboot_mode on its white screen but when I try to run commands from my pc- it doesn't work (i.e. waiting for device, etc.) Also I get those two same driver options as you. At this very minute, I am connected in debug mode and under my device manger I have "ADB Interface>Android Composite ADB Interface"
Is this what your pc shows?
"And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf"
The only files I have in that folder are .dll files. I have no .inf files.
rnj79 said:
Curious if you and I are having identical problems... My Streak does show fastboot_mode on its white screen but when I try to run commands from my pc- it doesn't work (i.e. waiting for device, etc.) Also I get those two same driver options as you. At this very minute, I am connected in debug mode and under my device manger I have "ADB Interface>Android Composite ADB Interface"
Is this what your pc shows?
Click to expand...
Click to collapse
Yes it is. And its not the correct driver. You need adb bootloader driver.
If someone cant post the android_winusb.inf can someone put their dell into fastboot mode then go to device manager in windows and find the android phone device, right click and select properties. Then to go details and tell me what it says under device id. That will help me a bunch and I may be able to get it working. If so I will post how for anyone having this issue.
rnj79 said:
"And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf"
The only files I have in that folder are .dll files. I have no .inf files.
Click to expand...
Click to collapse
Are you sure you didnt go into the i386 folder? the inf file is located one folder up. I have .dll's in my C:\Program Files\Dell\PC Suite\Drv\i386 but if you go back to the parent folder Drv then you should see a .inf file. Its ok though because if you are having the same problem I am your .inf wont help. I need it from someone who has fastboot working.
Laaf2005 said:
Yes it is. And its not the correct driver. You need adb bootloader driver.
If someone cant post the android_winusb.inf can someone put their dell into fastboot mode then go to device manager in windows and find the android phone device, right click and select properties. Then to go details and tell me what it says under device id. That will help me a bunch and I may be able to get it working. If so I will post how for anyone having this issue.
Click to expand...
Click to collapse
I'm just like you! I cannot find the bootloader driver. Surely it can't be just the two of us with this stupid issue?
Laaf2005 said:
Are you sure you didnt go into the i386 folder? the inf file is located one folder up. I have .dll's in my C:\Program Files\Dell\PC Suite\Drv\i386 but if you go back to the parent folder Drv then you should see a .inf file. Its ok though because if you are having the same problem I am your .inf wont help. I need it from someone who has fastboot working.
Click to expand...
Click to collapse
I have no .inf files in the DRV folder. The only folder in that is i386 otherwise, the DRV folder is empty. Obviously I'm not going to be of any help to you but at least I know I am not alone and am not crazy- thats the part that helps
Well I dont know why its empty, but I have a .inf in my folder. its for basically telling your computer which streak drivers you have available and in the file it only lists adb composite driver with the id for the driver. All I need is for someone to post the device id of the bootloader driver so i can try adding it. Or if someone can post the drivers here.
I beleive i have the same priblem, there is no way i can install android fastboot, ive tried the pc suite, manual random drivers from the internet and nothing, so annoying
Arya
Sent from my Dell Streak using XDA App
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable
When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2
download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium
i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city？
Sent from my SHW-M190S using xda premium
You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.
Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.
bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.
I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?
Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC
Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app
I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app
Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse
rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.
I just bought a Nexus 4.
All I've done thus far -
Upgraded to 4.3.
Installed the drivers from the Android SDK kit, so in my device manager, all that shows is 'Android Composite ADB device' when the Nexus 4 is connected.
Yet, when I run fastboot devices in platform-tools, I'm getting nothing.
I've tried un-installing, then re-installing the drivers to no avail.
Any help?
It should be called "Google Nexus 4 Bootloader Interface".
The device probably didn't get the correct usb driver. Try going to Device Manager, Uninstall that ADB device and also select the checkbox "Delete the driver software for this device."
Then press the icon to "Scan for hardware changes". Reinstall the driver this time using Universal Naked Driver.
Just to make sure. Are in the bootloader on your phone when you are trying this?
As you can't use fastboot in android
To get there hold power and volume down
Your phone well reboot
Keep the buttons held and you will appear in the bootloader.
If you are trying this from within the bootloader then I'm very sorry for sounding patronising. That was not the intent
Sent from my Nexus 4 using xda app-developers app
As was previously mentioned, make sure that you are in the bootloader when running fastboot.
Now, when I updated to Android 4.3, my very old SDK kit had several programs that did not work anymore (Some of the commands didn't work, USB driver didn't work, etc.). So I installed the latest SDK, but later noticed that there was an update manager built right into the kit. It is located in the folder that has a name similar to the following: adt-bundle-windows-x86_64-20130717 (The name may look a little different), and the name of the program is "SDK Manager.exe". I ran it and several updates appeared, so I clicked on the Install button. The Windows driver is hidden under the "Extras" section and listed as "Google USB Driver". When you highlight that item it shows where it is located in Windows on the hard drive. The current version of this driver is "revision 8". After removing the old driver from the Device Manager in Windows, as I recall, I had to use the "search for the driver" mode, as pointing directly to the driver did not work for some reason. After installing it into Windows, it was listed as "Android Bootloader Interface", Version 8.0.0.0, dated 07-09-2013. These various updates solved all my 4.3 problems. What is really nice about the SDK is that you don't have to rely on drivers and programs posted on a forum somewhere that you have no idea whether they are up to date or not, and for that same reason and really understanding how things work and how to troubleshoot from the command line, is why I would never use a toolkit.
Alex240188 said:
Just to make sure. Are in the bootloader on your phone when you are trying this?
As you can't use fastboot in android
To get there hold power and volume down
Your phone well reboot
Keep the buttons held and you will appear in the bootloader.
If you are trying this from within the bootloader then I'm very sorry for sounding patronising. That was not the intent
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was it. Thank you very much. You will have to forgive me for my incompetence in advance. I am coming from dark side (iOS) after having finally seen the light.
Now, onto flashing LTE on my phone...
I am generally good at rooting any android phone. I am having a hard time locating the drivers for the VZW LG G2. I have the zip file from the post on how to root the phone, but I am not sure which file to install.
Any input would be appreciated.
If they aren't auto detected and installed after a reboot with phone plugged in, goto device manager, locate the phone and manually update driver pointing it to the LG folder full of drivers. To get the adb interface working, you may need to be in the internet connection mode with the ethernet option selected. Can't remember if that was the case or not.
iowabowtech said:
If they aren't auto detected and installed after a reboot with phone plugged in, goto device manager, locate the phone and manually update driver pointing it to the LG folder full of drivers. To get the adb interface working, you may need to be in the internet connection mode with the ethernet option selected. Can't remember if that was the case or not.
Click to expand...
Click to collapse
I needed to install LG VZW_United_WHQL_v2.11.1 then go to LG website and download drivers from the G2 support page. I couldn't upload the exe file. Restart computer and all went well. I had same issue and struggled to solve.
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
Bxrider117 said:
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
Click to expand...
Click to collapse
You must have the sdk with adb installed before you do that part. Browse to that directory, find adb, shift right click, open command prompt here. Then do 'adb devices'. You'll see serial # on left and 'device' on right. It's working then. If you get 'offline' on right, you need to update your adb.
i'm having the same issue. i'm trying to root, and it won't list it at all, and i'm not getting the debugging icon on top. no serial number popping up on the abd devices and i just tried with both 3.8 and 3.10 drivers. anything?
If I remember correctly I had to go to settings>pc connection>select USB connection method and then choose Internet connection, then choose modem in order to get the debugging icon to appear.
Sent from my VS980 4G using xda app-developers app
I'm having trouble with my PC not recognizing my phone at all. It says USB device not recognized. I'm on Windows 7 64bit if that matters.
Sent from my LG-D801 using xda app-developers app
thanks!
bigox said:
I'm having trouble with my PC not recognizing my phone at all. It says USB device not recognized. I'm on Windows 7 64bit if that matters.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
Most likely it's because you don't have the right drivers installed. Try installing these http://g2-lg.com/download-lg-g2-android-usb-drivers-ver-3-10/.
Sent from my VS980 4G using xda app-developers app
The drivers aren't working for me so i will link where you can get the drivers from the actual website. Please note: this link is for Tmobile D801 but you can search for your device on there.
http://www.lg.com/us/support-mobile/lg-D801
LG's website has drivers for D800 and D801. I'm looking for D802 drivers. Where can I find them or which are compatible?
The Universal device drivers aren't universal?
Sent from my VS980 4G using xda app-developers app
cggorman said:
The Universal device drivers aren't universal?
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Where can I find Universal drivers? Not on LGs website.
I installed this:
http://forum.xda-developers.com/showthread.php?t=1379875
And after that it worked fine. I have a ls980, so the att and t-mobile don't work for me. This did.
This took me a while to sort out. There is a certain driver package for the verizon phone. The drivers listed here dont seem to work for me. I'm using win 7. Here is what I needed to use, then everything just came together - LG VZW_United_WHQL_v2.11.1
These can be downloaded at LG's site. Make sure you search for drivers pertaining to the model number of your phone.
Hope this helps someone
EVOme said:
You must have the sdk with adb installed before you do that part. Browse to that directory, find adb, shift right click, open command prompt here. Then do 'adb devices'. You'll see serial # on left and 'device' on right. It's working then. If you get 'offline' on right, you need to update your adb.
Click to expand...
Click to collapse
I am having the same issue..what is the sdk with adb installed and what directory do i browse to? sorry for the noob questions, ive always had nexus's, so much easier to flash recoveries etc
LG Drivers failing to install
I Install LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1.exe from LG website, it installs and I get a "successful" message from the software package. However, shortly after windows pops up a bubble with "not successful". Details:
Uninedntified Device - No Driver Found
Creative Game Port - Failed
Plug in phone and select “PC Software”, since none of the other options make any sense (USB charge, Media Transfer, Tethering, and Picture Transfer). Sidebar: None of the other options seem to change anything even when tried. "Media Transfer" is the only one that seems to actually install something successfully, but nothing changes with the device list. Back on track: Get a new windows “installing” bubble. Shortly after I get another “not successful” message with the following:
MTP USB Device – Failed
I go to Devices and Printers, select the phone, and look in the properties. Click “update driver” and pick the LG folder in Program Files. It says “driver already installed”.
Rebooting the computer accomplishes nothing.
I’ve tried several full uninstalls.
No matter what I try, if I run “adb devices”, I get “List of Devices Attached” then my prompt back, meaning none found I assume.
Yes I have turned on dev mode on the phone and I get the debugging icon when the USB cable is plugged in. I’m on Win7 64. WTF is wrong with this driver?
Thanks for any help you can give!
Uncheck usb debug? Had this on my htc one x. Maybe helps
Sent from my LG-D802 using XDA Premium 4 mobile app