Related
Let me give you the run down. I recently bricked my phone trying a 2.3.320 SBF update which got stuck on the M logo. I followed steps as on rootzwiki and got my phone working again, with the new 2.3.320 update. I backed up my cricket APN so the reflash wasn't to bad. I use Droid Overclock at low volts running 1.2Ghz. I have done so for months...never had an issue....ran smooth and fast.
After the new SBF update and re-rooting and running my usual overclock settings, my phone got a lil warmer then usual. I was removing bloat at this point, nothing else. I could not get it to boot into the homescreen...I thought this was unusual as I did not delete any important files ( just bloat ). So, I restarted it, so I thought.
I can not even get it to turn on and after several hours on the charger, It will not turn on! I can get into bootloader but all it states is
Batter Low
Cannot Program
When it's plugged into the USB on my computer, the LED light turns solid green and stays green unless I unplug it. I can not turn it on nor boot into recovery. Only thing I can do is load bootloader and get that exact same message everytime.
My phone is in mint condition. Nothing less then perfect....until today, until I loaded the new 2.3.320 using RSD Lite. Whats going on with my phone? Is it a goner? I will be heading to the VZW store for a brand new battery but I don't think it is the case.
Ideas? Anyone? Sad, sad day for my X...
I think the problem may be that you accidently removed the files necessary for it to charge. If you knew someone else that had the same phone, you could try charging your battery in his phone. That could possibly work.
It had 70% charge when I turned it off to reboot it the first time.
Wierdest thing, as I was reading your post...CWM just started up out of no where and out of excitment, I grabbed my phone and hit the camera button on accident and it rebooted, past the M logo but got stuck on the Droid animation! I had my chance to flash it back to a working nandroid and missed it.
Something wierd is going on here...
If you pull the battery, put it in, then plug it in you should go right to CWM. Keep playing with it until you make it in. I know my phone won't boot up (dead battery), but still gets to CWM.
Might have to jump start it
If the battery is too dead you'll either have to borrow a battery or cut a USB cable to 'jump start' it. I found a post with pictures on how to do it for mine, or look for one of my old posts where I describe it a little.
Use the wall charger. I have the same problem except when my phones dead it wont charge over a computer USB cause its not getting the correct voltage for it to charge. Try that if that's not the case then use another battery and sbf.
Sent from my DROIDX using XDA App
not boot looping, just nothing at all. The phone won't power on.
The battery ran completely out, but now, after charging it overnight, it will not power on at all. I've seen various threads saying to take the battery out for 30 min or so, try pulling the battery & SD card WHILE it's plugged into the charger, try booting it with no battery at all (just charger), and all of them state to use the wall charger, as being in a PC USB port won't be enough.
I've tried everything, but nada.
My phone is/was running the rooted gingerblur leak, which I installed correctly by SBFing first beforehand and doing a total wipe. I honestly didn't even bother reinstalling very many apps, I've been so busy at work over spring break. The phone HAD been shut down and restarted a few times since flashing the gingerblur, so this wasn't the first time it rebooted since then or anything.
Had a few force closes and random reboots over the time on gingerblur, and was actually not that excited about it, but now I'm stuck with a brick it looks like.... any ideas?
I had the same problem on mine it would stay at the boot logo and wouldnt go past that I called Verizon and they are sending me a replacement.
tyvallely said:
I had the same problem on mine it would stay at the boot logo...
Click to expand...
Click to collapse
Mine doesn't do *anything*... no boot logo, no nothing.
just got back from verizon with a new battery, works fine again... just posting as a followup. I thought it would be odd that even with a dead battery in the unit, it wouldn't power on with the wall charger attached, but with a new battery (got the extended one while I was at it) it works fine again.
another update: ate thru that battery, and died again. Recharging the new battery does nothing. Mine seems to have a hardware failure in general that it won't recharge batteries at all. New batteries come with some juice in them, but once that's gone it's gone.
Bought one more battery just to SBF it back to vanilla before I send it in for warranty service. Will keep this thread posted just in case anyone else runs into this... I hate finding threads with problems that just trail off with no resolution.
I'm not sure if they intended the DX to work like this, or whatever; but if my battery runs completely dead, the phone cannot charge it. I get the same green light you do, annnnd nothing when I try to power on.
What I have done to solve this in the past was to cut open the cable for either a 5v power supply or a usb cable. Either tape off the unused wires or be seriously careful not to go crossing wires, plug the charger in, and touch the appropriate cables to the battery terminals, (battery out of the phone). About a minute is all it takes to give it enough juice to charge in the phone with a standard charger.
Someone else posted a more in dept guide on this process, if you are unsure of any steps, please search for that rather than causing damage.
Not my fault if something bad happens from anyone following this; however, I have done this numerous times with zero issues.
happened to me twice and each time verizon replaces just after hearing the symptom. must be hw failure
LIH said:
happened to me twice and each time verizon replaces just after hearing the symptom. must be hw failure
Click to expand...
Click to collapse
Replaces Battery or phone?
yeah, final post on this, but Verizon is sending me a replacement phone. I've had the DX since launch, and this will be my third one, but they've always been good about sucking it up and just sending me a new one free of charge.
I bought two replacement batteries in total (which were both returned) -- one thinking that it was just a bad battery and another when it became apparent that wasn't the fix. I thought I'd be sending it to motorola for warranty, and wanted to flash the SBF back on to return it to vanilla.
Anyway, long story short: if you found this thread because you're having the same issues, just buy another battery, flash it back to stock, and take it in for replacement. Then you can return the battery.
Cheers.
I need help. I messed up my Droid 2 restoring a backup and the battery died during SBF. So I did the Macgiver trick where you connect an old stripped usb wire to the battery so that the phone can be tricked into booting up and being flashed. Since then I've had a question mark in my battery icon. It wont read that battery or the battery that I've just purchased and I get the "Invalid Battery" message and the battery wont charge in the phone. Both batteries are official Motorola. I can't send the phone back as its not under warranty. So I have a few questions.
Is the some sort of workaround/ fix for this? Motorola put software on the Droid 2 since Froyo that reads whether or not a battery is official Motorola product. Can the battery software be hacked/ deleted so that I can use my battery as normal?
Wow, we have this same exact situation like a month ago, and since then my fiancee still uses her broken phone . We did the Macgyver trick also and we got the battery with the question mark. We even bought a new battery and it still shows it, tried reflashing with a fully charged battery and nothing changed. We also tried clearing battery stats none of it is working. If anyone knows anything about this problem please let us know. If you get an answer that cures your phone please please please let us know about it. I actually posted your question on Yahoo! Answers since it was the same exact problem that we had and if anyone answers we will post the reply on here.
Thanks a lot and good luck!
I've got the exact same problem. All I did was purchase one of those external chargers so that one battery is always charged. It is annoying, yes, but its not too bad. I'm also looking forward to see if there is a solution, but I doubt it. We probably all fried the contacts on the phone, but we'll see.
Sent from my DROID2 using XDA App
hey, yeah we did the same thing, we bought the second battery yesterday but i have a question, did you try flashing it again with the new battery in? I was wondering if it would work but i want to see if it will before clearing one more time my fiancee's cellphone since theres a fish game that may be lost if we do that.
Thanks a lot.
Brandon
I've SBF'd multiple times since then, and the question mark is still there. I don't think theres a way around it, unfortunately. Personally, it's not really a big deal, but it may be for you.
I just really hate it because I have no clue when my battery dies.
Never had the issue, but one thing comes to mind..why not root, install clockwork recovery and then clear the battery cache?
jediman said:
Never had the issue, but one thing comes to mind..why not root, install clockwork recovery and then clear the battery cache?
Click to expand...
Click to collapse
They said they already tried that.
What exactly is this Macgiver trick? If you have a link, or some info on how it's I might be able to shed some light on this for you guys
The D2 battery is 3.7 volts; USB is 5. You probably blew out the A/D channel used to measure battery level.
Smartzkid said:
The D2 battery is 3.7 volts; USB is 5. You probably blew out the A/D channel used to measure battery level.
Click to expand...
Click to collapse
Ah, I see so they're hooking up the USB straight to the phone...found it after a little searching...
But i'm curious, wouldn't that only happen if the wires ended up touching the other two terminals, and not just the outer (+) and (-) ones?
Will getting a new oem battery work?
No, replacing the battery will not work if you messed up when connecting the spliced USB charger + and - to the wrong terminals in the phone.
I have exactly same problem. I sliced the usb cable to revive my Droid X when the battery died during sbfing. Now my phone survived but Im stuck with question mark on battery icon. I flashed reflahsed and flashed again but no luck. wiped batt stat but no luck. Tried new OEM battery, no luck.. Put the batt in the freezer for 10min but no luck. I ran out of all the possible solution.
Now I just got the external stand along batt charger from ebay with 2 extra batts. I just carry extra battery since I dont know when the phone will go dead..
I would love to find out if someone can fix this issue. I still got 6 mo to go before I can upgrade.
I HAVE A SOLUTION (worked for me):
When doing the "Macgyver Hack", I jammed the USB wires into the battery. This pushed the metal spring terminals out. After that, the battery terminal springs don't all touch the connectors in the phone.
Take a needle, and carefully pull the battery's metal springs toward each other.
This worked for me.
Also, try this:
Remove battery and unplug phone. Plug phone in (without battery), then turn on (some phones will turn on without a battery). After the logo comes up, insert the battery. This made my phone recognize the battery and get into the OS.
Once the battery is recognized and you can boot to the OS, root the phone and get the battery calibration app (and use it).
I have a Motorola Defy, and used the Macgyver hack, then had the question mark problem for days before figuring this out.
jodaboda, Thank you a ton for that. I've been searching and trying out things to fix this and this is the closest I've come.
Although the Droid 2 doesn't boot up without a battery, I've had to the Macgyver Hack to get it to boot. The battery calibration app reads 100% charged when I am using the Macgyver Hack and is showing that the battery is charging. I'll tell you if it works once my battery is charged and I calibrate.
I wasn't able to get it to work. I think there is potential but my phone eventually died and it wasn't able to fix it. That app can measure the volts correctly tho, which means we should be able to get the battery working again somehow.
jodaboda said:
I HAVE A SOLUTION (worked for me):
When doing the "Macgyver Hack", I jammed the USB wires into the battery. This pushed the metal spring terminals out. After that, the battery terminal springs don't all touch the connectors in the phone.
Take a needle, and carefully pull the battery's metal springs toward each other.
This worked for me.
Also, try this:
Remove battery and unplug phone. Plug phone in (without battery), then turn on (some phones will turn on without a battery). After the logo comes up, insert the battery. This made my phone recognize the battery and get into the OS.
Once the battery is recognized and you can boot to the OS, root the phone and get the battery calibration app (and use it).
I have a Motorola Defy, and used the Macgyver hack, then had the question mark problem for days before figuring this out.
Click to expand...
Click to collapse
I don't have a nan back up from recovery but have read on another thread that you can also fix this by doing a restore of a back up through the recovery from a time before you have had the battery ? issue.. several people have also mentioned that it worked for them.. in my case I don't have a back up before this issue so I cannot confirm.
my phone died noooo
bumping in case anyone has a solution?
please. pretty please.
tried methods above, phone wont boot unless plugged in... i don't care i can't tell what % its at, but i do care it wont boot off battery power.
Tried 2 Ways with no Luck.
1. Power button + volume button down Long press less than a min. ?
2. Plug in for a day or more. ?
Gotto try jadaboda's tip.
Theheroitsme said:
Tried 2 Ways with no Luck.
1. Power button + volume button down Long press less than a min. ?
2. Plug in for a day or more. ?
Gotto try jadaboda's tip.
Click to expand...
Click to collapse
try a fastboot cable or a spare battery charger
sd_shadow's [Collection] of Links for:
Droid 2 (a955)
Sent from my XT1254 using XDA Labs
Hello,
I know, there are several threads about this issue, and I checked them all, tried all what they wrote, still nothing changed.
Yesterday I've installed KitKat on my mobile. I've tested it for an hour than installed CM 10.1.3 back. At first, I had no Wi-fi, neither for second try. I read that I need to flash a modem.zip to fix that. So I did that, reinstalled CM again and on system reboot, my phone didn't turn back on.
I doubt its battery issue cause it was on charger and was around 74% (after I couldn't do anything, I left my Nexus on charge whole night, but nothing changed).
The red light appears when the phone is plugged and I press the buttons for 15/60 secs, than fades after few seconds.
Have you got any idea? I can't enter recovery, nothing at all.
After trying every solution - and when I say every, I mean that all possibilities found over the whole internet - the only thing I could do is giving a call Google support. Since I bought my phone in SF, my warranty is up only there (and I live in Hungary).
Luckily, they send me a new one, but only to an US address, else I should call LG for help.
About the issue:
the red light - also called as the red light of death - is a known Android bug. The OS it self lowers the battery's strength, so the phone gets a very few energy which causes that you are not able to turn on the device. When I mentioned this red light thingy to the support, she only said "ahh, that..." and asked me if I want a new Nexus 4 or I want my money back.
Sounds like your phone is bricked.
Generally Google/LG is fine with rooted phones, at least in my case. I'd give It back and get a new phone.
Sent from my Nexus 4 using Tapatalk
So what you say is that after you flashed the Modem fix zip your phone went into red light mode?
Maybe you flashed a wrong zip file, which bricked your device? What zip file did you flash?
I fixed mine. You must be plugged in to a charger. Turn off. Which it should be already. Then press power button for long enough go the red light to turn green. Then yank off the USB. The phone thinks its out of juice. It is and does happen. But I got mine working this way. Timing is key.
Sent from my Nexus 4 using xda app-developers app
leave it on the charger for a while.
but, the only 100% method to get your phone back is to take the back off, remove the battery, then plug the battery back in. the "resets" your battery. this would be a normal battery pull for a device with a removable battery, but since the n4 doesnt have a removable battery..
Guys, I've tried all these and nothing helped. It happened a week ago, so the battery had time to go on 0%, I've charged it and still no life signals... I even removed the battery - nothing.
Meanwhile, Google decided to screw me up, so we keep trying to resurrect the phone...
About the modem.zip: doubt it was a bad zip, cause others used it before me also. I had a bad luck, happens...
Google shows me I'm not even remotely alone in my trouble, but with the way tech works every problem is at least a little unique. I'll give a rundown of what I've down and whats happened up to this point.
First, I bought it used from Amazon. Very Good condition from a seller with 99% or whatever satisfaction. I think I've bought from them before, actually. So while this isn't a new device, I know I wasn't scammed. It was also factory reset and I'm assuming it wasn't rooted, though admittedly I have no idea how to check on a Nook.
Second, when it arrived the first thing I did, naturally, was turn it on. Plugged in the Nook to my computer, it booted up just fine, I registered, and loaded one a few ebooks with Calibre. The books opened up, they looked great, we were golden.That was when I noticed the battery indicator in the top didn't have a number on it. It was solid black with a ?. I thought that was weird, so I tried rebooting the device. That was when I was hit with an update, it downloaded and installed then rebooted. Here's when it all went to crap.
Third, I can get into the device. If I hold the power button and wait a bit it takes me to the homescreen where I'm met with a 0% Battery warning saying to plug it in or the device will shut off. Waiting for this message do disappear seems to give me normal access to the device, except the battery indicator is still just ?. This still happens now, after about 10 hours of charging.
Fourth, plugging in the device to anything be it wall charger or computer causes the device to reboot back to the Read Forever screen. Even if the device is completely powered off. It just hangs at the boot screen and goes nowhere. If I hold down the power button, or power + n, all it does is flash the screen to blank and then goes back to the boot screen. If I unplug it and hold down power it goes back to the previous problem.
That's everything I know. I seem to have the proper Nook micro USB cable, but the adapter is a little white Chinese looking thing so I know it's not the official. So I've switched to my Nexus 5's micro USB cable since I know it works and plugged it into my PC. The charging indicator is on, but thanks to my minor colour blindess I'm having a hell of a time deciding if it's orange or green. It's either green, orange, or yellow for sure though. Right now I'm going to go to sleep, let it charge through the night. I've had a similar problem happen to my Nexus 7 where it wouldn't turn on, and a nightlong charge seemed to fix it so who knows, this thread might be useless in the morning.
In the more likely event that it's still very useful, any help would be appreciated. And please try to keep it simple. I'm not new to technology or Android in phone/tablet form and all the associated hairpulling, but this is literally the first time I've ever dealt with an ereader. I'd like to get this solved at home, since I don't have a warranty and the price to ship this thing back to the seller would make this end up costing more than a new one would have since I'm Canadian and the seller isn't.
Thanks in advance.
Edit: After a night of charging, still 0%.
This, unfortunately, is the sign of a factory buggy (for lack of a better word) device. I doubt there's any hope. Sorry about that.
Keep me updated.
I think that there might be software to blame. My Motorola Defy also had that sort of weird battery behaviour after one of factory resets. Since then I have to install a patch written by one of XDA members every time I make a reset. But it works. Unfortunately I have no idea if it can be helpful in this case. (I'm refering to this post: http://forum.xda-developers.com/showpost.php?p=34590229&postcount=1 )
Nonetheless I would seek some slight hope in disconnecting and reconnecting the battery.
Alright, so. Progress report:
I tried the 8 failed boots trick to reset the device back to the original firmware. This brought me back to square one. The device worked, I could load books on to it via USB, and read them. But the battery indicator was just a question mark. Going into the settings revealed that the battery was at 100%, or at least claimed to be. But hey, I could read on it so I figured I was alright.
Now, a couple days later, I just woke up to find it with a new problem. Pressing the little N button to wake it up isn't doing anything. It won't respond to holding the power button down and my computer wont pick it up when it is plugged in. The charging light still comes on but I don't know how much it can be trusted.
I'm going to let it charge for a bit, but I'm beginning to think the battery is just toast.
Shodex said:
Alright, so. Progress report:
I tried the 8 failed boots trick to reset the device back to the original firmware. This brought me back to square one. The device worked, I could load books on to it via USB, and read them. But the battery indicator was just a question mark. Going into the settings revealed that the battery was at 100%, or at least claimed to be. But hey, I could read on it so I figured I was alright.
Now, a couple days later, I just woke up to find it with a new problem. Pressing the little N button to wake it up isn't doing anything. It won't respond to holding the power button down and my computer wont pick it up when it is plugged in. The charging light still comes on but I don't know how much it can be trusted.
I'm going to let it charge for a bit, but I'm beginning to think the battery is just toast.
Click to expand...
Click to collapse
Hi, I just went through something similar 48 hrs ago. The NST is frozen, stuck at reading forever. Before that, the battery icon had a '?', and the device info said battery status was "unavailable". Plugging in to charge had a solid green light.
I read around, and what worked was to open the case, and disconnect the battery. Google said to wait 30 mins, I waited 1. Re plugged in, put it to charge. The LED turned to orange, and 15 mins later, the NST booted. All good now.
Total cost: set of TORX scredrivers (you need a T5).
ghane0 said:
Hi, I just went through something similar 48 hrs ago. The NST is frozen, stuck at reading forever. Before that, the battery icon had a '?', and the device info said battery status was "unavailable". Plugging in to charge had a solid green light.
I read around, and what worked was to open the case, and disconnect the battery. Google said to wait 30 mins, I waited 1. Re plugged in, put it to charge. The LED turned to orange, and 15 mins later, the NST booted. All good now.
Total cost: set of TORX scredrivers (you need a T5).
Click to expand...
Click to collapse
Okay, so. No T5 but I managed it with a teensy weensy flathead. Unlugged the battery, left it that way for about 20 minutes, plugged it back in, then left it to charge. 15 minutes later I came back and viola, it works and the battery is reporting it's remaining juice. Thank you very much, that seems to have done the trick.
You know, this might be the first time I ever managed to have a tech problem solved entirely by a forum.
Shodex said:
Okay, so. No T5 but I managed it with a teensy weensy flathead.
Click to expand...
Click to collapse
You realise that that voids the warranty you get from XDA?
Shodex said:
You know, this might be the first time I ever managed to have a tech problem solved entirely by a forum.
Click to expand...
Click to collapse
I knew the Internet would be useful for something, one day
ghane0 said:
You realise that that voids the warranty you get from XDA?
Click to expand...
Click to collapse
It's a used device, there was never a warranty.
Looks like the problem is fixed. Great! Sorry I was inactive.
Later!