constant reboots in, cwm,cm boot logo and cm11 it's self - Nook HD, HD+ Q&A, Help & Troubleshooting

I'm getting constant times when my nook HD+ just shuts down, it first happened in cm11 the 9/11 nightly, it would shut off when I went on certain web pages and on YouTube, then it would shut off when I tried to change the wallpaper. It would then shut off at the cm boot logo after about 2 seconds,only being able to boot fully after repeating about 4 times. So I did a factory reset and reinstalled the rom, but then when I tried to install gapps the device would shut off, so I went in did factory reset again and formatted system, installed the ROM and gapps fine this time but the first time it still shut off at the cm boot logo, its now booted back into cm 11 the second time but still getting shut off's when I try to apply wallpaper etc.
I've re installed the stock ROM and I'm still getting random shut downs and its saying my battery is 1% when its fully charged
can anybody help please ?

same here
neontigers said:
I'm getting constant times when my nook HD+ just shuts down, it first happened in cm11 the 9/11 nightly, it would shut off when I went on certain web pages and on YouTube, then it would shut off when I tried to change the wallpaper. It would then shut off at the cm boot logo after about 2 seconds,only being able to boot fully after repeating about 4 times. So I did a factory reset and reinstalled the rom, but then when I tried to install gapps the device would shut off, so I went in did factory reset again and formatted system, installed the ROM and gapps fine this time but the first time it still shut off at the cm boot logo, its now booted back into cm 11 the second time but still getting shut off's when I try to apply wallpaper etc.
I've re installed the stock ROM and I'm still getting random shut downs and its saying my battery is 1% when its fully charged
can anybody help please ?
Click to expand...
Click to collapse
i have been having this issue for like two months now. it all started when my daughter ran the tablet out totaly. took a good three days of tinkering before it would actualy take a charge. now i get constant shut downs, flickering screen. will say im 100 percent charge and when take the cable out it will go down to 1% i dont think the battery is bad because sometimes it will actualy hold the charge.

Could be the power connector or at least somewhere along the power path. My old kindle had what looked like battery issues which was actually the cable itself at the port that was a bit loose and a different cable had fixed it - it even said it was fully charged but drained 4x faster (give or take). After the fix the battery life was normal again.
Its would be incredibly confusing [to me] if draining all life from the battery is the cause of your problems as I do it often with all phones/tablets (and others do it) and its never caused me a problem not even once. I do it on purpose not accidental.
More likely a coincidence and not the actual cause and the issue is that something was damaged or going bad. It doesn't sound like a software problem. And since it appears to be battery related that would likely be the battery or related path such as the power cable, port, wall plug.
Since its made by humans, I'm going to say if it turns green fully charged then its not necessarily anywhere near fully charged especially if the incoming power wasn't the proper amount, it could potentially be thrown off and confused instead of what one would expect happening that of either/or.
Wrong or right there's my best guess. Do with it what you will.
Adding if its still under warranty (I would assume), according to leapinlar, BN will give you a new power cable if that's the problem, or same with the device (as I took advantage of for hardware defect).

sandsofmyst said:
Adding if its still under warranty (I would assume), according to leapinlar, BN will give you a new power cable if that's the problem, or same with the device (as I took advantage of for hardware defect).
Click to expand...
Click to collapse
They will only give you a new cable if it is still in the warranty period AND it still is running stock. You may get by with just taking the cable in, and if they can demonstrate it is defective, get a new one. But if you bring the device in with CM on it the warranty goes bye-bye. So if you take it in, be sure stock is on it.
Sent from my BN NookHD+ using XDA Premium HD app

*gasp* the rest of it. Thanks for the correction there.

GOT IT
So i took it apart thinking i would replace the battery. Didn't end up having to. i disconnected the battery from the main board, then plugged it back in. tablet fired up and showed 100% battery. haven't had a single issue since. :good::good::good:

Related

[Q] can't charge or turn on my nook hd+ at all

My nook was idle for a day or two, as I remember I hv shut it off.
But then yesterday I try to charged it, the light was green then turn to red, n then it went off, usually the nook would turn on right after I plug the charger. So I didn't notice it until today, and I tried to turn it on by pressing the power button, and the N button together as well, both didn't work.
It seems that I can't charge it or turn it on. Everytime I tried to re-plug it to power or press power button while its connected, the light went on in green to red then off again.
Sent from my GT-N7000 using xda app-developers app
Connect your charger. Let it stay on charger 20 min. Then try push n button. If this not bring screen on then try push power button for 5 sec. Again if not then try power and n button combination.
Hope this helps.
Thx! Turns out tht external charger didn't work.
Sent from my BNTV600 using xda app-developers app
I think that last opinion is make CWM sd card (without CM10) and insert it do device, then try to switch the device on (with charger trick or power button). If you then get it live all is ok. If not then last change is wait when battery goes empty and charger wakes it up.
Actually i predict that item is itself faulty and you must return it for change (maybe not faulty at hardware side, only OMAP inside code got corrupt).
I don't know, that might because I rooted my device, and I did sth wrong. Sometimes it would reboot itself, since my cmw card was inserted, it would load tht root page so I found out. But I live in Asia so returning the device might be too costly, probably won't do it.
Sent from my BNTV600 using xda app-developers app
ling_1118 said:
I don't know, that might because I rooted my device, and I did sth wrong. Sometimes it would reboot itself, since my cmw card was inserted, it would load tht root page so I found out. But I live in Asia so returning the device might be too costly, probably won't do it.
Sent from my BNTV600 using xda app-developers app
Click to expand...
Click to collapse
It could be several things. The most likely is it was trying to update itself and could not because the CWM card was there. I don't think your device is defective.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
It could be several things. The most likely is it was trying to update itself and could not because the CWM card was there. I don't think your device is defective.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Now i can say same. With first information things was other.
...It's more or less a known bug to those of us who use CM10 (even to some who use stock), the battery simply often can't tell how much she has left. So she may fluctuate from 1% to 26% to 0% a moment later . In one such moment my Nook HD+ shut down (went from 26% to 0%). So I put it up for charging thinking (naively) that it would boot up ... it didn't, now all I get is a charging icon that never goes away (orange led remains lit). What's more I *know* it has some charge (the "26%" was the right value) and I know the battery works, so what prevents it from starting is the "battery charge sensor".
It's a pretty silly way to lose your (my) tablet over. Even more so given how much I grew attached to it for my workflow. So what's next? Is there a secret way to convince it to boot. As I said both the hardware and its software is in top condition. I guess an alternative would be to ship it back for replacement but I'm afraid that I've lost my receipt and -as I said- it's a silly way to lose your tablet over, there *has* to be a (fast) way out...
BTW when connected to my PC my device manager briefly shows an "Omap 4470" unknown device (with an exlamation mark) which goes away few secs later, so I cannot attain ADB control over my devices either (sadly)....
Stevethegreat said:
...It's more or less a known bug to those of us who use CM10 (even to some who use stock), the battery simply often can't tell how much she has left. So she may fluctuate from 1% to 26% to 0% a moment later . In one such moment my Nook HD+ shut down (went from 26% to 0%). So I put it up for charging thinking (naively) that it would boot up ... it didn't, now all I get is a charging icon that never goes away (orange led remains lit). What's more I *know* it has some charge (the "26%" was the right value) and I know the battery works, so what prevents it from starting is the "battery charge sensor".
It's a pretty silly way to lose your (my) tablet over. Even more so given how much I grew attached to it for my workflow. So what's next? Is there a secret way to convince it to boot. As I said both the hardware and its software is in top condition. I guess an alternative would be to ship it back for replacement but I'm afraid that I've lost my receipt and -as I said- it's a silly way to lose your tablet over, there *has* to be a (fast) way out...
BTW when connected to my PC my device manager briefly shows an "Omap 4470" unknown device (with an exlamation mark) which goes away few secs later, so I cannot attain ADB control over my devices either (sadly)....
Click to expand...
Click to collapse
If you are running CM10 or 10.1, there is an easy way to connect with ADB. Do it wirelesly over wifi. That is built into CM. Just enable it in the developer options. No need to mess with the USB cable and windows drivers. You can do the same thing with rooted stock by installing an app called ADBWireless.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
If you are running CM10 or 10.1, there is an easy way to connect with ADB. Do it wirelesly over wifi. That is built into CM. Just enable it in the developer options. No need to mess with the USB cable and windows drivers. You can do the same thing with rooted stock by installing an app called ADBWireless.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
At the time that could not happen , since (as I had implied) my nook was not booting to begin with...
Anyhow, what I did was to leave it for three solid hours on the charger, and after that period of time it booted on its own wiithout warning. It's the first that such behavior was/is ever present to my nook and it's deeply worrying. A battery fix for the CM kernel couldn't come any sooner; now, if only verygreen was around
There's a few ideas on a couple of other threads including putting it in the fridge, etc. Question, if you plug it in, does the charging light come on? Does it come on after pushing the power button or the N button? If so, take your SD out, leave it charging overnight and try again. It often reboots when in this state and if there's an update problem, that could be the issue. Also, it is sometimes erratic on when and how it charges, be careful with the connections.
dbh369 said:
There's a few ideas on a couple of other threads including putting it in the fridge, etc. Question, if you plug it in, does the charging light come on? Does it come on after pushing the power button or the N button? If so, take your SD out, leave it charging overnight and try again. It often reboots when in this state and if there's an update problem, that could be the issue. Also, it is sometimes erratic on when and how it charges, be careful with the connections.
Click to expand...
Click to collapse
As I said it came up on its own, without warning after leaving it for 3 hours on the charger...
As for your question, the led (charging light) was on all the time but it would only show me that it had no battery (couldn't charge even though it was ... charging?)
Maybe the fridge makes sense in those situations, as it was indeed into a (relatively) hot environment and maybe it couldn't charge as a safety against overheating and since (at the same time) it also thought it had 0 battery. But what I can't understand is why needed 3 hours before starting to charge up, it was already cool enough long before ... strange things are/were happening with my battery all along and I worry...
Stevethegreat said:
As I said it came up on its own, without warning after leaving it for 3 hours on the charger...
As for your question, the led (charging light) was on all the time but it would only show me that it had no battery (couldn't charge even though it was ... charging?)
Maybe the fridge makes sense in those situations, as it was indeed into a (relatively) hot environment and maybe it couldn't charge as a safety against overheating and since (at the same time) it also thought it had 0 battery. But what I can't understand is why needed 3 hours before starting to charge up, it was already cool enough long before ... strange things are/were happening with my battery all along and I worry...
Click to expand...
Click to collapse
Yep, I've noticed the same thing a few times. It no longer panicks me. When it doesn't turn on, I take out the SD, plug it in, wiggle the connector a few times, and let it alone. So far, it has always eventually rebooted, often as you say on its own. Quirky, but not fatal at least. One poor guy on here never did get his to turn on, but the key was the charging light,his didn't come on.
Need help cannot turn on Nook HD+ at all
Hi!
I cannot turn it on at all and it won't reboot.
It went out some point I didn't watch it. When I connected it to the charger the LED next to the connector starts blinking amber and green for a few seconds and then stays blinking red and makes a high pitched noise.
The only reaction I get is when I press power on an volume down after some time - it display turns on an shows a charging sign - but it never really seems to fully charge. I left it on the charger over night - still the same. Once the display blinked and showed “nook” but went out immediately after a few milliseconds.
Might it be some kind of bootloop!?!?
What combination to press to make a reset?
Thanks in advance for any help
Medizinmann

0% battery after crashes

So I've had this phone for about a year now, the moment I got it I unlocked the bootloader, rooted it and flashed cyanfox (cm11 fork) onto it.
It's been serving me great ever since, no problems whatsoever with it.
But as of a few days back I found it with a black screen, unresponsive. I connected the charger and it light up the green led solid, tries to boot but can't get past the boot loader message
This continues in an almost endless loop until getting to a 'battery 1%' screen with it showing the battery. After that I'm able to boot it up without problem
I first thought that was the end of it.. I finally got it too boot all seemed fine, battery showed 3% at start up bit voltage was suggesting it was 100%. It flashed to 100% later.
Good, no problem until then. But when leaving it over night to charge and disconnecting it from the charger this morning it turned off again. And now it's back in the bootloop when on charger :crying:
also important to mention is that when it crashes and gets into the bootloop on charger(0% battery and all) it was at 50-100% before the crash.
If anyone has any ideas what might be the cause I'd be very thankful
Main problem(s):
-random crashes instantly rendering battery % as 0 while there is still charge
-getting atrix hd to turn on at <1% battery
Some maybe useful information:
-it does say 'battery OK' in fastboot while connected to the wallcharger
-after I get it to boot it will run just fine on battery and charge as normal, but will crash/brick again after some time
-I can get into boot selection screen and fastboot, but only on wallcharger
-I cannot get to fastboot when connected to use, pc doesn't see the phone
-It won't boot past the bootloader('Motorola logo' for you on not unlocked bootloaders) no matter the boot selection(recovery, bp tools etc)
-This is a second hand model already in use by me (the second owner) for over a year now
-no custom kernel, only rom, cyanfox 4.4.2 (cm11 based)
-the few times it got past the bootloop and I was able to boot was on my aftermarket charger (stock charger will make the green led light up but no proof of being able to get past bootloop over time on it)
I've had dead batteries before.. and since It looked good last time I got it on (it won't go on at all now) I was skeptic about the battery being dead. But a quick test of the multimeter gives me <1v :crying:
I know batteries can be drained pretty bad.. but this just seems a bit extreme.. I'll try to get it to boot for a while.
Thanks in advance for any helpful solutions or ideas on the matter
EDIT: Got it on again last night, turned off this morning when pulling out the charger, was at 100%. Checked battery and again read around 1V.
blaming the battery, ordered a new one just in case, should be here in a month or so. Still open for suggestions on the matter
Catblaster said:
I've had dead batteries before.. and since It looked good last time I got it on (it won't go on at all now) I was skeptic about the battery being dead. But a quick test of the multimeter gives me <1v :crying:
I know batteries can be drained pretty bad.. but this just seems a bit extreme.. I'll try to get it to boot for a while.
Thanks in advance for any helpful solutions or ideas on the matter
EDIT: Got it on again last night, turned off this morning when pulling out the charger, was at 100%. Checked battery and again read around 1V.
blaming the battery, ordered a new one just in case, should be here in a month or so. Still open for suggestions on the matter
Click to expand...
Click to collapse
Did you fix it somehow in the end?
My Atrix HD freezes after several minutes(sometimes even on wall charger). Bought new battery, tried to reset everything: usb storage, cash, system, factory reset. Went back to ROM I was using before(stable) but didn't help.
?
michael8s said:
Did you fix it somehow in the end?
My Atrix HD freezes after several minutes(sometimes even on wall charger). Bought new battery, tried to reset everything: usb storage, cash, system, factory reset. Went back to ROM I was using before(stable) but didn't help.
?
Click to expand...
Click to collapse
It ended up being the battery, all problems were gone after I changed the battery.
Which in the end wasn't so bad because I'd been wanting to upgrade my eb20 to an eb40
No Idea to what it could be in your case.
Everything working appart from that? no battery hickups or things not working properly?
Catblaster said:
It ended up being the battery, all problems were gone after I changed the battery.
Which in the end wasn't so bad because I'd been wanting to upgrade my eb20 to an eb40
No Idea to what it could be in your case.
Everything working appart from that? no battery hickups or things not working properly?
Click to expand...
Click to collapse
"0% battery after crashes" that is what was happening in the begging, so I thought it is the battery. I changed it to UB40
but everything's got worse. With the new battery I have crashes even when the battery is almost full.(but not always, for example I can play movie from youtube normally, but when I try to send sms or something else it crashes ).
Hard to believe that there is something with the new battery(I have it just one week+It took a month to ship from ebay).
I tried to flash another ROM, but still have freezes.
Last thing sometimes battery charges normally but then suddenly jumps to ~100%. Now I try to flash Stock ROM, but eventually soft bricked the phone. (+had "battery low" in fastboot, while charging animation was saying 100%)
Where did you buy EB40?
____________________________________
It turned out that EB40 battery was bad, after replacing it with another one everything work

[Q] Nook HD won't boot

Hi,
I've owned a B&N Nook HD (7 inch) for just over a year, when I first got it I flashed CWM and CM10 onto it and ever since have had absolutely no issues with it, however a couple of weeks back I was having trouble getting it to charge, it would take a few tries of plugging the cable in before it would finally begin (I'm not sure whether this is related at all to the issue) However a couple of days ago I was happily browsing the internet, then it made a strange "Pop" sound and the screen went completely black. Ever since then it won't boot up, it will briefly display the Nook logo but will then make the same pop sound and go to what looks like a black screen, however under low light you can see that the backlight is still faintly on, and to turn it off you have to hold the power button for 7ish seconds. Also on one attempt to boot it made it past the nook logo, and onto the cm loading screen but then had the same issue. I've also tried booting it to recovery but with no success :crying: .
Any help would be greatly appreciated, even if it's just to say that it's a complete right off.
Thanks
Probably you might have damage battery
bobjohnsonandco said:
Hi,
I've owned a B&N Nook HD (7 inch) for just over a year, when I first got it I flashed CWM and CM10 onto it and ever since have had absolutely no issues with it, however a couple of weeks back I was having trouble getting it to charge, it would take a few tries of plugging the cable in before it would finally begin (I'm not sure whether this is related at all to the issue) However a couple of days ago I was happily browsing the internet, then it made a strange "Pop" sound and the screen went completely black. Ever since then it won't boot up, it will briefly display the Nook logo but will then make the same pop sound and go to what looks like a black screen, however under low light you can see that the backlight is still faintly on, and to turn it off you have to hold the power button for 7ish seconds. Also on one attempt to boot it made it past the nook logo, and onto the cm loading screen but then had the same issue. I've also tried booting it to recovery but with no success :crying: .
Any help would be greatly appreciated, even if it's just to say that it's a complete right off.
Thanks
Click to expand...
Click to collapse
Please watch this tutorial how to remove battery. https://www.youtube.com/watch?v=YfYvhtw30mU.
Then charge your battery via external power source i.e.Master charger. If you still can't turn on your device. Then buy new battery. Link of ebay is http://www.ebay.com/bhp/nook-battery
If it is software issue @leapinlar will surely figure it out.
Thank you very much for your quick response, I'll give the link a try!
Battery Charged
keshabbhattarai126 said:
Please watch this tutorial how to remove battery.
Then charge your battery via external power source i.e.Master charger. If you still can't turn on your device. Then buy new battery. Link of ebay is
If it is software issue @leapinlar will surely figure it out.
Click to expand...
Click to collapse
I had a go at removing the battery, but as I don't have a Master charger or anything like that around, just stuck a multimeter onto the connector, and it read about 3.5v so to me that seems pretty charged.
Does this mean it is a damaged battery, as I'm on a bit of a shoestring budget, so want to make sure I'm getting the right thing
Regards
Bobjohnsonandco
bobjohnsonandco said:
I had a go at removing the battery, but as I don't have a Master charger or anything like that around, just stuck a multimeter onto the connector, and it read about 3.5v so to me that seems pretty charged.
Does this mean it is a damaged battery, as I'm on a bit of a shoestring budget, so want to make sure I'm getting the right thing
Regards
Bobjohnsonandco
Click to expand...
Click to collapse
I've install stable cyanodgen 10.2.1 a year ago and have this issue ever since. Not sure if it's common but whenever the nook is drain completely to dead...when you try charging it..the light would be green..then amber. So I don't know whether its charge or not but I guess it is. I would not be able to power it back on...the normal way. It would seems dead. The way for me to get it to power up is to get into cwm recovery by pressing both the power and home button at the same time, then reboot it. It gets annoying because I would have to do that all the time since my 5 year would drain it out lol

[SOLVED] Shutdown during boot (was "Battery indicator issue with CM 12.1")

(Please see post #4 as the issue has evolved)
I recently updated my husband's HD from CM 11 to CM 12.1 (the one build in @amaces obsolete folder). This restored some functionality to a few apps that had "moved on" beyond KitKat and preserved the HMDI functionality. Everything else is essentially the same. Except.
Too often on starting the tablet up in the morning it shows about the same battery level as at shutdown the prior evening (maybe 50-ish) and then in a matter of minutes nosedives to 1%. You can see the behavior on the power usage graphic in Settings and it's pretty shocking. There's a vertical line for when it booted up and then *bam*, it drops to essentially nothing. If the tablet is plugged in for just a moment, the battery level returns to normal and everything is fine. It can be disconnected from the power supply and behaves normally the rest of the day.
So this is annoying (moreso because I need to hear about it every time it happens ). I've read the entire (unofficial) CM 12 thread. This issue comes up once or twice and seems to be "resolved" by "calibrating" the battery either with an app from the PlayStore or without. The app seems to just delete a file that would be overwritten at boot anyway from what else I have read on the subject, but the main idea is to drain the battery to an actual 1%, shut down and charge (the tablet remains "off" although the screen is on) until you've got 100% (which has to be judged by the green LED since the tablet is off).
I tried this (with the app), beginning by wiping cache and dalvik cache. It seemed to work for awhile. Then I foolishly suggested doing a backup. I did this with the emmc TWRP and everything seemed to go well except the battery indicator issue started up again...
So we did the battery thing again.... And it was just fine until this morning (not what you want to hear as you sit down to breakfast).
Clearly one could live with this if you always have the charger close at hand, but it's pretty lame. The tablet behaves beautifully in all other respects. I don't think it's a hardware issue as it started right after flashing the new ROM.
One person in the CM 12 thread actually praised the ROM as eliminating this issue which he had from CM 11!
Is this a flashing glitch which might be fixed by reflashing the ROM? I'm loath to do a clean install and reconstruct everything again after such a short time, but I wonder if a "dirty" install (don't wipe data, right?) would be enough. If I reflash the ROM do I have to reflash GApps also?
Suggestions? I'm really at a loss here.
nmyshkin said:
...
Is this a flashing glitch which might be fixed by reflashing the ROM? I'm loath to do a clean install and reconstruct everything again after such a short time, but I wonder if a "dirty" install (don't wipe data, right?) would be enough.
Click to expand...
Click to collapse
I doubt if a dirty flash would change anything, but there does not appear to be any penalty to try it out as a shot in the dark.
If I reflash the ROM do I have to reflash GApps also?
Click to expand...
Click to collapse
Not if you don't wipe /data -- basically same as in the case of a dirty upgrade.
digixmax said:
I doubt if a dirty flash would change anything, but there does not appear to be any penalty to try it out as a shot in the dark.
Not if you don't wipe /data -- basically same as in the case of a dirty upgrade.
Click to expand...
Click to collapse
I finally got around to this after much complaining about the issue and now I've managed to make it much worse. Before, the tablet would drop from the 50's (or lower) to 1% on boot. Higher percentages of charge were usually safe. Now it goes through the boot process up to the animation and then abruptly shuts down UNLESS the power cable is connected, regardless of the state of battery charge. If the cable is connected boot occurs normally and you can disconnect after boot is complete and everything is "fine".
Except, of course, it's not "fine" at all. Unless you have the charger and cable with you at all times, the tablet has to be left on when you're on the go.
Ugh. Any ideas besides going back to stock and starting over?
nmyshkin said:
I finally got around to this after much complaining about the issue and now I've managed to make it much worse. Before, the tablet would drop from the 50's (or lower) to 1% on boot. Higher percentages of charge were usually safe. Now it goes through the boot process up to the animation and then abruptly shuts down UNLESS the power cable is connected, regardless of the state of battery charge. If the cable is connected boot occurs normally and you can disconnect after boot is complete and everything is "fine".
Except, of course, it's not "fine" at all. Unless you have the charger and cable with you at all times, the tablet has to be left on when you're on the go.
Ugh. Any ideas besides going back to stock and starting over?
Click to expand...
Click to collapse
I came across a post that suggested returning all the way to stock and doing a factory reset, then rebuilding the system.
Once at stock I had no trouble completing a boot without being plugged in. So that is not a hardware issue. I didn't stay on stock long enough to see if the battery indicator behaved, but I'm guessing it did. I prepared a completely new SD card with newly downloaded files and proceeded to do the needed flashing for CM 12.1 w/GApps, using CWM 6.045. It all seemed to go well--even no screen flashing--until I unplugged the tablet so I could easily remove the SD card and reboot. As soon as I removed the power cord the periodic screen flashing that seems to be common during CWM use started up.
I rebooted and got only so far with the CM logo before the tablet shut down.
I don't get it. It worked fine before. What about this process could be causing this odd behavior?
Edit: in desperation I tried flashing The ROM again right over the prior installation. This time I booted into the emmc CWM (6.0.4.6) and waited for the tablet to calm down. Then I unplugged it and flashed the ROM from the ext.SD card. No error messages. I held my breath and rebooted. I got to several iterations of the cyan android face and then it shut down again.
Next I flashed TWRP 2.8.7.4 to emmc and tried flashing the ROM from the ext.SD card that way. Same result.
The battery charge shows 80% so it's not like the tablet is running on fumes and it's hard to believe the problem is the battery or the indicator since none of this happens on the stock ROM.
I just don't get it. We don't want to go back to stock but I don't understand any of what is going on. Initially CM 12.1 was working beautifully. Then the battery indicator issue started. I addressed that as best I could and when it seemed like we had that on the run I did a backup. That resulted in this shutdown issue. You can use the tablet just fine if you never turn it off and keep either the charger or a portable power pack handy (don't forget the cable!).
I really need some help troubleshooting. I'm willing to try just about anything.
Edit: indeed, the last resort was to buy another HD... But it turns out the booting issue was caused by an SD card that somehow was not properly prepared as 0x0C FAT32 LBA but was instead something else which I don't remember now (something with a "b"). Anyway, once a new card was carefully prepared, the tablet booted fine without being plugged in. Whether this also solves the battery indicator issue remains to be seen.

Fire Reboot to Recovery - Unresponsive

Hi there, I'm having an unfortunate issue with my Amazon Fire (rooted, flashed AOSP with FireFlash). As I was sending a message last night, it rebooted itself to recovery. To get back to the OS, I selected it to reboot the tablet, and I have not had any signs of life since. The battery was around 50%, but I plugged it back in to charge overnight. I have held the power button for over 40 seconds, both volume combinations don't seem to change anything, and it wasn't detected by Windows. I don't see the backlight coming on at all, either. Is there anything that I can do to force it to boot or reset? I don't mind flashing a new OS if it means I can use my tablet again.
ryanstein said:
Hi there, I'm having an unfortunate issue with my Amazon Fire (rooted, flashed AOSP with FireFlash). As I was sending a message last night, it rebooted itself to recovery. To get back to the OS, I selected it to reboot the tablet, and I have not had any signs of life since. The battery was around 50%, but I plugged it back in to charge overnight. I have held the power button for over 40 seconds, both volume combinations don't seem to change anything, and it wasn't detected by Windows. I don't see the backlight coming on at all, either. Is there anything that I can do to force it to boot or reset? I don't mind flashing a new OS if it means I can use my tablet again.
Click to expand...
Click to collapse
Suspect your device suffered a fatal hardware failure. Components are not especially robust to meet Amazon's aggressive price points. Spontaneous hardware failures have been reported by others. Given you were running a custom ROM an uninvited OTA update can be quickly ruled out.
Another possibility is a bad battery. I have seen devices that will not respond while 'plugged in' if the battery is missing or bad. Replacing the battery pack is fairly easy although you will need to disassemble the device. Whether it's cost effective depends on how much you value root and the ability to use a custom ROM.

Categories

Resources