Database Info

[Q] Broken USB connection, possible brick

I have a NS i9020T which was running the latest MIUI ROM until I tried to update it to MIUI ICS. I had noticed, while running pre-ICS, that my computer wouldn't mount USB storage. As a working around (rather that trying to fix the issue) I just FTPed files. When I tried to install MIUI ICS something went wrong (probably corrupt ROM image) and now my NS won't boot.
If I go through Clockwork Recovery to mount USB mass storage, nothing happens. I'm running OS X, but I've tried mounting in Ubuntu 11 and Win7 -- Windows recognizes that there is a device there but the drivers won't recognize it (I think).
Finally, I've tried flashing a new recovery using fastboot but I get "<waiting for device>" in Terminal.
My best guess is that the USB connection is shot, which would probably require me ripping the NS open and tinkering around (which I have zero experience doing).
Does anyone have any ideas for fixing what is likely a permanent brick? I can boot into Win7, OS X, or Linux to troubleshoot. Also I'm on the XDA IRC as "threepape" right now trying to solve this issue.
Thanks in advance!

I was working with threepape on IRC trying to narrow down the issue.
Basically he's had his phone rooted, tried flashing a rom and now it's stuck at the boot screen. He went to connect to his computer and it gave him an error. and wouldn't let him connect his phone to the os. This is a problem.
So he then downloaded kies to see if it would install drivers automatically, downloaded odin and then tried to see if odin would recognize the phone. It did not and his computer gave him the error "unknown USB device, error code 43"
So we reviewed what we could control: trying different cords, checking drivers, etc.
Now we are going to try booting into an osx platform, installing heimdall and seeing if "heimdall detect" prompt will detect the phone. If that doesn't work we're going to either need more help or rule it out as a hardware issue.
<threepape>
Failed to detect compatible download-mode device.
[8:55pm] <ddrt>
so you typed out heimdall, then heimdall detect and it came back with that?
[8:55pm] <ddrt>
and you are 100% it was in download mode?
[8:55pm] <threepape>
yep
[8:56pm] <threepape>
it does ay on my phonee "USB Control Init USB Control Init End"
Click to expand...
Click to collapse
edit: device is not being detected on multiple os using different programs, device will not wipe fully when doing a factory restore through CWM. I am at a loss.

[Q] TF101 Won't connect via USB

I'm quite confused with this one. Here's what's happened so far.
I was on AOKP Build 31 with CWM touch 5.8.2.1 and decided I want to go back to stock and start fresh. I found a mostly stock 9.2.1.17 from a thread in XDA titled "[ROM] TF101 Rooted Stock 9.2.1.17 + bootloader + modded recovery US and WW" (sorry, can't post links). I downloaded, checked the MD5, made a nandroid, wiped data/cache/Dalvik and installed the ROM. After doing that, I have been unable to get my device to connect to any computer via USB. I tried restoring my backup and also re-flashing a fresh copy of AOKP Build 31. I am able, however, to connect via ADB using TCP/IP. When I plug the device into my Windows 7 Pro, 64-bit I don't get any sort of notification or sound. When I plug the device into my Ubuntu 11.10, 64 bit I also don't have a connection showing up using the 'sudo lsusb' command. The strangest thing is that when I plug the device in the screen turns on, so clearly the USB cable is not the cause. I've tried two different Win. 7 computers, my Ubuntu box and a Fedora box (and multiple USB ports on each computer). Any suggestions?

Try this, Settings> Storage> hit the 3 dots sign at top right corner, hit USB computer connection,
Un check the MTP box and check it again. If that don't work try turning off USB debugging

Try this, Settings> Storage> hit the 3 dots sign at top right corner, hit USB computer connection,
Un check the MTP box and check it again. If that don't work try turning off USB debugging
Click to expand...
Click to collapse
Tried that on one of the Win. 7 boxes and the Ubuntu box, no success.

Have you tried reinstalling the drivers? I had to do that when I went from stock to custom rom.

This happens a lot. Something to do with the bootloader not getting flashed properly or something.
Get the full ICS ROM from Asus website and flash it.

horndroid said:
This happens a lot. Something to do with the bootloader not getting flashed properly or something.
Get the full ICS ROM from Asus website and flash it.
Click to expand...
Click to collapse
Just did that... lost root -.- stock and no usb >:/
Does anyone have any ide how i can root it now?

Get the full ICS ROM from Asus website and flash it.
Click to expand...
Click to collapse
I also tried doing this, without success. I'll try a few other things, thanks for the help though all!

You can root it (rather painfully and obscurely) by using an update.zip with the version of the firmware Razorclaw needs to work, and root in tablet and then flash in tablet. Downgrading to the required honeycomb might fix the usb too. I've never had to use ADB to do anything on my tf, aside from developing

Thing O Doom said:
You can root it (rather painfully and obscurely) by using an update.zip with the version of the firmware Razorclaw needs to work, and root in tablet and then flash in tablet. Downgrading to the required honeycomb might fix the usb too. I've never had to use ADB to do anything on my tf, aside from developing
Click to expand...
Click to collapse
How can i downgrade to honeycomb? without recovery?? and where can i find the ww version of it?

baseballfanz said:
Try this, Settings> Storage> hit the 3 dots sign at top right corner, hit USB computer connection,
Un check the MTP box and check it again. If that don't work try turning off USB debugging
Click to expand...
Click to collapse
Ive rooted a bajillion devioces and never thought to look there when my tf101 stopped connecting, ive rebooted my pc and it a hundred times
Thanks for the DOH! moment !!

no usb data. need to root -tf101

Long time listener. First time caller.
I have an issue. My tf101 lost the ability to transfer data about week ago. Meaning, its not detectable by computers or any usb device
The tablet was rooted but i returned to stock in an effort to fix the problem and lost root.
I have tried:
3 cables
4 PC's
1 linux box
The tablet charges fine and even trickle charges from usb ports
I narrowed down the problem to a partially corrupt bootloader. Or simply a bad flash(team rouges rec and revolution rom)
I think i may be able to fix the problem by flashing ClockWork recovery, but i need to get root access. Any ideas or am i just screwed?

So im screwed right?

Zone3 said:
Long time listener. First time caller.
I have an issue. My tf101 lost the ability to transfer data about week ago. Meaning, its not detectable by computers or any usb device
The tablet was rooted but i returned to stock in an effort to fix the problem and lost root.
I have tried:
3 cables
4 PC's
1 linux box
The tablet charges fine and even trickle charges from usb ports
I narrowed down the problem to a partially corrupt bootloader. Or simply a bad flash(team rouges rec and revolution rom)
I think i may be able to fix the problem by flashing ClockWork recovery, but i need to get root access. Any ideas or am i just screwed?
Click to expand...
Click to collapse
No, you're not "screwed" You could always just download an over-wifi file transfer app. I'm not sure what the best ones are on the Play Store, but I'd do you research if you're gonna drop a couple bucks on one. I haven't bothered since my Skyrocket is Samsung and I already get Kies Air.
I would suggest after flashing ClockWork recovery trying out some other ROMs and kernels and seeing if that fixes your problem. I would also highly suggest Team Win Recovery Project. It's been my favorite recovery so far, not to mention the touch screen interface is fantastic.

enterflux said:
No, you're not "screwed" You could always just download an over-wifi file transfer app. I'm not sure what the best ones are on the Play Store, but I'd do you research if you're gonna drop a couple bucks on one. I haven't bothered since my Skyrocket is Samsung and I already get Kies Air.
I would suggest after flashing ClockWork recovery trying out some other ROMs and kernels and seeing if that fixes your problem. I would also highly suggest Team Win Recovery Project. It's been my favorite recovery so far, not to mention the touch screen interface is fantastic.
Click to expand...
Click to collapse
Thanks for answering
Ive been using a combination of google drive and file expert for file transfer, but i cant flash any recovery or any rom or adbwireless because i dont have root anymore.

Did you try loading the official USB drivers?

Zone3 said:
Thanks for answering
Ive been using a combination of google drive and file expert for file transfer, but i cant flash any recovery or any rom or adbwireless because i dont have root anymore.
Click to expand...
Click to collapse
So you lost your recovery manager too?

enterflux said:
So you lost your recovery manager too?
Click to expand...
Click to collapse
Yep, and that appears to be my biggest hurdle in solving this issue.
Seems more than a few are having this issue as well

Zone3 said:
Yep, and that appears to be my biggest hurdle in solving this issue.
Seems more than a few are having this issue as well
Click to expand...
Click to collapse
I assume you can still get into APX mode? If so, I would try running this. It's what I initially used to root my TF101, and it doesn't require you to use your installed recovery. Basically it roots and installs CWM recovery from a script run from your computer. Let me know what happens.

enterflux said:
I assume you can still get into APX mode? If so, I would try running this. It's what I initially used to root my TF101, and it doesn't require you to use your installed recovery. Basically it roots and installs CWM recovery from a script run from your computer. Let me know what happens.
Click to expand...
Click to collapse
Yes, the tab can go into apx mode, but the computer wouldnt know if it was in apx. Pc doesn't know the tab exists when plugged in.

Zone3 said:
Yes, the tab can go into apx mode, but the computer wouldnt know if it was in apx. Pc doesn't know the tab exists when plugged in.
Click to expand...
Click to collapse
When plugged in to your computer and in APX mode, check Device Manager and see if there's any unrecognized devices.

enterflux said:
When plugged in to your computer and in APX mode, check Device Manager and see if there's any unrecognized devices.
Click to expand...
Click to collapse
Ive been through that. Its not a simple driver issue. Windows doesnt even acknowledge it as an "unrecognized usb device"
Linux does even list it with the lsusb command.
Same for mac.
There is no data being transfered. It doesnt even attempt usb handshaking...

Zone3 said:
Ive been through that. Its not a simple driver issue. Windows doesnt even acknowledge it as an "unrecognized usb device"
Linux does even list it with the lsusb command.
Same for mac.
There is no data being transfered. It doesnt even attempt usb handshaking...
Click to expand...
Click to collapse
Well, I'm assuming that this is no longer on stock firmware and/or too old to be still under warrantee. The only thing I can think of, unless someone else here can give you an answer, is that it may be a hardware problem and you'd have to send it in to ASUS to get it fixed.....

enterflux said:
Well, I'm assuming that this is no longer on stock firmware and/or too old to be still under warrantee. The only thing I can think of, unless someone else here can give you an answer, is that it may be a hardware problem and you'd have to send it in to ASUS to get it fixed.....
Click to expand...
Click to collapse
Did the OP found a solution to that? I have the exact same issue .

haha,, months after.....
But i am in the same situation...
a lost root and the USB dosnt work, exactly like the autor of this post...
any ideas?

sad_janus said:
haha,, months after.....
But i am in the same situation...
a lost root and the USB dosnt work, exactly like the autor of this post...
any ideas?
Click to expand...
Click to collapse
You need USB to root. I had the same issue and a new USB cable fixed it straight away.

frederuco said:
You need USB to root. I had the same issue and a new USB cable fixed it straight away.
Click to expand...
Click to collapse
hmmm, I'll try when I can get a new cable = (
but from what I've read some have tester with multiple cables and even so the USB dont work,,

sad_janus said:
hmmm, I'll try when I can get a new cable = (
but from what I've read some have tester with multiple cables and even so the USB dont work,,
Click to expand...
Click to collapse
If you have another PC you can try hat is the only other suggestion I have.

frederuco said:
If you have another PC you can try hat is the only other suggestion I have.
Click to expand...
Click to collapse
thanks
yeah, of curse i tried
but no luck. i try everything,
APX dosnt work, USB it is invisible for windows, in any way

USB not recognized + no Recovery

Hi All,
It has been a time that I unlocked my TF700t then followed the CM10 documentation to install 10.0 using CWM.
Recently I wanted to upgrade to 10.1 but it didn't work and ended with my tablet rebooting undefinitely.
I reverted then to install back the ASUS stock Rom from their website :
- I downloaded the file
- unzipped it (since it contains another zip)
- put it on a micro SD
- Booted into CWM
- installed the zip
I ended with a working tablet on the stock rom JB 4.1 but know I wanted to try again CM but I cannot access recovery anymore. I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign.
I thought I would need to flash another recovery (TWRP or other) using fastboot but now when I plug the tablet to my PC it keeps telling me that the device is not recognized. I tried to install the USB driver but it doesn't get detected.
Can anyone please help ? The tablet is working but I am afraid that it has lost some of its capabilities.
Thanks
Nacef

nacef_l said:
Hi All,
It has been a time that I unlocked my TF700t then followed the CM10 documentation to install 10.0 using CWM.
Recently I wanted to upgrade to 10.1 but it didn't work and ended with my tablet rebooting undefinitely.
I reverted then to install back the ASUS stock Rom from their website :
- I downloaded the file
- unzipped it (since it contains another zip)
- put it on a micro SD
- Booted into CWM
- installed the zip
I ended with a working tablet on the stock rom JB 4.1 but know I wanted to try again CM but I cannot access recovery anymore. I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign.
I thought I would need to flash another recovery (TWRP or other) using fastboot but now when I plug the tablet to my PC it keeps telling me that the device is not recognized. I tried to install the USB driver but it doesn't get detected.
Can anyone please help ? The tablet is working but I am afraid that it has lost some of its capabilities.
Thanks
Nacef
Click to expand...
Click to collapse
Go to your system setting and select storage. Click the 3 dots in the upper right corner and tick the box which is Media device (MTP).. Good luck..

LetMeKnow said:
Go to your system setting and select storage. Click the 3 dots in the upper right corner and tick the box which is Media device (MTP).. Good luck..
Click to expand...
Click to collapse
I just tried that but it did not work, windows is still displaying USB device not recognized.

nacef_l said:
I just tried that but it did not work, windows is still displaying USB device not recognized.
Click to expand...
Click to collapse
What Windows version are you running?
You may have to uninstall the drivers for your MTP device before installing new ones as well as disabling Windows to automatically install drivers for a new device, then manually point it to the Universal Naked Drivers folder.
Or downlaod Android SDK tool ad through it the Platform Tools and USB drivers.
BTW: When you flashed the stock firmware you lost your custom recovery. That's why you see the dead Droid - it's the stock recovery.
If you can't get fastboot to work you can use Motochopper to root your JB 4.1 stock firmware and then GooManager to install the latest TWRP recovery.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

I have tested it on WinXP, Win7, Ubuntu and another box with Win XP. Always same thing the device is not recognized.
When I try to update the driver and point it manually to the naked drivers it cannot detect them.
I guess that even for running Motochopper I will need to get USB working to be able to root my device.
Any help please ? I am stuck with a sluggish stock mod that buries the perfs of my device.

nacef_l said:
I have tested it on WinXP, Win7, Ubuntu and another box with Win XP. Always same thing the device is not recognized.
When I try to update the driver and point it manually to the naked drivers it cannot detect them.
I guess that even for running Motochopper I will need to get USB working to be able to root my device.
Any help please ? I am stuck with a sluggish stock mod that buries the perfs of my device.
Click to expand...
Click to collapse
You do have USB debugging enabled in the Developer settings, do you?
Sent from my DROID4 using Tapatalk 2

berndblb said:
You do have USB debugging enabled in the Developer settings, do you?
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Yes checked and double checked that

nacef_l said:
Yes checked and double checked that
Click to expand...
Click to collapse
Then it's a driver problem and it's solvable. What do you see in Device Manager under Portable Devices with your tablet connected? Did you uninstall the driver and re-install it?
Did you try to install Asus Sync (which should give you compatible drivers for the TF700)?
So many driver problems lately... there's got to be a pattern to it, but what it may be beats me :what:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

berndblb said:
Then it's a driver problem and it's solvable. What do you see in Device Manager under Portable Devices with your tablet connected? Did you uninstall the driver and re-install it?
Did you try to install Asus Sync (which should give you compatible drivers for the TF700)?
So many driver problems lately... there's got to be a pattern to it, but what it may be beats me :what:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
In the Device Manager I have nothing under Portable Devices, but under USB devices it appears an Unrecognized USB Device and a bubble notifying about an unrecognized USB device keeps popping in the task bar. Even after installing ASUS Sync it is not detected.

nacef_l said:
In the Device Manager I have nothing under Portable Devices, but under USB devices it appears an Unrecognized USB Device and a bubble notifying about an unrecognized USB device keeps popping in the task bar. Even after installing ASUS Sync it is not detected.
Click to expand...
Click to collapse
You don't connect your tablet to the PC through the dock USB port, do you?? Just had that in another thread....
If you connect the tablet directly, I'm stumped. No idea why it's not recognized...
Sent from my DROID4 using Tapatalk 2

berndblb said:
You don't connect your tablet to the PC through the dock USB port, do you?? Just had that in another thread....
If you connect the tablet directly, I'm stumped. No idea why it's not recognized...
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
I don't have a dock and I am connecting directly with the cable. I have just reflashed it to stock rom again hoping it resolves itself but nothing.
It's driving me crazy. The stock rom is really sluggish and I want to flash it to CM

Sounds like a windows driver issue to me. You need to force windows to use the right usb drivers. You normally do this by upgrading thenm in device manager. You may have a borked windows installation to fix as well..
Try the ones I have attached.

sbdags said:
Sounds like a windows driver issue to me. You need to force windows to use the right usb drivers. You normally do this by upgrading thenm in device manager. You may have a borked windows installation to fix as well..
Try the ones I have attached.
Click to expand...
Click to collapse
I have tried different windows installations with the different drivers that you provided me, still nothing. It seems to me that the device is not even sending proper ids to the system. Can it be caused by a damaged cable ?
Sent from my iPhone using Tapatalk - now Free

Had the same problem.I fixed it by uninstalling the faulty usb device. Then disconnected the usb cable. Reconnected. And the drivers installed.

nacef_l said:
I have tried different windows installations with the different drivers that you provided me, still nothing. It seems to me that the device is not even sending proper ids to the system. Can it be caused by a damaged cable ?
Click to expand...
Click to collapse
Im having the same problem and after one day of research I could not find a solution. I bought a use TF700 with a standard andriod on it, no mod, not unlocked, no root. When I connect it to the pc I get the same error, meaning just a USB Device showing up. Tried different PC's with different types of OS, no success.
Did you manage to fix the problem ? I would really appreciate some help because now I can't use that tablet in debug mode to test my android applications and that's all I bought it for. By the way, is there a adb tool that works wireless and doesn't neet root access or can I get root access without connecting my pad to my pc ?
Thanks for the help !

Well did you install adb fastboot drivers on the PCs you tried? Did you try it under Linux? Do you have the original Asus cable you connect it with?
adb over network is an option under Developer Options in Omni and Omni based roms - at least the LP roms. I don't think you can get that with an app you install. Probably needs to be baked into the kernel.

berndblb said:
Well did you install adb fastboot drivers on the PCs you tried? Did you try it under Linux? Do you have the original Asus cable you connect it with?
adb over network is an option under Developer Options in Omni and Omni based roms - at least the LP roms. I don't think you can get that with an app you install. Probably needs to be baked into the kernel.
Click to expand...
Click to collapse
First of all thanks a lot for your response, didn't think anyone would still react on that post because it's quite old. Yes I did install adb fastboot drivers, the device only shows up in the usb section saying usb device not recognized. I tried nearly every driver I found, installed the Andriod SDK, the Asus Sync Tool, the naked drivers... then removed them all (including the hidden ones) and installed just the adb fastboot -> no success. I have not tried it on linux, but on windows 7, 8 and 10. Android version is 4.2.1 and Build is 10.6.1.14.10. I now unlocked it using the apk provided by asus (version 7 , 8 did not work). Still for rooting I need pc connection, so I ordered a new cable today (cable is original Asus though).
I installed the Rom Manager and that tells me the ClockworkMod Recovery and TWRP are already installed. I also tried that recovery (power + vol) and got the same result as nacef meaning " I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign." Thing is, I don't know what the previews owner did, so it might be the reason he sold the Tablet. Can I get anywhere form that Bootloader ? Maybe boot as a Superuser and then use wireless adb to root the device ?
Thanks a lot for your help, Im feeling that I have wasted the money and the only way to get rid of that feeling is to fix the problem

Grab the Puppy Linux live CD from here: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It has adb fastboot already installed. If you don't get a connection with that one the problem would be tablet side, not Windows related.

I booted using that Puppy Linux and followed the Guide but no success. After entering "adb devices" I get the output "list of adb devices attached" and than a blank space. So I tried booting in fastboot like you described in your guide and entered "fastboot devices" but that also gives me nothing. Fastboot works though (as it's already included in that image) so I tried a bunch of other fastboot commands but that just results in "waiting for the device".
I don't know what to do now, it has something to do with the tablet itself. Im waiting for the new cable but don't think thats gonna change anything.

You are not trying to do this through the dock port, right? You are connecting the tablet directly to the PC?
The only answer I have left is either a broken cable or one of the pins in the port is bent or broken. Get a magnifying glass and check them out.

[Q] Unbricked successfully, ADB broken?

Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.

Does usb debugging is on?

Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?

If You use asus drivers it worth to try universal naked driver.

Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.

Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.

Hmm... How windows show tablet when You connect it to PC?

Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?

It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?

Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.

Try first remove all drivers and software for tablet. Then install universal naked driver.

Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.