Well I decided to install ADB on my home laptop that is running Windows Vista, and when I connect to the device with "adb shell" and execute "ls" I am getting the filenames with a strange characters like:
Code:
←[
I.e.
←[1;34mcache←[0m
Of course linux has no issues given the right TERM settings.
Any pointers on how to make it look normal on Windows?
Related
Got a new computer and Im having trouble getting my ADb setup. When I try to run adb devices I get
adb is not recognized as an internal or external command, operable program or batch file.
I have adb setup on C, JDK is installed. Downloaded drives from htc sync, but did not install htc sync. Under Device Manager, the phone is listed as
-Android USB Devices
-My HTC. the monitor has a lilttle yellow triangle with an !. I tried to update the drives, but it says I have the most recent installed.
Any help would be greatly appreciated. Thanks.
Edit.....need to use the platform-tools folder, not tools.
+1
I have tried to run ADB on my Inc, Nook Color and now the TBolt.
I just cant get it to work.
It would be easy to just say I am a dope, but I have had a highly successful run with the Inc. I have flashed/installed/performed/restored every worthwhile mod available for the INC and Nook with no trouble. I just cant get ADB to run.
ive just helped someone with this.
they HTC Sync software has the ADB drivers
download
install
then cancel HTC sync instalation
http://forum.xda-developers.com/showthread.php?t=1000751
It sounds to me like your problem is that the adb executable is not in your path and you're not trying to run it from within the directory it is installed in, as indicated by your saying "adb is not recognized as an internal or external command, operable program or batch file".
In your terminal window, try using the cd command to switch to whatever folder the adb.exe file is in, and then try running the command. You don't even need the phone hooked up to test at first...just type adb devices or something to see if the app runs or not. On my Mac, if I just type adb at the command line, adb responds with a list of all available commands.
Do a dir command (Win) or ls (Mac/Linux) to confirm the file is in the same directory you are.
distortedloop said:
It sounds to me like your problem is that the adb executable is not in your path and you're not trying to run it from within the directory it is installed in, as indicated by your saying "adb is not recognized as an internal or external command, operable program or batch file".
In your terminal window, try using the cd command to switch to whatever folder the adb.exe file is in, and then try running the command. You don't even need the phone hooked up to test at first...just type adb devices or something to see if the app runs or not. On my Mac, if I just type adb at the command line, adb responds with a list of all available commands.
Do a dir command (Win) or ls (Mac/Linux) to confirm the file is in the same directory you are.
Click to expand...
Click to collapse
Yea, the error is the one you get when you use a windows command thats not in the path. So do this, or add it to your path environment variable
Thanks to all who answered. That is why this community is the best. The older version of adb just had tools folder, while the new version has platform tools that needs to be used. Again thanks.
sent from my commando style T-Bolt.
I'm on win 7 32 bit.
I have HTC sync installed, adb installed, added system variables and cannot get adb to recongize my device in command prompt.
http://www.youtube.com/watch?v=A1SOSXwkc_8
im using windows 7 64bit and trying to learn adb and cmd
i was watch how to install adb and following..
after installing adb and drivers and added adb on system variables
i type cmd and then typed C:\android-sdk-windows\platform-tools
after that i typed adb devices but got an error
C:\android-sdk-windows\platform-tools\adb.exe is not a valid Win32 application.
what do i have to do here?? T.T
If I'm not mistaken in Win7 64, the Android SDK installs ADB to c:\Program Files(x86)\Android\android-sdk\platform-tools\adb.exe
feedhead said:
If I'm not mistaken in Win7 64, the Android SDK installs ADB to c:\Program Files(x86)\Android\android-sdk\platform-tools\adb.exe
Click to expand...
Click to collapse
that is correct. i'm on win 7 x64 and its there.
Type cd then space in front of C:\....
That changes directories.
Sent from my ADR6400L using XDA Premium App
qudwis said:
im using windows 7 64bit and trying to learn adb and cmd
i was watch how to install adb and following..
after installing adb and drivers and added adb on system variables
i type cmd and then typed C:\android-sdk-windows\platform-tools
after that i typed adb devices but got an error
C:\android-sdk-windows\platform-tools\adb.exe is not a valid Win32 application.
what do i have to do here?? T.T
Click to expand...
Click to collapse
First confirm that adb installed where you think it did.
Code:
C:\android-sdk-windows\platform-tools
Hit the start button in Windows and copy and paste your path from above into the Search programs and files box. If the path is valid, Windows Explorer will open to that directory.
If the path is not valid, try typing adb.exe in the search box to see if Windows knows where it is. If it comes up in the search results, right click on it and select "Open file location" and Explorer will open to where it is installed.
Once you have verified where adb is, you should be able to pick up from where you ran into a problem.
I attached the .pdf that I followed when I first installed adb ... I wish I remembered where I got it so I could credit them appropriately. The screen-shots might be helpful to you.
(Note: there is a typo on page 8 where the System Variables are setup paltform should be platform)
Oops the file was too big.
It is zipped and attached to this post.
Edit: I found where I got the document from. http://forum.xda-developers.com/showthread.php?t=1009419
http://forum.xda-developers.com/showthread.php?p=9959449
So im trying to get HDMI mirroring on my atrix
I've successfully rooted the phone (and it shows up as rooted with root check app)
I've downloaded eclipse and gotten android SDK manager (and AVD) operating.
I changed the PATH on my cpu to include:
;c:\android-sdk-windows\tools;c:\android-sdk-windows\platform-tools
(which is the file location I saved SDK to)
When i have my phone plugged in and if i go under Control Panel>Hardware and Sound>Device Manager>
ADB Interface (and subgroup Mot Composite ADB Interface) show up
but when i open the command prompt and try to open the adb shell it says:
'adb' is not recognized as an internal or external command,
operable program or batch file
Any help please?
(operating on windows vista 64 bit)
Hello,
I'm trying to build my own ROM (CyanogemMod) unfortunately, the command adb devices returns the device name but says its offline.
I don't think it's directly caused by the phone because the same command under Windows is working fine. (see attached pic)
So I tried every USB port (2.0 or 3.0), restarted the VM, the Phone, kill then start the adb server, but the issue remains.
I desperately need your help
Thank you
--
My "building" machine is running under Linux x64 (Ubuntu 12.10) through VMware 9.x
Hi,
Hope this is the right forum.
I just upgraded from Windows 7 to 10. Now Helium for Windows can't activate the backup on my android phones any more (Moto X and Samsung Galaxy).
Any settings that I need to change?
Thanks
--- update
I installed the driver from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and now it's working.
Use the chrome version
I have tested on windows 10 build 11082 and worked.
I had the same problem: my Helium Backup App could not be activated by my Windows 10 helium desktop program.
I dived into it and saw that Helium uses ADB under the hood. But I found out it is using an older version of ADB.
When I typed ADB I got:
Code:
adb server is out of date. killing...
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
xplorr said:
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
Click to expand...
Click to collapse
Easy enough fix. Wonder if the Helium creators will update.
This worked perfectly! Thanks so much!
this worked perfect for me!
The coder really should make his windows application just point to the default ADB installation folder. Or better yet, he should have a prompt/wizard which will lead the user to the default directory but also give them the opportunity to point to a non-default location. Since ADB is a pre-requisit for this program, users just need to be told "go to the android website and download platform-tools or the android studio." I prefer the studio because it comes with the GUI sdkmanager and that's nice because I dont have to go anywhere to find out if there has been an update to platform-tools, it tells me right away and will download/install it for me. And that's good for me cause I can be pretty lazy sometimes.
xplorr said:
I had the same problem: my Helium Backup App could not be activated by my Windows 10 helium desktop program.
I dived into it and saw that Helium uses ADB under the hood. But I found out it is using an older version of ADB.
When I typed ADB I got:
Code:
adb server is out of date. killing...
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
Click to expand...
Click to collapse
xplorr said:
I had the same problem: my Helium Backup App could not be activated by my Windows 10 helium desktop program.
I dived into it and saw that Helium uses ADB under the hood. But I found out it is using an older version of ADB.
When I typed ADB I got:
Code:
adb server is out of date. killing...
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
Click to expand...
Click to collapse
i Don't believe such a simple trick works ..... thank you very much ...