New answers tagged

0

Download ADB drivers from here. Extract somewhere. Now, go to Device Manager and select your ADB device. Update Driver Software > Search your Computer > Browse to the folder you extracted and let it install.


0

If you have apks in different folders (like if you used adb pull) then you can use my script: for /r %f in (*.apk) do adb install -r %f Just run it in the folder above all your apks and it will recurse and install all of them.


2

I got this one. Your cat listens for text, but... it keeps listening. You never signal the input termination, thus it doesn't create the file. Instead of the following lines: cat > test.txt test test 12345 test use these: cat << EOF > test.txt test test 12345 test EOF This will instruct cat to accept input until the End Of File is ...


0

Perhaps you could try out something like Assistant menu's cursor facility, Unfortunately, I am not sure where you could get one though. It's you phone's hardware that is not working right? If so, you could just make all touch events in upper half with such a software and emulate that touch occurred in lower half somewhere? You would (most likely) need ...


0

Issues like this this are often corrected by returning to a "known good configuration" before processing additional changes. I would suggest returning to the current official Google firmware via fastboot, then verify the device is booting and operating properly, then you can flash custom recovery and install a third party ROM such as CyanogenMod. ...


-1

This method will effectively divide your home screen in half, allotting each half to its own app and allowing you to fit a compact version of the app screen into the working part of your digitizer. It doesn't fix the issue of the keyboard, which when called replaces the bottom app, and obviously won't work. One easy fix would be to add a hardware keyboard ...


3

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


1

Update: This works from Recovery mode: - Full factory reset and then: - Apply Update -> From ADB .\adb sideload cm-13.0-20160510-NIGHTLY-mako.zip


0

This helped me, before step 13 "Enable USB debugging on the phone (Settings => About phone => Click 7 times on Android Build to unlock developer options)" make sure you have enabled MTP over USB on the phone. Sometimes it helps to revoke the approved debug devices as well.


0

In Android versions equipped with wm tool, you can use the commands: wm size # shows the real size and current size wm density # shows the real density and current density (Click image to enlarge) I've tested successfully on stock Android 5.x and 6.x. Since wm tool comes with Android 4.3.x and 4.4.x as well, the solution may work on them as ...


1

You can find the frequency of a device (as long as it was sold in the USA) by searching the devices FCC ID. This is a unique identifier used for authorizing the device to transmit at licensed frequencies. The Padfone X has two FCC IDs, so you will have to figure out which one applies (try checking under the battery cover): MSQT00S, MSQT00D


-1

I answer myself, just updated and everything has gone smooth! Nice!


2

After some trial and error seem to have managed to get it working, turns out it is a DNS issue. If anyone else has this issue then it turns out that you need some extra commands in order to get KitKat to work. I added these on to the end of my script posted above and I can now ping google and get pings returned: adb shell su -c 'ndc resolver setifdns ...


0

Unfortunately is impossible without root. You can however Root and if you have any problem that need go to fix it, you can Unroot the phone.


-1

Have you tried this? http://forum.xda-developers.com/showthread.php?t=1371345 It says it's compatible with lower than 5.0 android versions.


1

I found a solution (for windows): Download the official MEDION ADB driver for some other tablets they offer Unpack Open the android_winusb.inf file in a texteditor Add the following lines at the end of the two sections [Google.NTx86]up and [Google.NTamd64] ; ;MEDION Life E4001 %SingleAdbInterface% = USB_Install, USB\VID_109B&PID_911E ...


1

adb pull is for files. /dev/block/mmcblk0 is a block device. user1133275's answer to that question doesn't work; try the other one, i.e. run adb shell and then: $ su # dd if=/dev/block/mmcblk0 of=/sdcard/something.bin Then you can run adb pull /sdcard/something.bin.


0

You can flash a new recovery image with fastboot. The command is: fastboot flash recovery recovery.img where 'recovery.img' is the name of the image. If you enter fasboot on the command line with no options or parameters you will see the usage, which is: fastboot flash [partition] [filename]


1

I thought adb gives some sort of unrestricted temporary access (like temporary root). When you open an ordinary terminal emulator app, you're shown a terminal and are automatically logged in as a particular user. The User ID of this particular user is the user ID of your displayed terminal emulator app. Such user and app is considered untrustworthy and ...


0

I have faced the same issues too and your best bet is to reset the phone via a custom recovery(assuming you have one installed) since you flashed cm13.


0

adb does not grant automatic root access unless you modify the system to run adbd as root (and if you're able to do that, you probably have root anyways) or if you are running an insecure development ROM (typically only for Nexus devices) and run adb root. So normally, you have to be rooted and run su within adb shell just like you would within within a ...


1

No, it is not possible to remove the app from bootloader. ADB daemon is not running in the device in that tiny environment when the device is in fastboot mode and stock recovery doesn't offer shell access. Your best bet is to flash a custom recovery, such as TWRP, CWM or Philz Touch from fastboot/download mode or from a tool using PC (if at all possible ...


0

Based on the information by others, now I know that the backup file is just a prefixed Deflated (GZip) stream, based on this information this simple program can unpack it for you: import java.io.*; import java.util.zip.*; /** Run: javac unab.java && java unab backupfile.ab */ public class unab { private static final int BACKUP_HEADER_LENGTH = ...


1

None of the workarounds worked for me here, and I don't want to downgrade my SDK tools. Here's what I came up with: skip adb backup on the computer and go straight to device via adb shell. $adb version Android Debug Bridge version 1.0.35 Revision fc2a139a55f5-android $ adb shell shell@jflte:/ $ bu 1 backup -apk app.package.name > /sdcard/backup.ab ...


0

ADB backups usually do not contain system apps, unless explicitly specified by you while performing the backup process. If this is the case, you can certainly restore safely without any problem. But some apps may be incompatible with 6.0 as such. So they may not work after the restore.


0

Yesterday we ended up in the same state after trying to flash CyanogenMod 13 on the phone: loop trying to boot CyanogenMod 13 (cyan robot head with circle waves) and no way to get the phone to put itself into adb or fastboot mode. Here's how we solved the issue and got the phone working again, just if it's useful for somebody in the future: Reboot to the ...


0

Based on my testing, adb status-window will continuously monitor the status of the ADB (whether it's connected to a device or not). While it's active, connecting a device will show Android Debug Bridge State: device and disconnecting it will show Android Debug Bridge State: unknown On the other hand, adb logcat also continuously monitors the ...



Top 50 recent answers are included