Tag Info

Hot answers tagged

11

Yes. The command is pm disable <package name>. You must be root in order to do this: PC> adb shell shell@hammerhead:/ $ su root@hammerhead:/ # pm list packages -e | grep 'calculator' package:com.android.calculator2 root@hammerhead:/ # pm disable com.android.calculator2 Package com.android.calculator2 new state: disabled root@hammerhead:/ # pm list ...


10

What fixed it for me was clicking on the "Connected as a media device" up at the top left corner, de-selecting Media Device (MTP) and then checking Camera (PTP). This essentially made it show up as a different kind of USB device with different options and allowed the process to work perfectly.


8

I just did this! /data/property/persist.sys.dalvik.vm.lib is a textfile containing one of two values: 'libart.so' or 'libdvm.so'. You can change from ART to Dalvik simply by editing this file. Ex: adb shell 'echo libdvm.so >/data/property/persist.sys.dalvik.vm.lib'


7

There is no way to get Gingerbread to prompt the host to verify RSA key as that is found in newer versions of Android (Jellybean 4.1 and upwards). The only true method of hardening ADB in the sense of prevention of communicating over the USB is to modify the kernel for that appropriate device and disable the USB functionality within it in such a way that ...


7

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.


6

Chor WaiChun mentioned this on a locked question you posted on StackOverflow: I've seen somewhere stated that this behaviour is because both android and linux run on same kernel, and same situation goes to developing android on mac. Both OS runs in very similar OS kernel with Android, that is why they don't need any drivers. These are just ...


5

You don't have to uninstall, when you install an app already installed, you have to use adb install -r. (for more help, juste type adb) To uninstall an app, you have to use adb uninstall package-name (e.g. adb uninstall com.example.app).


4

This line will do it (found here): awk '{print $1}' < ~/.android/adbkey.pub | openssl base64 -A -d -a | openssl md5 -c


4

There are two ways. The simpler one is to use a legacy market://details?id=com.shadowburst.showr URL instead of https://play.google.com/store/apps/details?id=com.shadowburst.showr. No browser will offer to open a market:// URL, but it's still possible that another installed app will do so. The more complex way is to explicitly specify what activity you ...


4

Personally I had to run fastboot as root/sudo for fastboot to detect the device. I tried this on Linux as I don't own a Mac, but it's *NIX anyway ;)


3

Got the same issue, and fixed it by updating the driver from the ASUS usb_driver_r06_windows.zip driver pack. The issue is that this driver does not report properly the supported devices (at least mine were not listed) My device is reported as a PID 4EE2 which is not part of the supported devices. I had to add the following lines in the android_winusb.inf ...


3

By default stock Android mksh uses this config file: /system/etc/mkshrc


3

It's not enough to make the Developer options page appear in the settings menu (by repeatedly tapping the build number). On that page, there's an option USB debugging, which defaults to off. When USB Debugging is enabled, connecting your device to a PC using USB makes the "USB debugging connected" notification appear, regardless of whether adb is currently ...


3

The command is mount -o remount,rw /system


3

Quite easy: find / starts exploring at the file system root (i.e. the very top). So it comes to places you have no access to as normal user, and runs into permission issues. It sees a directory called /proc/19619 and, knowing this is a directory, wants to traverse into it. But it is not permitted to (most likely the permission of that directory is something ...


3

You don't use adb to connect to a device when it's in the bootloader menu: you need to use the fastboot command instead. That's why it's called "fastboot mode"! Not all phones support fastboot: in particular, older HTC phones use a proprietary protocol called HBOOT instead, but I think the newer ones support fastboot.


3

Not from within Android, no. Only root can mount or remount filesystems, including /system. There is another way, which is to go outside of Android completely by making the change you want from the recovery. Since the recovery doesn't use Android's permissions system, it can let you mount whatever filesystems you like, however you like. But if you're going ...


2

the -s should be before the 'install'


2

You could check whether there's a way to disable Keyguard (there must be some intent to use, as many apps like e.g. Tasker support that). That would turn any keylock off. One example how to do that I just found at Google Groups. First, that thread says the keycode should be 59 (keycode.KEYCODE_SHIFT_LEFT), but then also offers alternatives like: $ adb shell ...


2

To uninstall the package using adb, you need to use the package name listed in the manifest, for example: adb uninstall com.shadowburst.showr You might also want to use the -k option to avoid deleting the app's data when uninstalling. You can also uninstall apps from the Settings app: click Apps, find your app in the list, then click Uninstall. This ...


2

If the device in question is rooted, you can write to the system settings directly from a shell command in adb shell. The name of the setting to write depends on which Android version you have. If your device isn't rooted, you can't change the USB debugging setting from adb or any non-system app.


2

Try to switch the device into PTP mode (under Settings -> Storage -> USB Computer Connection and manually select the connection mode...) and connect to computer. Let it install, switch back to USB mode and plug in again. Update: XDA tread


2

Additionally to what @Alex-p wrote, you can set the ENV environment variable to override the path of the mkshrc file used. All login shells also read /system/etc/profile and $HOME/.profile (these are a good place to export ENV). Disclaimer: I’m the mksh maintainer.


2

You probably need to root it to gain access to the protected "/system" file system. XDA Developer's has a (probably) outdated thread how to do it here. After you suceeded, you can take the usual steps to mod it (remount /system read-write, copy your edited file over, etc.)


2

You can't install a ROM using adb install, just like you can't install a fresh Ubuntu system with apt-get. You use fastboot to install new ROMs, when the device is in fastboot mode. Instructions are different for each device, and the ROM you downloaded should come with them. Regardless, from the symptoms you describe, it doesn't sound like installing a new ...


2

You wont be able to pull a "protected app" without root, sorry. This has nothing to do with the app being payed, except that usually only payed apps are "protected" (theoretically, free apps could be "protected" as well); think of it rather as a kind of "DRM". Once your device is rooted, you can use "root powers" to pull those .apk files. This can be done ...


2

Logcat displays Android's logs. This is by definition information about things that happened in the past. Android's logs are stored in a ring buffer and if full, the then oldest entries are overwritten. It depends on how much is being logged, when that happens. Besides this, the buffer is reset when you restart the phone, so logs cannot be older than the ...


2

If you can get to recovery you should be able to flash the full factory image which will restore your phone to completely stock. Download the full occam factory image, which includes the full system, bootloader, recovery, kernel (boot.img), and radio. It's a clean slate for these components - they'll flash cleanly over anything you have now. You can run ...


2

The problem is that you're missing the adb recovery driver. You might consider trying Koush's universal USB driver installer -- it solved this very problem by installing the missing drivers.


2

For future reference, this was my related case (involving a Nexus 4): I tried to bring my phone back to the original state (bootloader locked + stock rom). Now fastboot devices did not show the device where adb device did, until I put the phone in fastboot mode (this makes sense, but took me a while to figure out...) To put the Nexus 4 in fastboot mode: ...



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