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"
Hello iam using windows vista and xp and I had the same.problems on both. I downloaded the ADB program which gave me 5 seperate files. and downloaded thedrivers for my moto Atrix. But I was told not to run the adb.exe but to look for a run command line prompt. Where and how do I find this. And where do I go to run the commands?
Sent from my MB860 using XDA App
RPK925 said:
Hello iam using windows vista and xp and I had the same.problems on both. I downloaded the ADB program which gave me 5 seperate files. and downloaded thedrivers for my moto Atrix. But I was told not to run the adb.exe but to look for a run command line prompt. Where and how do I find this. And where do I go to run the commands?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hey
press the start button (bottom left), on start menu you should see "run" with a small icon looks like a dialogue box (might be below search), press this. in the dialogue pop up type CMD.
Tho you will prob need to set up Environment Variables before you can use ADB.
kam333 said:
Hey
press the start button (bottom left), on start menu you should see "run" with a small icon looks like a dialogue box (might be below search), press this. in the dialogue pop up type CMD.
Tho you will prob need to set up Environment Variables before you can use ADB.
Click to expand...
Click to collapse
Then you have to go to folder where "adb.exe" is...
For example if you have it in "c:\adb_folder" you have to type "cd adb_folder".......
Then your command line will be like this → C:\adb_folder>
Then, if you want to test if your device is connected properly you have to type "adb devices" and you will see your device listed....
If not, there is a problem.....
(don't forget to enable "USB debugging" at your phone through Applications→Development)
I
pigeonaras said:
Then you have to where "adb.exe" is...
For example if you have it in "c:\adb_folder" you have to type "cd adb_folder".......
Then your command line line will be like this → C:\adb_folder>
Then, if you want to test if your device is connected properly you have to type "adb devices" and you will see your device listed....
If not, there is a problem.....
(don't forget to enable "USB debugging" at your phone through Applications→Development)
Click to expand...
Click to collapse
I was.able.to open up the command.prompt, but when I run adb devices it just says "adb is not a recgonized as an internal or external....." . It is.like its not connecting for somereason ? Iam a complete noon so any help would be great. Thanks
Sent from my MB860 using XDA App
pigeonaras said:
(don't forget to enable "USB debugging" at your phone through Applications→Development)
Click to expand...
Click to collapse
Have you done this .....??????
RPK925 said:
I
I was.able.to open up the command.prompt, but when I run adb devices it just says "adb is not a recgonized as an internal or external....." . It is.like its not connecting for somereason ? Iam a complete noon so any help would be great. Thanks
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Before you can use adb command, you have to direct the terminal to the location of the folder where adb is located.
If the location of the file adb is at C:\\windows\androidsdktools\tools\adb
In your terminal type
cd \
Press enter, then type,
cd windows\androidsdktools\tools
Now the terminal should be in the folder where adb is located.
adb devices
A better way in my opinion to use adb is to set the path so it is usable from anywhere, simple easy and no need to always cd the path
directly quoted from dreamsforgotten's tutorial on theming for the epic
http://forum.xda-developers.com/showthread.php?t=821638
"On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ directory to the path."
Click to expand...
Click to collapse
tmspyder said:
A better way in my opinion to use adb is to set the path so it is usable from anywhere, simple easy and no need to always cd the path
directly quoted from dreamsforgotten's tutorial on theming for the epic
http://forum.xda-developers.com/showthread.php?t=821638
Click to expand...
Click to collapse
This Works!
install adb driver first£¬turn your phone in ¡°charge only mode¡±£¬then find the adb floder£¬hold ¡°shift¡±and right click the floder.choose ¡°run in cmd line mode¡±£¬yeah£¬you done it
How come nothing happens when I try to start adb?
A cmd window pops up then vanishes just as quick...
sounds like you are launching adb from explorer or run command. Open a cmd window first and navigate to adb location and run adb.
adb is launched by opening a regular cmd window, then navigate to the android sdk tools folder as such:
cd android-sdk-windows\tools
if you didn't extract it to the root of the C: drive edit the path accordingly.
if you extracted it to the root of another drive type #: (# being the drive letter) first then use cd android-sdk-windows\tools command. From there use ADB commands.
thanks.
now lets hope I don't break something!
still have so much trouble
C:\Program Files (x86)\Android\android-sdk\platform-tools is the location.
what should I type...
type cd /Program Files (x86) then type cd android-sdk\tools, then run your commands.
You can hold shift and right click the folder and go to open command window here
Sent from my LG-VM670 using Tapatalk
After installing ADP and fastbook, after I type a command, the dos window pops up and then disappears. When I open up the task manager, it is running in the background. Could this be a problem with Windows 8?
cnh56 said:
After installing ADP and fastbook, after I type a command, the dos window pops up and then disappears. When I open up the task manager, it is running in the background. Could this be a problem with Windows 8?
Click to expand...
Click to collapse
Its ADB (Android Debug Bridge) not ADP. I'll let it slide on fastbook because you got it right in the title.
Where are you typing these commands at, the Windows Run line or a cmd shell? Sounds like you might be running them from the run line. Nothing should pop-up because you should already be in the shell before you type your commands. You need to run "cmd" then from that shell type your commands. From the shell type "adb devices" to see if your PC can see your device over adb. If successful, the output will be your device SN. From the shell type "exit" to return to Windows (if run maximized) or to close the window (if run floating-whatever that's called, normal I think).
So basicly im trying to follow a tutorial to get my screen working in ubuntu touch, which involves using adb shell, nano to modify a file.
the little tutorial goes like this:
thecosmicfrog said:
Sure thing. Boot up your device, then plug in a USB cable. Open a terminal and run "adb devices". Make sure that a device shows up. If not, unplug and plug in again. I find that it never works the first time for me.
Next, run "adb shell". This will connect you to your phone and open a shell session on it. Open the /etc/rc.local file in a text editor using the following command:
"nano /etc/rc.local"
Scroll down to the bottom using your keyboard's arrow keys and on the line before "exit 0", insert the following:
./system/bin/sensorservice &
Save and exit the file using Ctrl+X then reboot your phone by running the command "reboot".
This should fix the black screen problems.
Click to expand...
Click to collapse
well when im in adb shell, and type nano /etc/rc.local my adb (or cmd window) screws up completely (see attachement)
what is going on and how do i fix it?
this isn't normal i think!
j