Edit: [SOLVED] I also had to copy over AdbWinUsbApi.dll from platform-tools. Derp.
I am running Windows 10 Pro on a Surface Pro 3. When I enter "adb devices" into a command line, there is nothing under "list of devices attached." USB debugging is enabled.
Initially I copied adb, AdbWinApi.dll, and fastboot to another directory from platform-tools from the Android SDK. Then I installed the Motorola Device Manager. But adb could not see my device. I then installed Minimal ADB which did not help. After that I uninstalled Motorola Device Manager and solely installed the drivers from this thread http://forum.xda-developers.com/showthread.php?t=2550635, including the additional file, which also did not work. But if I launch adb using Android Studio, and then typing "adb devices" into a command line, adb can then see my device. What does Android Studio do or use that is different? How can I make adb see my device solely from command line?
Related
I'm running windows 7 x64 and i'm trying to run "nandroid-mobile.sh restore" on an EVO 4g via adb, but adb isn't working and never has on my computer. I believe i've downloaded and installed all the required programs for adb. am I missing something or should I use an xp desktop as my adb repair station?
edit: when trying to run adb from the sdk/tools directory it just opens and closes a command prompt.
edit 2 (resolution): right click inside sdk/tools folder, click "open command prompt here"
my adb commands in windows cmd are not recognized. I have done the following and am trying to install a custom boot animation
-Installed android SDK
-Installed Java SDK
-Have phone charging only while in debugging mode
-Added environment variable on windows 7 pc
First install of sdk yielded no recognition of adb commands, reinstalled and adb help command worked so downloaded the bootanimation i wanted, went back to command, ran adb command again - not recognized as valid command. So it seems the adb script commands just aren't sticking...arrggg
UPDATE : I have adb running commands now, but my device is not recognized [error: device not found] I have installed the google usb drivers and manually installed them on my computer but do not know if they are working correctly, there are three:
-Android ADB interface
-Android Bootloader interface
-Android composite ASD interface
FIXED : 1.Needed HTC Sense driver for adb inteface, found standalone driver 2. adb commands wouldn't run unless your in the adb directory - duh
THE DEVICE penta ws 708 c is detected in disk manager .even name and driver version displayed.
pdanet 3.02 installed and operating fine.when adb command is used in command prompt it runs fine.
but when adb devices command is run it shows under list of devices no name or number .
so also when backup command is run it says -adb unable to connect to the device. what needs to be done?
SDK IS UP TO DATE with ECLIPSE STARTING UP AND RUNNING AND PLATFORM TOOLS UPDATED> PLEASE CLICK ON ATTACHMENTS AND SEE IF YOU CN FIND ANY PROBLEMS THERE.
I have a new laptop running Windows 8.1. So I had to reinstall adb and fastboot on it. I used the quick installer described in:
http://forum.xda-developers.com/showthread.php?t=2588979
It installed in seconds.
I now need to issue some adb commands to my rooted nexus 5 running stock 4.4.4. So I
1. opened a command prompt in Windows
2. Connected the nexus 5 to the laptop with its usb cable.
The nexus appeared in Windows as a drive named "internal storage".
3. Typed adb devices and got as a response
"list of devices attached"
But nothing else shown under it.
It's been a while since I used adb. What am I doing wrong?
My nexus 5 is rooted.
Usb debugging is selected.
Should I change something else on it?
Appreciate any help.
Search and download minimal adb for windows on google ..run the program and put whatever file it is your trying to push in the same folder as adb in program files tab ..work like a charmed sideloading ota ..I'm pure stock
I have used the same adb installer in windows 7 and it works.
Are you opening cmd as an administrator? That is the only miss I can find.
It was my fault. When I installed the correct driver, everything went well.
Sorry to have bothered you guys and thanks for helping.
Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.
herkio1 said:
Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.
Click to expand...
Click to collapse
Adb use Adb.exe and fastboot fasboot.exe (differente programs)
For Twrp you must use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.
download sdk Platform tools https://developer.android.com/studio/releases/platform-tools.
extract platform-tools folder.
Put this twrp https://androidfilehost.com/?fid=17248734326145679747 into platform tools folder
Phone in fastboot mode power and volume - (Obviously the phone must be detected on the pc)
use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.
Solved thanks, I used fastboot for fastboot mode and adb for in twrp/booted in system. I must have mistyped because I could flash the twrp.img file but it then gave me an error when trying to boot into it.