Tag Info

New answers tagged

-1

I didn't add, I erased the all line. Now I don't know what to do? Which is the original line??? I need help. Please.


1

Here is the home project page for adb and fast boot install for Mac from Google. Here is the download page from the same source. description this script installs ADB and Fastboot to /usr/local/bin/ on Mac OS X. You can uninstall using the Uninstall ADB.sh script provided. how to install from terminal Run ADB Install Mac.sh from Terminal ...


0

Have you tried this app from Chainfire? https://play.google.com/store/apps/details?id=eu.chainfire.liveboot From the description, it shows a logcat of the boot process over the boot animation.


1

My Asus Nexus7 (2012) will not show with lsusb, not with any of the 5 cables that with my nexus4 show fine. Usb port works for charging and I can read usb stick with specific cable and application, so presumably the usb port is working fine. I have added several versions of udev rules and tried connection in usbdebuggin mode, normal mode even fastboot mode ...


1

Well with the boot loader unlocked you can temporarily boot up into recovery by using fastboot: fastboot boot recovery-clockwork-6.0.4.7-mako.img This will then give you adb access to your device to get files off etc. The adb debug mode could then be turned on by editing a settings file and copying in the crypto keys generated by adb on the host computer. ...


1

If you're on Linux, Adebar contains a tiny little shell script to convert ADB Backups (.ab) to tar files, which you then easily can investigate with any archive manager. Only limitation is: it doesn't work on password protected backup files. The basic command it runs (everything else mainly is a wrapper for command line options and syntax) is: dd if=$1 ...


0

Have you enabled developer options in your mobile? If yes, then navigate to Settings > Developer Options(turn it on) >and select(or check depending on your phone) USB debugging this should work


0

Try disabling "Connected as a media device" (unmounting storage). On your device, you should be able to select the notification and then select an option like "Charge only" to disable the mount. You may have to go to Apps > Settings > Storage > Menu (button) > USB computer connection to change the setting.


0

That device doesn't have a button configuration to boot into recovery. You are going to have to run sh reboot-recovery.sh from the SDcard, (posted in my original answer) after your device gets past bootloader.


1

Real Reboot Works on Android 2.1 - 4.2.1 No Root 4.2.2 and up needs root. For a PC method you will be using Android Debug Bridge, commonly called ADB. Here is a link for a download. It's from the XDA Forums. Read the page while your there and get some good insight on ADB. After installed to the computer, open a command prompt (L shift + R mouse click) ...


-1

If you're rooted : Just search for any app that restarts the phone. Just search on play store - "Restart". That'll do the work... If you're not rooted As HasH_BrowN told, adb is the solution. The first step is to have USB debugging turned on, which you have. Now, follow these steps : Install adb and your phone's drivers on your PC/Mac/Linux ...


2

Though not directly related to your question, this does answer it in a very round-about way. I found this blog which gives directions on how to open the file and modify contents. My reasoning is that if the file opens then it should probably be ok. Here's the link: http://nelenkov.blogspot.in/2012/06/unpacking-android-backups.html I'd really love if anyone ...


0

if you got samsung phone (with non modified ROM) try this fully free app https://play.google.com/store/apps/details?id=com.ospolice.packagedisabler&hl=en_GB no rooting needed


0

Try running commands as root from your adb folder: sudo ./adb kill-server; sudo ./adb start-server; sudo ./adb devices


0

The app's file has been modified in some way, changed or removed. Look up your build number in settings and search for it on Google. Hopefully you'll find a zip with .img files in it. If you've got the correct img files, reflash system.img and you're able to flash the ota.


0

The legacy/ locations are always pointing to the data of the currently active user. Let me first point to a few related questions/answers explicitly dealing with those multi-user storage issues for some background: Why did /sdcard/ turn into /sdcard/0/ with 4.2? Confusing internal memory folder structure So to find the files of the secondary user: list ...


2

Since you have a .tgz file, I would assume you downloaded the factory image for your device. You cannot use adb sideload with those archives. They are not packaged for that. You note in your comment: The instructions also said to do it as a .zip ...and the instructions are correct. If you find that your environment is deviating from the stated ...


1

You can use as many emulators on the same machine as you want, simultaneously, at the same time, there's no actual limit, as long as you have sufficient RAM in your computer to handle that many emulators. When you want to debug an app you just choose whichever emulator you need.


1

This cannot be done without unlocking the device. If the touchscreen still works try to boot the device, let it settle, press the power button to wake it up and then draw the pattern from memory. You can print a photo of the phone on the lockscreen and mark the point on the display as a reference.


0

Issue 62198 - android - FAILED (remote: (InvalidState)) - Android Open Source Project - Issue Tracker - Google Project Hosting


2

adb logcat outputs the BackupManager activities, so you can monitor if the process is running or stalled. Since adb logcat produces lots of logs from other processes, it is not easy to watch BackupManager logs. The easy way to watch BackupManager output is to use grep. adb logcat | grep BackupManager will filter only BackupManager logs.


3

If your device is rooted, as it probably is with CM, you can also do this via adb: adb shell rm /data/misc/adb/adb_keys Depending on your build you probably have to run adb as root(1) or call the su binary(2). (1) adb root or adb kill-server; sudo $(which adb) start-server --> adb shell rm /data/misc/adb/adb_keys (2)adb shell --> su --> rm ...



Top 50 recent answers are included