not recognised by adb?

[Guest rjm2k]

Any advice, tried enabling usb debugging and connecting to xp laptop, adb won't recognise it, the device doesn't fully install under xp device manager shows zte hsusb as being incorrectly installed. I think fastboot works, I can do fastboot reboot and fastboot devices lists ? as the device.

[Guest ritterkeks]

I have got the same problem under win7, driver wont install.

Under Linux adb wont recognize the SF

[Guest jutley]

If you need to get recovery on the and root and custom rom and you cans get adb to work use my guide look guide for beginners and or non working adb

http://android.modaco.com/content/zte-blad...ustom-recovery/

Edited October 21, 2010 by jutley

[Guest ritterkeks]

nice howto.

however, I have alreade flashed clockwork over fastboot.

Since the SF's android kernel wont support tethering apps,

I wanted to use proxoid and adb (tcp tunneling) for web connection.

As atm I have only my mobile to get access to the internet, this is very annoying.

I can switch my SIM to my old WM Phone and it works perfectly without any configuration (have been surprisd myself)

[Guest ritterkeks]

ive just been to the console and tried to start adbd (which is in /sbin )

as root and also as user.

the result is the same:

cannot bind 'tcp:5037'

any clue what this could could mean?

[Guest zuccster]

ive just been to the console and tried to start adbd (which is in /sbin )

as root and also as user.

the result is the same:

cannot bind 'tcp:5037'

any clue what this could could mean?

Something (an existing adb?) is already bound to 5037.

# netstat -tlnp | grep 5037

Will tell you what (may need to be root if you started adb as root)

Kill it and try again.

[Guest ritterkeks]

Something (an existing adb?) is already bound to 5037.

# netstat -tlnp | grep 5037

Will tell you what (may need to be root if you started adb as root)

Kill it and try again.

ah shure. tried it and adbd is running - so this may mean that there is no problem on the phone side?!

will try netstat on linux, but i dont think anything uses that port.

and still, why refuses windows to use the driver which comes with the adb package with the blade?

[Guest x.balli.x]

i got adb working on windows 7 ,but now am trying to run it in ubuntu 10.10 , when i write the command

adb devices

????????? no permissions'[/codebox]

any idea what the problem here, if i need to edit udev, which line do i have to add in there?

Edited November 2, 2010 by x.balli.x

[Guest rjm2k]

i got adb working on windows 7 ,but now am trying to run it in ubuntu 10.10 , when i write the command

adb devices

????????? no permissions'[/codebox]

any idea what the problem here, if i need to edit udev, which line do i have to add in there?

on linux you have to do everything as root

[Guest ritterkeks]

on linux you have to do everything as root

i have found the advice (also in a thread here) to "umask"? or "chown" the device via an udev rule to make it avaliable for the user....

didn't work for me though, seems that ive done something wrong

[Guest TheTwiddler]

i have found the advice (also in a thread here) to "umask"? or "chown" the device via an udev rule to make it avaliable for the user....

didn't work for me though, seems that ive done something wrong

The following works for me on Ubuntu 10.10, with Eclipse 3.5.2, the ADT 0.9.9 plugin and SDK Tools R7 as described here Android ADT Plugin and here SDK Tools R7

This link Android Device Development says that you need to login as root and create a file named /etc/udev/rules.d/51-android.rules, which can be done as follows from a terminal window:

$ sudo touch /etc/udev/rules.d/51-android.rules

$ sudo chmod 644 /etc/udev/rules.d/51-android.rules

The file should then have the following permissions (use ls -la /etc/udev/rules.d)

-rw-r--r-- 1 root root 163 2010-10-27 00:18 51-android.rules

Edit the above file in a text editor to contain the following two lines:

SUBSYSTEM=="usb", SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="1354", MODE="0666"

SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", SYSFS{idProduct}=="d00d", MODE="0666"

The first line matches the vendor/device Ids for the Adb interfaces that the SF presents when powered up normally and connected via USB.

The second line matches the vendor/device Id for the fastboot interface that the SF presents when powered up with the VolumeUp button pressed, though I have not yet tried this for myself.

Once done, I would recommend rebooting Ubuntu so that the above rules are activated.

If I then power the SF up normally and connect it via USB, then cd to where I have the SDK Tools installed, I can launch an adb shell as follows without needing to become root or use sudo

$ cd /home/android-sdk-linux_x86/tools

$ ./adb shell

#

Hope this is enough to get you going.

Edit:

Fastboot does work with the above setup, but is isn't included in the SDK Tools.

A bit of Googling and I found a copy here: Fastboot for Linux. Download it and copy/move it to the Android Tools directory where the adb executable lives and make it executable as follows:

$ chmod 777 fastboot

Edited November 4, 2010 by TheTwiddler

[Guest x.balli.x]

Thanks alot, will try it tonight

[Guest robot1000]

If you're connected to a home/office network, you can get the following App which allowes for wireless adb

http://www.appbrain.com/app/adbwireless-(w....es.adbWireless