I bought a new Samsung Galaxy Tab GT-P6200 for developing android application. When I connect my tablet device to the system(with Ubuntu 11.04 OS and with Eclipse ), it doesn't recognize debugging mode even I enable debugging mode in the settings. It automatically connects to MTP-mode(Media Transfer Protocol), and I cannot view the folders in the sdcard. Someone please help me to connect my device in debugging mode.
Have you try restarting the adb server?
Open a Terminal, go to your android-sdk/platform-tools folder and execute:
./adb kill-server
then start it again with root access
sudo ./adb start-server
I remember I faced this problem before. You should try to following:
Check if you have install driver for it(in Help/Software Updates of eclispe)
Also, sudo ./adb kill-server sudo ./adb start-server check if it connected by sudo ./adb devices
Try with other USB port.
Hope it helps
Related
I need remote ADB shell..
I know that we have to issue "ADB tcpip ".. to change ADB server to TCP listening mode.
But, the problem is that my phone is not rooted, and I do not have USB cable.
I can't issue tcpip command since I do not have USB cable,,
I can't change default.prop file as the phone is not rooted.
Is there any other ways to change ADB server to TCP listening mode???
I found an articel that says you can execute setprop persist.adb.tcp.port 5555 to make tcpip mode autostart after reboot.
The problem is, you must run this command as root.
On my device unfortunally the command su doeas not exist.
Here is the orginal Permanent network debugging on android
EDIT: I discovered, that the su command is only available when your device is rooted.
So the solution only works when you have a rooted phone
The simple answer is: no, you can't.
As you said, you can't access the prop file and don't have a cable to change with ADB. The only way is you find the port via an Android terminal emulator (a.k.a Termux)
For anyone looking for a better answer:
YES, YOU CAN!!
When you try to execute "adb tcpip 5555" without an USB cable, it returns:
"error: no devices/emulators found"
Emulators?? After googling I found the way and made a batch file that connects my device directly through WIFI, no cables needed at all:
set /p ip= Device IP:
:CONNECT
if "%CD%"=="C:\" goto ROOT
cd ..
goto CONNECT
:ROOT
cd ...Android\Sdk\emulator
echo.
echo Starting emulator...
start /MIN emulator -avd Nexus_5X_API_29_x86 -no-window
(you can check other avaliable devices with "emulator -list-avds")
cd ..
cd platform-tools
adb wait-for-device
echo.
echo Emulator started.
echo Connecting with device...
adb tcpip 5555
adb connect %ip%
echo.
echo Closing emulator...
(you need it just to be able to execute "adb tcpip 5555")
adb -s emulator-5554 emu kill
(you can check the name with "adb devices")
To enable wireless debug need to configure the ADB command. (in mac os)
Step1:- First of all need to enable adb command. (check SDK tool and install command-line tools)
Step2:- connect the device with a USB cable after that run the below command.
command: adb devices
the above command will show a list of connected mobiles.
Step3:- after that, we need to configure TCPIP protocol:
e.g : adb tcpip 5556
Step4:- Run command to connect the device.
command: adb connect your_ip:port_address
eg:- adb connect 192.168.1.152:5556
If you are using the stock android os system, then you can enable remote debugging in Settting -> developer options.
I'm running adb on ubuntu, and my app (that I'd like to test) on a Galaxy S3. Got my S3 in debugging mode, I've edited /lib/udev/rules.d/51.android and .android files, restarted adb, and my laptop, but no luck. Any ideas what I might be doing wrong?
Try this on command prompt:
sudo -s
adb kill-server
adb start-server
Some more things you can try as I often find this helpful.
Check the Data Card, it might have problem.
Plug the data card to another port on the system.
I'm trying to debug an Application on a Xperia cellphone with Cyanogenmod installed, but it doesn't seem to recognize my cell phone. Also, adb seems to be gone, I followed http://developer.android.com/guide/developing/device.html the official guide, but when executing:
$./adb devices
on the plataform-tools/ directory the system doesn't recognize the device.
also I tried
$sudo ./adb devices
any ideas?
thanks to everyone for the help.!! I solved
the problem was that I needed to restart the adb server I did it like this:
$sudo ./adb kill-server
$sudo ./adb start-server
Is there any way to make a phone whose status is offline to online without replug the usb line?
Just copy an paste in notepad with a .bat extension.
Before that make sure your adb.exe is included in system path or alternatively replace the 'adb' with path to adb.exe, For example:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb kill-server
#echo off
adb kill-server
adb start-server
adb devices
cls
echo "Android Debug Bridge Restated!!!"
pause
Disable and enable again USB debugging on the phone. Works most of the time. You can also try restarting the adb server on the desktop machine.
There's an 'adb reconnect' subcommand I hadn't noticed before today: it might only be in the newer versions of adb.
There's also a device-side version, but I don't quite see how the local machine can tell the device to do that without already being connected, so perhaps that's something you can execute in a device-side shell.
I followed the tutorial to set up ZTE tablet device for development. I am developing under Ubuntu 10.04.
After create the rules file: /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="19D2", MODE="0666"
After I plug in the ZTE tablet device with debugging enabled. I run command:
adb kill-server
adb start-server
adb devices
I got :
List of devices attached
???????????? no permissions
I thought may be it is because I did not restart adb as root. SO, I tried to restart adb as root, and I entered the command in my terminal:
sudo adb kill-server , but I got the message in terminal that "sudo: adb: command not found"
But if I enter command without "sudo", that's "adb kill-server" it works.
Is it because my path setting is wrong?????
I set the path under HOME/.bashrc, with :
export PATH=$PATH{}:/home/user/android-sdk-linux_x86/platform-tools:/home/user/android-sdk-linux_x86/platform-tools
Conclude all above, I got two problems:
the adb listed device has no permissions
I can not run adb as root
My questions:
Are the problems all because of my path setting is wrong?
Is it because ZTE tablet device is different from mobile device? Some tricks need to be done for tablet??
something else?
Where am I wrong?
P.S. Since I lost the USB cable shipped with the ZTE tablet, I use a NOKIA USB cable to connect the ZTE tablet with my development Ubuntu machine, could this also cause the above problems???? (With Nokia USB cable, I can still access the ZTE tablet file system anyhow)
Every thing goes fine after I run the command:
sudo -s
adb kill-server
adb start-server
adb devices
Then my ZTE tablet is shown.