Related
C:\Documents and Settings\SilenT>cd c:\android\tools
C:\android\tools>adb usb
error: device not found
C:\android\tools>adb devices
List of devices attached
debugg mode on/off ...same problem
and my recovery img dosent work when i enter the recovery mode Exclamation Point with android guy
os: win xpsp3 ... drivers unninstaled\instaled from everywhere ~X( still no luck sombody pls hlp !!
I am not sure yet on all your errors, but you do have debugging enabled on your phone?
---------- Post added at 03:16 AM ---------- Previous post was at 03:15 AM ----------
no need for two threads
You really need to give a bit more info. It looks like your PC isn't seeing your phone. This could be due to a number of reasons, including wrong driver, bad usb cable, phone not set up correctly (adbd not started), etc...
What exactly have you done? From what you've posted I've no idea if you phone is even hooked up with a cable...
OP, go into Device Manager on your PC with your N1 plugged into USB. Is there a yellow warning triangle with an exclamation point next to the entry for ADB Device/Nexus one?
On Windows 7 i've always had to install N1 drivers manually from a package i found here:
http://forum.xda-developers.com/showthread.php?t=613217
So I downloaded and installed the Motorola drivers from there website... Motorola Device Manager
Unfortunately when I plug in the D3 to my computer and windows goes to install the appropriate drivers, the USB mass storage install fails. The other two, can't recall the names right now, are successful. I have tried while with and without enabling mass storage on the device
Any tricks to get it to stick? The D3 isn't showing up in windows device manager except for as a adb composition device
Sent from my Galaxy Nexus using xda premium
I've tried with and without USB debugging as well, with the phone in all of the optional modes. Several drivers install just fine except MTP USB device. Phones storage will not display nor will the memory card
Sent from my Galaxy Nexus using xda premium
you could try just installing the drivers, links in my list
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
Sent from my XT862 using xda premium
I'd much prefer to have the drivers without the Motorola software.
I will give it a go when I return home and can get the gf to let me try again
Thanks for the link
Sent from my Galaxy Nexus using xda premium
I went through your links and saw that you have Motorola_end_user_something drivers version 5.4.
I tried the 64 bit variant from the zip because I have a 64bit windows 7 laptop. Installs all drivers except the mtp USB mass storage
Thanks for the link, however, I saw a video someone showed using the "latest" being version 5.5
I can't find em for the life of me, any further assistance is greatly appreciated
I can't run motofail successfully following directions to the letter and watching a video.
I'm no noon to android, just Motorola devices and its being a pain in the arse!
Sent from my Galaxy Nexus using xda premium
I rebooted computer and phone and came back and all is good in the android world again. thanks for the file and the help!
great, rebooting is often a forgotten step
Same issue- but Nothing works!
sd_shadow said:
you could try just installing the drivers, links in my list
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs....
Click to expand...
Click to collapse
Hi, SD_Shadow!
I have the same problem. I have been looking everywhere on this site's forums for a solution, and I tried every single technique from your "Installing Drivers and Drivers Errors" section that you suggested. My computer (Windows Vista) will not connect with my Droid 3 (2.3.4).
When I plug in my Droid 3 with the USB, the only way anything will pop up on my cpu, is when I go into DLNA & choose "Share Media".
-Then a window will pop up stating "Found New Hardware" "Windows needs to install driver software for your Motorola Phone".
-I click on "Locate and install driver software (recommended)".
-Then it shows "Driver Software Installation" "Installing Device Driver Software" for a few seconds & another window pops up:
-"Found New Hardware- Motorola Phone" "Insert the disc that came with your Motorola Phone"
-I am forced to choose the option "I don't have the disc. Show me other options"
-Which leads me to the next window that says "Windows couldn't find the driver for your device" & offers two options to click:
-"Check for a Solution" and "Browse my computer for driver software (advanced)"
1. I have already went through both of these options and still no luck.
2. I have tried all your recommended techniques in your Sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... (P.S. when I had attempted the last option in the "Installing Drivers and Drivers Errors" section with the .rar file, I extracted the file using 7zip, which I already had on my cpu)
3. I have tried uninstalling & reinstalling the Motorola Device Manager (all it does is search for a new update & nothing else)
4. I have also tried rebooting my computer which has not helped this situation either
If there is anything any of you OP's can come up with for me, I'd greatly appreciate it! I tried to include as much detail as possible on here so hopefully it will make it easier to find a solution. My intentions once my phone is connected to my cpu like it should be, is to root my phone using Motofail. As you can see, I cannot accomplish the root until my cpu recognizes my device! :crying:
try
connect droid 3 to pc, open device manager (start>control panel>Hardware and sound)
find the droid 3 select uninstall and check delete the driver for this device
disconnect droid 3, then reconnect, then use the Browse my computer for driver software option
find the moto diver folder should have placed it in C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
Still no luck!
sd_shadow said:
try
connect droid 3 to pc, open device manager (start>control panel>Hardware and sound)
find the droid 3 select uninstall and check delete the driver for this device
disconnect droid 3, then reconnect, then use the Browse my computer for driver software option
find the moto diver folder should have placed it in C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
Click to expand...
Click to collapse
Hello!
Thanks for getting back with me. I did exactly what you suggested, & still nothing.
After clicking "Browse my computer for driver software (advanced)"
The next window stated "Windows was unable to install your Motorola Phone"
Also, the first time, when I posted on here & said I tried both of the options:
"Check for a Solution" and "Browse my computer for driver software (advanced)"
When I chose the 2nd option, I had already chosen C:\Program Files\Common Files\Motorola Shared\Mobile Drivers but this was my result that time too. I went ahead with the process in your response, but I got the same result.
Any other ideas?
Thanks again!
how is the droid 3 listed in device manager?
sd_shadow said:
how is the droid 3 listed in device manager?
Click to expand...
Click to collapse
When going through "Device Manager":
Start>Control Panel>Hardware and Sound>Device Manager
My device is listed as "Motorola Phone"
What seems weird to me, though, is when going through "Connect to":
Start>Connect to>View Network Computers and Devices
My device is listed as "Droid 3"
This may be irrelevant, or it may be helpful, but since I had noticed the difference, I thought I'd mention it.
on the phone's top bar/notification bar, it should have a usb icon
if you pull the top bar down should see 4 options
pc mode
windows media sync
usb mass storage
charge only
which one is selected?
sd_shadow said:
on the phone's top bar/notification bar, it should have a usb icon
if you pull the top bar down should see 4 options
pc mode
windows media sync
usb mass storage
charge only
which one is selected?
Click to expand...
Click to collapse
I had someone that looked for this option, & they couldn't find it. The only way we could get anything to pop up on the cpu when plugging in my phone with the USB, was when I turned on "Share Media" in the DLNA.
When I just simply plug my phone into the cpu with the USB, it only charges & does not give any options otherwise. Nothing pops up on my phone or the cpu when doing this. It would've been so simple if my phone gave the options you listed!
Jamie840 said:
I had someone that looked for this option, & they couldn't find it. The only way we could get anything to pop up on the cpu when plugging in my phone with the USB, was when I turned on "Share Media" in the DLNA.
When I just simply plug my phone into the cpu with the USB, it only charges & does not give any options otherwise. Nothing pops up on my phone or the cpu when doing this. It would've been so simple if my phone gave the options you listed!
Click to expand...
Click to collapse
even if drivers are not installed, phone should show a usb connection.
Is Share Media" in the DLNA. still on? if so turn off
and delete Droid 3 device driver in device manager
other things to try
different usb port rear ports are often better than front
different usb data cable
different pc
sd_shadow said:
even if drivers are not installed, phone should show a usb connection.
Is Share Media" in the DLNA. still on? if so turn off
and delete Droid 3 device driver in device manager
Click to expand...
Click to collapse
I know, it's strange. Like I said, it only shows that it's charging when connected to the cpu with the USB. It does not show anything like you had described during USB connection.
I turned off "Share Media" in the DLNA & deleted Droid 3 in Device Manager, before, when you had suggested:
sd_shadow said:
try
connect droid 3 to pc, open device manager (start>control panel>Hardware and sound)
find the droid 3 select uninstall and check delete the driver for this device
disconnect droid 3, then reconnect, then use the Browse my computer for driver software option
find the moto diver folder should have placed it in C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
Click to expand...
Click to collapse
& to the second half of your response...
sd_shadow said:
other things to try
different usb port rear ports are often better than front
different usb data cable
different pc
Click to expand...
Click to collapse
I was using the USB ports in the front, so I will try the ones in the back.
If this doesn't work, I will then see if I have another USB cable, and try that.
If those don't work, I will see if I can use someone else's cpu.
Also, I'll let you know how it goes- just in case anyone ever has the same issue- since these forums have been so helpful to me with different things. Thanks again for your time!
ok copied moto drivers from my Vista laptop, and uploaded to http://d-h.st/6VJ
same directions as before
download<unzip to C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
open device manager>select droid 3>update driver
Browse my computer>browse Computer>local disc C>program files>\Common Files\Motorola Shared\Mobile Drivers\Drivers
but if phone is not showing usb connection, don't think it will work.
probably should delete old C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers folder, before moving new files
---------- Post added at 11:38 PM ---------- Previous post was at 10:55 PM ----------
not sure what happened, but the first copy of moto drivers for Vista was incomplete
reuploaded http://d-h.st/6VJ
My pc windows 7 installed google nexus adb interface once i plugged in my nexus 6 but dosent show up in devices with removable storage or pop up open file once plugged in. I checked in the device and printer area and see the nexus 6 under unspecified section. Im stuck please help me figure this out
MrJesseJay said:
My pc windows 7 installed google nexus adb interface once i plugged in my nexus 6 but dosent show up in devices with removable storage or pop up open file once plugged in. I checked in the device and printer area and see the nexus 6 under unspecified section. Im stuck please help me figure this out
Click to expand...
Click to collapse
I had no issues and used the latest Google USB drivers which aren't hard to find.
You could also try using Wug's Toolkit I believe it will also install all the necessary divers for everything to work 100%
turn off USB Debugging.
Uninstall the Drivers through Device Manager.
Unplug and then plug back in.
It should install the Nexus 6 drivers.
Did all these methods still no good. Does with my PC have to connected to the internet or something?
MrJesseJay said:
Did all these methods still no good. Does with my PC have to connected to the internet or something?
Click to expand...
Click to collapse
my computer and drivers just dont mix. i used most everything in this link to flash the drivers and more, flawless
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Switch the USB connection from MTP to camera. Then drop anything you wanna drop from your computer in the " picture " folder that your PC picks up from the phone. Then with a file explorer move your contents to wherever you wanna move them in your phone
---------- Post added at 06:36 PM ---------- Previous post was at 06:35 PM ----------
It's a workaround
In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.
vgdoc said:
In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.
Click to expand...
Click to collapse
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.
Hi, I run into the same issue on win 10 and also installed the android sdk. however, I only can see driver version 11 or an unsigned version 7, both are not working for me.
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
stefipant said:
Hi, I run into the same issue on win 10 and also installed the android sdk. however, I only can see driver version 11 or an unsigned version 7, both are not working for me.
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Click to expand...
Click to collapse
You still have problem, unlocking your device?
Sent from my Xiaomi Mi 5 using XDA Labs
vgdoc said:
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.
Click to expand...
Click to collapse
May I ask where you downloaded sdk tools and which file you used to manually update the driver? I have the same problem you had earlier. I'm using Windows 10 if that makes a difference.
abelmaster said:
May I ask where you downloaded sdk tools and which file you used to manually update the driver? I have the same problem you had earlier. I'm using Windows 10 if that makes a difference.
Click to expand...
Click to collapse
Common error.. Use sdk from ADT.. Or just use minimal adb and fastboot
Sent from my Xiaomi Mi 5 using XDA Labs
harish15 said:
Common error.. Use sdk from ADT.. Or just use minimal adb and fastboot
Click to expand...
Click to collapse
For me fastboot doesn't work, it doesn't show any device connected when I use minimal adb and fastboot, that is why I am searching for another solution.
So how do you suggest to get the right drivers with sdk from ADT? Where should I download it and how can I manually update the driver to the drivers included in this sdk?
abelmaster said:
For me fastboot doesn't work, it doesn't show any device connected when I use minimal adb and fastboot, that is why I am searching for another solution.
So how do you suggest to get the right drivers with sdk from ADT? Where should I download it and how can I manually update the driver to the drivers included in this sdk?
Click to expand...
Click to collapse
https://dl.google.com/android/installer_r24.4.1-windows.exe
Download and install this. Choose google usb driver and install package.
Then connect in fastboot mode and in the device manager update driver manually(let me choose update) and install version 9 driver.
Reboot your system and try unlocking again.
vgdoc said:
https://dl.google.com/android/installer_r24.4.1-windows.exe
Download and install this. Choose google usb driver and install package.
Then connect in fastboot mode and in the device manager update driver manually(let me choose update) and install version 9 driver.
Reboot your system and try unlocking again.
Click to expand...
Click to collapse
Thanks for posting your link, this helps me find it quick. Now one last question (I hope . Where can I find/download the version 9 driver?
"Google USB driver" in the SDK tools application. That is the version 9 driver.
vgdoc said:
"Google USB driver" in the SDK tools application. That is the version 9 driver.
Click to expand...
Click to collapse
When I type SDK tools application into windows menu bar nothing pops up, so i guess you mean the android sdk manager?
{
"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"
}
But where in the SDK manager can I "google" (or do you mean "search") for something?
In SDK manager did you install tools > Android sdk tools and tools > Android sdk platform-tools ?
If not try to install them, then check you can detect your device with adb tools :
connect your phone with usb
windows key + r
in prompt enter cmd
go to your adroid sdk platform-tools directory with "cd" command
then type "adb devices"
Your device should be find
Here an example :
Code:
cd /D F:\android\sdk\platform-tools
F:\android\sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
74a9b5b5 device <<<<<<<<<<<<<<<<<<<
If you do not see your device there is something wrong, try to install this pack from xda :
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
It worked for me.
If it still not work after installation usb driver from xda have a look in the miFlashunlock log directory, open the MiFlashUnlock.log file and check the error.
What helped me was to
- get to the 50% error
- uninstall the kedacom USB device (remove drivers)
- restart miunlocker
- miumlocker would reinstall the driver
- the connection would work, but only once. If there is another error after 50%, you will have to remove/reinstall driver again.
Wasted a lot of time on that, they really should work on the quality of their software. I get the security concerns, but fastboot oem unlock is so much better.
I'm convinced it's impossible.
I've done a clean install of all the drivers (either via SDK or the minimal adb packs), tried doing what crim did... Still stuck on 50% error. Mind boggling stuff.
vgdoc said:
In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.
Click to expand...
Click to collapse
same problem guys plz help me
---------- Post added at 02:43 AM ---------- Previous post was at 02:04 AM ----------
dkmsn8 said:
same problem guys plz help me
Click to expand...
Click to collapse
ok i did it guys thanks
Crim Soukyuu said:
What helped me was to
- get to the 50% error
- uninstall the kedacom USB device (remove drivers)
- restart miunlocker
- miumlocker would reinstall the driver
- the connection would work, but only once. If there is another error after 50%, you will have to remove/reinstall driver again.
Wasted a lot of time on that, they really should work on the quality of their software. I get the security concerns, but fastboot oem unlock is so much better.
Click to expand...
Click to collapse
I dont know why this worked, but it did. Finally! I tried this method a couple of times and the fourth time it works. Have to say that mi unlock did not install the driver for me, I searched for it online with the built in windows driver update. It gave me the kedacom one again, but it worked!
vgdoc said:
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.
Click to expand...
Click to collapse
hello, i am a chinese mi5 user and i get the same problem with you when i unlock my mi5 at first. and this problem almost spends me 2 whole days to solve it.i searched many webs and i found many other mi5 users had this problem. i do all the procedures that the official posts and others suggested again and again and it helps nothing. in the end, i solved it. i believe you did not bind your account with your phone after your login your account.i cant say where to type that option(i mean bind your accout with your phone) because i am using aosp now.your should try to find that option in miui and type that option,then you will solve this problem.sorry for my bad english and i hope you can understand what i wanna express. good luck.
---------- Post added at 01:16 PM ---------- Previous post was at 01:13 PM ----------
eros1on said:
hello, i am a chinese mi5 user and i get the same problem with you when i unlock my mi5 at first. and this problem almost spends me 2 whole days to solve it.i searched many webs and i found many other mi5 users had this problem. i do all the procedures that the official posts and others suggested again and again and it helps nothing. in the end, i solved it. i believe you did not bind your account with your phone after your login your account.i cant say where to type that option(i mean bind your accout with your phone) because i am using aosp now.your should try to find that option in miui and type that option,then you will solve this problem.sorry for my bad english and i hope you can understand what i wanna express. good luck.
Click to expand...
Click to collapse
and i believe other guys with this problem can also solve it via this method.
i solved it by;
1.disable internet coonection cause of auto update driver
2.uninstall kedacom driver, select delete files.
3.update driver manually and select let me pick driver.
4. choose usb composite device than try "fastboot oem-devices" command .
if it shows your device. unlock wont be stuck at %50.
So thanks to the awful instructions on how to root the phone (https://forum.xda-developers.com/le-2/how-to/guide-unlocking-rooting-restoring-to-t3515555) my phone seems to be bricked now
I managed to get TWRP flashed. I format'ed Data, did a backup, and thats where it went wrong.
The instructions say to go to Mount > Enable MTP
There was no " Enable MTP" button. Just a "Disable MTP" button. I tapped it and it turned into "Enable MTP", I tapped that again. Nothing seemed to happen.
Since I couldn't do anything, I rebooted the phone with TWRP, and now it just sits at the "LeEco" screen forever.
when I plug the phone into the PC, ADB see's it but it is showing up as "unauthorized" and I cannot reboot into the bootloader. Google tells me I need to recheck the USC debugging option on the device, but apparently my device no longer can boot to the OS so I cannot check that option.
I can hold down Vol + and Power and get into the EUI Recovery, which says I can flash an update.zip or erase data. But when I do this, ADB doesn't see it at all, and Windows doesn't see it to put any files on it.
I've tried several drivers, none seem to make any difference. And as a side note, given that there are zillions of drivers out there, and having the exact correct ones seems pretty important, why in the world do these rooting guides not link to the correct one?
Any advice, or is it time to box it up and ship it back?
Is it boot in recovery
I can boot into recovery but it's the le Eco recovery. The directions killed the phone before TWRP was flashed.
So at this point I have the phone stuck at the Le Eco boot up screen.
I have the ADB driver installed, and adb devices shows the device, but it says "unauthorized".
there are 3 "Android Device" entries in my Device Manager with yellow exclamation points next to them. I have no idea which driver it is looking for. When I manually browse to the drivers, I get 3 options, "ADB interface, Bootloader interface, or Composite ADB interface"
I am unable to reboot into recovery via adb because the device is unauthorized
1. download the rom from this ppst:
https://forum.xda-developers.com/le-2/how-to/leeco-le-2-x520-stock-firmware-t3657689
2. Then unzip the rom and open the folder, make sure there are no spaces in the folder name and its parent folders.
3. Then youll find a file named multi-brush, with the extension '. Bat' change the extension to '.bat' i.e. remove the space.
4. Then power on the mobile while pressing vol-down and power button, to enter fastboot mode and connect it yo the PC.
5. Then double click this multi brush file and wait for it to finish.
Important, this will wipe all your data!!
It worked for me,simple and error free,only for snapdragon le2
---------- Post added at 01:18 AM ---------- Previous post was at 01:18 AM ----------
https://forum.xda-developers.com/le-2/how-to/repair-hard-bricked-phone-x52x-sd-t3648348
I had that problem with the enable mtp step. Turns out it's a driver issue. This is a rough guide as my pc isn't with me right now so i may have misremembered a step or two.
During that step with your phone connected,
Goto device manger
> android devices
> right click the driver there
> click update driver
> manual update
> "let me pick"
> you'll see some drivers listed, pick one that has either MTP or usb composite device in it's name.
> install it
> your phone should now show up as a storage device
> if not, on your phone disable then enable mtp.
If your phone doesn't show up on your system unplug and replug your phone, re enable MTP.
If it still doesn't work, repeat above steps and pick a different driver.
On another note, I'm pretty sure that you were supposed to authorize your system for usb debugging before starting the rooting process, which is why the steps in that post say you should boot into recovery through adb i.e to ensure your system is authorized.
---------- Post added at 11:35 PM ---------- Previous post was at 11:28 PM ----------
I should probably post this on the rooting thread as well… but I prolly won't, I excel at procrastinating.