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.
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
I just had an idea. I know you can root some phones using ADB and I got to thinking. All android phones have an ADB daemon running in the background that you can connect to through usb on your pc using the ADB client application provided by google(adb.exe) and usb adb drivers provided by google.
Now that you can turn your phone into a USB host using USB OTG, wouldn't you be able to use your phone instead of a computer? With a Micro-B to Micro-B USB cable? Someone has already ported the ADB client to android(ARM-Linux ELF). So someone would just need to port over the drivers to android, and then we could connect to adb on one phone using another with a terminal emulator. Right?
What are your thought?
I have attached the adb and fastboot clients that were ported to android. (adb-fastboot for arm)
EDIT:
I found this for raspberry pi (which is arm based):http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=6130
So after reading a bit more it seems that the drivers aren't even needed. They are only needed when using ADB with windows. But, since Android doesn't use "udev" I don't know if or how android would recognize that another phone is connected.
Can someone explain me how to get ADB working on my SGS8? I've tried everything: installing drivers, Java, Android SDK, 15 sec adb driver, universal ADB driver, minimal adb. I can't figure out how to do that.
Do what? Get an ADB shell with a pc?
Just install the samsung drivers from here, enable debugging in developer options on your phone and connect via usb
jaannnis said:
Do what? Get an ADB shell with a pc?
Just install the samsung drivers from here, enable debugging in developer options on your phone and connect via usb
Click to expand...
Click to collapse
Thanks, will try that
i was having one hell of a time as well. I tried everything on my laptop to no success. So i actually gave up. Than i thought well maybe its my laptop. So i ended up trying another one i had in the house and viola it worked like a charm. It seems like certain pc are just unable to connect to the samsung s8 via adb mode. Which is totally weird because I had been using adb mode on my pixel xl with no issues what-so-ever. So try a different pc if you can, it worked for me flawlessly.
Might be the USB port.
I had a similar problem connecting my Lenovo laptop to a Kindle Fire. I used a different USB port and everything worked.
9 bin
Hello,
I recently got a Pixel 2 on stock Android 11 with the intent of flashing LineageOS + rooting. But I haven't had any luck getting ADB to recognize the phone so far. I am using Windows 10 and Ubuntu Linux 20.04 LTS.
As a prerequisite, I enabled developer options, USB debugging, and OEM unlock.
I'm pretty sure the USB port of the phone is okay because the phone still fast charges.
Here's what I've tried:
- using Minimal ADB (device does not appear when adb devices is run)
- using platform-tools ADB (same as above)
- using wireless ADB (ADB is able to pair but the phone still doesn't appear when adb devices is run)
- checking Device Manager (device does not appear)
- Installing Google USB drivers
- using OEM cables from Samsung and other Android OEMs
- using a micro USB cable with a micro-to-C adapter
- using a USB hub
Am I missing something? What should I be doing to get my phone to be recognized by my computer?
Thank you in advance.
Hi, sounds like you've tried all the usual trouble shooting bits with cables, ports etc. Only other things I can think of at a stretch are to try enabling file transfer when you connect to a pc and see if that makes any difference or booting into bootloader via the button combo from powered off and then running fastboot devices from your adb and fastboot to see if it is recognised in fastboot mode?