Database Users

USB connected msg when not

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.

[Q/Help] Phone will not turn off...?

When I turn off the phone, it vibrates to let me know it is off, and then it waits two seconds or so then turns itself back on.
I have done hard reset after hard reset, put the latest KE8 on and it still does it. Could it be a battery fault?

Do you have Advanced Power Menu installed?

Nope. It is now not letting me switch it on unless plugged into the charger.
If I switch it on away from the charger, it shows me a battery on the screen with a flickering yellow warning triangle with a thermometer next to it.
Any thoughts?

sorry to hear that!
i've had this problem about one or two months ago, after i flashed a new rom (can'r remember which one, was it lightning?). did almost everything i could
imagine (flashed other recovery, kernel, modem) and nothing helped. also a
complete fresh install (wipe everything before) didn't solve this!
the only thing which worked for me was to go back to my old rom. after that
everything was fine again!
so, i cannot say what causes this, but if you flash another rom it should work again! if not, try to repartition with odin, using one of the provided PIT files!

yep also had this problem when i first flashed cognition. my phone would reboot after turning it off. and if the battery went dead, when i plugged it into charge it would turn itself on instead of going to the battery charging screen. all i did was reflash the rom and all was fine.

This morning I updated to Android 2.3.4.
If I root like this:
http://androidflip.com/root-samsung-galaxy-s2-android-234-xxkg1-firmware/
Will it help do you think?

Just to update, it seems to be resolved now using this:
http://www.theandroidsoul.com/root-xxkg1-android-2-3-4-firmware-rom-on-galaxy-s2/
Thanks for your help guys!

And now its doing it again lol
I can live with it, but a couple of things like it thinking there is a USB cable connected seem to happen every now and again...?

hmm thats the same way as i did it but i didnt do the yellow triangle trick so im not sure about that. everything else is standard, thats how i flashed my rom and i only had your problem the first time i flashed. did you do the yellow triangle removal?

I did the remove triangle thing yea.
I do think it is a problem with the USB connector, it could be touching itself inside, possibly causing a shortage as it occasionally thinks a USB cable is connected.
So, if I turn off, it could be thinking that the charger has initiated connection and starts up to charge, but can't charge so just continues to boot.
I have plugged the usb cable in and with nothing at the other end, and nothing pops up. So it could be something like what I suggest. It has been ok for an hour or so now so fingers crossed lol!

lol that cud be it then. it wud make sence. might wanna get that looked at tho if you dont wanna risk damaging the phone. if its doing what you said, then it cud end up killing the phone if it shorts it out permantly. let me know how its going in a day or so.

Even on lock screen if you press and hold the power button for 8 seconds the phone does shut off, is it happening for ya?

I had this a few weeks back. Reflashing cf root kernel fixed mine.

minty1978 said:
I had this a few weeks back. Reflashing cf root kernel fixed mine.
Click to expand...
Click to collapse
Likewise, solved my problems with the phone rebooting itself instead of turning off.

Guys read this and give thoughts please!!!!

Ok this will be a bit lengthy but please bare with me and read...
Ive been running Darkyy 10.1 EE for months now and every has been fine.
Easily a couple of days battery, no force close issues of any sorts... Everything has been perfect.
Then the other day i noticed my battery started dropping fast. NO THIS IS NOT A BATTERY DRAIN THREAD SO PLEASE READ ON.
I took my phone off charge the other night within seconds of hearing the beep for battery full and the fully charged icon in the top right of the bar stayed there for a few seconds ( like maybe 10 ) and then the battery level dropped to 80%.
I thought hhmmm thats not right but left it and went to bed.
6 hours later i woke up to 31% battery.
I thought something must be running killing my battery so i did a reboot...
Now this is where it gets weird. Read on my friends...
after i rebooted the phone it kept rebooting itself every 2 minutes or so.
I pulled the battery of for 30 minutes and put it back but i had the same problem.
When i got home i did a factory rest and wipe cache partition and decided to flash Darkyy 10.2...
I had the same problems as above only now when my phone rebooted the battery lvl would drop by 20% then next time raise by 5% etc etc
NOW THIS BIT IS SCARY BUT READ ON!!!
I decided to flash back to froyo with ezbase using repartition to see if that would help.
I plugged my phone into the computer and nothing happened!!!! My computer wouldnt recognise my phone at all neither would my phone start charging whilst plugged into the computer.
I managed to get my computer to see my phone by booting into recovery and and then download mode and flashed ezbase.
Again same problems. So i thought OK this might be an insurance job so i flashed it back to stock JPY from samfirmware.com. I plugged it back into my computer and my PC says "the USB device you have connected has malfunctioned and windows cannot recognise..."
I have had my phone unplugged over night but the icon on the bar is still there showing USB connected, and in the pull down shade there is still the option to connect USB to copy files.
I have plugged it in this morning and it started charging but windows didnt even recognise that there was anything attached at all! No beep no fault deviced attached message... Nothing!
Oh i would also like to mention that when i flashed ezbase and tryied to do a reboot i would get the battery icon for a second like if you charged while the phone was off and then it would power down again... The only way i could get the phone to boot back up was to flash EZbase again with auto reboot ticked!
Yes that was very long sorry and thankyou to those who took the time to read it.
If anyone has any thoughts on why this would have happened please post.
Do you think this is something caused by the custom rom or is this a hardware issue completely out of my hands?
Thank you again for reading!

Have you tried another battery?
Sent using geek power

First, I would try to check if its a hardware problem.
For that burn a stock rom and see how it is doing. If its working fine with stock, without any problem, then obviously its ROM issue.
Else if the stock also gives you the same problem, then I would say its a hardware problem.

gsw5700 said:
Have you tried another battery?
Sent using geek power
Click to expand...
Click to collapse
I dont think its a battery issue because the battery wouldnt prevent the computer from seeing the device would it?
mammenj said:
First, I would try to check if its a hardware problem.
For that burn a stock rom and see how it is doing. If its working fine with stock, without any problem, then obviously its ROM issue.
Else if the stock also gives you the same problem, then I would say its a hardware problem.
Click to expand...
Click to collapse
Im running stock JPY right now and have the same problem

Could it be a damaged usb port, so that it doesn't always charge properly, and doesn't always detect the phone correctly when connected to the computer? That might explain the problems... Especially if that port is getting worse all the time.
Can you get it to detect on the computer if you wiggle the usb plug to the phone? Have you tried a replacement usb lead?
It does sound weird. Hope you manage to sort it out.
Mike
Garbled meaning induced by swype!

don wadte time if ur phone dosnt work on stock then its the port tht got damaged and the hardware,,,,something wrong .....better go to a service center..don expirement ,cause it might damage it more

I have just dropped it off at the shop i bought it from and they are sending it away for repair.
2 weeks of nokia 3210 magic for me!
Thanks for replies guys.

[Q] Charging Problem - Verizon xt907

Trying to fix a family members xt907 so here's the situation which has been nothing but headaches for me:
1. The Phone is only 7 months old and the bootloader is unlocked so warranty exchange is out of the question. She let the battery run down until the phone died. Then without charging the phone she turned it back on and it died again. From that point she couldn't get it to charge or turn back on while plugged in. At this point she brought it to me.
2. I got the phone and did a soft reset which finally got the charging screen to come up (showed the actual charging icon and the fill meter would flash up and then back down periodically). Problem is it never went past 0% after charging all night. I went ahead and tried to power it up thinking maybe it was just a glitch with the charging screen. Phone wouldnt boot. Just stuck at the Motorola logo. Another soft reset and the phone finally boots but now the battery icon showed a '?' and status showed '5% - Unknown'.
3. Performed a factory reset. No change. So I used RSD to flash the stock 4.1.2 firmware/kernel/modem, etc... What I found strange here is that despite the low battery Fastboot AP showed battery as OK, not low and let me flash (bootloader is unlocked, not sure if that affects low battery flashing or if that safeguard just wasnt built into the M).
4. So phone boots back up and shows 7% battery. Plugging in the charger at first notice has no affect. Battery stats shows '7% - Not Charging'. So I unplug the charger and the low battery warning pops up. Plug it back in and phone still doesnt register as charging, but says 'Not Charging'. Then I notice that the lockscreen shows '7% Charging'. Weird. Regardless of all that, the battery was not charging. The percentage never goes up and after reboots the percentage will remain the same. The battery does slowly discharge on the charger if I have it powered on.
5. I tried flashing a couple different roms before flashing back to stock and all had the same problem. I've formated /system hoping it was a problem with the OS but it didnt help. All of these charging tests were performed with the stock Motorola usb cable plugged into the wall charger. I tested the Motorola charger against my S4 to verify it works and also tried my Samsung charger on the Razr and it made no difference. However, booting the Razr M up with the Samsung charger resulted in the '?' in the battery icon and a notification in the status bar saying something about a CommServer starting. This notification was persistant and could not be dismissed. If I reboot the phone with the Motorola charger or no charger then that notification and the '?' dont appear.
6. I should also point out that I opened the phone up and disconnected the battery from the board and discharged the board. As a last resort I completely removed the battery and peeled back the tape on the bottom of the battery to expose the + and - terminals on the battery and wired it up to a stripped down charger and left it for a bit. Upon putting the battery back in the phone it showed a charge of 30% but still had all the same problems otherwise. So the battery is capable of taking a charge, it just wont take it through the phone, whether powered on or off. Thats what leads me to believe the battery itself is not bad. Its not practical for her to pull the battery to charge it, obviously. The phone detects the cable being plugged in and I can transfer files via usb cable to/from the computer no problem, so I'm fairly sure the Micro usb port is ok. Just refuses to charge.
A little lengthy but I'm at my wits end on this and really dont want to have her buy a $50 battery and then its a problem with the phone. I dont usually get stumped when it comes to fixing something but this one really has me. So if anybody can shed some light on this situation it would be greatly appreciated.

CallMeAria said:
Trying to fix a family members xt907 so here's the situation which has been nothing but headaches for me:
1. The Phone is only 7 months old and the bootloader is unlocked so warranty exchange is out of the question. She let the battery run down until the phone died. Then without charging the phone she turned it back on and it died again. From that point she couldn't get it to charge or turn back on while plugged in. At this point she brought it to me.
2. I got the phone and did a soft reset which finally got the charging screen to come up (showed the actual charging icon and the fill meter would flash up and then back down periodically). Problem is it never went past 0% after charging all night. I went ahead and tried to power it up thinking maybe it was just a glitch with the charging screen. Phone wouldnt boot. Just stuck at the Motorola logo. Another soft reset and the phone finally boots but now the battery icon showed a '?' and status showed '5% - Unknown'.
3. Performed a factory reset. No change. So I used RSD to flash the stock 4.1.2 firmware/kernel/modem, etc... What I found strange here is that despite the low battery Fastboot AP showed battery as OK, not low and let me flash (bootloader is unlocked, not sure if that affects low battery flashing or if that safeguard just wasnt built into the M).
4. So phone boots back up and shows 7% battery. Plugging in the charger at first notice has no affect. Battery stats shows '7% - Not Charging'. So I unplug the charger and the low battery warning pops up. Plug it back in and phone still doesnt register as charging, but says 'Not Charging'. Then I notice that the lockscreen shows '7% Charging'. Weird. Regardless of all that, the battery was not charging. The percentage never goes up and after reboots the percentage will remain the same. The battery does slowly discharge on the charger if I have it powered on.
5. I tried flashing a couple different roms before flashing back to stock and all had the same problem. I've formated /system hoping it was a problem with the OS but it didnt help. All of these charging tests were performed with the stock Motorola usb cable plugged into the wall charger. I tested the Motorola charger against my S4 to verify it works and also tried my Samsung charger on the Razr and it made no difference. However, booting the Razr M up with the Samsung charger resulted in the '?' in the battery icon and a notification in the status bar saying something about a CommServer starting. This notification was persistant and could not be dismissed. If I reboot the phone with the Motorola charger or no charger then that notification and the '?' dont appear.
6. I should also point out that I opened the phone up and disconnected the battery from the board and discharged the board. As a last resort I completely removed the battery and peeled back the tape on the bottom of the battery to expose the + and - terminals on the battery and wired it up to a stripped down charger and left it for a bit. Upon putting the battery back in the phone it showed a charge of 30% but still had all the same problems otherwise. So the battery is capable of taking a charge, it just wont take it through the phone, whether powered on or off. Thats what leads me to believe the battery itself is not bad. Its not practical for her to pull the battery to charge it, obviously. The phone detects the cable being plugged in and I can transfer files via usb cable to/from the computer no problem, so I'm fairly sure the Micro usb port is ok. Just refuses to charge.
A little lengthy but I'm at my wits end on this and really dont want to have her buy a $50 battery and then its a problem with the phone. I dont usually get stumped when it comes to fixing something but this one really has me. So if anybody can shed some light on this situation it would be greatly appreciated.
Click to expand...
Click to collapse
I presumed you tried to wipe the battery stats via the battery calibration app? not that I think it would make a difference. another option is enable/disable USB debugging. you could also try charging into a PC or a different outlet (perhaps that outlet does not provide a good current)?
not really sure, just tossing out some ideas...

jco23 said:
I presumed you tried to wipe the battery stats via the battery calibration app? not that I think it would make a difference. another option is enable/disable USB debugging. you could also try charging into a PC or a different outlet (perhaps that outlet does not provide a good current)?
not really sure, just tossing out some ideas...
Click to expand...
Click to collapse
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.

CallMeAria said:
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
Click to expand...
Click to collapse
Doubt it. However, the issue seems to be with the hardware, and since it is not a software issue, Motorola could honor the warranty. Last resort would be to unroot and see if you can get an exchange.
Sent from my XT907 using xda app-developers app

have you tried a non moto cable? the one that came with my fone was total crap, would continuously connect and disconnect when i hooked it up to my comp or try to charge it, so i tried my old samsung cable and i didnt have any disconnect problems at all. just a suggestion

CallMeAria said:
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
Click to expand...
Click to collapse
Did you ever find a solution? I am having the same issues with my xt907.

What did you have it plugged in to? The fact that it said it was not charging indicates maybe you didn't have enough power coming through the charging port...
Sent from my XT907 using Tapatalk 4 Beta

uthkuknwme said:
have you tried a non moto cable? the one that came with my fone was total crap, would continuously connect and disconnect when i hooked it up to my comp or try to charge it, so i tried my old samsung cable and i didnt have any disconnect problems at all. just a suggestion
Click to expand...
Click to collapse
yeah I tried my Samsung cable as well.
jgramkow said:
Did you ever find a solution? I am having the same issues with my xt907.
Click to expand...
Click to collapse
No. Verizon finally sent her a refurb replacement. I got the battery to charge up by taking it out and rigging a charger to it. But the phone still wouldnt accept a charge with the battery back in and it lost the charge it did have 2-3 times faster than normal. Battery Stats also showed the battery was showing a pretty decent voltage so unless the battery itself has a low charge circuit that gets tripped I'd be hesitant to point to the battery itself. And the charger port transfered files just fine and the phone recognized when the charger was plugged in (would go from 'discharging' to 'not charging'. So yeah, I was left stumped. Hopefully somebody else can get this solved for you.

CallMeAria said:
yeah I tried my Samsung cable as well.
No. Verizon finally sent her a refurb replacement. I got the battery to charge up by taking it out and rigging a charger to it. But the phone still wouldnt accept a charge with the battery back in and it lost the charge it did have 2-3 times faster than normal. Battery Stats also showed the battery was showing a pretty decent voltage so unless the battery itself has a low charge circuit that gets tripped I'd be hesitant to point to the battery itself. And the charger port transfered files just fine and the phone recognized when the charger was plugged in (would go from 'discharging' to 'not charging'. So yeah, I was left stumped. Hopefully somebody else can get this solved for you.
Click to expand...
Click to collapse
Just an update: I ended up buying a replacement battery and it fixed the charging issue. I rsd back to stock. Then, playing around with it, I booted to bootloader and selected "Factory" and it immediately booted back to stock, but, the battery had a "?" again. Ready to throw the damn phone against the wall, I rebooted it. The "?" is mysteriously gone. What is the "Factory" setting? I think I tried it before, but had CM10.1 installed. My theory is that this "factory" boot from bootloader actually soft bricked the phone. Either that or the issue was truly the battery and simply replacing it fixed things. I am up and running now, cm10.1 is flawless, imho. Thanks for the quick reply and I hope this helps anyone with similar issues.
Beware of the "Factory" bootloader option...........

Here we go again. Upon a reboot into recovery. Recovery is twrp 2.5. What I notice is the motorola boot img takes an extremely long time (2 minutes) to turn off and cyanogenmod to begin. Could there be something corrupt in the bootloader? Is there any way to reload the bootloader on this device? Anyone have any ideas? Could it be Recovery?

Phone wont lasted 10 seconds without plugging in ,But not battery problem.

Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks 

Jz Chong said:
Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks 
Click to expand...
Click to collapse
Have you tried making a clean wipe and trying either stock or another ROM, to see if it works then?

Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.

DrFredPhD said:
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
Click to expand...
Click to collapse
Hello, much appreciate your reply. I flashed back to stock 5.1.1 now and yet this problem is still persisting. Thus pretty obvious thats an hardware faulty.
In another forum, a guy with Nexus 7 had similar situation as me, and he suggests that its the battery or the circuit board at the charging port went kaput.
Guess nothing else I could do right now, gonna send in the phone for repair and hope the bill wont cost as much as a used nexus 4