I have yet to see this issue reported anywhere so was wondering if anyone was having the same problem.
After having the phone charging in the wall my vibrant has started piping up with a notification that usb has connected even though it's not plugged into anything. Rebooting doesn't seem to help.
Any ideas?
Sent from my SGH-T959 using XDA App
Does that when I charge it in my car. I just ignore it.
Sent from my Samsung Vibrant using the XDA app
Does that with my wall charger but I suspect it is happening bc my puppy chewed on the cord. Didn't get all the way thru though and it still charges fine
Sent from my SGH-T959 using XDA App
My phone has been doing the same thing. Says usb connected when nothing is plugged in. stovk firmware, only rooted. Just happened this morning. Apparently many other people have been having the same problem. Can't seem to find a solution yet. Reboot into recovery and wore cache sill no luck. I heard wiping data doesnt work either.
I'm having the same issue but on the Fascinate. I thought that this was do to the Voodoo lagfix so I removed that but it's still happening.
I'm rooted and have CWM loaded but no other modifications.
For me, the USB notifier keeps popping up every second or so. I can't reboot the phone as it still thinks it's connected and shows a battery symbol that isn't charging and then dims. To complete boot I have to either 1) plug in a powered usb cable or 2) pull the battery.
I've had the battery out for 15 minutes and that usually stops this from happening for a day or so. I have no idea what's causing this but I'm leaning towards this being hardware related. Possibly bad battery? I don't know. I have experienced this in my car too.
Some other thoughts, does this phone react differently to different USB cables? I know it's odd, but when I plug into my wall jack using a generic cable I don't get the notifier at all, when I plug into my car with the Samsung cable, sometimes it appears. Of course, it's more of a problem when it appears when no cable it pushed in and it cycles on and off.
Does anyone with this problem have a spare battery they could try?
That happened to me before. I rebooted and that didn't fix it, so I did a master reset and that cleared it up. It was kind of pain to redo everything, but not too bad.
Someone else posted over at Something awful the following:
Stunt Rock posted:
I had a really fun day with my Vibrant yesterday. Interested in seeing if it repeats today. I was on the phone when it just randomly shut down. I was a little surprised, since it was plugged into the car charger and shouldn't have run out of batteries. Then without me pressing any buttons, it boots itself up. Then over the course of the evening it does the following:
* Repeatedly turn itself on then shut itself down while plugged in.
* Repeatedly display the "USB Connected" dialogue while not connected
* Refuse to recognize USB actually IS connected while plugged in to the computer.
* Randomly turn itself off if not connected to USB
* Automatically turn itself on whenever plugged into the USB port.
* Refuse to turn on if the battery cover isn't attached.
Plus some other stuff I'm probably forgetting. I have no idea what started all this.
This continued in more hilarious fashion yesterday when I took it to the T-Mobile store and the rep couldn't get it to boot (it would just give the spinning wheel for a few seconds). The rep called in for a warrant replacement.
I told him it would get past that screen if plugged in. Sadly, I was going out of town and left my USB charger. So I found out if I blew into the USB charging port right as I pushed the power button it would boot.
I charged it overnight and today it continued the errors (repeatedly USB connected while unplugged, etc). T-Mobile tried to push the JI-6 update again. It bricked my phone, again. I went into Odin and restored it to stock, again.
Then I manually applied the JI6 update via ODIN. Phone has been working flawlessly since then.
Click to expand...
Click to collapse
Maybe coincidental but I just blew into my USB port and the notifier stopped flashing on and off.
Serveral ways to do it and it is actually all over this thread as it appears to be a pretty major issue lately. I also had it on my phone, called tech support and they said it was a known issue and JI6 had the fix. I couldn't get the fix since i was on a third party ROM but was able to find Bionix 1.9.1 that has the JI6 update built in and flashed it and have been without the USB annoyance since. So, to fix you can flash a ROM with the JI6 update built in OR use Odin to flash the JI6 to your phone. For me using Rom Manager is easier than Odin.
Read my thread for a fix that worked for me. Its in Q&A
Sent from my SGH-T959 using XDA App
homerbrew said:
That happened to me before. I rebooted and that didn't fix it, so I did a master reset and that cleared it up. It was kind of pain to redo everything, but not too bad.
Click to expand...
Click to collapse
I've done a Factory Reset before when I went back to stock and that didn't help me.
deez1234 said:
Read my thread for a fix that worked for me. Its in Q&A
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I suppose this wouldn't be possible for me as I have the Verizon Fascinate. Our update 2.1 - Update 1, DI01 didn't include a USB fix that I'm aware of.
any body have fix usb connected ?
i've done all which is writes around the internernet after reading 400+ web site threads/posts still not able to solve, Please if anybody have done please share with us
thanks
the vibrant seems to do that when you have a cable that is wired for data transfer, the vibrant sometimes gives you the message even when your not connected to a computer, (I.E. connected to the wall) if you use a cable that does not do data transfer (it will specifically say not for data transfer on the package) then it will never pop up. Rocketfish makes one of these type cables, its usually more convenient to just deal with the notification rather than getting a special cable though. I only got the charging cable cause the data transfer cables were pretty expensive at best buy. the power only cables are a bit cheaper.
@firely
i think you don;t know my all story ;-)
actually without connect charger or usb cable i'm not able to turn on my phone,
after on usb connected message appear at left side top,
i want to trade my phone (its brand new like get before 2 weeks)
that's way i want to solve this problem, Phone Should be on without any power connected like usb and charger,
its my story
USB Issue Perhaps Larger Then It Seems
My update on this, no one seems to have presented a solution. Flashes, kernels, etc don't fix. The problem is it incapacitates your phone, as there is no internal SD card mounted since it thinks USB is plugged in. Can't download songs on SD card, can't power on without it plugged in and seeing battery indicator first. Then last night on top of everything, my market showed downloads that I didn't authorize. Strange behavior, I have put bionix, know how to ODIN, etc, but nothing so far has fixed this USB connected / mounted issue and it seems like I have to return this. I'm worried there is a virus associeted with this behavior. I don't download apps that appear dangerous, (sex related, obscure, not without many downloads or robust developer site). I have a friend who has JI6 but has never rooted or modded and around the same time, Halloween his started this too. Power indicator still indicates charging after unplugged, USB connected constantly flashes off and on, battery life is worse. There is soemthing deeper seemingly happening because rebooting, resetting data, wiping dalvik cache, does not give me the basic ability to turn on phone without USB connection. App settings, I say choose on connect. Finally got computer to recognize again as a drive, but inconsistent, tried to reinstall USB drivers on win7. over all really wonky behavior since it powered down while on charger a week or so ago. Sometimes plugging into wall charger gives error. Only way to get it to stop showing USB message was to unmount phone storage, but now I don't even get options to mount or unmount phone storage. love this screen and have loved modding but frustration is sinking in, will try to get tmo to replace with this, but hoping it's not a larger virus related issue, would be scary deal.
hey said it was a known issue and JI6 had the fix
Click to expand...
Click to collapse
I don't think so: I have the rooted JI6 on the phone incl. Clockw.
Yesterday I see also that the USB cable "should" be connected, after I have enable the Debug-Mode, the red Triangle comes too in the status bar.
That's all in the Underground station
A reboot helps on my side.
USB Woes Continue, Phone Meltdown
This is not just a debugging / reboot issue in my case, it is also effecting my friends who doesn't have bionix, just the JI6 build TMO OTA update. THis is a serious bug, perhaps brought on by a virus who knows, but my buddy who has this same problem is now going ballistic and running into the arms of apple. there is no resolution to this issue throughout the forums. Tmo is exchanging with me, and I have installed multiple ROMs, know how to search forums, kernels, ODIN, all that. Now my radio for cellular doesn't turn on and I have to reboot, it just seems pretty hosed at the moment and I find it coincidental that my friends phone (he is a technical design guy) is having the same mounting SD card issue, basically bottom line is, the thing won't turn on without being plugged in and flashing back to stock, different roms, still will not mount the internal SD card, or recognize it in many cases. I have reformatted, cleared davlik cache, most options from recovery, no dice. can't download to SD card, because it always thinks USB is connected, even when the device is turned off. i hope this resent one works fine and I will document the details since this happened for the hard working devs to have details that maybe can be discovered, but the most worrisome part is that it seems like it may be virus related. I hope that's not the case and just odd coincidence. There is no changing USB settings or debugging combinations that will solve this issue in my experience.
sad but hopeful vibrant owner,
jellyculligan
vibrant with stock (after bionix fusion), oc / uv JAC kernel.
I just got this issue as well and nothing has worked for me so i'll be replacing it with a new vibrant but I wont have a phone for about a month! Does anyone know if tmobile rents out phones?
deez1234 said:
Read my thread for a fix that worked for me. Its in Q&A
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
would you happen to have a link to said thread?
Mine does it when I plug into the wall charger. I just went ahead and synced with the house. Now I can turn the lamps on/off from anywhere.
This is a bizarre problem for me that's I can't find solutions to anywhere else. I have a 32GB Nexus 7 (NOT the 2013 variety) running Android 4.3. I've never rooted this tablet before, everything is original and I've never seen any issues with battery or screen performance before. After using my tablet during class with no problems and an 80% charge, I turned it off, traveled 10 minutes to a meeting, and pulled it out of my bag to turn it on. The screen didn't turn on, so I held the power button to soft rest it. Nothing happened, so I tried booting into the bootloader by holding down power and volume down. No luck there either. I plugged it into my computer and got an error message saying "USB device has malfunctioned". I tried using adb to reboot it or reflash a stock ROM with no luck, as the command prompt couldn't find my device. If I performed a soft rest or unlplugged my tablet from the computer, I would get a chime indicating that a USB device had been disconnected.
Does anyone have any suggestions with how I could proceed troubleshooting from here? I suspect there's probably a hardware issue, but that doesn't make much sense, since it was in a protected pocket for only 10 minutes and stopped working. Any help would be greatly appreciated.
Hi folks,
Fortunately I've not had much necessity to post here for help. However, that's now change.
I am looking for suggestions on:
1) What might be the cause of an issue with my N4
2) What I might be able to do about it.
Here's the background:
My N4 was working fine. Stock device, 4.4.2, no rooting, etc.
The other day it spontaneously turned off. I was not able to turn it back on. "Google" would appear on the screen, but a few seconds later would vanish and device was off again.
I did figure out I could turn it on (most of the time) when it was plugged into a power source. But detaching from that power source (whilst it was running) would result in it turning off within a couple of seconds at most.
I managed to back up most of my data, whilst having it plugged in and turned on.
A few days later device tells me there's a 4.4.3 update. I update it.
Issue remains.
I then try to initiate a factory reset.
Device reboots during that process. But fails to restart.
I could no longer restart it whether plugged in or not.
It can sit in bootloader mode without being plugged in, for as long as it takes to run the battery down.
It can't be in recovery mode without ext power.
I load the TWRP recovery image. That is on and working fine.
I can access the device with fastboot command (via Windows 7)... which is how I got the TWRP image on there.
In recovery mode the device is not detected by windows, and adp command can't see the device.
This is about where I have come unstuck. I was attempting to install a clean Android 4.4.3 image onto the device. But I can't get ADB access to it. Tried on a Mac and a Windows 7 PC.
UPDATE: I did manage to complete instructions for installing new Android 4.4.3 image over fastboot mode. But even after completing the steps successfully, device won't start. Just "Google" flashes up, and devices stops after few seconds.
HARDWARE FAILURE?: It's possible this whole issue is hardware related and I'll have to ditch the device. If that likely? I've seen some people mentioning similar issues, which they resolved by replacing the USB port board. Is that likely to cause this kind of issue?
Does some kind person have any suggestions on steps I can from here?
I'd really like to recover this beast... it's my first and only smart phone, and would hate to drop to a cheap replacement cell phone for the foreseeable future.
Thank you...
Somehow my title was blank (just a [Q]). Might explain why I got no replies so far :silly:
Updated.
If its happening even after a full reset and flashing of the factory image, that most likely means it is a hardware issue, maybe the battery. You can try changing it yourself or getting someone else to do it. This is what I think the issue is.
lolcakes203 said:
If its happening even after a full reset and flashing of the factory image, that most likely means it is a hardware issue, maybe the battery. You can try changing it yourself or getting someone else to do it. This is what I think the issue is.
Click to expand...
Click to collapse
Hi there,
Thanks.
Regarding the battery... I had considered that. Although the battery was working fine right up to the time the N4 started having issues. Even during the issues... I could charge and discharge the battery as per normal. I tested this by discharging it by leaving the N4 in bootloader mode, and unplugged. After about 12 hours it would discharge completely. I was then able to charge it up, as per normal.
So that had me thinking it was not likely the battery at fault. What are your thoughts?
Very strange situation here. It seems somehow that booting into android causes some sort of power delivery issue and that results in the phone shutting down. I don't understand how that power delivery issue can exist within the android os but not within the bootloader if it was a hardware issue, especially after flashing the full factory image. I'm not sure, but I would still bet it a hardware issue, although perhaps not the battery.
Sent from my Nexus 4 using XDA Free mobile app
It sounds like the battery to me, running in bootloader mode requires nowhere near the current that the full OS does.
DrFredPhD said:
It sounds like the battery to me, running in bootloader mode requires nowhere near the current that the full OS does.
Click to expand...
Click to collapse
I apologise for taking so long to respond. I don't seem to be getting notifications. Will check into that.
With regard to the battery... When the phone is fully charged (and it was just like normal... prior to me toasting the OS in an attempt to refresh the device, AND it charges normally by plugging it in when turned off or in BL mode), it takes perhaps 12 hours or more to discharge, with the screen on permanently, whilst I leave it in BL mode. So if the battery is the issue, it's certainly got nothing to do with the battery being able to receive and take a charge. That happens absolutely per normal.
What I am wondering, however, if perhaps the USB board could be faulty? I actually replaced the USB board a month or two ago, as the connector on the original one died and Google refused to repair it on warranty because there was a crack on the back glass. The replacement is an LG part. I am wondering if there might be something in that logic of that board that is screwing up... such that when the cable is unplugged the device somehow "thinks" it is plugged in and thus in charge mode, rather than drawing from the battery. I am not sure where the logic for the device to determine whether to draw current from battery or USB resides. But is it feasible that this might be going on?
I'd love to revive this little brick back to smart-phone status.
My son has an SM N910F note 4. Completely stock. It suddenly stopped charging after a long international flight and now when connected to the charger the battery charging image appears, but then after a brief pause disappears, and the vibrator motor vibrates continuously at 1 sec intervals after that. The phone boots into stock rom OK and also into recovery and fastboot mode.
I have tried different cables (several), 4 different chargers , cleaned the connector on the phone (and cable connectors) with air and alcohol. Contacts seem to be OK on visual inspection. Cables and chargers work fine on other devices including a stock rooted Galaxy S4. Also, purchased a new battery but it did not change any of the above symptoms. When I tried to access the Note 4 from my Linux PC, MTP showed nothing and adb devices and fastboot devices saw nothing lsusb didn't see anything either. Different cables didn't alter this.
One odd thing is that when I boot into recovery I do not see the recovery menu but it immediately reports that it is installing an update and after a minute stops with the "failed to find command " error message. We are unaware of any recent uninstalled OTA updates though. Then the recovery menu reappears.
Can someone suggest for me what might account for these symptoms. I have no idea, but when the device was not visible in my Linux machine I began to suspect a faulty USB/charging port. Trouble is we are running out of battery charge to test anything now and no way of recharging
gc2712 said:
My son has an SM N910F note 4. Completely stock. It suddenly stopped charging after a long international flight and now when connected to the charger the battery charging image appears, but then after a brief pause disappears, and the vibrator motor vibrates continuously at 1 sec intervals after that. The phone boots into stock rom OK and also into recovery and fastboot mode.
I have tried different cables (several), 4 different chargers , cleaned the connector on the phone (and cable connectors) with air and alcohol. Contacts seem to be OK on visual inspection. Cables and chargers work fine on other devices including a stock rooted Galaxy S4. Also, purchased a new battery but it did not change any of the above symptoms. When I tried to access the Note 4 from my Linux PC, MTP showed nothing and adb devices and fastboot devices saw nothing lsusb didn't see anything either. Different cables didn't alter this.
One odd thing is that when I boot into recovery I do not see the recovery menu but it immediately reports that it is installing an update and after a minute stops with the "failed to find command " error message. We are unaware of any recent uninstalled OTA updates though. Then the recovery menu reappears.
Can someone suggest for me what might account for these symptoms. I have no idea, but when the device was not visible in my Linux machine I began to suspect a faulty USB/charging port. Trouble is we are running out of battery charge to test anything now and no way of recharging
Click to expand...
Click to collapse
Can you boot to download (odin ) mode ?
HW failure
Unfutunately, it is a HW problem. You should the USB connector panel.
Search note 4 flex usb on ebay or Ali.
android freek said:
Can you boot to download (odin ) mode ?
Click to expand...
Click to collapse
Yes, I can boot into Odin mode or recovery, but not recognised by laptop. Also, when charger is plugged in the Note 4 will not boot from power button. But as soon as I remove USB cable it will boot. Also, since posting I tried a factory reset and formatted data and cache from recovery. No change though. Still vibrates every 2 secs and will not boot. Battery does not charge at all during this process.
It's still under warranty so I don't want to try the eBay path suggested by Balint320 for repairing it myself at this stage.
Fixed?
Did you get this resolved? Mine is doing the exact same thing since a t-mobile security update. Have tried the master reset twice and clearing the cache. Tried the original charger and several others.
i am having the same problem on n910g, it just stopped charging.I tried everything, from different chargers to a new battery, but no avail.it just vibrates at 1 sec continuously and does not charge at all.
I still have 1 month warranty left but It was rooted and everything so..if there is a way to migrate to fully stock ROM please guide me, so that I can take it to service center.
IronMan_in said:
i am having the same problem on n910g, it just stopped charging.I tried everything, from different chargers to a new battery, but no avail.it just vibrates at 1 sec continuously and does not charge at all.
I still have 1 month warranty left but It was rooted and everything so..if there is a way to migrate to fully stock ROM please guide me, so that I can take it to service center.
Click to expand...
Click to collapse
The only thing I can suggest is, of you are able to get into download mode, is downloading the stock ROM and reinstalling with Odin. Some suggest holding the power button down for a few seconds after removing the battery to make sure that all charge to components is drained before restarting.
Have you tried installing Smartswitch on your PC to see if it detects a problem and is willing to correct it? At least, it will install the correct USB drivers to ensure Odin works fine. Sometimes I think Samsung need a kick in the butt for their slack approach to software reliability and utilities for maintainence and repair. Try just sending it back under warranty anyway if you can't get it to work. Maybe hardware failure. Good luck.
Anyone has any such similar issue with their Zen3 Max? This happened after using a micro ubs/otg fan on my phone. Shutdown, restarted and stuck in bootloop. Initially, I lost charging too, unless I turned the phone off. But after a couple of factory resets, normal charging came back. Now the phone will just randomly restart by itself. Annoying thing is it wont get past the boot image and restart all over again. This will continue forever, unless I plug the reverse charging otg cable on. Strange. And this would stop the random restart/reboot issue too. What gives? Anyone has any idea? I've done like 10 factory resets and wipe cache but it is still the same. And reverse charging still works fine.
Experienced the same problem too.
I've been thinking it's the kernel and the kernel doesn't support the otg fan.
Can we request some developers to provide us a stock modified kernel out from the asus support website with included drivers for otg support?