i have had a rooted G1 for about a year and a half. i just recieved my Evo this morning.
the issue is I open sync on my pc, connect the phone and select htc sync from drop down. htc sync on the phone says that my vista pc does not have sync.
i have tried installing sync from the stock sd card and downloaded from htc.com
nothing seems to work. i saw similar questions asked several times but not clearly answered. if anyone can offer some suggestions i would be grateful.
Try uninstalling HTC Sync from your PC. And then reinstall the one from the website (it's the latest version compared to the one in the SD card). After installation run HTC Sync and connect the USB cable to your PC (don't connect the other end of the USB cable to the Evo yet). Then connect your Evo to the USB cable. If it doesn't work, try restarting your PC and then connecting it again. If it still doesn't work, try a different USB cable. I don't know if it will work but those are the procedures I'll be doing if I'm in your shoes. Sometimes USB cables and it's accompanying software are not that Plug N Play as we want them to be.
joackie27 said:
Try uninstalling HTC Sync from your PC. And then reinstall the one from the website (it's the latest version compared to the one in the SD card). After installation run HTC Sync and connect the USB cable to your PC (don't connect the other end of the USB cable to the Evo yet). Then connect your Evo to the USB cable. If it doesn't work, try restarting your PC and then connecting it again. If it still doesn't work, try a different USB cable. I don't know if it will work but those are the procedures I'll be doing if I'm in your shoes. Sometimes USB cables and it's accompanying software are not that Plug N Play as we want them to be.
Click to expand...
Click to collapse
Attempting that now. thank you.
I did as you suggested, even used my wife's data cable for her pre. and still nothing.
just to clarify...all i (should) have to do is open sync on the computer and then choose sync from the notification dropdown after connecting to usb, right?
maybe someone else has had and fixed this problem? i am unable to root without htc sync working.
2) Make sure your phone is set to USB debugging
3) Add the downloaded Vista drivers folder to the aforementioned location.
4) Go into the Device Manager (Start > Control Panel > Device Manager) and look for 'ADB Interface' or similar and expand that.
5) Right-click on the item under that and go to properties.
6) Click Update Driver and then "Browse my computer for driver software".
7) IMPORTANT STEP: Click the link, "Let me pick from a list of device drivers on my computer"
8) Click "Have Disk" and Browse to the location where you put the HTC Driver folder and open the Vista 64x folder.
9) There are two INF files in there. Choose 'htcrndis.inf' and click Open.
10) Click Okay and the device shown will be "My HTC". Select that and click Next to install.
sorry to be annoying. it is killing me to not root this device. any help?
garyfunk said:
2) Make sure your phone is set to USB debugging
3) Add the downloaded Vista drivers folder to the aforementioned location.
4) Go into the Device Manager (Start > Control Panel > Device Manager) and look for 'ADB Interface' or similar and expand that.
5) Right-click on the item under that and go to properties.
6) Click Update Driver and then "Browse my computer for driver software".
7) IMPORTANT STEP: Click the link, "Let me pick from a list of device drivers on my computer"
8) Click "Have Disk" and Browse to the location where you put the HTC Driver folder and open the Vista 64x folder.
9) There are two INF files in there. Choose 'htcrndis.inf' and click Open.
10) Click Okay and the device shown will be "My HTC". Select that and click Next to install.
Click to expand...
Click to collapse
is this folder in the sdk? where do i download from?
ok. so i go into device manager and and the "my htc" device has a triangle with a ! in it. under properties it says windows cant initialize the device driver. i go to driver properties and find "C:\Windows\system32\Drivers\ANDROIDUSB.sys and CWindows\system32\WdfCoInstaller01007.dll". i go to the appropriate folders and delete them and then install C:\Programfiles\HTC\HTCDriver\DriverFiles\Vista_x86\htcrmdis.inf i do this based on someones advice. i then reboot the computer, go to device manager, plug in phone, and the drivers are right back to "C:\Windows\system32\Drivers\ANDROIDUSB.sys and CWindows\system32\WdfCoInstaller01007.dll"
which driver in the htc drivers file should i be using?
I love CM11 but I'm just not having great service anymore like I did with the Fire OS... Now here is the question... I have the At&t version with 464 installed... Then installed the CM11 now is it possible to install 463 OS from the unlocked version so that I can install the play store and Google services... Amazons app store lack a lot of apps I currently use... If so how do I go about doing that?
1. Download the "GSM unlocked" firmware image: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
Assuming you are using Windows 7 / 8 / 10, if not, don't bother reading the following wall of text:
2. Connect device to PC & boot in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. In Windows, run the "CMD": adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin
4. If you have trouble getting your device recognised after entering recovery / ADB sideloading mode:
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try this tool (& driver) ADB, Fastboot and Drivers
It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":
Bingo,
Thanks for the guide, but I cannot get my computers to recognize the Phone in recovery ADB mode. It shows the device description as SD4930UR. It only shows as unknown. The hardware IDs are VID_1949&PID_0800. I tried the linked tool (both the 1.4.2 and 1.3 version he had) and the google drivers.
What is the exact driver that works for you?
wats2u said:
What is the exact driver that works for you?
Click to expand...
Click to collapse
I used the "15 seconds ADB Installer" v. 1.3, so the OS used the drivers from there (on Win 7 x64). Use a USB 2.0 port, just to be sure.
The drivers that work on my system might not work for your configuration...
Are you using Win 10? If so, have you tried updating the drivers with the integrated update function?
g0tNoodles said:
It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one, which also needed updating which I have just done and appears to now let the CMD see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now.
Click to expand...
Click to collapse
I can't access my phone from my computer to run the .bin after rebooting it into recovery mode. The download links for that driver installer you linked to don't work. In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.
powerlocked said:
In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.
Click to expand...
Click to collapse
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface
powerlocked said:
I can't access my phone from my computer to run the .bin after rebooting it into recovery mode. The download links for that driver installer you linked to don't work. In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.
Click to expand...
Click to collapse
DePingus said:
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface
Click to expand...
Click to collapse
What DePingus said, regarding the 15 seconds ADB... It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Not the first time people struggling with it, Windows is just too darn complicated.
Bingo Bronson said:
What DePingus said, regarding the 15 seconds ADB... It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Not the first time people struggling with it, Windows is just too darn complicated.
Click to expand...
Click to collapse
Good lord...tried all of that and more and still not able to get my device to show up in ADB. The last installer gives me the message "[Error] Incompatible with Win8 x64". So two questions...anything else I can try for drivers, or, can I use a method other than ADB, such as Safestrap?
Thanks again for all your insight on this forum
EDIT: For anyone that struggled as much as me to finally get drivers to work, this method ultimately worked as posted by @hijax2001
4) I also grabbed the Kindle Fire ADB drivers from here for convenience in Step 7 (below) https://docs.google.com/file/d/0B1Z1J6LQic8PQjFjS0FpVGVia2M/edit
7) For me, ADB did not initially detect my phone. I ended up having to go into Control Panel in Windows, to Device Manager, find the Fire phone, choose Update Drivers, then Browse My Computer, Let Me Pick, Show All Devices, Have Disk, then find the folder from Step 4 (above) and add Android Composite ADB Interface by hand. Once I did that, I unplugged and replugged the USB to the phone and then typed "ADB devices" again at the ADB command prompt, like in Step 6. There it is! Ok, next step...
ElQuixote said:
Good lord...tried all of that and more and still not able to get my device to show up in ADB. The last installer gives me the message "[Error] Incompatible with Win8 x64". So two questions...anything else I can try for drivers, or, can I use a method other than ADB, such as Safestrap?
Thanks again for all your insight on this forum
Click to expand...
Click to collapse
I'm not familiar with adbdriverinstaller, but which ever you use, make sure you are running the installer as admin (right-click on the installer). Also, if you extract the 15 second installer exe with 7zip you get access to the drivers installers separately. Maybe try manually installing them.
DePingus said:
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface
Click to expand...
Click to collapse
Ran 15s ADB. I right clicked SD4930UR in device manager. After selecting update driver, then 'Let me pick from a list..' there is no 'left' or Google listed. It loads a list int he center of the screen of generic hardware devices.. the only one that pertains to a phone is 'mobile' and after selecting that there are no driver options to be found. There is no 'android' to select from that list.
It's doing this on both windows 7 and windows 10.
Bingo Bronson said:
1. Download the "GSM unlocked" firmware image: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
Assuming you are using Windows 7 / 8 / 10, if not, don't bother reading the following wall of text:
2. Connect device to PC & boot in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. In Windows, run the "CMD": adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin
Click to expand...
Click to collapse
I tried this method, to install 4.6.3 unlocked over my ATT (now carrier unlocked) 4.6.4. After I sideloaded, I get the following lines in Recovery, indicating that this didn't work. Any thought? Is there something else I need to do to be able to install the GSM on the ATT version?
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted
EDIT: Determined that the file I originally downloaded may not have been complete and sure enough a second version is larger...
powerlocked said:
Ran 15s ADB. I right clicked SD4930UR in device manager. After selecting update driver, then 'Let me pick from a list..' there is no 'left' or Google listed. It loads a list int he center of the screen of generic hardware devices.. the only one that pertains to a phone is 'mobile' and after selecting that there are no driver options to be found. There is no 'android' to select from that list.
It's doing this on both windows 7 and windows 10.
Click to expand...
Click to collapse
I think those steps are for Windows XP. For Windows 7, 8, or 10 use the following steps to update the driver:
Those steps are for Google USB driver. For Amazon Kindle Fire USB driver, use the following steps:
1) Right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer.
2) Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>.
jack9955 said:
I think those steps are for Windows XP. For Windows 7, 8, or 10 use the following steps to update the driver:
1) Right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer.
2) Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>.
Click to expand...
Click to collapse
Ohhhh okay thank you for explaining this. After finding KindleFire down the list I was able to update my drivers. I've now installed the update to both of my ATT Fire phones, and both are now 4.6.3 and working great with working playstore options.
Thank you jack9955 and everyone else for the tutorials.. much appreciated!
How to Setup the Fire phone for ADB
An illustrated guide ... 2015-09-15
Open open Device Manager. This is what my 4.6.3 Fire phone looks like when plugged in normally to my Windows 7 computer. Power it off and boot into the stock recovery using PWR + VOL UP (hold both buttons until recovery screen appears). The Fire device will disappear from Device Manager.
At the phone's recovery menu choose "Apply update from ADB". Back in Device Manager do a Scan for Hardware Changes and you should now see this. Right click on the Fire and choose uninstall.
Grab "15 Seconds ADB Installer" and install it as admin and hit yes for everything. http://forum.xda-developers.com/showthread.php?t=2588979
Now scan for hardware changes again and you will see this new device. Right Click this device and choose Update Driver Software.
From this window choose "Browse my computer for driver software."
From this window choose "Let me pick from a list of device drivers on my computer."
From this window choose "Show all devices."
In the section on the left that says Manufacturer find "Google Inc." Then, on the right, choose "Android Composite ADB Interface." Accept through any warnings.
The Device Manager should now show this.
Open up a cmd prompt and test that adb can see your phone with the "adb devices" command. Now you can sideload 4.6.3 or whatever.
DePingus said:
How to Setup the Fire phone for ADB
An illustrated guide ... 2015-09-15
Open open Device Manager. This is what my 4.6.3 Fire phone looks like when plugged in normally to my Windows 7 computer. Power it off and boot into the stock recovery using PWR + VOL UP (hold both buttons until recovery screen appears). The Fire device will disappear from Device Manager.
At the phone's recovery menu choose "Apply update from ADB". Back in Device Manager do a Scan for Hardware Changes and you should now see this. Right click on the Fire and choose uninstall.
Grab "15 Seconds ADB Installer" and install it as admin and hit yes for everything. http://forum.xda-developers.com/showthread.php?t=2588979
Now scan for hardware changes again and you will see this new device. Right Click this device and choose Update Driver Software.
From this window choose "Browse my computer for driver software."
From this window choose "Let me pick from a list of device drivers on my computer."
From this window choose "Show all devices."
In the section on the left that says Manufacturer find "Google Inc." Then, on the right, choose "Android Composite ADB Interface." Accept through any warnings.
The Device Manager should now show this.
Open up a cmd prompt and test that adb can see your phone with the "adb devices" command. Now you can sideload 4.6.3 or whatever.
Click to expand...
Click to collapse
I see there are atleast two USB drivers you can use to set up ADB on the Fire Phone. Amazon Kindle Fire USB driver and Google USB driver. If Google USB driver is installed, you should select "Google, Inc." for Manufacturer. For Amazon USB driver, you should select "Amazon.com" for the Manufacturer, Device Manager will show the device as Kindle Fire> Android Composite ADB Interface.
jack9955 said:
I see there are atleast two USB drivers you can use to set up ADB on the Fire Phone. Amazon Kindle Fire USB driver and Google USB driver. If Google USB driver is installed, you should select "Google, Inc." for Manufacturer. For Amazon USB driver, you should select "Amazon.com" for the Manufacturer, Device Manager will show the device as Kindle Fire> Android Composite ADB Interface.
Click to expand...
Click to collapse
I've also noticed some people using the Amazon drivers. But they're not included with "15 Seconds ADB".
Works seamlessly too on any linux terminal
Just, so you know, your method works very well too on any linux computer. I had the same issue and now it is fixed. I can write a tutorial complimenting this if needed.
hello lam from china english is very bad thanks for friephone cm l hope you will do cm12 cm12.1 don't abandon our china people have lot's of people hope and camera have better solution official camera and fire os5 Do you have any news thanks
csx21 said:
hello lam from china english is very bad thanks for friephone cm l hope you will do cm12 cm12.1 don't abandon our china people have lot's of people hope and camera have better solution official camera and fire os5 Do you have any news thanks
Click to expand...
Click to collapse
We can't do CM12 because the Fire Phone's bootloader is still locked and the current FireOS 4 is based on KitKat. Unless Amazon unlocks the bootloader or releases FireOS 5 for these phones, we are stuck in KitKat (CM11).
Will applying update from adb format the phone..hopefully it will
I have my new Nexus 5X with Android 6 on it. I am trying to unlock and root.
I have enabled USB debugging and OEM unlock.
I have downloaded and installed the SDK package with Platform-Tools and drivers in the 'Extras' folder.
When first plugging in the phone I install the drivers with the 'Have Disk' and browse method.
Every time, installing the driver returns an Error 'Code 10 - device cannot start. 'Android ADB interface' shows up in device manager when I plug in the phone but with an exclamation point.
I have uninstalled, downloaded fresh drivers from other sources, reinstalled, tried plugging the phone in while in 'recovery' mode (starting by pressing all 3 hardware buttons).
I uninstall every time and reboot both the computer and the phone. The drivers simply won't work.
What is going on here? Is the phone/Android 6 still too new to unlock and root?
P.S. I should also say that I go into Developer options and change the Select USB Configuration between PTP and MTP (between which, I have not seen mention of the correct choice. Does it not matter?) - I cannot chose the others RNDIS, Audio Source, or MIDI; it seems to want to default to 'Charging' when I try to change to these choices.
Having the same issues on Windows 8.1. Can't get my 5x to connect to transfer files or to show up in adb.
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
bsinc1962 said:
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
ahunter said:
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
Click to expand...
Click to collapse
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
rgerrans said:
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
Click to expand...
Click to collapse
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
ahunter said:
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
Click to expand...
Click to collapse
Sorry. I should have been more specific. Part of it is I did so many different approaches they've bled together in my head and I was on my way out the door yesterday when I fired off the reply.
To try to break it down from memory (going to throw in a couple of different options since I can’t seem to fully uninstall / reinstall so please provide any corrections once you get it to work or let me know if anything doesn’t match what you find and I’ll try to remember from there):
Phase I (phone on and connected to computer):
Open Device Manager. My phone shows as Android Device | Android Composite ADB Interface or Android ADB Interface.
If it is the Composite version, I believe I had to update it to the straight “Android ADB Interface to get Phase II to work)
If you don’t see that, look to see if you have any uninstalled devices by scanning for new. If so, then right click on that device, and choose “Update Driver”
Choose “Browse my computer for driver software”
Choose the “Have disk” option and browse to your USB Driver folder
From there, choose “Google | Android ADB Interface”
Phase II (phone in recovery connected to computer)
On phone, choose “Update device from ADB”
Open Device Manager and you should see the Nexus 5 under Other Devices with the yellow triangle.
Right click on it and “Update Drivers”
Choose “Browse my computer for driver software”
Choose “Let me pick from a list….”
Choose “Android Device”
Choose “Android ADB Interface”
Now you should be able to push the update over
Simple method: What I did was plug it in and wait for it to show up in device manager. Then I deleted the device (the one that shows adb) from device manager. Then I unplugged the device and plugged it back in... Then waited for drivers to install on it's own. Everything was good after that.
I have no trouble other than on Windows 10. Windows 10 doesn't even show the drivers from a list to install.
Sent from my Nexus 5X using Tapatalk
I followed this to get my Nexus 5X detected on my Windows 10: http://stackoverflow.com/questions/...ould-we-use-for-the-nexus-5/19839812#19839812
I have no trouble with Fastboot or adb. It only happens when I try and sideload. I end up have to use my Macbook Pro to sideload.
Sent from my Nexus 5X using Tapatalk
bsinc1962 said:
Just need the right drivers. Download the driver files from here:
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I wish it were that easy. But, no, this does not work. Nor do I believe my issue is the same as you others here, as I have Windows 7 and not the 8.1 and 10 issues that you are having.
No, no matter what driver I use, including any from your kind link, bsinc1962, they return an error, code 10 when trying just to install the drivers. I cannot go further.
What is this Code 10 error preventing drivers from installing?
tl;dr: Boot your Moto in Fastboot mode with USB connected to PC for it to recognize the device, then reboot normally.
For those with issues with their PC recognizing the device, in my case Verizon's Droid variant. I racked my brain all weekend and tried multiple different cables and PCs in order to push some ADB commands and transfer files with nothing seeming to get the PCs to recognize the phone. I just now rebooted into Fastboot mode and the PC now recognizes the phone, both in Fastboot and under normal boot. Hope this helps anyone with a similar problem. Cheers!
I have tried this method and still the PC does not see the Phone in File Transfer mode but will see it in Photo transfer.
Help, I have the Moto 6.4 drivers installed, when I check device Manger on the PC i see "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)"
If I try to force a driver update I am told the "INF" is invalid. Any suggestions are welcome, this has me scratching me head and is driving me nuts.
Connect your phone first
and Choose Usb to File Transfer in Mobile
In PC
Go to the Device Manager
And you will see Portable Devices
and there your Device Name or Unknown Device
Open it By clicking Double
Click Driver
ThenUpdate Driver
then you have tow option to fix
1.Search automatically for update driver software
2.Browse my Computer for driver software
I recommendedd OPTION 2
then come up two option
1.Browse driver software
2.Let me pick from a list of device drivers on my computerr
I recommended OPTION 2
and computer will show you all Compatible driver
I recommended to select MTP USB Device
THen NEXT NEXT BOOM
mijing said:
Connect your phone first
and Choose Usb to File Transfer in Mobile
In PC
Go to the Device Manager
And you will see Portable Devices
and there your Device Name or Unknown Device
Open it By clicking Double
Click Driver
ThenUpdate Driver
then you have tow option to fix
1.Search automatically for update driver software
2.Browse my Computer for driver software
I recommendedd OPTION 2
then come up two option
1.Browse driver software
2.Let me pick from a list of device drivers on my computerr
I recommended OPTION 2
and computer will show you all Compatible driver
I recommended to select MTP USB Device
THen NEXT NEXT BOOM
Click to expand...
Click to collapse
BOOM, Thank you worked like a charm... after trying every other way I could think of was driving me nuts.
mijing said:
Connect your phone first
and Choose Usb to File Transfer in Mobile
-- snip --
THen NEXT NEXT BOOM
Click to expand...
Click to collapse
Thanks so much! Was having same issue as OP but with Win 7 and Moto Z2 Force. Even with the Motorola Device Manager app installed, I the device kept showing up as "unknown" in Windows Device Manager.
I've updated your steps to include one you left out (in bold):
Connect your phone first
and Choose Usb to File Transfer in Mobile
In PC
Go to the Device Manager
And you will see Portable Devices
and there your Device Name or Unknown Device
Open it By clicking Double
Click Driver
ThenUpdate Driver
then you have tow option to fix
1.Search automatically for update driver software
2.Browse my Computer for driver software
I recommendedd OPTION 2
then come up two option
1.Browse driver software
2.Let me pick from a list of device drivers on my computerr
I recommended OPTION 2
and computer will show you all Compatible driver
I recommended to select Mobile Device
Then select MTP USB Device
THen NEXT NEXT BOOM