5 replies to this topic

[envygreen]

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.  I tried pulling the sd card.  No luck.

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?  So I went ahead and updated SU.  

But the second I reboot, I have the same problem unless I race to undo the overclock again. Tried flashing various nightlies now that SU is updated, still no joy.

Anything I can do to fix this?  Or am I screwed and need to find an old backup or start from scratch again?  Did this really happen because I updated to a nightly without having the latest version of SU installed?

[spdrfall]

What I had to do was factory wipe and fresh install. The SU update staved off something from crashing the OS on boot, but I couldn't/didn't pin it down any farther than the system would only stabilize after I got that quick OC.

[envygreen]

Ouch.  Now I'm wondering when my last full backup was and what I've done since then.  Hopefully nothing much!  Thanks spdrfall.

[patruns]

I have never installed an app called super user. It's there but I assume it was part of CM7. In any event, try disabling the widget. Also, uncheck the "on boot" box in the CPU settings for now until you have it running smoothly.

[envygreen]

Yeah, SU is part of the install.  Disable which widget?  Another thread discussing this, they removed all widgets and that didn't resolve, but I can try next time I have time to troubleshoot.

I did unclick the on boot box, but it's not properly saving because when I reboot, it's back to being overclocked and I have to go back to the settings and drop the speed again manually or it crashes and restarts.

[patruns]

You mentioned a clock widget. Frankly, I would uninstall any widgets that load on boot until you resolve your issues.

Ok, did you lower the CPU settings and then click on on boot box? If it still doesn't stick I would consider a fresh install and wipe everything. If you can keep it running, use Titanium Backup for all of your apps and data first so you can restore them later.