Right now I am trying to connect to Samsung Captivate. I see the device, but adb devices shows and empty list. Debugging in Eclipse I cannot see the device. I see it in the Windows 7 device list however. phone says connected. But adb devices does not list anything. What else do I need to do?
Samsung has a separate driver for connecting their Android devices for to Windows machines. I think there is an option in Kies to install this.
This solution is to connect via wifi, so there is no installation of drivers needed.
First
you need to download the shell terminal emulator on your android phone.
make sure both your android phone and computer are on the same wifi connection.
after downloading the application, open it and type this:
type "su" and press Enter.
type "setprop service.adb.tcp.port 5555" and press Enter.
type "stop adbd" and press Enter.
type "start adbd" and press Enter.
after that.
navigate through your SDK folder wherein you can find an "Adb.exe" and open that in CMD and type this.
type "adb connect " and press Enter.
and you are done.
Related
I'd like to connect to android emulator on bluestacks 4 with adb.
but I've got an error with adb.exe -s emulator-5554 shell
checking devices.
$ adb.exe devices
List of devices attached
BH901... device
CB512... unauthorized
emulator-5554 device
once I shutdown bluestacks window, the emulator-5554 will be hidden from above command's result. thus I think emulator-5554 means bluestacks.
then commnad as below to use adb.
$ adb.exe -s emulator-5554 shell
error: closed
but as you know, an error occured.
First, in Bluestacks, go to Settings -> Preferences -> Enable Android Debug Bridge (ADB). Like this:
At this point, Bluestacks enables its adb functionality and exposes itself to the localhost at port 5555 (the default port)
So, in your command line, type adb connect localhost:5555 and you should be good to go.
I did exactly as the chosen approved answer but i still could not connect my android studio to Bluestack 4. Hence i think the problem both of us are encountering could be due to bluestack device ip has changed. (Even if you had detect the device using adb devices command earlier on). Each time i open up my bluestack emulator, i notice that its ip is always different. Hence that could be one of the reason why you could not add adb to bluestack4.
The following step works for me. I am using windows 10, Android Studio 4.0.1, Bluestacks 4.200.
find your android studio sdk platform tool folder. For me its is
custom installed in my D drive. for example->
D:\AppData\Local\Android\Sdk\platform-tools
right click on adb.exe and run as administrator. (click on yes if
a pop up ask if you would like to make changes to your devices.
After that you would only see another pop up that suddenly
disappear.)
open Bluestacks. Run your selected emulator (samsung/pixel etc).
Ensure that you have enable "Enable Android Debug Bridge (ADB) in
the emulator preferences.
open platform tools folder path: Click on address bar, alternatively press Alt + D. Now when address bar is highlighted, type cmd in the bar. Press Enter key.
enter the following command->adb connect xxxxxxxxxxx
where xxxxxx is your device localhost ip. (see attach pic. My device ip is
127.0.0.1:xxxxx hence my command is ->adb connect 127.0.0.1:xxxxx
continue with the following command->adb devices
you would see your bluestack emulator device. same ip listed.
open your andriod studio. you would be able to see your bluestack
emulator
[
And I have test bluestack 4 in windows 10 and enable the adb permission in bluestacks 4 settings. It works for me.
After enabling adb in blue stack
go to platform-tools folder
e.g. "C:\Users\Your Username\AppData\Local\Android\Sdk\platform-tools"
run this in cmd "adb connect localhost:5555" or whatever port given by bluestack.
or just run directly from Win+R
"C:\Users\Your
Username\AppData\Local\Android\Sdk\platform-tools\adb connect
localhost:5555"
n.b. localhost = 127.0.0.1
On BlueStack 5 it should be in Advanced -> Android Debug Bridge
This question already has answers here:
How can I connect to Android with ADB over TCP? [closed]
(37 answers)
Closed 5 years ago.
I want to debug Android APPs on my phone (LG nexus 4). I'm travelling and I forgot my USB cable. When I work at home I can do it just connecting the USB cable and executing the command 'adb tcpip 5555'. Then I can unplug the USB cable and connect via 'adb connect IP'.
But now I cannot execute the first command because I don't have a cable. I don't understand why I have to do it every time, since I already execute the 'adb tcpip' command before.
What I tried now:
I installed a terminal application on my Android and tried to execute that command there, but I received a "device not found" error. Maybe he cannot see himself...
I search for any reasonable option in "Android Development Options" and enabled everything seemed to have relation with Wifi. But nothing helped.
I search StackOverflow, but all answers I found involving connect via USB cable before. Is there I way to do this connection without the need of a cable at all?
Some info:
My Nexus 4 isn't rooted.
The android version is 5.1.1.
The question is about a non rooted device but if it is rooted the simplest way would be to:
From the terminal on your phone, do this:
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
See this answer for full details.
For your question
Adb over wireless without USB cable at all for not rooted phones.
Old Answer:
You need to connect your device to your computer via USB cable. Make sure USB debugging is working. You can check if it shows up when running adb devices.
Open cmd in ...\AppData\Local\Android\sdk\platform-tools
Step1: Run adb devices
Ex: C:\pathToSDK\platform-tools>adb devices
You can check if it shows up when running adb devices.
Step2: Run adb tcpip 5555
Ex: C:\pathToSDK\platform-tools>adb tcpip 5555
Disconnect your device (remove the USB cable).
Step3: Go to the Settings -> About phone -> Status to view the IP address of your phone.
Step4: Run adb connect <IP address of your device>:5555
Ex: C:\pathToSDK\platform-tools>adb connect 192.168.0.2
Step5: Run adb devices again, you should see your device.
Now you can execute adb commands or use your favorite IDE for android development - wireless!
Now you might ask, what do I have to do when I move into a different workspace and change WiFi networks? You do not have to repeat steps 1 to 3 (these set your phone into WiFi-debug mode). You do have to connect to your phone again by executing steps 4 to 6.
Unfortunately, the android phones lose the WiFi-debug mode when restarting. Thus, if your battery died, you have to start over. Otherwise, if you keep an eye on your battery and do not restart your phone, you can live without a cable for weeks!
See here for more
Ref: https://futurestud.io/tutorials/how-to-debug-your-android-app-over-wifi-without-root
UPDATE 1:
If you set C:\pathToSDK\platform-tools this path in Environment variables then there is no need to repeat all steps, you can simply use only Step 4 that's it, it will connect to your device.
To set a path:
My Computer-> Right click--> properties -> Advanced system settings -> Environment variables -> edit path in System variables -> paste the platform-tools path in variable value -> ok -> ok -> ok
UPDATE 2:
Go to the android terminal
adb tcpip 5555
adb connect your_ip_address
We can do it without a USB cable at all in the following ways.
NEW UPDATE 1: (Latest Answer without using USB cable at all)
Note: It will work only when your laptop and mobile should connect to the same WiFi.
Step 1: In Android studio choose "Pair Devices Using Wi-Fi" from the Device Connections dropdown.
Step 2: In Mobile go to settings and search for "Pair using QR code" and scan the QR code
NEW UPDATE 2: (Latest Answer without using USB cable at all)
Note: It will work only when your laptop and mobile should connect to the same WiFi.
Go to developer options from the mobile settings and enable Wireless Debugging
That's it!
Had same issue, however I'm using Macbook Pro (2016) which has USB-c only and I forgot my adapter at home.
Since unable to run adb at all on my development machine, I found a different approach.
Connecting phone with USB cable to another computer (in same WiFi) and enable run adb tcpip from there.
Master-machine : computer where development goes on, with only USB-C connectors
Slave-machine: another computer with USB and in same WiFi
Steps:
Connect the phone to a different computer (slave-machine)
Run adb usb && adb tcpip 5555 from there
On master machine
deko$: adb devices
List of devices attached
deko$: adb connect 10.0.20.153:5555
connected to 10.0.20.153:5555
Now Android Studio or Xamarin can install and run app on the phone
Sidenote:
I also tested Bluetooth tethering from the Phone to Master-machine and successfully connected to phone. Both Android Studio and Xamarin worked well, however the upload process, from Xamarin was taking long time. But it works.
This might help:
If the adb connection is ever lost:
Make sure that your host is still connected to the same Wi-Fi network your Android device is.
Reconnect by executing the "adb connect IP" step. (IP is obviously different when you change location.)
Or if that doesn't work, reset your adb host:
adb kill-server
and then start over from the beginning.
If usb is not working you should checkout debugging over bluetooth (Without Rooting)
http://zcourts.com/2013/07/19/android-debugging-over-bluetooth-without-root/#sthash.hVCLtWSk.dpbs
type in Windows cmd.exe
cd %userprofile%\.android
dir
copy adbkey.pub adb_keys
dir
copy the file adb_keys to your phone folder /data/misc/adb. Reboot the phone. RSA Key is now authorized.
from:
How to solve ADB device unauthorized in Android ADB host device?
now follow the instructions for adb connect, or use any app for preparing. i prefer ADB over WIFI Widget from Mehdy Bohlool, it works without root.
from:
How can I connect to Android with ADB over TCP?
Connect android phone without using USB cable except XIAOMI PHONES
== MAKE SURE THAT YOUR PHONE HAS USB DEBUGGING ENABLED ==
== IP Address series should NOT be '0' like 192.168.0.10
1. Connect your PC (Laptop) and Android phone to same wifi network.
2. Go to the Android SDK folder > platform-tools and open command prompt by holding the shift key and right clicking on the folder.
3. Type the command "adb tcpip 5555", and hit Enter, sometimes it gives an error but ignore it and go ahead.
4. Type "adb connect [YOUR PHONE IP]". example: "adb connect 192.168.1.34" and hit enter, your phone will be connected to PC.
I've been trying to extract a logcat from a sonim xp7 device. I turned on developér options and USB debug, instaled the USB driver for windows and the adb from the android adk both on linux and windows, but in both systems when I type adb devices on the comand line (Already set adb as system variable) the return is nothing even with the device connected (Works for another device samsung s5 and a LG but not with the sonim xp7). Anyone knows how to make the adb work for this device?
I just got a Sonim XP7 IS device, and here is how I successfully installed the ADB interface driver on Windows 7 X64:
make sure you have got the Google USB driver from Android SDK:
This is how the phone shows in your device manager:
Select "Browse my computer for driver software"
]3
Right click on that exclamation marked device, select Update driver software. And choose "Let me pick from a list of device drivers on my computer". (Ignore the upper half's browsing for driver location stuff)
Select "Have Disk" button:
You can copy & paste the Google USB driver location here (On my computer it's "C:\android\sdk\extras\google\usb_driver"), you select "Browse" button and choose the location.
Now you have some option to choose, please choose "Android Composite ADB Inteface".
Probably you got a warning because of compatibility risk. Press "Yes" to confirm.
Now you need to confirm again to install this "Google Inc. Android Phone" device driver.
You have done the driver software installation for: Android Composite ADB Interface.
Go back to your device manager and double check the device "Android Composite ADB Interface" is working now.
Now go to command prompt, type "adb start-server", your phone probably will prompt for RSA fingerprint confirmation, remember to select "Yes" otherwise the adb device list will show it as "Unauthenticated".
If you don't see the fingerprint confirmation prompt on the phone, unplug the cable, and plug it again, it should come, double check with "adb devices" in command prompt.
Download universal adb driver from the following link
http://googleweblight.com/?lite_url=http://adbdriver.com/&ei=Ho-htPxw&lc=en-IN&s=1&m=853&ts=1435775034&sig=AG8Ucul1mSgYkNHuK-mv8n8xYcMkCw3JOw
Open the driver software, keep ur device connected with system.., and install the driver.
Now close the command prompt, open again and check with adb devices command.
Since my android phone does not connect via usb to my pc anymore (it just start charging), i would like to know if it is possible to install/debug apps (using Android Studio or Eclipse) via wifi (my device is NOT ROOTED). I have another phone (LGP690) that is configured to be a wifi hotspot. My PC and the other smartphone (an LG P880, the one with usb connection problem) are connected to it. Note that the LGP690 phone can be connected to my PC via usb.
Have you tried doing any of the options below with your LG P880?
Connect your cellphone to your computer
Right click on your My Computer and go to Properties then Device Manager
Look for your device (It may be under Other Devices or under a separate branch maybe LG)
When you find the device, right click on it and select uninstall
In the meantime, you can go to this link and download Universal Windows ADB Driver (This one worked for me) or if you want to use the one you downloaded from SDK Manager, just go to: C:/Users/(Username)/AppData/Local/Android/sdk/extras/google/usb_driver
When you finish uninstalling the driver unplug it and plug it back in so the computer can recognize the device.
When the computer recognize it, go back into device manager and look for the device that has an yellow exclamation point.
Right click on the device with the yellow exclamation point and click Update Driver Software...
When the update driver window shows up, click Browse my computer for driver software
If you downloaded and installed the Universal ADB, the you must direct the path to C:/Program Files (x86)/ClockworkMod/Universal Adb Driver/usb_driver if not then to the other path which is the one I mentioned above
Wait until installation finish then restart the computer (Optional) then give it a try.
Connect android phone without using USB cable except XIAOMI PHONES
== MAKE SURE THAT YOUR PHONE HAS USB DEBUGGING ENABLED ==
== IP Address series should NOT be '0' like 192.168.0.10
1. Connect your PC (Laptop) and Android phone to same wifi network.
2. Goto Android SDK folder > platform-tools and Open command prompt holding Shift key from folder.
3. Type command "adb tcpip 5555", and hit Enter, sometimes it gives error but ignore it and go ahead.
4. Type "adb connect [YOUR PHONE IP]". example: adb connect 192.168.1.34 and hit enter, Your phone will be connected to PC.
I have a G-Tide E56 running android 2.3.9
The "adb devices" command can't find my device , I've tried all the solutions I've found
for other devices but still no result, because I can't find a single answer regarding the G-Tide E56 specifically. Can any one point me to start. I'm Using a mac running OSX 10.7.4
Things I've tried:
1. check USB debugging enabled on the device
2. update adb
3. restart adb (kill-server, start-server)
The USB mass Storage is working perfectly so I'm sure there is nothing wrong with the USB port
Be sure that USB Debugging is enabled on the device
Windows Key + R -> devmgmt.msc
Find the connected device and right click
Update Driver Software
Browse...
Let me pick...
Next...
Have Disk...
%AndroidSKDLocation%/extras/google/usb_driver/android_winusb.inf
Open
See if this works, this will try and use the Android SDK Default ADB driver.
EDIT My DROID4 will only work in ADB connected mode if the USB connection is set to type MTP / Media Device, so try chaning you USB Connection modes and running adb devices while in each one.
Have you tryed going to were your adb.exe and clicking it. it will run really fast than dissapear worked once for me.Aldo another time I had to go into the task manager and kill the currently running adb
The USB drivers can be found in your sdk manager under extras