yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Q&A, Help & Troubleshooting] haxin:
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.
[Eee Pad Transformer Q&A, Help & Troubleshooting] qandrav:
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?
[Eee Pad Transformer Q&A, Help & Troubleshooting] haxin:
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
[Eee Pad Transformer Q&A, Help & Troubleshooting] qandrav:
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!!!
[Eee Pad Transformer Q&A, Help & Troubleshooting] joevirus563:
I understand but how do you root using adb tcp???

Envoyé depuis mon Transformer TF101 avec Tapatalk
[Eee Pad Transformer Q&A, Help & Troubleshooting] qandrav:
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...
[Eee Pad Transformer Q&A, Help & Troubleshooting] haxin:
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.
[Eee Pad Transformer Q&A, Help & Troubleshooting] pm124493:
The Real Question when USB does not connect.

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.
[Eee Pad Transformer Q&A, Help & Troubleshooting] deff42:
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)
[Eee Pad Transformer Q&A, Help & Troubleshooting] jusser:
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...
[Eee Pad Transformer Q&A, Help & Troubleshooting] haxin:
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.
[Eee Pad Transformer Q&A, Help & Troubleshooting] 1234556789:
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
[Eee Pad Transformer Q&A, Help & Troubleshooting] haxin:
when you plug in the asus, check device manager, uninstall any asus related adb drivers if any. then reboot.

then extract he zip ive included, go to the adb-drivers folder, right click android_winusb.inf and click "install" this should install your drivers properly.
[Eee Pad Transformer Q&A, Help & Troubleshooting] _naj:
To add my observation: Using the original cable my tf101 charges via the plug, but wasn't recognized on two different windows machines. Also, on the transformer no USB notification was shown. After buying a new (probably china) cable, it was seen directly as a MTP device, including the USB notification on the tf101. I guess that some of the connections of the original cable have been damaged over time, so that charging still works, but USB not.

Gesendet von meinem Transformer mit Tapatalk 2
[Eee Pad Transformer Q&A, Help & Troubleshooting] 1234556789:
thanks for the answer.

I find no asus driver in the device manager, so i try to install the winusb.inf- my folder is named:C:\AndoidSDK\extras\google\usb_driver

but then there is the message: This installationmethod will not supportet from this inf file.:(

Kind regards gandalf
[Eee Pad Transformer Q&A, Help & Troubleshooting] hearts king101:
Thanks

but how can I do that without root ??? :confused:

It did not work for me ! :confused:
[Eee Pad Transformer Q&A, Help & Troubleshooting] CodeKid:
same problem with me...
[Eee Pad Transformer Q&A, Help & Troubleshooting] pm124493:
Permission Denied on step one

Tried this and got - Permission denied

I am really interested in this process so if you can work with me so I can do a recovery blog and upgrade to jb, I would be appreciative.

NOTE: If I try to boot to recovery now, I fails. I get a dead Android robot with !.
[Eee Pad Transformer Q&A, Help & Troubleshooting] cobykyros0301:
The android robot with the ! in it is the stock recovery.
[Eee Pad Transformer Q&A, Help & Troubleshooting] cinho:
ICS 9.2.1.27 no connection usb keyboard and dock

Hello, I'm new here and looking for some help for my problem. I have a TF101-B60 that a week atraz this with Honeycomb 3.1 + recovery, did the update to ICS 9.2.1.27. Since then I had no connection usb keyboard and dock, this problem can not do root to make a recovery or a downgrade. Ja did all test cables and different PCs and nothing. The problem is not because the electronic usb foncionava in Honeycomb but she stopped after the update.

Asus does not answer me. Can any of you help me?

Thanks and sorry if the translation was not good.Desfazer edições
[Eee Pad Transformer Q&A, Help & Troubleshooting] ethoms:
No adb with my TF101

I can't use adb either. I think I used it once with my LG Optimus One (phone). It just can't find device.

It does work with nvflash and wheelie though! But that is when in PXE mode.

---------- Post added at 07:17 AM ---------- Previous post was at 07:12 AM ----------

If anyone needs to root their TF101 after upgrading to ICS, wheelie is the way to go.

---------- Post added at 07:25 AM ---------- Previous post was at 07:17 AM ----------

Wheelie instructions can be found here: androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/

---------- Post added at 07:31 AM ---------- Previous post was at 07:25 AM ----------

I downloaded TWRP recovery (blob) and then used blobunpack command to get the *recovery*.SOS file, then use wheelie / nvflash to flash the recovery ROM to the SOS partition.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilixp:
same problem

I don't think my TF has ADB enabled, and i have a non working power button. No access to internal or external storage, and pc doesn't want to detect my TF. Is there a way around this?

Asus eee pad transformer TF101; CaynogenMode 10; I click reflash_sbkv1 on wheelie folder in APX mode. Going lines in cmd and TF restart, apear EEE logo and stop. I click Power button and nothing. Black screen, i cant induce APX mode, Buttons not working, APX mode Off, controled on 2 computers on windows 8, windows 7, Ubuntu. No responding.

Cable work

Buttons not broken
[Eee Pad Transformer Q&A, Help & Troubleshooting] joevirus563:
USB cable.

Still not working wainting for my usb cable to come.
[Eee Pad Transformer Q&A, Help & Troubleshooting] jalfonso119:
I have this same issue... What was ur last steps before this happening? I was on cm 10 nightly amd went to flash eos 4 and now I can't get computer to read it either... I tried 3 cables
[Eee Pad Transformer Q&A, Help & Troubleshooting] hearts king101:
Please Please Please Help Me .......

I have TF101G running stock ICS , no root , no recovery .

The issue is usb was working, then dont know what happened but UNKNOWN DEVICE message appeared, the now when i connect my tf to my PC, the screen turns on but nothing detected by the pc .:confused::eek::confused::eek::confused::eek:

Please Help me solve my problem.

Regards,
[Eee Pad Transformer Q&A, Help & Troubleshooting] josmcg:
I had same issue

I had same issue and I fixed it by simply buying a new cable. I ran into a thread saying some asus cable just don't work sometimes, post the link if I find it!
[Eee Pad Transformer Q&A, Help & Troubleshooting] jalfonso119:
I tried 3 cables no go still
[Eee Pad Transformer Q&A, Help & Troubleshooting] benmatlock:
hmmm

I just wanted to let you all know the following:

I use Debian Squeeze, and when I plug my eeepad (SL101) into my box, it isn't 'detected' either (in terms of nothing appears telling me it's been connected).

However, I am able to 'sudo adb shell' just fine... AND the dev notification icon shows on my eeePad (look for it, if it's there, you got a connection no matter what linux says/doesn't say, unless you have specific errors or dmesg doesn't show your device at all)... Not sure if these issues are just with no gui notification appearing for these users, or if they're not running adb as root (hence the sudo) which does cause problems in itself...

Just my $0.02
[Eee Pad Transformer Q&A, Help & Troubleshooting] waywardfrantz:
Ok so here's my experience using the suggestions in this thread.

1. Run stuff using terminal emulator on SD card. Can't run stuff from there, requires root.

2. Install using ADB over Wifi. Apps require root.

3. Use ./adb connect . My research into adb suggests this is a command utilized with adb over wifi, the only thing i found similar is ./adb devices which lists all connected devices, the "daemon" that starts up initially will automatically check all usb ports. This can be restarted with ./adb usb , but this hasn't helped me. One other interesting thing i found but don't understand is this

networking:

adb ppp <tty> [parameters] - Run PPP over USB.

Note: you should not automatically start a PPP connection.

<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1

[parameters] - Eg. defaultroute debug dump local notty usepeerdns

Looks cool, might be handy in crafting a solution.

4. A root kit I haven't seen before, but it has 2011 windows drivers and a bizarre one click root. No luck.

This is a combination of windows and linux (ubuntu) tactics. None of them have worked. I'm getting a new cable which I'll try, even though it appears that only one of the ten people in this thread had any luck with that either. Still, it's only 4$ and it'd be nice to have a spare anyway. Not getting my hopes up on it helping root.

So how do we fix this? It is clearly a widespread problem. Especially now that asus announced that they won't give us JB, lots of people are going to be looking to root and running into this problem. We really need something that can be run from the device itself, but who knows, maybe someone could come up with a patch to fix the connectivity issue as it certainly appears to be a software issue.

Direction for a Possible Solution:

Ok so I went looking around for "root tf101 from sdcard" and found this http://www.overclock.net/a/rooting-transformer-tf101-tested-on-9-2-1-21

I noticed that the shell commands looked familiar, and realized it was the same thing suggested in this thread using a terminal emulator! But for some reason if you open the shell on your device using adb on your computer, it will let you do it (at least according to this thread). So how can we trick the tablet into thinking that the terminal emulator was opened by adb?
[Eee Pad Transformer Q&A, Help & Troubleshooting] jalfonso119:
I curious if there would be a fix or answer why it's happening.... I talked to walmart which I have a protection plan and the guy had no idea what's going on and I'm sending it back for repair.... However I was able to connect to adb using the tcp connection but that was all
[Eee Pad Transformer Q&A, Help & Troubleshooting] trevh:
boot screens without USB, no ADB device found.

I have the same problem ... no APX mode no matter what I try (I have tried FOUR usb cables from different suppliers without success!). There's nothing wrong with the connector inside the tablet because it reads and writes data, plays movies etc from USB drives and SD cards when it's plugged in to the keyboard dock (through that same connector).

What I DO have is only a VERY minimal attempt to boot into recovery, just two lines of text on the screen from the bootloader after starting with VOL DOWN + Power buttons:-

Android ww_epad_user bootloader < e> released by "WW_epad-9.1.2.27-20120615".

checking for android ota recovery

Checking for RCK.. press key <VOL-UP> in 5 sec to enter RCK

If I press <VOL-UP>, I get a new line of text:-

booting recovery kernel image

then, after maybe one scond of animated polygons in the android chest cavity, :) it changes to the chubby android logo with an exclamation mark on it and stays that way until I switch it off. Or if I do nothing, after the 5 seconds the screen changes to display:-

OS will cold boot in 10 seconds if no input detected

Press <VOL-DOWN> to change mode,

Press <VOL-UP> to confirm mode.

Pressing on VOL-DOWN shifts the highlight between the 2 graphics in the middle of the screen, on the left is the "WIPE DATA" (a red curved arrow coming out of a 3D box), and on the right the chubby green android logo with the word "android" on it.

When I keep pressing <VOL-DOWN>, the screen highlight shuffles back and forth until after 10 seconds it continues to boot with the added text under the menu:-

Platform Pre OS Boot configuration...

Cold-Booting Linux

So...

Is APX mode part of the bootloader, or at least opening up the connector for data transfer called up by it? Is it part of the recovery image?

In other words, are our bootloaders partially corrupted? (seems likely to me) or is it the Recovery image, or is it that the bootloader simply finds and unsigned version of recovery?

Is there one (or more!) update.zip files that have a version(s) of the OTA recovery image that the bootloader seems to be looking for, or at least enough to get APX mode working again?

I'm going to keep searching for these (maybe someone from ASUS may take pity on us and release them). Meanwhile, I'm in no hurry because my TF101 boots into ICS with no problems if I just press the power button (it was unrooting for the ICS update that "broke" my TF101, I think). If I DO manage to fix this, I'll post the results here in hopes that it helps others.
[Eee Pad Transformer Q&A, Help & Troubleshooting] frederuco:
That is normal for recovery to act like that. It is the stock recovery.

To boot to APX mode, hold VOL UP and POWER for about 10 seconds. You can do it when the tablet is off, in recovery, or fully booted. The screen will be BLACK. The only way to know it is in APX mode is that a computer will detect new hardware.

Also, AFAIK, Linux has no NVFlash so it is mostly useless.

If you want to use ADB, be sure to tick the USB Debugging in Settings - Developer Options.
[Eee Pad Transformer Q&A, Help & Troubleshooting] trevh:
Yes, thanks for that. I used to use APX mode before the ICS update to move bloatware away from the system directory etc, but now when I press <VOL UP> + PWR I get to the black screen ok but nothing "sees" it, no response to ADB devices, other than daemon started but an empty list as result.

I did not know that I was describing the normal recovery which gives me much more hope, now, that the correct update.zip file might well cure the problem of no USB developer access, whether or not the USB developer box is ticked, and no "mass storage mode" whether or not MTP is ticked.
[Eee Pad Transformer Q&A, Help & Troubleshooting] frederuco:
ADB does NOT work in APX mode. APX mode is for using NVFlash to wipe/restore your tablet (NVidia devices only).

ADB works when booted normally and when USB Debugging is ticked. ADB = Android Debug Bridge and every android device is capable of ADB interface.
[Eee Pad Transformer Q&A, Help & Troubleshooting] trevh:
Of course you are correct and helpful, frederuco, thank you! Your guide to getting root and flashing roms for the TF-101 is also very helpful (yes, I have read it) :)

I only had root on the TF101 for a short time, a long time ago, before losing both root and USB access when flashing to stock ICS, so my memory of those times is quite clearly faulty. More recently I've been rooting and romming HTC & Xperia phones for Jelly Bean (experimenting with Utter apk offline mode to help a vision impaired lady) which adds more confusion in me. Sorry. I believed that I had been using simple adb commands like "adb devices", "adb reboot recovery" with the TF101 but maybe it was my Ideos X5 that I was using at the same time.

But I am quietly confident that after trying everything that I can find on XDA, (except dangerous? flashing another rom from SD card - update.zip mode), I am not able to access "USB - control" mode either when fully booted, or "partially"? booted to APX mode. Yet when my TF-101 is docked to the Asus keyboard/battery unit it does at least fully control mass storage devices that are plugged in to the dock. (I tried a USB-Ethernet adaptor that didn't work, not really a surprise tho).

So I'll think some more about what I can do ... what works, what doesn't work at the hardware/firmware level. I'll be away from fast broadband (for downloading alternate roms) for about a week because of my job, then I can address the issue again when I get back.
[Eee Pad Transformer Q&A, Help & Troubleshooting] frederuco:
Having USB mass storage devices working is a completely different ball game from having ADB work over USB.

Have you tried using the charger cable with just the tablet (undocked)? Also, just to be sure you know you must use the charging cable and not a USB cable with a gender changer to one of the USB ports on the dock, it has to be the USB to 40 pin charging cable.
[Eee Pad Transformer Q&A, Help & Troubleshooting] sad_janus:
sorry guys...

i join to the group..

Same here,, no USB, windows no detect apx, nothing

before i dont care,, i uses all over wifi FTP, trasnfer of data,, but i install stock rom =( and,, now cant root the tablet,,, !!!

any progress here????
[Eee Pad Transformer Q&A, Help & Troubleshooting] frederuco:
Long story short - no USB, no root. I had a bad USB cable. It still charges fine, but no USB (MTP/ADB/APX). New cable fixed it for me.
[Eee Pad Transformer Q&A, Help & Troubleshooting] sad_janus:
thanks

you bought a new cable and could root??

bought an original cable or an generic ??

i read some cases with 3 different cables, and even doesnt recognize him on windows,,

because the problem was after install some roms =(
[Eee Pad Transformer Q&A, Help & Troubleshooting] frederuco:
I bought a new genuine Asus cable.

If you are on stock and you can't get a PC to recognize in MTP, ADB or APX, it is either the PC or the USB cable.