Hot answers tagged

16

Short Answer Try using an earlier version of adb. 1.0.32 did not work for me, but 1.0.31 did. Long Answer I just encountered this issue on a Nexus 5 running CyanogenMod 11 (based on Android 4.4) using the current version of the Platform Tools and ADB (Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android). Using adb logcat to watch the ...


7

I got it to work :) NOTE: This also requires your device to be rooted. (Thankfully, mine was rooted) 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 recovery mode....


6

I have not tried this myself, but there's an app named ADB Wireless (no root) which, as the name suggests, claims to make this possible without involving root: This app is for developers wanting adb access over WiFi without rooting your phone. … *** NO ROOT REQUIRED *** Usage instructions can be found on the app's playstore page – looks pretty easy ...


6

The other answers about the command arguments being quoted is accurate. I've found that if you escape the spaces between the arguments, it works. Like this: adb backup -apk\ -shared\ -all\ -system


6

The workaround was to set the desktop backup password under Developer settings. It seems there is a bug in backup process. If you din't set a desktop backup password under the developer options settings the above problems occurs and your backup will eventually be incomplete(empty backup file). However I couldn't find an official source for this bug report ...


6

Try the 15-seconds ADB/drivers all-in-one installer. You could also install the Samsung drivers rather than conventional OnePlus drivers. I installed these drivers and I've had mine working since the upgrade. You could also try following this guide on how to set it up.


6

If you need to do something that requires root privileges, your device must be rooted. You can't circumvent this via ADB because what ADB does is to provide a shell on your host machine through which you can run commands on the Android device. So essentially you are running commands on your device through your PC. Hence you can't do anything that requires ...


5

This is not a final answer, as it is not generic (only works on some devices) – but it's a start at least: As we've figured out, at least CM based ROMs with Kitkat (Android 4.4) and above ship with the aapt binary available in /system/bin1. If your ROM doesn't have it, and installing the binary on the device is an option, you can find it here. Using aapt, ...


5

The fix for me was using a different micro-usb cable. No software change, no drivers to update, just the usb cable. Apparently they aren't all created equal.


5

As described by ss-3-1415926535897932384626433 there is no flag, but you have to get a list of files first and then check if your local files match. I wrote a little script for it: #!/bin/sh rfolder=/sdcard/DCIM/Camera lfolder=Camera adb shell ls "$rfolder" > android.files ls "$lfolder" -1 > local.files rm -f update.files touch update.files while ...


5

As for the first part: Yes, that definitely means your device is rooted. For the second part of your question, IMHO it's close to impossible to figure the exact timestamp of rooting (apart from yourself noting it in some document). Though there seem to be tools reporting it, as mentioned in this answer1, I'm afraid that timestamp is not much reliable (...


5

Easy to do – as in any Linux system: Connect your device as usual log into it using adb shell use the ls command to list files in the current directory, and the cd command to change directories (i.e. walk the tree / navigate through directories) For details on the commands, check for the corresponding Linux man pages – e.g. man ls and man cd. Edit: If ...


5

Note: The solution is tested on Android 4.2.1, 5.0.2 and 5.1.1. The value for the system property persist.sys.safemode determines whether the phone should boot into safe mode or in normal mode. When booted into Android OS, provided root access, the value can be changed as adb shell su -c 'setprop persist.sys.safemode 1' adb shell su -c 'echo "1" > /...


5

Yes. All you need to do is test for the presence of the file that enables it. On devices that do: # adb shell ls /system/etc/permissions/android.hardware.usb.host.xml /system/etc/permissions/android.hardware.usb.host.xml And otherwise: # adb shell ls /system/etc/permissions/android.hardware.usb.host.xml /system/etc/permissions/android.hardware.usb.host....


4

To add to Jared's answer (can't comment - not enough reputation yet :/). This works with the emulator only so I wrote an app you can run on a real device and it provides exactly the same interface (telnet to :5554 and run "geo fix ..." or "geo nmea"): MockGeoFix


4

15 seconds minimal ADB, fastboot and drivers installer. No need to navigate to the installation folder in CMD. It can be installed system-wide. No need to check for manufacturer specific drivers. Everything included in 9MB.


4

in that App Info (though grey out), click the three vertical dots and use Uninstall for All Users.


4

Running an APK without installing it? No matter if you won't accept the answer, running an APK is not possible. It's not an executable, it's an archive containing the application and instructions on where all it's resources should be placed so that the app can run. Android APK File Format Asking this question is the same as asking how you run an iso ...


4

Enable USB debugging on the device This is done in Settings › Development. If you don't have that entry in your settings menu, go to Settings › About, scroll to the "Build number", and hammer it like a monkey until your device congratulates you having become a developer. Go back to the main page of the Settings menu, and close to the bottom you should see ...


3

Building on kevenoid's answer, it may depend on what version of adb is running on the phone. You can find out what version the phone is running natively by doing the following: First find out what version you are running on your desktop adb version Then open the shell on your phone adb shell Once the shell is open then you can run adb version ...


3

Non-Rooted Solution: Enable USB-debugging in the developer setting and connect your phone to your computer via USB. Run the adb command, adb tcpip 5555 (Make sure port 5555 is not blocked by any firewall programs) To get your Wi-Fi IP address assigned to your device, adb shell and then netcfg and run the adb command adb connect <IP_ADDRESS>. For ...


3

You may check-out my updated answer dealing with the question in entirety, or consider the following info: High accuracy: gps,wifi,network or gps,network (if you don't want Wi-Fi enabled) Battery saving: wifi,network or network only Device only: gps E.g: adb shell settings put secure location_providers_allowed gps,wifi,network To disable Location mode ...


3

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 %...


3

On your device, Go to Settings > About Device and repeatedly tap "Build Number" until it says you're a developer. Then go back to Settings and into Developer Options. Turn it on and check the box for USB debugging. Then Revoke USB debugging authorisations. Now, connect your device, install its drivers if you haven't and type any ADB command. A message will ...


3

First make sure that you have virtualization on in the BIOS. Next, make sure you have done what I have done in my question. What I forgot to do was install the android_winusb file in the usb_driver folder. The path should be sdk\extras\google\usb_driver. In my case, C:\Users\Ruchir\AppData\Local\Android\sdk\extras\google\usb_driver After doing that, go ...


3

There is always a lack of documentation because the drivers are device specific so you need to find documentation for your specific device. You can try using Universal ADB Driver, but the best solution is to install a companion app for your device, something like Kies for Samsung, as they usually install drivers alongside. To know if ADB is installed - it'...


3

As Firelord asked me to sum things up, here we go: First, you cannot do a backup using fastboot. Fastboot is like a one-way road: you can only use it to write partitions (either by flashing a corresponding image, or by wiping it) – but you cannot "pull" a partition. Which leaves ADB. Yes, it's possible via ADB – but it will require root. As Firelord ...


3

Install the Google Driver while in phone is booted to bootloader. Those are in your SDK folder location - extras - google - usb_driver. When my N6 is booted to bootloader, Windows 10 shows me the following: Win10 Device Manager screenshot


3

If the OTG drive is plugged in at the time of the command, you can also detect OTG by querying these directories: /storage/UsbDriveA (Samsung devices) /storage/USBstorage1 (LG G4, V10, G3, G2, LG devices) /storage/usbdisk (Moto Maxx, Turbo 2, Moto X Pure, Motorola devices) /storage/usbotg (Sony Xperia devices, Lenovo Tabs) /storage/UDiskA ...


3

Addressing Revision 4 You're still doing things incorrectly even though I noted in revision 1 of my answer that you would need adb in PC for once and once alone as long as no reboot or disabling of USB debugging occurs. Regarding your attempt: u0_a192@klimtwifi:/ $ adb connect localhost:9999 * daemon not running. starting it now on port 5038 * * ...



Only top voted, non community-wiki answers of a minimum length are eligible