Database Users

Weird USB issue

I've been tethering my phone with PDAnet and just recently it has started to act up. The only way my computer will recognize and sync with my phone is if I put a little downward pressure on the usb cable (phone side). Then, if it gets jostled to much it'll disconnect and say "USB device not recognized" when I try to plug it in again. It will start working if I put my computer into stand-by or shutdown. But only once. What is going on?

hadmanysons said:
I've been tethering my phone with PDAnet and just recently it has started to act up. The only way my computer will recognize and sync with my phone is if I put a little downward pressure on the usb cable (phone side). Then, if it gets jostled to much it'll disconnect and say "USB device not recognized" when I try to plug it in again. It will start working if I put my computer into stand-by or shutdown. But only once. What is going on?
Click to expand...
Click to collapse
Your USB port is flaking out. I have had it happen to 2 titans. They start as you describe and then get worse and worse until the port stops working completely. Then you take it back and get the insurance replacement (hint hint...if you do not have insurance on your handset this would be a good time to get it). When I complained to the guy at the alltel store the second time he said that it was common enough that he might even say inevitable.
Personally I think it is a poor design because the mini usb port on the titan (and the apache) are not really supported very well by the plastic housing. They fixed this with the touch pro (have not seen a diamond yet) so I am guessing it was a pretty widespread problem.
Not the answer you want I am sure, but the above has been my experience. If you need to drag it out (i.e make it last a little longer so the insurance you just added is not immediately and suspiciously followed by a new claim) you can always sync/tether using bluetooth instead. It is a little slower (1 mb) but not too terrible.
Why are you using PDA.net? Windows internet sharing works very well and is built in (free).

I use PDAnet because my provider would frown upon traditional method of Internet Connection Sharing. However, I appreciate you sharing your experience about the Titan with me. I love the phone, but maybe it is time to put her out to pasture.

Windows 7 will not detect device

When I plug my wife's phone in, most of the time it does not even recognize that anything is plugged in at all, but the phone charges. Sometimes in device manager the phone comes up with a yellow exclamation point and the error
Windows has stopped this device because it has reported problems. (Code 43)
I installed the Android SDK and USB driver.
I installed the Samsung Driver from the site.
I thought possibly it was a software issue, so I was going to try to set the phone to factory settings. When I go into recovery, there is an Android logo with a red exclamation point, then eventually it boots back into Android with no change.
I manually added the driver into android_winusb.inf as I saw on another post here, but no matter what it is not picking it up.
I want to just be able to connect so I can root the phone and put a ROM on it. The phone is pretty hosed and slow. Any suggestions?

I had this at one point. It was the device, I had to get a replacement.
Sent from my SCH-I815 using Tapatalk 2

esoh said:
I had this at one point. It was the device, I had to get a replacement.
Sent from my SCH-I815 using Tapatalk 2
Click to expand...
Click to collapse
Well I do have insurance on it, and I agree that is the easy way, but I really don't think the hardware is broken.
I mean it charges, so the USB port works. I think if I was able to reload Android from scratch onto it, it would work. However, every solution I see requires rooting and you can't root without USB. It is a frustrating catch 22. Any other possible solutions? If not, I guess we are screwed.
The most frustrating part is factory reset not working.

I am currently having similar problems like you, I have one USB port from memory card reader and on that port phone isn't even charging but a flash drive works without problems. On other ports (back of case and front) there is charging but computer can't recognize the device. Try uninstalling all phone related drivers or cleaning them with some sort of driver cleaner. Then reinstall driver, or let Windows update it automatically. Mine worked for a while, and in device manager it was recognized as Acer ADB.
EDIT: Hi, just to report reason of my problems, my USB cables started failing for no apparent reason, my original Samsung USB cable and one other no name have both failed. I'm currently using my old LG USB cable, wrapped up in insulating tape, but everything is working good. So try some other micro USB cable, it maybe the source of your problems.

[Q] Of TF101 and Possums

I have a TF101 that's seemingly dead after being dropped. Currently, it does not power on. When plugged in with the ac charger, it shows no sign of charging, i.e., no light of any kind - amber, green or otherwise. I assume the mainboard has gone south.
When I connect it to my laptop, however, Windows 7 gives a chime and recognizes it as an MTP device, and even lists it as a TF101 in device manager. Linux also acknowledges that much. I can pretty much browse and access the content of the internal SD card like an external HD. Holding the power button long enough will unmount the device in either OS, which suggests that the device has turned itself off, and thus still responding to physical commands, or functioning on some level.
So it appears dead but not really. Being totally unfamiliar with this model, I'm not sure what possibilities the current state of affairs might indicate insofar as the device's vitality. Any input as to what this means is greatly appreciated.
If is it determined that the mainboard is done for, can anyone point me to a source for a replacement? If this kind of info solicitation is proscribed by regulation, my apology. Thank you.

My guess is, if the board was dead, you wouldn't be able to mount the device at all. It would suggest that it's actually alive and well, but the graphic/monitor part is dead, so you have no display at all. Mine also shows no signs of life (assuming I don't check the display) while it's charging and not on the dock. Only the dock has charging status lights as far as I can tell.
Sadly I can't help you further than that. I know they sell replacement parts on ebay and such, but I never even opened mine up, so I have no idea how easy it would be to replace any part. I know there's repair videos on youtube for the tf101, it might give you a clue if you open it up and run some tests.
Also check this out.

Lethe6 said:
My guess is, if the board was dead, you wouldn't be able to mount the device at all. It would suggest that it's actually alive and well, but the graphic/monitor part is dead, so you have no display at all. Mine also shows no signs of life (assuming I don't check the display) while it's charging and not on the dock. Only the dock has charging status lights as far as I can tell.
Sadly I can't help you further than that. I know they sell replacement parts on ebay and such, but I never even opened mine up, so I have no idea how easy it would be to replace any part. I know there's repair videos on youtube for the tf101, it might give you a clue if you open it up and run some tests.
Also check this out.
Click to expand...
Click to collapse
On second thought, I'm not too keen on replacing the MB just yet. Cracking the thing open is no big deal. I am dexterous enough. However, I am more intrigued by what is possibly going on.
If you guessed right, and transferring PC knowledge to this, the board would have a video chip integrated, with the other part consisting of an inverter and the LCD. If the integrated video circuit is dead, then connecting the device via HDMI to a TV would show nothing. If the device shows up, for instance, it's just the display part from the inverter on and so forth.
But I'm hesitant to go down that route. If it's the video part, then I should be able to do everything else like putting it in APX Mode, or flashing as with a normal device. Unfortunately, my computer never registered such activities; the tablet does not respond beyond the symptoms I described above.
As a matter of fact, I'd entertain any mad proposal on what should be tried on the thing at this point, just for the fun of it. I stand to lose little. So you can use your imagination and shoot some crazy ideas my way, and we'll see what.

So you tried with HDMI and it didn't work? You're right about APX though unless you're missing the drivers.. so maybe there really is some damage to the board. Sadly I don't have any crazy/mad suggestions at this point

My normal approach to possums (and the only legal thing I can do with them once captured) is to kill them or get someone else to kill them for me. :good:
As for your TF101, I seem to remember reading on another forum that when these devices are dropped and show the symptoms you describe, it can be caused by a ribbon cable that connects the display to the motherboard being jolted loose. It might be worth opening it up and check both ends of the appropriate cable for secure fit.

Mike_NZ said:
My normal approach to possums (and the only legal thing I can do with them once captured) is to kill them or get someone else to kill them for me. :good:
As for your TF101, I seem to remember reading on another forum that when these devices are dropped and show the symptoms you describe, it can be caused by a ribbon cable that connects the display to the motherboard being jolted loose. It might be worth opening it up and check both ends of the appropriate cable for secure fit.
Click to expand...
Click to collapse
Hey I totally agree that killing it may be the only option right now. And I don't mind that, just that I'd prefer the scalpel to the cleaver, and doing it in such a way that I would learn something about it that may be of benefit to me and incidentally, to others. I did open the thing, and you're again right, people have run into this problem of the LCD cable being jarred loose on impact from Asia to the Western Hemisphere to Eastern Europe. But it's not that, as I did unseat and reseat the cable on both ends, for naught.
As to the APX drivers, I did try both Easy Flasher and PERI 0.4. They act as if they finish the job. However, the tablet remains consistently inert. Lethe6, am I missing something here? How do you tell if the APX drivers are missing? Normally Windows would show the USB device as in APX mode right? Mine did not do that. When I tried to update the driver in Device Manager, Windows refused to do it claiming it was not necessary. Is there a way to force-install the drivers just to see?
Oh well, I'd just let the issue hang at this point and see what else comes this way.

Yeah if you connect your device in APX mode it should pop up in the device manager, just right-click uninstall then re-install the drivers. I don't remember what's the exact device name but iirc it's something generic. Sorry I can't check I'm on a Mac at work and my TF101 is at home.
What about HDMI? Did you ever get a signal through there? Tried having it connected when assuming to do a full boot?

Lethe6 said:
Yeah if you connect your device in APX mode it should pop up in the device manager, just right-click uninstall then re-install the drivers. I don't remember what's the exact device name but iirc it's something generic. Sorry I can't check I'm on a Mac at work and my TF101 is at home.
What about HDMI? Did you ever get a signal through there? Tried having it connected when assuming to do a full boot?
Click to expand...
Click to collapse
I never had the chance to try the HDMI output. Still waiting for the adapter to arrive. Ebay can be a pain during holiday season. But I'd sure to report the result. When I plugged the thing in, Win recognized it as an MTP device and proceeded to install drivers automatically. After which it showed in Device Manager as TF-101. So apparently the drivers are correct, though they dated back to 2006!!?? However, with other devices like the Acer A500, the USB device symbol normally would appear at the right bottom bar with the designation "APX device." With this thing, nothing - not even the icon. What's your thought on this?

I don't have any other devices that I can boot into APX (HTC won't tell anyone and my other tablet is a craplet, have to ADB on the live FS, which is awesome lol) so I can't compare here, but have you tried these drivers for APX? It's been a while but I seem to remember needing special drivers for APX. The device had a weird name.. like a bunch of numbers and letters... haven't used it since easyflasher though.
When I plug it in APX the device is called "NVIDIA USB Boot-recovery driver for mobile devices" and it's dated 1/31/2011.
When I plug it in Rogue Recovery the device is called "Asus Android MTP Device" dated 7/17/2012.
When I plug it in booted to 4.0.3 the device is called "Transformer TF101" dated 7/17/2012.
So I'm guessing yours never enters APX or has the wrong drivers? Maybe try installing the ASUS Sync software? Not sure but it may bring newer drivers...
I assume you're doing all this undocked as well?

[Q] Formated Nexus 7 2012, now what?

Hello all!
I'm just guna say, this might get long winded so, TLDR, Nexus 7 has no OS, I can get into the boot loader, the only thing I can actually do is get into TWRP v2.8.01, computer doesn't recognize it, can't get it to even see a flash drive that I've formatted to Fat32, now what?
For those who want some background. I got my N7 refurbished from ebay, if that matters at all. First thing I did was update it to Kitkat and root it. Installed some apps and was happy with it for a few months. About a month or so ago it stopped connecting to the Google Play Store. I wasn't bothered by it too much. But as time goes on, I find new apps and would like to use them. But obviously can not.
So, just to be safe, I wrote down all the apps I still had on it just in case they didn't want to load back up. Did a factory reset, still couldn't connect. Looked online and cleared caches and stopped services. Still didn't work. When I went onto the GPS, heh, on my computer it said that I had no devices so that was a clue of some sort. I could still go onto Youtube and log in and use it just fine. Just nothing in the store. So I decided to try something else.
What that was was to clear all my data with TWRP. Went to put in my email and password, couldn't connect, tried another wifi connection, still no go. I was able to use it, but the Play Store still didn't want to play nice. So in a bit of, "rage" we'll call it. I formatted it and now I'm where I am now. With a tablet that won't boot, just sit at the Google logo for up to 5 mins, as long as I've let it sit there for anyway. I have downloaded the Nexus Root Kit and tried to use that, but my computer won't even see my N7 now. In the bootloader or TWRP. So I can't even get anything onto it now.
So, what now? Do I have a bricked tablet that won't do anything or is there something an Android Guru out there can help me with? I'd like to keep it. I mainly used it to read and for various videos.
I have posted on forums.androidcentral but after a week and almost 300 views, no one has made any comments. I'm sorry for my ignorance if I'm missing something.
Thanks! I shall be hoping for good news.

So, does ADB recognize your tablet or not when you type "fastboot devices"?

I take it you mean shift+right clicking in the platform tools folder, open command window here, and typing that into the command prompt? If so, then no, it doesn't show up.

Waslow said:
I take it you mean shift+right clicking in the platform tools folder, open command window here, and typing that into the command prompt? If so, then no, it doesn't show up.
Click to expand...
Click to collapse
Can you go into the bootloader? Did you install the right drivers?

I can get into the boot loader just fine. Recovery sends me to TWRP 2.8.01. I've got the drivers from the Android SDK Manager, Rev. 11 apparently. Would that be any different from the standard drivers that get installed when you hook up the N7? Well, when it works?

Waslow said:
I can get into the boot loader just fine. Recovery sends me to TWRP 2.8.01. I've got the drivers from the Android SDK Manager, Rev. 11 apparently. Would that be any different from the standard drivers that get installed when you hook up the N7? Well, when it works?
Click to expand...
Click to collapse
That is correct. Use this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
And if doesn't work check in device manager.
If it works flash the latest factory image and then you will be good to go

I've already had that installed and set up and nothing pops up in the device manager. I've also tried all the usb ports on my computer to no avail.

Waslow said:
I've already had that installed and set up and nothing pops up in the device manager. I've also tried all the usb ports on my computer to no avail.
Click to expand...
Click to collapse
Then try the driver manual in nexus root toolkit

I can follow the instructions, but that doesn't resolve the fact that my computer can't see the Nexus .

go into device manager and delete every single entry that suggests anything to do with a phone, tablet, google device, nexus device, ETC. if you dont do that first, this will probably not work.
once you delete every single entry in there, go to the top command bar and somewhere in those menus is an option to show disconnected devices. delete everything again as above.
now, does your tablet still charge on the AC plugged into the wall? does it still charge when plugged into the computer usb? drivers are NOT required for usb to supply power. if so, the usb connector is probably OK. if not, your usb connector may be toast.
next, connect to the computer. does windows show any device connected? if not, try a different usb cable. report your findings back.

Sorry for the late reply.
There is nothing in the device manager related to my Nexus, which is odd, it had entries for flash drives, a camera, and my phone. All of which were in the disconnected devices. I got rid of just for the sake of it. Nexus charges just fine, either from the wall or any of my usb ports. If there is no way to make ANY computer see my Nexus, is it safe to say it's bricked?
I do have a cousin who's fluent in Linux if that means anything. I know that Android is a flavor of it. Might work better if both devices speak the same language. Grasping for straws I know.
Again, thanks for the help fwayfarer, GtrCraft, and Fobos531!

If I am reading right, you did NOT try a new USB CABLE yet, did you?
Try a known good USB cable, what I mean by that is try a cable you KNOW works for data transfer on another device and report back.
Connecting it to a Linux machine isn't going to make any difference in my opinion.

I have 2 cables and they transfer things just fine with my phone and my Kindle. I just downloaded everything off of both things, and transferred them back. No issue with the cables. I just popped open my Nexus and it looks like the usb connector and ribbon are fine. I did wiggle them a little but to no avail.

Pull the battery cable, smash the power button for a few minutes, reconnect and try again. It won't recognize a USB thumb drive in bootloader or recovery to my knowledge, BTW. I noticed you mentioned it not seeing one.

I unplugged the battery, hit the power switch for a while, plugged the battery back in, plugged the usb back in, nothing. Still nothing. I had read before that you can put the version of android you wanted on a flash drive. With an otg cable you could use that to update/install what you wanted.

You're probably right, I haven't tried using one in recovery for a long time. You didn't change the battery or anything recently did you?

Nope, haven't replaced anything in the Nexus. The only thing that I could think of that could be wrong is the usb connector. But for it to "fail" at the same time I formatted everything, too much of a coincidence.

Over a week bump

I ran into a similar problem about a year ago. Unless your tablet is connected to the computer you will not see it show up it the windows device manager. You should be able to connect your N7 to a work computer & it should go out for the drivers. If not, then you are Sol. You might have a blown main board.

The only thing my N7 does when I plug it in, is that it charges. That's the only thing I can get it to do. Well, this sucks. If I really have a bricked, or worse, tablet, it's still good for its screen and other bits.

Difficulties w/ BLU C5L

I realize the BLU C5L is a very inexpensive (meaning cheap) phone and I'm not expecting some 'miracle cure to make it the latest, greatest phone ever". I'm having a number of issues w/ this phone and feel that re-flashing may/should be the answer(?) Right now ,#1. I can't even get WIN 10 to recognize the phone so that I could flash it. #2. read that phone needed to be rooted before flashing and I've tried 3 different programs and all get to 78 -83% and quit saying phone can't be rooted.(???) I've made sure I have USB debugging, 3rd party apps checked, and MTP checked. Oh, that's another thing, MTP will NOT stay on...upon sleep, shutdown or comp to phone disconnect, it always reverts to PTP. C'mon, is Android 8.1 GO that difficult? Sure would appreciate some "know-how" concerning this phone. THANX
Addendum: Just tried KingRoot (again) and it and said " too many phones connected select only one device" Yea, well...had only one???? got that solved and next: "KingRoot says failed to obtain root permission" C'mon...it can't be that difficult on such a cheap phone??? ANYONE....what the hell is going on? Hope to hear from someone who knows about this phone and what I need to do to get it rooted/re-flashed. THANX
RICK