Related
Hey guys, flashed Sinless 5.1.1 last night and ever since installing this particular ROM I'm unable to access my phone's folders via MTP or anything. I've tried re-installing drivers on my PC, rebooting phone and PC several times, trying to access my phone in ADB and fastboot... I can't even push or sideload a new ROM so I really don't know what to do!
Anyone got any idea what to try next and/or how to solve this?
Did you enable Developers options USB debugging?
If not go to about phone and click on Build number a
bunch of times. If that doesn't work install latest HTC
drivers.
Armeniandave said:
Did you enable Developers options USB debugging?
If not go to about phone and click on Build number a
bunch of times. If that doesn't work install latest HTC
drivers.
Click to expand...
Click to collapse
Tried both, to no avail.
EDIT: It was working fine yesterday on Insertcoin 4.3 ROM, so I'm copying that back to my phone via WIFI transfer, gonna flash that and see if I get USB access back.
rpalmer92 said:
Tried both, to no avail.
Click to expand...
Click to collapse
I'm actually running that exact ROM and my phone is seen on both my Mac and Windows 7.
Did you try a different USB port? Does a message pop up on your phone asking to trust your
computer? My computer wouldn't see my phone until I accepted that pop up.
If you've tried all that then give a little more info on your PC so we can diagnose it.
Armeniandave said:
I'm actually running that exact ROM and my phone is seen on both my Mac and Windows 7.
Did you try a different USB port? Does a message pop up on your phone asking to trust your
computer? My computer wouldn't see my phone until I accepted that pop up.
If you've tried all that then give a little more info on your PC so we can diagnose it.
Click to expand...
Click to collapse
I never saw any message pop up. I've tried 4 different USB 2.0 ports. My USB 3.0 ports aren't usable.
I am runnings Windows 7 x64 Ultimate with latest HTC drivers installed.
rpalmer92 said:
I never saw any message pop up. I've tried 4 different USB 2.0 ports. My USB 3.0 ports aren't usable.
I am runnings Windows 7 x64 Ultimate with latest HTC drivers installed.
Click to expand...
Click to collapse
Kinda stumped then! Only thing I can think is that you don't have the very latest drivers.
Can you ADB and see the phone? Check the following thread on how to do this.
(Sorry if you already know how)
http://forum.xda-developers.com/showthread.php?t=2365506
If I do "adb devices", nothing shows up. Simple commands like "adb reboot" respond with "error: device not found".
I've just flashed ARHD 31.6 (Android 4.3) and re-installed drivers and my phone still isn't recognisable. I'm lost!
Okay, big trouble now!! I just read elsewhere that it could be an internal storage corruption problem, so without thinking I formatted internal storage along with data and system in recovery and attempted to ADB sideload a new ROM and was going to start over. Stupid idea! ADB still isn't working so now I can't even sideload or push a ROM. All I have to work with now is fastboot and recovery, and my PC isn't recognizing either of them. Any ideas?
YOU AREN'T GOING TO BELIEVE THIS!!!
Girlfriend stayed over the weekend and happened to swap our USB cables over. She left and took my OTG cable and left me with her identical looking USB charge only cable.
Just tried my mother's Nokia cable and voila! Installing device drivers.
Now to sideload a ROM and start from scratch -.-
I know this thread is old but if someone stumbles upon it this is what I did.
New USB worked.
***While using the USB cord that wouldn't connect like it usually does, I re-installed HTC Sync Manager and it immediately recognized it.
www.htc.com/hsm
Hi!
My One "connects" to my PC when it's booting (that sound), but after that it stays disconnected. While booting it's being recognized as an MTP device. Recovery has the same problem: Until recovery starts it's kinda connected, but when TWRP is started, even sideload doesn't work. And in the booloader the "device enumeration failed". The ROM is ARHD GE 6.1
Does some1 know solutions to those probs?
Pwnie2012 said:
Hi!
My One "connects" to my PC when it's booting (that sound), but after that it stays disconnected. While booting it's being recognized as an MTP device. Recovery has the same problem: Until recovery starts it's kinda connected, but when TWRP is started, even sideload doesn't work. And in the booloader the "device enumeration failed". The ROM is ARHD GE 6.1
Does some1 know solutions to those probs?
Click to expand...
Click to collapse
You definitely have a driver problem. Install the drivers from this thread, that should solve your problems.
Make sure to uninstall all currently installed drivers for your HTC One. For this go to the device manager on your pc. (windows + x, -> device manager)
$tefanDroid said:
You definitely have a driver problem. Install the drivers from this thread, that should solve your problems.
Make sure to uninstall all currently installed drivers for your HTC One. For this go to the device manager on your pc. (windows + x, -> device manager)
Click to expand...
Click to collapse
any idea how i could list the drivers which i can uninstall?
Pwnie2012 said:
any idea how i could list the drivers which i can uninstall?
Click to expand...
Click to collapse
http://msdn.microsoft.com/en-us/library/windows/hardware/ff553572(v=vs.85).aspx
$tefanDroid said:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff553572(v=vs.85).aspx
Click to expand...
Click to collapse
uninstalled them, now it always get's recognized as an unknown device (searching drivers), but before it finds a driver it again disconnects
Pwnie2012 said:
uninstalled them, now it always get's recognized as an unknown device (searching drivers), but before it finds a driver it again disconnects
Click to expand...
Click to collapse
Hmm try this one http://forum.xda-developers.com/showthread.php?t=2588979
$tefanDroid said:
Hmm try this one http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
in fastboot i have a "failed device enumeration", the windows-update from the driver thread doesnt work, it says it isnt applicable for my OS
(8.1pro)
EDIT: was able to install the update now, after uninstalling another one. testing fastboot asap (after a reboot).
EDIT 2: Ok, doesnt work.
i now tested, if OTG works on it. doesnt even recognize that there was a usb cable inserted
So on my One, it is bootlooped so when i go onto TWRP and plug in my USB (connected to my computer) nothing happens, i have tried multiple USB's which work with other devices. Any ideas ?
Thanks
mrsimpson321 said:
So on my One, it is bootlooped so when i go onto TWRP and plug in my USB (connected to my computer) nothing happens, i have tried multiple USB's which work with other devices. Any ideas ?
Thanks
Click to expand...
Click to collapse
what does device manager show?
check if this is the problem, FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
no
nkk71 said:
what does device manager show?
check if this is the problem, FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
nothing comes up at all whether its plugged in or not and device manager show nothing, any other ideas ?
mrsimpson321 said:
nothing comes up at all whether its plugged in or not and device manager show nothing, any other ideas ?
Click to expand...
Click to collapse
clean phone's usb port (gently), try a different cable
nkk71 said:
clean phone's usb port (gently), try a different cable
Click to expand...
Click to collapse
i have tried lots of cables which work with other androids and how do i clean the usb port ?
thanks
mrsimpson321 said:
i have tried lots of cables which work with other androids and how do i clean the usb port ?
thanks
Click to expand...
Click to collapse
don't know never had that problem.
compressed air-can i guess would work
having exactly same issue, tryed everything, from universal drivers to cleaning the port, changing pc´s , changing cables, it will only charge, no fastboot or adb can detect it, device manager displays nothing eighter...
Same for me :S
I am having issues with my Nexus 6. I am unable to get it to connect to any computer. Windows says the device is malfunctioning, but it charges okay. Windows gives the error "Device descriptor request has failed." It doesn't matter if I'm booted, in fastboot, or have the phone off, it gives that error.
What I have tried:
Toggled USB debugging, MTP, and PTP.
Nexus Root Toolkit to try to install the drivers
15 Second ADB Installer by Snoop05
Alternate drivers (Naked, Generic, PDA).
Each time I have tried new drivers, I have checked to uninstall anything using USBDeview.
Tried "Updating drivers"
Tried three different Windows machines.
Tried different USB cables
USB 2.0 and USB 3.0 ports
Cleared cache partition
I think I am down to two things: Factory reset or draining my battery all the way and letting the hardware reset itself. I am not confident that factory resetting it will work since this same message pops up in the bootloader.
I have researched the hell out of this and one person in this section was having similar issues but got it working when plugging it into their USB 3.0 port. If those last two things do not work, then I don't know how the hell I'm going to lock the bootloader to get it worked on--that's the only thing I have done to it as far as modification wise (/system is stock, no root).
Any help is greatly appreciated. This is so frustrating since using USB is our way of working on these damn things. If I could get root without having to use USB, then I could easily lock the bootloader back.
Does anyone know how to re-lock the bootloader without root or using USB? At least I could have it locked so I can RMA it.
In your device manager see if you see the device with a yellow exclamation mark. If so right click it properties select update driver and then choose the driver option and it will give you a list of things to select.
bluh5d said:
In your device manager see if you see the device with a yellow exclamation mark. If so right click it properties select update driver and then choose the driver option and it will give you a list of things to select.
Click to expand...
Click to collapse
Doesn't work, I'm afraid. Windows says it already has the best drivers for the device. The device simply is not telling Windows what it is. Thanks for your reply.
dijit4l said:
Doesn't work, I'm afraid. Windows says it already has the best drivers for the device. The device simply is not telling Windows what it is. Thanks for your reply.
Click to expand...
Click to collapse
I've come to understand that USB problems are generally Windows' fault (i.e. Windows itself or poorly written drivers) rather than the device's fault. Not always, but the vast majority of the time.
See if anything in this article helps - installing the Google USB driver worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
HTH...
right click the file then go to update driver than select browse my computer then at bottom select let me pick.
Tiptonian said:
I've come to understand that USB problems are generally Windows' fault (i.e. Windows itself or poorly written drivers) rather than the device's fault. Not always, but the vast majority of the time.
See if anything in this article helps - installing the Google USB driver worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
HTH...
Click to expand...
Click to collapse
Thanks for your reply. However, I have a hard time thinking that three Windows machines are experiencing the same thing. I have successfully gotten it connected before the 5.0.1 update to transfer ringtones. I even booted into Linux Mint and couldn't get it to connect either. It's like the controller is bad but it can still charge.
Also, I have followed every direction on your link at least twice already.
bluh5d said:
right click the file then go to update driver than select browse my computer then at bottom select let me pick.
Click to expand...
Click to collapse
Thanks for your suggestion. I have tried this and Windows refuses to use the proper drivers. It argues they aren't for 64-bit OS, but they have worked in the past. I almost got it to use some Samsung drivers, but after it installed, no change. The device is not reporting the details it needs to convey to the computer to start a proper driver setup.
I have not been able to connect either. Tried 2 different Nexus 6 devices, numerous reboots, different cables, different USB ports and all the stuff you tried also to know avail. I updated drivers, went through device manager, but I can connect when I switch from MTP to pictures, however you don't get the same access.
HotInEER said:
I have not been able to connect either. Tried 2 different Nexus 6 devices, numerous reboots, different cables, different USB ports and all the stuff you tried also to know avail. I updated drivers, went through device manager, but I can connect when I switch from MTP to pictures, however you don't get the same access.
Click to expand...
Click to collapse
To me, it sounds like you have a glimmer of hope. Have you tried a different computer? If you don't have a different computer handy, boot Linux from a flash drive and install fastboot and adb.
Hi guys,
I need to unroot my RP2 to send it in for repair, but I can't for the life of me get my fastboot drivers working in Windows 10 2004. I've tried various versions of the stock Google USB drivers (bootloader, of course), but the phone still shows up as "Android" in "Other devices".
Thanks in advance for any suggestions, fellas.
-edison
Try Samsung USB Drivers. Sometimes theirs work when Google's doesn't.
FQuimson23 said:
Try Samsung USB Drivers. Sometimes theirs work when Google's doesn't.
Click to expand...
Click to collapse
I downloaded their driver pack, but couldn't find any Android-specific ones. Any idea which one would work?
edison said:
I downloaded their driver pack, but couldn't find any Android-specific ones. Any idea which one would work?
Click to expand...
Click to collapse
https://developer.samsung.com/mobile/android-usb-driver.html
The issue is with the newest version of windows. I haven't tried the Samsung drivers. What worked for me was making a live usb install of FWUL. Then I could boot from the USB and everything worked.
I have Windows 10 Ver 20H2 installed and can confirm I have gotten ADB and Fastboot drivers WORKING, following the original installation instructions from Razer. It's not very clear, but be SURE to EXTRACT the files AFTER downloading from Razer. Follow the instructions CAREFULLY. I can't tell you how many times I've had to go back and re-read the directions to get it right. I went so far as to reinstall Windows 10 v.1909 on an external drive and issued commands that way, as a work around. Today, I decided to take a chance, and got everything working again.
MoPhoMike said:
I have Windows 10 Ver 20H2 installed and can confirm I have gotten ADB and Fastboot drivers WORKING, following the original installation instructions from Razer. It's not very clear, but be SURE to EXTRACT the files AFTER downloading from Razer. Follow the instructions CAREFULLY. I can't tell you how many times I've had to go back and re-read the directions to get it right. I went so far as to reinstall Windows 10 v.1909 on an external drive and issued commands that way, as a work around. Today, I decided to take a chance, and got everything working again.
Click to expand...
Click to collapse
i treid this with no luck
dokibull said:
i treid this with no luck
Click to expand...
Click to collapse
What errors are you seeing? No communication in fastboot mode? If so, your driver is not properly installed. Your phone MUST be in fastboot mode when installing the driver. If your phone is booted up, you;ll only be able to install the ADB driver.
Additionally, I should have gone back and edited this post. The issue I was facing "back then" was that I didn't follow the driver installation directions EXACTLY. It's a bit confusing, but if you follow it step-by-step, it'll get you there. Also DO NOT use a USB C to C cable or a USB-C port. USB-A 3.0 or slower is a must with this phone. Fastboot mode is VERY picky about which USB protocol and cable you use. Recently found this out with my Surface Pro7 and had to use a regular usb a-c cable going through a 4-port hub to communicate properly and get the correct fastboot driver to install.
so i turn off the phone. plug in to the pc, power on then volume down. i downloaded the drivers from the link, but if i trie to install the drivers(browse in the folder where thr driver is) windows says there are no drivers found for this device.
MoPhoMike said:
What errors are you seeing? No communication in fastboot mode? If so, your driver is not properly installed. Your phone MUST be in fastboot mode when installing the driver. If your phone is booted up, you;ll only be able to install the ADB driver.
Additionally, I should have gone back and edited this post. The issue I was facing "back then" was that I didn't follow the driver installation directions EXACTLY. It's a bit confusing, but if you follow it step-by-step, it'll get you there. Also DO NOT use a USB C to C cable or a USB-C port. USB-A 3.0 or slower is a must with this phone. Fastboot mode is VERY picky about which USB protocol and cable you use. Recently found this out with my Surface Pro7 and had to use a regular usb a-c cable going through a 4-port hub to communicate properly and get the correct fastboot driver to install.
Click to expand...
Click to collapse
so i turn off the phone. plug in to the pc, power on then volume down. i downloaded the drivers from the link, but if i trie to install the drivers(browse in the folder where thr driver is) windows says there are no drivers found for this device.
dokibull said:
so i turn off the phone. plug in to the pc, power on then volume down. i downloaded the drivers from the link, but if i trie to install the drivers(browse in the folder where thr driver is) windows says there are no drivers found for this device.
Click to expand...
Click to collapse
Open "device manager" with the phone in fastboot mode. Scroll down to "other devices" and you should see "Android" or something of that nature. Right click it and select "update driver" follow the steps on PG 3 of the PDF I sent you and follow them exactly. NOTE where it says to click "Have Disk". Most people click "Android Bootloader Interface" then click "NEXT" at the bottom, DON'T do that. You must click "Have Disk" and then follow the prompts that follow.
Also, did you make sure to set your "environment variables" in "windows adv. system settings? This is so windows knows where to find adb.exe and fastboot.exe to execute commands.
MoPhoMike said:
Open "device manager" with the phone in fastboot mode. Scroll down to "other devices" and you should see "Android" or something of that nature. Right click it and select "update driver" follow the steps on PG 3 of the PDF I sent you and follow them exactly. Or hit me up in chat to walk you through it over the phone. Also, did you make sure to set your "environment variables" in "windows adv. system settings? This is so windows knows where to find adb.exe and fastboot.exe to execute commands.
Click to expand...
Click to collapse
e
yes ,im that point where i browse for the drivers, i select the dowlnloaded drivers and windows says there are no drivers for the device
dokibull said:
e
yes ,im that point where i browse for the drivers, i select the dowlnloaded drivers and windows says there are no drivers for the device
Click to expand...
Click to collapse
I'm having the same issue with my Sony Pro-I (just here scrounging the webs for clues in other forums)
Got adb to work but windows refuses to recognise my sony driver folder as a valid driver for the device. Did you get past this point or give up? If you solved the issue, what helped?
Tsuchimursu said:
I'm having the same issue with my Sony Pro-I (just here scrounging the webs for clues in other forums)
Got adb to work but windows refuses to recognise my sony driver folder as a valid driver for the device. Did you get past this point or give up? If you solved the issue, what helped?
Click to expand...
Click to collapse
win7 did the trick
dokibull said:
win7 did the trick
Click to expand...
Click to collapse
welp. I'll try getting the fastboot drivers to work on my win10 for a whoile longer, I only have one PC and installing win7 would be a huge pain jsut for rooting a device... ^^;
thanks for the swift reply anyhow. Will keep that as an option in mind.
Tsuchimursu said:
I'm having the same issue with my Sony Pro-I (just here scrounging the webs for clues in other forums)
Got adb to work but windows refuses to recognise my sony driver folder as a valid driver for the device. Did you get past this point or give up? If you solved the issue, what helped?
Click to expand...
Click to collapse
Okay, simple mistake. Just had to follow the installation instructions more carefully, and not click "next" here, but go to a device list. I think this is where some of us think they know what they're doing and click forward
Tsuchimursu said:
Okay, simple mistake. Just had to follow the installation instructions more carefully, and not click "next" here, but go to a device list. I think this is where some of us think they know what they're doing and click forward View attachment 5708435
Click to expand...
Click to collapse
this didn't work for me
i tried on multiple windows 10 computers and mine just won't recognize, the driver just doesn't work. i tried on linux and i was able to get fastboot devices to recognize phone but when flashing, it just gets stuck on "sending boot", any ideas?