So, finnaly solved!
After reading the whole internet (literally) about this problem happening to many HTC (but not only HTC) phones, including not chargind just when turned off, not recognized by computer (including adb, fastboot), going in car mode, I finally found the solution
Here is what I tried
Several custom and stock kernel and recovery flash, different nandroid backups, different roms including stock even clean install (weird, see later why), different cables, drivers, port cleaning.(RUU isn't possible as the phone doesn't get recognized)
The solution however was muck simpler, just wipe cache and dalvik cache and BAM! all working (at my initial arhd rom)
What I suggest (the order doesn't matter) from all the reading done before conclude it's a hardware problem is:
DO A NANDROID BACKUP!
Try different cables and drivers, even computers
Uncheck the fastboot option in power settings and reset
Clean the port with alcohool (or similar), with the phone shut down and then dry it completely
Wipe cache and dalvik cache
Restore the nandroid backup several times, at some people this did the trick
Boot in safe-mode if possible (APM), this way you can check if it's a 3rd party software that can give problems as in safe mode only stock apps are available
Hope I helped
Hello,
Long story short, out of the blue my One doesn't get recognized by any computer, I tried 3 different laptops, all 3 with win7,different cables, latest HTC drivers installed, uninstalled and installed again, but no succes, even my One doesn't get the usb icons show up when I connect it to any laptop, BUT it does charge
Anyway I tried flashing another Rom,factory reset, kernel but nothing changes, adb and fastboot don't recognize my phone
Also the Icon appears when I connect the phone to an MHL adapter but no picture shows up on TV, it worked before
edit: when booted in fastboot it says fastboot AC, not fastboot usb
The get back to HTC solution is a no go as I don,t have any invoice of buying this phone and in EU is required for warranty
I'm currently on ARHD 41.0 kk 4.4 and Elementalx 10.10.1 kernel, S-off, usb debugging on, TWRP 2.6.3.4
What should I try to fix this? Thanks for any suggestions made!
I have the exact same thing, but the device is the HTC One V. It'll charge, but any attempt for it to be recognized as a usb device fail. I have figured out that the usb connector is bad.
Do you get a snug fit when you plug it in to a usb cable,or is it loose and wobbly?
BCH/HTC said:
I have the exact same thing, but the device is the HTC One V. It'll charge, but any attempt for it to be recognized as a usb device fail. I have figured out that the usb connector is bad.
Do you get a snug fit when you plug it in to a usb cable,or is it loose and wobbly?
Click to expand...
Click to collapse
It's not wobbly at all. But if it's a usb connector failure, why does charging work?
tudorlv said:
It's not wobbly at all. But if it's a usb connector failure, why does charging work?
Click to expand...
Click to collapse
I agree. It's bizzare. If it's charging fine and it's not loose, it doesn't make sense. I assume that HTC sync won't recognize it either? Have you tried relocking the bootloader and go back completely stock? Do you also get the Windows error that the "usb device has failed"?
BCH/HTC said:
I agree. It's bizzare. If it's charging fine and it's not loose, it doesn't make sense. I assume that HTC sync won't recognize it either? Have you tried relocking the bootloader and go back completely stock? Do you also get the Windows error that the "usb device has failed"?
Click to expand...
Click to collapse
No, htc sync does not recognize it, didn't try relocking and get stock. Have you? so I don't go that way without succes. Lastly, no windows error when connecting the phone, not even that annoyng beep sounds.
tudorlv said:
No, htc sync does not recognize it, didn't try relocking and get stock. Have you? so I don't go that way without succes. Lastly, no windows error when connecting the phone, not even that annoyng beep sounds.
Click to expand...
Click to collapse
Crap. I just realized that relocking the bootloader is impossible if it can't be recognized as "usb fastboot" or "adb device".
That sucks man. It really doesn't make sense. Try uninstalling everything HTC related, reinstall drivers, and then reboot your pc.
install drivers again and see if that does anything.
BCH/HTC said:
Crap. I just realized that relocking the bootloader is impossible if it can't be recognized as "usb fastboot" or "adb device".
That sucks man. It really doesn't make sense. Try uninstalling everything HTC related, reinstall drivers, and then reboot your pc.
install drivers again and see if that does anything.
Click to expand...
Click to collapse
I know it sucks. Already tried uninstalling and reinstalling everything related with no succes. I'm thinking this could be solved (or tried) by terminal emulator commands on Rom toolbox, if it's not hardware related. I will backup my sdcard trough airdroid (it will take long) and try to format it
WTF my internet data connection does't work either, wifi and gps works though
EDIT: data works, carrier fault now it's ok
tudorlv said:
WTF my internet data connection does't work either, wifi and gps works though
Click to expand...
Click to collapse
Is there anything you downloaded either to your device or to your PC lately? Does toggling USB Debugging do anything?
Like you said, backup everything, & then completely wipe it all. Like I said, my HTC One V had all the same symptoms, right down to the "Fastboot AC" message. To this day I still can't figure it out, but if I carefully wiggle the usb cable, I can get it to almost get the drivers installed, but it ultimately fails.
I did a little searching on the web & some guy had the same issues & for some reason he was told to update his Windows media player & it worked again. Long shot..I know.
Also..I know you said you tried a few different USB cables, but I would still suggest buying a brand new one and giving it a go. USB cables can be super finicky for some reason. They will charge, but when it comes to data, they won't work sometimes. Just a suggestion.
BCH/HTC said:
Is there anything you downloaded either to your device or to your PC lately? Does toggling USB Debugging do anything?
Like you said, backup everything, & then completely wipe it all. Like I said, my HTC One V had all the same symptoms, right down to the "Fastboot AC" message. To this day I still can't figure it out, but if I carefully wiggle the usb cable, I can get it to almost get the drivers installed, but it ultimately fails.
I did a little searching on the web & some guy had the same issues & for some reason he was told to update his Windows media player & it worked again. Long shot..I know.
Also..I know you said you tried a few different USB cables, but I would still suggest buying a brand new one and giving it a go. USB cables can be super finicky for some reason. They will charge, but when it comes to data, they won't work sometimes. Just a suggestion.
Click to expand...
Click to collapse
Ok, I will try later this day with other cables, hope it works. I will get back here if successful
BCH/HTC said:
Is there anything you downloaded either to your device or to your PC lately? Does toggling USB Debugging do anything?
Like you said, backup everything, & then completely wipe it all. Like I said, my HTC One V had all the same symptoms, right down to the "Fastboot AC" message. To this day I still can't figure it out, but if I carefully wiggle the usb cable, I can get it to almost get the drivers installed, but it ultimately fails.
I did a little searching on the web & some guy had the same issues & for some reason he was told to update his Windows media player & it worked again. Long shot..I know.
Also..I know you said you tried a few different USB cables, but I would still suggest buying a brand new one and giving it a go. USB cables can be super finicky for some reason. They will charge, but when it comes to data, they won't work sometimes. Just a suggestion.
Click to expand...
Click to collapse
So tried right now with a working cable, win7, it does recognize a galaxy3 but not the One
Just realised that if I format the sdcard there is no way of reinstalling or recovering anything
tudorlv said:
So tried right now with a working cable, win7, it does recognize a galaxy3 but not the One
Just realised that if I format the sdcard there is no way of reinstalling or recovering anything
Click to expand...
Click to collapse
Man...this is bizarre. I wish I had some other suggestions for you. The only thing I can think of is that the data partition is now corrupted within the device. How that would happen though, I have no idea.
I found this write-up on the web. Maybe it can help you, but to be honest, I am not positive it'll help. There has to be some other more experienced veterans on this site that can help you out some more.
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
BCH/HTC said:
Man...this is bizarre. I wish I had some other suggestions for you. The only thing I can think of is that the data partition is now corrupted within the device. How that would happen though, I have no idea.
I found this write-up on the web. Maybe it can help you, but to be honest, I am not positive it'll help. There has to be some other more experienced veterans on this site that can help you out some more.
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
Click to expand...
Click to collapse
Well, thank you for trying to help, but it seems nothing that can be done by connecting to a computer (adb fastboot commands) is working.
I am pretty sure that the micro usb port is not damaged because this morning when I booted the One after 3 or so minutes (still connected to my win7 64b laptop) it was detected by windows, even both usb icons appeared in statusbar on phone, and pretty surprised I disconnected and reconnected it but it failed.Tried to move the usb connection in ever way possible without breaking it but nothing. You can't imagine the frustration...
I can't go back to stock as I can't flash the recovery or anything else from computer as I stated before.
As everything else is working perfectly including charging I'm afraid to try possible solutins without being able to revert them easily, so my cry for help is to someone who knows how to use terminal emulator commands and make something out of it.
Thanks again!
tudorlv said:
Well, thank you for trying to help, but it seems nothing that can be done by connecting to a computer (adb fastboot commands) is working.
I am pretty sure that the micro usb port is not damaged because this morning when I booted the One after 3 or so minutes (still connected to my win7 64b laptop) it was detected by windows, even both usb icons appeared in statusbar on phone, and pretty surprised I disconnected and reconnected it but it failed.Tried to move the usb connection in ever way possible without breaking it but nothing. You can't imagine the frustration...
I can't go back to stock as I can't flash the recovery or anything else from computer as I stated before.
As everything else is working perfectly including charging I'm afraid to try possible solutins without being able to revert them easily, so my cry for help is to someone who knows how to use terminal emulator commands and make something out of it.
Thanks again!
Click to expand...
Click to collapse
Sorry to hear that man. I hope everything gets sorted. Good Luck!!:good:
BCH/HTC said:
Sorry to hear that man. I hope everything gets sorted. Good Luck!!:good:
Click to expand...
Click to collapse
Solved, check first post (wipe cache and dalvik cache)
tudorlv said:
Solved, check first post (wipe cache and dalvik cache)
Click to expand...
Click to collapse
Wow!...I can't believe it was that easy. That's awesome though. Glad you got it up and running again.
tudorlv said:
Solved, check first post (wipe cache and dalvik cache)
Click to expand...
Click to collapse
how to wipe dalvik cache without custom recovery
tudorlv said:
So, finnaly solved!
After reading the whole internet (literally) about this problem happening to many HTC (but not only HTC) phones, including not chargind just when turned off, not recognized by computer (including adb, fastboot), going in car mode, I finally found the solution
Here is what I tried
Several custom and stock kernel and recovery flash, different nandroid backups, different roms including stock even clean install (weird, see later why), different cables, drivers, port cleaning.(RUU isn't possible as the phone doesn't get recognized)
The solution however was muck simpler, just wipe cache and dalvik cache and BAM! all working (at my initial arhd rom)
What I suggest (the order doesn't matter) from all the reading done before conclude it's a hardware problem is:
DO A NANDROID BACKUP!
Try different cables and drivers, even computers
Uncheck the fastboot option in power settings and reset
Clean the port with alcohool (or similar), with the phone shut down and then dry it completely
Wipe cache and dalvik cache
Restore the nandroid backup several times, at some people this did the trick
Boot in safe-mode if possible (APM), this way you can check if it's a 3rd party software that can give problems as in safe mode only stock apps are available
Hope I helped
Hello,
Long story short, out of the blue my One doesn't get recognized by any computer, I tried 3 different laptops, all 3 with win7,different cables, latest HTC drivers installed, uninstalled and installed again, but no succes, even my One doesn't get the usb icons show up when I connect it to any laptop, BUT it does charge
Anyway I tried flashing another Rom,factory reset, kernel but nothing changes, adb and fastboot don't recognize my phone
Also the Icon appears when I connect the phone to an MHL adapter but no picture shows up on TV, it worked before
edit: when booted in fastboot it says fastboot AC, not fastboot usb
The get back to HTC solution is a no go as I don,t have any invoice of buying this phone and in EU is required for warranty
I'm currently on ARHD 41.0 kk 4.4 and Elementalx 10.10.1 kernel, S-off, usb debugging on, TWRP 2.6.3.4
What should I try to fix this? Thanks for any suggestions made!
Click to expand...
Click to collapse
HI man , I have a similar problem,the app car mode start automatically, the pc doesn't recognize my htc one and doesn't recharge it, but i have the options of 'fastboot usb' so i've flash other room : cyano and gpe stock, but however it doesn't work. the strange thing is that after connecting the phone to pc i'cant recharge it with the charger but I have to restart it before and so it works. I've wiped cache and dalvik cache but it still not work :crying:
Mr.Ronik said:
HI man , I have a similar problem,the app car mode start automatically, the pc doesn't recognize my htc one and doesn't recharge it, but i have the options of 'fastboot usb' so i've flash other room : cyano and gpe stock, but however it doesn't work. the strange thing is that after connecting the phone to pc i'cant recharge it with the charger but I have to restart it before and so it works. I've wiped cache and dalvik cache but it still not work :crying:
Click to expand...
Click to collapse
I know this is very late but have you get any solution for it?
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.
My fire 5th gen tablet worked for the longest time with gow but I was gonna change the boot screen with a boot animation changer and now I cant get my computer to recognise that its hooked up while it is now stuck in a boot loop although i can still get to fast boot and stock recovery but with the computer not pickup when I hook it up how can I do anything please help asap the last rom that was on it before I flashed to amazon nexus by gow was 5.3.10 fire os.
Crashoverride1993 said:
My fire 5th gen tablet worked for the longest time with gow but I was gonna change the boot screen with a boot animation changer and now I cant get my computer to recognise that its hooked up while it is now stuck in a boot loop although i can still get to fast boot and stock recovery but with the computer not pickup when I hook it up how can I do anything please help asap the last rom that was on it before I flashed to amazon nexus by gow was 5.3.10 fire os.
Click to expand...
Click to collapse
Reboot PC. Try changing the USB cable; amazing how often this is the culprit. Also try a different USB port, preferably USB2. Avoid external hubs which can block tethered communications. If all else fails try a different computer.
Davey126 said:
Reboot PC. Try changing the USB cable; amazing how often this is the culprit. Also try a different USB port, preferably USB2. Avoid external hubs which can block tethered communications. If all else fails try a different computer.
Click to expand...
Click to collapse
is it possible for 3 Diffrent USB cables to be bad all at once one of them is relatively new and if this was not enough I tryed on my desktop and it too is not seeing the tablet If I had been the one that had the funds to by it I would have gotten a much more hackable tablet but this one was a christmas gift.
Crashoverride1993 said:
is it possible for 3 Diffrent USB cables to be bad all at once one of them is relatively new and if this was not enough I tryed on my desktop and it too is not seeing the tablet If I had been the one that had the funds to by it I would have gotten a much more hackable tablet but this one was a christmas gift.
Click to expand...
Click to collapse
Probably not. Possible device has a problem with USB port. Open Windows Device Manager; look for any activity while tethering/untethering while device is in recovery mode (specifically the option that permits reloading FireOS).
Davey126 said:
Probably not. Possible device has a problem with USB port. Open Windows Device Manager; look for any activity while tethering/untethering while device is in recovery mode (specifically the option that permits reloading FireOS).
Click to expand...
Click to collapse
I got it recognising it in fastboot but not adb can I restore it with fastboot somehow
Crashoverride1993 said:
I got it recognising it in fastboot but not adb can I restore it with fastboot somehow
Click to expand...
Click to collapse
Unfortunately, no as fastboot environment is crippled on this device.
Davey126 said:
Unfortunately, no as fastboot environment is crippled on this device.
Click to expand...
Click to collapse
I dont know why it dosent see the device when booted into adb but it dosent but it see's the device booted as fast boot so what could be wrong Also the adb sees it when its constantly rebooting from the boot loop but its only temporary because when it reboots it temporarly disconnects so any thing else I really want to fix this thing but dont know what else to do.
Crashoverride1993 said:
I dont know why it dosent see the device when booted into adb but it dosent but it see's the device booted as fast boot so what could be wrong Also the adb sees it when its constantly rebooting from the boot loop but its only temporary because when it reboots it temporarly disconnects so any thing else I really want to fix this thing but dont know what else to do.
Click to expand...
Click to collapse
Assume you are selecting "apply update from ADB" in recovery *prior* to adb connection attempt. While a long shot also try the two wipe options although I'd be surprised if either changed the situation.
Good chance irreversible damage occurred when you tried to change the bootloader (vs ROM) boot animation. As the bootloader is locked on this device little more can be done beyond the steps previously outlined.
yes I tried the wipe options nothing changed as for adb update I tried while connected and when I tried that app I thought it was gonna change the ROM animation I dont think the bootloader was quite touched as it still says amazon and then shows the custom boot screen then reboots without actually booting the rom but yes the the rom boot screen was my intended change Good news I think however is I belive now that my cable is faulty because When messing with it it seems while in adb mode I get unknown device
Crashoverride1993 said:
yes I tried the wipe options nothing changed as for adb update I tried while connected and when I tried that app I thought it was gonna change the ROM animation I dont think the bootloader was quite touched as it still says amazon and then shows the custom boot screen then reboots without actually booting the rom but yes the the rom boot screen was my intended change Good news I think however is I belive now that my cable is faulty because When messing with it it seems while in adb mode I get unknown device
Click to expand...
Click to collapse
That was the first thing mentioned and is often the primary culprit. Add your experience to countless others who dismiss or underweight potential cable issues. Also look for a loose USB connector (rare) which can exhibit similar symptoms.
Davey126 said:
That was the first thing mentioned and is often the primary culprit. Add your experience to countless others who dismiss or underweight potential cable issues. Also look for a loose USB connector (rare) which can exhibit similar symptoms.
Click to expand...
Click to collapse
Its weird that the cable is the problem cause it seems 3 did nothing and one says unknown device buying another cable though Im not sure when I can do.
Crashoverride1993 said:
Its weird that the cable is the problem cause it seems 3 did nothing and one says unknown device buying another cable though Im not sure when I can do.
Click to expand...
Click to collapse
Just giving an update I bought a brand new actual amazon usb cable and got it running again no sweat even rerooted and blocked ota updates
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.