Related
To start off, yes I am a complete noob to this, so bear with me. I have been trying for hours to get the adb info to install on my computer so I can root with the new 2.2 method. I have Vista/32 bit and I have tried multiple ways to install, from guides here and you-tube and nothing will recognize the adb in cmd.exe. I have copied the sdk info into a tools folder like I'm supposed to, I think, and followed the instructions and all I get is that it is not recognized or not an executable file or whatever.... Can someone please offer some help here?? Thanks in advance
did you try to run abd from the /android-sdk/tools folder in the command prompt? and did you add the path to the enviroment variables?
I have tried to run it from the folder, and I thought I had it added but I'll double check...
OK, it's in the path now, but I still get a 'not recognized as an internal or external command, operable program or batch file.' I'm stuck in the mud, spinning my wheels....
I get the same thing with win7 I can get the command prompt android tools folder hit enter and it said 'not recognized as an internal or external command, operable program or batch file
Ooooh...I got it...had the cmd info in wrong folder...needed it in the same tools folder...thanks folks
Yeah, getting adb into your path is kinda hard the first few times. I add it to both of my Paths and then reboot. If you follow the documentation on the Android site, it usually works after a reboot.
To make sure its just a path issue, you go to your sdk folder and navigate to tools (in the command prompt, of course, which is done by "cd \path\to\sdk\tools\") and then typing adb. If that works, then you type adb devices and make sure your phone is found. If that works, then all you need to do is finish the path installation and reboot. That's usually how I get it. Once on your path, you can adb shell from any location on your computer, which is nice when you want to push files to your phone.
So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?
HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?
DressedUpPanda said:
So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?
Click to expand...
Click to collapse
The PATH issue, relates to ADB, if you are running into errors like:
'adb' is not recognized as an internal or external command
Click to expand...
Click to collapse
When executing ADB commands that is your issue, it can be resolved by adding the path where ADB lives to either your user or system PATH in Windows. The PATH is irrelevant if you are running ADB from the folder where the ADB files live.
The other (common) issue is drivers, where ADB is working but won't see your device. Do you see an "ADB Device" or similar with a yellow icon in your device manager when your phone is connected to your PC? If so you don't have the correct driver loaded. The only reason you install HTC Sync is to load this driver but the driver can also be loaded separately.
Sorry to hi-jack this thread, and since I'm new to adb I might as well use this.
I have adb running, did the file paths and everything. I'm just trying to test it out, since I'm already rooted using visionaryr13 as well as s-off. Went back and gfree over that, and I've also verified through terminal emulator on my phone, but I'm just testing my skills with adb and failing miserably. I Have d/l the verify file, and unzipped in a folder inside my downloads folder I might add.
When it says:
"
VERIFY (using "gfree_verify")
Now you can try using a new SIM card to verify that it worked.
In addition you can use gfree_verify to verify the state of your locks.
Download gfree_verify.zip from gfree_verify_v01.zip
ON YOUR PC:
Unzip gfree_verify_v01.zip to a place on your computer. Navigate to where the file is on your computer, and type:
$ adb push gfree_verify /data/local
"
I'm having a problem with the navigate to where the file is on your computer and type. I have cmd open, and have tried everyway but the right way to push this through. This is the error I'm getting.
cannont stat 'gfree_verify': no file or directory
EDIT: I got it and I'm sure everyone is laughing at this idiot. So in the cmd prompt you have to navigate to where you put the folder, then push the file to your phone, DUH!
OK, stupid question number two, since I answered number 1.
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?
mrbmg said:
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?
Click to expand...
Click to collapse
Type "exit".
ty ty.
Ok so I updated something in adb and it's not working. LOL, well restarted, and now the sdk manager is updating some more stuff so hopefully that is the reason I was not getting in.
EDIT: everything is working now.
Ty stevie, really appreciate all your hard work helping us noobies man!
steviewevie said:
HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?
Click to expand...
Click to collapse
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'
DressedUpPanda said:
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'
Click to expand...
Click to collapse
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.
steviewevie said:
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.
Click to expand...
Click to collapse
Ok well here is the path that i have set up.
- C:\AndroidSDK\tools;C:\AndroidSDK\platform-tools
I saved the file right to my "C" drive so thats why i didn't go to the program files. I also changed the name of the folder so it was easier to type.
Edit: I got it to finally recognize my device. I went back to my path and found that i had spaced in between my ';' and 'C:/' so thank you very much Stevie on making me double check it!!!
Hey guys I'm getting setup to root my buddies Evo shift. I Dloaded android sdk followed the instruction. I've opened cmd.exe when I type in a command it says it says 'adb ' is not recognized as an internal or external command, operable command or batch file.
I'm trying it out on my Evo first just to get familiar with the system any direction is greatly appreciated
Sent from my PC36100 using XDA App
30bushido1 said:
Hey guys I'm getting setup to root my buddies Evo shift. I Dloaded android sdk followed the instruction. I've opened cmd.exe when I type in a command it says it says 'adb ' is not recognized as an internal or external command, operable command or batch file.
I'm trying it out on my Evo first just to get familiar with the system any direction is greatly appreciated
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What version of windows are you on? You followed all of the instructions on setting up adb from that thread in the Shift forums? I also rooted my roomate's Shift, and I read that adb setup tutorial when I was over there. It was pretty solid. I already had adb set up, but read it through to see. When I set up adb, I had someone advise to me to place the adb.exe, and that .dll file (found in platform tools, in the SDK download) in my 'system32' folder of my PC. Once I placed those two files in the 'system32' folder, adb has worked flawlessly.
Also, have you made sure you have all the correct drivers installed? I believe I also had to install HTC Sync, because that installed some drivers that were necessary. Once it installed, I uninstalled it (the drivers will remain installed) because it can interfere with adb communication, apparently. Hope you get it set up. Once you do, rooting the Shift wasn't hard. Just follow the instructions to the t, and just copy and paste the commands, to eliminate the possibility of messing up the commands.
Thanks man I'm gonna give the HTC sync thing a shot
Sent from my PC36100 using XDA App
30bushido1 said:
Thanks man I'm gonna give the HTC sync thing a shot
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You're welcome, feel free to PM me if you have any more issues.
to get adb to work, you need to be in the same directory as all of the sdk tools to use my setup as an example, my stuff is located in
C:\SDK\platform-tools
when I open the cmd prompt, it starts in
C:\Documents and Settings\Chris>
to change directories, type
C:\Documents and Settings\Chris>cd \
the display will change to
C:\>
type (in my example, yours may vary unless you set your folders up the same way)
C:\>cd SDK\platform-tools
it will change to
C:\SDK\platform-tools>
then you will be able to use adb commands like push/pull, shell, devices, etc.
Muellersirch said:
to get adb to work, you need to be in the same directory as all of the sdk tools to use my setup as an example, my stuff is located in
C:\SDK\platform-tools
when I open the cmd prompt, it starts in
C:\Documents and Settings\Chris>
to change directories, type
C:\Documents and Settings\Chris>cd \
the display will change to
C:\>
type (in my example, yours may vary unless you set your folders up the same way)
C:\>cd SDK\platform-tools
it will change to
C:\SDK\platform-tools>
then you will be able to use adb commands like push/pull, shell, devices, etc.
Click to expand...
Click to collapse
By putting the adb.exe and the .dll files in the 'system32' folder, that will allow you to execute adb commands from any directory in the command prompt. I don't have to navigate to my sdk tools to use adb. It saves a few steps, so you can just open up your command prompt and command away.
Or you can put the directory that contains adb in your system PATH. This will let you execute adb in a command prompt anywhere...
Sent from my ADR6300 using XDA App
I'm running wd7. I've gone through it again and installed the drivers then uninstall HTC sync I'm still not able to access sdk through the command prompt. I know its something simple I'm missing how do I move adb to the system path
Sent from my PC36100 using XDA App
C:\user\paul>
Is what the terminal reads any command I enter is not recognized as an internal or external command.
I have got the command list to show up but cannot exicute any of them
Sent from my PC36100 using XDA App
when i tried to run sdk , got this error
C:\>android-sdk-windows\tools
'android-sdk-windows\tools' is not recognized as an internal or external command
,
operable program or batch file.
C:\>
can somebody help me to solve this error
i am on windows xp
what do you want to do?if you want to use the program inside the tools folder you should enter the folder. you can make a shortcut file by make a new txt file in tools folder, type cmd.exe then save the file. change the extension to *bat. in this way anytime you open the *bat file you'll enter tools folder in cmd automatically.
The folder you cd should have adb in it. Otherwise it won't work
Sent from my GT-S5360 using XDA
Define more clearly !
The error you have mentioned isn't from sdk, its a cmd error & is trying to inform you that the command you entered isn't an executable(script or binary), its just a simple path to which you can cd not execute.
You can just find the windows executable(like *.exe, *.bat, *.cmd,.. etc) you are trying to execute & double click
Like the default location for Sdk Manager : "C:\Program Files\Android\android-sdk\SDK Manager.exe"
yup...thats right. but the *exe command only work if executed from cmd. he has solve this problem anyway. mod can close it now.
He didn't mentioned about gui or command-line. So replied that way.
That's not sdk error,....
Sent from my Nexus One using Tapatalk
Hello. I was trying to Root my 1st gen Kindle Fire with KFU, but when I type 2 to Install Permanent Boot, I encounter several problems:
'find' is not recognized as an internal or external command,
operable program or batch file.
***********************************************
* Installing Permanent Root *
***********************************************
***********************************************
* Activating Fastboot (4002) *
***********************************************
2756 KB/s (510876 bytes in 0.181s)
fail opening shift: No such file or directory
The kindle has been told to reboot in Fastboot Mode.
twrp.img is missing.
So we will download it for you!
'find' is not recognized as an internal or external command,
operable program or batch file.
'find' is not recognized as an internal or external command,
operable program or batch file.
wget: missing URL
Usage: wget OPTION... URL...
Try `wget --help' for more options.
Cannot open input file recovery\twrp.img
Download successful.
fff.bin is missing.
So we will download it for you!
'find' is not recognized as an internal or external command,
operable program or batch file.
'find' is not recognized as an internal or external command,
operable program or batch file.
wget: missing URL
Usage: wget OPTION... URL...
Try `wget --help' for more options.
Cannot open input file recovery\fff.bin
Download successful.
***********************************************
* NOTICE *
***********************************************
'find' is not recognized as an internal or external command,
operable program or batch file.
'find' is not recognized as an internal or external command,
operable program or batch file.
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
Cannot open input file recovery\fff.bin
error: cannot load 'recovery\fff.bin'
Installing TWRP...
Cannot open input file recovery\twrp.img
error: cannot load 'recovery\twrp.img'
Setting Recovery Bootmode.
< waiting for device >
I don't know why all of this is happening, I followed several tutorials for Rooting with KFU. I've looked everywhere for a fix to this, but I've yet to find one. Hopefully someone could tell me what I'm doing wrong?
Looks like at least one or two possible things driver and possibly java try installing jdk and reinstalling the driver. What os are you using? Could also be a corruption in the kfu you are using as well redownload it.
Okay
Thepooch said:
Looks like at least one or two possible things driver and possibly java try installing jdk and reinstalling the driver. What os are you using? Could also be a corruption in the kfu you are using as well redownload it.
Click to expand...
Click to collapse
I'll try what you said, and I am using Windows 7
UPDATE: I reinstalled JDK, the drivers, and KFU, yet still getting the same things. I've tried this on two computers, both running Windows 7.
Sounds like your path in windows might not be set up properly. Search the KFU thread for my post on what to look for. If I remember correctly it was that C:\Windows\system32 has to be in the PATH environment variable.
EDIT: Found it:
Check your PATH variable in Windows. Either view it by right clicking on My Computer and selecting Properties, then going to the Advanced Tab and selecting Environment Variables, or open a CMD window and type
echo %path:;=&echo.%
That will show all the entries, each on a new line so they are easier to read. Make sure there is a path entry for C:\WINDOWS\system32. If there is not add the following:
%SystemRoot%\system32
redbean25 said:
Sounds like your path in windows might not be set up properly. Search the KFU thread for my post on what to look for. If I remember correctly it was that C:\Windows\system32 has to be in the PATH environment variable.
EDIT: Found it:
Check your PATH variable in Windows. Either view it by right clicking on My Computer and selecting Properties, then going to the Advanced Tab and selecting Environment Variables, or open a CMD window and type
echo %path:;=&echo.%
That will show all the entries, each on a new line so they are easier to read. Make sure there is a path entry for C:\WINDOWS\system32. If there is not add the following:
%SystemRoot%\system32
Click to expand...
Click to collapse
There is a path entry for C:\Windows\system32. So then what's wrong?
UPDATE: Okay, sorry about that, one of the computers has the path entry, the other doesn't, but when I try %SystemRoot%\system32 it says
'C:\Windows\system32' is not recognized as an internal or external command,
operable program or batch file.
If it's something simple, I apologize for my ignorance.
UPDATE: I just got it working on one of the Computers, but at one point it says
***********************************************
* NOTICE *
***********************************************
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
< waiting for device >
It's been like that for 10 minutes or so. What do I do?
Madnessfan34537 said:
There is a path entry for C:\Windows\system32. So then what's wrong?
UPDATE: Okay, sorry about that, one of the computers has the path entry, the other doesn't, but when I try %SystemRoot%\system32 it says
'C:\Windows\system32' is not recognized as an internal or external command,
operable program or batch file.
If it's something simple, I apologize for my ignorance.
UPDATE: I just got it working on one of the Computers, but at one point it says
***********************************************
* NOTICE *
***********************************************
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
< waiting for device >
It's been like that for 10 minutes or so. What do I do?
Click to expand...
Click to collapse
Reboot the device and it should continue when it reboots .
redbean25 said:
Reboot the device and it should continue when it reboots .
Click to expand...
Click to collapse
Nothing happens.
Madnessfan34537 said:
Nothing happens.
Click to expand...
Click to collapse
Sound like the driver for fast boot mode is not installed correctly then. Double check that your drivers are installed properly.
redbean25 said:
Sound like the driver for fast boot mode is not installed correctly then. Double check that your drivers are installed properly.
Click to expand...
Click to collapse
Everything seems to be in order, hmm.
UPDATE: I was trying to do other things through cmd with the Kindle Fire, and it would say <waiting for device> every time. There is definitely something wrong, I just don't know how to fix it, because I don't know what exactly is wrong. Someone help?
UPDATE: Screencap of what's going on http://i.imgur.com/rjx0azF.jpg