KFHD running CM10.1 powers off randomly - 7" Kindle Fire HD Q&A, Help & Troubleshooting

For about a week now my KFHD running CyanogenMod 10.1 has been powering off randomly. I think each time it has happened, I have been playing or attempting to play audio or video. This is an instant power-off, rather than a proper shutdown -- i.e., the screen goes black, and I have to go through the boot sequence when I power it back on.
This might be a coincidence, but the first time it happened was very shortly after I added a second user account. I was trying to play a podcast with the WTF app, and it suddenly turned off. After the first power-off I booted up the tablet and went straight to the WTF app, and played a couple of seconds of audio before it turned off again; this happened repeatedly, maybe three times in a row.
I removed the second user account, on the chance this was related to the power-offs, but since then it has happened several more times. I believe these other times I was using the Stitcher radio app (audio) and Netflix (video). I noticed the last few times the battery level was pretty low -- i.e., approaching 15% -- but I can't say if this has been the case every time. I think the first time it happened the battery level was higher, but I can't be sure.
I suppose I should look to see if there are any clue in the system logs, but I wanted to know if anyone has encountered this problem before. (Also, I just noticed that when I try to run 'adb' to inspect the logs from my Mac, it says the device is "offline." I haven't seen this before, but I don't know if I've tried to use adb since I installed CM a couple of months ago.) Apart from installing a custom firmware, I haven't done anything else to my device that might make it unstable, like overclocking it.

I'm guessing the kernel is crashing, do you have viper4android installed? I had a similar problem with my cm 10.1 os a few weeks back, when having keyboard sounds on and typing really fast with viper on my kernel was crashing. If you don't have that or acid installed, then try wiping the system partition and reflashing the ROM, you won't lose any data. You might be able to debug it by continuously using your kindle while hooked up to your PC and running adb logcat, and waiting for it to crash and seeing what it said last in the log before it crashes. Idk if kernel errors show up there though, and I dunno how to view a continuous view of the kernel log outside of repeatedly running dmesg.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Several users have been dealing with a similar issue regarding CM10.1. I would suggest upgrading to 10.2 or trying a different ROM altogether to see if you get the same results.

@stunts513: I don't have viper4android or keyboard sounds, but it does seems like the kernel is crashing. I haven't had time to figure out why adb isn't working for me right now, but when I do I'll see if I can make it crash and watch the log.
@soupmagnet: Thanks for the tip. I've been waiting till the next build of 10.2, but maybe I'll give it a try sooner.
stunts513 said:
I'm guessing the kernel is crashing, do you have viper4android installed? I had a similar problem with my cm 10.1 os a few weeks back, when having keyboard sounds on and typing really fast with viper on my kernel was crashing. If you don't have that or acid installed, then try wiping the system partition and reflashing the ROM, you won't lose any data. You might be able to debug it by continuously using your kindle while hooked up to your PC and running adb logcat, and waiting for it to crash and seeing what it said last in the log before it crashes. Idk if kernel errors show up there though, and I dunno how to view a continuous view of the kernel log outside of repeatedly running dmesg.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
soupmagnet said:
Several users have been dealing with a similar issue regarding CM10.1. I would suggest upgrading to 10.2 or trying a different ROM altogether to see if you get the same results.
Click to expand...
Click to collapse

jay-roc said:
@stunts513: I don't have viper4android or keyboard sounds, but it does seems like the kernel is crashing. I haven't had time to figure out why adb isn't working for me right now, but when I do I'll see if I can make it crash and watch the log.
@soupmagnet: Thanks for the tip. I've been waiting till the next build of 10.2, but maybe I'll give it a try sooner.
Click to expand...
Click to collapse
I had the same issue with 10.1. I upgraded to 10.2, same issues. Random shutdowns. Sometimes it doesn't even load CM all the way before crashing when starting up the KFHD. Should I create a new thread or continue here?

GrecoISU said:
I had the same issue with 10.1. I upgraded to 10.2, same issues. Random shutdowns. Sometimes it doesn't even load CM all the way before crashing when starting up the KFHD. Should I create a new thread or continue here?
Click to expand...
Click to collapse
Going from CM10.1 to CM10.2 doesn't really rule much out if they are both from the same developer/device tree/etc. Have you tried installing a completely different ROM like Kinology or PA to see if the results are the same?

soupmagnet said:
Going from CM10.1 to CM10.2 doesn't really rule much out if they are both from the same developer/device tree/etc. Have you tried installing a completely different ROM like Kinology or PA to see if the results are the same?
Click to expand...
Click to collapse
No. I haven't yet. I've been a bit apprehensive about it. Can I just download, move to SD, then wipe and install?

GrecoISU said:
No. I haven't yet. I've been a bit apprehensive about it. Can I just download, move to SD, then wipe and install?
Click to expand...
Click to collapse
I don't see why not

soupmagnet said:
I don't see why not
Click to expand...
Click to collapse
I followed all directions for Kinology but I'm getting crashes every time I try to unlock the lockscreen. Only twice I've seen the setup options (language) and both times it's crashed prior to making a selection.
Edit: Redid everything following directions and I'm still getting a lockscreen crash as I swipe to unlock.
Edit 2: I'm just going to restore completely and try everything fresh.

If I remember right, when going from a amazon os to a cm ROM and vice-versa, you need to do a factory reset before you flash the ROM (kinology), also wipe cache, dalvik cache, and system before the flash.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
If I remember right, when going from a amazon os to a cm ROM and vice-versa, you need to do a factory reset before you flash the ROM (kinology), also wipe cache, dalvik cache, and system before the flash.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
this^^

Related

[Q] Rooted Nook HD+ boot problem

A question for any intellectual Android/Nook-addicts out there...
Basically, I've rooted my Nook HD+ (Numberous times now) and have experience rooting android devices in the past and have had no problems. I used the CWM method - installed universal root on factory stock (And afterwards, 2.1.0 stock just to see if it fixed the problem... it didn't) and extras (Tried not installing extras twice also, didn't make a difference)
Basically, I've learnt the hard way that eight resets on boot and the device hard-resets to factory stock. The first Root Bootup is fine (The bootup after removing the CWM sdc) and, after turning it off and on again, so is the second bootup... But the third one is where the problem occurs. I power on as normal, and the standard 'Nook' screen appears as it begins to boot...
It then proceeds to resetting itself eight times - never getting past the 'Nook' screen that appears at the start of every bootup, therefore causing a hard factory reset.
I've tried using the CWM recover method to the OS I used before rooting the nook originally, and there doesn't seem to be any problems if the device isn't rooted. I've also just let it update itself from factory version to current version - and it works fine with that also.
Perhaps this is common and I'm just a plain idiot. I honestly can't find any answers - so if it is common, sorry for wasting your time!
Thanks for your time!
- P
Do you have some apps being automatically installed by Play Store? Sometime people have their settings set so that happens. Then a root app gets installed and makes some changes to /system and causes a reset. Go to Play Store and tell it not to automatically install or upgrade apps.`
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Do you have some apps being automatically installed by Play Store? Sometime people have their settings set so that happens. Then a root app gets installed and makes some changes to /system and causes a reset. Go to Play Store and tell it not to automatically install or upgrade apps.`
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
No apps that automatically download that i can see. But you're likely onto something - I do install all the apps manually (No matter how menial) (Going through the list, hitting install for each of them) before manually logging into each one afterwards. I do use a few root apps - no ad-versions to avoid those annoying popups, Ultrabox, Superuser, Pimp my Android and Root Browser to name most, if not all of them.
I'm going to have to do things the awkward way now, installing each app, setting them to the setting I want for them, and seeing what happens. I have a mild suspicion it's a setting on Pimp my Android...
I'll let you know if I sort it. Thanks for the suggestion :cyclops:
P Complex said:
No apps that automatically download that i can see. But you're likely onto something - I do install all the apps manually (No matter how menial) (Going through the list, hitting install for each of them) before manually logging into each one afterwards. I do use a few root apps - no ad-versions to avoid those annoying popups, Ultrabox, Superuser, Pimp my Android and Root Browser to name most, if not all of them.
I'm going to have to do things the awkward way now, installing each app, setting them to the setting I want for them, and seeing what happens. I have a mild suspicion it's a setting on Pimp my Android...
I'll let you know if I sort it. Thanks for the suggestion :cyclops:
Click to expand...
Click to collapse
Why are you installing superuser? It is already installed with the universal root. That may be it too.
Edit: And some of the apps I put on there are old on purpose. Like Root Browser. I have it set so that the free version is ad free. If you update it, the ad free goes away.
Sent from my Nook HD+ running CM10.1 on emmc.
I am VERY sorry it's taken me so long to reply! Even though I've only just joined, I should have done it long before now.
I found the problem - it was 'Pimp my Android' app. I was experiencing something called 'boot loop' - so much for my research skills for such a common problem. I fiddled about with my usual settings - and found some that cause it to get stuck like that, even when they're set not to activate on startup!
Tis' all working now. Everything else seems to be just peachy! You were right, thanks for your help

[Q] reset to factory settings a rooted KFHD 7" and install Cyanogenmod on it

Hello everyone,
My name is Marika and I'm quite desperate! in fact, I decided to register on this forum because I can't figure out how to "save" my Kindle Fire HD 7".
I must say I am a total novice and working on a Mac, but I have access to a PC with Windows and Linux, too.
My problem is the following: I rooted my KFHD to install Google Play store and I installed Go Launcher EX and HD because I hated the carousel and wanted a nice tablet without necessarily showing everyone what was going on on my device.
I don't know if something went wrong but everything worked just fine until I noticed that even if I tried it, I couldn't update my KFHD from Amazon. I tried to ask the troubleshooting service and they told me I had to send back the device and they would send me a new one; so I tried to wipe it clean and unroot it otherwise they would charge me for the second device. The unroot part was fairly easy, and I tried to restore it to the factory settings by the default button inside the device, everything was cancelled but I couldn't update it, still, plus I noticed that the Go Launchers were still there. I re rooted it in order to try to remove the files manually but I couldn't figure out what to do, the only thing I know is that I have no "uninstall" button on these apps so I can't get rid of them, can someone help me? I would like to install Cyanogenmode now instead of those...
Thank you in advance for your time and sorry if this problem was already posted somewhere else, but I couldn't find anything similar to my case!
I'm confused, why area you trying to remove this stuff if you want to install CyanogenMod, when you install cyanogen mod it wipes everything including the os and excluding the sdcard, so there's no point in removing launchers. It sounds like you thought cm was a launcher, am I right or not understanding this right?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
actually no, I didn't think that Cyanogenmode was a launcher; I just thought that the Go Launchers would stay loaded on it anyways and that I needed to get rid of them to install the OS.
I would also like to figure out what could have happened to the KFHD to behave in a such way, because maybe there's really something that doesn't work and it's better if I get a working one while the warranty is still active, that's why I needed/wanted to do what I explained.
Thank you for your reply!
Well when flashing cm it you will basically factory reset, and the launchers that are stored in/system/apps will be wiped too, because everything in /system is deleted when you flash it. As for the updates you could always just restore a older version of amazon os and it would probably fix it, but why do you want to update the os? Most people disable updates so they don't have to keep rerooting it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
yeah probably it's easier and better to install cm right away without any other troubles!

[Q] Kindle App crashes on start (CM 10.2)

I'm running CM 10.2 on my Kindle. Whenever I run the Kindle app it crashes instantly. I've tried clearing the cache, clearing all data, rebooting, backup and restoring from Titanium, and reinstalling from the Play store. Is there a fix for this?
StormConjurer said:
I'm running CM 10.2 on my Kindle. Whenever I run the Kindle app it crashes instantly. I've tried clearing the cache, clearing all data, rebooting, backup and restoring from Titanium, and reinstalling from the Play store. Is there a fix for this?
Click to expand...
Click to collapse
I've been having this problem since the Kindle app upgrade on December 17th came out. I was on CM10.1, but I've upgraded to CM11 and it still does it. I think something is wrong with the way the new version works. The best thing is to go back to an earlier version, but unfortunately I can't find it anywhere, and I don't have any back-ups!
(Edit - here's a post with the older APKs - try one of these on for size. http://forum.xda-developers.com/showthread.php?t=2576131)
Kindle app on rooted Kindle has a workaround
Kindle app crashing has a workaround: http://forum.xda-developers.com/showthread.php?p=48928053#post48928053...
Short answer:
download Build.prop Editor from the Play store and use it to change the ro.product.manufacturer line from Amazon to Samsung.
:good: :good:
Gman650 said:
Kindle app crashing has a workaround: http://forum.xda-developers.com/showthread.php?p=48928053#post48928053...
Short answer:
download Build.prop Editor from the Play store and use it to change the ro.product.manufacturer line from Amazon to Samsung.
:good: :good:
Click to expand...
Click to collapse
Did this work for anyone, would like to know before I change to CM
kevorski said:
Did this work for anyone, would like to know before I change to CM
Click to expand...
Click to collapse
This absolutely worked for me. I even went ahead and later put KitKat on the Kindle Fire.. Same issue with the kindle app.. kept crashing.. I downloaded this other app.. changed the entry.. and it's good to go again.
Gman650 said:
This absolutely worked for me. I even went ahead and later put KitKat on the Kindle Fire.. Same issue with the kindle app.. kept crashing.. I downloaded this other app.. changed the entry.. and it's good to go again.
Click to expand...
Click to collapse
Awesome. Downloading cm10.1.3 right now as we speak. Have you had any other luck with any other custom Roms? I've only tried 10.1.3
kevorski said:
Awesome. Downloading cm10.1.3 right now as we speak. Have you had any other luck with any other custom Roms? I've only tried 10.1.3
Click to expand...
Click to collapse
I've run 10.2.1 (stable) without any issues at all... and am currently running cm-11-20140104-SNAPSHOT-M2-otter.zip (snapshot). No issues that I know of but it's my wife's Kindle and I certainly dont push it or load it up like my own Nexus 7.

[Q] CM10.1 freezing/sluggish

Hey all, I recently followed all the guides on here to update my TP. Was runningn CM9 for over a year, and needed a change. Decided on Jcsullins snapshot, cm-10.1-20131210-SNAPSHOT-VPN-tenderloin.zip, as I need bluetooth and camera to work, and also wanted low battery drain. Did a complete acme uninstall of android, repartitioned system to 600mb, and then used tptoolbox to install.
Now, the rom was very smooth through setup. However, after I started installing apps, about 30, it became very sluggish. pressing the home button I would have to wait about 10 seconds for it to actually go home. Apps would take 10 seconds to startup. Web/facebook scrolling was horribly choppy. Interesting though, if I rebooted, the tablet would run very smooth for the first few minutes. Only after that did it start to become slow.
So I decided to reflash the rom. Did a full wipe in CWM, and reinstalled. Again, tablet was running fine. I decided to only install a few apps this time, about 6, and everything seemed fine. But after a few minutes again, it got sluggish.
I'm wondering if maybe using tptoolbox messed something up? From everything I read about that rom, nobody has any problems with it being slow.
Also, I don't really want a heavily modified rom, which is why I haven't tried the Schizoid rom. I would like to stay at 10.1 for stability. I see the official CM nightlies here: http://forum.xda-developers.com/showthread.php?t=2290346
However, there are no download links to that rom, the link goes to the 10.2 download page. I didn't really want to get into a DM rom at this point. And it seems that bluetooth isn't working on that rom? Am I correct in saying that besides Schizoid, jcsullins 10.1 is the only 10.1 with bluetooth fully working?
Hum, got the same problem 1 year ago, my cm partition at the time was full, Using the TP Toolbox, try to give some space to the cm partition sacrificing some from the shared partition. There are more than 1 cm named partition, i don't remember exactly which one at the time was the faulty. Maybe it was the media partition.
sitlet said:
Hey all, I recently followed all the guides on here to update my TP. Was runningn CM9 for over a year, and needed a change. Decided on Jcsullins snapshot, cm-10.1-20131210-SNAPSHOT-VPN-tenderloin.zip, as I need bluetooth and camera to work, and also wanted low battery drain. Did a complete acme uninstall of android, repartitioned system to 600mb, and then used tptoolbox to install.
Now, the rom was very smooth through setup. However, after I started installing apps, about 30, it became very sluggish. pressing the home button I would have to wait about 10 seconds for it to actually go home. Apps would take 10 seconds to startup. Web/facebook scrolling was horribly choppy. Interesting though, if I rebooted, the tablet would run very smooth for the first few minutes. Only after that did it start to become slow.
So I decided to reflash the rom. Did a full wipe in CWM, and reinstalled. Again, tablet was running fine. I decided to only install a few apps this time, about 6, and everything seemed fine. But after a few minutes again, it got sluggish.
I'm wondering if maybe using tptoolbox messed something up? From everything I read about that rom, nobody has any problems with it being slow.
Also, I don't really want a heavily modified rom, which is why I haven't tried the Schizoid rom. I would like to stay at 10.1 for stability. I see the official CM nightlies here: http://forum.xda-developers.com/showthread.php?t=2290346
However, there are no download links to that rom, the link goes to the 10.2 download page. I didn't really want to get into a DM rom at this point. And it seems that bluetooth isn't working on that rom? Am I correct in saying that besides Schizoid, jcsullins 10.1 is the only 10.1 with bluetooth fully working?
Click to expand...
Click to collapse
Atari-San said:
Hum, got the same problem 1 year ago, my cm partition at the time was full, Using the TP Toolbox, try to give some space to the cm partition sacrificing some from the shared partition. There are more than 1 cm named partition, i don't remember exactly which one at the time was the faulty. Maybe it was the media partition.
Click to expand...
Click to collapse
You can check the size of your partitions by typing "df" without quotes into terminal emulator.
Hope this helps.
Thanks for the suggestions. I checked the partitions, and they are all good. I ended up reflashing a third time, and I've been running it for two days, and it's been fine 90% of the time. A few slow downs, but nothing like before.
However I do have another problem, and I don't know if it's rom related or not. I have an HP slim bluetooth keyboard that paired successfully with the tablet. Works perfectly, except if I leave the tablet unattended for about 15 minutes or so, it doesn't work. I'm fairly sure the keyboard itself is going to sleep. However, when I wake it and the tablet up, the tablet freezes completely. Tonight it even rebooted itself twice. Once was on it's own after I tried to wake the keyboard up by pressing a few buttons. The other I turned the keyboard off and back on, and when it was connected the tablet rebooted.
Seem related to a rom problem with drivers support for bluetooth accessory. If it was working before with the same roms, try to reflash it, otherwise, try another roms or early/newly build.

Nook HD+ app issues, reboots, now stuck at boot. Help.

I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Kov8 said:
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Click to expand...
Click to collapse
Hi Kov8.
I was running CM 11.1 for ovation and experienced the same thing. My solution was to install a newer version.
To save your data, set up an SD card (be sure you have enough extra room for your data) with the TWRP 3.0.1-0 version here:
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
Load TWRP and look for the File Manager. I think it's under "Advanced." You can use that to copy or move your data to the SD card.
After that, consider upgrading to AOSP or LNOS. I can install AOSP without much difficulty, but LNOS doesn't go well. More on that in a later post.
If you need more detailed information, look at this post and download the pdf at the end of the first post:
https://forum.xda-developers.com/nook-hd/general/install-cyanogenmod-12-1-barnes-noble-t3211119
Kov8 said:
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Click to expand...
Click to collapse
Yes. I've been reading that all the recent ROMs do that.
The solution is to do a standard shutdown followed by a hard shutdown (by holding the power button for 8 seconds).
I suspect that going straight for the hard shutdown caused some file system errors that made installing new ROMs very difficult.
I'm OK now, though.
Thanks for the detailed reply! I will try.
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Kov8 said:
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Click to expand...
Click to collapse
That's funny. I just downloaded two copies from that link.
For version 3.2.1-0, it sounds like you're looking at the version from the team win website. I haven't tested that one thoroughly, but I have tried out their version 3.1.1-0. It works pretty well. It gave me some minor error messages here and there, but if I just repeated what resulted in the error, it generally went through on the second attempt without an error.
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Kov8 said:
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Click to expand...
Click to collapse
Mind telling how you managed to update twrp from 3.0 1 to the latest? I successfully installed 3.0.1 to my nook hd+, then flashed 3.2.1 img to recovery, now the device stuck at boot.
I simply downloaded to img file from their website (for ovation, my device), placed on the micro-sd, and installed it from TWRP itself. As simple as that.
Are you sure that you got the correct version for your device?
I also always verify the integrity of roms after writing them to a card. I've seen bad cards.

Categories

Resources