adb Problem - G2 and Desire Z Q&A, Help & Troubleshooting

Heya,
I'm in the process of getting permaroot and I got a problem with adb commands which is really annoying.
Whenever I fire up an adb command, either in dos or adb shell, it works with a chance of 50/50. It can happen that I fire the command and nothing happens but a cursor, then I have to ctrl+c out and try it again.
And this sucks especially when I have to do several commands in a row in the shell -.-

What kind of commands, how are you connecting it to the computer, what kind of computer (windows, OSX, Linux?) what Rom? Are you connecting thru a USB hub (powered or unpowered), are you using the latest android SDK that matches your Rom's version?
Basically a lot of information needs to be mentioned.

Related

[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

[Q] Inc not recognized by ADB on Mac

Hey all,
My Incredible won't be recognized by ADB on my Mac through the terminal. I type in "adb devices" and it returns "List of connected devices" but doesn't actually list anything. If I try something like "adb shell" it says "error: no devices connected". What could the issue be?? I have a PC as well and ADB works fine on the PC.
If it helps at all the phone is recognized through fastboot on my Mac but I can't perform any operations... I tried to flash a new recovery through fastboot and when I tried to do "fastboot erase recovery" it returned something like "erase recovery failed status malformed"...
Thanks!
debug turned on? Thought that it needed to be adb
Yeah debug is on.... also in case it didn't go without saying I'm rooted.
Hope someone can help with this!
Sent from my ADR6300 using XDA Premium App
Anyone have any ideas on this one?
Go here and follow steps for your system.....
http://androidsamurai.com/forum/viewtopic.php?f=12&t=4&sid=e1f4ce4f9ba69613dca7ba5db4a711a2
if I helped please don't hesitate to hit the thanks button
Sent from my Incredible using XDA App
Thanks for the advice, but I had already followed those directions when installing the SDK. As I said, the phone is recognized just fine on a Windows machine so I can only assume it's some setting that's perhaps incorrect on my Mac? Maybe in System Prefs?
I dunno. It isn't the biggest deal but it'd be nice to be able to use the ADB on my Mac without needing to boot up the PC. Thanks!
nufan947 said:
Thanks for the advice, but I had already followed those directions when installing the SDK. As I said, the phone is recognized just fine on a Windows machine so I can only assume it's some setting that's perhaps incorrect on my Mac? Maybe in System Prefs?
I dunno. It isn't the biggest deal but it'd be nice to be able to use the ADB on my Mac without needing to boot up the PC. Thanks!
Click to expand...
Click to collapse
Are you positive your path is correct..... and if it is check and make sure there are no spaces or weird characters....
Sent from my Incredible using XDA App
was it working before and it stopped working? I noticed that my Mac doesn't recognized the phone every once in a while with CM7 and the Incredikernel. I have to unplug it and plug it back in couple times to get it to register.
newtoroot said:
Are you positive your path is correct..... and if it is check and make sure there are no spaces or weird characters....
Click to expand...
Click to collapse
I'm pretty sure it's correct because the Terminal recognizes the "adb" commands as valid. For example, I can run "adb shell" and it returns "error:device not found". So I don't think that's the issue...
Grooby97 said:
was it working before and it stopped working? I noticed that my Mac doesn't recognized the phone every once in a while with CM7 and the Incredikernel. I have to unplug it and plug it back in couple times to get it to register.
Click to expand...
Click to collapse
The thing is, the computer recognizes the phone just fine. I can plug it in and select "disk drive" and both the phone and SD card mount without an problem. But when I try to run adb commands that's when it doesn't seem to see it for some reason.... I really don't get why this could be, when without changing a single setting on the phone it works fine on a PC. I'm probably missing something obvious, but I don't know what that might be.....
nufan947 said:
I'm pretty sure it's correct because the Terminal recognizes the "adb" commands as valid. For example, I can run "adb shell" and it returns "error:device not found". So I don't think that's the issue...
The thing is, the computer recognizes the phone just fine. I can plug it in and select "disk drive" and both the phone and SD card mount without an problem. But when I try to run adb commands that's when it doesn't seem to see it for some reason.... I really don't get why this could be, when without changing a single setting on the phone it works fine on a PC. I'm probably missing something obvious, but I don't know what that might be.....
Click to expand...
Click to collapse
forgive me if im asking a dumb question im just trying to help you narrow down your problem,,,,,, did you check and make sure usb debugging is checked? and if you type adb devices what does it say? ive noticed on the newer sdk that i installed they moved adb to platform tools and out of tools so you might check those things
Yeah, USB debugging is checked... when I type "adb devices" I get "List of devices attached" and it doesn't actually list anything. And yeah, the Terminal is definitely pointing to the right folder, I don't think I'd be getting any sort of response if it was pointing towards the wrong place, right?
ADB definitely works. It just doesn't like my phone for some reason
Well it definitely works on OS X 10.6 that's what my laptop uses. Have you tried parallels or bootcamping into a version of Windows? My work iMac is a piece of dirt and does not like adb thru mac os x but works fine with win xp on parallels.
Yeah, I'm running 10.6 on my laptop as well... right now for when I want to use ADB I've just been running XP on my bootcamp partition, which works fine. It's not the worst solution in the world, but I'd prefer being able to do it on the Mac side of things, which is where I spend far more time.
This is very mysterious....

[Q] Not able to debug!

So I am a bit done with just flashing other roms to my kaiser and also want to develop some apps and want to experiment with making my own roms, but initially just porting roms from other devices like the HTC wildfire. But I am not able to use debugging:
So this is what I have done I have installed the android sdk and also installed the ADT plugin for eclipse. Then I have compied the android-sdk file to the root of my c drive so it is easier to use the command line interface with this file. I then run the following commands in the cmd, as admin:
adb kill-server
adb start-server
adb devices
And here is where the **** just hits the fans I am unable to see my device in the list of devices. While my device is recognized by the computer as ADB Interface > HTC Dream Composite ADB Interface in the device manager section. (But I must note that when I click on the device it is noted: "Device cannot start. (code 10)" ) Also when I double click on the device in the regular computer windows (where all your hd's are showed) the file system of the device is empty!
So does anyone have any advice?
Have you test it from a live usb or CD GNU/Linux like Ubuntu?
Nope, I hoped that it would work in Windows, but I will try it in Linux if that would solve it.l But can you see anything that i am doing wrong or is it just Windows
I always have problems with USB management on Windows, all versions...with all my computers. Linux kernel seems to be better, imho, for USB.

trouble enabling ADB access

Hi,
I've tried to root my Kindle and ran into some problems.
I installed the drivers and they seemed to work fine but I couldn't establish the ADB.
when I go to the CMD and type in there "adb devices" I get this:
C:\Users\Nikita>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
the driver seems to be just fine and the Kindle is connected to the computer so I just can't figure out the problem.
the driver is:
Android Composite ADB Interface
Thanks for the help.
Josepho1997 said:
You didnt even open adb. You just went to a random place and typed adb devices.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
What do you mean by that? I thought that installing the ADB drivers is the only thing I need to do..what else?

[Q] Kindle 2nd gen issue

Hello all.
This is my first post and my first experience with android devices so please go gentle.
I recently purchased for £20 a kindle fire 2nd gen otter.
The reason it was so cheap was that it is stuck in a bootloop.
The friend I bought it from intended to bring it back to life and install CM to the device but never got round to it. So I took it on as my little project.
I have been scrolling through pages and pages of google and this site for research but have hit a brick wall.
I purchased a factory or fastboot cable knowing I may well need it. I also have the original cable.
When trying to boot the device I get the usual kindle and fire logo orange as of it's booting then every 10 seconds or so the screen will go black and back to the kindle fire bootloop.
I have tried to use the normal cable to link to my desktop on windows 7. When doing this the device will not show up in device manager at all.
When I plug it via a fastboot cable it boots into fastboot with a green flashing light on screen and is recognised as an otter prod 04 on device manager.
I have installed the latest sdk. Also fastboot.
I have changed the windows environment variables under path on the PC and can successfully run fastboot in a command window. I can also issue adb commands through also a dos command window so I know both are working correctly on my PC.
I have typed in fastboot devices
I have also typed in adb devices.
When I issue either or these commands my device will not be found through the command window. It just returns a blank.
I know this is due to drivers not working correctly so have opened device manager. Update driver , have tried the android sdk path for drivers have also tried my adb drivers. I have also downloaded the latest Google USB driver and none will install. I have a programme running that allows any unsigned driver to be installed on win 7 so I know it's not that.
All I have returned is cannot install drivers for otter prod. 04
The only thing it will accept is choosing from a list of devices, Then android. And installs as adb device or adb composite device, this is obviously useless as I can't boot device into normal mode to be able to use it as adb or issue commands to it.
I have tried everything. I know this kindle is save able I just don't know how. My end result is make it bootable, root device and install CM
I have trawled through loads of pages of info and tried tried and tried for answers but nothing works. Can anybody shed some light on the issue for me.
Many thanks in advance
Just thought id add, I have also tried all timed variations of holding down the power button
I have also let device run flat and recharge. Have also tried a different PC and USB port.
Hello Vincent,
ADB stands for Android Device Bridge (Just wanted to point that out since you are new to Android).
The ADB Composite Device driver lets your computer and your Kindle Fire device communicate with each other. This includes ADB as well as fastboot.
Install the ADB Composite Device driver in Device Manager and then go to the command line window and type fastboot -i 0x1949 devices and it should now show up in fastboot.
Now flash the stock bootloader, recovery, and system img files to your device. After that, you should see it boot successfully.
Hope this helped, and don't be afraid to ask me more questions about your device!
phiftyopz
Sent from my iPhone using Tapatalk

Categories

Resources