Go into settings > about phone Toward the bottom of the list, you'll see an entry for "Build Number" Tap it 5 times and you'll see toast pop-up letting you know that the Developer Options have been enabled. Go back to the main options menu and tap Developer Options and you'll see a tick box for USB Debugging about halfway down the list.
I have had this happen multiple times on multiple Android devices. Solved every time by putting the device in Photo transfer (PTP) mode.
ADB will not work for me when my device is in MTP or any other mode.
I got it to work :)
NOTE: This requires unlocked bootloader.
Connect the device to Mac or PC in recovery mode. (I had to map the
process in my mind as the screen was broken).
Now open terminal/CMD in computer and go to platform-tools/. type
and enter ./adb devices to check if the device is connected in
Now type ./adb shell mount data and ./...
My SAMSUNG Galaxy S4 sometimes bothers me with this annoying offline status message too.
I always fix it by trying options below:
Try to revoke the USB Debugging authorization on Developer Options menu.
Try using adb kill-server and the adb usb commands.
Try to replug your device if none of above works.
Try Restarting your device.
Turn USB Debugging OFF and ...
If the question is simply "using the command-line"
Let it be simple (root possibly required):
settings put global development_settings_enabled 1
settings put global adb_enabled 1
And then you need to
echo "mtp,adb" > /data/property/persist.sys.usb.config
If you want to do this without touching your phone
Then I'm feeling interesting because in ...
The workaround was to set the desktop backup password under Developer settings. It seems there is a bug in backup process. If you didn't set a desktop backup password under the developer options settings the above problems occur and your backup will eventually be incomplete(empty backup file). However, I couldn't find an official source for this bug report ...
I found the solution: Assuming you have debugging mode enabled, you have to change the USB settings to Internet Connection: Modem or ethernet. Keeping it on Charge Phone, Media Sync, or Camera does not enable debugging.
I found the missing pieces of the puzzle were installing the Java SDK & Android SDK.
I came across this because I couldn't connect to the "adb interface" - the Android remote debugging instruction page never mentioned installing an SDK, so I Googled "how to set up adb interface", and I found this page on How To Geek.
After installing the Java SDK & ...
Details for that can be found in our usb-debugging tag-wiki (where I've just added them):
By default, USB debugging is disabled with stock ROMs (some custom ROMs however have it enabled by default). To toggle it on or off, you can find the corresponding switch in Settings › Development – a section originally hidden with Android 4.2 and up. You can make ...
I am not sure if you ever solved this problem, but I ran into this problem, and tried out many many different procedures, each of which might have helped others, but this is 2016 and a summary might help.
A brand new phone bought in 2016 didn't work when I installed Android Studio on Linux. A phone bought in 2015 worked without a problem. A new phone didn't ...
Here is the documentation on usage of the adb utility.
Basically, adb connect is only needed if you are trying to connect to a device over TCP IP, i.e. wireless network. You don't need to issue any "connect" commands for a device connected via USB if it is already recognized in adb devices prompt. Just issue any other command, e.g. adb shell ls /sdcard/ ...
You need to include the port number.
adb -s 192.168.60.69:5555 shell
If you're using a sensible shell with configurable tab-completion (i.e. not Windows), then you can type adb -sTab to get a list of devices.
On production (user) build of a ROM, you can't start adbd as root unless ROM or at least adbd binary is rebuilt with required modifications. Reason is the ALLOW_ADBD_ROOT build flag (1, 2).
That's why adbd Insecure was developed, which replaced the adbd binary with a modified one.
On a userdebug or eng build (or with insecure adbd binary extracted from any ...
You can see which devices were authorized by you on your phone to interact with it through adb. You would need root access though.
Go into the directory /data/misc/adb/. There would be two files:
adb_keys shows the public key of the other device followed by its user@machine name format. The user@machine should tell you which ...
The easiest way to get this driver is from the samsung website. There is a link to a download that installs only the driver (none of the bloat).
See https://stackoverflow.com/a/11851697/1427165 for more details.
Based on OP's clarification done in the comments below Izzy's answer, I propose the following solution if one's device is locked out and ADB is not enabled under Settings.
Note that this method is tested on Stock Android 4.2.1 and Stock CM 12.0 (Android 5.0) , both devices having custom Recovery (ADB always enabled as default) . If your Stock Recovery ...
For the RSA verification that you asked to bypass, I don't know whether it would work in your device, but it worked in my little experiment. In Lollipop, the ADB keys (after authorization) are saved in /data/misc/adb/adb_keys. Your private key is saved in computer. In Linux the directory location is $HOME/.android/. On Windows that usually translates to %...
Check adb devices. If no device shows up follow the steps below.
First, check to make sure USB Debugging is enabled. On most devices:
Go into 'About Phone', 'About Device', or 'About Tablet'
Find 'Build Number'. It's location varies from devices to device, but look for menus such as 'Software Information'
Tap 'Build Number' until you see a message saying '...
To make one of eldarerathis' cons less critical:
One could use Tasker or Locale together with the Secure Settings plugin to automatically toggle USB Debugging on for safe locations (based e.g. on cell towers, network/GPS location, WiFi networks connected or in reach), and toggle it off (exit-task with Tasker) when leaving such. With a NFC tag and the Locale ...
There was (and still is) such a tab. It's called File Explorer, and by default it shows up in the same part of the screen as the Threads and Heap views. If you've hidden it in the past, you can show it again from the Window menu → Show view, or by pressing Ctrl+3. (Thanks to Edgard Leal for suggesting the keyboard shortcut.)
The user44860 answer is almost correct. Goto Settings, About Phone, Software Information:
Click Build Number 7 times. You should see a message saying that now you're a developer.
So, you can go back and enabe USB Debugging in the Development Settings.
Maybe you've to detach the usb cable, enable the debug and re-plug the usb cable.
The PC Software setting is just for installing and using the LG PC software. Once your drivers are installed, enable USB Debugging, plug it in, change it from "charge only" to "MTP" and USB Debugging should work.
As it turns out, the issue was that my phone was no longer being recognised as a composite USB device by Windows, meaning only one of ADB, MTP or HTC Sync was capable of running at a given time. After the update, MTP was always recognised first. This explains both the 4.3 issue of MTP and ADB conflicting, and the 4.4 issue of no ADB.
The solution was ...
I figured this out on my own. I solved this by installing Airdroid using an OTG USB adapter and a wired mouse. I then used the airmirror capability of the software to control a virtual mouse on the device. I do have root on the device, this may be significant to the operation of Airmirror. I could then accept the debug confirmation on the screen and complete ...
Actually Windows Experience Feature is the answer!
I had the same problem and could not install usb drivers for a MotoG on a win2012 Server, but when I installed Desktop Experience feature, all runs flawlessly, drivers auto-installed and all!
BUT it is a little weird to find it...
Server Manager -> Open Add Roles and Features Wizard -> Features -> ...