Xiaomi Redmi 4X: Where to find ADB drivers? - Android Q&A, Help & Troubleshooting
Hi! I have a new Xiaomi Redmi 4X and want to use it for app development with Android studio. I enabled the developer options, usb debugging, installing apps over usb and usb debugging (security settings) on the phone. When I connect the device to Windows 7, I see a device called "ADB Interface" in the device manager which is missing a driver. The hardware id of this device is "USB\VID_2717&PID_FF48&REV_0318&MI_01".
I already tried the following things:
The Minimal ADB and Fastboot package from XDA developers (https://forum.xda-developers.com/showthread.php?t=2317790 --> https://www.androidfilehost.com/?fid=745425885120698566)
Xiaomi Mi Flash Tool (http://en.miui.com/thread-345974-1-1.html --> http://api.bbs.miui.com/url/MiFlash)
The Google USB driver that can be downloaded in the Android SDK manager
ADB Driver Lite and Platform-tools (adb/fastboot) for Redmi 4X (https://xiaomifirmware.com/downl ... ols-redmi-4x-prime/ --> https://xiaomifirmware.com/download/3718/)
Xiaomi Redmi 4X driver For Normal Connecting (https://gsmusbdriver.com/xiaomi-redmi-4x --> http://gsmusbdriver.com/driver/8597/)
None of these worked. The Xiaomi Mi Flash Tool only contained unsigned drivers which I could not install. For the rest of these packages, Windows could not find any matching drivers in them. I then selected several drivers from these packages manually and installed them despite Windows warning me that this might not work. The drivers did install, but then Android studio would complain with the message: "Installation failed with message Failed to establish session."
Where do I find a working driver for the "ADB Interface" of the Redmi 4X?
Any help appreciated!
Thanks!
Ok, I was able to solve this myself. The error in Android Studio when trying to install apks on the Redmi 4X was not caused by the ADB Interface driver, but by "wrong" settings on the Redmi 4X. I followed the directions in this thread to solve this:
en.miui.com/thread-410773-1-1.html (1st answer, by hackhert)
I'll quote the answer here:
Go to Settings -> Permissions -> Install via USB: Uncheck your App if it's listed.
Go to Settings -> Additional Settings -> Privacy: Check the Unknown Sources option.
Go to Settings -> Additional Settings -> Developer options: Check the Install via USB option.
Go to Settings -> Additional Settings -> Developer options:Enable view attribute inspection
Finally Go to Settings -> Additional Settings -> Developer options:Turn off MIUI optimization.
And then restart your device and whoooaaaa it will work i guaranteee..
NOTE - Signin in to MI account is required to enable Install via USB option.
Click to expand...
Click to collapse
The ADB driver I used is the one that can be downloaded in the Android SDK manager:
SDK Manager -> SDK Tools -> Install "Google USB Driver"
Go to Windows Device Manager, find "ADB Interface" -> update driver -> select manually -> select from list -> all devices -> select folder "C:\Users\Username\AppData\Local\Android\sdk\extras\google\usb_driver" -> select "Android ADB Interface"
Windows will warn you that this driver might not work, install it anyway
Device manager will show "Android ADB Interface" in the category "SAMSUNG Android Phone"
Thank you, this solution works perfectly for me too. Find this two days after looking around and tried thousands things.
Hahaha.... !
By doing this step :-Go to Windows Device Manager, find "ADB Interface" -> update driver -> select manually -> select from list -> all devices -> select folder "C:\Users\Username\AppData\Local\Android\sdk\extra s\google\usb_driver" -> select "Android ADB Interface"
It gives message "windows was unable to install your ADB interface" while I am giving right path.
Simple way for installing adb drivers for redmi note 4 and others
1) Download & install MiFlash Tool to your pc
2) Connect your phone to pc , automatic driver install will start , wait till it fails. (Skip driver searching on microsoft database wich is "Windows Update")
3) Open Device Manager and find there "Other devices" >> "ADB Interface" , double-click on that and hit "Update Driver"
in the window just apeared.
4) Hit "Browse my computer for driver software"
5) Hit "Let me pick from a list of device of device drivers on my computer"
6) With "Show all devices" highlighted hit "Next"
7)Then hit "Have disk" button
8) "Browse" to "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver" and "Open" there "android_winusb.inf" and hit "OK" and press "Next" with "Android ADB Interface" highlighted.
9) It will prompt you that windows cannot verify driver sources, just hit "Yes"
10)hit "Install that driver anyway"
Thats all , for most users of windows 7 this should work. Some of you may face some troubles on 64-bit Windows versions because of unsigned drivers. Google how to solve this on your OS. Guide was created on 64-bit Windows 7 Professional it may differ a bit for other windows users but you got the point where to find the original driver.
Driver ids used in guide:
USB\VID_2717&PID_FF48&REV_0318&MI_01
USB\VID_2717&PID_FF48&MI_01
P.S. Also mi flash tool has adb and fastboot executables in "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android"
i hope you will find this useful. Cheers !
I already tried the following things:
The Minimal ADB and Fastboot package from XDA developers (https://forum.xda-developers.com/sho....php?t=2317790 --> https://www.androidfilehost.com/?fid=745425885120698566)
Xiaomi Mi Flash Tool (http://en.miui.com/thread-345974-1-1.html --> http://api.bbs.miui.com/url/MiFlash)
The Google USB driver that can be downloaded in the Android SDK manager
ADB Driver Lite and Platform-tools (adb/fastboot) for Redmi 4X (https://xiaomifirmware.com/downl ... ols-redmi-4x-prime/ --> https://xiaomifirmware.com/download/3718/)
Click to expand...
Click to collapse
I tried all of that too and the ONLY drivers that work is the one that comes on the MiFlash unlock tool.
Open Device Manager. Go "Other devices" >> "ADB Interface" , double-click on that and hit "Update Driver" and manually go to the MiFlash tool folder. There's one inside that name Driver
Voila
Now you phone will be listed when you type "adb devices" on a cmd windows
Related
[A] Resolving one cause of warning "Device Cannot Start (Code 10)"
Hi, I've just spent a few hours trying to fix a problem with Kies and Windows 7. I had just used Odin3 and download mode to download a Chainfire kernel onto my GT-I9100, and afterword when I connected my phone Windows 7 would try installing drivers and fail on the MTP driver. I tried a lot of things to fix the problem, the only information I could get on it was an error message "Device Cannot Start (Code 10)". I had spotted that when connecting my phone in download mode to Odin3 that Windows 7 had detected and installed a driver for "Unknown Device". On a hunch that this driver was causing the issue with connecting after using Odin3 I tried to completely uninstall it. This is what I did (the first 8 or 9 steps are just to enable Device Manager to show *inactive* device drivers so you can uninstall the Unknown device. I've nicked this these steps from another site since I'm not allowed to link it yet): 1. Go to Control Panel and double click on System. You can also right-click "Computer" on the Start menu (or on the desktop if it's shown there) and choose Properties. Note: A faster way for opening up the System applet is to press the Windows logo key on your keyboard and then press Pause/Break at the same time. 2. Click on "Advance System Settings" link, and then click on the "Environment Variables" button. 3. In the System Variables section click on the "New" button. 4. In the New System Variable dialog box, under the Variable Name value enter devmgr_show_nonpresent_devices (just copy the value from here and paste it there) and give it a variable value of 1. Click Ok. 5. In the Environment Variables window notice how the new variable appeared in the System Variables section. Click Ok. 6. In the System Properties window click Ok. 7. Log off and log on. 8. Open Device Manager (Control Panel > System > Hardware > Device Manager). 9. From the View menu click Show Hidden Devices and searched for Unknown Device under Portable Device and USB Devices. 10. Right click the Unknown Device and select to uninstall, making sure to select complete removal of drivers option. 11. Restart the PC. 12. Start Kies without plugging the phone in. 13. Click on Troubleshooting for USB device and continue until it repairs the drivers. 14. Reboot the PC. Open Kies and plugin the phone again and let it reinstall the drivers. Hope this sheds some light on this pernicious issue.
Successfully install ADB drivers
I did some research on xda to find working solution, and finally use this method below. 1. enable USB debugging. 2. plug in your Tablet. 3. let windows install "null" driver. 4. go to Control Panel -> driver Manager. 5. find SGPT12 -> right click -> update driver. 6. browse my computer for driver software -> let me pick... 7. choose Google, Inc and "Android sooner Single ABD Interface" -> install it anyway. 8. done.
mingkee said: I did some research on xda to find working solution, and finally use this method below. 1. enable USB debugging. 2. plug in your Tablet. 3. let windows install "null" driver. 4. go to Control Panel -> driver Manager. 5. find SGPT12 -> right click -> update driver. 6. browse my computer for driver software -> let me pick... 7. choose Google, Inc and "Android sooner Single ABD Interface" -> install it anyway. 8. done. Click to expand... Click to collapse rooted or not?
Windows XP? Vista? 7? 8?
jiggykilla said: rooted or not? Click to expand... Click to collapse Since it is installed on PC (Win 7), rooted or not does not matter, but you must have Android ADB installed on your PC. BTW, I don't realize there's no Q&A section.
Working Bluetooth peripherals Drivers for VZW G3 and all phones
I found a fix for VZW LG G3 Bluetooth drivers work around that works 1 - Download the 'Windows Mobile Device Center' (current version is 6.1) which you can download it here for 32-bit OS or here for 64-bit OS. This works for both Vista and Windows 7. I've tried it on both. 2 - Install the downloaded software but it may not look like it worked on Windows 7 PCs. Vista automatically configured the settings on the Bluetooth devices but for those who have Windows 7, here are the things you should do: 3 - Go to 'Device Manager' from 'Control Panel' -Or- just right-click on Computer Icon and choose 'Properties' and then click on 'Device Manager'. 4 - You'll see an 'Unknown Device' named 'Bluetooth Peripheral Device' 5 - Right-Click it and click on "Update Driver Software" -Or- anyway you find it easy to bring up the Update driver window. Click "Browse My Computer Image for Driver Software" button. Click "Let Me Pick from a List of Device Drivers on my computer". Select 'Bluetooth Radio' from the list if it asked you to select and then in the next window, it will show a list of drivers with Company Names in one list and Drivers in another. In the Company List choose 'Microsoft Corporation', not only Microsoft. From the drivers list there may be one or more drivers with the name "Windows Mobile-Based Device Support" with different driver versions. Select one or the latest. Ignore any warnings and keep pressing next and then Finish at last. If all goes well, the last screen will show the message that device driver is successfully installed. After doing this and pairing my PC and phone again, I was able to send files between them through Bluetooth. I hope this helps
Having Trouble Getting ADB to recognize your device?
Excuse me if this has been posted before, but I've been having trouble with it (pretty new at this - the only other android I've had was a Galaxy S5 AT&T variant with a locked bootloader) I'm on Windows 10 if it matters. After installing the SDK and running the "adb devices" command, my results were: List of devices attached ...and nothing more. "adb reboot bootloader" also did nothing. The phone never asked me to authorize the computer for debugging either. The fix was to download the latest Google USB driver and install them manually. https://developer.android.com/sdk/win-usb.html (I can't post links yet) Open device manager with your phone connect via USB. On mine there was an item called simply "ADB Interface" with a yellow symbol superimposed over the icon. Extract the .zip containing the Google USB drivers (doesn't matter where). In Device manager right click "ADB Interface" and click "Update driver software..." Click "Browse my computer for driver software" Browse to the folder containing the drivers and click "ok" Make sure the box marked "Include subfolders" is checked and click next. Let the drivers instal. There should now be an entry under Android Device in Device Manager called Android Composite ADB Interface. After doing this, check your phone and there should be a window asking you to authorize your computer for debugging. Authorize it and you're done. Hope this helps someone do this a little faster than I did.
Man I gotta love you! thank you so much!!
Cannot connect via adb
I have not managed to connect to my Redmi Note 4 (Android 6.0 MRA58K, MIUI Global 8.1 | Stable) via adb from my Windows 7 computer. With my old SGN4 this was never a problem but I am a noob on the RN4. I have Android Studio (with adb) installed, then I connect my mobile via USB cable I select on the mobile "Use USB for: Transfer files (MTP)", USB debugging is enabled and I can see the phone in the Windows explorer then I open a command prompt and run adb but "nothing happens": c:\Progs\Android\sdk\platform-tools> c:\Progs\Android\sdk\platform-tools>adb.exe logcat - waiting for device - ^C c:\Progs\Android\sdk\platform-tools>adb devices List of devices attached c:\Progs\Android\sdk\platform-tools> What am I missing???
Check drivers on control panel, it is correct?
dromaczek said: Check drivers on control panel, it is correct? Click to expand... Click to collapse Not sure I can post an image: i.imgur.com/UFAi5ez.png In the Windows Device Manager there are two interesting entries: Other devices --- MTP [has an exclamation mark] Portable devices -- Redmi Note 4 [looks fine] Is the "Transfer files (MTP) mode correct"? Does the phone need to be rooted?
Gollob said: Not sure I can post an image: i.imgur.com/UFAi5ez.png In the Windows Device Manager there are two interesting entries: Other devices --- MTP [has an exclamation mark] Portable devices -- Redmi Note 4 [looks fine] Is the "Transfer files (MTP) mode correct"? Does the phone need to be rooted? Click to expand... Click to collapse You have wrong adb driver (choose manually other from control panel)
dromaczek said: You have wrong adb driver (choose manually other from control panel) Click to expand... Click to collapse The driver was indeed the issue, thanks for that. This is what I did: [1] xiaomifirmware.com/downloads/download-xiaomi-redmi-note-4-drivers-utilites [2] Download: latest_usb_driver_windows.zip [3] also downloaded ADB Installer v1.4.3: adb-setup-1.4.3.zip from the same page (not sure if this was necessary) [4] Control Panel, Device Manager: installed the driver (Android ADB Interface) Now I have this Android ADB Interface under the heading SAMSUNG Android Phone, not sure if this is a problem at some point later on as it is obviously a Xiaomi Android Phone that I have. [see: i.imgur.com/yvIyIjt.png] When running adb devices I got the device ID and unauthorized at first and after approving USB access on the handset it showed the device ID and authorized and I can issue commands like abd logcat.
Gollob said: The driver was indeed the issue, thanks for that. This is what I did: [1] xiaomifirmware.com/downloads/download-xiaomi-redmi-note-4-drivers-utilites [2] Download: latest_usb_driver_windows.zip [3] also downloaded ADB Installer v1.4.3: adb-setup-1.4.3.zip from the same page (not sure if this was necessary) [4] Control Panel, Device Manager: installed the driver (Android ADB Interface) Now I have this Android ADB Interface under the heading SAMSUNG Android Phone, not sure if this is a problem at some point later on as it is obviously a Xiaomi Android Phone that I have. [see: i.imgur.com/yvIyIjt.png] When running adb devices I got the device ID and unauthorized at first and after approving USB access on the handset it showed the device ID and authorized and I can issue commands like abd logcat. Click to expand... Click to collapse You must authorized access and check all ADB options on xiaomi rom to use for example adb density command etc (and log on mi acount)
[Solved] Xiaomi Redmi Note 4 : Connection with ADB Hi, As we all know Xiaomi works on its own MIUI, So when you want to connect to adb that is developer mode you need to connect as MIDI, Enable MIDI Step 1: Goto settings > Additional Settings > Developer options Step 2:In developer option, Enable developer options, Step 3: In same menu go down in side Networking and from the SELECT USB CONFIGURATION, select MIDI Now check adb devices on your command prompt you can see your Xiaomi is connected. Happy Coding
Does your phone show up on the terminal with adb devices command when in recovery? Can be stock recovery too. Also, in fastboot, use fastboot commands i.e. fastboot devices instead of adb devices One more thing, go to device manager and manually install a legacy driver and browse to adb and choose Android Bootloader Interface (ABI) look into it, it's possible. That should do it. Tell me if it helps. Sorry I don't know how to quote stuff and format commands.
dromaczek said: Check drivers on control panel, it is correct? Click to expand... Click to collapse hello brother, I'm facing the same issue while unlocking the bootloader. I think these is prob with the drivers.. pps help me out