Related
Follow these instructions and your vista and 7 problems is over...
I used this guide and it works on my phone..
Originally Posted by pvdhelm
To follow this guide please make sure you have a copy of WinRAR installed, I will refer to the Windows Mobile Device Centre as the WMDC for ease of reading. If you do not have the WMDC installed please go here to install it first - http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
One problem with windows VISTA and 7 is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.
For this guide firstly you need to download the new drivers:
Drivers for Windows Vista/7 x32 - http://forum.xda-developers.com/attachment.php?attachmentid=33662&d=1169888879
Drivers for Windows Vista/7 x64 - http://forum.xda-developers.com/attachment.php?attachmentid=33892&d=1170385335
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.
Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA/7 PC.
Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon
In the connection settings menu untick "allow USB connections" then press OK.
Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.
Scroll down the list and make sure these services are present:
Windows Mobile-based connectivity
Windows Mobile 2003-based connectivity
If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.
Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync".
This will bring up the properties of the currently connected device (the hermes in bootloader).
Go to the "Driver" tab and click "Update Driver".
Click "Browse My Computer for Driver Software".
Select "Let me pick from a list...."
Click the "Have Disk" button.
Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.
Vista x32 users select the file "wceusbsh.inf"
Vista x64 users select the file "wceusbshx64.inf"
Then click Open.
click next and the driver will be installed (wait a moment).
Press close and escape back to the desktop now.
Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.
click the WMDC line and click "End Process". In the confirmation window, again press End Process.
Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").
Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which vista uses when the device is in bootloader mode.
Can this be made a Sticky please..??
Followed your Steps on Win7 x64 but WMDC doesnt connect do my device although I re-enabled USB connections. Digital Driver signing is disbaled.
No it did work, I just didnt get it
Write this into the wiki plx, really helpful.
All done till the driver installation.
But start from task manager and so on, it's failed to connect.
Am i doing wrong?
Just try to flash, at my side WMDC shows no connections either but flashing is possible.
DasEtwas said:
Just try to flash, at my side WMDC shows no connections either but flashing is possible.
Click to expand...
Click to collapse
After i installed the drivers then i started WMCD and re-enable USB connections and then took out my cable out of the phone then put it back in and it connected..
Method with no install
What I have been doing with Win7 without installing any drivers is
- Put phone in bootloader mode (press power and left OK button while pressing the reset button on bottom)
- Start the RUUWrapper
This of course assumes that you have hardSPLed the phone and select the right options, no autodetect
This is what I have been doing for a while now, I dont recall updating any drivers or activesync/mobile center
coolsva said:
What I have been doing with Win7 without installing any drivers is
- Put phone in bootloader mode (press power and left OK button while pressing the reset button on bottom)
- Start the RUUWrapper
This of course assumes that you have hardSPLed the phone and select the right options, no autodetect
This is what I have been doing for a while now, I dont recall updating any drivers or activesync/mobile center
Click to expand...
Click to collapse
Well this is another option you can do then...should i add this to my post..?
Hello i have a problem unlocking the bootloader of my xperia sl. The problem is when i turn off my phone to blue led, suddenly it goes to orange then began charging? What do? I have checked my rooting status and the bootloader is allowed:yes .. Please help me, if there's a solution thanks more power
doodoot_09 said:
Hello i have a problem unlocking the bootloader of my xperia sl. The problem is when i turn off my phone to blue led, suddenly it goes to orange then began charging? What do? I have checked my rooting status and the bootloader is allowed:yes .. Please help me, if there's a solution thanks more power
Click to expand...
Click to collapse
Do just that :- Step By Step
- open device manager
- connect in fastboot mode and click the s1 boot fastboot right away
- disconnect the device , without closing the s1boot fastboot windows !
- click update drivers -> browse for drivers on my computer -> let me pick from a list of device drivers on my computer
-> have disk -> browse and locate the device drivers -> press ok
- reconnect the device in fastboot and click next on the computer right away of the blue led
hello bro it says it encountered an error, the android ADB something bro
white paranoia said:
Do just that :- Step By Step
- open device manager
- connect in fastboot mode and click the s1 boot fastboot right away
- disconnect the device , without closing the s1boot fastboot windows !
- click update drivers -> browse for drivers on my computer -> let me pick from a list of device drivers on my computer
-> have disk -> browse and locate the device drivers -> press ok
- reconnect the device in fastboot and click next on the computer right away of the blue led
Click to expand...
Click to collapse
doodoot_09 said:
hello bro it says it encountered an error, the android ADB something bro
Click to expand...
Click to collapse
I think you dont need to disconnect the phone...
Open Device Manager in your windows, standby at that....Turn off your phone, and after it turned off, push and hold the Volume Up button and at the same time connect the phone to the computer with a USB-cable. This will trigger FASTBOOT mode and windows will start driver search....
Once there is a popup in Device Manager with what word i cant remember, directly right click on it and point to the folder containing the driver...If the folder youre having, failed to give the driver required....Download driver below, my driver compilation...
http://www.mediafire.com/?dw77ineguikk7bo
Unzip the Xperia_Ion_Fastboot_USBDriver.rar and unzip both files that came out
that is fastboot_with_Android_USB_file.rar and drivers.zip
Point out the driver search to drivers.zip folder...Hope it helps
Shows up on my laptop but not on my desktop, have tried back and front USB ports
have uninstalled USB drivers, reinstalled USB drivers (universal adbdriversetup6 downloaded from xda sources)
downloaded android SDK manager and installed whatever USB stuff it had there
used USBdeview to remove any nexus 7 related things and then re-install USB drivers
Cannot for the life of me figure out what's going on... can anyone help me please
When I plug it in my desktop it makes the sound like something got connected... even has the safely remove hardware thing with nexus 7 there, but nothing in my computer
also have tried with/without USB debugging
tried removing my rom and flashing stock etc
Nothing has worked so far
and yes forgot to put in the title but this is for the Nexus 7FHD 2013
Is there a chance you are using usb3.0 port and can switch to usb2.0?
I would suggest you backup, flash stock, and redo your driver deinstall/install on stock. Try to get it working there first. Make sure USB debugging is disable on stock.
sfhub said:
Is there a chance you are using usb3.0 port and can switch to usb2.0?
I would suggest you backup, flash stock, and redo your driver deinstall/install on stock. Try to get it working there first. Make sure USB debugging is disable on stock.
Click to expand...
Click to collapse
tried USB 3.0 as well as 2.0 on desktop doesnt work, shows up as a device on safely remove hardware, and I can also see it under other devices in hardware manager or whatever but doesnt display in computer
USB debugging enabled or disabled on stock doesn't work.. tried going back to stock and doing driver installation etc as well
In device manager are there any unknown devices?
Did you remember to
Originally Posted by Geodude074 View Post
When you uninstall the driver, make sure you check the option to DELETE the driver as well. Otherwise when you try to reinstall it, it will just reinstall the old driver again
Driver instal with WinXP
I went around with this problem after both my Win7 laptop and WinXP desktop both recognized my N7 2013 the first time I connected to them. I had no problem dragging and dropping files.
I had then returned the tab back to BB for a exchange for another. This time after setting up the tab and setting the MTP file toggle and USB settings correctly......The Win7 laptop worked find and recognized the N7 just like it did on the first tab. But now the WinXP desktop did not work and only saw the N7 as a ABD device.
You may already have the correct drivers (if not those are available here in several posts). You just have to direct windows driver update to the correct place for the MTP driver. Here is how i did it.
1. Open up the Device Manager on your PC and locate the Android device it sees. Select the update driver option and you get to the "Welcome to the Hardware Update Wizard" screen.
2. In this window it asks "Can Windows connect to Windows Update to search for software?" Select the 3rd option ' No, not at this time"
3. In the next window "This wizard helps you install software for...." Select the 2nd option "Install from a list or specific location (Advanced)
4. In the "Please choose your search and installation options" window... go down to the bottom and select "Don't search, I will choose the driver to install" option.
5. Now finally the window we need..... "Select the device driver you want to install for this hardware" The "show compatible hardware" button should be selected...if not check that box. You should see 2 choices in the "Model" area..... Google Nexus ADB Interface" and what we need to select " MTP Device" click on the MTP Device and hit next......it should install and your Nexus 7 should then show up properly.
Hope this works for all that have had a hard time as I did....I just found it odd after getting a replacement N7 my XP desktop did not recognize it as it did to the original one I used the day prior.
un1bomber said:
Shows up on my laptop but not on my desktop, have tried back and front USB ports
have uninstalled USB drivers, reinstalled USB drivers (universal adbdriversetup6 downloaded from xda sources)
downloaded android SDK manager and installed whatever USB stuff it had there
used USBdeview to remove any nexus 7 related things and then re-install USB drivers
Cannot for the life of me figure out what's going on... can anyone help me please
When I plug it in my desktop it makes the sound like something got connected... even has the safely remove hardware thing with nexus 7 there, but nothing in my computer
also have tried with/without USB debugging
tried removing my rom and flashing stock etc
Nothing has worked so far
Click to expand...
Click to collapse
Just go in settings then storage and then computer usb connection by opening preferences in storage and then make sure mtp is checked.
Thank you guys SO MUCH for the help... I actually just returned my unit to staples because those POS wont give me a price adjustment vs google play
Will buy another one from google play and follow steps in the thread!
un1bomber said:
Thank you guys SO MUCH for the help... I actually just returned my unit to staples because those POS wont give me a price adjustment vs google play
Will buy another one from google play and follow steps in the thread!
Click to expand...
Click to collapse
We are always here to help.
I remember few years back I installed miui ROM on my xperia n couldn't connect to PC , only to realise USB wasn't turned to mtp by default. I thought it was a bug, tried everything even to fix it only to realise this.
Thanks a lot !!! This solution worked perfectly for me
You saved lots of time for me
Thanks a ton :good::good::good:
Best regards,
RR215 said:
I went around with this problem after both my Win7 laptop and WinXP desktop both recognized my N7 2013 the first time I connected to them. I had no problem dragging and dropping files.
I had then returned the tab back to BB for a exchange for another. This time after setting up the tab and setting the MTP file toggle and USB settings correctly......The Win7 laptop worked find and recognized the N7 just like it did on the first tab. But now the WinXP desktop did not work and only saw the N7 as a ABD device.
You may already have the correct drivers (if not those are available here in several posts). You just have to direct windows driver update to the correct place for the MTP driver. Here is how i did it.
1. Open up the Device Manager on your PC and locate the Android device it sees. Select the update driver option and you get to the "Welcome to the Hardware Update Wizard" screen.
2. In this window it asks "Can Windows connect to Windows Update to search for software?" Select the 3rd option ' No, not at this time"
3. In the next window "This wizard helps you install software for...." Select the 2nd option "Install from a list or specific location (Advanced)
4. In the "Please choose your search and installation options" window... go down to the bottom and select "Don't search, I will choose the driver to install" option.
5. Now finally the window we need..... "Select the device driver you want to install for this hardware" The "show compatible hardware" button should be selected...if not check that box. You should see 2 choices in the "Model" area..... Google Nexus ADB Interface" and what we need to select " MTP Device" click on the MTP Device and hit next......it should install and your Nexus 7 should then show up properly.
Hope this works for all that have had a hard time as I did....I just found it odd after getting a replacement N7 my XP desktop did not recognize it as it did to the original one I used the day prior.
Click to expand...
Click to collapse
If nothing else here has helped you solve this issue, check my thread, it should be of some help to you...
I'm having an issue where I can connect to my laptop in debug mode, but I'm not able to connect in the MTP mode with debug turned off. I expected to be able to mount the device storage in either mode.
Is that correct? If so, any ideas? I do notice I can't seem to get the MTP driver to stay in device manager.
Rick
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?
I installed the motorola device manager, it just got me the file transfer driver.
While on fastboot mode, all i get on windows 10 is an inactive device called "Fastboot Addison S".
Anyone can help ?
I've been searching for days but can't find the driver.....
Did you solve this issue?
same issue here, please help
I know this is an old post but I came across this issue on the moto Z as well as the moto Z play and was happy to find that this installer package contained the files for both (The EXE installer worked for me, whereas the raw drivers did not)
Note that this solution works only for Windows, I could not get any drivers to run correctly for the play on MacOS so I just booted into windows instead.
Firstly download this zip file.
Unzip it wherever you like, and run either DPInst_x64.exe or DPInstx86.exe depending on your OS (Note, x86 is 32-bit and x64 is 64-bit, if you are unsure whether your system is 64 or 32, please hold the winkey and press R, and type "msinfo32" without the quotation marks, and look at system type on the right)
After installing, you must go into Device manager, select your "Fastboot" incorrectly labeled device, right-click, click "update drivers" click "browse my computer for driver software" then click "Let me pick from a list of available drivers on my computer" double click on "Android device" and pick whatever the device is plugged in as. Eg: If you're plugged in on bootloader currently, select fastboot.
This works for the Z play AND Z for me. Hopefully this helps anyone else with the same issue who also stumbles across this thread on Google, or at least one of you guys.
Cheers.
Lemagex said:
Firstly download this zip file.
After installing, you must go into Device manager, select your "Fastboot" incorrectly labeled device, right-click, click "update drivers" click "browse my computer for driver software" then click "Let me pick from a list of available drivers on my computer" double click on "Android device" and pick whatever the device is plugged in as. Eg: If you're plugged in on bootloader currently, select fastboot.
Click to expand...
Click to collapse
I just wanted to let everyone know that this worked perfectly for me. I can now see my Moto Z2 Play in the Device Manager on Windows 10 using this method. I'm planning to unlock it all and flash custom ROMs, root, etc etc now that I can do it all. Thanks for this post!:good:
Hi! I had the same problem with my Moto Z Play and did what you suggested, but foolishly I installed the CDMA instead of the GSM, then - when I noticed the mistake - I erased the driver, and now I'm trying to install the right one, but there is no longer a list where it is supposed to be (I mean the different types of phones). I've tried to reinstall the DPInst_x64.exe several times now, rebooting my PC each time, but nothing...It still won't show the list What should I do?
I had the same issue before when i switched back form Linux to Windows for a few weeks. This drivers works for me.
https://support.motorola.com/us/en/solution/MS88481