Related
I'm 99% sure this isn't a failed rooting attempt.
My phone works fine *IF* I can get it to power on with the power cord. As soon as it comes unplugged it's anybody's guess as to how long it will stay on for.
After it powers off it won't turn on at all. I have to plug a power cord into it and wait for the green light to show up. (Sometimes takes minutes, sometimes takes days.)
Sometimes when it's plugged in and won't turn on if I hit the power button all the button lights come on for just as long as I press the button, I can push the power button over and over and all the buttons light up. But if I unplug it that too stops working.
When it started I had moved back from CM6 to 5.0.8.
I am on the 2.22.23.02 radio and have Rom manager with the clockwork mod recovery that it wants you to use.
I have tried multiple batteries this is not a battery issue
I'm hoping it's not a hardware problem.
Could it be the recovery or radio causing these issues? I'm afraid that if I try to reflash the radio it will power off in the middle of the flash process and really brick my phone.
Anyone have any other ideas or maybe has anyone seen this before?
xelaboy said:
I'm 99% sure this isn't a failed rooting attempt.
Click to expand...
Click to collapse
I'll bump that certainty up to 100% for you. Your battery has failed. Time to buy a new one.
I realize you say it isnt, but it is.
I have 2 batteries of my own.
I took it to batteries plus to have them test it there. They had a perfectly good battery and it wouldn't power the phone on. Believe me I desperately wanted to believe that it was just a battery issue. I actually still do. But having 2 batteries myself and seeing a third not work just seems like overwhelming evidence against the battery being the problem.
You can try to wipe battery statistics, it might help you.
In AmonRA there is an option to do so, if such an option exists in Clockwork, too, I I don't know.
AndDiSa said:
You can try to wipe battery statistics, it might help you.
Click to expand...
Click to collapse
That's a good idea. I hadn't thought of doing that. I'll give it a shot next time my phone allows me to turn it on.
The newest update bricked the device and i'm looking to get some files off the phone before using the sbf to restore. Is there a way to have ADB access if you are not able to successfully boot into the OS?
Hey, as an avid flasher (gosh i believe i did it over 15 times just this month =O), I noticed that even if you reflash everything on your phone, only your apps are erased as well as some data. If you're looking to back up stuff in the internal SD card, you should be fine as flashing won't touch that. As for if you're looking to grab some user data, I don't believe there's a way to do that, but I could totally be wrong. Sorry if that didn't help =\
if you reboot holding arrow down, it seems like I saw a USB enumeration option if you keep pressing down volume through the option. That may be a way to get the stuff off, depends what you want to do though.
I can also confirm SBF'n back to factory will retain SD info. I did it this morning to update to latest OTA.
Accidentally rooted and bricked ... but now the battery won't charge ... so RDS says battery is too low to flash ... any suggestions?
My only thought is to go to the ATT store and ask if they can swap batteries, but I don't see why they would.
If you plug it into the wall it should charge with the phone turned off. If the battery is completely dead- it will appear nothing is happening. Just leave it plugged in for a while, drink a beer, do something around the house, then come back. It should show a charging light at this point or have tried to turn itself on.
I will also 2nd that SBF flash will keep the files on /sdcard/ level intact.
Thanks for the quick reply...I feel silly asking, but how do you turn it off? As soon as I plug it in it turns on and gives the message "Failed to boot 2 / Starting RSD mode / Battery too low to flash." I press power, nothing happens. I hold down power, nothing happens. I hold Vol Down and press power, nothing happens. I charge overnight 12+ hours with the screen on, it gets warm, but otherwise nothing happens. I charge with the USB to the computer, the screen stays off, and it seems to get a little bit of charge (enough so that it doesn't shut off as soon as it's unplugged), but hours of trying to charge this way nets the same error message. She's bricked. I guess you can't flash without a battery in place?
Edit: Or just buy this spare battery desktop charger
My next best suggestion for you is to find a way to get 3.7 volts of power to those battery pins. Either with a regulated power supply or another lithium cell battery. I'm not sure whether or not the detection circuit will allow the phone to boot or not or if that is charge-related only, but it would be an alternative to keeping a bricked phone. If you choose to try to run this without a battery keep in mind wall wart type power is unstable (read: voltage changes) at different current draws.
Went to the store near closing time (10 min) and they gave me a fresh battery instead of going through warranty, said that could take days with no phone. Fortunately he didn't test the battery and, upon putting a new one in, he only looked at it long enough to see the dual core logo and not the Failed to Boot message.
Flashing worked perfectly after I had a fresh battery, thankfully. No longer bricked, no longer using 6-yo crackberry!
I recently went on a 3 month trip. Before I left, my nook was working perfectly fine, when i got back, it didn't work at all. It's not dead because i left it plugged in overnight but it still didn't turn on. when i plug it in the LED goes from orange to green and then off (or green to orange, i can't remember). The screen doesn't turn on at all. I can't get to recovery either.
This is a Nook HD, I believe it had CM11.
:crying:
Can this be fixed
or should i plan it's funeral
Same here
The same has happened to me. Screen doesn't turn on, but there is power, I can play it into my laptop and something is there, just not enough.
Good excuse for a new tablet!
It can be fixed. I've done it before. It has to do with the fstrim not being compatible with certain hardware versions of our device. If I can remember how I fixed it, I'll post it here. Trying to fix mine (again).
tambourineman86 said:
It can be fixed. I've done it before. It has to do with the fstrim not being compatible with certain hardware versions of our device. If I can remember how I fixed it, I'll post it here. Trying to fix mine (again).
Click to expand...
Click to collapse
If would be fab if you could fix. Seems to be a common issue
I was able to fix it. YMMV.
1) Make sure the Nook is completely off and unplugged
2) Take out your sdcard
3) Hold down power button until the "battery depleted" icon shows, then promptly plug in the power before the icon disappears.
4) Let it set. The screen will go black, then it will attempt to boot and get stuck on the faint black screen, but this time, the charging light should stay amber.
If you want to be safe, wait until the device reboots itself. That could take hours though. If you're plugged into the wall wait at least 30 - 45 minutes before holding the power button down til it shuts down and then rebooting it (with the sdcard inserted).
Good luck, I hope it works for you.
EDIT: Also, I've read this may also have to do with wifi sending the device into some sort of strange bootloop when the screen is off. I personally believe it has more to do with the fstrim of JB but perhaps changing the wifi sleep policy may prevent this issue from happening again. I'm skeptical, but figured I'd pass that info along if anyone wants to try it as well.
tambourineman86 said:
I was able to fix it. YMMV.
1) Make sure the Nook is completely off and unplugged
2) Take out your sdcard
3) Hold down power button until the "battery depleted" icon shows, then promptly plug in the power before the icon disappears.
4) Let it set. The screen will go black, then it will attempt to boot and get stuck on the faint black screen, but this time, the charging light should stay amber.
If you want to be safe, wait until the device reboots itself. That could take hours though. If you're plugged into the wall wait at least 30 - 45 minutes before holding the power button down til it shuts down and then rebooting it (with the sdcard inserted).
Good luck, I hope it works for you.
EDIT: Also, I've read this may also have to do with wifi sending the device into some sort of strange bootloop when the screen is off. I personally believe it has more to do with the fstrim of JB but perhaps changing the wifi sleep policy may prevent this issue from happening again. I'm skeptical, but figured I'd pass that info along if anyone wants to try it as well.
Click to expand...
Click to collapse
Not sure we have the same problem. My screen doesn't come on at all, I don't get a battery depleted icon, no matter how long I hold in the power button. The only sign of life I get is when it's plugged in, when it goes from orange to green after about 10 seconds.
Thanks for the help, but I think it's a lost cause.
YMMV. But mine was the same issue. You should be able to get the icon by holding the power button down for 5 or 6 seconds. I'd say just eff with it until that icon appears. Try different button combinations. I used power and home trying to get the icon to show.
developerbuzz said:
when it goes from orange to green after about 10 seconds.
Thanks for the help, but I think it's a lost cause.
Click to expand...
Click to collapse
Anyway... since people are continually running into this kind of issue...
Give or take 21 seconds after turning orange it turns green during actual boot cycle into rom
Give or take 10 seconds after turning orange is cwm internal recovery.
After about 10 seconds the charging screen image disappears.
The charging screen image once finally no longer may not show up again until full power off/on (holding power button > 10 seconds or full battery discharge). Unplugging and plugging back in does nothing except making the device look bricked if there's too much light shining on it.
Device may not automatically leave the above state under a specific situation(s). May still need manual full power off/on.
Guessing 10 seconds could also be something else during the early/late boot process or other. The light changing color though should indicate that something is indeed happening.
Light should stay green during the boot process if its completely and fully no questions asked 100%. If you go based on that than yours doesn't appear to be completely fully charged which should either mean its turning on and using battery or not charging correctly.
The light turning off is curious. The device could be shutting off. If light comes back on a moment later then the device has rebooted. if the light stays off = n/a.
If its booting into recovery then the device would be available via adb. At that point it could be further evaluated.
On the off chance the screen was damaged it should boot and usb should be available via computer as well as adb.
If not then its probably toast unless its simply not getting a good enough current causing mislead battery stats and/or not enough energy to get to charging screen (bad wall power adapter in use, damaged power cable - though could be bad battery, defect, damage or whatever). OR there's some major error on behalf of the user happening (think should have tried that in the morning not while 1/2 asleep or came home from long trip and forget how that works).
Maybe the only other things are the emmc brick bug, was left sitting in the sun or heat or ocean air or other physical damage/defect even to the power port as well.
Or maybe it was mad that you left it. Shouldn't have hurt its feelings you know. At least its not crying battery acid on you.
That should just about cover everything except for the things not mentioned. Since its your device, you decide what happened.
Its complicated so anyone see any improvements, clarifications, or mistakes? Please put it in a post.
Jsorren said:
when i plug it in the LED goes from orange to green and then off (or green to orange, i can't remember). The screen doesn't turn on at all.
Click to expand...
Click to collapse
Bumping this thread to make it aware that there is a real answer. I have been able to duplicate this problem and rather easily too.
The problem is indeed from bad power. The device isn't receiving the correct amount of power needed to charge and start from a fully discharged battery.
To safely* duplicate this you can use a usb extension that isn't fully connected to the nook power cable. You may need to fully connect it first then slowly disconnect/connect till the light turns green when it should actually be charging. It won't actually charge in this state, or if it is, its very little and the battery percentage will continue to drop.
Leave the cable as is and unplugged. After the tablet is fully discharged, connect the usb cable. The light will change through the modes and turn off. The device will not turn on.
There are probably other ways to cause the problem like for instance a portable usb battery that doesn't put out enough juice (not the orange kind). Etc.
* It didn't hurt mine, but not my fault if it breaks your device.
sandsofmyst said:
Bumping this thread to make it aware that there is a real answer. I have been able to duplicate this problem and rather easily too.
The problem is indeed from bad power. The device isn't receiving the correct amount of power needed to charge and start from a fully discharged battery.
To safely* duplicate this you can use a usb extension that isn't fully connected to the nook power cable. You may need to fully connect it first then slowly disconnect/connect till the light turns green when it should actually be charging. It won't actually charge in this state, or if it is, its very little and the battery percentage will continue to drop.
Leave the cable as is and unplugged. After the tablet is fully discharged, connect the usb cable. The light will change through the modes and turn off. The device will not turn on.
There are probably other ways to cause the problem like for instance a portable usb battery that doesn't put out enough juice (not the orange kind). Etc.
* It didn't hurt mine, but not my fault if it breaks your device.
Click to expand...
Click to collapse
I actually ended up fixing it yesterday!! I haven't touched it in about 3 months, and I was planning on just throwing it out getting rid of it some how. For the heck of it, I decided to plug it in, assuming that it was gonna go through the same process. But this time it went from green to amber, but it never went off. So I pressed the power button and the battery icon appeared. This was a really good sign. So I left plugged in for about 5 to 10 minutes then tried to power on.:fingers-crossed: As soon as I saw that '' Nook" boot up screen, my heart stopped. It booted up perfectly and I almost blew up from excitement :victory:. So I then flashed the stock firmware back onto it, so this would never happen again.
I guess the battery had to be completely depleted or just had to cool down. Idk but either way this was one heck of a miracle
So I recommend for anyone having this problem to just leave it off and don't mess with it. I wouldn't say for 3 months like I did but maybe test it each week or wait a month if you have good patience
Wow. Man, that's awesome! Glad you posted that update on it. Thought if you had posted an update it would be the opposite as in trashed it
Actually, I guess only you could answer if you had also moved/unplugged the power cable from the wall adapter or put it into a different wall adapter, etc. Thinking there could have been a difference there.
These modern day devices are so finicky, guess anything is possible. Like you say, maybe sitting without power is another answer.
From some experimentation I have etermined that your power adapter (that plugs into the outlet) is the issue. It does not like to be leaft plugged in indefinately. It will continually use power even when the nook is not plugged in.
Also, if you use a differnt adapter you will have the same problem unless it is also of the exact same voltage and amps.
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.
Stuck on "please lock bootloader" screen when plugging in after depleting the battery
No button inputs work. The only solution seems to be waiting until the battery fully runs out and plugging it in again, after which it sometimes boots up. At least I got it to the first time, it failed just now. Maybe I need to hold some button combination while doing so?
How do I fix this properly? And what's a sure way to get it to boot from this? I'm already wasting half and hour on a minute's charge, God forbid I ever forget about it plugged in for longer. Would have to throw it in the drawer for a couple days and probably end up with some permanent burn-in too.
I haven't seen the screen in ages but doesn't it tell you to press the power button to acknowledge the unlocked bootloader? Also from memory it tells you it will automatically continue but it never does.
What seems to have done the trick is holding power&volume+ (probably just power is enough), so it loops through the 'empty battery' splash screen at least once. I think that's how I did it the first time too.
drwharris said:
I haven't seen the screen in ages but doesn't it tell you to press the power button to acknowledge the unlocked bootloader? Also from memory it tells you it will automatically continue but it never does.
Click to expand...
Click to collapse
It never seemed to make any difference whether I pressed the power button or not, in fact it always booted up automatically after some time, this scenario excluded.
I suppose my problem might lie in the fact that buttons aren't working on that screen for whatever reason? Rather than it not going away automatically after battery depletion.
It is a bug in the bootloader. You can get out of the screen by disconnecting (!) the cable, and then holding all three buttons for multiple minutes until the device forcefully shuts down.
Before you do that, leave the phone plugged in for 10 minutes or so, so it can charge the battery to some extend. Then start the phone without (!) the cable plugged in, and wait until it boots into Android. When it is booted, you can safely plug in the cable and let it charge to 100%.
Just make sure you leave it for some minutes so it has enough charge to boot through the bootloader and start Android.
VonZigmas said:
I suppose my problem might lie in the fact that buttons aren't working on that screen for whatever reason? Rather than it not going away automatically after battery depletion.
Click to expand...
Click to collapse
i had a similar problem after a failed attempt to boot into recovery.
for me the following did do the trick and booted my phone back into system:
- deplete battery completely
- plug in charger and keep power button pressed until phone is charged enough to attempt boot
- keep the power button pressed until nokia logo appears
THMSP said:
It is a bug in the bootloader. You can get out of the screen by disconnecting (!) the cable, and then holding all three buttons for multiple minutes until the device forcefully shuts down.
Before you do that, leave the phone plugged in for 10 minutes or so, so it can charge the battery to some extend. Then start the phone without (!) the cable plugged in, and wait until it boots into Android. When it is booted, you can safely plug in the cable and let it charge to 100%.
Just make sure you leave it for some minutes so it has enough charge to boot through the bootloader and start Android.
Click to expand...
Click to collapse
How long is "multiple minutes"? I tried holding all three buttons at first, but gave up after probably a minute of nothing happening. I'll keep that in mind though.
Is there any hope for this to be fixed in the future?
VonZigmas said:
How long is "multiple minutes"? I tried holding all three buttons at first, but gave up after probably a minute of nothing happening. I'll keep that in mind though.
Is there any hope for this to be fixed in the future?
Click to expand...
Click to collapse
Well, multiple definitly isn't one I haven't stopped the time yet, but expect waiting and pressing them for around 2 to 3 minutes, maybe even 5. It might sound stupid, but it will work.
About fixing it, I don't know. It might be a bug in the reference bootloader that Qualcomm provides for Snapdragon 835 chipsets, and I doubt that FIH / HMD have the resources to debug and fix that.
I get this same screen while the phone's powered off + charging and it's annoying.
I was going to start a thread to ask whether it's possible to charge this phone while it's turned off (without the screen being kept on) after unlocking the bootloader. I guess based on the posts in this thread, that's not possible? [emoji2357]
OneDream said:
I get this same screen while the phone's powered off + charging and it's annoying.
I was going to start a thread to ask whether it's possible to charge this phone while it's turned off (without the screen being kept on) after unlocking the bootloader. I guess based on the posts in this thread, that's not possible? [emoji2357]
Click to expand...
Click to collapse
No, I guess it isn't. I've tried to plug it in while it's off and turn off as it's charging and in either case it resulted in the phone hanging up on that screen. I can confirm though that holding all three buttons for a while does turn it off and allow me to boot normally which is cool.
But is that possible with a locked bootloader anyway? Or does it always power on? I can't tell if I ever needed it to charge like that.
I see this "warning" message only on android pie builds, it doesn't seem on oreo builds. I think problem seems that kernel dependent (oreo is on 4.4.78 and pie is on 4.4.153). There is one way to get rid of that message, as @THMSP said, holding all 3 buttons pressed during 2-3 minutes and let it to be shuted down. Then, let the device to boot normally and plug in. Finally you shouldn't connect to charger when it's turned off on any pie build.