ADB is not recognizing my Redmi Note device. I am using windows 8
Also when I use below command in CMD,
adb devices
it is displaying
I followed the procedure in below link,
Using Hardware Devices
For the Redmi Note ADB drivers, you have to go through this hoop. I am certain it is the same with all MI phones or maybe for all non-Google mfg phones, I am not sure. First of all if you connect the device with USB cable and USB Debugging off, you will see that Windows 8 loads a generic driver for you to copy on/off files to the phone and SD storage. This will appear when the USB cable is first plugged in and appears as a device icon under Control Panel, Device Manager, Portable Devices, HM Note(or the device you are working with).
Go to the phone and switch on USB Debugging in the Developer section of your phone. Notice that an additional item appears as an undefined device now in the device manager list, it will have the yellow exclamation mark and it may not have the same name of the phone listed as you saw under Portable Devices. Ignore this item for the moment. Now, without doing anything to the phone (it should be already in USB debug mode) go back to the Portable Devices in Device Manager and right-click the HM Note or whatever phone you are working with that is listed there without the exclamation mark (listed under Portable Devices). Right click on the icon under Portable Devices. On that icon select Properties, Details, and under the pull down, select Hardware IDs and copy down what you see.
For Redmi Note I get:
USB\VID_2717&PID_1218&REV_0216&MI_00
USB\VID_2717&PID_1218&MI_00
(Note if you do this out of turn, the HW ID will be different with the phone USB debugging turned off. You want to copy the value that it changes to when the USB debugging is ON)
Now do as the instructions say above, of course customizing the lines you add the the INF file with those relating to your own phone, not the Nexus 10. Here is what to customize; when you downloaded the SDK you should have a file structure expanded from the ZIP such as this:
\adt-bundle-windows-x86_64-20140321\sdk\extras\google\usb_driver
Find the file named: android_winusb.inf in the usb_driver folder Make a copy of it and name it anything, such as redmi.inf.
Edit the redmi.inf and add the lines as instructed above only modified for your particular phone. For example, for the HM Note, I added the following 2 lines as instructed in the 2 locations as instructed.
;HM Note
%SingleAdbInterface% = USB_Install, USB\VID_2717&PID_1218&REV_0216&MI_0
%CompositeAdbInterface% = USB_Install, USB\VID_2717&PID_1218&MI_00
Now go back up to the unknown device that appeared in Device Manager when you switched on device USB debugging and right click on this item (has yellow exclamation mark), right click on it and then select Update Driver Software, and then Browse My Computer, Let Me Pick, click on the Have Disk button and browse to find the Redmi.inf. Continue to agree to all the prompts warning you it might not be the right driver. As the final step, Windows should have identified the device as Android ADB Interface and once that is done, you should be able to go back, open your CMD window and run the command "adb devices" as instructed in this tutorial and now you should see that the phone is now discovered and communicating.
I found this at ADB No Devices Found
Follow the below step to resolve adb shell not showing device issue.
1) Go to About Phone, and tap MIUI version for 7 to 8 times. This is to enable developer mode.
2) Got to Additional Settings -> Developer options. Enable USB debugging. And set MIDI in Select USB configuration. If you need apk installation via adb, then enable Install via USB also.
This solution worked for me :
Try Installing the PC Suite that came with Redmi Note and it will install all the necessary drivers for the mobile to work properly with PC Suite ;) . And after that check the connection with ADB it works fine.
I found a workaround without installing anything. Follow these steps:
Turn on Developer options.
Open the developer options.
Turn on the android debugging.
Scroll to bottom of the list.
There will be an option called "Turn on MIUI optimisation" which will be turned on by default, turn it off. the device will restart.
Voila! Your adb should be able to detect your mi device now.
PS: I found this solution a year back but now I don't remember where.:)
You need to enable the hidden Developer Options on your Redmi Note. To do so:
On your Redmi phone, find and launch the Settings app.
Tap General settings.
Tap About phone.
Tap "MIUI version" for 7 times.
Once you reached the 7th times, you’ll see the “You are now a developer” message appears on screen.
You are now a developer.
Once turned on, you can tap Developer options on the General Settings screen to access a list of options which deemed to be mainly useful to the developers.
Lastly, you can do a factory reset to hide the Developer options.
After the above steps, go to command prompt and run adb devices command. It should fetch the device id for connected redmi note phone.
If it doesn't work out by trying out solutions mentioned by others, then on top of that Try installing and running MI PC-SUITE from official Mi website HERE. Then try debugging again and you will see your device name in the list of available devices/options to run the app.
revoke all USB-debugging options and reenable it again in MI phones.
Setting -> Developer options -> Revoke all USB-debugging -> Then enable USB debugging
Disable MIUI optimizations
Related
Having trouble with Android Studio connecting to my Pixel phone. I'm sort of out of ideas and am looking for suggestions. I feel like I'm missing an obvious step.
Things I've done:
Made sure developer options is on with USB debugging on.
Have tried switching from MTP to PTP.
My computer recognizes the Pixel just fine under windows 8.
Made sure android studio is up to date including "Google USB Driver" installed under SDK tools.
My previous phone (Droid mini) connects just fine.
Tried different USB ports for the cable to my phone.
Encountered this problem today as I tested on other people's phones. I found 4 possibilities why a device may not be recognized:
Case #1: The USB cable supports charging but not data transfer.
Case #2: Developer options haven't been enabled on target phone (see: https://www.verizonwireless.com/support/knowledge-base-215055/)
Case#3: Developer options enabled, but USB debugging hasn't been enabled. Go to Settings > System > Developer Options > USB Debugging
Case #4: Some (but not all) phones require MTP transfer mode to be enabled. It can be enabled by sliding a finger from the top of the screen and tapping "Android system - USB charging this device" > Tap for more options > Transfer files.
Hope this helps someone ^_^
EDIT:
It's come to my attention that there's another possibility. I don't know what causes this, but if you get really stuck, sometimes you need to go into Settings > Developer Options > Debugging > Revoke USB debugging authorisations. This will reset your device USB pairing fingerprint which will often bring the phone back as a device target in Android Studio.
In Pixel devices USB debugging is enable when:
Step 1. Enable Developer Options to double tap on Build Number, you can get it by search with build in setting.
Step 2. Enable USB debugging Option, to enable this just to search usb debugging in settings.
Step 3. Pixel devices require USB tethering mode to be enabled, It can be enabled by sliding a finger from the top of the screen and tapping "Android system - USB use for " > Tap on USB tethering.
After completion of all these steps you will be able to use you pixel device as enabled for debugging in SDK.
Android Studio / SDK Manager will provide the driver but Windows might not automatically install it for your device. Try checking the device manager, unplugging and reconnecting the device or let the device manager search for new hardware.
The driver (when installed via SDK Manager) will be found by windows when provided with the SDK root directory, usually AppData/Local/Android/sdk
I have had the same trouble with my Google Pixel 2 (Android 9); I couldn't connect it to ADB in Android Studio 3.3. In my special case, AS runs on Kubuntu 18.04 in a VMware Workstation on a Windows host.
I have to do following steps every time I want to connect the phone (the phone is already in developer mode):
Plug phone via USB into the computer (and connect it to the VMware guest, if you use it)
Phone: Swipe down the notification bar, there should be a message 'Charging the device via UDB'
Tab on it and change the 'Use USB for' from 'No data transfer' to 'File trasfer'
You can activate 'USB debugging' on your phone's developer screen before or after this procedure, both works for me.
That happened to me with a generic Type C to USB Cable (White Cable in the Picture Attached). Then I bought another Cable (The Black one in the Picture Attached) and it worked perfectly. It was the Cable. Make sure to have one that says "Data & Power".
Hope it helps!
The solution to device not found when running adb devices from windows 7 standard terminal for my Pixel 4a 5g was to simply update my google USB drivers. https://developer.android.com/studio/run/win-usb
If dev options aren't available, double click the build number until a notification appears stating dev options have been enabled.
I tried to play Android Studio 2.0 with my mobile without success, what I did are:
In my mobile, Apps/gear icon/Settings/SYSTEM/{} Developer options/ Android debugging/, enable the Android Debug Bridge(adb) interface (set tick).
After plug in my mobile to my PC with a USB cable, I found A0001 in my Computer folder. Within A0001, I can see the files in my mobile.
In my PC, run Android Studio/bin/studio.exe, "Select Deployment Target" window shows with message "No USB devices or running emulators detected"
I have tried two different USB drivers but got no lucky.
Perhaps I should tell Android Studio where is my USB driver? But, how?
Can you help?
I had the same problem too and I managed to resolve it this way.
First, enable debugger mode in your android device.
Go to Device Manager from Start Menu and try to find ADB Interface with an error symbol on it. This generally happens because windows sometimes fail to load all the mobile device drives.
Next, Go to http://adbdriver.com/downloads/ and download the driver installer, unzip and run it.
Now go to Android Studio and you should find that everything is working fine.
Chill....
same here... but I hope you can avoid this problem the same way I Did.
There is an "universal ADB Driver for all Android Devices".
Yep... sounds like magic.
Just follow this link.
https://devs-lab.com/usb-adb-drivers-for-all-android-devices.html
Fun fact there is no "Step 5" in that article so I'll give you.
you have to enable "USB Depuration" from "Developer Options" connect your cellphone to computer as a "MTP storage" , after windows detected your cellphone as a "Portable Device" Execute ADBDriverInstaller.exe (that downloaded from devs-lab)
check the device list and your cellphone will say "Driver incorrectly", select your cellphone and press install.
Step 6: Once the process is completed, you’ll see something like the image that appears there (in the link).
I hope that somebody else work this
Go to Run > Edit Configurations...
Under Deployment Target Options select Show Device Chooser
Dialog from the drop-down-list
See picture for reference
After struggling with this problem for a while, I found that there are certain cables that can only charge your phone, and even though they seem to be working, they do not allow your phone to be used as a "Media Device" and therefore Android Studio does not detect it.
Go to
Tools | Android | Enable ADB Integration
Make sure it's enabled. When I upgraded to 2.X it was for some reason disabled for me and it took me hours to find it.
I just cannot beleive why it is so difficult! let me try again and please check my steps again:
I installed Android Studio 2.0, then run Computer/OS(C:)/....../Android Studio/bin/studio.exe.
The Android Studio window appeared in my working area Computer/OS2(J:)/Users/MyAccount/Desktop/.
I connected my mobile with my computer, Cpmputer/A0001/ appeared, from it, I can see the files in my mobile.
I clicked the run icon in the Android Studio window, a "Select Deployment Target" window apeared with message "No USB devices or running emulators detected".
(I got two USB ports and tried both but got the same result.)
Finally found the solution : )
1. Install device’s required driver. (for me it was motorola device
manager)
2. Download Google Usb Driver from SDK Manager
3. Open your phone's setting->developer options and turn on USB debugging.
4. connect your device to computer
5. Go to Device Manager from Start Menu and try to find if there is ADB Interface with an error symbol on it.
5.1. If yes, then right click on the ADB interface->Update driver
software->Browse my computer for driver software-> Let me pick from
a list of device drivers on my computer->Select Motorola ADB interface
5.2. Now one confirmation will pop up in your mobile, accept it
5.3. Now you should see no error mark beside the ADB interface in your
device manager
There are 3 steps to set up your phone for debugging:
1) Change your phone to developer's mode by going to Settings, About Phone, Software Info, Android Version - tap at least 7 times on the Build Number text. You will get a message saying you are now a Developer.
2) Enable USB Debugging in Settings - Developer Options. Make sure you are not connected to your USB port to see the USB Debugging option enabled, otherwise it will be disabled.
After you plug in your USB, swipe at the top of your screen, you will see USB Debugging on.
3) Make sure USB connection is set to Photo Transfer (or MTP - Transfer photos and videos). After you plug in your USB, swipe at the top of your screen, and you will see Tap to change USB options on the menu. Tap it, and select Photo Transfer option.
Perhaps your mobile manufacturer does not provide the proper driver.
Go to Device MAnager and look for: Android Composite ADB Interface. If it's there, the driver is properly installed. If not... You and I are on the same "wagon"...
I tell you: Acer? Never again.
USB debugging somehow got turned off under developer options on my Samsung. Turned it back on and it worked, but only by clicking on "debug app" instead of on "run app".
With me, when connecting the mobile to the pc, three options appeared on my mobile.
Charge this phone
Transfer Files
Transfer Images
I thought I should select "Transfer Files", but it dd not work
But it only when works I choose "Charge this phone"
Few ways to resolve this problem.
Case 1: Install PdaNet+ in your system. (worked for me).
Case 2: Enable the USB debugging option in your mobile. Setting > developer > Check "USB Debugging".
Case 3: Change from MTP to PTP.(sometimes vise versa works).
Question is Your development sdk no mobile version android sdk Platform.
For example, my android phone system is 6.0, i need download sdk Platform 6.0.
First, try to revoke the usb sessions in the developer options, then try downloading an oem usb driver
If then doesn’t help you can try opening the device manager on windows, right click on your phone, select uninstall. This worked for me if I had the same issue.
I couldn't find my android phone or any USB device I connect to my windows laptop on the hidden icons. Well, my mouse and phone could charge but I can't seem to see my phone in the File Explorer option.
I prefer running Apps using my phone rather than emulator in Android Studio and yet I couldn't see my phone when I connect using the USB.
This helped me solve all my problems after several hours of searching for solution.
Download Universal ADB Drivers - One size fits all Windows Drivers for Android Debug Bridge
Please use this link: https://adb.clockworkmod.com/
I hope this works for you like magic!
I can see all the devices I connect using the USB cable and my mouse receiver.
I recently bought LG G3 and I have enabled debugging mode but Eclipse is still not recognizing it, back when I used the Galaxy S3 for development I had to install Samsung Kies. The G3 drivers are installed and I can see it in My Computer, do I need something like the Kies but for the LG? If so can someone please post a link for that?
See update below
I found the answer that worked for me.
When you plug in the phone, bring down the status shade, pick the USB item ("USB connected") then, from there, pick "Internet connection" -- I chose Ethernet, but I'm not sure the choice matters on the dialog that pops up..
This enables USB debugging to become active; leaving it on Charging, MTP, or PTP does not work.
Once you do this, you can follow #Siddharth's steps to setting the ADB drivers, if needed. (You may need to use the actual LG drivers and not the Google drivers, but once I got this far, it was just like any other phone.)
Caveat
For me, even after going through this once, I still get the "installer" first and then have got go in and choose the "Internet connection" again. But, at least it works.
Update 10 Dec 2014
A recent firmware update has, indeed, removed the "Internet connection" as an option. Instead, PTP now works. I still get the "Connected as an installer" notification every time I plug in the phone and have to click on the notification then click on "Camera (PTP)" -- or wait about a minute. It's slightly better than what It was.
Also note: When this change occurred I had to install the drivers again for the phone, since it comes up as a different type of device when "Camera (PTP)" is chosen than when I used the "Internet connection" option.
For me, this has solved the problem: simply go to LG's website, http://www.lg.com/us/support/software-manuals, select the model (I have selected 'D850') and go to Software Updates tab where you can download the driver. I have installed it and then Eclipse recognized my device. I'm working on Windows 8.1, by the way.
yakobom
After a lot of searching and trying all solutions still I couldn't connect my LG G3 to eclipse on mac. Finally I find this solution, it works for me hope for you works too:
Install LG USB driver for mac
Go and enable developer mode in your G3 (Setting->About phone (in General Tab)--> Software information --> Tap 8 times on Build Number) then you will see the message which says the Developer option is enabled
In this step you expect that after connecting your mobile via USB cable, the Eclipse detect it
But for me it didn't happen
in this step you need to go (Setting--> Developer Options--> and turn off this option from above green (on/off) switch then again switch on this option from same place (If you don't do this step the "USB Debugging" mode will stay fray and you can not enable it)
In Developer Options menu scroll down until find the "USB Debugging" then tic it and enable it.
almost finished , you should back and configure running mode for your application and see the G3 in your connected usb devices
Try this solution :
Right click on My Computer --> Properties --> Device Manager
Right Click on your device --> Update driver software
Click on "Browse my computer for driver software"
Give path of your android sdk like "D:\Android_Sdk\sdk\extras\google\usb_driver" and tick "Include subfolders"
Click
Now repeat the steps till "Browse my computer for driver software".
Then click on "Let me pick form list of device drivers on my computer". Click on the first option and click next and then click yes. Drivers will be installed for your device.
Hope this helps.
Change the USB mode to PTP and you will get the RSA prompt.
Within the prompt, select allow it > ok and you are done.
This worked for me when I had the same problem on a Mac computer.
To contribute to possible solutions for this fix: I am using an LG G3 on a Mac.
In my case, ADB saw it as a device when I checked, and the Mac showed the device information in the System Information window, yet Eclipse did not see it. I also did not get the RSA confirmation pop-up when I connected the device through USB.
To fix, with my G3 connected, I selected the USB PC Connection (either from the navigation bar or through the settings) and changed it to be Send Images (PTP). Once this was on, I was given the RSA pop up and Eclipse recognized the phone in the Run Configurations window.
If you have this problem on Ubuntu; here is what I did to get it working:
Switch to PTP from MTP on the phone (this assumes you're connected via USB)
Disconnect the USB cable
Go to settings -> developer options and select revoke usb authorizations then ok
Make sure USB Debugging is checked
Reconnect the USB cable and your phone will say its connected as an installer; wait a minute or three and debugging mode should appear on the status bar (on the phone)
Open Eclipse and go to DDMS
Select "reset adb" in the dropdown if your phone isn't appearing yet
Working on Windows 7. All of the solutions from other sites didn't help (i.e. restarting adb and switching between MTP, PTP, Charing). In the end, I found this article (http://www.technobuzz.net/install-lg-g3-lg-drivers-windows-mac-usb-adb/), which contains links for the necessary drivers for the lg g3 (and some others I think). This did the trick and made the RSA key fingerprint dialog appear finally. After confirming, adb and eclipse recognize my device perfectly!
I had this buggy error with my LG Optimus L3 phone connecting to Win7/8 machines!
Cause: Device Driver was missing as it seemed at the end when I fixed it!
How to Fix:
Search through web (using Google) "LG < Your_Phone_Model Number > Drivers Download".(Ex.:- Go to About phone in your settings list > Model Number, for me it's LG-E400f)
Mostly the first few links are related to the required Device Driver download page.(Ex.:- for me I got the following link and for each device driver LG or most of the other vendors/manufactures have that kind of a Manuals and Drivers Page) Visit that page mentiioning about software update and drivers downloads.
Scroll down to the section of "Manuals and Software Update" and doing just the Step 1 was enough for me, which is "Install the USB DRIVERS "
Download it(for Mac or Windows) > Install It > Check Your Eclipse ADT > and it should be visible under Devices tab by now
Cheers!!!
Hope this helps to someone else to clearly get to the solution!
it seems that Eclipse shows the offline mode for lg G3 and some newer devices
and there is no way no use these devices for ADB debugging
there is a way
I am using windows 10
1- download this 11 MB file < http://dl2.uncox.com/android/upload/platform-tools-v22.zip>
2- then go to the directory that you installed the SDK
3- extract the zip file in to the platform-tools folder , override all files(click yes to all) be sure that Eclipse doesn't running
4- open Eclipse and select your android device that stands in devices tab at the right-top corner of your screen and then you can see the arrow near the screen- capture icon and you will find the reset-ADB. click on it ,after that your phone will ask you to allow android debugging for your device click on it
5- congratulations .now you can see that your device shown online
i hope this will help .sorry for my english
I also had a great deal of trouble when attempting to debug android applications on my shiny new LG G3. What ended up working for me was first installing the default google drivers onto the G3 and then following the process detailed by #lilbyrdie.
The process of installing the google usb drivers is very nicely gone through here.
However, with the most recently pushed android update to the G3 there are no longer the options for internet connection or charge only; but they seem to have fixed this defect forcing you to make this odd choice to enable debugging. The only options remaining are MTP and PTP, but if you pull down the notification drawer, choose the 'USB connected' notification (assuming the device is connected to your computer via USB of course) and from there click on 'Media sync (MTP)' even if it is already selected then debugging should be enabled.
Android can't update on the fly the developer mode. So, after turning on developer mode (and given you have the latest driver) switch the green button(under settings->general->developer options) to off and then back on. Then turn debug mode on (after that windows recognizes a new device) and you should be good to go.
In my solution for Windows 7 was helpful to update Android SDK Tools to latest version.
ADB Single/Composite values for LG G3 phones -
I found it was necessary to update (~userName/.android/)adb_usb.ini file with the line 0x1004:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2207
0x1004
In addition, I needed to add the following entry in (.../sdk/extras/google/usb_driver/)android_winusb.inf:
;
; Android WinUsb driver installation.
;
...
[Google.NTx86]
...
;LGE Android Phone
%SingleAdbInterface% = USB_Install, USB\VID_1004&PID_633E
%CompositeAdbInterface% = USB_Install, USB\VID_1004&PID_631D&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_1004&PID_631D&MI_01
[Google.NTamd64]
...
Oh, and set USB to PTP as well as turn-on USB debugging.
When you're all done with the file modifications and several passes at installing the drivers (ref. earlier posts), you can verify your phone is ready via the Device Manager. It will list your phone as "Android Device"->"Android Composite ADB Interface". I believe an earlier post explains setting up the drivers
I have a Samsung Galaxy S i9000 smartphone, and I want to debug my Android app on my device.
I read the instructions at http://developer.android.com/guide/developing/device.html. I must say that although I didn't install any other driver than the Kiel Software and the USB drivers coming with the smartphone itself, I can see my device on the list when I write adb devices -- I see a device there with some numbers at the beginning and than 'device'. I also see a device in my device manager as Samsung Android Composite ADB Interface under the ADB Interface branch. Also in DDMS tool I see two devices; one emulator, and the other device with the same number as I see in the command line.
I think everything is right so far, but when I press the run button in Eclipse, or the debug button, a Device Chooser dialog does not show up as described in the android development website. Has anyone any idea?
Check the Console window to see what is going on. The Device Chooser dialog only shows up if it cannot automatically select a target.
Well the steps should be:
- install drivers (or Kies, it's simpler for me since I connect a lot of different devices)
- check if USB Debugging is checked under Settings -> Applications -> Development -> USB Debugging
- check if the device shows up in the ADB list
If that doesn't work, as was the case with me once trying something on Honeycomb, try simply deleting any emulators and see if it doesn't automatically upload to your device.
I am trying to enable USB Debugging on Android so that I don't need to use the emulator.
I did what all the posts all around the web say to do: I went to settings -> applications -> Developer -> USB debugging
It still does not turn on the notification sign that USB Debugging is enabled, and Eclipse does not recognize it, and uses the regular emulator.
Does anyone have any idea what is wrong?
You haven't specified what device you are using or what operating system you are using, so that could be helpful.
A few things to keep in mind:
1 Don't mount as USB storage.
2 You also need to make sure to install the drivers for your phone so that the Android Debug Bridge (ADB) can properly communicate. After these are installed, try the command "adb devices" and you should see an item in your list of devices.
Update based on your comment: You can download Kies from Samsung, which include the drivers (as well as other things): http://www.samsung.com/us/kies/
Or you can find unofficial driver-only packages, such as: http://forum.xda-developers.com/showthread.php?t=961956
I think you'll need the OEM USB dirvers.
Read this:
OEM USB Drivers
My experience with windows has been that you might need to un-install the USB drivers under device manager. Then disconnect the device (restart might be required). After plugging the device back in make sure you use the manufactures drivers if available
you have installed your device driver rite?then right click on your app name->run as->run configurations->target->select manual->apply.after that click on debug button then it will ask you to select the device.
If everything else is tested, try with another USB cable.
On Android 4.2 and higher, the Developer options screen is hidden by default. To make it visible, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options at the bottom.
Fruthermore on some devices you will be asked to accept an RSA key, which allows debugging through your computer. This ensures that other adb commands cannot be executed unless you're able to unlock your device.
Detailed information can be found here:
http://developer.android.com/tools/help/adb.html It is the overview about adb commands (which is used to send data to your device) and it starts with the steps how to bring your phone to debug-mode.
I wish to add to Danation's answer with the following.
If you have installed KIES, and you've tried following instructions a couple of times (for the android SDK package) without success, here's what worked for me:
As a precaution, disconnect the device, and press 'Revoke USB Debugging authorizations'.
Now, go to kies, and reinstall the device driver as seen on the image below.
Connect the device.
For me, it was a routine, it usually works when installing kies, but I was stuck on this today for a little while, and I hope i can help others with my solution as well..