A coworker decided to replace the non-user-replaceable battery in his Droid 4 (it's actually pretty simple to do). The surgery seemed to go fine, but immediately afterwards the phone is basically acting as if it doesn't have a battery in it:
'M' logo comes up when plugged in
Holding VOL UP/DN+PWR allows access to the boot menu, but none of those options allow it to boot past the 'M' logo
No response from power button when not plugged in
Immediately powers off when power cable disconnected
I read that a factory data cable might help him, so we ordered one of those. This cable allows the phone to boot now (furthering the suspicion that it doesn't think there's a battery in it - the factory cable is supposed to allow this, and there's just an exclamation point for the battery status), but isn't much help otherwise as data can't be transferred from it. Point being, it's not a software brick - it boots fine with the factory cable.
Could this just be a bad battery or something? Has anybody here ever seen this behavior?
Thanks!
aftli said:
A coworker decided to replace the non-user-replaceable battery in his Droid 4 (it's actually pretty simple to do). The surgery seemed to go fine, but immediately afterwards the phone is basically acting as if it doesn't have a battery in it:
'M' logo comes up when plugged in
Holding VOL UP/DN+PWR allows access to the boot menu, but none of those options allow it to boot past the 'M' logo
No response from power button when not plugged in
Immediately powers off when power cable disconnected
I read that a factory data cable might help him, so we ordered one of those. This cable allows the phone to boot now (furthering the suspicion that it doesn't think there's a battery in it - the factory cable is supposed to allow this, and there's just an exclamation point for the battery status), but isn't much help otherwise as data can't be transferred from it. Point being, it's not a software brick - it boots fine with the factory cable.
Could this just be a bad battery or something? Has anybody here ever seen this behavior?
Thanks!
Click to expand...
Click to collapse
Hi,
It might be a loose connection. Did you make sure that the screws were fastened properly? Also check the battery contacts on the phone and the battery, clean it if necessary.
Are you sure that you didn't bend the battery ribbon cable? It is pretty sensitive, can be damaged by bending.
I'm pretty sure that the phone is OK, it's a battery connection problem.
aftli said:
A coworker decided to replace the non-user-replaceable battery in his Droid 4 (it's actually pretty simple to do). The surgery seemed to go fine, but immediately afterwards the phone is basically acting as if it doesn't have a battery in it:
'M' logo comes up when plugged in
Holding VOL UP/DN+PWR allows access to the boot menu, but none of those options allow it to boot past the 'M' logo
No response from power button when not plugged in
Immediately powers off when power cable disconnected
I read that a factory data cable might help him, so we ordered one of those. This cable allows the phone to boot now (furthering the suspicion that it doesn't think there's a battery in it - the factory cable is supposed to allow this, and there's just an exclamation point for the battery status), but isn't much help otherwise as data can't be transferred from it. Point being, it's not a software brick - it boots fine with the factory cable.
Could this just be a bad battery or something? Has anybody here ever seen this behavior?
Thanks!
Click to expand...
Click to collapse
This is screaming bad battery to me - either it was duff in the first place, or has been damaged during installation. Having said that, I've swapped lots of batteries multiple times, and have never damaged one during removal or installation, so if they were careful I suspect it was bad in the first place.
nagim said:
Hi,
It might be a loose connection. Did you make sure that the screws were fastened properly? Also check the battery contacts on the phone and the battery, clean it if necessary.
Are you sure that you didn't bend the battery ribbon cable? It is pretty sensitive, can be damaged by bending.
I'm pretty sure that the phone is OK, it's a battery connection problem.
Click to expand...
Click to collapse
Thanks for your input guys.
He's ordered a new battery and I'll be the one installing it this time. Will update when we get it in.
Related
I recently suffered through 3 weeks of not having a working power button and hoping that I could jiggle everything so that it would boot up if it powered off for any reason. I have since replaced the flex cable and board that goes with it. But I was wondering if there was a way to have my nexus one boot up once it got charged to a certain level? I know my friends OG Droid does it, but I wasn't sure if it was a device thing or something that could be done in android. Let me know and, as always, thanks for the help.
No, there isn't. But there is a way to power it up - remove the battery, insert USB charger cable, insert battery. It'll turn on and boot. Maybe not from a first time, though.
After an unfortunate rooting session with my Motorola Milestone, the phone now returns into an "dead" mode. It refuses to start at all. I tried charging it and see if it starts by itself, but it doesn't budge and the little while led doesn't lit. The only time when it lit is when I connect it to the PC. I tried putting in it a new battery, taking out the SD card and SIM, but to no avail. I remember seeing a video where a guy used a dissected USB cable to spark the phone into turning on again, so I take it I'll have to use a "hardware approach"? Please help.
I tried following this guide, though without success. The phone still has that white LED lit when it's connected to the PC.
After a reply on this thread I also made, it might be possible that the battery is charged, but the phone refuses to boot at all. Is there any way to unbrick the phone in this state?
Do you think your device is really BRICKED?
If so, you can try to flash your original sbf file into your phone. Guide here: http://forum.xda-developers.com/showthread.php?t=696845
If you are using a Linux, google for "sbf_flash".
I agree with my front floor..ermm, u dont need to worry about its 'dead'. just flash original sbf can rescure your phone.
I had the same problem too, but good news is I tried to revive my phone successfully recently, btw your phone is not 'dead', it's just staying in limbo state, the solution is to pull out the battery and don't connect to any usb, don't try to power it up, it must be completely out of power wait about 12 hours, and then try to power your phone, I think there is some capacitors in the phone which retain the phone state, to make it out of power will wipe out it's state, good luck
algopem said:
I had the same problem too, but good news is I tried to revive my phone successfully recently, btw your phone is not 'dead', it's just staying in limbo state, the solution is to pull out the battery and don't connect to any usb, don't try to power it up, it must be completely out of power wait about 12 hours, and then try to power your phone, I think there is some capacitors in the phone which retain the phone state, to make it out of power will wipe out it's state, good luck
Click to expand...
Click to collapse
"My phone is in limbo state... "
That's a pretty cool statement.
From technical view, it might have happened that something caused a kind of deadloop when reading scratchpad SRAM inside OMAP processor.
This SRAM, as well as the internal RTC is powered by a small battery soldered on the mainboard, while the phone is shut down and the battery is taken out.
What you did was, to wait untill this battery became uncharged.
All SRAM and RTC setting as well then gets erased.
Afterwards the CPU will start up with empty scratch SRAM, might be called a "real" cold boot
Normally the phone should not behave like this. Even if SRAM is not valid the phone should boot up...
...but anyway as you observed it like this, it might happen.
@andoruB:
Apart from that, the Milestone is hard to brick in general.
Might happen though, if you do evil things while flashing new firmware.
Especially while flashing bootloaders...
If you got some more information about the things you did, would be helpful!
Good luck anyway!
scholbert
andoruB said:
After an unfortunate rooting session with my Motorola Milestone, the phone now returns into an "dead" mode. It refuses to start at all. I tried charging it and see if it starts by itself, but it doesn't budge and the little while led doesn't lit. The only time when it lit is when I connect it to the PC. I tried putting in it a new battery, taking out the SD card and SIM, but to no avail. I remember seeing a video where a guy used a dissected USB cable to spark the phone into turning on again, so I take it I'll have to use a "hardware approach"? Please help.
Click to expand...
Click to collapse
how did u root it? can u give a more detailed description? and hows ur phone? sometimes, the milestone would just shut off and wont come up if the battery is gone. Try charging it for maybe 2-3 hours, untouched, and see what happens.
Have this exact problem. Was doing a nandroid recover when the phone got stuck. Pulled the battery out. Placed it back in, pressed the power button. Nothing.
Led lights up only when connected to the computer's USB. Battery was charged before Nandroid recover. Used nandroid a lot of times but for some reason, my stone stopped playing nice.
I just removed the battery. Hoping this works. Can someone please post if you got this same issue resolved? I like this phone no matter how slow it goes sometimes. Thanks!
I completely forgot about this thread, sorry guys!
I don't remember exactly what happened, it's been so long... but I do remember I left the phone "inactive" (it's not like i had much of a choice! XD ) for 1 or 2 months, with the battery out. After I got hold of a wall charger, I plugged in the battery, after I plugged in the charger, and what do you know? It worked! It started charging (was 60% charged, fully charged, I unplugged it, but after putting it to charge again just to make sure it was fully loaded before I would flash a new ROM, it was charged up to about 80%, weirdly, so I guess it was a weird battery problem)
I do remember I didn't do anything to it, so I'm not sure what to tell you guys to do, except leave out the battery for a month or so ^^;
Hi, as the title of this thread says, my mobile just died i dont know how but i cant do anything, i cant enter in recovery mode, i cant enter into fastboot mode, it wont recognize any command i put. The only thing it does, its that when i plug in the usb cable it turns on the green led and wants to start but when it gets to the "Warning: Bootloader unlocked" advice, it turns off again and starts again. I dont know if this can be fixed, i hope so. Thanks
PS: Sorry about my english XD
matiamb said:
Hi, as the title of this thread says, my mobile just died i dont know how but i cant do anything, i cant enter in recovery mode, i cant enter into fastboot mode, it wont recognize any command i put. The only thing it does, its that when i plug in the usb cable it turns on the green led and wants to start but when it gets to the "Warning: Bootloader unlocked" advice, it turns off again and starts again. I dont know if this can be fixed, i hope so. Thanks
PS: Sorry about my english XD
Click to expand...
Click to collapse
Just a guess, but you might have a bad battery. To test that, you can either buy or make a Motorola Factory Cable (google it) or get a new battery. Factory Cables power the phone directly from USB, bypassing the battery -- meaning if it works with the Factory Cable, the problem is with the battery. If it doesn't work with the Factory Cable, you might be screwed and need an actual repair from Motorola.
Also, try powering on the phone holding down all the buttons. That's how you access the boot menu, if you can get to that menu, you should be able to access fastboot and recovery.
And don't charge it with a PC, use the wall plug charger or a car charger. The phone treats a PC connection differently than the rest, even if the phone is off and only being plugged in to be charged -- it'll force boot/power on with a PC USB connection when it's turned off (it does for me). See if it'll take a charge with the wall/car.
My Bravo acts like this when that battery is really, really low and I plug it into a PC to charge when it's low....it also did exactly what your post said a year ago and I had to replace the battery....don't by a cheapo generic battery, I did and I regret it very badly (it has already gone out and doesn't work...the generic battery).
skeevydude said:
Just a guess, but you might have a bad battery. To test that, you can either buy or make a Motorola Factory Cable (google it) or get a new battery. Factory Cables power the phone directly from USB, bypassing the battery -- meaning if it works with the Factory Cable, the problem is with the battery. If it doesn't work with the Factory Cable, you might be screwed and need an actual repair from Motorola.
Also, try powering on the phone holding down all the buttons. That's how you access the boot menu, if you can get to that menu, you should be able to access fastboot and recovery.
And don't charge it with a PC, use the wall plug charger or a car charger. The phone treats a PC connection differently than the rest, even if the phone is off and only being plugged in to be charged -- it'll force boot/power on with a PC USB connection when it's turned off (it does for me). See if it'll take a charge with the wall/car.
My Bravo acts like this when that battery is really, really low and I plug it into a PC to charge when it's low....it also did exactly what your post said a year ago and I had to replace the battery....don't by a cheapo generic battery, I did and I regret it very badly (it has already gone out and doesn't work...the generic battery).
Click to expand...
Click to collapse
It might be the battery, because my mom dropped it into the water some weeks ago. I'll try factory cable now and see what happens. I tried holding down all the buttons but nothing happens. Just minutes ago I made it into fast boot mode, and now I'm scared of turn it off haha. I'll see what happens and let you know. Thank you for the reply!
matiamb said:
It might be the battery, because my mom dropped it into the water some weeks ago. I'll try factory cable now and see what happens. I tried holding down all the buttons but nothing happens. Just minutes ago I made it into fast boot mode, and now I'm scared of turn it off haha. I'll see what happens and let you know. Thank you for the reply!
Click to expand...
Click to collapse
Just leave it in a wall charger for a few hours then. Sounds like you might get lucky.
My Dad has dropped his in the toilet twice now (seriously, twice...figured he'd learn the first time) and on the second time, it had to be powered off, wrapped in a paper towel, and left in rice for 24 hours before it worked again (6 hours on his bed the first time). Rice draws out the moisture and is a cheap easy way to dry the internals of a phone if its soaked....just telling ya for future reference.
Mines been wet, but never soaked. These phones aren't hard at all to take apart and put back together (I repaired my Dad's cracked digitizer a few days ago in under a half hour...never taken one apart before then...the 22 #5 torx that are removed are damn annoying), so you could take it apart, blow dry it (warning: don't say on any one area for more than 5 seconds, you'll risk both unsticking the glue that holds the screen on as well as warping the motherboard), and use some PC cleaner or isopropyl alcohol (99% alcohol) and clean the board up being careful to not get alcohol on the screens -- (warning: alcohol can weaken certain plastics, but it's perfectly fine as a cleaning agent for a silicon based motherboard...alcohol also dries and removes trace amounts of moisture and can clean oxidation spots.
I can see oxidation on the battery terminals making the phone act like this. IRL, I install custom, solar powered, automatic iron gates, and the #1 repair I have to do is cleaning battery terminals. 30 seconds, a terminal post cleaner tool (glorified wire brush), and some WD-40 (acts as a sealant/water repellent) can make a non-functional gate into a working gate. Bad power flow is hell on electronics.
Just look at the EB40 mod guide. It has the exact same steps you'll need to do if you want to attempt cleaning the terminals, well, except for that step where you put in a better battery.
My phone had been working perfectly fine, as well as charging perfectly fine. Recently, I accidentally let it drop to 0%, which I don't usually do. I went to plug it into the same wall outlet as always, but instead of the usual charge process, the battery icon with the lightning bolt in the middle simply flashes on the screen and then turns off, which happens over and over again.
It should be noted as well that about 3 weeks ago my phone get fairly wet. After that incident, I turned it off till it dried, powered it up, and everything appeared to be totally ok.
Other facts:
-I can safely get into the recovery menu (power + vol down), which is stable, but any menu selections result in the Motorola splash screen for a quick second and then the phone powering down.
-The computer will recognize the connection to the phone.
Attempts to resolve:
-New cable, new usb hub, new wall outlet
-Trickle charge from the computer (same flashing)
-Phone in rice to remove moisture
-Toothbrush cleaning of Micro-usb port (suggestion from another thread)
I'm pulling my hair out, and I am considering prying off the back and replacing the battery. I have searched other threads, but have seen various solutions none of which worked for me. If anybody has any idea how I can fix this please help!!! Thanks in advance.
DroidGuy321 said:
My phone had been working perfectly fine, as well as charging perfectly fine. Recently, I accidentally let it drop to 0%, which I don't usually do. I went to plug it into the same wall outlet as always, but instead of the usual charge process, the battery icon with the lightning bolt in the middle simply flashes on the screen and then turns off, which happens over and over again.
It should be noted as well that about 3 weeks ago my phone get fairly wet. After that incident, I turned it off till it dried, powered it up, and everything appeared to be totally ok.
Other facts:
-I can safely get into the recovery menu (power + vol down), which is stable, but any menu selections result in the Motorola splash screen for a quick second and then the phone powering down.
-The computer will recognize the connection to the phone.
Attempts to resolve:
-New cable, new usb hub, new wall outlet
-Trickle charge from the computer (same flashing)
-Phone in rice to remove moisture
-Toothbrush cleaning of Micro-usb port (suggestion from another thread)
I'm pulling my hair out, and I am considering prying off the back and replacing the battery. I have searched other threads, but have seen various solutions none of which worked for me. If anybody has any idea how I can fix this please help!!! Thanks in advance.
Click to expand...
Click to collapse
Either there is something wrong with your battery, or there is something wrong with the USB port. If the USB port is the problem, you can use wireless charging instead. I'm a fan of this one, personally: https://www.amazon.com/gp/product/B00S7IBDGW/ref=oh_aui_search_detailpage?ie=UTF8&psc=1.
Also, are you unlocked? If so, what battery percentage does TWRP say?
TheSt33v said:
Either there is something wrong with your battery, or there is something wrong with the USB port. If the USB port is the problem, you can use wireless charging instead. I'm a fan of this one, personally:
Also, are you unlocked? If so, what battery percentage does TWRP say?
Click to expand...
Click to collapse
Thanks for the quick reply. It does seem like a battery problem, however it is just so coincidental that it stopped working after I let the battery drain to 0%, when only hours previously it was in use and charging without any issue at all.
Also, if there was a problem with the micro-usb port, I would think that a computer wouldnt be able to read the phone, but when I plug it in it is recognized as an ADB device.
I have another turbo with a cracked screen, I'm thinking about dissecting both and putting that battery in this phone as a replacement.
And unfortunately I am not unlocked :/.
Update
Well, after some further experimentation, I've gotten it working again. The solution was to charge it for like 5 hours, then let it sit off charge for an hour, and then it would boot... bizarre combination of actions. It has since dies twice and I've had to use this method.
It is working for now if I don't let the battery drop below like 15%. Seems more like a software or hardware issue to me, and i'm still trying to resolve it, so if anybody has any suggestions please let me know.
Also, what is the best way to re-calibrate the battery, maybe that could help?
DroidGuy321 said:
It is working for now if I don't let the battery drop below like 15%. Seems more like a software or hardware issue to me, and i'm still trying to resolve it, so if anybody has any suggestions please let me know.
Also, what is the best way to re-calibrate the battery, maybe that could help?
Click to expand...
Click to collapse
If you can't let the battery go below a certain percentage, it might be an early sign of failure. The voltage might drop suddenly and unexpectedly towards the end of discharge, prompting the phone to emergency-shutdown.
As for calibrating the battery...it depends on who you ask. I would say that running it to shutdown (even if shutdown is "15%") and then charging it to 100% should do it, since that gives the controller a full set of data with which to extrapolate a discharge curve. Clear your cache in recovery, so hopefully the OS will pick up on this to accurately track the battery's actual state.
Get Kernel Adiutor or something similar to check your battery's health, too. If there's something obviously badly wrong, it should report something other than "Good".
If you note when your battery dies abruptly and you immediately reboot the back light is very poor. Almost flickering.
I think this is a battery issue of not being able to feed enough amperage.
...however. My phone was doing this and after a full clean reflash it has stopped. I question if this is because I am running less apps now. Or if perhaps somehow the battery managed to lose its memory. (Li ion is an odd duck..)
mrkhigh said:
If you note when your battery dies abruptly and you immediately reboot the back light is very poor. Almost flickering.
I think this is a battery issue of not being able to feed enough amperage.
...however. My phone was doing this and after a full clean reflash it has stopped. I question if this is because I am running less apps now. Or if perhaps somehow the battery managed to lose its memory. (Li ion is an odd duck..)
Click to expand...
Click to collapse
Septfox said:
If you can't let the battery go below a certain percentage, it might be an early sign of failure. The voltage might drop suddenly and unexpectedly towards the end of discharge, prompting the phone to emergency-shutdown.
As for calibrating the battery...it depends on who you ask. I would say that running it to shutdown (even if shutdown is "15%") and then charging it to 100% should do it, since that gives the controller a full set of data with which to extrapolate a discharge curve. Clear your cache in recovery, so hopefully the OS will pick up on this to accurately track the battery's actual state.
Get Kernel Adiutor or something similar to check your battery's health, too. If there's something obviously badly wrong, it should report something other than "Good".
Click to expand...
Click to collapse
Thanks for the pointers. So strange, first it died at 40%, then 30% then 15%. Now, it is still dying early but I am no longer facing the issue I originally had, it will show normal charging when off, and boots up right away. Sure hope its not some ticking battery time bomb, its still a relatively new refurb.
I attempted the charge calibration so we shall see if it helps. I also did a factory reset for the hell of it, since I am on stock and can't reflash. Perhaps I'm in the clear, that would be awesome. Still no idea what the issue was in the first place though, which will annoy me to no end.
Maybe not the right sub-forum for this, but for some reason I show as not logged in on the Guides sub-forum.....
Long story short, I removed the shattered back of my phone for replacement, and in the process it appears I did something that broke the power and volume buttons. I don't know what broke, it all looks good, but I used a blade to lift the cover and in retrospect, I think heat and a suction cup would have been better.
I tried rebooting prior to installing the new rear cover, and lucky I did because I needed access to finally fix it. The buttons were completely dead, nothing worked, but if I plugged in power, it started charging, so I knew the battery and screen were still good. From adb, the device was there but unauthorized, so I was unable to boot that way (I've since rebooted and turned on USB debugging, but evidently it uses the vendor keys still when in recharge mode, and it still showed unauthorized).
None of the local shops were any help, I suspected that if I could get the boot sequence to start all would be good, and this turned out to be the case, but they were all clueless about anything other than changing the battery or the screen.
Anyway, onto the solution. The first time I got it to boot, I simply disconnected the battery, then plugged in the power using the Xiaomi charger, it wouldn't boot at all from USB power, it would only charge. As soon as I plugged it in, the power sequence started and the phone booted and ran fine. I pushed the battery connector back into place and all was good, except the problem of what happens if I power it off.
I went to developer options, checked USB debugging, and powered off, confident that even if I still couldn't see it in charging mode, I'd at least be able to manually power it on after disconnecting the battery. Well, of course, the second time it didn't work. ADB was still unauthorized, and the battery disconnection trick didn't work, it started to boot but then appeared to lose power and the screen faded. This gave me a clue that it might be possible to use the wireless charging to get it to boot, but the problem with that was that it wouldn't wirelessly charge with the battery disconnected. In the end, what worked was to loosely hold the battery connector with my finger over the contacts, while holding the phone against the wireless charger (I have the Xiaomi 65W wireless charger), in this state the battery reads 15% even though it's full, but the phone boots. I then pushed down to fully connect the battery, at which point it read 100% and was booted. It's super-fiddly to hold it all in the right position, but perseverance pays off. If you lose the connection to the battery completely at any point, the phone simply dies.
To get to the battery connection on the Mi 9 Pro, lift the wireless pad, at the top right corner of the battery you'll see a short flat black cable that runs towards the centre of the battery and then up to connect to the motherboard. Lift up on that connector with something thin to pop it off. When rebooting, hold your index finger on the connector with enough pressure to make a contact without fully reconnecting it, while holding the wireless pad against the charger. Why the hell this works I have no idea, but it does.
To operate the volume/power, just download widgets. It would be nice to have a physical volume button, but doing it from the screen works.
This was a life-saver for me because I friggin' love this phone. I have the 12/512 model, and it's so good I've finally stopped fiddling with ROMS because it just works perfectly. Unfortunately, it took me a week to figure this out, and I ordered a Mi 11 Pro in the meantime!
If anyone has any good ideas about an easier way for me to reboot in case it ever powers off (a simple reboot is fine), I'm all ears. I'm currently looking at having to remove the rear cover again and go through the whole rigmarole if it ever powers off.