Related
Hi, yesterday I installed CM7 on my android, all went well, very awesome.
Soon the LED Light messed up when I would plug the phone in via usb.
The LED had colors that were like mixed and all.
Searched on Google, and found nothing... So I then did the whole process over (wiped data...) And near the last step I wiped data instead of wiping cache.
It was like 5 in the am and I got sleepy so when I restarted the phone(Of course it would take a while), I went to lie down, then fell asleep. Woke up and my phone was still at the Motorola Logo screen. I also seen that I forgot to put it on the charger before went to sleep.
Long story short, My phone won't get past the logo screen, I would try to go back to 2.2 sbf but when I get into the bootloader screen the battery low cannot program.. error comes up.
Yeah, I explained practically everything..
What can I do to get it back to normal, so I can get CM7 back?
I only got to enjoy 20 minutes of the rom...
My phone: Motorola Bravo
Service: AT&T
You need to charge your battery some how? Does it charge at all
Do you know someone with phone?
If not ask for a battery replacement from at&t store and hope it has enough charge
Sent from my MB525 using XDA App
rdannar said:
You need to charge your battery some how? Does it charge at all
Do you know someone with phone?
If not ask for a battery replacement from at&t store and hope it has enough charge
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
My thought on charging was when the phone is off and you charge it, it goes to the charging screen, then eventually the display turns off.
Instead of that, it just stays at the Motorola Logo screen..
I've also had it on the charger for about 4 hours now. Still remaining at the logo screen, BUT it has also gotten warm..Maybe that means its charging? (right??)
2. Since I've moved, nope. Don't know anyone that has this phone and is near me.
3. Battery Replacement. It's 1am here so, I guess I'll just keep it on the charge till the morningmorning..
I could do the bootloader sbf back to froyo thing but since the phone's battery is dead to the max, I get the error, meaning I can't do that option.
I'll call my local AT&T store to see if I could get a battery replacement if I can't get it to turn on to at least the Recovery or bootloader.
Pain.. pain in my brain.
try to get it plugged in w/ no logo, to ensure it's off off... if not you might have to let it sit off the charger till it's dead enough that it doesn't try to boot...
i think it's trying to boot, but boot looping and not aquiring enough of a charge,
do you have it on a wall charger? make sure it's like 800 mah or higher, i think the phone comes with a 5.1v 800mah which was weird to me tha tit was 5.1 cause all other phones are 5.0 but anyway maybe you're not getting enough of a current to it to overcome the drain from the bootloop?
Are you able to get into custom recovery? (Do you see the blue LED at any point when the phone begins to try to power on?)
You have soft bricked your phone, so the only way to get it working is to sbf back to 2.2. The problem is, the bootloader doesn't allow you to sbf if your battery is below a certain point. You need to either get that battery charged or get a new one.
If you can't get anything at your store, I will cross-ship/trade you a charged battery (1 year old) for your current one and $3 for shipping? Let me know if you'd be interested in something like that...
I also bought a battery from Amazon (OEMShop or something), and I think it came 40%ish charged... You could try your luck?
Just so you understand the charging, Android uses the OS to monitor the charging. If the phone is bricked it doesn't charge… plain and simple. It sucks if you try to sbf after the battery is drained, but the only thing you can do is get another one. Hope your search for one comes up well.
Sent from my MB525 using XDA App
dontbejeff said:
Just so you understand the charging, Android uses the OS to monitor the charging. If the phone is bricked it doesn't charge… plain and simple. It sucks if you try to sbf after the battery is drained, but the only thing you can do is get another one. Hope your search for one comes up well.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yeah..no.. I'll be getting a replacement phone (same one). Basically in 4 to 6 days..
I'm so happy, my phone kept restarting anyway when using data.. But yeah, thanks though.
Before you send other phone back... sbf with other battery back to stock.
AndroidRocksSocks said:
Yeah..no.. I'll be getting a replacement phone (same one). Basically in 4 to 6 days..
I'm so happy, my phone kept restarting anyway when using data.. But yeah, thanks though.
Click to expand...
Click to collapse
Sent from my MB525 using XDA App
rdannar said:
Before you send other phone back... sbf with other battery back to stock.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yeah, I thought of that when I got of the phone with them. Thanks for the heads up though!
My replacement phone came in the mail earlier this afternoon! Thanks for all the help you guys. Glad I came here. So excited, just 10% more and it's fully charged.
I think I may get a extra battery just in case for my phone. Great post!
This just happened to me too. I thought what to do...
Spliced one of my old car phone chargers and hooked it to my phone battery... plugged it into my car fir 5 minutes and was charged enough to sbf.
Don't recommend it if you don't know what your doing
Cheers
Sent from my MB525 using XDA App
rubbachicken said:
try to get it plugged in w/ no logo, to ensure it's off off... if not you might have to let it sit off the charger till it's dead enough that it doesn't try to boot...
i think it's trying to boot, but boot looping and not aquiring enough of a charge,
do you have it on a wall charger? make sure it's like 800 mah or higher, i think the phone comes with a 5.1v 800mah which was weird to me tha tit was 5.1 cause all other phones are 5.0 but anyway maybe you're not getting enough of a current to it to overcome the drain from the bootloop?
Are you able to get into custom recovery? (Do you see the blue LED at any point when the phone begins to try to power on?)
Click to expand...
Click to collapse
Volume up... not down... got it
I have been using a new ICS build and wanted to warn everyone about the shutdown problems. It seems that by choosing to shut down by pushing the button and choosing "shut down" leaves the backlight running (you can see it if you look).
This has drained my battery down to nothing preventing my Kindle from booting. The stock charger did nothing, no charge, no light, no boot. Plugging in to the PC made the Kindle come on, but reboot after a couple seconds, not long enough for me to even get into recovery mode.
On a hunch I used my phone charger. Not only did the Kindle kick on and boot, but it seems to be slowly charging. I restored back to the stock ROM and now it seems like the stock charger has no effect at all.
Just be careful and be aware that the back light will stay on for now until the kernel is updated.
Thanks!
Sent from my Kindle Fire using xda premium
It happened to me already, but it woke up with the original charger.
Thanks!
yeah two known bugs for the 3.0 kernal are usb wall charging and the device not shutting all the way off (backlight stays on). if you need to you can always go into recovery to charge up. also turning lockscreen and touch sounds off in settings>sound will help save battery
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
This just happened to me...
My kindle died after shutting down for one day. No battery at all...
Did you even read the first post of the kernel thread?
ryanhuong said:
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
Click to expand...
Click to collapse
Something for the volume control:
https://play.google.com/store/apps/details?id=rubberbigpepper.VolumeControl
Back to OP, I used to hold power until the backlight would turn off (about 15sec) but one day it just so happened that my kindle did not turn off completely even then. After that I have been holding it down for a straight 20sec.
Sent from my Amazon Kindle Fire using XDA
StaticMatt said:
Did you even read the first post of the kernel thread?
Click to expand...
Click to collapse
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
If the devs were offered a dime every time somebody failed to follow directions...
Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Not going to argue with you on that one.
ryanhuong said:
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Click to expand...
Click to collapse
You do see the irony in all that, right?
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
umash4 said:
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
Click to expand...
Click to collapse
With the newest kernel yes it seems to charge fine. The Pure AOKP build seemed to have more issues. Now I am using the newer AOKP and not does the charger work again, but the LED now shows orange or green (but the battery icon s still wrong).
Huge improvements so far.
This happened a few times with my Optimus V. This was because there was no offline charging support for AOSP ROMs at the time. The only way I could get the phone to stay on was to force the battery into a LG Rumor Touch and recharge it with that until the battery could boot the Optimus. Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
I know the AOKP ROMs fully power off the device. So at least I'm okay with that.
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Sent from my Amazon Kindle Fire using Tapatalk 2
It will always work best with the stock charger, but until the bugs are fixed, who knows.
KemikalElite said:
Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
Click to expand...
Click to collapse
It does charge offline, the problem lies in the LED not reporting this properly (it doesn't turn on to reflect the charge status).
KemikalElite said:
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Click to expand...
Click to collapse
This is normal, as they usually provide less amps than the stock charger (1.8).
For what it's worth, I am on #33 AOKP KF Edition and the LED works perfectly. It's the icons that don't work right.
EDIT: I take that back. If the KF is asleep and you plug it in the LED stays dark. If the tablet is awake and you connect the charger, the orange comes on, putting the tablet to sleep the LED stays orange till it turns green when full.
Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
Actually as one of the guys that's working on the kernel I would have to say you're incorrect. Wall charging does in fact work. The issue with the led is that the kernel doesn't correctly update it, as well as it doesn't update the from in a manner for the icon to change. If you download a battery widget in the market you will see that it does in fact charge with a wall charger. This is also a better route to go since the OEM charger puts out about 1000mv as opposed to 100mv w/USB 1.0 or 500mv w/USB 2.0. Only other steady charging scenario would be USB 3.0 because its output is 900mv.
Sent from my MB860 using XDA
All was well untill i was off on holiday for a week. I had kept my nexus 7 on standby ti check how the battery fairs. Anyway, while using it, it suddenly switched off at 14% battery. I then charged it to 100% and started using it.
After using it for 30mins there was no change in battery % n it still showed 100% ( weird i know ). Eventually it started depleting as normal until it got down to 14% n shutdown. Then it wouldn't charge when plugged in anywhere, had to press the power button foe 30sec or more for it to boot up again.
Now my question is, Is there a way to fix the faulty battery indication without rooting the device? (And i know you all will be thinking of suggesting a factort reset, but i don't want to lose my gaming progress).
Any suggestions will be helpful.
Thanks.
Sent from my MB525 using xda premium
I have had a few N7 that exhibit this behavior. Also haven't figured out a way to fix it either, I exchanged the early ones I had and the C8 I have now goes at 8% as well and to avoid it, I just charge before it hits 20%. I know its not a fix and now that I've flashed the new 4.1.2 I am waiting to run it thru a charge to see if maybe it was a bug with JRO03D.
Here are a few threads I've posted in where I've seen people talk about the same thing, nobody actually knows or has posted a fix other than to exchange and hope the new one doesn't do it:
http://forum.xda-developers.com/showthread.php?t=1798756
http://forum.xda-developers.com/showthread.php?t=1798054
http://forum.xda-developers.com/showthread.php?t=1797126
Hi All,
I was browsing the web a couple of hours ago and my N10's screen started flashing on/off and after around 10secs the thing crashed/turned itself off. Being an N10 this was not an unusual event! However when I try to turn it back on nothing happens. I can hold the power button / power button with volume buttons pressed and nothing happens. If I plug it in to charge I do not get even get a charging icon.
If it makes any difference I was running the latest Rasaber with Franco's r11 kernel and I know I had at least 40% battery left when it died. I have left it plugged in to the stock charger for around an hour hoping that something might happen but still nothing.
Has anyone ever experienced anything like this?
There was not a sad enough looking Emoticon to convey my sadness over the possibility my lovely Manta is dead......
no man ... it s impossible . nexus 10 its the best device ever . acording to some gurus here
your device its dead . now you have to stay on your knees to google replace it . good luck
Sent from my Nexus 10 using xda app-developers app
Something similar happened to me but I'm totally stock. I Googled and the solution was to recharge the unit via my PC USB instead of plugging it into an outlet. I have no idea what happened but after a few hours of being connected to my PC it was back and working. Hope that helps.
I'm running the same rom and kernel combo. No problems or anything weird happened. It must be hardware related.
Did you try the holding-the-power-button-for-a-minute routine?
I would try to leave it plugged in on the charger for a while and see if it gets fixed. That usually solves all sorts of "wont turn on" problems
samwheat said:
no man ... it s impossible . nexus 10 its the best device ever . acording to some gurus here
your device its dead . now you have to stay on your knees to google replace it . good luck
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
You seem upset
i seem realistic
another nexus 10 with problems
Sent from my Nexus 10 using xda app-developers app
is it possible for the tablet to get overheated?
I have had that happen on stock.
My theory: it is linked to the 'battery status not updating'-bug. Your Nexus thinks the tank is still half full, while in fact you are running on fumes. It does not realize this, so no dimming of screen, no low power warning, it just goes full steam ahead, until the battery is totally and utterly and completely depleted.
Then, obviously, it won't start but it will also have trouble charging. You need to charge it for quite some time, sometimes try a different charger, and sometimes keep the power button depressed for a full minute for it to come back to life.
Now when I use my Nexus, I keep an eye on the battery status. If it does not go down, I know I need to reboot for the battery status to be read properly again. It is a bit of a bother, but not too much. The bug only kicks in after the tab has been lying around for a while sleeping. So if I want to watch a movie, I first reboot. As long as I keep using the tab (i.e.watching the movie), the bug won't 'activate' and the tab will shut off properly when it senses the battery is low, in stead of continuing and deep depleting the battery.
Sent from my Nexus 10 using XDA Premium HD app
A few weeks ago, i flashed a stock rom on my wifi nexus. I was happy with it until last week. Charging became incredibly slow - 30% over 8 hours. I threw it in my bag and wheb i got home 8 hours later, the battery was depleted completely. I couldn't turn it on. I plugged it in over night and it stayed at zero percent. I booted into recovery and reflashed my stock rom abd wiped my data. Still didn't charge. I tried going into my bootloader and hitting power off and then plugging in, but it still wouldn't charge. I can't flash my backup because it's on my card that i lost, and even if i had it, i wouldn't be able to keep it on long enough to flash it. ADB won't run on my pc and i don't know how to use the program anyway. What can i do to save my device? Please help.....
Sent from my YP-G1 using xda app-developers app
Replace battery?
veeman said:
Replace battery?
Click to expand...
Click to collapse
Not the average flasher knows how to tear apart a device - including myself. Anyways, this thing won't power up at all? You tried leaving it plugged in and booted into bootloader? If so, sounds like a hardware issue or the battery is defective.
I would be willing to bet that your battery connection came loose. Start at your USB port with a thin piece of plastic, such as a guitar pic. Work your way around the device and remove the back.
Sent from my Nexus 7 using xda app-developers app
DroidOnRoids said:
Not the average flasher knows how to tear apart a device - including myself. Anyways, this thing won't power up at all? You tried leaving it plugged in and booted into bootloader? If so, sounds like a hardware issue or the battery is defective.
Click to expand...
Click to collapse
It's not too difficult. iFixit has a good tutorial on it. http://www.ifixit.com/Guide/Installing+Nexus+7+Battery/9895/1
happyjack96 said:
A few weeks ago, i flashed a stock rom on my wifi nexus. I was happy with it until last week. Charging became incredibly slow - 30% over 8 hours. I threw it in my bag and wheb i got home 8 hours later, the battery was depleted completely. I couldn't turn it on. I plugged it in over night and it stayed at zero percent. I booted into recovery and reflashed my stock rom abd wiped my data. Still didn't charge. I tried going into my bootloader and hitting power off and then plugging in, but it still wouldn't charge. I can't flash my backup because it's on my card that i lost, and even if i had it, i wouldn't be able to keep it on long enough to flash it. ADB won't run on my pc and i don't know how to use the program anyway. What can i do to save my device? Please help.....
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
Sounds like my device... only I even can't get into the bootloader nothing... Someone suggested that the battery got so far depleted that it will nor recharge.
However seems you at least can run the bootloader... for me it just stays black ..... nothing nopes nadda
dkd2625 said:
Sounds like my device... only I even can't get into the bootloader nothing... Someone suggested that the battery got so far depleted that it will nor recharge.
However seems you at least can run the bootloader... for me it just stays black ..... nothing nopes nadda
Click to expand...
Click to collapse
Actually, there's a sticky for these issues haha
N7 Turns Off/Won't Turn Back On/Battery Status Issues - The Fixes **UPDATE**...
---------- Post added at 11:28 AM ---------- Previous post was at 11:27 AM ----------
veeman said:
It's not too difficult. iFixit has a good tutorial on it. http://www.ifixit.com/Guide/Installing+Nexus+7+Battery/9895/1
Click to expand...
Click to collapse
I heard that was a good site. I'm more scared of screwing up any hardware than doing the actually tearing apart.
I can boot for like 30 seconds and then it shuts off. I've tried the solutions in the thread link above; however, i still think it is a software issue. I've used other roms that had really slow charging, but i was able to switch to another one before the battery got depleted. So i think my best bet is to somehow get a new rom on my device somehow. ADB won't run on my computer. It just flashes a command prompt on the screen for like half a second and closes.
Sent from my YP-G1 using xda app-developers app
happyjack96 said:
I can boot for like 30 seconds and then it shuts off. I've tried the solutions in the thread link above; however, i still think it is a software issue. I've used other roms that had really slow charging, but i was able to switch to another one before the battery got depleted. So i think my best bet is to somehow get a new rom on my device somehow. ADB won't run on my computer. It just flashes a command prompt on the screen for like half a second and closes.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
What kernel are you on? The kernel is what does the charging operations.
happyjack96 said:
I can boot for like 30 seconds and then it shuts off. I've tried the solutions in the thread link above; however, i still think it is a software issue. I've used other roms that had really slow charging, but i was able to switch to another one before the battery got depleted. So i think my best bet is to somehow get a new rom on my device somehow. ADB won't run on my computer. It just flashes a command prompt on the screen for like half a second and closes.
Click to expand...
Click to collapse
I had a similar situation in that after the battery died, I got it to the point where I could boot up, but after a screen timeout, it would be dead again. Finally, I got it booted again (while plugged into power) and immediately went to developer options and checked the Stay Awake, never sleep while charging. Keeping the screen awake kept the N7 on and it charged up.
Funny my Galaxy Nexus started doing this crap on me too after I updated the rom and kernel. The phone and battery are only 2 months old replaced in April.
Occasionally it won't take a charge. I have to **** with the battery, removing it several times. Then all of a sudden it starts charging again after 10-15 resets.
Haven't had a problem in a while. Typically hits me like every 2 weeks.
No problem on N7 though but it happens. First thing is to change your kernel and rom to something else. If still draining, flash stock and relock, unlock, relock, wipe. Boot, upgrade to 4.2.2 and test.
Sent from my Nexus 7 using XDA Premium HD app