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.
Related
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?
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 had this problem for a while now. Whenever I shut down or reboot my nook it will reboot on its own over and over for quite some time.
It seems random, sometimes rebooting only a few times, but most of the time it reboots many, many times.
It'll get to the main screen, start loading stuff, then reboot.
I just recently figured out that if I turn the screen on and off rapidly for a few seconds it will interrupt whatever is causing it to reboot. But this does not always work.
I'm using cyanogen, and I think it started while using a nightly. I then tried a couple newer nightlies, then the stable 7.0, then newer nightlies, then the stable 7.1, and now the most current nightly.
Anyone have any idea what's going on? It's driving me nuts.
Could someone point me to a good tutorial on installing cyanogen, with how to format correctly and such? I would not mind starting from scratch with this, formatting it and everything.
Thanks so much.
Ok, first off are you running from an SD card? If so what is the brand and class?
Sent from space
No, its installed on internal memory. I do have an SD card that I use for storage, and its a Sandisk 16GB.
Well, I followed this guide: http://forum.xda-developers.com/showthread.php?t=1160424 and paid special attention to the partitioning section at the beginning because I have a blue dot version. I then installed the most current nightly of cyanogen and google apps. I also formatted /data a couple times and formatted /cache.
I did not get the rebooting problem.
Was it something to do with the partitioning?
And now its doing the reboot thing again. Just got most of my apps reinstalled and decided to reboot to see if it does it. And it does.
Any ideas?
Didn't know the root cause yet but first thought, could you redo the fresh installation, flash gapps but do not install any app. Try to reboot a few times to see if problem persisted. If not, thinking about what kind of app you installed.
That's what I figured I'd have to do. But first, I want to try to completely remove flash. I remember reading about flash causing rebooting somehow.
Anyone know how to get rid of all traces of flash? And adobe related stuff for that matter.
First off are you using beautiful Widgets? That causes a lot of problems. If that isn't it try installing your apps one by one and see what app it causing the problem.
Sent from my NookColor using Tapatalk
Not using beautiful widgets, but am using a few standalone ones. Bobclock d3, temp+cpu v2, text battery widget, and that power control one.
I uninstalled all downloaded apps, a couple to a few at a time. I got all the way down to just the basic google ones, nook tweaks, and a couple other ones I can't remember off hand.
At one point the endless reboot problem stopped.
So now I have started reinstalling apps one at a time, rebooting after each install. So far I have gmail, maps, market, nook tweaks, and youtube installed.
I will keep going through my list of apps, one at a time. It's a very time consuming ordeal, but gotta do it I guess.
I'm pretty sure it was nook tweaks. I reinstalled it and checked all the settings, and the rebooting stopped.
Not sure exactly what was wrong with it to be honest.
Anyone have any similar problems with nook tweaks?
Nook Tweaks may be causing my problem...
nookle said:
I'm pretty sure it was nook tweaks. I reinstalled it and checked all the settings, and the rebooting stopped.
Not sure exactly what was wrong with it to be honest.
Anyone have any similar problems with nook tweaks?
Click to expand...
Click to collapse
Apparently YES!
I have been having the same problem, random reboots. Not full boots, just a soft restart. And I dreaded having to actually do a full shutdown or reboot, because it would lead to a bunch of soft restarts. Drove me nuts.
This occurred on my original NC (old partitions, CM7 nightlies, stable and Mirage), and on my replacement one for a bad speaker (refurb has new partitions, Mirage with V6 and PDroid added).
So after reading this, I uninstalled Nook Tweaks and have been thrashing it for the last two days. Hallelujah! No reboots!
I no longer fear doing a shutdown and restart! Stability at last!
After a while, I'll probably reinstall Nook Tweaks to see what happens.
Thankyou, thankyou, thankyou for your post. Somehow, it never crossed my mind to think that Nook Tweaks might be the culprit.
Hi Guys,
I am not sure if I am posting in the right place, but I could use some assistance on the Team EOS nightlies. They won't let me post in the DEV section yet, becuase I am mostly reader, not a poster. Anyway....
I've been running the EOS roms for a while, but I can't seem to run any nightly past 74. 74 runs great, when I tried to update to 75 (rom/gapps/wipe cache) it won't get past the "DUAL CORE" logo. I thought I bricked my xoom, but I am able to boot to recovery, reflash 74 (gapps/wipe) and it boot with no issue. I did a full wipe, and tried again with 76 but no joy (77 wasn't out at the time). I thought it was a problem with n75 and n76. I flashed back to n14 and it works fine, and I can upgrade back to n74. Tonight I tried to update again to n77, but still no dice. I let it sit for 15 minutes at the "Dual Core" logo, and all I noticed is that is got warm, but still no boot.
Any thoughts? All advise is welcome!
BTW, this is for a Stingray 4g xoom
And while I have your attention, I love the work you guys do, and this community, it really makes Android something special!
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Still not working right, very frustrated, but I have new information
dellenrules said:
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Click to expand...
Click to collapse
bigrushdog said:
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Click to expand...
Click to collapse
Thanks to both of you. I did try this. What I have discovered so far is that some of the flashing fun I have been doing with my may have caused so minor issues with my external SD Card. I backed up the internal to it, and pulled it. I went through the process of nuking the xoom entirely. I.E. Wiped Cache, dalvik, full wipe, factory reset, reset permission, and deleted everything off the internal SD (wasn't in this order, but it all got done) I was able to flash N77, without GAPPS fine. It seemed to run faster with nothing else installed. Rebooted a few times, no problem. I was stoked. I flashed gapps, 03-17 version (the latest). factory reset again so that it was fresh and wiped the cache (just in case). It booted again no problems, ran me through initial config, and then began downloading my apps back. It seemed to run much faster than it ever did before.
Then I rebooted it, without doing any titanium backup restores, just fresh tablet, N77 with my 90 or so apps freshly installed from the market, and it froze again at the "Dual Core" boot screen. I waited hoping for some delayed joy, but none came.
So I went back through the process once again, factory reset, N77 install, wipe cache, install GAPPs. Booted.....initial config, auto downloaded 90 apps from market, reboot......dead.
So then I just flashed N74 again, wiped cache, install GAPPS, initial config, app download.....reboot.......works fine.
<general frustration directed at tablet, not anyone here/>
What gives???? I can't tell what the difference in internal apps in the ROM are that could be conflicting with the ones installed from the market.
Why the hell is N74 working and N77 not, when the apps in both ROMs look the same?
Why does N77 work great when the apps aren't restored?????
Why don't I make a million dollars?????
Why aren't I emperor of the universe???????????????
</general frustration directed at tablet, not anyone here>
Thanks much for all your help!
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
fkntwizted said:
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
Click to expand...
Click to collapse
He has the STINGRAY not the WINGRAY Xoom.
N77 is the latest for the 4G version. The version he has.
Read the OP
EOS Nightlies hate my xoom, my Xoom wanted CM9 I guess
joshndroid said:
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
Click to expand...
Click to collapse
Thanks much for this. I had already attempted the formatting of everything except the SD card before.....but for sh*ts and giggles I tried it one more time. unfortunately that didn't work.
Using the second option, of reverting stock, I went through sleeplessnija's tutorial on reverting. It really didn't seem that bad, taking me longer to setup my work machine than it did to send the fastboot commands. I was able to get it to boot stock (of course I didn't re-lock it) just fine, and it was quick....so it seems like my hardware is fine.
I used fastboot to put the replacement tiamat recovery, and formatted everything in the mounts menu again. I also mounted my SD card as USB storage and used the full format for it under windows. Then i copied N77 and GAPPS back to it, and re-installed them. It got to the second boot logo (first was the shaking team eos, the second is the square thing with rounded corners that moves). It hung for about 10 minutes, and I shut it off. annoyed.
So I went back into recovery, mounted my SD for USB access from my desktop, and copied the unofficial (which I think is now official) CM9 distro from Team Rogue (Steady's Rom I believe?). I formatted everything, and wiped everything (except the SD) again, and installed CM9 and gapps. Booted fine. Configured account, downloaded 90 apps, rebooted, no problems. Played with it for a while, rebooted....no problems.
I like that my xoom is back up and running......however it seemed that Steadies rom is just a little less fully featured than Team EOS. THAT IS NOT A KNOCK AGAINST TEAM ROGUE OR CM9.....my Xoom is working again (so far) thanks to him (them), and I run CM9 on my AT&T GSII. I just really like Team EOS on my Xoom, and have been with them since the beginning. I would love to know why my xoom suddenly hates the latest nightlies (everything since 74).
Edit: I forgot to ask, Joshndroid.....you mentioned running logcat to see what going on. If it can't boot past the dual core logo or the second boot logo from Team EOS....how do I get the logs? I am not familiar with android's logging.....even though I am a flash-a-holic. I am just thinking that if this is happening to me, maybe I can help out the devs (and myself, and maybe someone else) with the log output.
Edit 2: And Josh.....I forgot to tell you .....good call on the revert to stock answer. I didn't think about that before and thought I was screwed!
Thanks!!
Hi!
I recently updated my ROM to the Paranoid Android 3.98, I did a full wipe, flashed the ROM, latest Gapps (with TWRP) and ever since the tablet has been become really laggy on opening apps or doing anything. I realised something was wrong straight after I booted it up by how long it was taking to connect to the WIFI etc.
Anyway, its hanging a lot on the unlock screen and sometimes I get a "Process System is not Responding" prompt. I've tried going back into recovery and clearing the caches/data again and its still hanging. Ive also tried using CWM recovery to wipe the tablet, flash the ROM/Gapps etc and its still really slow. Lastly, I just tried a factory reset from the settings menu and again, its still the same!
Any ideas on whats up with it and how to sort it out? I was thinking about unrooting it back to stock although I think the problem will still probably happen. I came from the PA 3.95 build and did a clean flash.
Cheers!
Chris
I think I have fixed it by following a post by Chasmodo on how to do a super-clean install.
1) I booted into recovery.
2) Did the three wipes (Data, Cache, Dalvik) several times over.
3) Went to Mount & Storage and formatted both system & cache*.
4) Flashed PA 3.98 & latest PA-Gapps.
5) Wiped both caches again and rebooted.
As soon as connecting WIFI, signing into Google I could tell it was running a lot faster again and now the lag on the unlock screen & opening apps seems to have stopped, also haven't had the "System Process isn't Responding since."
*Chasmodos version of the super-clean install didn't say to format the cache as well although I had tried just formatting the system and it didn't fix the issue. So I thought I'd try the same process with a cache format as well and now all issues seem to have been rectified.
Cheers
Chris