Sorry, this "export ADB_TRACE=all" should be entered in root shell, just before ./adb command execution, for example after "sudo -i". About USB mass storage, I think it is wrong. When I connect my Android device I do not get mass storage, unless I switch it on on a telephone. And I can't connect with adb after this.

What about "sudo ./adb devices" after disabling mass storage?

PeterUK

04-27-2012 06:12 PM

Quote:

Originally Posted by eSelix
(Post 4664908)

Sorry, this "export ADB_TRACE=all" should be entered in root shell, just before ./adb command execution, for example after "sudo -i". About USB mass storage, I think it is wrong. When I connect my Android device I do not get mass storage, unless I switch it on on a telephone. And I can't connect with adb after this.

What about "sudo ./adb devices" after disabling mass storage?

I did:

sudo -i export ADB_TRACE=all

and it still not working!

Just one thing there is not a memory card on the phone, would that make any different?

You said when turn the phone? What do you mean by it? What state was it before and how did you get there?

PeterUK

04-28-2012 09:15 AM

Quote:

Originally Posted by PeterUK
(Post 4664949)

I did:

sudo -i export ADB_TRACE=all

and it still not working!

Just one thing there is not a memory card on the phone, would that make any different?

You said when turn the phone? What do you mean by it? What state was it before and how did you get there?

I am trying in another machine with a different kernel and download again the SDK and I get this:

You said when turn the phone? What do you mean by it? What state was it before and how did you get there?

No, sorry for my bad english, by "switching on" I mean enabling proper option. Anyway if you get response after "./adb devices" then it is correct.

If you get "???????????? device" then thats mean your phone has been recognized, but I suspect that you have no permissions to access it. Are you doing it as root? If not as root then everything is ok. But to access your device on user account, you need proper udev rule, check by "lsusb" your "idVendor", it probably changed after switching to non mass storage mode.

No, sorry for my bad english, by "switching on" I mean enabling proper option. Anyway if you get response after "./adb devices" then it is correct.

If you get "???????????? device" then thats mean your phone has been recognized, but I suspect that you have no permissions to access it. Are you doing it as root? If not as root then everything is ok. But to access your device on user account, you need proper udev rule, check by "lsusb" your "idVendor", it probably changed after switching to non mass storage mode.

You should see something like this:

Code:

List of devices attached
HT0CBRX11571 device

Thanks for your input here! I thought give an update what I have done so far. In Linux 2 PC manage to get in recognize as ??????? device I am going to play a bit with udev to see if it changed but I did create the rules for that PC, I also manage to download my first application by adb command line but Eclipse still not be able to download it to the phone.