I've got a rooted but not s=off HTC One XL which I'm trying to do s=off and get back on the latest version of CM. The problem I have is that I can't get fastboot to work anymore. From a command prompt I can do adb devices and get a response back that shows my phone. I issue the adb reboot bootloader and my phone reboots into the bootloader. The problem is it says fastboot ac and fastboot devices shows nothing. There are several odd things which partially leads me to suspect that my phone has something wrong with it. The only device that will show my phone through adb is my wife's ancient laptop, and I get a message about the USB port slowing things down. My work laptop, personal laptop, and PC all refuse to see the phone despite downloading HTC Sync, installing it for the drivers and removing Sync. Only the old laptop gets as far as the adb devices to work.
When I boot into bootloader, Windows Vista gives a message about unknown device and the device manager updates from showing the phone under Android and MyHTC to going under Universal Serial Bus controllers and showing as an unknown device. I try to update the drivers and point at HTC driver and windows lies to me and says that the best driver is already installed.
I'm at a total loss and can't find anything else to try. I have also used two different cables with the same results, one is a generic USB cable and the other is an HTC cable. I can mount the phone as a USB drive and copy/paste files. It is only in the bootloader that the phone becomes unknown.
Try using a linux bootable usb stick or a windows vm. It's more likely that something is interfering with the driver.
Sent from my HTC One X using xda app-developers app
Related
Not sure when USB stopped working but nothing I've done let's my HTC One X (AT&T) connect via usb. I'm running CM10.1 and have tried both MTP and USB Storage and none of my PC's will see my phone.
I'm running TWRP 2.5, which I just updated today. When I boot into recovery and mount USB, my PC shows nothing. I boot the phone into recovery and the fastboot line says fastboot AC instead of fastboot USB. I've tried 3 different cables, an older cable that came with a MyTouch 4G, the HOX cable, and a generic USB cable. All three cables work with my wife's HOX, though hers is stock.
I've also tried on two different laptops (one vista, one win7), my PC (win7), even ran an Ubuntu VM on my PC and nothing.
HTC Sync Manager has been installed and is currently uninstalled though I do see the HTC Driver in Programs so it is there. Some times when I plug the phone in I get an error from Windows about the USB device not installing right. One odd thing is I don't see the device anywhere in device manager, nothing other Other, Android Devices or anything like that.
Developer options are turned on, with Android debugging, USB debugging notify turned on. Root access is set to Apps and ADB.
I've tried other things I've found such as turning the phone off and plugging it into the USB and letting windows detect that way. Pretty much at a loss at this point.
al_g said:
Not sure when USB stopped working but nothing I've done let's my HTC One X (AT&T) connect via usb. I'm running CM10.1 and have tried both MTP and USB Storage and none of my PC's will see my phone.
I'm running TWRP 2.5, which I just updated today. When I boot into recovery and mount USB, my PC shows nothing. I boot the phone into recovery and the fastboot line says fastboot AC instead of fastboot USB. I've tried 3 different cables, an older cable that came with a MyTouch 4G, the HOX cable, and a generic USB cable. All three cables work with my wife's HOX, though hers is stock.
I've also tried on two different laptops (one vista, one win7), my PC (win7), even ran an Ubuntu VM on my PC and nothing.
HTC Sync Manager has been installed and is currently uninstalled though I do see the HTC Driver in Programs so it is there. Some times when I plug the phone in I get an error from Windows about the USB device not installing right. One odd thing is I don't see the device anywhere in device manager, nothing other Other, Android Devices or anything like that.
Developer options are turned on, with Android debugging, USB debugging notify turned on. Root access is set to Apps and ADB.
I've tried other things I've found such as turning the phone off and plugging it into the USB and letting windows detect that way. Pretty much at a loss at this point.
Click to expand...
Click to collapse
Helping a gentleman with the same issue in another thread, it sounds to me like a hardware issue.
Hi! I'm having some issues trying to unlock my bootloader so I can root my new one mini.
I've been trying to follow the instructions here: http://www.htcdev.com/bootloader/unlock-instructions/
But when I get to step five, fastboot won't detect the phone. adb can't see the phone either. My computer cannot recognize the device
I have sync killed on my computer, I've tried both USB 2.0 and 3.0 ports, and I know my USB driver is up to date.
Something with my computer's OS or drivers is not working, and I can't figure out how to progress. Can anyone help?
HTC USB drivers don't work on Windows 8/8.1.
Sent from my HTC One mini using Tapatalk
HTC One S4
Alright, I've looked into this for quite a bit. There's 3 things I've found:
- Change charging cable (done)
- Install HTC Sync (done)
- The USB connector port on the phone could be broken (hope not)
Anything else I can look into?
- Rom is ViperOneS JB
I believe I've tried ADB devices, I haven't really done any sort of ROM changing so I've forgotten much of this, but I believe ADB devices doesn't show any available devices.
EDIT: Another thing to add is that the PC recognises the phone when in CWM but doesn't mount the device such that I can access the files.
EDIT 2: I tried Fastboot USB, only comes up as Fastboot AC :/
Another thing: I charge my phone using a dodgy eBay USB cable, I didn't use this for connecting to the PC but whenever I plug in the charger the phone says to unlock in order to access files on the PC (as it would if my PC detected the phone).
Sorry to sound desperate but I need a response, fast!
Uninstal htc sync.
Instal latest HTC drivers & adb.
PS
Windows 8.1 have a problem with driver.
It says the device connected to the PC has "malfunctioned". I deleted HTC Sync, haven't updated ADB cos I can't remember the link.
Installed latest adb, no avail.
http://forum.xda-developers.com/showthread.php?t=2217396
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
I already have those.
Anyone at all know anything?
Bump :/
It does say unlock to access phone storage on computer and then when I do, nothing happens.
I have the same issue, and I've tried to access my One S from multiple computers (different usb ports, 2.0, hub, et.c., Windows, OSX, Linux) and nothing seems to do the trick. I'm completely locked out from switch recovery (TWRP installed but can't be accessed, possibly due to old 1.13 hboot).
Sorry not to be able to offer any help, just that I doubt it'll be fixed in your case by switching computers/os/ports et.c. since I've tried most of that already, and I must've been through 10-12 different usb cables by now.
Just about ready to ditch this phone.
Flash the original recovery.
So I was given another HTC sensation recently but this time it's bricked and I don't know how to fix it.
I have a working HTC sensation phone to test that the driver work on win 8.1
The problem
When turning on the phone it goes to a black screen with HTC logo in the middle and 4 small triangles with exclamation point in each corner, from here I have to take out the battery to turn off the phone.
Holding Power+volume down brings up this screen as well so I can't get into bootloader/hboot using pwr+volume down, same thing with plugging in phone to usb
What I've been told
phone is s-off (I assume this means it has a some sort of custom recovery)
bricked when pulling out cable during RUU while trying to return to stock
What I've done/know
windows 8.1
plugged to USB 2.0 port
USB device not recognised when plugging in phone, in device manager in Android HTC device properties
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
disabled driver signing security
install Android Universal Naked Driver in Win8 test mode
install Minimal ADB and fastboot utility
adb devices doesn't list any device
other adb command give "error: device not found"
fastboot command produces "waiting for device"
same with fastboot getvar cid
Thank you for any assistance you can give
stillsober said:
So I was given another HTC sensation recently but this time it's bricked and I don't know how to fix it.
I have a working HTC sensation phone to test that the driver work on win 8.1
The problem
When turning on the phone it goes to a black screen with HTC logo in the middle and 4 small triangles with exclamation point in each corner, from here I have to take out the battery to turn off the phone.
Holding Power+volume down brings up this screen as well so I can't get into bootloader/hboot using pwr+volume down, same thing with plugging in phone to usb
What I've been told
phone is s-off (I assume this means it has a some sort of custom recovery)
bricked when pulling out cable during RUU while trying to return to stock
What I've done/know
windows 8.1
plugged to USB 2.0 port
USB device not recognised when plugging in phone, in device manager in Android HTC device properties
disabled driver signing security
install Android Universal Naked Driver in Win8 test mode
install Minimal ADB and fastboot utility
adb devices doesn't list any device
other adb command give "error: device not found"
fastboot command produces "waiting for device"
same with fastboot getvar cid
Thank you for any assistance you can give
Click to expand...
Click to collapse
you have to make the device being recognized from win 8.1
there a lot of guides here in xda on how to set up adb/fastboot on windows 8
then use again the ruu
I have 2 HTC sensations, one working one bricked.
the working one is recognised on the pc, fastboot etc working
the bricked one isn't
USB device not recognised when plugging in phone, in device manager in Android HTC device properties
Quote:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
I'm hoping someone can help me out here. I've rooted phones before and didn't have any trouble previously. I just bought a used Pixel 3 on eBay with the plan to root using Magisk. The only problem is I can't get the device to be recognized at all on my PC. I've tried all the usual things like different USB ports, different cables, cleaning out the port, etc. I have the latest drivers installed and I have a Pixel XL that is recognized by my PC immediately so I know I have the correct drivers installed. Pixel 3 does not show up in Device Manager at all. I have USB debugging enabled on the device, but it never prompts me to Allow USB debugging when I connect the Pixel 3 to my PC.
Now, here's the weird part. I know the cable is working fine because I use the same cable and plug it into my Mac. The Pixel 3 is recognized immediately and I'm prompted to enable USB debugging. ADB then works just fine on my Mac. 'adb devices' shows my phone. But I then try to use 'adb reboot bootloader' and my phone reboots to the bootloader as it should. At this point my phone says it's in FastBoot Mode, but the device isn't recognized using 'sudo fastboot devices' and if I try 'sudo fastboot flashing unlock' it just sits there saying 'waiting for any device'. I've also tried putting it into FastBoot mode manually by using the Power and Volume Down key, but run into the same issue with it not being recognized while in FastBoot mode.
Could the previous owner have done something to the bootloader to cause the device to not be recognized in FastBoot mode? And is there any way to fix it? Why would the phone be recognized on my Mac without issue, but using the same cable and multiple different ports on my PC, it never gets recognized?
Any help would be very much appreciated here as I'm at a loss as to what I can do and fear I just spent money on an expensive paperweight.
I tested the cable I'm using with my Pixel XL and it's immediately recognized by my PC and the notification for USB debugging shows on the phone, so I know the cable is working out. No device ever shows in the device manager when I have my Pixel 3 connected though. I've even uninstalled the drivers while my Pixel XL is connected to hopefully put Windows into a driverless state hoping my Pixel 3 would then show up as an unrecognized device, but no device. I can't get it to show up at all in Windows for some reason and it's not recognized while in fastboot mode on my Mac. Fastboot mode information all seems to match what a Pixel 3 should look like as well, so I don't think the previous owner installed the wrong software causing device id mismatch. Anyone have any other suggestions for what I can try?