Database Info

[Q] ADB (again)

I have installed the moto drivers and then connect my Xoom to the B port. I have debugging turned on.
Here's what I get:
E:\xoom>adb devices
List of devices attached
161c110242c015d7 offline
E:\xoom>adb shell
error: device offline
I have run clean and reinstall on the installer without any change.
Any advice?

You need to be in the folder on your computer with adb in it.
Sent from my Xoom using Tapatalk

I am in that folder.

Is your device locked? As in, do you have a lock password/PIN that you need to input first?

Try a different cable.

Different cable no help. Any other ideas?

Just an idea... are you using a USB hub or one of the USB ports from the front of your PC? Sometimes these ports don't provide enough power to communicate with certain devices. Try one of the ports on the back of the PC.
Other than that, reboot your PC and the Xoom and try again

I'll be darned! I plugged it into the back (USB port on motherboard) instead of the front and voila!
You are the man!

Now that you have answered that question so well, please answer this one!
I am trying to run adb install xxxx.apk but it just hangs. I have the Xoom set to allow installation of non-market applications.
Any ideas?

Never mind - a reboot all around fixed that. Thanks for everyone's help.

no ADB connection anymore

ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "ADB devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!

yasinis said:
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "dab devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
Click to expand...
Click to collapse
shouldnt it be adb devices instead of dab ?

I wanna try this ABD but there no link?!!

Shouldn't this ABC post be somewhere else?

you guys should quit cluttering this thread and help him figure this whole KFC thing out....

sheetmetalninja said:
you guys should quit cluttering this thread and help him figure this whole KFC thing out....
Click to expand...
Click to collapse
You're right.
But I also don't know anything about BAD or FASTBOOB or anything like that. I don't like reading. :[

yasinis said:
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "dab devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
Click to expand...
Click to collapse
go into devmgmt.msc and see if your phone shows up under adb interfaces. if not, could be 1) bad usb cable, 2) bad usb port, 3) bad adb driver.

Check the drivers, you may need to update them
Sent from my Desire HD using XDA App

taney said:
go into devmgmt.msc and see if your phone shows up under adb interfaces. if not, could be 1) bad usb cable, 2) bad usb port, 3) bad adb driver.
Click to expand...
Click to collapse
how 2 do that? i mean what do you mean with devmgmt.msc(device management...?)
1) usb cable is good, the original one. also tried different usb cables, it doesn't matter.
2) usb port is also ok, other devices running out of the box (f.e. dvd drive oder dslr)
3) adb driver already updated via "Android SDK and AVD Manager".
i installed Android SDK tools, SDK Platform tools, sdk platform (--> is there sth. missing?)

Try disabling debugging on the phone, plug it in, reboot it, then enable debugging again

Romanbb said:
Try disabling debugging on the phone, plug it in, reboot it, then enable debugging again
Click to expand...
Click to collapse
no sorry...won't work..
getting the same:
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
also tried without fastboot rebooting.

there are news guys:
just got an windows 7 personal computer for a couple of days.
installing the sdk and usb driver just worked fine.
why it doesn't work for mac?
already installed all new...

You may also check the cable you're using to connect the phone to your Mac. I was getting the same problem when trying to use the cable from my car charger - the phone was not even visible on the system list of USB devices. Using the cable that came with the phone did the trick.
(although if you used the same cable with Windows and it worked, my hint won't be of much help)

Do you got HTC sync installed on your PC?

TheStigx said:
Do you got HTC sync installed on your PC?
Click to expand...
Click to collapse
please remember - i'm using a MAC!
so finally i tested my device with several computers at the university.
i just found out, that the problem may been caused of my installed mac osx lion - but don't ask me why!
on the mac of my prof (also osx lion with latest updates) it worked out of the box...
--> so i'm gonna making backups now and will format my hard disk and reinstall lion again.
i'll give u feedback again ;-)

Have you closed the htc-sync application? solved the connection-error for me...

Maeffjus said:
Have you closed the htc-sync application? solved the connection-error for me...
Click to expand...
Click to collapse
again guys:
I'm using a MAC!
is there any official sync app for mac i don't know about??

ok guys,
just reinstalled my system an got the problem away..
i don't know why this was so, but i'm happy to make it work now.

yasinis said:
ok guys,
just reinstalled my system an got the problem away..
i don't know why this was so, but i'm happy to make it work now.
Click to expand...
Click to collapse
ok, just found out where the problem was caused. it was EasyTether!
this will help:
Code:
If you have installed EasyTether on OS X, the EasyTetherUSBEthernet.kext can prevent adb from communicating with your mobile device.
If you use Easy Tether, BEFORE you plug in your phone run:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
(or unplug/plug your phone in after)
If you are done debugging and want to use EasyTether again, either restart or:
sudo kextload /System/Library/Extensions/EasyTetherUSBEthernet.kext
If you want to remove the EasyTether kext so it never hassels you again:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
sudo rm -rf /System/Library/Extensions/EasyTetherUSBEthernet.kext

[SOLVED] Infuse wont connect to Ubuntu....

UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.

weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.

Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.

Linux driver should be perfect, before connects to PC the mass storage mode should be selected.

dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/

well I see you fixed it. did you get adb going?

Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk

are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.

Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone

[Q] Updated to JB, and a few issues started happening...

I updated to Jellybean last night, and was in the process of rooting it and installing CWM again. I plug the pad into my computer, and realized that it's not being recognized by my computer. It's not even charging it! However, when I attach the wire to the wall adapter, it's charging. When I plug it into my comptuer, and if the pad's screen is on sleep, it autowakes it though.
I tried using someone else's cable and the same issue still occurs. Is there a way I can install CWM on my pad and root it without using adb commands on my computer? because that could be my only solution now. Unless, there's a way I can get it to recognize on my computer.
P.S. I had root+CWM installed when I was on ICS.

BUMP.
No one else has this issue? I'm 99% sure its my port, but how can i ota fastboot and flash cwm and root?

Caduceus46 said:
I updated to Jellybean last night, and was in the process of rooting it and installing CWM again. I plug the pad into my computer, and realized that it's not being recognized by my computer. It's not even charging it! However, when I attach the wire to the wall adapter, it's charging. When I plug it into my comptuer, and if the pad's screen is on sleep, it autowakes it though.
I tried using someone else's cable and the same issue still occurs. Is there a way I can install CWM on my pad and root it without using adb commands on my computer? because that could be my only solution now. Unless, there's a way I can get it to recognize on my computer.
P.S. I had root+CWM installed when I was on ICS.
Click to expand...
Click to collapse
It's a problem that some users have, and in my mind it was not resolved.
But If you want to install your recovery, you can do with TWRP recovery and Terminal Emulator app (play store)
You should search if you can make it by the same process for CWM, apparently no, cause you need fastboot.
Try this : [GUIDE] Help for flash more faster when you use Fastboot Line Command maybe you've got a problem with your fastboot. I don't know.
It's an easy installation of fastboot.

Caduceus46 said:
BUMP.
No one else has this issue? I'm 99% sure its my port, but how can i ota fastboot and flash cwm and root?
Click to expand...
Click to collapse
There is an option to allow ADB over network, but I haven't experimented with it. If you were adventurous, you could try it and let the community know what happens?
In the ROM I'm running (Baked Blackbean #5, Android 4.1.1 and based on CyanogenMOD) you can select this option by going to Settings-->Developer Options--->"ADB over network"
I just attempted to do this, and it worked rather flawlessly. Enable ADB over network, and it will give you the IP address of your device (in my case, 172.16.1.22:5555).
Then, follow the steps below. This assumes you have a rooted device. To do the terminal commands on my tablet, I use the "Terminal Emulator" program, free from the Market.
This is really simple.
First make sure you are rooted. Download a terminal emulator from market (there are lots that are free). Make sure that your android is connected to your WiFi and get the WiFi IP address. Open the terminal program and type:
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Now go to your computer (assuming that you are using windows) create a shortcut on the desktop for "cmd.exe" (without the quotations).
Right click on the cmd shortcut and choose "Run as Administrator"
Change to your android-sdk-windows\tools folder
Type:
adb connect ***wifi.ip.address***:5555
(example: adb connect 192.168.0.105:5555)
adb should now say that you are connected. Note: if you are too fast to give the connect command it may fail. so try at least 2 times 5 seconds apart before you say this doesn't work.
Click to expand...
Click to collapse
To put the device back to USB, once you get it working (because ADB over network is NOT SECURE):
And you can disable it and return ADB to listening on USB with
setprop service.adb.tcp.port -1
stop adbd
start adbd
Click to expand...
Click to collapse
Got this information from: Here
I do want to note that all I did was verify that ADB is detected over wifi. When I type 'adb devices' on my Windows 7 PC, it detects the IP address of my tablet, which indicates the two devices are communicating correctly. I didn't try pushing/pulling files since I have no need for that, but hopefully this helps you.

I will try next week (cause I'm off @t work) this process, just for seen if it works well.
I don't need it, but it's interesting to know this.
The post which speak about this use is in N1 forum => here -> Post #22.
But it's more complete here : How can I connect to Android with ADB over TCP?
Apps which are automate this process :
- adbWireless - no updated since Sept 5 - 2010 - You need root access
- WiFi ADB - You need root access - Updated September 29, 2012
- ADB WiFi - Updated August 27, 2012 - You need root access
Well done @opethfan89 :good:

philos64 said:
I will try next week (cause I'm off @t work) this process, just for seen if it works well.
I don't need it, but it's interesting to know this.
The post which speak about this use is in N1 forum => here -> Post #22.
But it's more complete here : How can I connect to Android with ADB over TCP?
Apps which are automate this process :
- adbWireless - no updated since Sept 5 - 2010 - You need root access
- WiFi ADB - You need root access - Updated September 29, 2012
- ADB WiFi - Updated August 27, 2012 - You need root access
Well done @opethfan89 :good:
Click to expand...
Click to collapse
Thanks!!
Sent from my Transformer Pad TF300T using xda app-developers app

@opethfan89, ADB over network will probably not work for me because I don't have root anymore. Appreciate the help :good:
@Philos64, thank you for your post as well. I will try that sometime this week and let you know the results as well.

Oh wait, I don't think that method will work. I will need su permission to flash twrp. I don't have root anymore either

Caduceus46 said:
Oh wait, I don't think that method will work. I will need su permission to flash twrp. I don't have root anymore either
Click to expand...
Click to collapse
Perhaps I'm wrong, but you don't need root to be able to flash a custom recovery, since the recovery operates outside of the Android OS (and root only affects app permissions within the OS). You would just need fastboot to be able to flash the recovery. Do you have the proper drivers installed on your computer? Can you try different USB ports? Maybe a USB hub? Try it on a different computer to, just to process of eliminate any kinks between the tablet and the physical connection of the USB cable.
Sent from my Transformer Pad TF300T using xda app-developers app

How to enable USB debuggin with broken touchscreen?

Hi
I have a old nexus with broken touchscreen . I want to use it via mirror on pc.
unfortunatly USB debuggin wasn't enable so i can't install any app.
any tips?
thanks
PS: i saw many use usb adapter to connect a mouse but i don't have it
EDIT: right now i just need a rom/kernel with USB debugging mode enabled by default

the screen still works , only the touch screen is broken
power , and volume bottons still work
the device is rooted

If it's only installing apps you could install them via recovery. (as zip)
Or you could check for a cheap replacement touchscreen.

nonameleft4me said:
If it's only installing apps you could install them via recovery. (as zip)
Or you could check for a cheap replacement touchscreen.
Click to expand...
Click to collapse
thanks for the answer!
sorry i forgot to mention that i need USB debuggin for make the app works correctly.
I'm trying now to find out what rom i have installed and maybe then find a kernel with OTG support . (yes i found a otg cable )
i'm not a expert of rooting

I think google has an app called voice control. Not sure how operational it is though. Supposedly you can control the entire system via voice.

nonameleft4me said:
I think google has an app called voice control. Not sure how operational it is though. Supposedly you can control the entire system via voice.
Click to expand...
Click to collapse
i need to unlock the phone and tap on the widget "search" to start voice command .
I think the best way is to find a way to enable OTG and then use a usb mouse

Boot into Recovery and mount*Data*partition.
Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace*~/*with home directory of your OS.
Open that file in a text editor and you would possibly see*mtp*written there. Change it to*mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using*adb pullbut doing:
adb shell echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the*echo*command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
Unmount*Data*and reboot into Android OS. USB Debugging would probably be enabled.
Sent from my Aqua Trend using Tapatalk

Itzabhaysingj said:
Boot into Recovery and mount*Data*partition.
Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace*~/*with home directory of your OS.
Open that file in a text editor and you would possibly see*mtp*written there. Change it to*mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using*adb pullbut doing:
adb shell echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the*echo*command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
Unmount*Data*and reboot into Android OS. USB Debugging would probably be enabled.
Sent from my Aqua Trend using Tapatalk
Click to expand...
Click to collapse
thanks!
i tryed
1) i went in recovery mode
2) i connect via usb the nexus4 to my pc
3)went in "mounts and storage"
4)then "mount /data"
5)in cmd i tryed your command "adb pull /data/property/persist.sys.usb.config" but i says i'm unauthorized
i checked via command "adb devices" and it return a alphanumerica string plus "unauthorized"
i tryed then to
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
adb shell reboot
but it still says error : device unauthorizated . please check the confirmation dialog on your device

i tryed also with a different version of adb and now gives me after "adb devices" an "offline" response
NB: if i connect the phone (not in recovery mode) via usb i can copy files in and out (i can explore onlyfew folders) , maybe this could help.

hartman11 said:
i tryed also with a different version of adb and now gives me after "adb devices" an "offline" response
NB: if i connect the phone (not in recovery mode) via usb i can copy files in and out (i can explore onlyfew folders) , maybe this could help.
Click to expand...
Click to collapse
Sorry but this could not help... Now only thing you can do is connect any USB mouse to your phone via otg cable (as it is not costly also), and you can also try USB gamepad. I also have used USB gamepad before when my touchscreen was not working.
Second thing you can do is download any android device manager for your PC like mobogenie or mobilego they directly install any app from play store to you android device, through USB.And I don't think they need USB debugging option to be enabled.
Sent from my Aqua Trend using Tapatalk

my problem is not installing an app (i could do it in recovery mode with a .zip) but enabling the USB debuggin
I have a otg cable but not the "Y" type ( the one with power source ) , also i don't know if OTG is supported by my kernel . I would like to install maybe another kernel which has OTG support and usb debuggin mode enable by default but i don't know what kind of rom i have D:

right now i just need a rom/kernel with USB debugging mode enabled by default

up