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
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
I would take the time to learn ADB or wait until a one click is out. Learning ADB while rooting your phone could easily break it.
what os are you using?
svalle713 said:
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
Click to expand...
Click to collapse
Honestly just take the time to read the procedure, other help topics on these forums, and take your time when actually going through the procedure.
I had never used ADB either or rooted an android phone for that matter, and I gotta say, rooting the TBolt was cake.
I just took my time with it ensuring I typed in the commands properly.
But if you need a video, here you go: http://www.droid-life.com/2011/03/22/video-rooting-the-htc-thunderbolt/
what drivers do we need for the process, are they only the htc sync drivers? where can these be found?
Android SDK should be extracted/installed straight onto the C:\ directory to make it easy. Open the android-sdk folder and in it is a program sdkmanager.exe, open that and you can reject all of the downloads but scroll down and install one called the "google usb driver package" which may be necessary, I'm not sure (you should also have the htc sync drivers installed)
The contents from the "exploit.zip" should be extracted into the folder "platform-tools" within the android-sdk folder. Plug in your phone to the usb and open the command prompt. To get started open the command prompt (like a dos prompt) and get the prompt into the folder 'platform-tools' and type "adb devices" then hit enter. If your phone is connected and you have "usb debugging" enabled on your phone from the settings, your phone should appear and you can begin the instructions from jcase
sorry, but i need help, all day i have been trying to install android sdk and run on my windows 7 laptop. I went to youtube and followed everything but still can't get it. I installed 3 things. and I placed them in the c drive. now i have a file c:\android-sdk\tools.....now when I go into cmd and type that in it says invalid path...I tried d drive says device not ready....my evo is on debugged. someone please help me out.
In cmd try typing cd\
That will take u to root directory, now try c:\android-sdk\tools and assuming that is the valid path you should now be in that folder. If that does not work you may have an extra folder like android\android-sdk\tools.
I am assuming in the files u installed included were the drivers for the evo. These need to be installed otherwise once in tools dir u will get device not found when trying an adb command.
i tried cd then c:\android-sdk\tools....it says invalid internal external command. also I did download the driver for evo 3d but what do I do with it....where do i put it.....thanks for help in advance......im getting very frustrated.
"Cd\" without quotes then press enter. Then try specifying path for the tools folder which you say is c:\android-sdk\tools.
If that doesnt work you can type dir\w and that will show you all the folders in the directory. Make sure you type folder names exact.
As for the drivers just run the install and make sure u get right version. U msentioned windows 7 but 32 bit or 64 bit? If your phone has debugging on and the drivers are installed correctly you should be able to plug you phone in without being prompted to install new device.
Typed in c:/dir/w. It said volume in drive c has no label. Volume serial number is eore-14a9...also when I put my usb cable in laptop sees it.
Installed latest version of CWM..made backup of original rom...Rebooted System...No problem...Flashed CM9 per instructions...Full Wipe...Played with it for awhile...Backed it up...tried to restore Stock Rom ...went into CWM loop...Read a lot of threads and I still have drivers and Asus is seen in Device Manager with ADB Interface...So I tried Command prompts for 1a...and what I get is 'adb' is not recognized as an internal or external command,operable program or batch file...
Am I typin the command right ???...I never used ADB before...Came over from Epic Touch 4g Forum here...and I only used Odin...Could someone give me a clue if on on the right path of Unbrickin this thing...
Thanx...
BTW its Unlocked and of course rooted...
Your salvation is at hand:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Follow this guide. To the letter, very important you set the path correctly in the environment variables or you'll be going around in circles. Once it's done, you'll have a working ADB and fastboot environment, you will also want the "Universal naked USB driver" which can be found on this site.
Once you've got that up and running, try getting your system into fastboot protocol and type fastboot -i 0x0b05 reboot, if that works, then you've access to ADB and fastboot protocols, follow the commands given in solution 1a then to complete your recovery.
Hope this helps.
Hobbesian said:
Your salvation is at hand:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Follow this guide. To the letter, very important you set the path correctly in the environment variables or you'll be going around in circles. Once it's done, you'll have a working ADB and fastboot environment, you will also want the "Universal naked USB driver" which can be found on this site.
Once you've got that up and running, try getting your system into fastboot protocol and type fastboot -i 0x0b05 reboot, if that works, then you've access to ADB and fastboot protocols, follow the commands given in solution 1a then to complete your recovery.
Hope this helps.
Click to expand...
Click to collapse
Yep it was a Nandroid Backup...Im not at all familiar with ADB ...Just Odin which I use Rooting Phones...Ill give it a try...This is drivin me nuts...Just cant get ADB to work for me thru commands...Ill definitely do what you suggest...Thanx a lot Ill let ya know what happens...
Still gettin this when I run a command prompt
adb is not recognized as an internal or external command,operable program or batch file..Says the same for fastboot...Am I typin the commands right...
Installed driver and extracted the files from the download to my c part of the drive...Do I have to open anything in the download folder inorder for it to work or just extract everything like I did...
Didnt have the path of the extracted files in the right spot...Just had to change it...Wurked fine...Up and Runnin...Thanx a lot...Really appreciate it...
Help
ronny71 said:
Didnt have the path of the extracted files in the right spot...Just had to change it...Wurked fine...Up and Runnin...Thanx a lot...Really appreciate it...
Click to expand...
Click to collapse
What did you do? What files? I did literally the EXACT same thing to my prime. Please help. (Idk what to do with this driver download)
chrsbrrss said:
What did you do? What files? I did literally the EXACT same thing to my prime. Please help. (Idk what to do with this driver download)
Click to expand...
Click to collapse
Extract it if you haven't already.... put your prime into recovery .... plug it into the pc... in device manager find the prime and update the driver manually... point windows to the driver and your there...
For adb... you need to download that too I use the one in the nvfashpack... so... you extract the file.. with the window open... press and hold shift then right click in the window (nvflashpack folder, where the adb.exe file is) and select open command prompt here. Now you can use the adb commands... if your trying to push a file...it is best to put it in the same folder (nvflashpack)
Hi guys,
EDIT: See the last posts - I have figured this out, and tried to include helpful information, if you are having this problem too.
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
urbainmenace said:
Hi guys,
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
Click to expand...
Click to collapse
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
goodayoo said:
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
Click to expand...
Click to collapse
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
urbainmenace said:
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
Click to expand...
Click to collapse
OK，I think I'm gonna get one and give it a try. the only way to fix this brick is in the ADB Interface I'm sure. though I also don't know How to do.
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
urbainmenace said:
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
Click to expand...
Click to collapse
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
goodayoo said:
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
Click to expand...
Click to collapse
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
bootlooped, adb runs some commands
urbainmenace said:
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
Click to expand...
Click to collapse
Working with the HDX 8.9.
I think I have deleted some of the system files also. I was reloading a safestrap backup and rebooted but the backup had failed to complete. I don't know what may be missing from the system files and would like to push the system files onto the device.
Right now I get a gray kindlefire screen for about 90 seconds, during which I have adb access, then it goes to the color kindlefire screen and asks if I want to Restore to Factory Defaults or reboot. I finally subjected it to the Restore to Factory Defaults, but that just wiped the cache and data partitions, I don't see where it did anything to the system files. It did not change my adb access.
In adb I can push files to some locations but others say: failed to copy ....: Read-only file system.
I cannot run shell commands
# adb shell
soinfo_link_image(linker.cpp:1617): could not load library "/vendor/lib/libNimsWrap.so" needed by "/system/bin/sh"; caused by load_library(linker.cpp:745): library "/vendor/lib/libNimsWrap.so" not foundCANNOT LINK EXECUTABLE
I was working in Windows 8.1 but have switched to Suse Linux but the results are the same so far.
I have the stock system files but I am not sure how to push them to the device, if it can be done, while the device is trying to reboot.
fastboot
I can put the HDX in Fastboot mode with the adb command. But when I try to pass commands to the HDX I get:
< waiting for device >
and I have to Ctrl-c to stop the process.
Do the fastboot commands only work if you have a fastboot cable???
Since you guys are using adb checkout these threads:
http://forum.xda-developers.com/showthread.php?t=2530623 Factory Reset
http://forum.xda-developers.com/showthread.php?t=2636817 [Video Tutorial] GAPPS + Amazon from Cpasjuste
http://forum.xda-developers.com/showthread.php?t=2638241 How to un-boot-loop (another way)
http://forum.xda-developers.com/showthread.php?t=2598577 [TUT/FIX] Fix the Boot Loop on Kindle Fire HDX 7"
This guy may also be able to help, forum member: GSLEON3 Post #16
http://forum.xda-developers.com/showthread.php?t=2580989&page=2