Tag Info

New answers tagged

0

You should be able to use ADB as far as it is just a tunnel to the Android device's shell. MTP (Media Transfer Protocol) is not connected to ADB apart from the fact that they share the USB connection. Just try it out, it shouldn't harm your device.


1

First go to settings->Apps->Your app->move to SD Card. Then follow these steps: First download ES File explorer Search for the app's folder on the SD card. If you cannot, go to the Android folder->DATA->Your app. OR go to Android->OBB->your app. If you cannot find the folder, the developer ought to help you, especially since you are ...


0

After 3-4 days of trial-error I've found what's the source of the issue... It has something to do with virtualized ethernet adapter hardware. When I switched to Virt IO and I installed the driver in my Windows 7 guest machine, ADB has started to work as expected! Conclusion: if you want to debug Android apps from a Windows guest to an emulator or device, ...


0

For rooted devices: Run the below command adb rm -rf /data/data/<your.package.name> For non-rooted device: Change the ApplicationId of the app. Refer this link to change ApplicationId. Build and install the app. App will install successfully because it is treated as new app. Now uninstall this app. Which will clear the data. Now change the ...


1

Well, since the FileManager.apk package resides in a /system/app/ directory it is a system app. So the general way to remove it is: adb shell su mount -o rw,remount /system rm -rf /system/app/FileManager.apk rm -rf /data/data/org.openintents.filemanager mount -o ro,remount /system exit exit


0

Try adb shell command. It gives you super user permissions in the connected device.


0

I was having the same problem.I tried this http://myandroidteacher.blogspot.in/2014/07/fix-fastboot-problems-on-windows-8-and.html


1

I have put together some build scripts to compile SQLite for Android Native Code using the Android NDK. It builds the SQLite CLI in two versions: Statically and Dynamically Linked, as well as it's Static and Shared Libraries. You may get the scripts from my GitHub and build the binaries yourself: https://github.com/stockrt/sqlite3-android Hope this will be ...


3

here is an another method, go to android shell then shutdown the phone! adb shell shutdown


2

If it helps, I found ADB.exe here in a new Android Studio 1.0.2 install: C:\Users\USERNAME\AppData\Local\Android\sdk\platform-tools


0

your device manager is showing that the adb drivers are not properly installed. If properly installed there would be no question mark by the left of the icon. I found the following steps in this article here First of all you have to Enable the USB Debugging in the Developer settings. Connect your tablet to the computer USB port. Select MTP connection ...


0

try using adb reboot-bootloader from the adb usage text adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program adb reboot-bootloader - reboots the device into the bootloader


0

You may be able to restore apps and data as far as they are no system apps. But be sure to fix permissions (Owner, Group and access) to what the system uses for all files (data and apps). I already did this on my SIII LTE for an upgrade of Android 4.4.4 (CM11) to Android 5.0.1 (CM12) with no side effects (except some single apps that deleted and recreated ...


0

I just spent way too many hours trying to fix this same problem when trying to sideload onto my Nexus 6. What finally worked for me: Apply update from ADB in the recovery menu. Once the phone was waiting for the files I unplugged the phone from USB then re-plugged it back into the computer. Then it was there in the device manager and when I did a ...


1

During recovery mode, adb will be running as root so any file you push will have root as owner and group. Once your device boots up, you cannot see those files because they are not under media_rw and sdcard_r.


-1

what worked for me was to restart the phone and the damaged message went away!


0

Set the device in "no lock" mode in security settings (lock settings in some android versions) so that after reboot the OS goes straight to the home screen. You can then send any key event, best an unrecognised one so it's not handled by the default handler, to wake up the screen. EDIT: This works fine on 4.1. I checked on 4.4 and events other than 26 do ...



Top 50 recent answers are included