Related
2 days ago i had my cingular 8125 plugged into a charger . when i woke up it was off and dead, still plugged in?
now when i plug it in (to the stock charger) the red light comes on, but if i take the battery out, it stays on. if the battery is in, it is on. but i cant turn it on. ive left it for 15 hours now, and still nothing
even tried another battery.
when i first put the other battery in it turned on, was booting, but then died. probably cuz the battery was dead. but i had it plugged in as soon as i turned it on.
now the same thing happens.
any ideas?
i also thought i smelled something burnt. like if you have ever had a laptop that had a bad a/c connector and would heat up a bit, or even smoke!
dont know if it was my imagination or what?
thanks in advance
dan
T mobile MDA shows RED LED
that is strange that you post this today, because I just received T-mobile MDA unit from 3bay that has a similar problem.
-The phone does not turn on when I press the power button.
-It does not respond to a soft reset or a hard reset.
-With the battery in, I connect the AC charger to the phone and for about 1-3 seconds the charging LED color is RED. THe LED turns off and I can not get the same result if I reconnect the AC charger.
The only visible sign of life this MDA unit has is:
-with the battery out and the AC charger connected, when the USB is removed to the point where it is not connected to the MDA, the charging LED light flashes red for a split second and the screen flashes white for a split second as well. [I hope this is a sign that there's still life in this MDA, but i'm thinking my unit is truly a brick..]
From all the websites I've searched, this does not seem to be an issue, although for me it is a scary one! Anybody that can help would be much appreciated because I want a working MDA not a dead one
EDIT: It turns out my non-booting MDA was due to a faulty vibrator and flashlight MDA part. After removing these two pieces that are connected to the back cover of the MDA housing, the MDA booted up with no problem.
danrw84 said:
2 days ago i had my cingular 8125 plugged into a charger . when i woke up it was off and dead, still plugged in?
Click to expand...
Click to collapse
I'm in exactly the same position - left phone on charge overnight two days ago and in the morning it was completely dead. I have managed to get it to power on for about 2-3 seconds on one or two occasions but now it won't do a thing
Not sure if this will help, but have you tried to push that soft reset button that you have to to push with your stylus when it is plugged in?
Sounds stupid, but my power button is completely dead and I thats how I have to start mine up. I also have to pop out the SD card to get the screen to come out of sleep mode!
I might not work, but hey...worth a try.
Well, I eventually got back up and running. Turns out the battery was completely dead. I used the 9v battery trick and then used my USB charger to get the battery fully charged and all is well.
This leads me to query how do I now charge my phone when I don't have access to a PC? I was using a standard AC wall charger and the phone showed that it was charging but due to the fact that the display stays lit whilst on external power, this eventually killed the battery as the charge indicator appeared to be false.
*as posted verbatim in another thread*
WHAT IS THIS 9 VOLT TRICK YOU SPEAK OF?!?
funny...i'm having the same problem with 2, what were perfectly fine, wizards.
which is what brought me to this forum post.
These two devices were turned off and sat in my desk for months as they were not needed. They were perfectly good, successfully unlocked and upgraded from the advice/steps/tools provided here (thanks!). They were my primary personal and work devices until i was given the option to try a few iPAQs.
Now that I want to go back NEITHER device will boot. On the original chargers (both wall and usb) both devices will display the red light as shown in the pic above, will not boot normally, or via the 2 or 3 button methods common for these devices. The batteries do not get warm, which tells me that they are not getting current...which makes NO sense if i'm using 4 different stock charging options (2 wall and 2 usb) in different locations. One expect some variable would work to eliminate some oddity, but nothing is working.
something odd is going here. how can 2 perfectly good devices and charges suddenly crapout? I could really believe it's the battery, but one is grand spankin new (only used for a month)! Both have the main board die? Both not recognizable on any computer?
Is it possible that the backup battery is causing this? Can it me charged same as the standard if its drained? I know i'm grasping at straws here, but this odd a coincidence.
FOUND FIX
okay..this was too simple.
for some reason the USB will not provide enough"juice" to pop these out of their sleep.
I have been using this great little charging system made by good old Radio Shack that is a single plug with different adapters for all different devices...i've been using it for my iPAQ's, Blackjacks, BB's, ect. SO as a last resort i went and got the CORRECT adapter (as there are many mini usb adapters available) and SHAZAM!!! they boot right up!
don't ask me why the stock wall chargers will not work, but these RS iGo systems are the trick!
i'm going to link to the other similar issue in hopes any other folks having the same issue can benefit from this.
My 2 months old Touch HD doesn't charge the battery anymore.
If i plug the power cord, the notification led turns red for 5-7 sec., then it turns off, and the battery meter shows no charging.
I can sync it with PC but runs again on battery, even the check box (under the power meter) is unchecked.
The only way to charge the battery, is to let the battery drains out (the phone turns itself off) and remove the battery from phone for few minutes.
I have the original ROM 1.57.831.1 (47324) WWE from 04/08/09 and i tried one hard reset ("clear storage" from settings).
Does anyone know how to fix this ?
I'm verry disappointed. Now it does'nt charge even i remove the battery.
I think i'll try the warranty service.
No other suggestions ?
Are you sure it is the problem of the HTC HD? I got hte same problem. But because I charged my second battery which was newly bought from the official website HTC UK. My original battery works well. So I returned my second battery.
Try another battery.
ci6i said:
I'm verry disappointed. Now it does'nt charge even i remove the battery.
I think i'll try the warranty service.
No other suggestions ?
Click to expand...
Click to collapse
yep, same here...
my girlfriend and me, we own a HD, pretty much the same issue...
My device frist stated "unkown main battery status" and has been only willing to charge the battery while switched off and connected to PC (charger doesn't work).
My grilfriend's one now refuses to start at all.
One thing for sure - its not battery related since my fully recharged battery doesn't make her device starting.
I sometimes pulled out the battery without swichting the device off, or left it running for days before reseting it...i guess that might have triggered the problem...
gotta send it in, hopefully they don't mind my custom rom!
ci6i said:
My 2 months old Touch HD doesn't charge the battery anymore.
If i plug the power cord, the notification led turns red for 5-7 sec., then it turns off, and the battery meter shows no charging.
I can sync it with PC but runs again on battery, even the check box (under the power meter) is unchecked.
The only way to charge the battery, is to let the battery drains out (the phone turns itself off) and remove the battery from phone for few minutes.
I have the original ROM 1.57.831.1 (47324) WWE from 04/08/09 and i tried one hard reset ("clear storage" from settings).
Does anyone know how to fix this ?
Click to expand...
Click to collapse
I had this problem to.... Change of USB cable did the trick! So.....it's possible that your USB mini cable is dead. Try another USB if you haven't tried it yet.
Thank you all.
alper1 said:
I had this problem to.... Change of USB cable did the trick! So.....it's possible that your USB mini cable is dead. Try another USB if you haven't tried it yet.
Click to expand...
Click to collapse
I don't think it's the cable because i let the phone charging on my desk and suddenly, after few minutes (sometimes 1 min, sometimes 60 min) it stops charging (without touching/moving the cable),
ccieuser said:
...Try another battery
Click to expand...
Click to collapse
I'll try to find another battery but my friends use Nokia
4irm said:
...One thing for sure - its not battery related since my fully recharged battery doesn't make her device starting.
I sometimes pulled out the battery without swichting the device off, or left it running for days before reseting it
Click to expand...
Click to collapse
Well, in your case, for sure its not battery related.
After i left the battery out of the phone for 6 hours, it start charging again for 45 min then, the notification led start blinking red and green. After 2 minutes, the led turns off and i started the phone with 40% battery life.
It's driving me crazy and i don't know what to think!
I start to believe it's a battery problem but i'll ask for service opinion too, since i payed a lot of money for this.
Solved
My handset was repaired in service.
The problem was hardware related, generated by malfunction of switching power alimentation mechanism to motherboard.
When running n163, my charger (twice) stopped working until I rebooted. The odd symptom was that the "n" was green, right down to a low-battery shutdown, even when the USB end of the cable was unplugged.
The NC itself acted as if the cable was unplugged, even when plugged into a USB port.
It hasn't happened under n165, but that's only since this morning.
These were some USB changes recently, weren't there?
Thanks!
Sent from my NookColor using XDA Premium App
It happened to me again just now. I'm running n177 now, and I'd been using my NC off and on the charger all morning. I plugged in with the gauge at about half, the plug light went green, and I got no lightning bolt on the gauge.
A reboot restored normal charging.
Sent from my NookColor using XDA Premium App
stolenmoment said:
It happened to me again just now. I'm running n177 now, and I'd been using my NC off and on the charger all morning. I plugged in with the gauge at about half, the plug light went green, and I got no lightning bolt on the gauge.
A reboot restored normal charging.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
Check chargin with another cable if it works fine u need to replace ur cable.
siddhantfriends said:
Check chargin with another cable if it works fine u need to replace ur cable.
Click to expand...
Click to collapse
Same cable works fine after reboot, didn't even unplug it for the reboot. The light changed color midway through the boot.
Sent from my NookColor using XDA Premium App
I had this happen to me too. Put it on the charger last night right before I went to bed. Woke up to a green 'n' but the battery was down 6%. Unplugged & replugged the charger, still a green 'n' but not charging. Reboot got an orange 'n' and it's finally charging.
Running Nightly 174.
I am seeing a bit of bizarre behavior with Nightly 166. On two units, when I power down, and plug in the charging cord, the unit boots up. I have had to press the power button to get the screen to go dark, and it will charge faster than if I had not done so.
Also, I have experienced once or twice, an issue of putting the unit under charge only to have the charge level reported as low, but, strangely, it felt like the unit was warm, like the battery had undergone charging.
A friend's Nook with 166, he claimed when he put the unit on a charge, it kept cycling screen on/off. He was using a non-OEM cable, but the proper AC adapter.
Does the unit have to wake itself? Does the OS assist in charging the device? Is there a known issue with %Charge being displayed?
I had Nightly 177 loaded but backed it out because the Market wasn't working.
samiam24x7 said:
I am seeing a bit of bizarre behavior with Nightly 166. On two units, when I power down, and plug in the charging cord, the unit boots up. I have had to press the power button to get the screen to go dark, and it will charge faster than if I had not done so.
Click to expand...
Click to collapse
That's normal behavior. Something about preventing Sleep of Death.
Also, I have experienced once or twice, an issue of putting the unit under charge only to have the charge level reported as low, but, strangely, it felt like the unit was warm, like the battery had undergone charging.
A friend's Nook with 166, he claimed when he put the unit on a charge, it kept cycling screen on/off. He was using a non-OEM cable, but the proper AC adapter.
Click to expand...
Click to collapse
Can't trust non-OEM cables; there're extra conductors in the B&N cable for faster charging.
[QJUOTE]Does the unit have to wake itself? Does the OS assist in charging the device? Is there a known issue with %Charge being displayed?
[/QUOTE]
Yes; look for PBD, Premature Battery Death.
Turning USB host mode on and off affects my problem, but it doesn't help it any.
Sent from my NookColor using xda premium
416inversed said:
I had this happen to me too. Put it on the charger last night right before I went to bed. Woke up to a green 'n' but the battery was down 6%. Unplugged & replugged the charger, still a green 'n' but not charging. Reboot got an orange 'n' and it's finally charging.
Running Nightly 174.
Click to expand...
Click to collapse
Sounds like the same issue. I find that if it's unplugged when I boot, it just doesn't charge, and the NC never notices when I insert or remove the charger cable, the lightning bolt never changes. Also, I've lost USB storage mode altogether, a real pain.
Sent from my NookColor using xda premium
Well, it turns out that this whole problem was the charge cable. I had satisfied myself that it wasn't the cable with a visit to the store earlier, but I think that was before I realized that the "plugged in" state never changed after boot.
The fact that the plug could make the NC itself so confused about the state of the power supply is really startling. By the end, the light on the cable was changing color when I powered up.
Sent from my NookColor using xda premium
Battery Status Wonky....
Ok. Reading through this I seem to have a similar but not identical situation.
Running CyanogenMod-7-08312011-Nightly-encore with kernel 2.6.32.9.
Nothing special about the install.
Few days ago Nook took a nap and didn't wake up. Thought it was bricked but after fussing with a combination of pressing power and the "N" button finally got it to boot up like if nothing had happened.
Problem? When the battery started to discharge after its nap of death it got to 16% and stopped. Doesn't move. Perpetually at 16%.
If I plug it is to charge it the bottom gets warm, status says it is charging and the cable changes color like it is supposed to, (orange to green), just like it were fully charged but the Battery Status stays at 16%.
Bought a new cable from B&N and same thing. Battery Status stuck at 16%. Nook feels warm, (as if battery has been charged), and the cable changes color correctly, (orange to green).
At one point I even took the cable out and the status indicator showed that the battery was still being charged but no change from the 16%.
Very annoying as I keep getting notifications that I need to recharge since the battery is at 16% but I can leave it on for HOURS and it keeps working fine.
Any ideas or should I reformat to stock and get a new one from B&N?
Occams_Razor said:
Few days ago Nook took a nap and didn't wake up. Thought it was bricked but after fussing with a combination of pressing power and the "N" button finally got it to boot up like if nothing had happened.
Click to expand...
Click to collapse
That sounds like classic Sleep of Death, and is most likely unrelated.
Problem? When the battery started to discharge after its nap of death it got to 16% and stopped. Doesn't move. Perpetually at 16%.
If I plug it is to charge it the bottom gets warm, status says it is charging and the cable changes color like it is supposed to, (orange to green), just like it were fully charged but the Battery Status stays at 16%.
Click to expand...
Click to collapse
At this point, I trust the cable light over the software to reflect reality, but mine would change color as I wiggled it because it was flaking out.
Bought a new cable from B&N and same thing. Battery Status stuck at 16%. Nook feels warm, (as if battery has been charged), and the cable changes color correctly, (orange to green).
Click to expand...
Click to collapse
Did you power-cycle while plugged in? I did several boot-to-CWR while fiddling with things, and wound up with not enough power to boot when I got to the store. Try full power down, insert new cable, power up. I'm pretty sure that the software has a role in this.
At one point I even took the cable out and the status indicator showed that the battery was still being charged but no change from the 16%.
Very annoying as I keep getting notifications that I need to recharge since the battery is at 16% but I can leave it on for HOURS and it keeps working fine.
Click to expand...
Click to collapse
What's reporting 16%? Battery monitor and the status bar (just the icon) both reported consistent levels throughout, except for being always plugged in.
Any ideas or should I reformat to stock and get a new one from B&N?
Click to expand...
Click to collapse
See what happens with a power cycle while plugged in.
Sent from my NookColor using xda premium
Okay. Decided to try and discharge this puppy completely and they let it charge all the way up again and see what the Battery Status indicators look like.
As of right now, (12:24 am on Wednesday 9/14/2011), my Nook has been on since boot for 7:22:14 and the Battery Voltage still shows 3613 mV with a Battery Level of 16%.
BTW Battery Temp is 27.8 C and Battery Status shows as Discharging.
How long this sucker is going to last is anyone's guess. Hopefully by tomorrow it will be dead and I can start charging it to see if the battery status goes back to normal.
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?
Hello.
When I try to turn on my N4, I hold power button, and after about 10 seconds Red light blinks (just once, if it's connected to USB that 1 blink last for 3 seconds, if connected to wall, it's just quick 1 blink. If it not connected anywhere there is no action at all, it just stays dead, no blinks, nothing). Same if I try to go in bootloader by holding volume down+power.
This happened after I successfully installed CM12, with no errors. Then I rebooted my phone, and it just stayed black as it is now. Battery was around 25~30% that time, and phone was connected to USB.
Did I bricked my phone totally? I am now trying to charge it up already for 1 hour... but it nothing changes.
I have searched here for similar problems, but couldn't find solution...
Edit: Charging already for 10h+ , still same..
Edit2: I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Edit3: I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".
easy fix
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
zelexon said:
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
Click to expand...
Click to collapse
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Cracken6 said:
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Click to expand...
Click to collapse
I had the same problem a year ago, I tried to remove the battery, charging all night, and other solutions that I found online and no one worked.
Finally I found here in XDA a user with the same problem and his solution was charger the phone with a wireless charger, a friend of mine has one and I put the phone to charge and after a few minutes the screen goes on and the phone was charged, then I press power button and the nexus run again.
Hope this works.
Sorry for my bad English, I'm from Spain.
Good luck.
(I bought a wireless charger in case it happen again)
I don't know anyone with wireless charger. I already ordered a new battery, and then I probably will get wireless charger also. Ty.
But this problem is very weird if you think so.. I think it happened because of many aspects together:
1) Battery was already below 30%
2) I pretty regularly charge phone with USB (won't do it again)
3) It was connected to PC USB in same time.
4) I installed CM12 ROM in same time
So main reason I think is USB, that I restarted phone while it was on pretty low battery and with USB connected.. phone restarted and got invalid voltages and couldn't even boot up or charge phone. I also found an article which says, minimum voltage, when phone battery has 0%, it's 3.0V, so I was below that.. it just screwed everything and battery died. Well, I am not sure for 100% that it's battery fault, but I hope so, I really love my N4 and still wanna use it for long time, I hope it's not dead phone, just a dead battery. Lets see! I will update this thread , when I get my new battery (less than month probably).
Sorry, my english is also not perfect. I am from Latvia.
I was playing when it happened to me. The phone was very very hot and the battery was around 70%. When I put in the wireless charged and I can reboot the phone the battery was at 65%, so it had charge but the phone won't boot.
I charge my phone almost every day, sometimes with AC, others with USB (plugging to PC) or wireless that depends of my needs
I hope you can fix it. Good luck.
Btw. Do you know if battery charges with wireless charger, if it's removed from the phone?
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Flipz77 said:
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Click to expand...
Click to collapse
The battery will charge with a NCF Charger
Major Issue Google
This "Nexus SOD" issue is showing up on many sites across the Internet. I have multiple "Nexus" devices including 2 Nexus 4, 1 Nexus 5, 2 "Nexus 7 2013". It suddenly started out of the blue with one of my Nexus 4 phones. Symptoms included rapid battery discharge. I am using Lollipop 5.1 on all devices. There are many claims as to the cause, Hardware Motherboard, Power Button etc. Others claim it is "Software Related" or App Related. The problem effects Nexus 4 and Nexus 5 phones. I have ordered a new motherboard for my nexus 4 device and see if that makes a difference.
This problem should warrant a "Major Android Lollipop Crisis Team" by Google to investigate the cause and let us know what it is and what Google is doing to solve the problem before moving to announce "Android M". This issue needs to brought up and actively pursued at the upcoming "Google I/O Conference" by the strong Android Developers Groups to press for "Formal Action"
charging method
Cracken6 said:
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
Click to expand...
Click to collapse
I had this problem a long time ago and my fix worked for me after doing a little research it seems like this is a case called battery total discharge. The fix was simply to charge your phone using the wall adapter that came with your phone (I still use my old apple cube wall thing) and to wait for the red light to appear then wait about ten minutes before trying to reboot.
I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
AndRe5575 said:
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
Click to expand...
Click to collapse
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Cracken6 said:
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Click to expand...
Click to collapse
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
as9333 said:
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
Click to expand...
Click to collapse
Just tried booting without battery, and connecting to wall. Same - red light blinks once, after I hold Power button or Power+Volume down for about 15 seconds. If I keep buttons pressed, it just repeats every ~15 seconds.
Power buttons works fine.
After I checked that Device manager thing in google.. it looks very bad.. phone is dead.. probably need to change motherboard. I am just shocked, how this could happen... I didn't receive any errors during CM12 installation. Phone just instantly died after restart.