Database Info

ADB won't find the device... can't root. Going insane.

I installed the Samsung USB drivers on my Win 7 64-bit laptop. I have ADB installed, and have used it for other devices, no problem. I can still use it to connect to my Color Nook.
I kill-server; start-server, and look for devices - nothing. But I can see the USB installer and those other few files on the phone, and I can see everything on the sdcard.
Any ideas? I'm going crazy here.

Do you have USB debugging on?
Sent from my SCH-I510 using XDA App

I had this problem as well.
First see if you have the "SAMSUNG usb driver" installed in control panel programs.
If not, take off usb debug and connect phone to computer. Then you should get a "install verizon software" option once you plug it in. Install software .. Then, enable "usb debuging" try it again, if that doesn't work .. remove verizon software, not usb drivers. This is basically what i did, and it started working

[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] TF101 usb dosent't get connected to linux and windows...

Ok,
I'm not new here but Im new with a TF101...
I have 3 rooted devices at home.
Now when I plug the TF that I bought used, it dosent get detected. I mean at all!
Not "!" yellow in windows and nothing it linux, no noise nothing.
I have usb dev checked...
Now, do I need usb 3.0 to just get it detected and root it using xp or linux???

joevirus563 said:
Ok,
I'm not new here but Im new with a TF101...
I have 3 rooted devices at home.
Now when I plug the TF that I bought used, it dosent get detected. I mean at all!
Not "!" yellow in windows and nothing it linux, no noise nothing.
I have usb dev checked...
Now, do I need usb 3.0 to just get it detected and root it using xp or linux???
Click to expand...
Click to collapse
Go to Settings - Storage - USB computer connection - tick Media device (MTP)

hapahopi said:
Go to Settings - Storage - USB computer connection - tick Media device (MTP)
Click to expand...
Click to collapse
Its already at MTP...
Any way to root without computer?

I've been having the exact same problem for a few months now , I reckon i either have a faulty usb cable or the port has been damaged . I hope there's a software fix for this .

Happydondavid said:
I've been having the exact same problem for a few months now , I reckon i either have a faulty usb cable or the port has been damaged . I hope there's a software fix for this .
Click to expand...
Click to collapse
Ok and whant have you done to fix it?
New usb cable?

I've not managed to fix it yet . When i plug my TF into my pc it seems to think its charging but the pc doesn't register it at all , if i get a new usb cable and it works i'll report back .

Well does anyone know if this is a problem with the cable or not ?

Happydondavid said:
Well does anyone know if this is a problem with the cable or not ?
Click to expand...
Click to collapse
I have the same problem. I sent my tf101 to the Asus service center to have it repaired. When it came back it would connect to the PC. After a few months it would not connect. Same problem. It appears to me to be software related somehow. In my case the cable has nothing to do with it. None of the suggestions on this or other forums work. Asus does not respond. Maybe Jelly Bean will fix it. Or maybe not.

are you able to ./adb connect to the asus via usb? if so then that will tell you that the problem is not the cable, it's not the usb version, it's not the device hardware. its likely a driver install issue in windows. i would boot into android and make sure that android debugging is selected in the developer settings menu. then try an adb connection. im not sure about how to install all the stupid drivers in windows because i do everything in linux and its soooooo much simpler.
f it is in fact the hardware cable or port that is not working properly then you can always move files to and from the device over wlan connection, with either adb tcp connection, or using some file manager such as es file explorer. just remember as long as you can get an
./adb connection to your android then anything is fixable. ADB IS YOUR FRIEND. get to know it well.

same problem here...tried everything except format the pc (running windows 7)
I have a simple question for the people WITHOUT problem connecting tf101: when you connect the tablet (mtp or not) what do you see on the screen of the pc? something related to autoplay? Are you able to copy, move files to and from the tf101 like a usb stick?

qandrav said:
same problem here...tried everything except format the pc (running windows 7)
I have a simple question for the people WITHOUT problem connecting tf101: when you connect the tablet (mtp or not) what do you see on the screen of the pc? something related to autoplay? Are you able to copy, move files to and from the tf101 like a usb stick?
Click to expand...
Click to collapse
I dont ever connect my devices as mass storage to he computers at all. i just do everything via ./adb usb or ./adb tcp connections over wifi. or i use es file explorer setup as an ftp server on my devices and move files around that way if i need to. but i went ahead and pulled out my windows asus tf101 drivers and sync app and linked them for you at the bottom. my advice really is to lose windows and stick with doing everything on android with linux. soooo much better.
https://www.box.com/s/q2j8n7h8xi5o3ld2bt5z

thank you for your long reply! and obv for the files, I'll give it a try!
I admit that sometimes I used swiftp (over wifi) but every time I have to disconnect pc & tablet from the modem...Sometimes use bluetooth but it's too too slow!!! thank you again!!!

I understand but how do you root using adb tcp???
Envoyé depuis mon Transformer TF101 avec Tapatalk

when I rooted moths ago I used "razorclaw" (and my tf101 is a b70). I use adb with other devices and is very cool but I never need to use with the tf101...

joevirus563 said:
I understand but how do you root using adb tcp???
Envoyé depuis mon Transformer TF101 avec Tapatalk
Click to expand...
Click to collapse
ok so adb over a tcp connection it works pretty much like adb over usb except your connection is done over the network. so lets say your tf101 and your computer are both on the same WLAN. you can enable enable adb over tcp and connect to it with the computer over the network. however to enable adb tcp connections you need to already have root.

The Real Question when USB does not connect.
haxin said:
ok so adb over a tcp connection it works pretty much like adb over usb except your connection is done over the network. so lets say your tf101 and your computer are both on the same WLAN. you can enable enable adb over tcp and connect to it with the computer over the network. however to enable adb tcp connections you need to already have root.
Click to expand...
Click to collapse
I have both Linux and Windows systems. My TF101 does not connect on either machine. My assumption is I have a internal problem. I have tried two different cables and systems. I need to ROOT the TF101 and upgrade to Jelly Bean. From this post I am told to use ./adb commands over tcp and I appreciate that, but I need to have a rooted TF101.
The ultimate question is can I root the TF101 without using the usb connector? I suspect not, but will defer to the expert developers.
I have tried with settings in various selections like MTP "yes" or "no", Developer USB "yes" or "no" or both on or off at the same time. I have loaded and unloaded Windows Asus Sync and USB drivers many times.
The strange thing is if I am attached to the keyboard, I can see any USB thumb drives attached to the keyboard including my USB serial adapter. I would think USB would not work if the cable does not work. Also if anyone has a link to instructions for loading ADB on Linux Mint 13 64bit, I would appreciate the link.
Thank you in advance.

beware of usb cable
Hi,I personnally own a TF101 sb50.
I had some trouble with usb. Tha cable was ok for charging but didn t register correctly under an usb connection ( it showed up and got kicked out in windows didn t register in lsusb on linux)
If you check the diagram for the cable, it s well endowed there 's resistance inside the cable, and multiple connection.
Depending on your version it doesn t use the same pin, even if it's the same cable.
You can buy a cable on ebay for around 10 euro in europe ( i did it s ok) or buy it cheaper from china(no idea about quality).
to sum it up even if your cable work with another TF, it doesn t mean your cable is not faulty ( i have bounce a nano osci on the faulty cable , and it showed no apparent flaw.) and buying a new one was the solution for me.
good luck for rooting (sb50 :: no need to adb)

The ADB thru WiFi solution worked perfectly for me thankfully, and I am one of the many others who have been having major trouble getting Windows and Linux to recognize the Intercept.
Not sure if this is a duplicate post somewhere, but here's my version using Linux:
1. Go to the Play Store and download the 'ADB over Wifi Widget' app.
2. After installed on your device, the app should be on your home screen. Tap it once to toggle on. You should see an IP address and a port #.
Note the IP address, as this is the address of your device.
3. Open a terminal in Linux.
4. CD to the folder that contains your ADB files. (example: cd /androidsdk/platform-tools)
5. Enter the following code:
chmod 755 ./adb
./adb connect <enter IP address here without brackets of course>
6. You should now be connected to your phone.
Hope this helps...

pm124493 said:
I have both Linux and Windows systems. My TF101 does not connect on either machine. My assumption is I have a internal problem. I have tried two different cables and systems. I need to ROOT the TF101 and upgrade to Jelly Bean. From this post I am told to use ./adb commands over tcp and I appreciate that, but I need to have a rooted TF101.
The ultimate question is can I root the TF101 without using the usb connector? I suspect not, but will defer to the expert developers.
I have tried with settings in various selections like MTP "yes" or "no", Developer USB "yes" or "no" or both on or off at the same time. I have loaded and unloaded Windows Asus Sync and USB drivers many times.
The strange thing is if I am attached to the keyboard, I can see any USB thumb drives attached to the keyboard including my USB serial adapter. I would think USB would not work if the cable does not work. Also if anyone has a link to instructions for loading ADB on Linux Mint 13 64bit, I would appreciate the link.
Thank you in advance.
Click to expand...
Click to collapse
ok when you say that the tf101 doesnt connect in either your windows or linux machine, what do you mean exactly? you mean it doesnt show up as a mass storage device or an MTP device? and have you downloaded and installed the android-sdk in linux? and when you connect the tf101 to your linux machine, do yo uhave usb debugging enabled in the developer settings menu, and are you using the "./adb devices" command in the linux terminal from your /android-sdk/platform-tools/ directory?
also you should be able to flash a custom recovery which will enable you to flash custom rom without using the usb cable. theres a couple files that you need to put on your tf101 in the /sdcard/ directory first.
one is the recovery blob and if you want to keep the stock rom and kernel but just root it then youll need the superuser zip i have included both of them at the bottom.
for starters you need to install a terminal emulator app on the tf101 from the play store.
then once you have the recovery blob on your device in /sdcard/ you can continue. (remember /sdcard/ is the internal memory not the micro sd card)
start the terminal emulator on the tf101 and enter these commands.
mv /data/local/tmp /data/local/tmp.bak
exit
(open another terminal window on the tf101 and enter these commands)
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
(now reboot the tf101 when it boots into android start the terminal emulator app again then enter these comands)
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
exit
(now you should have a team rogue recovery flashed to your tf101)
reboot your tf101.
now you can hold the vol -down button while you power on the tf101 you will see a message at the top of the screen that says soomething like "Checking for RCK" when you see that press the vol- up button right away, this should boot you into the team rogue recovery where you can flash custom roms or just flash your superuser.zip to get root.
hopefully this makes sense and hopefully it works for you.
remember you have to extract the recoveryblob from the zip folder before you move it to the /sdcard/ on your asus. the superuser.zip can remain zipped though.

I had the same problem:
windows will not notice my transformer (rooted).
( usb debugging is on, android 4.0.3 with Android Revolution HD 3.5.1.)
i know in the past it works.
adb list ( of devices) ist empty also. Same Problem with the two cables i have.
can you give me a help what i can do?
Sorry for my poor english
kind regards
gandalf

CM12S and adb device on Windows 7

My setup used to work
Windows 7
CM11S
MTP work just fine. Can browse OPO /sdcard from windows 7
adb device work just fine. I can run all adb commands without problem: devices, shell, push, pull, etc
Now that I have upgraded to CM12S
MTP still work. I can browse OPO /sdcard from windows 7
adb device does not work.
adb devices report nothing. No error, just nothing. As if the phone is not plugged into the computer [see attached screenshot].
But I already installed usb driver, both google's latest and koush's universal adb driver, and tried ADB Interface and ADB Composite Interface
Currently, phone is setup as follow
Setting -> Storage -> USB Computer Connection : MTP
Setting -> Developer Option -> Android Debugging : on
With Android Debugging on, adb device won't show my phone serial when USB Computer Connection is MTP or PTP
When USB Computer Connection is set to charge only, Android Debugging is disabled
With Android Debugging off, I can browse the whole /sdcard when USB Computer Connection is set to MTP
With Android Debugging off, I can browse only DCIM and Pictures from /sdcard when USB Computer Connection is set to PTP
Back in CM11S
When USB Computer Connection is set to MTP, and Android Debugging off, I can browse the whole /sdcard from PC
When USB Computer Connection has NOTHING selected (no MTP, no PTP), and Android Debugging is on, I can use adb.exe on command line: devices, shell, push, pull, etc all work just fine
On CM12S, one of these options MUST be selected in USB Computer Connection: MTP, PTP, Charge Only. This is changed from CM11S
Does anyone have any success with adb.exe on command line on Windows 7 and CM12S (stock kernel)?
If yes, what is your phone setup for adb.exe to work, and which usb driver you installed on your winodws 7?
Thanks!
EDIT: fastboot work just fine

When you're on CM12S you can't have MTP enabled if you want to use adb. Disable MTP temporarily and adb should work.
Transmitted via Bacon

timmaaa said:
When you're on CM12S you can't have MTP enabled if you want to use adb. Disable MTP temporarily and adb should work.
Transmitted via Bacon
Click to expand...
Click to collapse
timmaaa, this is what i could figure out
my only problem is: how do I disable MTP on CM12S?
On CM11S, I can
On CM12S, I must choose one of the options: MTP, PTP, Charge Only
If I am on MTP, and I press it again, the screen just grey out
and then I push back button to go back to main storage screen
and now I choose USB Computer Connection again, and MTP is still selected/enabled
Have you tried to do adb devices on windows on CM12S?
If you can, did you ever enable MTP or PTP?
Thanks

animefans said:
timmaaa, this is what i could figure out
my only problem is: how do I disable MTP on CM12S?
On CM11S, I can
On CM12S, I must choose one of the options: MTP, PTP, Charge Only
If I am on MTP, and I press it again, the screen just grey out
and then I push back button to go back to main storage screen
and now I choose USB Computer Connection again, and MTP is still selected/enabled
Have you tried to do adb devices on windows on CM12S?
If you can, did you ever enable MTP or PTP?
Thanks
Click to expand...
Click to collapse
Instead of pressing MTP again, select PTP.
Transmitted via Bacon

timmaaa said:
Instead of pressing MTP again, select PTP.
Transmitted via Bacon
Click to expand...
Click to collapse
I will try to reconfirm, but I believe I tried that already
regardless of MTP or PTP, adb devices does not find my phone
EDIT: yup, regardless of MTP or PTP, when adb debug is on in developer tools, adb device does not show serial number, so can't connect to phone via adb shell

Same exact problem here, adb worked fine until I turned on MTP now I can't turn it back off and thus adb not working.
No matter what I select or disable I always end up with MTP back on and no ADB working. Someone else who just got their OPO yesterday having same issue and what caused me to mess with MTP setting breaking my ability to ADB :/
Also another new behavior to me is that I cannot access "USB Computer Connection" screen unless I am plugged into PC. When not connected to PC it just rescans internal storage and go's nowhere.
Quick dirty screencast showing how MTP can't be turned off (sorry rushed and kid in background)
https://drive.google.com/file/d/0Bwwwt8cZbp9rYXRGa0Y1dFBfY1k/view?usp=sharing

Good to hear, in a way...
Good is that it's not just me
Bad is that this problem exist
BTW, created this problem in jira
https://jira.cyanogenmod.org/browse/BACON-3358
Hopefully this is a bug in the setting app where USB Computer Connection option is not required. Right now options are required
PS: and yes, I notice the same thing where USB Computer Connection is not even available until you plugged it into PC
PPS: I wonder what is the behavior of USB Computer Connection under OxygenOS and Stock Android (ie Nexus 5/6/etc). Having this data point can narrow down if issue is cyanogenmod OS specific issue, or it's a general Lollipop AOSP issue

is this can be problem why I couldn't install custom recovery?? I try install TWRP, device have unlocked bootloader

if running adb devices on your PC can not see the phone (ie phone serial), then yes you can't install TWRP this way
However, I believe there are other ways to install custom recovery onto your phone without PC
Try TWRP Manager on play store
I used this to update my TWRP recently in order to update to CM12S without going through OTA

Yeah I have the same issue as well and now i don't have Twerp or root . and i can confirm i never had the issue on my nexus 4 with stock LP and Dirty unicorns so it looks like a CM bug to me my phone feels incomplete without root

Solodude said:
Yeah I have the same issue as well and now i don't have Twerp or root . and i can confirm i never had the issue on my nexus 4 with stock LP and Dirty unicorns so it looks like a CM bug to me my phone feels incomplete without root
Click to expand...
Click to collapse
Thank you for the data Solodude!

Quick update on my current situation on this issue
http://forum.xda-developers.com/showpost.php?p=61975450&postcount=4

Android file transfer using a USB cable

Hi,
For some reason I can no longer transfer files from my Android device to my Linux PC using Android File Transfer.
I can list the device:
sudo adb devices -l
List of devices attached
????????? device usb:1-4 product:OnePlus5T model:ONEPLUS_A5010 device:OnePlus5T transport_id:2
Click to expand...
Click to collapse
but Andorid File Transfer (version 4.2) wouldn't start with this phone. When I attach an older phone (Nexus 4) all is fine and I can transfer files without problem.
USB Debugging is enabled on the device.
On USB Preferences File Transfer is selected. Other options are USB tethering, MIDI, PTP, No data transfer.
Any help will be appreciated.
Update: problem solved - had to use root privilidges

Try another cable. Cliché but it's often the culprit. When you get the USB mode popup just cancel it and it'll decide on its own. Disable USB debugging as it doesn't need to be on. Try other USB ports, or the last one it was known working on. Failing that see if there's a proprietary software. Microsoft Your Phone Companion might help..