Hello Everyone,
I'm trying to get ADB to communicate with my new V10 and I'm having a hard time getting the device to come up (using adb devices -l).
I have followed the instructions to enable the Developers Options setting on the phone, gone into DO and check off the Boolean for USB Debugging. When I connect the phone to the computer it recognizes it as a "Portable Device" and not the ADB device needed for ADB.
Here's what I've tried so far:
Install Andriod Studio - Downloaded the latest version of Andriod Studio. Installed it, ran the SDK Manager, and installed the Google USB Driver. Repeated this installation on 3 separate workstations (Windows 10 Pro, Windows 8.1 Enterprise, and Windows 7 Pro). All 3 recognize the phone as a Portable Device only.
Is there anything else I should look at in order to get ADB to work. I'm not an Android Expert, but I have successfully gotten ADB to work with my prior 2 phones (LG G2X and Samsung Galaxy S4).
Thank you for taking to time to look this over,
- Space
Download the drivers for the LG G4,did you do that? Also, I searched xda for "adb drivers" and you can find the thread with adb and fastboot drivers instead of the sdk. You can install them system wide, which IMHO makes it a little easier.
Sent from my LG-H901 using Xparent Skyblue Tapatalk 2
I had a similar issue and fixed it by using pdaNet (I believe that's what it's called) to install the drivers and I also had to change the way the phone behaved when plugged in (the popup on the phone when you connect via usb).
Warrior1975 said:
Download the drivers for the LG G4,did you do that? Also, I searched xda for "adb drivers" and you can find the thread with adb and fastboot drivers instead of the sdk. You can install them system wide, which IMHO makes it a little easier.
Sent from my LG-H901 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Thank you! Don't know why I didn't start searching for the G4 drivers. Was able to google them, find them for download, install them and get ADB to recognize my device.
Related
Hi!
I keep reading that the driver shows ASUS Android Composite ADB Interface but mine shows Transformer Prime TF201 instead.
I have been able to root, unlock and flashed TWRP.
Before flashing Roms I want to install NVFLASH but I am worried that my driver is not showing that ASUS Android Composite ADB Interface name.
I tried updating as I have read but whenever I select the folder with the drivers I want I get the message that Windows has determined that my software is up to date...
Every time I try to select the folder with the drivers I get "the folder you specified doesn't contain a compatible driver"
Any idea?
UPDATE: I used the other option to install drivers and selected the ASUS Android Composite ADB Interface from a list and it installed it. I am able to access my files on the phone.
Is there a way to test fastboot and adb to make sure I am good to try nvflash?
This is Windows 7 64bit
shaolin95 said:
UPDATE: I used the other option to install drivers and selected the ASUS Android Composite ADB Interface from a list and it installed it. I am able to access my files on the phone.
Is there a way to test fastboot and adb to make sure I am good to try nvflash
Click to expand...
Click to collapse
I always test the connection using the commands "adb devices" or "fastboot devices", it will tell you if any devices are connected.
You could also push a small file to the tab (eg. baba.txt with "adb push baba.txt /sdcard/") and find it on your tab, just to make certain.
Are you using Universal Naked Drivers? Asus ones suck...
http://forum.xda-developers.com/showthread.php?p=20995229
Striatum_bdr said:
Are you using Universal Naked Drivers? Asus ones suck...
http://forum.xda-developers.com/showthread.php?p=20995229
Click to expand...
Click to collapse
I am not but I can sure try those.
But before I do, if the test passes then it I should be fine with the current drivers?
I am done with nvflash!
I followed this video to do it in case someone has the same issues
http://www.youtube.com/watch?v=J3ypzUaKxvo
CODE 10 on all 5 naked adb drivers
No matter which I choose i get told that they cannot start. I have tried all 5 options in the naked set to no avail. this is a windows 7 ultimate pc. I am trying to fix my tf201 as it just keeps looping to a TWRP screen and gives me the key driver missing message
Hey XDA I got my DNA the day it was released and love it. I am a creature of habit though so i want to root it like my past dinc2. I am running into a problem though. the command
Code:
adb devices
doesn't return my device. when i type in
Code:
fastboot devices
my phones serial number comes up, like it should. Fastboot works but ADB doesn't. I am trying to do JCase's Bootloader Exploit. I have the drivers installed, environment variable path set to my adb/fastboot location, and java sdk and android sdk all installed. I know ADB doesnt recognize it in the fastboot menu, just the beginning menu so that's what I'm doing. How can i get ADB to recognize my device like fastboot does.
Here's what I'm getting:
Code:
C:\And-sdk\platform-tools>adb devices
List of devices attached
C:\And-sdk\platform-tools>fastboot devices
FA2BBS500706 fastboot
Any help is greatly appreciated!!
Um, do you have usb debugging enabled.
Sent from my HTC6435LVW using xda app-developers app
termin8tor22 said:
Hey XDA I got my DNA the day it was released and love it. I am a creature of habit though so i want to root it like my past dinc2. I am running into a problem though. the command
Code:
adb devices
doesn't return my device. when i type in
Code:
fastboot devices
my phones serial number comes up, like it should. Fastboot works but ADB doesn't. I am trying to do JCase's Bootloader Exploit. I have the drivers installed, environment variable path set to my adb/fastboot location, and java sdk and android sdk all installed. I know ADB doesnt recognize it in the fastboot menu, just the beginning menu so that's what I'm doing. How can i get ADB to recognize my device like fastboot does.
Here's what I'm getting:
Code:
C:\And-sdk\platform-tools>adb devices
List of devices attached
C:\And-sdk\platform-tools>fastboot devices
FA2BBS500706 fastboot
Any help is greatly appreciated!!
Click to expand...
Click to collapse
having the same issue. I can issue commands through fastboot and ADB commands when I'm in recovery but not when my phone is fully booted.
Try going into slept dev. settings turning adb debugging off then back on
Sent from my HTC6435LVW using xda premium
@Bigandrewgold:
Its really bugging me. All Google says is "ADB works, Fastboot doesn't" and that's the opposite of our problem!!!
@Chyrux:
Um, do you have usb debugging enabled.
Click to expand...
Click to collapse
yes, usb debugging is enabled, has been (I'm not that dumb haha).
@starscream86:
Try going into slept dev. settings turning adb debugging off then back on
Click to expand...
Click to collapse
Not sure what "slept dev. settings" is (typo maybe??). I have on/off'd dev settings and check/unchecked usb debugging a alot of times to no success.
Here's the cure all....I'm assuming you have the lastest SDK and have yor ADB folder set to something simple like C:\ADB and I'm also assuming you are running Windows
I had the same issue ....initially I had no issue in ADB and I was able to do the CIG change and unlock on HTC Dev..but later on I installed HTC sync drivers and from then on no matter what I did only fastboot commands worked in recovery...ADB did not in recovery or when my phone was running normal.
So...uninstall all htc SYnc and driverin programs/features on oyur laptop...reboot your laptop. on the laptop download and instal PDANet 3.50 (its free). it will prompt you to connect your phone and will install a proper driver (and also throw the pda net 3.50 program on your phone). Once you have successfully installed it, ADB should work perfectly for you.
bakemcbride21 said:
Here's the cure all....I'm assuming you have the lastest SDK and have yor ADB folder set to something simple like C:\ADB and I'm also assuming you are running Windows
I had the same issue ....initially I had no issue in ADB and I was able to do the CIG change and unlock on HTC Dev..but later on I installed HTC sync drivers and from then on no matter what I did only fastboot commands worked in recovery...ADB did not in recovery or when my phone was running normal.
So...uninstall all htc SYnc and driverin programs/features on oyur laptop...reboot your laptop. on the laptop download and instal PDANet 3.50 (its free). it will prompt you to connect your phone and will install a proper driver (and also throw the pda net 3.50 program on your phone). Once you have successfully installed it, ADB should work perfectly for you.
Click to expand...
Click to collapse
This didn't work for me... PDANet gave me error 103 when i connected my phone. I have uploaded the image.
termin8tor22 said:
This didn't work for me... PDANet gave me error 103 when i connected my phone. I have uploaded the image.
Click to expand...
Click to collapse
yeah, whatever Windows or other HTC driver you have that install for thephone is still on the laptop and that will conflict when installing.
You get PDANet to install successfully your ADB will come back.
In your programs and features make sure HTC SYnc AND HTC Drivers are unisntalled.
No idea if Windows 8 is more of a pain..I'm still on 7
before anything else, make sure your sdk is updated to an ics or later level
i just update the sdk whenever google pushes an update
I'm on 7 as well. How can I uninstall the drivers for good, like to the point where its like the first time I'm connecting my phone to pc again
Sent from my HTC6435LVW using xda app-developers app
termin8tor22 said:
I'm on 7 as well. How can I uninstall the drivers for good, like to the point where its like the first time I'm connecting my phone to pc again
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
With your phone not attached..
Control Panel- Programs Features...when I had HTC Sync installed I had to uninstall that AND the program entry for HTC Drivers as well.
You can then also use USBDeview..sort/toggle by Last Plug/Unplug and uninstall any Android drivers you see which could be conflicting.
Reboot, Install PDA Net and attach the phone when prompted. Also accept the driver even though you get the warning that it isn;t digitally signed from JuneFabrics.
This didn't work I'm still getting error 103 Android Device not found
Update:
I got Pdanet installed via putting the phone into fastboot mode and installing Pdanet on the computer.
I did notice that when im in fastboot my Android adb interface (in device manager) popped up but when I left fastboot mode and went to the bootloader my Android adb interface went away, this may be my issue with adb devices not working i think...
Sent from my HTC6435LVW using xda app-developers app
i am currently having this same issue. i did as you did and went to usbfastboot loader and tried installing pda net. i also saw the same adb device pop up but my install is stuck at installing pdanet phone and not moving. did you leave it in fastboot mode or did you reboot back?
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
It sounds like the waiting for device message with fastboot it because you're in bootloader (hboot) instead of fastboot maybe. You want to uninstall the HTC sync program, it's used because it installs the drivers then you get rid of the program itself or at least make sure it's not running at startup and when you connect the device. On Windows 8 did you disable the driver signature verification yet?
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
It sounds like the waiting for device message with fastboot it because you're in bootloader (hboot) instead of fastboot maybe. You want to uninstall the HTC sync program, it's used because it installs the drivers then you get rid of the program itself or at least make sure it's not running at startup and when you connect the device. On Windows 8 did you disable the driver signature verification yet?
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same result in fastboot, I'll try uninstalling HTC sync and disabling driver signature verification now and see how it goes
edit: same result, adb devices comes up empty when in fastboot after disabling driver signature verification and uninstalling HTC sync
It should be "fastboot devices" as the command.
Does your computer have native USB 3?
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
It should be "fastboot devices"
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
that returns nothing it just starts a new command line.
and two of the ports are usb 3.0 one is 2.0, I've tried all three
Use the snip tool in windows to grab a screenshot of the command window stretched out to show the history, that may point me in the right direction. Do a search for Windows 8 ADB and Fastboot driver installation (i prefer Google and prefix the search with "site: www.xda-developers.com" no quotes) and you should find a thread with the steps for installing the drivers properly after signature verification is disabled in Windows 8. I used it to remotely fix a user's computer with the same issue you're having but I'm mobile at the moment. I'll help you get it straightened out though that's kind of my specialty. I'm about to go get something to eat, I'm working on a migraine and when I get back I'll check back in. Feel free to PM me if you want while waiting on input from others also.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
Use the snip tool in windows to grab a screenshot of the command window stretched out to show the history, that may point me in the right direction. Do a search for Windows 8 ADB and Fastboot driver installation (i prefer Google and prefix the search with "site: www.xda-developers.com" no quotes) and you should find a thread with the steps for installing the drivers properly after signature verification is disabled in Windows 8. I used it to remotely fix a user's computer with the same issue you're having but I'm mobile at the moment. I'll help you get it straightened out though that's kind of my specialty. I'm about to go get something to eat, I'm working on a migraine and when I get back I'll check back in. Feel free to PM me if you want while waiting on input from others also.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you for the help, I hope this is all you need from the command window. I'm trying the adb and fastboot driver installation thread that you suggested now, hopefully this will have it resolved by the time you get back.
edit: unfortunately that didn't work, it said that the driver is already up to date. The phone shows up as "My HTC" under android USB devices already, even when in the bootloader/fastboot, but it shows the device status as "This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I just have some extra things in the folder like some ROMs/recoveries but I don't think that would matter. I have adb.exe, fastboot.exe, and the two .dll's so I think I have everything I need.
And I tried fastboot reboot while in fastboot, I got waiting for device in command prompt. Also when I entered the command I got a "USB device not recognized" popup from the taskbar. Device manager shows the phone as My HTC with a yellow caution triangle on the icon and the device status "This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
That's usually the result of using a USB 3.0 port, do you have a different set of ports you can try? Like back of the computer instead of front, side of notebook to back of notebook etc. Most motherboards have a USB 2.0 hub and USB 3.0 hub but the manufacturers don't make it obvious which is which in most cases. Also make sure antivirus and such is turned off while you're testing. Its one of those things that's just a tad bit off such as the ports or a driver.
Let me know how the above turns out and tomorrow if you want I can hop on teamviewer and we can try uninstalling what's there, starting fresh with the Google sdk and go from there.
PS- Sorry I haven't had a more direct answer I know it can be frustrating with so much trial and error and it being almost working. But I promise I'll stick with it until we get something figured out, or you get mad and remotely smack me over the head with a keyboard.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
That's usually the result of using a USB 3.0 port, do you have a different set of ports you can try? Like back of the computer instead of front, side of notebook to back of notebook etc. Most motherboards have a USB 2.0 hub and USB 3.0 hub but the manufacturers don't make it obvious which is which in most cases. Also make sure antivirus and such is turned off while you're testing. Its one of those things that's just a tad bit off such as the ports or a driver.
Let me know how the above turns out and tomorrow if you want I can hop on teamviewer and we can try uninstalling what's there, starting fresh with the Google sdk and go from there.
PS- Sorry I haven't had a more direct answer I know it can be frustrating with so much trial and error and it being almost working. But I promise I'll stick with it until we get something figured out, or you get mad and remotely smack me over the head with a keyboard.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm pretty sure I was using the 2.0 port but I could be wrong. I'll keep working on it and if I can't resolve it I'd love to try teamviewer wth you. Thank you so much for all the help so far.
Finally got it working, kept trying on my old computer that I unlocked it originally with and eventually it just decided to recognize it and worked.
Thanks so much for the help getting to this point.
kalbany said:
I'm pretty sure I was using the 2.0 port but I could be wrong. I'll keep working on it and if I can't resolve it I'd love to try teamviewer wth you. Thank you so much for all the help so far.
Click to expand...
Click to collapse
I
Is there an error information, e.g: Windows code 10.
If yes, I googled it, it shows:
The error message probably occurs when you are trying to use a particular piece of hardware, such as a USB connected device or internal DVD drive. Take note of the device you are using when the error occurs in order to update the correct drivers.
error.info/windows/driver-10.html
Cheers,
Lun:
kalbany said:
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
Click to expand...
Click to collapse
I have Started a thread for HTC Droid Incredible phones in the troubleshooting area. Im having the same exact problem and im running Windows
as soon as i do the command: fastboot oem get_identifier_token, it just sits there and waits. and then i get a pop up from the system tray saying that my device has malfunctioned.
CharliesTheMan said:
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Regardless of how old this thread is I'm running into the same problems now!
My Xperia XZ1 Compact doesn't seem to be recognized when in the bootloader (indicated by a black screen and blue led).
I tried "adb reboot hboot" and it booted into a new black screen, but didn't last long before rebooting.
I tried other button combinations during the sequence and those didn't change anything.
Hey there,
Today I got my new Nexus 9 and wanted to install a custom ROM the old-fashioned way - so I unlocked the bootloader, flashed TWRP, rebooted to recovery, did a factory reset and then realized TWRP's MTP is not recognized by my PC running Win 8.1
This is pretty infuriating, since I already wiped everything, including the stock rom (yes, I know that was not the smartest move, and I also know Win8.1 has a lot of issues dealing with MTP and bad drivers)
Now I tried every possible fix I could find during the last couple of hours, I tried kicking out the "Andoid ADB Interface" in the Device Manager and reconnecting, getting the newest Google USB drivers and fiddling around with the other drivers listed in the Device Manager.
"Nexus 9" is still listed as "Unspecified" under Devices and Printers, Claiming to use "Android ADB Interface", "MTP USB Device" and "USB Composite Device" drivers.
I'd be very glad if anyone had some advice for me - if there is some information missing I'd be very happy to provide it.
Update: I got desperate and just turned MTP off and on in TWRP and suddenly at least Win seems to recognize the Nexus 9, internal storage is completely empty, though and when I try to copy a file it starts without throwing an error but the progress bar stays at 0. In Devices and Printers it shows up as simple "MTP"
Have you allowed unsigned drivers?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Have you allowed unsigned drivers?
Click to expand...
Click to collapse
sure
is android sdk updated to the latest versions?
Basically my phone stops being recognized by the computer once I reboot into the bootloader. To be clear, the phone is recognized just fine and shows up when I type 'adb devices' when the phone is operating in the android os. Seeing that all is well there, I proceed to 'adb reboot bootloader' and it appropriately reboots to the white screen with the android on it. But there the problems begin: It reads on the screen:
FASTBOOT&RESCUE MODE
Please Connect Usb Cable to
Your Computer and Open Hisuite
More information:
the huawei website
Then it displays the droid
Then it says:
Phone Locked
FRP Unlock
I tried going ahead and running 'fastboot oem unlock ###...' but it just sits there waiting for a device to be connected. I have tried multiple USB drivers on my 2 windows 10 computers. I have removed all drivers using USBdeview and tried different drivers. Windows will not allow me to point to manualy choose my driver, instead saying, 'The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.' So I tried it on an old 32-bit windows 7 system. No joy. I've tried multiple USB cords and ports. In windows device manager it has the device labeled as 'Kedacom USB Device' -> 'Android Bootloader Interface'. I can't figure out what's going wrong other than to say it seems that Windows is not using the correct driver once it enters the bootloader. PLEASE HELP!!!
Surely you have a drivers problem.
Are you using Huawei or Google adb drivers?
I couldn't find any Huawei drivers. So I used the drivers from Android developer site and several others I found here on XDA. If you have a link for specific Huawei drivers that would be AWESOME!
Try HiSuite.
Sent from my Galaxy Tab 3 using XDA Labs
ajalogan said:
I couldn't find any Huawei drivers. So I used the drivers from Android developer site and several others I found here on XDA. If you have a link for specific Huawei drivers that would be AWESOME!
Click to expand...
Click to collapse
Have you tried this?
http://semantic.gs/huawei_handset_adb_interface_driver_download
Google ADB should be fine.
i just unlocked bootloader few hours ago... i using adb driver from this thread , and it worked for me http://forum.xda-developers.com/showthread.php?t=2588979
and i also installed HIsuite before that...
seii3 said:
i just unlocked bootloader few hours ago... i using adb driver from this thread , and it worked for me http://forum.xda-developers.com/showthread.php?t=2588979
and i also installed HIsuite before that...
Click to expand...
Click to collapse
Did you used Huawei oficial site to get unlock code or did you used a 3rd party method?
zinko_pt said:
Did you used Huawei oficial site to get unlock code or did you used a 3rd party method?
Click to expand...
Click to collapse
Huawei official website
same issue, different flavor....
I'm having this issue as well, on a debian system. I have good ADB connectivity, all ADB commands seem to work fine. With fastboot, I get a device listed form them fastboot devices command. After that all fastboot commands are "waiting for device". If this is a driver issue, any hints on how to install those drivers in Linux/Debian? I tried a number of google searches, and have found all sorts of information, but nothing telling me where to put which files where to get the working drivers. Any hints?
Are you on Windows? Check if the device manager shows the device as Android with an exclamation mark inside a yellow triangle.
The problem could be with Windows 8.1/10.
Try with Windows 7
Here are the official drivers for Windows x64, ripped from Hisuite:
Mediafire | MEGA
Windows 10 is fine, it's what I use and have zero problems. Most of the time is other software that conflicts.
I'm facing the exact same issue (using Windows 10). I did the oem unlock using the code from Huawei. However after connecting the phone via cable to the PC, it does not allow me to browse the storage (internal or SD card) of the phone. All I see is a device named KIW-L24 which appears as an empty folder, and a virtual CD drive HiSuite. I installed HiSuite and the software shows me the photos/apps/etc. however there is no way to move files from the PC to the phone storage. Any pointers to the process to install the right drivers?
can you give me the link for huawei official win X32 drivers pls?!
Install hisuite , it will install all huawei drivers that u needed