I've seen a couple of threads that explain how I ended up where I am I think, but nothing so far on how to get out of it. So, any advice?
I updated to the 209 nightly the usual way (emmc install via clockwork recovery after wiping cache and dalvik) and it booted, started loading my home screen and clock widget, and then crashed completely and rebooted. Repeatedly.
I tried fixing permissions. I tried downgrading my version to 207, I tried upgrading to 210 and later 211. It either freezes or reboots.
After reading that the latest version of superuser needed to be installed before updating nightlies to avoid this type of problem and that it tied into overclocking, I was able to get into my nook by quickly going to the overclock settings and taking my max cpu down to 600 before it had a chance to lock and reboot. Yay right?
But the second I reboot, I have the same problem unless I race to undo the overclock again. Anything I can do to fix this? Or am I screwed and need to find an old backup or start from scratch again?
Related
I've rooted a half a dozen Nook Colors for friends and family over the past couple of months. I use a microSD card made with this procedure
http://forum.xda-developers.com/showthread.php?t=1030227
I started at N97 and have worked with various nightlies since. I also installed gapps and the OC kernel. Since the OC kernel has been incorporated into nightlies, I just do the latest nightly and Gapps, now
My problem is that immediately after rooting, upon boot up I go through the setup process. I almost always start getting FCs near the end of setup. If I try to install anything from the market I again get FCs. I seldom am ever able to download anything.
I then reboot to the CWR card and do a wipe date and reset to factory defaults. This nearly always fixes the FCs and alllows me to finish setting it up.
Can anyone tell me what I can do to avoid the rash of FCs I get when first trying to run setup? Thanks
Do you check off the box to wipe the Davlik cache when you do the updates? If not, you should.
My nook has been giving me some problems lately. The Market refuses to recognize my user name and password. And this week it has started to lock up and crash a lot.
I'm thinking I just want to reinstall CM7 (or is there something better now?)
My question is do I need to wipe the nook first and then re-root it? If I do wipe it do I need to install the stock nook OS before re-rooting or can I just install CM7 overtop of everything and do it that way? I've done that in the past and that may be part of my problem. I'm not concerned with backing up my data or apps. I can just reinstall them. I don't have a lot on it other than comics.
Thank you.
Boot into recovery, mounts and storage, format cache, format data, format system, then flash your CM7 package, gapps, and whatever else you want as you normally would. I wouldn't think going back to the stock ROM, then back to CM7 would accomplish anything more than just re-installing CM7 would. Also, if you were doing any kind of overclocking don't do it after the clean install until you are satisfied that the performance has stabilized. If do a clean install of CM7 with no overclocking and you continue experience lock ups, you may be looking at a hardware problem.
Awesome. Thank you.
I have been having issues with some apps freezing up or acting on their own. Sometimes shutting screen off then turning back on works, other times cleaning screen works, but doesn't seem to cure the issues. Anyone experience this? Some games include cordy and puffle launch.
I have been running the kanged builds of CM9 for a while, but it began to get bogged down recently and would freeze up almost daily forcing a hard shutdown and reboot.
Sometime yesterday, it began to boot only into recovery no matter what option I tried in the Cyanoboot menu. From there I tried a factory reset and wipe dalvik to hopefully get back into CM9 and here's where the strangeness really kicked off.
Clockwork (which was running off emmc) would freeze in the middle of the factory reset just like it would when CM9 was running (the graphics would degrade slightly upon inspection of the screen).
So, I grabbed my old sdcard with clockwork recovery on it to boot from sd, and I run into the same problem again. Freezing before a wipe, factory reset, or install from sd can complete.
Now, after each failed attempt in clockwork (sd and emmc) it sticks at a backlit black screen and after a hard shutdown refuses to boot (sd or emmc) for about an hour, only to repeat the madness again.
Does anyone have any ideas what I can try from here or familiar with a similar situation?
My sd clockwork version is 3.2.something and I've also tried 3.0.1.something.
UPDATE: For reasons unknown, my Nook seems to be booting regularly as of this morning. However, I am still unable to get a successful flash out of any rom. The closest I've gotten to success is stuck in a boot loop. I think from here I'll likely be able to figure it out, but just as before...
Any help is welcome and appreciated!
I had the same problem with the black screen when trying to install different roms on mine. I just kept clicking the power button and after a few minutes it would kick back on every time.
There is an entire thread specifically on this
http://forum.xda-developers.com/showthread.php?t=949699
As far as CM9 I can't help you much there. I would just try to install a different rom, and hope that works.
Thanks!
I had seen that thread, but I thought my experience was a different; either way, I've managed past that problem using a method similar to yours.
If this helps any, I have been trying to to 7.2 RC1 for a while as well, but it will not get me any further than the stuck boot screen same as the CM9.
Have you tried to follow the tread on returning it to stock ?? I would reformat and repartition it and return it to stock ... then make sure it runs. After that I would try to reinstall the new roms ...
Just my 2 cents
Tinpau
Hey there! I was updating my version of Paranoid Android and my kernel and it seemed fine at first but It yield some odd problems. I went into Clockworkmod recovery and Flashed my rom and kernel I then proceeded to wipe my cache and dalvik cache. I have done this many times before on many devices. I encountered a problem when I rebooted for the second time, I got the Android is updating apps display and I continued to get it every time I booted. The device would also randomly turn off when the screen dimmmed. I proceeded to set out and fix it. Here are the steps I took and the problems it caused.
Flashed stock rom-would not boot properly
Flash RESET kernel-I messed up and though this was a real kernel, my problems escalated from here.
Flashed stock rom and recovery.
Flashed reset kernel and then real kernel-Still had problems.
Flashed stock rom
My problems from all this accumulated somewhat and I can barely boot into fastboot. I get weird static screens and weird white noise sounds. It does not always let me boot into android and will get to the google logo 1 out of ten tries.
These is really unnerving and I have no clues whats what.
Note: I am using Faux123's kernels and his reset kernel.
Thanks a lot for any help!!!
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.
Same issue
Hello,
I am having this exact same issue. Did you ever find a fix for this? I have been searching for hours. I have tried numerous things, flashing back to stock with lg flash tool, installing different roms, it happens on all roms.
Thanks