I think I have a driver problem. I downloaded the most recent drivers for the Moto X from motorola. But when I am connected to my Windows 7 PC, it doesn't recognize my Moto X in bootloader mode.
This is what it shows in Device Manager when my phone is in bootloader mode connected to my Windows 7 PC.
Also, I have PDANet installed, so not sure if that causes a conflict. What can I do to correct this driver problem?
Thanks!!
Cozume said:
I think I have a driver problem. I downloaded the most recent drivers for the Moto X from motorola. But when I am connected to my Windows 7 PC, it doesn't recognize my Moto X in bootloader mode.
This is what it shows in Device Manager when my phone is in bootloader mode connected to my Windows 7 PC.
Also, I have PDANet installed, so not sure if that causes a conflict. What can I do to correct this driver problem?
Thanks!!
Click to expand...
Click to collapse
Did you try getting the Motorola Drivers from Motorola?
Cozume said:
I think I have a driver problem. I downloaded the most recent drivers for the Moto X from motorola. But when I am connected to my Windows 7 PC, it doesn't recognize my Moto X in bootloader mode.
This is what it shows in Device Manager when my phone is in bootloader mode connected to my Windows 7 PC.
Also, I have PDANet installed, so not sure if that causes a conflict. What can I do to correct this driver problem?
Thanks!!
Click to expand...
Click to collapse
Have you made sure USB Debugging is enabled?
SwiftLeeO said:
Did you try getting the Motorola Drivers from Motorola?
Click to expand...
Click to collapse
yes, I downloaded and installed the Motorola Device Manager as instructed and I have USB debugging enabled. When I am not in bootloader mode and my Moto X is connected, this is what i see - Mot Composite ADB Interface, which I believe is the correct driver.
But in bootloader, it is the Mot Single ADB Interface. I am wondering if that is the issue?
When I type adb devices, it says list of devices attached but it does not list any devices. If I type fastboot devices, it lists my device. So fastboot works but adb doesn't.
DuvelDroid said:
Have you made sure USB Debugging is enabled?
Click to expand...
Click to collapse
yes
Cozume said:
yes, I downloaded and installed the Motorola Device Manager as instructed and I have USB debugging enabled. When I am not in bootloader mode and my Moto X is connected, this is what i see - Mot Composite ADB Interface, which I believe is the correct driver.
But in bootloader, it is the Mot Single ADB Interface. I am wondering if that is the issue?
When I type adb devices, it says list of devices attached but it does not list any devices. If I type fastboot devices, it lists my device. So fastboot works but adb doesn't.
Click to expand...
Click to collapse
Okay so this isn't the same exact phone but maybe it will help:
http://forum.xda-developers.com/showthread.php?t=1322323
SwiftLeeO said:
That is interesting. Have you installed SDK Tools for Android? It's a long shot but it got my Nexus 7 to be recognized. Then again I believe those were google specific drivers but you can try that... Otherwise, you shouldn't be having any issues.
Click to expand...
Click to collapse
no, what is it?
I have tried 2 USB cables, one is a brand new USB cable and I have used both USB ports on my laptop. There are other people online I can find who had this same issue, but not much info on how to resolve it.
I have uninstalled and reinstalled the Motorola Device Manager, which installs the drivers, 3 or 4 times now. Rebooted my laptop and my phone several times. Uninstalled PDANet in case that was an issue.
Fastboot works, adb doesn't.
I would like to manually install the Mot Composite ADB Interface driver while in the bootloader mode, but I can't seem to find where it is on my computer.
Cozume said:
yes, I downloaded and installed the Motorola Device Manager as instructed and I have USB debugging enabled. When I am not in bootloader mode and my Moto X is connected, this is what i see - Mot Composite ADB Interface, which I believe is the correct driver.
But in bootloader, it is the Mot Single ADB Interface. I am wondering if that is the issue?
When I type adb devices, it says list of devices attached but it does not list any devices. If I type fastboot devices, it lists my device. So fastboot works but adb doesn't.
Click to expand...
Click to collapse
right click on the Mot Single ADB and uninstall then move the usb cable to a different port and let it reinstall then try again i know you dont have to have the SDK installed because i dont and my phone works fine. also try using a different cable some phones are really picky when it comes to what cable you are using
SwiftLeeO said:
Okay so this isn't the same exact phone but maybe it will help:
http://forum.xda-developers.com/showthread.php?t=1322323
Click to expand...
Click to collapse
the only motorola program I have on my computer is the motorola device manager and I uninstalled it and reinstalled it several times now. For some reason, Windows uses the wrong driver when I am in bootloader mode.
dray_jr said:
right click on the Mot Single ADB and uninstall then move the usb cable to a different port and let it reinstall then try again i know you dont have to have the SDK installed because i dont and my phone works fine. also try using a different cable some phones are really picky when it comes to what cable you are using
Click to expand...
Click to collapse
When I did that, I removed the Mot Single ADB Interface software from my computer and then it failed to install Fastboot ghost s. I need to find out where the Mot Composite ADB Interface driver is on my PC so I can manually install it. Where should I look for it?
when I put the phone in recovery TWRP 2.6.3.1, adb will recognize my device but it thinks it is my Samsung Galaxy Nexus.
Cozume said:
when I put the phone in recovery TWRP 2.6.3.1, adb will recognize my device but it thinks it is my Samsung Galaxy Nexus.
Click to expand...
Click to collapse
Uninstall everything on your USB ports/drivers restart let windows redownload the USB ports/drivers and run the Motorola drivers install
MOTO X Slapped
[email protected] said:
Uninstall everything on your USB ports/drivers restart let windows redownload the USB ports/drivers and run the Motorola drivers install
Click to expand...
Click to collapse
yeah, that is looking like what I am going to have to do
I hit the issue earlier and fixed it with the steps. hope will help you too.
1. connect your phone with computer
2. go to C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\
3. run Motorola Driver Installer.exe, choose clean and Reinstall.
Related
I just recently got into modding my N1 a few weeks ago and finally hit my first snag:
Original root was through superoneclick, so bootloader is still locked. I flashed over to stock GRI40 OTA without realizing (stupidly) that flashing
it would also flash over my RA recovery and unroot my phone. Now, superoneclick is incompatible with GRI40, so I can't re-root through that, and I'm having trouble
with unlocking the bootloader through fastboot.
I get no response from ADB or fastboot in windows cmd prompt when I boot phone to FASTBOOT.
the command "fastboot devices" gives me a repeat of the same prompt with no error. (I can't get fastboot to work in normal debugging mode either, and I don't know if it usually will, because this is the first time I've used it.)
the command "adb devices" gives me response-- "list of devices attached" with nothing below (ADB works fine in debugging mode though).
I thought it might be a driver problem, but "Android bootloader Interface" driver is on the device manager list while phone is in fastboot, and seems to be properly
installed; I can't seem to find another suitable driver to update it to anyways.
Beyond that, there don't seem to be any other drivers running in the device manager either.
It's to the point where I'm considering taking the long way around and re-rooting through passimg, but that may not work anyways from what I've been reading, and that still won't fix my fastboot issue.
Any ideas on why I can't get fastboot to work?
my devise manager lists it as 'Android 1.0' when connected with fast boot..
if the drivers were installed on their own, then uninstal them.. and manually update the drivers (download them yourself)
that might help.. idk..
Sent from my nexus one
I think that may be part of the problem because I'm not seeing Android 1.0 on the device manager list. I do have an unknown device on there, but I can't update the driver with any of the Google USB drivers. Also, I'm pretty sure it's not my N1 because I'll unplug the N1, delete the unknown device, and scan for hardware changes and it will pop up again, so I don't think it has anything to do with my phone.
Put your phone in to fast boot, plug the phone in to a different port on your computer. If you have been plugging it in to the front, plug it in to the back. If you have been plugging it in to the back, plug it in to the front.
This should force windows to re-detect your device and it will hopefully install the missing drivers you're needing...
That was a good idea, but I had no luck with that one either. Thanks though.
Alright, shreyas said device is "Android 1.0" from windows device manager when the phone is in fastboot. Why does mine say "Android Bootloader Interface" and is this the case for everyone else?
Even more interestingly, I'll uninstall it, manually install whatever driver I chose for it, and that installation will fail. Then, I'll uninstall it again and have 'puter automatically scan for hardware, "android 1.0" pops up as one of the unknown devices but then gets reassigned as "android Bootloader Interface" after automatically installing drivers.
Oh yeah, I'm running Windows 7 64.
The drivers mentioned here didn't help either
http://forum.xda-developers.com/showthread.php?t=702927
stratmn5105571 said:
Oh yeah, I'm running Windows 7 64.
Click to expand...
Click to collapse
i am on win7 32!
btw umm try this link
http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/
another umm stupid thing mayb, did you try out adb wireless..?
Have you tried using the PDANet drivers? Those are the ones that I've had the best luck with on my Win7 x64 laptop.
EDIT: Seems you have...
I'd recommed using an application called USBDeView (I think?) to manually uninstall all USB drivers for Android/HTC/ADB/NexusOne/etc, and THEN installing the PDANet drivers.
Thanks for your help. I ended up downloading "superboot," which has fastboot on it, and it works just fine. I don't know what the deal is with the fastboot that came with the SDK but my computer just doesn't seem to like it. I checked and rechecked all commands and file directories, and I just don't get it...oh well, I hope this helps others.
Thanks again.
Got my phone about a week ago & got pretty bored of it so I wanted to root it and get a different ROM going. For some reason, I can't get the phone to connect to HTC Sync Manager though I updated the drivers. Any time the phone is switched into USB debugging, My HTC drivers fail to install. I have no idea how to solve this problem. Also when trying to get the Token ID using the command prompt, the device doesn't show up after using the command adb devices either. Need help please.
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
bigdaddy619 said:
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
Click to expand...
Click to collapse
If the phone doesn't have USB debugging enabled, it doesn't appear in the device manager besides under portable devices. Once USB debugging is turned on, Android devices tab appears at the top but the drop down reads My HTC with the yellow triangle with ! on the inside indicating there's some sort of issue. I tried updating the drivers, uninstalling the drivers, restarting the phone and computer, then reinstalling the drivers but nothing has worked thus far. HTC Sync still isn't detecting the phone at all and I can't get the Token ID to continue the rooting process until the device is able to be detected.
HurtMeSole said:
If the phone doesn't have USB debugging enabled, it doesn't appear in the device manager besides under portable devices. Once USB debugging is turned on, Android devices tab appears at the top but the drop down reads My HTC with the yellow triangle with ! on the inside indicating there's some sort of issue. I tried updating the drivers, uninstalling the drivers, restarting the phone and computer, then reinstalling the drivers but nothing has worked thus far. HTC Sync still isn't detecting the phone at all and I can't get the Token ID to continue the rooting process until the device is able to be detected.
Click to expand...
Click to collapse
Windows 8.1?
bigdaddy619 said:
Windows 8.1?
Click to expand...
Click to collapse
No, Windows 7, 64-bit.
HurtMeSole said:
No, Windows 7, 64-bit.
Click to expand...
Click to collapse
Check PM
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
trinity343 said:
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
Click to expand...
Click to collapse
I'm still having the same issue. I gave up for the time being but hopefully someone else had the same issue & can help us out.
HurtMeSole said:
I'm still having the same issue. I gave up for the time being but hopefully someone else had the same issue & can help us out.
Click to expand...
Click to collapse
Same problem here with an HTC One Mini. Its driving me mad!:silly:
trinity343 said:
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
Click to expand...
Click to collapse
Strangely enough, I literally just tried it on a different computer and everything worked exactly as it was supposed to. I had 3 computers in my home, none of which worked but got to work and the laptop they gave me worked just fine. Then I got on my gf's Mac and it went mostly smooth (even though it was difficult not being as familiar with the OS). My advice is do everything you're doing on a different computer until you see it without the ! in the device manager.
Boblud said:
Same problem here with an HTC One Mini. Its driving me mad!:silly:
Click to expand...
Click to collapse
Should try using a different computer. Worked for me after trying several computers.
BD619 said:
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
Click to expand...
Click to collapse
My experience may be helpful. I had no ADB driver, but Composite USB seemed to work. However, the driver install crashed. I needed to open my phone and answer the dialogs on my phone while the driver was installing. After that, everything is hunky-dorry (I know, showing my age).
I was having the same problem until I UNCHECKED the USB debugging mode and reconnected the phone to the computer. Drivers reinstalled and HTC Sync Manager (not HTC Sync--different program) recognized the phone. I had to answer dialogue on phone and then the USB debugging mode status changed itself to enabled. It's all working now, after hours of fiddling.
So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......
Gage_Hero said:
So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......
Click to expand...
Click to collapse
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I will try wugfish to install the drivers and then see if I can use ADB after that.... I definitely did not have the device show up as nexus 6 in device manager other than the mtp part... pretty hard for that not to show up..... I'll give it a shot on Sunday unless the ota drops to the phone first.
A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app
Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.
tvtodd said:
Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.
Click to expand...
Click to collapse
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.
z28 justin said:
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.
Click to expand...
Click to collapse
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....
Gage_Hero said:
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....
Click to expand...
Click to collapse
I followed those instructions as well and it still registered as a Samsung Device. However, I did finally get it to work by going through my "Uninstall or change a program list" and removing a "Samsung Driver Installation" program I had installed for my wife's S4. Then I ran back through Wugfish's driver directions and sure enough, it finally registered as a standard Android device and not a damn Samsung.
I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!
Mephisto_POA said:
I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!
Click to expand...
Click to collapse
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app
I don't know if this will solve your issues. When I was side loading the 5.1 update I couldn't get tmy win 7 machine to see the device after rebooting from adb to sideload.
I ended up finding a thread somewhere that suggested a newer version of adb. Once I downloaded the most recent version it installed fine.
I also rebooted into fastboot through adb, went to device manager and found my nexus, manually updated the driver. After all that everything worked fine.
Don't know if that helps or not....
I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.
Intub8 said:
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I found the problem
each mode has a unique hardware ID
when phone is in normal mode with USB debug, when it is at bootloader and then afterwards when it is in recovery mode
the last mode, hardware ID VID_18D1&PID_D001 didn't get any dirvers installed, evne downloading official drivers from google and other parties.
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
lukesdiesel said:
I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.
Click to expand...
Click to collapse
https://www.reddit.com/r/nexus6/comments/2yyfri/nexus_6_not_getting_detected_during/
check this
got it to work
I got it to work by unplugging and plugging back in once I had hit the adb sideload option in recovery. When I was just in recovery it had no effect.
rkshack
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
thanks. this worked
Mephisto_POA said:
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
Click to expand...
Click to collapse
My device needed %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002.
This happened to me too, I just ended up using a different computer: https://plus.google.com/+LoganJonesJ/posts/hrDRAnyrotf
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Click to expand...
Click to collapse
Worked for me as well, thanks!
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
Worked like a charm. Thanks!
A2CKilla said:
A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks so much for this! I had tried EVERYTHING trying to get my 6P to connect with no success. This simple fix was exactly what I needed.
I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** device
Then I can do "adb reboot bootloader"
Phone shuts down and get on fastboot with this "waiting for device" I got stuck there.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
Sent from my SM-A800F using XDA-Developers mobile app
Yeah I'm experiencing this too as well! I just recently updated to 20p and I am trying to root again. I was able to use fastboot to install twrp before. Don't know why this is happening.
This is what I did
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Bootloader unrecognized
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
wish0 said:
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Click to expand...
Click to collapse
[email protected] said:
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
Click to expand...
Click to collapse
Can one of you share a link to the driver you used?
MaRz0o said:
Can one of you share a link to the driver you used?
Click to expand...
Click to collapse
I'm at work won't get off for another 13 hours but like the post maybe two above here it was Marshall something. Go to device manager look for the boot loader adb interface can't remember exactly what it's called and double click it and use the menu option to rollback not update the driver and you should be good. I tried everything else including the one touch and only the rollback worked.
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
chromiumfan said:
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
Click to expand...
Click to collapse
Do you have the driver? I have none to roll back to.
Okay...
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
wish0 said:
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
Click to expand...
Click to collapse
I am having the "waiting for device" issue. But I dont have the "Marshal London" drivers. I have adb 15 sec drivers installed. Any idea where I could get them?
okay another try..
Okay have you tried, while the waiting for device prompt is up, instead of telling your computer you want to select from the list of drivers, to choose automatic: search online for the driver?
So basically I searched everywhere and found many people with this issue.
I tried everything everyone said.
From installing the drivers, to turning on developer mode.
Also fastboot mode is not working.
I hope my is not a hardware issue. I tried a new cable with the same results.
Anything else I can try?
I have been using FTP to transfer files but I want to root my phone and I can't.
MagilsugaM said:
So basically I searched everywhere and found many people with this issue.
I tried everything everyone said.
From installing the drivers, to turning on developer mode.
Also fastboot mode is not working.
I hope my is not a hardware issue. I tried a new cable with the same results.
Anything else I can try?
I have been using FTP to transfer files but I want to root my phone and I can't.
Click to expand...
Click to collapse
Did you enable USB debugging in Developer mode?
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Did you enable USB debugging in Developer mode?
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Yes, that didn't help either
MagilsugaM said:
Yes, that didn't help either
Click to expand...
Click to collapse
The last time I read about someone having a similar problem it was resolved by using an original cable. But I can't find the thread where this was discussed.
Sent from my OnePlus 3T using XDA Labs
Just to rule it out, after you connect your cable are you seeing the Notification with USB options and have you selected 'Data Transfer', (or whatever it's called)?
If you are seeing the Notification and the PC still can't see the device, uninstall whatever Drivers and ADB packages you currently have installed. Download the ADB package from Google and, when prompted, say 'yes' to installing the Drivers.
Make sure you try all your available USB ports.
Are there any Yellow exclaimation marks in Device Manager? Do you have the most recent Motherboard drivers from your Manufacturers website?
Dirk said:
Just to rule it out, after you connect your cable are you seeing the Notification with USB options and have you selected 'Data Transfer', (or whatever it's called)?
If you are seeing the Notification and the PC still can't see the device, uninstall whatever Drivers and ADB packages you currently have installed. Download the ADB package from Google and, when prompted, say 'yes' to installing the Drivers.
Make sure you try all your available USB ports.
Are there any Yellow exclaimation marks in Device Manager? Do you have the most recent Motherboard drivers from your Manufacturers website?
Click to expand...
Click to collapse
Yes, I updated the drivers too.
I tried uninstalling the google drivers and everything you mentioned.
No the notification doesn't show up and my device doesn't show up on device manager.
I am running windows 10 latest update.
MagilsugaM said:
Yes, I updated the drivers too.
I tried uninstalling the google drivers and everything you mentioned.
No the notification doesn't show up and my device doesn't show up on device manager.
I am running windows 10 latest update.
Click to expand...
Click to collapse
If you have a can of compressed air, try blowing out the USB port. There may be debris up there. It does sound like a Hardware problem. You really need to try it on another PC to know for sure.
You don't have any issues when charging?
Dirk said:
If you have a can of compressed air, try blowing out the USB port. There may be debris up there. It does sound like a Hardware problem. You really need to try it on another PC to know for sure.
You don't have any issues when charging?
Click to expand...
Click to collapse
The phones charges perfectly, I already cleaned out the port.
So, I still have this issue and I wasn't able to solve it. Pretty much the phone only charges, doesn't get recognized by any computer. I also tried my laptop and same thing happens. How do I find out if it's a hardware issue?
Is there any way to save the phone?
i got this too , stuck in recovery and fastboot because i cant connect my device in any pc
MagilsugaM said:
So, I still have this issue and I wasn't able to solve it. Pretty much the phone only charges, doesn't get recognized by any computer. I also tried my laptop and same thing happens. How do I find out if it's a hardware issue?
Is there any way to save the phone?
Click to expand...
Click to collapse
You can connect your PC to your phone without cables using ADB over wifi provided your phone is rooted and on the same wifi network as your PC.
I know this won't solve your hardware problem but it does allow you to move files between your PC and your phone using ADB.
Note that this doesn't work in recovery or fastboot modes.
Here's how:
On the phone using Terminal
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
On the PC in a command terminal
adb connect xxx.xxx.xxx.xxx:5555
...
adb disconnect xxx.xxx.xxx.xxx:5555
where xxx.xxx.xxx.xxx is the phone's IP address
To set the phone back to normal (optional)
On the phone
su
setprop service.adb.tcp.port -1
stop adbd
start adbd
Sent from my OnePlus 3T using XDA Labs
I fix using a old PC that a have connected and installed drivers before but was a windows 7 , I delet all drivers content about phones and USB and re installed again using the unbrick tools and drivers , plugged the phone in fastboot and magically was recognized again ..
MagilsugaM said:
So, I still have this issue and I wasn't able to solve it. Pretty much the phone only charges, doesn't get recognized by any computer. I also tried my laptop and same thing happens. How do I find out if it's a hardware issue?
Is there any way to save the phone?
Click to expand...
Click to collapse
You could also try using flash drive via OTG. This won't help you connect to PC/Laptop in any way, but could at least progress a bit that the phone hardware is okay for data part.
This problem start again , fortunelly im in nougat so if i go to dev options and change the usb charging to mtp his comes to charging again . I think this is the problem , the phone dont comes to mtp so dont "have" a device in windows to connect , with this im unable to make root and do anything in fastboot because my phone lock to usb only for charge