I followed the instruction on this forum post Here to prep for and then install AOSCP 3.63/Android 7.1.2.
Everything went relatively smoothly for the install, but now I have a problem with the drivers.
I first noticed that once the install was complete HTC Sync Manager would not detect that my phone was plugged in, though windows explorer could access the microSD. I (actually foolishly) uninstalled HSM (loosing my data backup in the process, though I didn't have much anyway) and the HTC Driver Installer. I then reinstalled HSM hoping it would retrieve the drivers. That didn't change anything, but I thought it was fine, I just wouldn't worry about using HSM.
But I then came across the issue that Netflix won't install on a phone with an unlocked bootloader, so I thought I would just use fastboot to re-lock the bootloader now that the OS is installed and try installing Netflix again. What I ran into was that fastboot can't detect the phone as plugged into my computer either. I checked device manager and I find that it has what I assume is the phone under "Other Devices" named "SMS/MMS" without any driver installed. I've tried HSM again a few times but nothing changes. (See picture attached below)
So is there anything I can do to install a new driver that doesn't involve HSM? Their HTC Driver Installer is still on my computer. I did notice, when I first plugged in the phone after the OS install, windows said "setting up Android1", so it only saw the device as "Android1".
Any ideas?
I am running RR now. But when I plug into my PC I get a notification on the phone to charge, transfer files or transfer photos. When I select Transfer Files I get "Desire Eye" show in windows explorer and folders under it are internal or SD card. I don't have HTC installed on my PC at the moment so cannot comment about that.
Related
Hi there.
I picked up a refurbed Incredible 2 (running 2.3.4) and am trying to get it to connect to PC so I can move files across between the PC and either internal memory and/or microSD cards. I'm having no luck on Windows 7.
I changed the Default Connection Type from Charge Only to Media Sync / Disk Drive / HTC Sync (after installing the HTC Sync software - NOT the HTC Sync Manager, which apparently only supports the newer phones) to no avail. I've tried them all, and they all have the same issue. I've done this both with and without USB debugging checked, and with "Unknown Sources" ("allow installation of non-Market apps") checked. I've also tried uninstalling Sync, installing Sync Manager, trying again (no change), and then reversing it (uninstalling Manager, and reinstalling Sync) - again, no change. Sync does not see the phone while connected and in "HTC Sync" mode via the Default Connection Type (or anything else).
When I plug the phone in to the PC the PC shows a "USB Device not recognized" and sometimes I will get a "Driver did not install successfully" message. Device Manager is showing one Unknown Device with a "!" issue under the USB controllers category I'm assuming is the problem. There is also nothing showing up under the Disk Drives category in my Device Manager other than my hard disk, even though some of the guides I'm looking at say I should have something related to the phone in there.
I've tried connecting it with 2 different USB cables, just in case the one that came with it was not fully functional. I've used the second cable for data transfer in the past, so it should work. No difference.
I've restarted several times, with and without the microSD card installed. I've tried unmounting and remounting the card as well, no difference.
Am I missing some kind of Win7 drivers for the Incredible 2 that are not installed automatically and/or with the HTC Sync install? I've seen some references and links to HTC drivers that are apparently not on the HTC site, but I am very leery of downloading an .EXE from a random website and just installing it to see if it works. I'd think if this was necessary, it would be on the HTC site.
Anyone know what gives here? I can't think of anything else to try.
Am I a complete newb here, or is this potentially an issue with the refurb'ed phone?
Thank you very much for any assistance!
I use the driver linked on the revolutionary.io site (http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe) and I have never had an issue.
Sent from my DInc2...
update
Hi there.
I attempted this, but still no change. Do you know where this installs the drivers to, so I might try to manually point the Device Manager "Unknown Device" to them?
When I try to update the driver via Device Manager, however, it is telling me the following:
"Windows encountered a problem installing the driver software for your device.
windows found driver software for your device but encountered an error while attempting to install it.
'Unknown Device'
Windows has stopped this device because it has reported problems (Code 43)"
Thank you for any further assistance or ideas.
Doesn't matter where you place them but you'll need to go to control panel/system/device manager find the device with the issue and select update driver.... Then it should be recognized
Sent from my HTC Droid Incredible 2 using xda app-developers app
OP - do you have any other USB device drivers for other smartphone(s) installed on your PC? If so, uninstall all of them and reboot it clean.
Assumed that you are running VZW stock software - phone isn't rooted ?
Is your HTC Installer running this version - 3.0.0.007 - that's mine (have it running on W7 Pro and Ultimate on desktop & 2 laptop, no problems for me - I also have it running Win 8.
Uninstall HTC Installer & reboot - without connecting the phone. Turn off firewall & antivirus on your PC temporary, reconnect the phone & follow the prompts to reinstall HTC drivers. Once it's done, disconnect the phone & power down the computer.
Restart the PC and then reconnect the DI2 to it, hopefully - it will recognize the phone and allow you to connect & recognize the mSD card for data transfer, etc.
Please post any specific error messages as you see them. Good luck.
A common cause of "unrecognized USB device" is a bad cable. Try another. Or, try a different USB port on your PC.
I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.
OMG... finally got it working. I installed HTC Sync Manager again and decided to run it and see what happened. While it was scanning for music on my computer windows installed the drivers. More than once it seems.
Now I need to know if I can uninstall Sync Manager but keep the drivers. It keeps opening up and I don't know if it's safe to flash recovery if that's going to happen.
Flashed TWRP successfully and made my back up.
--------------------------
OLD NEWS BELOW:
Here's the deal... I just flashed the 3.x RUU so I'm stock but I'm unlocked and s-off. I'm trying to flash TWRP via fastboot so I can get a custom ROM on here. I turned on USB debugging on the phone.
First of all, that stupid HTC Sync manager keeps trying to install and I don't know how to stop it. Googling has not helped with this.
Second, I can't get the device to be seen in adb, or at least not online. I seem to be going backwards with all the steps I have taken to try to get this to happen.
I'm using dotatt's adb package. When I attach the phone while it is off windows looks for drivers and usually fails. One time it seemed to work and adb saw the device but then when it boots up that Sync Manager wants to install so I decline. Then my phone was seen but listed as offline.
So I tried uninstalling all HTC things on my computer and reattach phone. Didn't help anything. I tried installing the HTC Sync then uninstalling it thinking I would get the drivers, no go.
I grabbed these Universal ADB drivers http://www.koushikdutta.com/post/universal-adb-driver linked to from a twrp page here https://twrp.me/devices/htconem9.html
Nothing lists as a device in ADB at all now.
My windows Device Manager shows "Unkown Device" under "Other Devices" with no driver listed.
Tried this:
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
http://forum.xda-developers.com/showthread.php?t=2588979
Still not working.
ACK! Can anyone help me out?
Is there still an issue with using usb 3.0 ports? I feel like I heard something about that way back when.
That's pretty much how it's always been. Best way to get the appropriate drivers is to install HTC sync, let it do its thing, reboot the PC, then uninstall HTC sync without removing the drivers. To the best of my knowledge, been that way since at least the days of the Incredible, if not before. At least it's how I've always gotten the drivers to use adb.
Yeah I remember that from the Rezound, which is why I did that, but it seems that the drivers didn't actually get installed this time until I let HTC Sync Manager start running and scanning my computer. That's when I saw the message that it was looking for drivers and twice it told me it installed them.
I would think it would have them installed during the 'actual' installation process. So I guess I just uninstalled prematurely. Seems weird. But it's working now so all good.
Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.
Is my watch bricked? PC & Device Manager not recognizing watch, drivers are installed
I was running on the latest (v2.7) Negalite Rom NX 1 when I got the notification to update the watch. Upon rebooting (and presumably installing), the watch got stuck in loading screen (4 dot animation) so I force rebooted the watch into recovery and wiped everything (Advanced Wipe, everything).
Upon connecting my watch to my computer (watch in recovery (TWRP)), I was not able to connect the watch to ADB nor Fastboot; adb/fastboot devices returns nothing.
I tried reinstalling, uninstalling, deleting and reinstalling the drivers but I haven't gotten any success
I've tried several ports (and another computer) without any success
The watch does not show up at all in Device Manager (definitely not in "Other Devices")
I'm unable to manually install the device drivers because the watch does not show up in Device Manager
The device is connected because it's charging, but there's no notification sound when plugging the watch/USB cable into the computer
I have previously been able to connect the watch through ADB, to be able to transfer Negalite rom, likely half a year ago
I've tried installing Pdanet ADB Drivers, but it requires the watch to be detected otherwise it closes the installer
I am using Windows 10
Has anyone else had this problem? Is there a way to check if the drivers are installed or not?
Every thread I've read instructs to install the drivers manually for the device, but I don't have the device in Device Manager.
I'd love to be able to use the watch again (currently sitting @ 100% battery, in TWRP).
Thank you
Edit: When I boot system from recovery (I know I don't have an OS installed), I get a message that I haven't seen before: "Device software can't be checked for corruption"
I read that it was caused by unlocked bootloader, but I've never encountered that before, if I had accidentally booted system without OS.