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
Related
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
Good morning
I tried updating the rom on my htc sensation and to do so i usualy have to flash the boot.img aswell to get rid of the infinite startup screen
but my device doesnt work anymore when im in the bootloader in fastboot mode on windows i get a message usb device malfunctioned
i know the usb works as when im booted up in my (previous rom) i can still send data from my pc to my phone over the usb cable
any ideas?
regards
frayful said:
Good morning
I tried updating the rom on my htc sensation and to do so i usualy have to flash the boot.img aswell to get rid of the infinite startup screen
but my device doesnt work anymore when im in the bootloader in fastboot mode on windows i get a message usb device malfunctioned
i know the usb works as when im booted up in my (previous rom) i can still send data from my pc to my phone over the usb cable
any ideas?
regards
Click to expand...
Click to collapse
Might be a driver issue. Can you try a different USB port?
Sent from my HTC Desire S using Tapatalk
Heya i tried different usb ports tried different cables and tried it on 2 other laptops aswell all gave the error usb device not recognized, device malfunctioned after like 10 seconds after being connected
regards
Which Windows do you have?
tested on 3 windows 8.1 pc's
frayful said:
tested on 3 windows 8.1 pc's
Click to expand...
Click to collapse
maybe you are facing now connectivity issues with w8
write in the search box "how to set up adb/fastboot in windows 8"
check some threads and see if you have any success
Hi,
I am trying to update the custom recovery on my HTC Desire S. However, my PC does not detect the phone when in hboot or fastboot mode (but it does when in recovery and when OS is loaded).
When I connect the phone to USB in hboot/fastboot mode, it shows "hboot usb plug" or "fastboot usb" for maybe 10 seconds, but then stops shoinw "USB", and windows shows message "USB device not recognized".
Any suggestions what I should do?
The PC is running Windows 10 Pro, the HTC drivers were installed with HTC Sync 3.3.63 and I installed Android SDK today.
I hope someone can help.
Hi
I was trying to unlock my htc one e8 dual sim bootloader but i cannot get the device to be indentified as adb device. Here's what i did
1) Installed Android SDK platform tools and google usb driver and downloaded the fastboot binaries from htc dev
2)Installed htc sync manager for the drivers
3)Enabled USB debugging on phone
4)When the phone is turned on, it is shown in the adb devices list BUT as soon as i boot it in fastboot, it is not listed. I have tried installing the google usb driver , connecting it in Charging and Media Transfer mode but to no avail.
My laptop has only usb 3.0 ports
Kindly Help Me
Regards
Well... if you have the proper drivers installed, when you turn on the phone with the Vol - and PWR combination, you boot first on HBOOT, you must select Fastboot and then let the drivers get installed, thats the only way
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?