Hi,
Using Lineage beckham jleebl 20191007, unlocked and working previously.
Charging over USB works fine.
USB debugging enabled.
Default USB configuration set to file transfer
HTML:
adb devices
results in "List of devices attached" & no devices
HTML:
fastboot devices
returns nothing
Above commands tried OS and bootloader, same results.
Cannot connect to transfer files, or adb push.
I have gone over many of the proposed solutions for file transfer not appearing as an option, none have worked. I took the phone to an repair shop, they cleaned the USB port, but essentially said, "lol, you're phone's broke". Said there was no obvious hardware issue.
Trying to boot into recovery mode just dumps me back into the bootloader. Can't push boot TWRP as fastboot can't communicate with device.
Any help would be SOOOO appreciated. Not being able to update the OS is causing many problems.
Thanks!!
hexagface said:
Hi,
Using Lineage beckham jleebl 20191007, unlocked and working previously.
Charging over USB works fine.
USB debugging enabled.
Default USB configuration set to file transfer
adb devices
results in "List of devices attached" & no devices
fastboot devices
returns nothing
Above commands tried OS and bootloader, same results.
Cannot connect to transfer files, or adb push.
I have gone over many of the proposed solutions for file transfer not appearing as an option, none have worked. I took the phone to an repair shop, they cleaned the USB port, but essentially said, "lol, you're phone's broke". Said there was no obvious hardware issue.
Trying to boot into recovery mode just dumps me back into the bootloader. Can't push boot TWRP as fastboot can't communicate with device.
Any help would be SOOOO appreciated. Not being able to update the OS is causing many problems.
Thanks!!
Click to expand...
Click to collapse
Wait, you took your phone to a repair shop, they told you it's busted,. So you are here looking for a magician, to whammy your phone? When you find one, please ask for lotto numbers, and forward them to me.
Check that you are using data capable usb cable, some cheap cables are only charge capable.
Otherwise, light a candle.
just 4 causes: 1.- moto drivers and Usb debugg ,2.- usb PC, 3.- Usb phone or 4.- usb cable. The option 4.- need repair.
Related
I know there's a few threads already about this issue and believe me i looked at them all..i didn't find an answer yet.
It all started a few weeks ago(on my Mac with Mavericks) when i was trying to transfer music,I was using htc sync manager as i did many times before without problems,
then decided to use Android file transfer..Didn't work...so i uninstalled both and re-installed htc sync manager and that didn't work as well.
So i went to windows (8.1) installed countless times the latest HTC drivers,SDK (adb and fastboot) not showing up, keeps saying waiting for device.
Same thing with windows Vista(lol i know) and win 7 ultimate and another mac as well and nothing...even tried 4 different cables.
of course USB Debugging is enabled and tried different roms doing a clean install with same results.
If it is hardawre failure i would just return the device to stock and get it fixed, but i can't because I'm S-ON Rooted( to return to stock i need S-off) I can't get S-off if Fastboot and adb don't see my device.
M7_ul pvt ship S-on
hboot 1.54.0000
radio- 4A.17.3250.14
os-2.24.980.2
Jul.9-2013
I don't usually post because i like to resolve the problems on my own, but this time I'm stuck any help is greatly appreciated.
digitallsin said:
I know there's a few threads already about this issue and believe me i looked at them all..i didn't find an answer yet.
It all started a few weeks ago(on my Mac with Mavericks) when i was trying to transfer music,I was using htc sync manager as i did many times before without problems,
then decided to use Android file transfer..Didn't work...so i uninstalled both and re-installed htc sync manager and that didn't work as well.
So i went to windows (8.1) installed countless times the latest HTC drivers,SDK (adb and fastboot) not showing up, keeps saying waiting for device.
Same thing with windows Vista(lol i know) and win 7 ultimate and another mac as well and nothing...even tried 4 different cables.
of course USB Debugging is enabled and tried different roms doing a clean install with same results.
If it is hardawre failure i would just return the device to stock and get it fixed, but i can't because I'm S-ON Rooted( to return to stock i need S-off) I can't get S-off if Fastboot and adb don't see my device.
M7_ul pvt ship S-on
hboot 1.54.0000
radio- 4A.17.3250.14
os-2.24.980.2
Jul.9-2013
I don't usually post because i like to resolve the problems on my own, but this time I'm stuck any help is greatly appreciated.
Click to expand...
Click to collapse
can you post a screen shot of android devices in device manager on the windows PC.
also were these all different computers ? and none see your phone at all ?
you do realize adb devices only works when the phone is in recovery or booted to android and fastboot devices only works when in the bootloader with fastboot usb showing
Thanks for the reply
Nothing comes up in device manager in any of the computers,
Also I was able to run the command "adb devices" in Mac or Windows and it would show a number... Not anymore.
Now just says waiting for device....
And fastboot doesn't work ither in"hboot' or bootloader
digitallsin said:
Thanks for the reply
Nothing comes up in device manager in any of the computers,
Also I was able to run the command "adb devices" in Mac or Windows and it would show a number... Not anymore.
Now just says waiting for device....
And fastboot doesn't work ither in"hboot' or bootloader
Click to expand...
Click to collapse
Have you tried a different micro usb cable? I have like 5 different cables running around my house and only one allows my phone to be recognized by adb through my pc. Try that.
telegraph0000 said:
Have you tried a different micro usb cable? I have like 5 different cables running around my house and only one allows my phone to be recognized by adb through my pc. Try that.
Click to expand...
Click to collapse
well so far i have tried 6-7 cables of different type from friends and of mine, but only one is the original cable from HTC, and none of them work...i can charge, but that's about it. ( and that stupid message i get when i plug it in the computer...Slow charge,The connected charger will take longer to charge...blah blah blah)
i can only think of a corrupted file of some sort, but that wouldn't make sense because i did a clean install many times. Unless new roms (kikat) require USB 3? uhmm i doubt it.
I'll just keep trying different cables
Any suggestions are welcome.
digitallsin said:
well so far i have tried 6-7 cables of different type from friends and of mine, but only one is the original cable from HTC, and none of them work...i can charge, but that's about it. ( and that stupid message i get when i plug it in the computer...Slow charge,The connected charger will take longer to charge...blah blah blah)
i can only think of a corrupted file of some sort, but that wouldn't make sense because i did a clean install many times. Unless new roms (kikat) require USB 3? uhmm i doubt it.
I'll just keep trying different cables
Any suggestions are welcome.
Click to expand...
Click to collapse
sounds more like a hardware problem with the usb port on your phone, try cleaning it (maybe using a compressed air can or similar) to get any debris out.
nkk71 said:
sounds more like a hardware problem with the usb port on your phone, try cleaning it (maybe using a compressed air can or similar) to get any debris out.
Click to expand...
Click to collapse
lol funny you should say that because that's exactly what i did tonight but still not working...but i was reading somewhere else that it could be a corrupted HBOOT, but i have no idea how to change that..
I'll keep you updated just in case some other people have the same issue
digitallsin said:
lol funny you should say that because that's exactly what i did tonight but still not working...but i was reading somewhere else that it could be a corrupted HBOOT, but i have no idea how to change that..
I'll keep you updated just in case some other people have the same issue
Click to expand...
Click to collapse
if hboot was corrupted, you would have a brick on your hands; and since you're S-On, no way you can corrupt it.
hboot 1.44/1.54 don't play nice with Windows 8.1, but Windows 7 and Mac shouldn't have any issues.
If you really want to try another way, just make yourself an Ubuntu 12.04 (32bit) Live USB, boot from that, install adb & fastboot (you can check my guide in the FAQ section on how to do that)
then try
sudo fastboot devices in bootloader
adb devices in custom recovery
adb devices in booted up ROM (with USB debugging enabled)
nkk71 said:
if hboot was corrupted, you would have a brick on your hands; and since you're S-On, no way you can corrupt it.
hboot 1.44/1.54 don't play nice with Windows 8.1, but Windows 7 and Mac shouldn't have any issues.
If you really want to try another way, just make yourself an Ubuntu 12.04 (32bit) Live USB, boot from that, install adb & fastboot (you can check my guide in the FAQ section on how to do that)
then try
sudo fastboot devices in bootloader
adb devices in custom recovery
adb devices in booted up ROM (with USB debugging enabled)
Click to expand...
Click to collapse
Ok I'll try that tomorrow. Thanks for the help
nkk71 said:
if hboot was corrupted, you would have a brick on your hands; and since you're S-On, no way you can corrupt it.
hboot 1.44/1.54 don't play nice with Windows 8.1, but Windows 7 and Mac shouldn't have any issues.
If you really want to try another way, just make yourself an Ubuntu 12.04 (32bit) Live USB, boot from that, install adb & fastboot (you can check my guide in the FAQ section on how to do that)
then try
sudo fastboot devices in bootloader
adb devices in custom recovery
adb devices in booted up ROM (with USB debugging enabled)
Click to expand...
Click to collapse
Unfortunately i get nothing....but i must say..only once on my phone it said USB Connected tap to change settings, if clicked on it gave me the option of choosing a tethering choice (bluetooth,wifi,....) with no errors, i thought it was fixed.Then i run the commands and nothing:crying:
btw I'm liking Ubuntu...now i got 3 operating systems at boot:good:
If you got anymore ideas please, I'm all ears:fingers-crossed:
1.sudo fastboot devices in bootloader <=== i get nothing back
2.adb devices in custom recovery
[email protected]:~/android-sdk-linux/platform-tools$ sudo ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$
3.adb devices in booted up ROM (with USB debugging enabled)[/QUOTE]
[email protected]:~/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$
digitallsin said:
Unfortunately i get nothing....but i must say..only once on my phone it said USB Connected tap to change settings, if clicked on it gave me the option of choosing a tethering choice (bluetooth,wifi,....) with no errors, i thought it was fixed.Then i run the commands and nothing:crying:
btw I'm liking Ubuntu...now i got 3 operating systems at boot:good:
If you got anymore ideas please, I'm all ears:fingers-crossed:
1.sudo fastboot devices in bootloader <=== i get nothing back
2.adb devices in custom recovery
[email protected]:~/android-sdk-linux/platform-tools$ sudo ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$
3.adb devices in booted up ROM (with USB debugging enabled)
Click to expand...
Click to collapse
[email protected]:~/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$[/QUOTE]
sounds like a hardware issue: phone usb port and/or pc usb port and/or cable
nkk71 said:
[email protected]:~/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$
Click to expand...
Click to collapse
sounds like a hardware issue: phone usb port and/or pc usb port and/or cable[/QUOTE]
Im having the same problem i got the computer to see the phone because i went under device manager and updated the driver manually but i still cant get adb to see my device
getmoneygreen said:
Im having the same problem i got the computer to see the phone because i went under device manager and updated the driver manually but i still cant get adb to see my device
Click to expand...
Click to collapse
is it showing up as My HTC? like in FAQ #2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
also adb will only work in custom recovery
or a booted ROM with USB Debugging enabled
EDIT: and these drivers here seem to be working for a lot of people: http://forum.xda-developers.com/showthread.php?t=2588979
Same problem
digitallsin said:
I know there's a few threads already about this issue and believe me i looked at them all..i didn't find an answer yet.
It all started a few weeks ago(on my Mac with Mavericks) when i was trying to transfer music,I was using htc sync manager as i did many times before without problems,
then decided to use Android file transfer..Didn't work...so i uninstalled both and re-installed htc sync manager and that didn't work as well.
So i went to windows (8.1) installed countless times the latest HTC drivers,SDK (adb and fastboot) not showing up, keeps saying waiting for device.
Same thing with windows Vista(lol i know) and win 7 ultimate and another mac as well and nothing...even tried 4 different cables.
of course USB Debugging is enabled and tried different roms doing a clean install with same results.
If it is hardawre failure i would just return the device to stock and get it fixed, but i can't because I'm S-ON Rooted( to return to stock i need S-off) I can't get S-off if Fastboot and adb don't see my device.
M7_ul pvt ship S-on
hboot 1.54.0000
radio- 4A.17.3250.14
os-2.24.980.2
Jul.9-2013
I don't usually post because i like to resolve the problems on my own, but this time I'm stuck any help is greatly appreciated.
Click to expand...
Click to collapse
Did you ever get Fastboot working to display your device? I tried 3 different OSs, 3 different cables and every possible driver out there. I can push files back and forth when connect to pc in normal operating mode. I can do an "adb reboot bootloader" command and it will reboot to bootloader, My device manager shows the phone without yellow exclamation mark, but when I issue "adb devices" it successfully starts server but doesn't list device????? Losing my mind. I need to update my radio and firmware desperately.
daddygene said:
Did you ever get Fastboot working to display your device? I tried 3 different OSs, 3 different cables and every possible driver out there. I can push files back and forth when connect to pc in normal operating mode. I can do an "adb reboot bootloader" command and it will reboot to bootloader, My device manager shows the phone without yellow exclamation mark, but when I issue "adb devices" it successfully starts server but doesn't list device????? Losing my mind. I need to update my radio and firmware desperately.
Click to expand...
Click to collapse
Mine was hardware problems I ended up taking it back to Optus (Australia) and they gave me a refurbished one which had the exact same problem...sent it in again and got another one back, looks to be ok now but I'm very disappointed with HTC so I gave it to my wife and got myself the Galaxy s5 and didn't look back. sorry I can't be of any help
I recently tried to install PureNexus 7.1.2 along with the latest version of GApps 20170610. There seems to be some sort of conflict with that version of Google Play Services that prevents my device from completing setup. Without completing setup, I'm not able to do anything with the phone.
In an attempt to save myself, I want to go back to the older version of the ROM and GApps that worked, but first they need downloaded. In the past, I could go into TWRP and mount my device to my PC and transfer the files I needed to install. Now, Windows is showing my device as Unknown USB Device (Device Descriptor Request Failed). Going through every thread I could find about updating drivers, etc, it still does not work. This used to work just fine in the past on the same PC (Windows 10).
Both adb and fastboot don't seem to work either. There is no device found. When I boot the phone into Bootloader mode and plug in the USB cable, it shows Transfer Mode: USB Connected but running fastboot on the PC still can't find anything.
I am not sure how else to go about getting the necessary files on the device to flash them.
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
tristanlee85 said:
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
Click to expand...
Click to collapse
It could be just a dirty usb port.
Where's answers
ktmom said:
It could be just a dirty usb port.
Click to expand...
Click to collapse
Unfortunately I do not think that is the case. I have used a number of different means to clean the connection with rubbing alcohol and electrical terminal cleaner, small utensils to get in there and clean the contacts, but no luck. I am to the point now where the phone won't boot up the OS. I can get into TWRP and the Bootloader, but from there I have no way to transfer files to the device.
Bluetooth was my option before, but that is when the device would boot. There's no way to enable BT from recovery right? I am trying to reset the phone back to stock to trade it in to Google, but I am afraid I am going to be out $100 since it seems to be as good as dead now.
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
No big deal right? I mean sure, I didn't make a back up first (Mistake #2) but it shouldn't matter because I can just go into twrp and factory reset and reflash everything.
So off I went to copy over the zips to my phone -- went ahead and wiped everything (mistake #3) and then opened up windows explorer to copy over the zips. Turned out my computer couldn't see my phone.
I tried mounting and unmounting and installing and uninstalling drivers. Moving over to my other computer (linux mint) messing around with adb sideloads, and lastly tried using OTG. Turned out my computer just couldn't register my phone at all with adb.
So then I switched to fastboot -- at the very least I should be able to reflash stock and then root and then install custom stuf, right? But I couldn't get my phone to even register on windows or linux with driver changes using fastboot!
I was pretty upset at this point (still am, admittedly).
In fastboot mode whenever I plug in my phone my computer doesn't even bat an eye, and my phone just says it's waiting for a data cable connection. Windows will register it after a while as a "code 43: Windows has stopped this device because it has reported problems" after a while but I still wasn't able to get the right drivers to register the device. Doesn't even show up in lsusb in linux.
Wondering now if maybe when the device was alive I forgot to enable adb debugging first or maybe it doesn't register because it was set to charge only in the usb mode setting. Is there a way to change those settings in recovery like through the terminal? I would love to hear any possible solutions, I've been googling and search xda all over the place so any insight would be really appreciated.
Fortunately I had an extra shamu (with a very cracked screen) left over that I switched to in the mean time, but I'd like to get my old phone back in working order if possible! Any help or insight is appreciated!
gunha said:
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
Click to expand...
Click to collapse
You even made more errors. You don't seem to read properly. Franco does only support shamu up to nougat.
- Did you install the latest USB drivers and latest platform tools (adb, fastboot ...)
- Did you boot you phone into bootloader when you tried to connect?
Yup! I installed drivers from Google when I downloaded the platform-tools. I put my phone in bootloader mode when using fastboot, and my phone never indicated 'USB transfer cable connected' it just said 'connect usb.' also fastboot just said waiting for devices when I tried doing a getvar all....
try it on another laptop, try a new usb cable...you seem to have done everything right
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
gunha said:
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
Click to expand...
Click to collapse
Could be the cable. But the USB port could also be the cause. The simplest solution could be that the port is just full of dust. In that case, cleaning will help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
IF you still have access to TWRP, you can move your zips on an usb drive and connect it via otg and mount in TWRP and flash from the USB drive. Might help.
Hello,
I was on 10.0.7 version, rooted with magisk.
I had error while installing 10.0.8 version, then I downloaded 10.0.7 full rom, and used flash_all_except_data.bat.
Then after rebooting, it runs infinitely on loading animation (colors bar).
When I enter in fastboot, fastboot logo is displayed, but pc doesn't recognize phone anymore (fastboot devices show nothing).
[UPDATE]
I managed to boot with wiping data from recovery (Xiaomi stock recovery).
Now I can use the phone, but I don't have wifi (maybe something messed with vendor).
And I can't flash it because it is not recognized in fastboot mode (tried 3 W10 PCs, and 1 W7, it doesn't show in device manager)...
Can you help me ?
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
MIN313 said:
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Click to expand...
Click to collapse
In fastboot mode nothing shows in device manager, with 3 different cables, with 4 different computers (3x W10, 1xW7).
I tried connecting with a live cd of CentOS.
Same results, adb connect when phone is started, but when I go in fastboot mode nothings shows in lsusb or dmesg...
Looks like the phone doesn't connect to pc in fastboot, very very strange...
Hello ,
I encountered a very weird problem with the usb port.
I have turned on USB-debugging but my phone doesn't show the connection dialog that indicates the state of phone connection.
I experienced this on a windows-10 machine and on an Ubuntu driven machine.
Cables are ok, drivers are ok. I tried to connect an old moto g 1st edition and the rsa dialog showed up and then I could choose if I wanted to recharge the battery or make an another type of connection.
Adb bridge also worked fine with my old phone, so I am sure the computers and the cables are fine.
So I gave an last try to my XT1805. Did a reboot into fastboot mode by using the start and volume down buttons, and to my big surprise the fastboot commands worked fine.
Well after that booted back in normal mode, backed up everything a did a factory reset.
Unfortunately that didn't solve the problem, adb doesn't work but fastboot is ok.
Hope somebody con give me some hints to solve the problem.
Forgot to state that the phone is on Oreo updated by OTA to the most recent version.
Regards
jm_sanders said:
Hello ,
I encountered a very weird problem with the usb port.
I have turned on USB-debugging but my phone doesn't show the connection dialog that indicates the state of phone connection.
I experienced this on a windows-10 machine and on an Ubuntu driven machine.
Cables are ok, drivers are ok. I tried to connect an old moto g 1st edition and the rsa dialog showed up and then I could choose if I wanted to recharge the battery or make an another type of connection.
Adb bridge also worked fine with my old phone, so I am sure the computers and the cables are fine.
So I gave an last try to my XT1805. Did a reboot into fastboot mode by using the start and volume down buttons, and to my big surprise the fastboot commands worked fine.
Well after that booted back in normal mode, backed up everything a did a factory reset.
Unfortunately that didn't solve the problem, adb doesn't work but fastboot is ok.
Hope somebody con give me some hints to solve the problem.
Forgot to state that the phone is on Oreo updated by OTA to the most recent version.
Regards
Click to expand...
Click to collapse
You need to use adb device, in order to use the command while the device is on.
For bootloader:- fastboot (command)
For power on device:- adb (command)
riyan65 said:
You need to use adb device, in order to use the command while the device is on.
For bootloader:- fastboot (command)
For power on device:- adb (command)
Click to expand...
Click to collapse
Forgot to state that 'adb devices' does not show any device connected.
As I said it's not a problem on the computer side as other Android phones are accessed correctly in ' adb shell'.
Regards
jm_sanders said:
Forgot to state that 'adb devices' does not show any device connected.
As I said it's not a problem on the computer side as other Android phones are accessed correctly in ' adb shell'.
Regards
Click to expand...
Click to collapse
To get adb device, you need to enable adb debugging and enable for your pc on phone
riyan65 said:
To get adb device, you need to enable adb debugging and enable for your pc on phone
Click to expand...
Click to collapse
Of course enabled as stated in my first post.
Regards