I'm aware there is another thread on this, but his solution was simply switching the cable. For me, adb is currently working on multiple other phones, but on the G8X, it simply doesn't list the device. Any idea?
I do NOT have the full Android SDK, only the "minimal ADB and Fastboot" package, which just comes with adb, fastboot, and a couple other things. I love it and hope I don't have to install the full SDK for fastboot to work. D:
USB debugging is enabled, the device is connected as "File Transfer," and everything else is as it should be.
1337haXXor said:
I'm aware there is another thread on this, but his solution was simply switching the cable. For me, adb is currently working on multiple other phones, but on the G8X, it simply doesn't list the device. Any idea?
I do NOT have the full Android SDK, only the "minimal ADB and Fastboot" package, which just comes with adb, fastboot, and a couple other things. I love it and hope I don't have to install the full SDK for fastboot to work. D:
USB debugging is enabled, the device is connected as "File Transfer," and everything else is as it should be.
Click to expand...
Click to collapse
Same issue. Trying to use the Button Mapper app, and windows Button Mapper Setup keeps saying "Make sure the device is connected and USB Debugging is enabled."
Help?
You must try multiple times until a notification shows up to trust your PC.
hasso96 said:
You must try multiple times until a notification shows up to trust your PC.
Click to expand...
Click to collapse
Actually it was more "complicated" than that, as it said it ran an older version of the server than the phone at first. I googled some more, and managed to solve it. It was the installation of the LG USB mobile driver. I tried with the windows stock one at first, then tried Google USB driver from the SDKmanager, and even an universal driver didn't work. And even then when it was installed, THEN it said "unauthorized" and I had to just accept the connection on my phone
It's sorted now!
THANK YOU SO MUCH! Man, I wasn't expecting a reply after all this time, figured my unit was somehow defective or something. This worked perfectly! To others suffering, here's the direct link to the LG drivers, current version as of now, 4.4.2: tool.lime.gdms. lge .com/dn/downloader.dev?fileKey=UW00120120425 (Remove the spaces before and after the "lge").
Now I can tweak my system settings, debloat, use Button Mapper. Thanks again!
Related
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
It sounds like the waiting for device message with fastboot it because you're in bootloader (hboot) instead of fastboot maybe. You want to uninstall the HTC sync program, it's used because it installs the drivers then you get rid of the program itself or at least make sure it's not running at startup and when you connect the device. On Windows 8 did you disable the driver signature verification yet?
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
It sounds like the waiting for device message with fastboot it because you're in bootloader (hboot) instead of fastboot maybe. You want to uninstall the HTC sync program, it's used because it installs the drivers then you get rid of the program itself or at least make sure it's not running at startup and when you connect the device. On Windows 8 did you disable the driver signature verification yet?
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same result in fastboot, I'll try uninstalling HTC sync and disabling driver signature verification now and see how it goes
edit: same result, adb devices comes up empty when in fastboot after disabling driver signature verification and uninstalling HTC sync
It should be "fastboot devices" as the command.
Does your computer have native USB 3?
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
It should be "fastboot devices"
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
that returns nothing it just starts a new command line.
and two of the ports are usb 3.0 one is 2.0, I've tried all three
Use the snip tool in windows to grab a screenshot of the command window stretched out to show the history, that may point me in the right direction. Do a search for Windows 8 ADB and Fastboot driver installation (i prefer Google and prefix the search with "site: www.xda-developers.com" no quotes) and you should find a thread with the steps for installing the drivers properly after signature verification is disabled in Windows 8. I used it to remotely fix a user's computer with the same issue you're having but I'm mobile at the moment. I'll help you get it straightened out though that's kind of my specialty. I'm about to go get something to eat, I'm working on a migraine and when I get back I'll check back in. Feel free to PM me if you want while waiting on input from others also.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
Use the snip tool in windows to grab a screenshot of the command window stretched out to show the history, that may point me in the right direction. Do a search for Windows 8 ADB and Fastboot driver installation (i prefer Google and prefix the search with "site: www.xda-developers.com" no quotes) and you should find a thread with the steps for installing the drivers properly after signature verification is disabled in Windows 8. I used it to remotely fix a user's computer with the same issue you're having but I'm mobile at the moment. I'll help you get it straightened out though that's kind of my specialty. I'm about to go get something to eat, I'm working on a migraine and when I get back I'll check back in. Feel free to PM me if you want while waiting on input from others also.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you for the help, I hope this is all you need from the command window. I'm trying the adb and fastboot driver installation thread that you suggested now, hopefully this will have it resolved by the time you get back.
edit: unfortunately that didn't work, it said that the driver is already up to date. The phone shows up as "My HTC" under android USB devices already, even when in the bootloader/fastboot, but it shows the device status as "This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I just have some extra things in the folder like some ROMs/recoveries but I don't think that would matter. I have adb.exe, fastboot.exe, and the two .dll's so I think I have everything I need.
And I tried fastboot reboot while in fastboot, I got waiting for device in command prompt. Also when I entered the command I got a "USB device not recognized" popup from the taskbar. Device manager shows the phone as My HTC with a yellow caution triangle on the icon and the device status "This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
That's usually the result of using a USB 3.0 port, do you have a different set of ports you can try? Like back of the computer instead of front, side of notebook to back of notebook etc. Most motherboards have a USB 2.0 hub and USB 3.0 hub but the manufacturers don't make it obvious which is which in most cases. Also make sure antivirus and such is turned off while you're testing. Its one of those things that's just a tad bit off such as the ports or a driver.
Let me know how the above turns out and tomorrow if you want I can hop on teamviewer and we can try uninstalling what's there, starting fresh with the Google sdk and go from there.
PS- Sorry I haven't had a more direct answer I know it can be frustrating with so much trial and error and it being almost working. But I promise I'll stick with it until we get something figured out, or you get mad and remotely smack me over the head with a keyboard.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
That's usually the result of using a USB 3.0 port, do you have a different set of ports you can try? Like back of the computer instead of front, side of notebook to back of notebook etc. Most motherboards have a USB 2.0 hub and USB 3.0 hub but the manufacturers don't make it obvious which is which in most cases. Also make sure antivirus and such is turned off while you're testing. Its one of those things that's just a tad bit off such as the ports or a driver.
Let me know how the above turns out and tomorrow if you want I can hop on teamviewer and we can try uninstalling what's there, starting fresh with the Google sdk and go from there.
PS- Sorry I haven't had a more direct answer I know it can be frustrating with so much trial and error and it being almost working. But I promise I'll stick with it until we get something figured out, or you get mad and remotely smack me over the head with a keyboard.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm pretty sure I was using the 2.0 port but I could be wrong. I'll keep working on it and if I can't resolve it I'd love to try teamviewer wth you. Thank you so much for all the help so far.
Finally got it working, kept trying on my old computer that I unlocked it originally with and eventually it just decided to recognize it and worked.
Thanks so much for the help getting to this point.
kalbany said:
I'm pretty sure I was using the 2.0 port but I could be wrong. I'll keep working on it and if I can't resolve it I'd love to try teamviewer wth you. Thank you so much for all the help so far.
Click to expand...
Click to collapse
I
Is there an error information, e.g: Windows code 10.
If yes, I googled it, it shows:
The error message probably occurs when you are trying to use a particular piece of hardware, such as a USB connected device or internal DVD drive. Take note of the device you are using when the error occurs in order to update the correct drivers.
error.info/windows/driver-10.html
Cheers,
Lun:
kalbany said:
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
Click to expand...
Click to collapse
I have Started a thread for HTC Droid Incredible phones in the troubleshooting area. Im having the same exact problem and im running Windows
as soon as i do the command: fastboot oem get_identifier_token, it just sits there and waits. and then i get a pop up from the system tray saying that my device has malfunctioned.
CharliesTheMan said:
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Regardless of how old this thread is I'm running into the same problems now!
My Xperia XZ1 Compact doesn't seem to be recognized when in the bootloader (indicated by a black screen and blue led).
I tried "adb reboot hboot" and it booted into a new black screen, but didn't last long before rebooting.
I tried other button combinations during the sequence and those didn't change anything.
Alright so I'm no stranger to flashing ROMS and whatnot, but today I slipped up and deleted everything on my internal storage, including my NANDROID backup. I still have access to my recovery (CWM touch v6.0.4.5). So I thought "no problem, I"ll just ADB sideload". Well here we are.
Basically I can't get my ****ing phone to communicate with my computer. I installed every damn thing I could think of to get my device to show up after typing "adb devices". I tried the universal toolkit, but as expected it didn't work very well. I tried it on my laptop and desktop, through USB 2.0 and 3.0. I installed the generic Android USB ADB driver, I installed HTC sync for DNA drivers, I installed a standalone version of the DNA driver, and no dice. Can't even get fastboot to communicate. Even though my phone says fastboot USB my computer won't recognize it.
This is seriously ****ing pissing me off, because it should be a simple fix. Anybody have words of wisdom to help me out?
Thanks in advance.
FCO2011 said:
Alright so I'm no stranger to flashing ROMS and whatnot, but today I slipped up and deleted everything on my internal storage, including my NANDROID backup. I still have access to my recovery (CWM touch v6.0.4.5). So I thought "no problem, I"ll just ADB sideload". Well here we are.
Basically I can't get my ****ing phone to communicate with my computer. I installed every damn thing I could think of to get my device to show up after typing "adb devices". I tried the universal toolkit, but as expected it didn't work very well. I tried it on my laptop and desktop, through USB 2.0 and 3.0. I installed the generic Android USB ADB driver, I installed HTC sync for DNA drivers, I installed a standalone version of the DNA driver, and no dice. Can't even get fastboot to communicate. Even though my phone says fastboot USB my computer won't recognize it.
This is seriously ****ing pissing me off, because it should be a simple fix. Anybody have words of wisdom to help me out?
Thanks in advance.
Click to expand...
Click to collapse
When your in hboot/fastboot and connected to your computer does it say fastboot usb? If it does when you type in fastboot devices is it recognizing your device at all? Should bring up serial number. Are you on Windows xp/7/8 or 8.1?
Sent from my HTC6435LVW using XDA Free mobile app
Which version of the universal ADB drivers did you use, because I just did this to my phone about a month ago and had the same issue? Once I installed the universal generic driver everything communicated and worked properly.
Try installing PDAnet it blanket installs a bunch of drivers that got me out of a similar spot!
My phone isn't being detected by adb. Almost as if USB Debugging isn't even enabled (which it is). ADB is just blank when I run adb devices.
I've installed the LG VZW G3 drivers. Any suggestions?
Make sure you change the USB mode to internet and then Ethernet. Took me a while to figure that out.
Make sure you have developer options visible
Enable USB debugging
Connect your phone to your computer
Pull down and change the USB connection from installer/MTP to internet > ethernet
Open Command Prompt window where ADB is installed, and type in "adb devices"
Allow when you see the RSA prompt
Run the batch file for ioroot, type "adb reboot recovery", install from adb, run sideload command, and then reboot
Also, make sure you're running the latest version of the SDK. Mine wouldn't work until I updated. HTH!
mjforte said:
Make sure you change the USB mode to internet and then Ethernet. Took me a while to figure that out.
Click to expand...
Click to collapse
+1
Sent from my VS985 4G using Tapatalk
mjforte said:
Make sure you change the USB mode to internet and then Ethernet. Took me a while to figure that out.
Click to expand...
Click to collapse
+1 - This was my problem too...many thanks!
usb drivers
blmartin said:
+1 - This was my problem too...many thanks!
Click to expand...
Click to collapse
Use the LG USB drivers for Verizon Wireless!
Change the usb connection mode to Internet/Ethernet
My adb was the problem on mine. I had to reinstall java jdk and the sdk and worked perfectly the first time I tried after that
asialove2013 said:
Use the LG USB drivers for Verizon Wireless!
Change the usb connection mode to Internet/Ethernet
Click to expand...
Click to collapse
Either I'm completly blind or ... my G3 doesn't have that option. I only got "Charge Phone", "Media Device (MTP)", and "Send images (PTP)" to configure the USB PC CONNECTION. I also have the option to switch on USB tethering, but that doesn't change anything for the better, either.
Where's that Internet/Ethernet connection mode hidden?
The internet option might not appear until the usb is connected to the pc. Recheck available options while connected.
-Set phone for PTP connection
-Plug phone into PC via USB. You should see a driver loading/loaded message on your PC
-On the phone, change USB connection to Internet, then select Ethernet on the submenu that will appear
(PTP seems to "wake up" the ADB driver on the PC side for me. This was mandatory on a couple of prior phones/tablets, so it's what I did with the G3.)
Or switch to Linux and never hear about drivers ever again!
Verizon on Windows 8.1
So, the problem I had on windows 8.1 was that when you connect the device and it asks you what action to take automatically, you need to click that and install the Verizon stuff. I had my phone in USB debugging and Ethernet mode while doing this install. After it installed everything, the window on my phone for debugging permission showed up, and I allowed it. The phone now shows up in adb. I don't know if this was obvious but I thought Id mention it anyway
After the last G3 update from Verizon, the Ethernet option is gone. I can't get it to talk with ADB any longer. I see the developer mode come up on the phone, but it never asks for security key or appears in the ADB list. Anybody have any good ideas? This is on a Mac and I've never had a problem before doing this.
EDIT: After juggling back and forth from PTP to MTP to PTP, restarting ADB, I got it to connect. No clue what the key was, but working again for the moment. The Ethernet option is still gone from the phone though so that simple fix is no longer an issue.
Averix said:
After the last G3 update from Verizon, the Ethernet option is gone. I can't get it to talk with ADB any longer. I see the developer mode come up on the phone, but it never asks for security key or appears in the ADB list. Anybody have any good ideas? This is on a Mac and I've never had a problem before doing this.
EDIT: After juggling back and forth from PTP to MTP to PTP, restarting ADB, I got it to connect. No clue what the key was, but working again for the moment. The Ethernet option is still gone from the phone though so that simple fix is no longer an issue.
Click to expand...
Click to collapse
I installed the skydragon rom, which is based on stock so probably the same. I found that PTP worked but MTP did not. This is in Ubuntu Linux.
I've been having issues with adb on pie. It just doesn't recognise my phone. I've tried uninstalling and reinstalling the drivers but it doesnt work for me. Although, the pc can recognise my phone but not in adb. Whenever i run a adb command i don't get a prompt on my phone asking to allow the pc which is weird. I need help here.
Just had the same issue. On Windows. Reinstalled the adb drivers, didn't help. This, I think, is what resolved it for me, YMMV:
While the phone is plugged to PC,
disabled USB Debugging in Developer Options,
observed a toaster notification on Windows about updating/installing drivers for my phone,
enabled USB Debugging again, clicked Allow on the dialog that popped up,
and I was back in business.
nameanyone said:
Just had the same issue. On Windows. Reinstalled the adb drivers, didn't help. This, I think, is what resolved it for me, YMMV:
While the phone is plugged to PC,
disabled USB Debugging in Developer Options,
observed a toaster notification on Windows about updating/installing drivers for my phone,
enabled USB Debugging again, clicked Allow on the dialog that popped up,
and I was back in business.
Click to expand...
Click to collapse
Thanks. I'll try this once i get back home.
Me too
mayankjet said:
Thanks. I'll try this once i get back home.
Click to expand...
Click to collapse
I have the same problem, and it waas not fixed disabling and enabling USB debugging. Did you found the solution? Or someone found? Or God if you are there listening? Or the devil, i am ready to sell my soul for this.
marcebil said:
I have the same problem, and it waas not fixed disabling and enabling USB debugging. Did you found the solution? Or someone found? Or God if you are there listening? Or the devil, i am ready to sell my soul for this.
Click to expand...
Click to collapse
I think i had to update the adb to its latest version.
Sent from my Nokia 7.1 using XDA Labs
So, I have searched Reddit and other sites for clues and help and I have had no luck. I have even contacted an android developer and had him try on his computer and had no luck.
I am trying to install Lineage OS for 17.1 and am currently trying to root my device. I have downloaded Google USB Drivers directly and tried from Android Studio. It detects my device fine. I go into command and run adb device, it detects my device. I reboot the device into fastboot, windows detects the driver but has no driver to install. I manually install the driver and it says it "Windows could not find the drivers for your device" despite me pointing it to "...AppData\Local\Android\Sdk\extras\google\usb_driver" which is where the driver is located. I click let me pick, install it under Andoid Devic -> Android Bootloader Interface. It says "Successfully Updated Driver" but put the device in "Other Devices" with a "?" on the icon and "Unknown Device". Even tried to see if it still worked but no device was detected (fastboot device). The Google Pixel C is "Waiting for fastboot command . . . . " but that's it.
Tried both drivers downloaded. Windows updated and no driver download. Restart windows countless times. New usb cable. Different usb port including usb 2 and 3. Nothing.
Developer reported same. Any ideas appreciated!
Thanks!
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
jwoegerbauer said:
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
Click to expand...
Click to collapse
Sorry for the slow response.
Same issue. I wouldn't expect otherwise though because the ones straight from Android Studio and Googles website doesn't work. Still shows "Unknown Device" and won't let me install the driver after showing "Waiting for fastboot command. . . ."
Drivers work fine until in fastboot mode.
Waiting for fastboot command. . . .
@slitterell
I'm pretty sure the USB driver ( does NOT mean ADB and/or Fastboot drivers ) you've installed is the culprit: Uninstall it and install the one suitable at 100% to your phone, will say the Google USB driver.
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
@slitterell
The mentioned Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.
So it should be the correct USB-driver in your case.
The latest is attached.
slitterell said:
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
Click to expand...
Click to collapse
Google's driver package doesn't have Product ID of the Pixel C mentioned in its inf file, so it doesn't work for you. Interesting that you got adb connection anyway. So, maybe Windows has installed automatically some driver but it didn't had entry for the bootloader/fastboot.
Here is how people have added those adb entries. Bootloader entry can be found from device manager and added the same way...
https://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
Or you could just use my Yet Another Universal ADB Driver Package
https://forum.xda-developers.com/an...staller-universal-adb-driver-package-t3595277
http://yet-another-universal-adbdriver.blogspot.com/
and hope for the best...