I'm not sure if this is the correct forum for this, but anyway... I'm trying to connect my HTC One M8 (international edition - I'm in Australia) to linux. What should happen is that once the phone is plugged in to a USB port, then the linux command "lsusb" should show you that it's connected, and then you can go on with adb and fastboot. Well, on my system, lsusb shows nothing. I've tried four or five different cables, both USB ports (on my laptop), I've tried with USB debugging enabled and disabled, I've tried with mode set to charging, MTP, PTP. Nothing makes any difference; the phone remains completely invisible to the OS.
Is there something else I haven't tried? Or should I give up on this as a bad job, and live with the phone having its bootloader locked? FWIW, I'm using Archlinux, on a Lenovo X1 Carbon 3rd gen.
If this is not the right place for a question such as this, I'd be happy to be pointed in the direction of a better forum.
Thanks!
hello, the adb is it work in recovery mod?
please poste the output of lsusb, adb devices and fastboot devices.
in fastboot mod for the last commande.
Usb-utils installed? Or is it something different for archlinux?since ubuntu needs usbutils
Related
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Subscribed
I'm having the same issue. Stock non rooted and it will not connect. I have tried it on other computers cables ports everything.
Art2Fly said:
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Click to expand...
Click to collapse
You might try a different cord.
Open Device Manager in Windows and then plug the phone in. Do you see it in the list with a little yellow triangle? Do you see Android USB Devices listed?
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
beamer1341 said:
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
Click to expand...
Click to collapse
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Art2Fly said:
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Click to expand...
Click to collapse
Uninstall all HTC drivers and HTC Sync. Then connect the phone. DO NOT choose the option to automatically install any drivers.
Open Device Manager, find the phone. Select the option to manually pick the driver, and select the generic MTP device driver.
This is what worked for me, after countless attempts at re-installing various HTC drivers, different cables and ports, etc.
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Art2Fly said:
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Click to expand...
Click to collapse
Have you tried revoking the USB debugging authorization and then accepting the RSA fingerprint key again when connecting to PC?
Obviously it can't be an USB cable problem if you can connect to it in bootloader mode and use fastboot commands.
To clarify, the phone just charges when connected, it does not detect that it is connected to PC so debugging doesn't even trigger, neither does mtp. I don't even get the slow charging notification
Does it do the same when you plug it in and reboot the computer to "pick up" during boot up process? Or if you run a live CD? I never had an issue like that with my phone but I did have a similar problem with the USB external blu ray drive I bought some time ago. The pc just didn't detect it at all not on any of the ports until I rebooted my PC with the drive already plugged it and for some reason it picked it up. <Not a solution as I don't know what caused it to not be detected in the first place but still...
Not sure if it's an issue with the device(Phone for you, blu ray drive for me) or if it's a problem with the PC even though other things might still work for you as it definitely did for me(phone, headset, mouse, keyboard, usb extender + all the external hard-drives connected to it)...
Problem exists in all computers, Mac, pc, linux
Did you try what I suggest in Post #6 above?
This worked for me when I had the same issue. adb and fastboot would work, but it would not mount MTP.
And just in the last day or 2 I helped someone else with the same issue and fix.
The phone doesn't show up in device manager.
Have you modify the Kernel? (Applying some settings for example)
I browsed over the web for this issue and found some people with the same problems. They solved by removing the settings applied on the kernel or flashing a new one.
I've flashed various kernels and ruu, still same result
Still looking for help
I'm trying to unlock the bootloader on my daughter's G4, and I have run into a heavy snag. I get "code 10" (driver can not start) when it's in fastboot mode, but I'm fully able to connect with adb when the phone's up and running. This is not my first rodeo, and I'm sure the USB cable works (original cable), I have enabled USB Debugging (or ADB wouldn't work in the first place) and I think I have done everything else that should be done. But the damn thing won't work on any of my computers, under Windows 7 or 10. Driving me nuts! Also when it's booted up I see it as an LG Mobile ADB interface, but when it's on Fastboot it insists that it is an MTP device, even if I have set it as a PTP device when it's booted up. Can anybody please tell me what I have to do to get this to work? Another thing is that if I run "adb reboot-bootloader" (or even the wrong syntax (at least I think the dash should be there) "adb reboot bootloader", which LG's page says), it will not boot into fastboot/bootloader, it reboots into Android. So I have to get into the setup by holding in vol + and plugging in the USB cable. But I don't know if this is related.
Edit: Oh, btw, I have tried to find the latest drivers, so far I'm on 4.0.0.0. They are dated May 2015.
Hello everyone!
I recently decided to root my G4 (h815) and have downloaded the ADB drivers and have the drivers needed for the G4 however when I plug the phone into the PC ADB doesn't recognise the device is connected, even though the PC does know the phone is plugged in.
I have the phone set up correctly for debugging, and when I change to USB tethering the PC does make the little noise when a device is plugged in. I have tried in both USB 2 and USB 3 ports on two computers.
If it makes any difference the commands I used to try and get ADB to do something are:
ADB USB
ADB devices
Both say thre is no device connected.
Thanks in advance, sorry if this is in the wrong place.
Had the problem too, used WIN10, WIN 7, WIN XP. So i switched to Ubuntu.....that did the trick
are you enabled USB debugging in developers options?
Yes ADB is enabled.
I might try dualbooting with Ubuntu then. Seems odd that it doesn't work with Windows.
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
I seem to remember the same thing happening when I got mine a couple days ago and unlocked the BL within a few hours of unboxing. I ended up doing the standard unlock followed by unlock critical commands anyway. Worked fine for me.
morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
Try just turning the phone off and then entering fastboot via volume down and power button. THEN, plus in your phone. Do a 'fastboot devices' and see if it shows up now. In my experience, I got my phone...checked oem unlock and all that...booted into fastboot mode via hard method. And my phone is detected instantly. I did not install any drivers, update platform tools (mine is from like 2012), and even used a third-party USB-C cable. It works every time. Also, I am using the adb and fastboot executables from an older adb minimal set. Probably from like a year or so ago. I don't ever use the SDK ones really anymore.
morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
I'd check and make sure your adb/fastboot is up to date, or do a reinstall just in case.
There are so many options for adb/fastboot and drivers. Where does one find "the latest," that everyone is speaking of?
Thanks for the suggestions but still not working. Even tried disabling driver signature verification at startup. I'm going to uninstall everything, factory reset the device and start over. Might also try a usb-c to usb-a cable. Any other thoughts?
Update: Nothing worked until I used a usb-c to usb-a cable, then it worked like a charm. Must be a Lenovo thing.
morrowa2 said:
Thanks for the suggestions but still not working. Even tried disabling driver signature verification at startup. I'm going to uninstall everything, factory reset the device and start over. Might also try a usb-c to usb-a cable. Any other thoughts?
Update: Nothing worked until I used a usb-c to usb-a cable, then it worked like a charm. Must be a Lenovo thing.
Click to expand...
Click to collapse
I can't even get adb to recognize my device ....I have used multiple cables I'm about to return this phone
canemaxx said:
I can't even get adb to recognize my device ....I have used multiple cables I'm about to return this phone
Click to expand...
Click to collapse
have you tried a usb-c to usb-a cable. that worked for me.
morrowa2 said:
There are so many options for adb/fastboot and drivers. Where does one find "the latest," that everyone is speaking of?
Click to expand...
Click to collapse
Latest ADB/fastboot: https://developer.android.com/studio/releases/platform-tools.html
Latest USB driver: https://developer.android.com/studio/run/win-usb.html
I had no luck except about once in 20 it'd work. Then swapped to a different USB-C port on my laptop, then it worked. FWIW, I tried USB-C to USB-C and USB-C --> USB-A (adapter) to USB-C and it didn't make a difference.
js042507 said:
Try just turning the phone off and then entering fastboot via volume down and power button. THEN, plus in your phone. Do a 'fastboot devices' and see if it shows up now. In my experience, I got my phone...checked oem unlock and all that...booted into fastboot mode via hard method. And my phone is detected instantly. I did not install any drivers, update platform tools (mine is from like 2012), and even used a third-party USB-C cable. It works every time. Also, I am using the adb and fastboot executables from an older adb minimal set. Probably from like a year or so ago. I don't ever use the SDK ones really anymore.
Click to expand...
Click to collapse
I did this and when in the bootloader screen, I am able to display fastboot devices, but when I go into recovery mode and try and flash something via ADB (the November patch since I am not pulling it OTA), it seems to start but it just sits at "Verifying update package" on the phone and "loading: 'taimen-ota-******.zip'" and never progresses. Almost like the PC and the phone are not talking properly?
tluley51 said:
I did this and when in the bootloader screen, I am able to display fastboot devices, but when I go into recovery mode and try and flash something via ADB (the November patch since I am not pulling it OTA), it seems to start but it just sits at "Verifying update package" on the phone and "loading: 'taimen-ota-******.zip'" and never progresses. Almost like the PC and the phone are not talking properly?
Click to expand...
Click to collapse
Like others have stated, maybe try a USB-C to regular USB-A cable. I have only used that type of cable, but didn't realize that the actual cable that comes with the phone might be a problem. I never used it to test that theory though.
js042507 said:
Like others have stated, maybe try a USB-C to regular USB-A cable. I have only used that type of cable, but didn't realize that the actual cable that comes with the phone might be a problem. I never used it to test that theory though.
Click to expand...
Click to collapse
Yeah that is all I have ever used. I use a USB A to C Cable Matters cable.
tluley51 said:
Yeah that is all I have ever used. I use a USB A to C Cable Matters cable.
Click to expand...
Click to collapse
I don't know then. I haven't attempted the update yet to provide any feedback. However, others have reported this issue in the 'November OTA' thread. I would look there.
morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
For anyone in the future, ensure the that Device Manager is showing the 'Android Composite ADB Interface' driver installed.
Then, just download the latest Platform Tools (from https://developer.android.com/studio/releases/platform-tools), and from inside that folder, open a Powershell prompt, and then 'adb reboot bootloader'. Once you are in the 'fastboot' mode, the 'fastboot devices' command works.
I had the same problem. I fixed it by plugging in my UBS-C to USB-A cable into a USB 3 port instead of a USB 2 port.
I am facing the same issue, its been almost 20 days. Tried everything but couldn't get it worked. So dropped the idea of rooting my px2L
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
cooltime said:
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
Click to expand...
Click to collapse
worked for me thanks.
cooltime said:
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
Click to expand...
Click to collapse
This works... Get the Google Driver.
Fastboot does not recognize when unlocking bootloader.Fastboot does not recognize when unlocking bootloader.
Check to make sure you have the latest drivers installed.
I could not for the life of me get it to work on my windows laptop. Tried installing the OnePlus USB Drivers, tried isntalling generic USB drivers, rebooted multiple times, tried differetn cables, tried different versions of ADB, through chocolatey and the minimal ADB installer here on XDA.
On my other laptop running Arch Linux i installed the android-tools package and it worked perfectly though. adb reboot, and then fastboot devices, and fastboot oem unlock on first try.
I have one device (I do not remember what one) that always needed to be unplugged on the computer side after a reboot to bootloader for fastboot to find it.
A bit annoying but, I got use to it. I use USB-A 2.0 Port to USB-Micro/USB-C cables.
Unplugging the cable on the device side did not make a difference, it had to be the computer side.
Also try a different cable and USB port on computer.
Not sure if it helps or makes a difference in your circumstance. ¯\_(ツ)_/¯
I just remember it driving me crazy until I accidentally unplugged it and it was found as soon as I plugged it back in.
Cheers.
PS.
Found a post I recently made about cables I use for adb/fastboot.
USNF - [ xdaThread ] - Post # 2,638