Database Users

[Q] usb debugging failed

USB debugging no longer activates on my phone. Activating it in settings/applications/development brings up the "Allow USB debugging?" permission window. However, no usb notifications appear, and the phone appears to be a dead device to any PC it is connected to.
This started when I accidently got into the download screen from the phone options popup. The display showed the yellow sign, android guy with shovel, and message warning not to turn target off. Phone was not connected to anything at the time.
Searching found a couple of threads indicating that a battery pull was safe to get out of it. Did same.
Since then, usb debugging (or usb anything) has been dead on this phone. Other methods of usb access (thru usb settings) have no effect either.
Tried the following...
(1) restore to my last backup rom.
(2) numerous reboots and battery pulls.
(3) mount/unmount sd card in cwm recovery
(4) clear caches
(5) changed pc's and cables (all worked before)
(6) reinstalled usb drivers on pc (worked before, didn't expect it to help since issue is at phone end)
As you can see, I'm running out of sticks to poke the horse with. Does anyone have any ideas?
Update: new kernel didn't help, either
Update2:
(a) Can't do a restore via odin, which won't detect the phone.
(b) Updated my adb (which I don't use much). adb devices command will not detect the phone via usb.
(c) Installed adbWireless which allowed me to push a stock nandroid backup to the phone. Restored that, usb is still dead.
(d) Restored back to my superdark rom, usb is still dead.
Head scratch: I'd blame hardware except that it seems to be between the settings and execution. If it was purely hardware, I'd expect to see the usual usb notifications. Regardless, it looks like I'll have to revert back to stock and let Verizon figure it out.
Update3:
(a) switched to the new AOSP rom. Nice, but no usb.
(b) switched back to superdark since I like my speakerphone and the AOSP seems to be on hold. Still no usb.
Resolution:
My apologies for not posting a resolution. My bad. After the first few days the post kind of fell off the radar and I stopped checking.
Short version...dirty usb port.
Details...after a week or so, I saw the usb icon flash in the notification bar for a few seconds when I plugged it in for a recharge. Hadn't seen that in a week, hope springs eternal!
A thorough cleaning of the usb port using a paper swab dampened with alcohol restored usb functionality. Not much dirt came out on the paper, but it must have been enough to probably bridge the contacts somehow.
At present the phone is fully functional. The original Verizon cable seems to be a little wonky. I have an aftermarket cable that works fine. It may be that the aftermarket cable did some physical harm to the contacts in the port, or the original cable is going bad (I had something very similar happen on my Omnia). Not sure.
I now use the original verizon cable only for charging at work and use the aftermarket cable for usb connecting at home.
Bottom line...if your usb goes dead as described in the op, carefully clean the port.
My thanks to all who responded...

Download screen shouldn't have harmed you.
You probably are well aware of this, but sometimes it's the simplest solution: Is your usb cable unplugged when you are trying to turn on USB debugging? It will not let you if you are plugged into a pc or mounted for some other reason. Make sure your file manager and any other rogue app is closed. Again, it does sound like you have tried all of this, just giving my best shot ar an answer.
Other then that... Has anyone else had this problem? I haven't seen it in this forum before.
The most general solution to any issue on these fascinates is to undo whatever you did to break it, it's just difficult sometimes to isolate what that event was.
Swyped w/ XDA App. When in doubt, mumble.

Thanks for the reply.
USB is unplugged when turning on debugging. I've also tried turning the phone on with usb plugged in.
The last thing I had done (before accidently activating the download screen) was to install SiMi Folder Widget. Needless to say, it went away with the rom restore.
Also used ATK to kill running processes before turning on usb debugging. Also verified that I still have root.
I've buggered the phone up before but have always been able to figure out a way back (with help from forum searches). This one's got me stuck.
Tonight I'll try to figure out if it can be odin'd back to stock and rebuild from there.
Again, thanks. All suggestions/advice are appreciated.

See op for steps taken to (unsuccessfully) solve this.
Can anyone advise how I can flash back to stock DI01 without using odin, since it won't detect the phone? I can push files to the phone via adbWireless but that's about it.
thanx in advance...

I dont know if you fixed it or not, but here is a stupid question. Are you using the cable that came with your phone? I have several cables that will only charge my phone and only the stock one enables data transfer. Hope this helps. Good luck
Sent from my SCH-I500 using XDA App

Have you tried a factory data reset?
Sent from my SCH-I500 using XDA App

Did this ever get resolved? I hate to see an open issue die like this.

My apologies for not posting a resolution. My bad. After the first few days the post kind of fell off the radar and I stopped checking.
Short version...dirty usb port.
Details...after a week or so, I saw the usb icon flash in the notification bar for a few seconds when I plugged it in for a recharge. Hadn't seen that in a week, hope springs eternal!
A thorough cleaning of the usb port using a paper swab dampened with alcohol restored usb functionality. Not much dirt came out on the paper, but it must have been enough to probably bridge the contacts somehow.
At present the phone is fully functional. The original Verizon cable seems to be a little wonky. I have an aftermarket cable that works fine. It may be that the aftermarket cable did some physical harm to the contacts in the port, or the original cable is going bad (I had something very similar happen on my Omnia). Not sure.
I now use the original verizon cable only for charging at work and use the aftermarket cable for usb connecting at home.
Bottom line...if your usb goes dead as described in the op, carefully clean the port.
My thanks to all who responded...

This may be my problem! I'm having the same similar effects. Although mine randomly shows the symbol but also says my usb is connected when it does. I've been trying to solve this for 2 weeks now! I hope this is the solution.
Sent from my SCH-I500 using Tapatalk

common problem
This must be a common problem because I've had the same issue. switched cables and viola, all good.

My exact problem solved:
USB debugging activated on phone but computer did not detect it at all, nothing what so ever. Not even on dial-up mode, or download-Odin (yellow triangle).
Drivers installed (Fascinated and Nexus for the hell of it).
Tried to ADB my into it both from windows 7 and MAC OS-X.
Hell I even tried a different USB cord.
I would get the USB debug icon in the status bar only when on windows7 machine.
I cleaned the phones USB port with the alcohol damped paper towel/tooth pick and the **** worked, first time.
Man I gotta thanks God for this site. I been ****ing with for 2 days.
Then this lil SOB acted as if nothing ever happen. I wanted to beat the hell out the lil ****er. But we are back friends now.
Thanks dude. This **** needs publicized more. I went through a few links before I found this.
I would and tell people to use something non-metallic and removed the battery beforehand. I did just to be safe.

PC no longer sees NC.

Running CM7 N100 from SD card & my PC used to see the NC & I would get the notification on the NC. When enabled, the SD card & eMMC would be mounted. Now I get nothing. No response from PC or NC. The NC just shows charging. The only thing that I know for sure that has changed, is last night I did a Windows update. Any clue to fix this will be appreciated.
Thanks,
kev
Update: Powered off with USB cable connected to PC & heard a bunch of USB beeps off on off on then as the NC was booting the PC showed the drives the way it's supposed to & when the NC was up it showed the USB icon in notification, but when I press "USB Connected" I don't get the button to enable the connection & the sd card & eMMC are not mounted o the PC. I have read of someone else having this issue, but can't find the thread. Any help?
Update 2: Read elsewhere that someone was told to use a regular micro USB cable to fix this same problem, so I tried it & it worked. Then I tried it with the NC cable & it worked, so I don't know what just went on here. Are we getting bombarded with gamma rays from the sun or something?

i dont get anything when i plug my NC into pc now....
It just started this last night.
I have searched and can not find anything, so I am charging it and about to update or restore from backup. I just got everything the way I liked it
THIS IS DRIVING ME NUTS

Did you get any indication on the NC's status bar?

No indication what so ever. I finally wiped the NC and did a restore and that fixed it. I think it has something to do with the new nook tweaks USB host mode
Sent from my NookColor using XDA Premium App

Cannot get phone to mount as mass storage anymore

Well pretty much as the title says. I have never had a issue with it before, but as of today it will not for the life of me mount. I sometimes (after many tries) get the windows 7 pc to the mass storage device but when I click on it it just loads forever before freezing up and failing to load any files from the phone. Then after being disconnected and reconnected I cant even get it to let me mount the device.. When I click mass storage it goes to the confirm mount page, but when i try to mount it again it just clicks but nothing happens.
I have no idea what is up. I have ordered a new usb cable but im not sure thats the problem.
Has anyone else had this issue? What was the sollution you came across that fixed it for you. Any help is appreciated.

Plug it in and go to device manager. Delete it from device mgr if it shows up. Reboot.... plug it back in after reboot and see if it recognizes it. Should reinstall itself and recognize.
Let me know......
Sent from my SPH-D700 using XDA App

Had the same issue about the time I first moved to GB, turned out to be the cable but the timing of when it happened had me pretty twisted.

gregory15 said:
Plug it in and go to device manager. Delete it from device mgr if it shows up. Reboot.... plug it back in after reboot and see if it recognizes it. Should reinstall itself and recognize.
Let me know......
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I can once again see the device (drive H but when i click to view or explore it completely locks up the window. So its unable to access the device but it does however know its there. I can access my device with adb as i tried it to see if I can atleast get it to communicate.. but have no way of accessing the sdcard via mass storage :-(
*update* Well I really wanted to get some files (audiobooks) sent over.. so I gave the kies air a go... That seems to be a decent temp fix.. and over a gigabit connection to my wireless N phone the transfer speeds are probably on par if not faster than usb... atleast it seems so.

prolly the cable
happened to me before
the sdcard can be read through an sdcard reader, just not through the phone.
The usb cable would charge the phone but it wouldnt connect for NOTHING. I would tap connect, it would press but then unpress as if nothing happened. just following the motion of my finger.
Found a BB cable a couple weeks later after i lost my stock one, and my phone was picked up by odin,adb, sd card, blah blah blah
it was so funny cuz i was blaming my pc for it instead of the cable cuz it worked so well for me before until i plugged my phone in on a friends comp and it didnt pick it up, but when i used his HD2 cable, it went through without a hitch.
TL;DR
Kies air will do till your new cable comes in.

Are they any issues or quirks with the phone reading the sd card? We've had a rash of epics come in lately where the sd card port has gone bad. Just making sure it's not that (but it's a very easy fix, the port is actually removable and we get them shipped to us as a new part.)
Sent from my SPH-D700 using xda premium

I get this on froyo, can't connect, every once in a blue moon it does, when it dosnt I use dropbox, kies air works good also. But on GB it works everytime, same cable, go figure

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] 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.