Develop Bugs

New to ADB and have a few questions I can't find the answers to...

Now, I have figured out that I have to actually be in the android-sdk-windows\tools folder for ADB to work, but when I type adb devices it just says List of devices attached but doesn't list my Evo.
I have USB debugging on.
An Android ADB/rooting noob guide would be very helpful right now.

criccio said:
Now, I have figured out that I have to actually be in the android-sdk-windows\tools folder for ADB to work, but when I type adb devices it just says List of devices attached but doesn't list my Evo.
I have USB debugging on.
An Android ADB/rooting noob guide would be very helpful right now.
Click to expand...
Click to collapse
Does it have anything there when you type adb devices? Should come up with a HT and some numbers after it....being your device, EVO.
Actually, there is a step by step Guide for EVO root, and a ADB Guide for Beginners

Your device isn't being recoginized check the driver if u r in windows.

Ok, I managed to figure out the cryptic SDK installer and download the USB driver package to android-sdk-windows\usb_driver. I used Device Manager to install the driver and I pointed it to that folder and I get the "Windows was unable to install your ADB".

Are you already Rooted? as for the Drivers, when I plugged in my EVO via USB, it installed drivers...I also copied the HTC Sync that came on the SDCard w/phone, onto my pc. But I did not have to do anything further.
Can I ask what you are trying to do in adb? and is this for the EVO?

use the cd command to make sure you are in the android sdk tools folder
if you want adb to work
what i do
1. use the cd command to go to the directory where my sdk is located which for example is c:\androidsdk\tools
2. there you go
3. if you want shell make sure your device is connected
"adb shell"
and have htc sync from evo's sd card installed

http://myevo4g.net/main/?p=83
Sent from my HTC EVO

download htc sync and install that. i was having the same problems and apparently the usb drivers that get installed with that app are the ones that worked like a charm for me.

Try
Code:
./adb devices
Instead.

--> try" adb start-server "
If your HTC dont show up, it's usually because the ADB server isnt running. Hope this helps =]

I've rooted a hero before and felt pretty confident with android sdk, usb drivers, etc. After spending an hour trying to get it to work on my win 7 64 bit system, I thought it might save someone some time if I posted what finally allowed me to get adb to work.
My problem was the computer wouldn't recognize the EVO as a device. Even after I installed the usb drivers through android sdk. I tried to manually update them through device manager (pointing it to the usb drivers directory) and still no luck.
As the video linked above showed, the missing piece for me was installing htc sync. use the version that comes on the phone. So connect the phone to the computer, mount it as a drive from the phone menu, then copy over the htc sync directory to your computer, then run it. The version on my phone was 2.031. THEN the computer will recognize it with usb debugging turned on and I'm able to adb to the phone through the command prompt.
Hope that helps someone. Sean

[q] adb shell from any computer

Is it possible; from any computer, within the command line to run commands on any android devices/phone ie: adb shell, adb devices, adb logcat, adb push that already has android adb/sdk installed?
The reason I asked is cause I installed android sdk/window usb driver on my main laptop with no problems, but I recently purchased another laptop went through the same setup procedure but my adb does not recognize or see my phone when I have it plugged in via usb.
I am at a loss and dont know what to do...

UND3RTAK3R said:
Is it possible; from any computer, within the command line to run commands on any android devices/phone ie: adb shell, adb devices, adb logcat, adb push that already has android adb/sdk installed?
The reason I asked is cause I installed android sdk/window usb driver on my main laptop with no problems, but I recently purchased another laptop went through the same setup procedure but my adb does not recognize or see my phone when I have it plugged in via usb.
I am at a loss and dont know what to do...
Click to expand...
Click to collapse
1) install HTC sync to get the Evo drivers
2) install Android SDK
3) add the tools folder with adb.exe in it to your windows Path or always navigate the command line to that folder.
should work

[solved]win7 doesn´t recognizes my device into fastboot

okay ... a new question and also soo weird....
I want that my 2 PC´s recognize my device when its in bootloader mode
1º pc recognizes it well and its running UBUNTU.
2ºmy sister´s PC RUNNING WIN7 doesn´t recognize my DHD into bootloader mode.. but if i look the screen of the device the device automatically was changed his status to "HBOOT USB PLUG" but here is the problem:
When windoze7 detects and recognizes my device It issues a sound, but when I connect my DHD it issues different other one, that is to say detects it but it does not recognize her, then the usb mode I cannot use it
but if i boot my dhd and put her in debugging mode and run adb parameters windoze recognizes the device perfectly...
i am not an experienced user in windows
and i don´t know whats the problem. its strange..
any advise?thx in advance

Between you and the stickman you've had every problem going!!
Have you installed HTC Sync onto your sister's PC?
Why haven't you converted her to Ubuntu?

Mr_JMM said:
Between you and the stickman you've had every problem going!!
Have you installed HTC Sync onto your sister's PC?
Why haven't you converted her to Ubuntu?
Click to expand...
Click to collapse
lololol we have a lot of problems Especially with windows i hate it
but she is afraid of not being able to handle it if I am not in house (SHE HAS ANOTHER DHD) in addition she likes the Microsoft OFFICE. LOL (and not open office)
Yes i had installed htc sync drivers, and sdk working well in usb debugging mode with the DHD turned on

Get to the stage you were at before:
fastboot
connect phone to PC
Phone says HBOOT USB PLUG
Using the Android-sdk shell
type
Code:
fastboot devices
Do you get a response?

Mr_JMM said:
Get to the stage you were at before:
fastboot
connect phone to PC
Phone says HBOOT USB PLUG
Using the Android-sdk shell
type
Code:
fastboot devices
Do you get a response?
Click to expand...
Click to collapse
yes i tried in fastboot mode but only says "list of attached devices" and nothing more... there aren´t devices in the list..
and if i write adb shell""" says ""not devices found"" logically

SERGI.3210 said:
yes i tried in fastboot mode but only says "list of attached devices" and nothing more... there aren´t devices in the list..
and if i write adb shell""" says ""not devices found"" logically
Click to expand...
Click to collapse
the problem appears into fastboot and into bootloader
ok in fastboot mode into sdk shell write fastboot devices and shows me a message:
"unable to initialize the aplication because ADBWINAPI.DLL not found

Ok, try this:
Create an Ubuntu live CD.... you can see where I'm going with that one.
Sorry buddy, will need to wait for some other poor sap that uses Windoze to pop along.
There was an old thread I read once and someone solved it by going to device manager and updating drivers or something for the "android device". <<-- Re your new post
Other than that, usual suggestion is try a different USB socket (different side of PC).

Mr_JMM said:
Ok, try this:
Create an Ubuntu live CD.... you can see where I'm going with that one.
Sorry buddy, will need to wait for some other poor sap that uses Windoze to pop along.
There was an old thread I read once and someone solved it by going to device manager and updating drivers or something for the "android device". <<-- Re your new post
Other than that, usual suggestion is try a different USB socket (different side of PC).
Click to expand...
Click to collapse
ok tried another socket but the PC says to me :LOL
good idea mate... if i create aN ubuntu root/live cd i can try with the konsole
windoze please... burn in the ****ing hell
edit:with ubuntu works well again

.........................................................................................

spike_14 said:
.........................................................................................
Click to expand...
Click to collapse
good apreciation to the forum mate... LOL

okay... in advance thank´s again to my friend Mr_JMM for help me again (pressing your thank´s button AGAIN lol)
i solved my problem with "winfuck"7 (windows for microsoft´s friends)
ok when i was tried to input a fastboot code the CMD (shell) of windows returned me:
"unable to initialize the program because ADBWINAPI.DLL does not exist...
well i browsed for this file and its a library file for adb.exe commands.
under my experience fastboot parameters shouldn´t be afeccted by the ausence of this file but when i was downloaded it (a zip file with adbwinapi.exe, adbwinusbapi.dll and adb.exe) and i have put it in the folder "tools" of the sdk (Rightly where it shelters fastboot.exe) VOILÀ!!!!
i tried to enter:
"fastboot devices"
and returned to my
"HT.........."
also i tried to rebbot the device from fastboot with
"fastboot reboot" and WORKS WELL!!!!
END OF THIS THREAD.... SOLVED!!!!!!!!!!

Rooting problem

EDIT!!!
I tried using windroid but i get "Device: not found" when my phone is plugged into the USB cable, i have HTC sync installed and it fins my phone, USB debugging is also enabled but still "Device: not found", why?!
Hello
I have a HTC one X(from Sweden) with Android 4.2.2 installed on it and i want to root it to upgrade to 4.4. I downloaded "OneXRootOneClick" but when i run the file to root as administrator in windows 7 i get "adb is not recognized as an internal or external command "
i then got the newest Android SDK and unpacked it @ > C:\temp\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86_64-20140321\sdk\platform-tools
i then ran the following in CMD
set ANDROID_PLATFORM_TOOLS="C:\temp\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86_64-20140321\sdk\platform-tools"
set ANDROID_TOOLS="C:\temp\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86_64-20140321\sdk\tools"
set path=%path%;%ANDROID_PLATFORM_TOOLS%;%ANDROID_TOOLS%
but when i run the file in OneXRootOneClick again i get the very same thing once more, do anyone know why or how i could another way root my android(possibly without a reset)?

noone got any answer to this ? :/

Open a command window inside the platform tools folders and place the phone in the bootloader, you should see fastboot USB in red text. Type this in the command window :
Fastboot devices
Tell me what happens.
And don't use a tool, let's do this the old fashioned way with straight commands.

adb/fastboot ??

Is there any reason that I can't get fastboot commands to work with W7 64bit ?
I've been using them fine for about 2 years but I think it was on a 32bit system.
Just got a new pc which is 64bit.
The drivers install but when I open a command box, in "platform tools", and type "fastboot devices" I don't get the serial number.
It's not the phone that's at fault because I get the serial number when I use a laptop running xp.
Cheers

Check your setup and ADB drivers. Also, when you run an adb command for the first time, you should see it starting the adb daemon. Make sure it is starting correctly, and that it is in the process list.
I will say that it works, because I just got my phone's serial number on my work machine, and last night I updated my N7 and old Galaxy S2, from a Windows 7 64-bit system.

jshamlet said:
Check your setup and ADB drivers. Also, when you run an adb command for the first time, you should see it starting the adb daemon. Make sure it is starting correctly, and that it is in the process list.
I will say that it works, because I just got my phone's serial number on my work machine, and last night I updated my N7 and old Galaxy S2, from a Windows 7 64-bit system.
Click to expand...
Click to collapse
Thanks for your reply but I can't work out what you mean in top paragraph. My fault, NOT yours.
Cheers
Edit... I've just remembered in the past seeing the "daemon starting" prompt, but didn't see it tonight.

10rdan said:
Thanks for your reply but I can't work out what you mean in top paragraph. My fault, NOT yours.
Cheers
Edit... I've just remembered in the past seeing the "daemon starting" prompt, but didn't see it tonight.
Click to expand...
Click to collapse
Depending on how you installed the adb driver and tools, you may need to ensure that the PATH is correct. For example, I installed my adb tools in the (unimaginatively named) c:\adb folder. I put that in the PATH by adding it to the Path line (My Computer -> Properties -> Advanced System Settings -> Advanced (tab) -> Environment Variables -> Path). If this is correct, you can run adb/fastboot from anywhere, which is helpful if you have multiple devices and keep all of their files in separate folders. I am using the "kit" adb file set, not the full developer version, so the only files in the folder are adb.exe, fastboot.exe, and a couple of adb DLLs.
The first time you run adb/fastboot, your system will check to see if the daemon is running. If it isn't, it will start it. If it starts it, you should see a line with the assigned port number. It varies, but is usually ~5000 (Mine was 5037 earlier). After that, it will just return the output of the command. You should be able to launch Task Manager and see adb.exe in the process list if everything is working.

Hi, i have acer e600 i nid help using fastboot ive read that if you try to hard reset using fastboot with command "fastboot -w" or "fastboot erase userdata" it will wipe ur internal storage.. The problem is the system is installed on my internal storage (2.50gb) idk if its the one they called emulated storage but is it safe to wipe my data because i forgot my password and i think it dont have recovery mode partition and usb debugging is unchecked.

Got ONE of the M8s to take fastboot commands.
Windows 7 64bit will only install "Microsoft approved drivers".
Got into "advanced settings" by constantly pressing f8 while pc boots. Selected "install unsigned drivers" or words to that effect.
Connected phone via usb, restarted into bootloader then fastboot. PC installed drivers from phone and got the "fastboot usb" flag.
Could then run fastboot commands and got phones serial number.
The pc will revert back to NOT installing drivers not approved by Microsoft after a reboot.
Problem I have now is that only one of the m8s "can be found", strange.
Edit....constantly pressing f8 on pc reboot takes you to "advanced options". That's where the option to install unsigned drivers is.