If you're like me and own a mi410, and am an android tinkerer, then you have probably hunted down for the USB drivers for this device before, to go into ADB for some extra tinkering.
I present to you the spoils of my hunt.
USB Drivers
Tested to be working perfectly with my mi410, now able to ADB into the device and no more exclamation marks in my device manager
Enjoy :3
Hi,
Are these the same as the USB drivers on the huaweidevice.com site? Or are your drivers newer? Unfortunately, I can't include the link to the download page at huaweidevice.com because I don't have enough posts yet.
Thanks for your help.
Regards,
Jacko
I'm unsure, but these are essentially just drivers you can use for USB ADB connectivity.
It's more lightweight it seems than the one's huawei has, though if I had to put money on it, i'd say these are older.
Thanks for the prompt reply.
Googling for "HUAWEI Android Phones USB Driver" brings up the page as the first search result. It's only a 7MB download, so I thought it might be lighter than installing a suite.
Regards,
Jacko
Have you tried that though?
From what I remember, I was having difficulty finding USB drivers for this device, and I'm not sure if that one supports the u9000. I may be wrong though. If you're trying it out let me know.
I just installed it and ran "adb devices" and my device was shown, so it seems to be working.
Regards,
Jacko
I've tried a few other adb commands and they work. If there is any specific command you would like me to test this driver with, rather than potentially mess up your own setup by installing multiple drivers, please let me know.
Regards,
Jacko
If it works, it works. Functionality should be the same then. I've since upgraded though, and don't really need the drivers for them anymore :x
I m using same type of utility named Wondershare MobileGo. U think it installs the same drivers too?
not sure, just try to hook your device in, if it works it works, simple as that
USB drivers
Don't we have the USB drivers installed everytime we flash ROMs?
Because I can always do adb shell when my phone is connected to PC.
Or am I missing something?
N...ooooo, that's not true. It doesn't come with, you probably had something before that that worked as an adb driver.
It's the reason why I had to look for it isn't it? :|
USB drivers
I see.
If I get it right, what you're saying is adb drivers being installed is independent of our flashing of ROMs, ain't it?
Yes, they don't come hand in hand, though for the most part, unless you're using ADB commands, you don't really need ADB drivers.
But I don't remember installing adb drivers.
Or maybe it's just it, I just don't remember that I did install before.
Anyway, thanks man.
Some one have drivers for windows8...?
Related
sorry if this clutters up the forum for a bit, i promise to delete it when it dies.
i've recently started using adb when i flashed over to 5.0.2h. i followed the instructions in the tutorial and was able to use adb. 2 nights ago, i began doing more complicated commands (for me) and tried to push a .apk into /system/app.
i wasn't immediately successful but i eventually got it in there and decided to reboot my phone. after this reboot, however, i lost the use of adb. i tried upgrading to the usb drivers haykuro posted, uninstalling them and re-trying the old one, rebooting the computer, rebooting my phone and none of it works. i've since wiped my phone and flashed it with the latest h build from haykuro (thanks haykuro!) but that didn't work either. now i'm trying to see if the 1.5 sdk will work.
i was wondering if anyone would have an idea about what i should do next. should i reinstall adb? try it on another computer? another cable? it's not the worst loss in the world, my phone is fine and my usb cable still works in the conventional way. i even checked to see if i somehow lost root and i was able to get su on the terminal emulator. but i still want the use of adb for nandroid, if nothing else.
thanks in advance!
I had the same problem after flashing to the G rom. I couldn't get ADB to work but fastboot recognized my phone and I was able to flash back to my backup. First time I did a complete wipe before flashing, second time, no wipe, made no difference in either case for me
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
I just had the same problem, I had to update the driver and it is working fine now.
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
zer0day said:
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
Click to expand...
Click to collapse
Give me a few minutes I will find you a link for it.
jordanjf86 said:
Give me a few minutes I will find you a link for it.
Click to expand...
Click to collapse
Here it is. http://dl.google.com/android/android_usb_windows.zip after downloading this when you go to update your driver in device manager make sure to use this. Hopefully this will help it worked for me.
jashsu said:
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
Click to expand...
Click to collapse
yes, that's what it comes up as. and i've tried the usb drivers from haykuro's page and they didn't work before and after rebooting my computer.
i'm on vista and it wont accept the updated drivers. it downloads the standard removable memory drivers and wont let me update to anything else. anybody have any ideas
just installed the 1.5 apk and adb and it works again. for people running haykuro builds, i would suggest trying this if you have adb problems. just intall the 1.5 sdk as normal, copy adb.exe and AdbWinApi.dll into \system32 and you should be good.
unless requested i will delete this thread in two days. thanks everyone!
Hmm... i tried that and its still not working ):
Ive tried like 10 different USB drivers from various sites including this one, downloaded the 1.5 SDK and installed it, wen through several reboots and it always says either that the driver is for the wrong platform, the most up to date one is ALREADY installed (HTC Bootloader), or that Windows couldn't find any drivers.
Under ADB Interface in device manager is "%USB\VID_0BB4&PID0FFF.DeviceDescRelease%"
did you try and update the driver through the device manager? i've heard that it's the only way to update it for some people.
I had already Posted & Solved This Issue here : http://forum.xda-developers.com/showthread.php?t=493703
Go Check It, It ll work for sure....
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:
Hi
I actually replying about the bible quote you have mentioned? you into theology?
Since installing the Simply AOKP ICS ROM, I am assuming I need new drivers, but not sure. I found a newer ADB, and downloaded "usb_driver_r03-windows", and also USB drivers from Samsung. Neither are recognized as correct drivers for the phone.
Anyone have any suggestions?
I'm not sure which driver the first one you spoke of might be. You need to use the google driver (aka Nexus S Driver) to make adb work.
mrhaley30705 said:
I'm not sure which driver the first one you spoke of might be. You need to use the google driver (aka Nexus S Driver) to make adb work.
Click to expand...
Click to collapse
Thanks. I found it and have downloaded it, but not having success.
Of course, I think the old Samsung driver is installed. So, I plugged in the phone, went to Device Manager, and selected the Android phone to delete it.
When I plugged in the phone, it searched for drivers, and did not find them.
Any suggestions on how I proceed to get this driver installed? I did install it via
SDK Manager as instructed online.
[EDIT]
I just read through the Google docs again, and do see them saying it is in "<sdk>\extras\google\usb_driver\ directory". Searching now.
[EDIT2]
Thanks. That got me going.
So I know XDA is full of answers to this one, but it seems everyone either has some snarky comment like, "they won't check' or whatever. There are also some ok answers and tuts but some of it's confusing and a lot of the threads go off topic. So i'd like to ask, how do i get my phone back to stock? i have to mail my device back in for a warranty exchange as the speakers and camera stopped working suddenly.
My device is stock rooted, odex rom w/ TWRP. unlocked bootloader. Super CID and S-off. Tampered message gone in boot loader. My laptop runs Windows 8, which I'm having an issue getting the HTC manager to stay open for some reason, even after an uninstall/ reinstall of the manager and drivers. The drivers themselves seemed to have installed fine as my device is recognized as "my HTC" though when in fastboot, my comp will tell me the device is unrecognized. Using the stock usb plug that came with my phone and I've plugged in to both usb 3.0 and 2.0 ports. And yes, I do have ADB in the root of my computer, though I'm wondering if i need a different type of ADB since this is the one i used with windows 7 a while back..or does it matter?
I'd like to get things back to stock as much as possible and would be very appreciative. Thanks!
whitetiger_0603 said:
So I know XDA is full of answers to this one, but it seems everyone either has some snarky comment like, "they won't check' or whatever. There are also some ok answers and tuts but some of it's confusing and a lot of the threads go off topic. So i'd like to ask, how do i get my phone back to stock? i have to mail my device back in for a warranty exchange as the speakers and camera stopped working suddenly.
My device is stock rooted, odex rom w/ TWRP. unlocked bootloader. Super CID and S-off. Tampered message gone in boot loader. My laptop runs Windows 8, which I'm having an issue getting the HTC manager to stay open for some reason, even after an uninstall/ reinstall of the manager and drivers. The drivers themselves seemed to have installed fine as my device is recognized as "my HTC" though when in fastboot, my comp will tell me the device is unrecognized. Using the stock usb plug that came with my phone and I've plugged in to both usb 3.0 and 2.0 ports. And yes, I do have ADB in the root of my computer, though I'm wondering if i need a different type of ADB since this is the one i used with windows 7 a while back..or does it matter?
I'd like to get things back to stock as much as possible and would be very appreciative. Thanks!
Click to expand...
Click to collapse
if your problem is adb have you tried to add it in the "Environment Variables" ?
have you enabled USB debugging in your phone ?
i have windows 8 too and i don't have this kind of problem
I use windows 8 and it has mostly been trouble free for me. However I did have problems with my laptop recognising my phone when in recovery. It eventually worked on it's own but I found this after:
http://forum.xda-developers.com/showthread.php?t=2232799
Maybe try installing the windows 8 drivers above.
Ardmanz said:
I use windows 8 and it has mostly been trouble free for me. However I did have problems with my laptop recognising my phone when in recovery. It eventually worked on it's own but I found this after:
http://forum.xda-developers.com/showthread.php?t=2232799
Maybe try installing the windows 8 drivers above.
Click to expand...
Click to collapse
Yeah i saw that thread, but my phone was already showing up in devices. It just won't be recognized in bootloader or fastboot.
whitetiger_0603 said:
Yeah i saw that thread, but my phone was already showing up in devices. It just won't be recognized in bootloader or fastboot.
Click to expand...
Click to collapse
Mine was recognised everywhere (including recovery). I'd get the beep from windows 8 and the driver would initialise but it wasn't recognised by adb.
If you haven't tried installing the above drivers yet it certainly wouldn't hurt to try.
Ardmanz said:
Mine was recognised everywhere (including recovery). I'd get the beep from windows 8 and the driver would initialise but it wasn't recognised by adb.
If you haven't tried installing the above drivers yet it certainly wouldn't hurt to try.
Click to expand...
Click to collapse
I gave it a shot while in bootloader. Thanks tons. Just a question though, my cope recognizes my phone however when i input "adb devices" in CMD, nothing shows up. Just wondering if that is an issue before i continue.
Rayskull said:
if your problem is adb have you tried to add it in the "Environment Variables" ?
have you enabled USB debugging in your phone ?
i have windows 8 too and i don't have this kind of problem
Click to expand...
Click to collapse
I glanced at something about the environmental variables but i can't find it again. Yeah i have all the correct settings marked to do this
Hi Team,
I feel like I'm pretty close to being able to root this thing. Never used ADB, telnet, or any of the other random things I've spent several days reading about, but I think I've got it lined up to give it a shot.
I wish I could do this on my mac, but it seems the MotoWpNoMo step requires a PC. I do have an old laptop running xp (sp3), so for that step I'll use it. Unfortunately I can't seem to get the drivers to work. I've installed the motorola device manager's newest incarnation and still no luck getting it to pick up my device.
Any advice on how to get windows XP to recognize my device?
motoxuser said:
Hi Team,
I feel like I'm pretty close to being able to root this thing. Never used ADB, telnet, or any of the other random things I've spent several days reading about, but I think I've got it lined up to give it a shot.
I wish I could do this on my mac, but it seems the MotoWpNoMo step requires a PC. I do have an old laptop running xp (sp3), so for that step I'll use it. Unfortunately I can't seem to get the drivers to work. I've installed the motorola device manager's newest incarnation and still no luck getting it to pick up my device.
Any advice on how to get windows XP to recognize my device?
Click to expand...
Click to collapse
what do you mean by your computer won't pick up your device.
like when you plug in your device nothing happens no driver's start to install or on your phone does it say USb debugging enabled or MTP.
or when you computer trys to install the drivers it fails.
if you not getting anything at all when you plug your phone in i would try a different USB port if still nothing then i would try a different USB cable
if you are having issues getting the drivers to install you can try downloading the Moto X toolkit, it has a option to download the drivers plus it also comes with ADB and everything else in the folder it installs to.(location is C:/Program Files/stillthisguy)
here is the link for the Toolkit for PC
http://forum.xda-developers.com/showthread.php?t=2477132
ToolKit for Mac
http://forum.xda-developers.com/showthread.php?t=2591875
hey that got it - the toolkits are great. thanks!:good:
motoxuser said:
hey that got it - the toolkits are great. thanks!:good:
Click to expand...
Click to collapse
no problem man glad it got it up and running
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
AlkaliV2 said:
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
Click to expand...
Click to collapse
So, I've been on stock until I switched over to CM12. I do have a twrp backup but apparently only did that after I moved to CM12. I have only the most basic (read basically nonexistent) understanding of ADB, and can follow directions I find online but no real knowledge as to how anything works. I also did not use wugfresh, but unlocked via ADB and rooted via chainfire. Honestly, I followed most of the direction I found on youtube via a creator called wwjoshdo (I'd link but I'm not allowed).
Otherwise that feels like the info. I didn't fiddle with my nexus until I started have battery issues and then decided to unlock/root/flash, and that was about 6 weeks ago. I'm also running what standard apps for a rooted device on CM12, flashify, cyandelta, setcpu, and, Titanium Backup. Help?
llawhsoj said:
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
Click to expand...
Click to collapse
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
RMarkwald said:
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
Click to expand...
Click to collapse
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
llawhsoj said:
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
Click to expand...
Click to collapse
So this link will get you up and running with ADB (if it isn't already working): http://forums.team-nocturnal.com/index.php?/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10-updated-9-11-2015/
These are the most common commands that are used with ADB once you get it installed. Also, an excellent way to pull a log from the command prompt: http://developer.android.com/tools/help/shell.html
Assuming you can see the device once you pass the command, "adb devices" it means you are connected but the MTP driver hasn't been loaded properly. I had to fix this by cycling Android debugging and ADB notification in developer's option until Windows was like, "Hey! There it is!" Also, MTP works properly for me when booted into TWRP so if you desperately need to transfer a file you can do it from the TWRP recovery menu.
Noob Tip/Reminder: Make sure that when you plug it in the first time you change it from 'Charge Only' to MTP and if things still seem quirky reboot Windows. It's all just a game of getting it recognized at this point.