Related
Few days ago I charged my HTC One X wid micromax charger... The phone was charging as it does with HTC charger...
But I have a problem now dat the phone gets charged, but when i connect it to my computer it does not show any connection and just gets charged...
My phone is in warranty, but as i hav rooted it, warranty will be void I guess...
As it does not connect to computer i cannot unroot it...
Any solution for this problem ???
How can I unroot HTC One X without computer connection ??
Thanx in Advance...!!!
have you tried a different cable, and a different computer?
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
when connected try adb devices, see if it shows connected.
i think you'll need to make sure settings>developer options>usb debugging is enabled.
maxwordlife100 said:
Few days ago I charged my HTC One X wid micromax charger... The phone was charging as it does with HTC charger...
But I have a problem now dat the phone gets charged, but when i connect it to my computer it does not show any connection and just gets charged...
My phone is in warranty, but as i hav rooted it, warranty will be void I guess...
As it does not connect to computer i cannot unroot it...
Any solution for this problem ???
How can I unroot HTC One X without computer connection ??
Thanx in Advance...!!!
Click to expand...
Click to collapse
Try settings > connect to pc, check nothing's changed
Sent from my HTC One X using Tapatalk 2
lawrence750 said:
have you tried a different cable, and a different computer?
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
when connected try adb devices, see if it shows connected.
i think you'll need to make sure settings>developer options>usb debugging is enabled.
Click to expand...
Click to collapse
Tried a dozen of cables, but still it has the same problem... I have tried adb devices, but it does not show any device connected... Usb debugging is enabled, HTC drivers are also there...:crying::crying::crying::crying:
Can I unroot without USB cable so I can at least give it to the Service Station ????
seanicca said:
Try settings > connect to pc, check nothing's changed
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I hav seen dat, Tried hard drive and all other options, but there is no connection...
Can I unroot without USB cable so I can at least give it to the Service Station ????
Seniors Plz Help...!!!!
maxwordlife100 said:
Tried a dozen of cables, but still it has the same problem... I have tried adb devices, but it does not show any device connected... Usb debugging is enabled, HTC drivers are also there...:crying::crying::crying::crying:
Can I unroot without USB cable so I can at least give it to the Service Station ????
Click to expand...
Click to collapse
i'm not sure that you can do it without fastboot.
did you also try another computer?
lawrence750 said:
i'm not sure that you can do it without fastboot.
did you also try another computer?
Click to expand...
Click to collapse
Yes I hav tried to many computers still its showing only charging...
So any other solution for my problem ???
Thanx in advance...!!
Got the same problem here, but only used the official charger. Still it can charge but isnt able to communicate with a pc in any state, adb, fastboot, htc sync, disk drive etc.
Sent from my HTC One X using Tapatalk 2
ejic said:
Got the same problem here, but only used the official charger. Still it can charge but isnt able to communicate with a pc in any state, adb, fastboot, htc sync, disk drive etc.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Plz PM me if you find any solution...!!
See this: http://androidforums.com/htc-one-x-xl/541171-htc-one-x-unable-connect-computer-storage.html
A solution that worked was to press the power button for 10 seconds (whether or not connected to a PC) then try again.
thanks but that is not working. even in hboot when i connect the usb cable, the phones states "fastboot usb" but still isn't discovered by any pc using "fastboot devices" command. Tried 4 different computers with windows and 2 with linux (ubuntu and fedora). so i guess its a hardware problem with the socket or the motherboard.
Gammarax said:
See this: http://androidforums.com/htc-one-x-xl/541171-htc-one-x-unable-connect-computer-storage.html
A solution that worked was to press the power button for 10 seconds (whether or not connected to a PC) then try again.
Click to expand...
Click to collapse
Thanx for your reply, but i hav tried dat be4... Dint worked...!!!
Hi, I recently rooted and flashed cm11 to my DHD
It is S-OFF and rooted, 4ext recovery installed.
Problem is that now the phone is not recognised by my computer (or any computer, not a driver issue) I use linux and there is no output whatsoever from dmesg when phone is plugged/unplugged to usb.
Reading through other posts (but not relevant to DHD) it seems to be a prob with the misc partition (mtd0 on the desire, not sure on the DHD)
So I have no fastboot usb or adb over usb access, but can SSH into phone and use root shell on it, any suggestions?
Also, SD card not working - assume this is related to the USB problem since started happening at same time.
correction, sd works, so just usb needs sorting, tried reflashing /misc but no joy
jmprince80 said:
Hi, I recently rooted and flashed cm11 to my DHD
It is S-OFF and rooted, 4ext recovery installed.
Problem is that now the phone is not recognised by my computer (or any computer, not a driver issue) I use linux and there is no output whatsoever from dmesg when phone is plugged/unplugged to usb.
Reading through other posts (but not relevant to DHD) it seems to be a prob with the misc partition (mtd0 on the desire, not sure on the DHD)
So I have no fastboot usb or adb over usb access, but can SSH into phone and use root shell on it, any suggestions?
Also, SD card not working - assume this is related to the USB problem since started happening at same time.
Click to expand...
Click to collapse
No...when flashing to cm 11+ you need to update your SDK. Update the files(all the android versions). To access fastboot u have to open platform folder..then anywhere in that folder hold shift and right click..chose command here
---------- Post added at 03:20 AM ---------- Previous post was at 03:19 AM ----------
P.s.
Edit: its either platforms or platform tools folder. Sorry about that.
---------- Post added at 03:23 AM ---------- Previous post was at 03:20 AM ----------
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
it is not a problem with the computer, since the phone is not even shown on list of USB devices. even with no SDK or any other tools installed on a computer there should still be a USB vendor and product code when plugged in. the phone itself also does not recognise that it is plugged into anything but a power source. problem is phone side hence content of original post.
jmprince80 said:
it is not a problem with the computer, since the phone is not even shown on list of USB devices. even with no SDK or any other tools installed on a computer there should still be a USB vendor and product code when plugged in. the phone itself also does not recognise that it is plugged into anything but a power source. problem is phone side hence content of original post.
Click to expand...
Click to collapse
No! With the android versions 4.4 and up, you need to install the SDK updated files for that android versions. Believe me,I know
---------- Post added at 11:35 AM ---------- Previous post was at 11:34 AM ----------
If one cannot find the specific drivers for a device, they can use the SDK toolkit
Im happy to try installing the latest SDK.
However Im pretty sure that its not going to change anything.
Simple fact is that is a USB device is plugged in, whether or not there are drivers present, it will still show up with a LSUSB or as an unknown device in windows device manager.
I think the problem lies somewhere in one of the configuration partitions - I am able to flash different ROMS by adb pushing to /sdcard but none i have tried have yet solved the USB issue. If I flash back to stock I will lose recovery and be unable to fix problem at all.
Dude. Yes it will
in RUU are *ALL* partitions replaced back to stock? Don't fancy being stuck back on GB....
Its not a matter of "staying"on gingerbread. Its a matter of getting your device back on track. Running that ruu after locking your bootloader will sort things out. You can always unlock it again and flash a fresh custom ROM.
---------- Post added at 02:16 AM ---------- Previous post was at 02:13 AM ----------
If u are s off, then all that will be wiped pertaining to wiping is your bootloader. There u can use SDK to access your device. U don't exactly need the "USB" thing sorted. All u need is to have SDK updated with all android versions and getting access to your bootloader via platform tools in SDK. Ppl are sadly misguided by this USB situation.
I just installed AOCP 6 on my HTC Desire HD but whenever I want to connect my phone to PC with my usb cable, it only recognizes it as charger and it doesn't show me any option to connect it to the PC. Is there any fix for this?
Shawiee said:
I just installed AOCP 6 on my HTC Desire HD but whenever I want to connect my phone to PC with my usb cable, it only recognizes it as charger and it doesn't show me any option to connect it to the PC. Is there any fix for this?
Click to expand...
Click to collapse
Close this, the fault was at my pc I made a system restore for four days and now it is working.
Shawiee said:
I just installed AOCP 6 on my HTC Desire HD but whenever I want to connect my phone to PC with my usb cable, it only recognizes it as charger and it doesn't show me any option to connect it to the PC. Is there any fix for this?
Click to expand...
Click to collapse
Where is this aocp 6? Got a link? Never heard of such rom
Duh..nvm. Lol
Ahh..nostalgia...I flashed this again for old times sake..back then this ROM fc and random reboot a lot. But CED fixed it. Thanks again CED..we miss u here in our device forum..plan in making a comeback?
---------- Post added at 12:48 PM ---------- Previous post was at 12:48 PM ----------
@cedarctic
I enable ADB on developers options and was able to enter fast boot, the first time. But don't do anything.
But now the Watch is not recognized, I already try in 3 different PC's and received the message.
When I connect a box appear that indicate:
USB Device Not Recognized, the last USB device you connect to this computer malfunctioned and Windows does not recognized it.
Recommendation: Try Reconnecting the device. If Windows still does not recognize it, your device may not be working properly.
My Wife Watch are recognized in all 3 PC's and able to unlock bootloader, install TWRP and Kernel.
Also when I go to Device Manager a line (under Universal Serial Bus Controllers) are added tha indicate :
Unknown USB Device (Device Descriptor Request Failed)
I already reset the watch 3 times, wipe cache, but still same error message.
Under Developer Options, I revoke debugging authorizations.
What other options I had.
Thanks.
Getting this too, did you find a solution?
Hello ....
I have the same problem after the last update ..
I also got the same error. Hope somebody finds a fix
I have same problem :/
What do you think it has reason? HW or SW brick?
---------- Post added at 11:01 PM ---------- Previous post was at 10:59 PM ----------
but my watch still in android bootloop, recovery workinng but factory reset not helping.
I fixed it. For me the error occurred because I used a 3rd party charger. (Which came with my watch because I bought it second hand)
So I got the original huawei charger from Amazon and now everything is working fine.
ViktorFoedowski said:
I fixed it. For me the error occurred because I used a 3rd party charger. (Which came with my watch because I bought it second hand)
So I got the original huawei charger from Amazon and now everything is working fine.
Click to expand...
Click to collapse
Could you send me a link to the charger you bought please? Thanks!
Not sure exactly when this started, but went to try to sideload the P update and can't get any PC to recognize my phone. Tried different computers and different cables. Won't even pop up on the phone to transfer files. So not an adb/fastboot problem. Last time I remember plugging into a PC and working was when I ran an adb command to enable the Hide Nav Bar app. Possible my USB port crapped out? Charges and fast charges just fine.
Any insight is welcome.
edit: Phone reads flash drive connected through USB-C adapter
1. Make sure USB Debugging is enabled
2. Try all USB ports available on computer
3. Try all USB cables available (OEM cable is always the best choice)
3. Revoke USB permissions
4. Uninstall & reinstall adb drivers, then reboot computer
If you have access to another Android device, plug it in and see if the computer recognizes that one. If it does, then the problem is your device, not the adb environment.
My phone with thru that. I had to unroot, re-lock bootloader, and i sent the device back to google. Since it was still under warranty and the issue was that the hardware wasnt allowing the device to be read via andriod auto or any computer. Not even my headphone dongle worked.
TheKevinMaestre said:
My phone with thru that. I had to unroot, re-lock bootloader, and i sent the device back to google. Since it was still under warranty and the issue was that the hardware wasnt allowing the device to be read via andriod auto or any computer. Not even my headphone dongle worked.
Click to expand...
Click to collapse
Can you do this through terminal app?
i have the same problem but even my fastboot mode isn't reconized. i can't even boot the phone. Tried unistalling and reinstalling adb fastboot phone drivers but it didn't work. I even tried 4 different cable, usb c to c, usb c to a... nothing working)!!!! I don't know what to do... and it's the first time in 10 years of modding. My devices show the red triangle.... will google refurb it if they find out that's modded?
Balino said:
i have the same problem but even my fastboot mode isn't reconized. i can't even boot the phone. Tried unistalling and reinstalling adb fastboot phone drivers but it didn't work. I even tried 4 different cable, usb c to c, usb c to a... nothing working)!!!! I don't know what to do... and it's the first time in 10 years of modding. My devices show the red triangle.... will google refurb it if they find out that's modded?
Click to expand...
Click to collapse
if you are at the red triangle, you aren't in recovery, yet.
You'll need to hold the power button and tap the up volume key to get to recovery.
When my USB port recently crapped out, one of the symptoms was the inability to connect to a computer. Still not sure if it was hardware or something deep in the filesystem. A factory reset from recovery didn't fix it, but an RMA replacement under warranty from Google did.
Sent from my Pixel 2 XL using Tapatalk
Happened to my device too 3 weeks ago... the phone would sometimes charge, sometimes wouldn't at all, and wasn't detected anymore by my computers. Android Auto dead. USB-C -> minijack dead.
Had to RMA it, it was a problem with the USB controller or something
I had this issue as well I was able to fix by turning on and off USB debugging, still RMA'd it as I don't fully trust the port anymore. Not sure what happened, it was working fine on the way to work, on the way home I plugged in the USB for Android auto and got nothing.
This just happened to me too...think they are going to RMA but the phone is unlocked and I am not able to relock it anyway without connecting...
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
rajendra82 said:
When my USB port recently crapped out, one of the symptoms was the inability to connect to a computer. Still not sure if it was hardware or something deep in the filesystem. A factory reset from recovery didn't fix it, but an RMA replacement under warranty from Google did.
Click to expand...
Click to collapse
Was yours unlocked. I can't relock my phone cuz I can't connect to anything...I'm supposed to send in to Google but worried they won't honor warranty now...
My phone bootloader was not unlocked. I don't believe Google denies warranty coverage for unlocked phones, if the failure is not caused by it. They certainly never asked me any questions about it.
Sent from my Pixel 2 XL using Tapatalk