Quick backstory: I was using CM 10.1 and it started randomly shutting down. I updated to 10.2. Same issues, worse. It seemed like it happened more often between 60% and 40% battery life. I wiped and installed Kinology. It would do about the same thing, I never did get it fully set up after the install.
I decided to wipe the KFHD 7. I used KF First Aide and attempted to restore to 7.2.1, twice. Both times on the restart the Kindle Fire booted to recovery and it nothing I did would work.
Next I used the first aide utility to to update to 7.2.3. Success! Except... It still crashes on the lockscreen.
It is currently to factory settings and I'm still occasionally getting the crash. I assumed with a full restore then reroot and add custom rom I'd have fixed the problem.
Any help would be wonderful... Frustrating having messed with it all day.
Related
I know other people are having this same issue and it is happening to me quite frequntly now ( sometimes twice a day ) ... I could be doing anything or nothing at all and the nook is just sitting there in standby mod, when all of a sudden the NC just reset's itself back to stock. It does not delete anything and the sdcard is fully intact, but the nook is now back to stock and at the setup screen !!! Thank god I have ClockWork Mod installed and a copy to restore, so I can just restore my old system .... but it is just a matter of time until it resets itself again.
What could be causing this ??? Can anyone help me and the others that this happens to, and try and figure out why ?
My NC is running 1.0.1 and is fully rooted (with auto nooter ) and all the little extra's installed ( like geographic location fix and cell service turned off and adhoc support ect... ) I am also using ZEAM as my launcher. Any other info needed ??
There is a post about this in another sub forum here but I think this is a better place to post it.
Thanks for any help with this !!!
John
Just an update to my above post..... now It is factory reseting about every hour. What the heck !! What could be causing this ??
I posted about this on another thread. In my case it seemed to be a mechanical failure of the power button. It was stuck half on and the tiniest movement would trigger it. It actually seemed like the button had dislodged slightly and got stuck under the case. My replacement machine seemed to have a more sturdy case, and also came loafed with 1.01. There's several reports of this on the vanilla NC sites.
Sent from my NC using XDA app
bonobomidwest said:
I posted about this on another thread. In my case it seemed to be a mechanical failure of the power button. It was stuck half on and the tiniest movement would trigger it. It actually seemed like the button had dislodged slightly and got stuck under the case. My replacement machine seemed to have a more sturdy case, and also came loafed with 1.01. There's several reports of this on the vanilla NC sites.
Sent from my NC using XDA app
Click to expand...
Click to collapse
Ummm, well that would have nothing to do with the device reseting into factory default mode. My NC is 100% rooted and even if the power button was to get push in by mistake or by the case, it would not reset the device to stock.
But thanks for the reply ....
Are you using Titanium Backup to restore your apps? Don't restore the system app data. It will mess with the BN authentication, forcing resets.
ewong90 said:
Are you using Titanium Backup to restore your apps? Don't restore the system app data. It will mess with the BN authentication, forcing resets.
Click to expand...
Click to collapse
Mmmm ok I will keep that in mind. Thank you.
Boot Loop Even After Factory Resets
Hopefully my experience will help some other frustrated or novice users that may encounter their NC doing a random factory reset.
The B&N reset happened to me this past Fri. I was on firmware 1.0.0 with 900MHz kernel flash, Zeam, and many market and sideloaded apps. I was not in any B&N apps. I had been using this configuration for 3+ days with no issues (no reboot or reset issues prior to this and had my NC since late Dec 2010). All of a sudden a message stating that the Nook encountered a problem and that the NC would be reset to its original state??? message flashed. Since I had Clockwork installed, the NC simply booted into Clockwork. I had not done a Clockwork backup (read about an incomplete backup). I tried cycle powering, but the NC simply stalled after the black NC screen (the screen after "loading..."). I tried to flash the 1.0.1 kernel that was posted, but still stalled at the same screen. Since Clockwork was installed, I could not figure how to do a two/three finger salute to initiate a factory restore. I tried everything to get out of the boot loop or even perform a factory reset.
I followed NookDev instructions here http://nookdevs.com/NookColor_Fix_Boot_Loops
which for some reason invoked the factory reset (I still had adb functionality at that point). I performed the factory reset, but the process reached the end and indicated that it failed. Upon restart, I had lost Clockwork (probably because the orig boot image was restored) and the NC stalled at the same blank screen again. I did the two finger salute (power button + N button) which started the factory reset process (since I did not have Clockwork anymore). This time the factory reset indicated it completed successfully. However, upon restarting, the NC still stalled at the same screen. I tried several more time to factory reset my NC (from then on indicating successful factory reset), but still stalled at the same screen. Since I had lost Clockwork, I tried to boot of the SD card (flashed with Nook Froyo) thinking that I could adb the boot files onto the NC. Nookie Froyo hung at the "A N D R O I D" msg at the bottom even though adb devices showed 1122334455?? Thinking I had nothing further to lose, but to possibly return a bricked NC, I kept attempting performing factory resets. After the third or fifth (lost count) factory reset, the factory reset that time was different. It read "Performing ??? upgrade." Upon completing and restarting, I finally got past the blank screen I was stalled at. I tested the factory state several times by performing several reboots and several shut downs and boot ups. In device info, it read I was on firmware 1.0.0 which made sense since I had not upgraded to 1.0.1 (1.0.0 should still be the image in ROM). I rooted with Autonooter then installed all my previous apps and flashed the 900MHz kernel. I performed most/all the mods posted including disabling octcerts against upgrades. Yes, I ran a few Clockwork backups!!!
In short, if you encounter the dreaded NC factory reset for no reason, restore with Clockwork/Titanium. If you are stuck in a boot loop as I was (even after factory resets), keep at it. Unless there is something ridiculously wrong with the ROM/NC (hard to brick as other devs have noted), your NC has to restore from the image in ROM. You may have to manually interrupt/boot loop 8 times ??? like I did (24-40+ times???), but keep at it...it should restore.
At some point i had my kindle fire rooted with a jelly bean rom, with twrp recovery installed. I wanted to get rid of my fire, so i decided it was time to go back to the stock rom. In my infinite wisdom, I ended up wiping my factory backup by mistake. I went onto the kindle update site and downloaded the latest official version 6.3 bin file. I then renamed the .bin to .zip and updated it through twrp. When my kindle restarted, the factory OS came up, except I started getting android.acore errors along with another calendar process error. If that wasn't bad enough, it now randomly reboots whenever it feels like it. Luckily I can still usb mount it to my pc and can copy files back and forth. I tried using the kindle fire utility to root it again and install twrp, but no luck. Any ideas? Thanks in advance.
Pretty sure you're in the wrong forum - this is for the KF HD, not the original Fire.
Try your luck here: http://forum.xda-developers.com/forumdisplay.php?f=1306
oops, my bad. Thanks for the heads up.
Hi guys,
I just got two HD+ 32GB and installed cm-10.1-20130527-UNOFFICIAL-ovation-emmc following evergreen and leapinlar's instructions. The installation went well, and I can boot the tablets into twrp recovery. But I cannot boot one tablet into Android. It always hangs on CyanogenMod log (the rotating circle/wheel with CyanogenMod text at the center) when trying to boot into Android. I reboot the tablet several times now and still have the same issue.
I repeated the same procedure on another Nook HD+ 32GB and I can boot the second tablet into Android after several reboots. But I still have no luck with the first tablet.
Any suggestion?
Thanks a lot for the help!
Sean
I installed CM10.1 eMMC on my HD+ for the first time last night and the same thing happened to me. So I went back into recovery and installed the CM10.1 again and then it booted up normally afterwards. So in my case at least it seems like it didn't install right on the first try.
Ravynmagi said:
I installed CM10.1 eMMC on my HD+ for the first time last night and the same thing happened to me. So I went back into recovery and installed the CM10.1 again and then it booted up normally afterwards. So in my case at least it seems like it didn't install right on the first try.
Click to expand...
Click to collapse
Thanks a lot for the suggestion. I finally got It to work by booting into TWRP to wipe system, data, and caches, then re-installing from zips.
Sean
Same issue, apparently (hopefully...) resolved
LIke many other posters here and elsewhere, I installed CM 10.1 on my brand new Nook HD+ 32gb, got it to boot into CWM after many trials and tribulations (I had to reboot about 30 times to get the device to boot into recovery from SD; it crashed halfway through backup in spectacularly frustrating fashion, and it took me about 30 more hard resets to get it to boot into CWM again. I used a brand new Amazon Basics 32gb class 10 card). I did a little victory dance, loaded up some apps (probably too aggressively: 50 or 60 of them), rebooted, and.... you know what happened then, or you wouldn't be reading this (probably whilst sweating and/or crying).
After uninstalling some resource-intensive apps, then booting into recovery and wiping both caches, I was able to reboot normally (aside from waiting a couple of minutes for apps to be "updated" or "optimized" or whatever), but the next and all subsequent reboots failed unless I first booted into recovery and wiped the caches.
Finally, after reading a number of posters with the same problem (including @Ravynmagi and @sean_nj here--thanks, guys), I took a deep breath, did a full Titanium backup, booted into CWM, did a factory data reset, and reinstalled the three zips from the bootable SD. CM booted quickly and normally. I rebooted a couple of times with no problems. I installed a few apps, rebooted normally. I installed a few more apps (including a couple which I sideloaded), again rebooted normally. In the last 18 hours, I've installed a few more apps, played some resource-intensive games, tested Netflix and a sideloaded video, etc.
As of now, the device works like a charm and boots quickly and without drama. If anything changes (and I'm still able to communicate like a civilized human being), I'll make sure to update here.
unable to reboot get spinning logo
I recently updated Nook HD+ to 10.1 w/o problems.Each time I have rebooted it take 2 -3 tries before it finally boots ups. Those other times if boots to the spinning Cyanogen logo. Is there something I can do to check with the system booted up correctly to figure out the problem. If not, what steps should I take now and how do you do a complete backup of all the newly added material since the initial update. Thanks again,
Al
I'm facing the same problems but with a different setup: latest CM 10.2 Carbon ROM release (both versions with and without multiwindow). I have random bootloops and I'm unable to track down the problem.
Are we the only users with those bootloops?
Was searching for this. I am not having a problem booting per se, but all of a sudden I am getting a weird booting thing. Where the logo comes up and spins but its distorted, then it becomes normal looking, then my Nook will kind of reboot. Not a complete reboot just the screen goes black for a millisecond and then the logo starts over again where its all distorted, then it goes normal and then it boots.
I guess you can call it a logo boot loop. The thing is, it doesn't happen all he time, just most of the time now. When it happens, my SD card is incorrectly mounted and I have to umount it and take it out physically and re-insert it.
Nook HD+ 32gb, CM 10.1.3 stable and mbg4ga emmc. Not sure if this is the same as you guys but it sounds related. I've re-flashed several times. I think if you guys can find a cure, then it would probably work for me as well. Quick question, any of you guys using auto-patcher to patch Pdroid? How about Xposed?
For getting caught in the boot loop try:
Settings>Launcher>uncheck wallpaper quick render.
This is for stock Trebuchet 1.0 Launcher. I hope the developers are aware of this.
Probably coincidental but, the glitch caused by the magnetic closure on my case much better.(when you try to unlock and it blinks and goes back to lock).
Good luck.
I am running the 6/13 binary and the system gets stuck when I attempt a reboot. It freezes at the CyogenMod screen with the animation. I have attempted a reboot through powering off, and through the CWM, but I am still stuck. I was previously able to wipe the delvik cache, which worked, but all of the applications had to "optimize" every time before it booted up.
Is there a way to get past this?
I am running a 16GB Nook HD+ with an emmc install. It worked fine for a day, but now every time it boots it doesn't get past the CM animation.
I ended up with the same problem until I realized I flashed one of the nook HD zips instead of the HD+ version. Make sure everything you have says ovation and not hummingbird. Also don't flash any tablet UI stuff until you have a working nook
Sent from my Barnes & Noble Nook HD+ using xda app-developers app
ridetheworld said:
I am running the 6/13 binary and the system gets stuck when I attempt a reboot. It freezes at the CyogenMod screen with the animation. I have attempted a reboot through powering off, and through the CWM, but I am still stuck. I was previously able to wipe the delvik cache, which worked, but all of the applications had to "optimize" every time before it booted up.
Is there a way to get past this?
I am running a 16GB Nook HD+ with an emmc install. It worked fine for a day, but now every time it boots it doesn't get past the CM animation.
Click to expand...
Click to collapse
I've had the same thing happen. I've completely reflashed my HD+, but occasionally it will still happen. Sometimes it does not ever boot correctly and instead when I reboot it, it reloads the Nook software (people say 8 times, but I counted and mine restore Nook software after 5 hard reboots).
If you have your SD card installed, try taking it out. That's what started mine...I put a 64GB card in and it never booted again. Just sits on the circle animation, spinning forever.
Thanks, I will try reflashing everything and see how that goes. I am going to back it up with Titanium First.
hello everybody!!
i'll start from the beginning: recently, my TP (16gb) simply crashed. it was running webos and CM 10.1, and everything was fine until it just shut down while i was reading with it. then, when i tried to restart it, it went into a bootloop, and after a while it was just stuck on the cm boot animtaion.
i decided to fix it, so i took the following steps:
1. http://forum.xda-developers.com/showpost.php?p=24047078&postcount=3 - tried it a few times - didnt work, but CM was no longer loading (there was an error message, something abuot memory, cant quite remember)
2. next step was going with the instructions on this thread: http://forum.xda-developers.com/showthread.php?t=1426244.
3. here i thought i've won! http://forum.xda-developers.com/showpost.php?p=33933466&postcount=10 i did that one, and 3rd time was a charm!! webosDR went to 100%, and my TP restarted. BUT!! while i was setting the wifi on, it crashed and it wont boot webos now.
does anybody have any suggestions?
thank you so much for the time you took to read it, and for any time spent to help!!!