Hi folks.
I installed customized nookie froyo five days ago. I also overclocked the CPU, using the "set at boot" option.
I placed the nook on the charger last night, and later noticed it had rebooted, or at least was trying to reboot...
The "nookie froyo" animation during the boot process simply freezes, then tries to restart again, freezes, ad infinitum.
Don't know if it has anything to do w/ the overclocked kernel or not. Is this a common problem? Is there a way to fix it without re-installing?
Thanks!
I actually had the same thing happen to me (OC-ed, endless reboot), I ended up having to restore to stock. I wasn't entirely sure if it was because of the OC-ing, but since you're in a similar situation, it can't be coincidental.
wildkarrde21 said:
I actually had the same thing happen to me (OC-ed, endless reboot), I ended up having to restore to stock. I wasn't entirely sure if it was because of the OC-ing, but since you're in a similar situation, it can't be coincidental.
Click to expand...
Click to collapse
Did you actually need to restore to stock, or could I just install a different image?
Anybody want to chime in on the current state of the non-stock options? Are CM7 or honeycomb looking pretty stable, or should I stick w/ froyo?
Thanks.
How did you overclock? Via a kernal flash or via setcpu (the app)?
Depending on which you used will determine your next step.
If it simple was a kernal, simply use cwm and flash a new kernal.
Thing i have found to help me the past week has been my rom backups from rom manager.
I have been able to recover from 3 'bad' installs and return to my custom froyo 0.6.8 each time so far.
I use the 0.6.8 on sd to get to rommanager when i have overflashed my emmc.
Sent from my Nook Color (zoom2) using Tapatalk
miniaturepeddler said:
How did you overclock? Via a kernal flash or via setcpu (the app)?
Depending on which you used will determine your next step.
If it simple was a kernal, simply use cwm and flash a new kernal.
Thing i have found to help me the past week has been my rom backups from rom manager.
I have been able to recover from 3 'bad' installs and return to my custom froyo 0.6.8 each time so far.
I use the 0.6.8 on sd to get to rommanager when i have overflashed my emmc.
Sent from my Nook Color (zoom2) using Tapatalk
Click to expand...
Click to collapse
I had used setcpu.
I reinstalled, using ultimate droid 3.1.2.
Good to hear you are back up and running then.
Question: How far did you push your Nook?
I am using the Setcpu with mine and have it set at 1000 as the max.
Robyn
miniaturepeddler said:
Good to hear you are back up and running then.
Question: How far did you push your Nook?
I am using the Setcpu with mine and have it set at 1000 as the max.
Robyn
Click to expand...
Click to collapse
I was allowing it to max out (1100).
mrfeh said:
Did you actually need to restore to stock, or could I just install a different image?
Anybody want to chime in on the current state of the non-stock options? Are CM7 or honeycomb looking pretty stable, or should I stick w/ froyo?
Thanks.
Click to expand...
Click to collapse
I recently tried HC (Deeperblue version, not the new customized version). It's really interesting, but definitely still a work in progress. I'm currently using Phiremod 5.0, and it's fantastic. 5.1 was released last night, but I haven't had a chance to update.
human0metronome said:
I recently tried HC (Deeperblue version, not the new customized version). It's really interesting, but definitely still a work in progress. I'm currently using Phiremod 5.0, and it's fantastic. 5.1 was released last night, but I haven't had a chance to update.
Click to expand...
Click to collapse
Has anybody used both UD 3.x and phiremod? Could you compare and contrast them?
Thanks!
Related
So I'm picking up a Nook tomorrow and have been doing some research on the available hacks. It seems like for me, for the time being, a rooted 1.1 is going to work best. Once honeycomb (or cm7) are stable daily drivers, I'll be switching to one of them.
Anyway, I wanted to run my upgrade plan by everyone to make sure it sounds okay. I'm not new to android hacking (have a DInc and a DX) but this will be my first nook. Here's what I'm thinking:
1) Fire up and run through OOBE - Register device with BN
2) Once the OOBE finishes, immediately turn off wireless.
3) If not already on 1.0.1, download updates and install.
4) Apply audonooter 2.12.25
6) Install ROM Manager and Clockwork Recovery
5) Apply Decad3nce's V1.1.0_r2 ROM
Does that sound right? Am I missing anything?
After everything I've read, what you got seems to be the most reliable method. Except your number order is a little out of whack. Steps 1-4 are best done following http://nookdevs.com/NookColor_Rooting.
In fact, I'm going through this exact method to do a fresh install on my NC to try to eliminate quirks I have with wireless and the Gmail app on my current 1.1 install. But if this fresh install still has the quirks, I'm going back to 1.0.1 and the block patch found at http://forum.xda-developers.com/showthread.php?t=922870&highlight=cwm to prevent 1.1 being pushed automatically to my NC.
Why not just get updated to 1.1.0 and use Autonooter 3.0?
thanks fug!!!
how about OC'ing. after all said and one... i was thinking of then applying dalingrin's 950 OC. safe to do when not on froyo?
jerrykur said:
Why not just get updated to 1.1.0 and use Autonooter 3.0?
Click to expand...
Click to collapse
i've read there's problems running CWR when using autonooter 3. i don't mind spending a little extra time to make sure CWR works properly.
byproxy said:
thanks fug!!!
how about OC'ing. after all said and one... i was thinking of then applying dalingrin's 950 OC. safe to do when not on froyo?
Click to expand...
Click to collapse
No problem!
Honestly, I think there is no reason not to just go for the 1.1 GHz OC (the kernel-1100mhz-omap3630.zip file). I was running 1.1 GHz before my fresh install (which I've already finished) and I'll soon be running at that speed again. I guess if you want to go to 950 MHz and "break in" your new NC, then by all means. But at the time before I OC'd, I felt there was enough people that were able to go to 1.1 GHz without issues. Then again, I had my NC for 2 weeks before I tried OC'ing.
Also, a few friendly tips. Open up and power up your NC in the store and make sure there aren't any issues with your unit. Also, bring a pair of headphones with you to the store. Around the time I bought mine (just after Xmas), I read posts about headphone jack issues, dead pixels and other weirdness out of the box. I don't know if those quality issues are still out there but you never know.
jerrykur said:
Why not just get updated to 1.1.0 and use Autonooter 3.0?
Click to expand...
Click to collapse
byproxy is right about the feedback that Autonooter 3.0 is not compatible with CWR. There are enough posts confirming that. It's not worth the trouble. The method laid in the OP is the best way to maximize the NC, in my opinion.
I just Updated to 1.1 via B&N normal update path, used Autonooter 3.0 and then Used a CWR SD Card to flash the 1.1ghz Kernel . Easy as Pie.
I'm currently using 2 NC's. I've messed around with some of the different options out there. This week I tried hard to make Nookie Froyo 0.6.7 my preferred hack for day-to-day use but there are too many things I can't get working right. Anyway, I'm going back to the combination of Auto-Nooter 2.12.25 and Decad3nce's V1.1.0_r2 ROM for the time being.
Thanks again! Maybe I will go right to 1.1. Honestly my concern wasn't stability. It sounds like for someone who's experience and comfortable hacking an android device like this - they're pretty unbrickable.
My concern actually was the potential to fry the CPU. Has anyone run temp readings across different OC's levels to see how much hotter the CPU is getting at the higher speeds?
A crash is no problem... easy to fix. A cooked processor is $250 down the toilet!! LOL
fugitoid said:
No problem!
Honestly, I think there is no reason not to just go for the 1.1 GHz OC (the kernel-1100mhz-omap3630.zip file). I was running 1.1 GHz before my fresh install (which I've already finished) and I'll soon be running at that speed again. I guess if you want to go to 950 MHz and "break in" your new NC, then by all means. But at the time before I OC'd, I felt there was enough people that were able to go to 1.1 GHz without issues. Then again, I had my NC for 2 weeks before I tried OC'ing.
Also, a few friendly tips. Open up and power up your NC in the store and make sure there aren't any issues with your unit. Also, bring a pair of headphones with you to the store. Around the time I bought mine (just after Xmas), I read posts about headphone jack issues, dead pixels and other weirdness out of the box. I don't know if those quality issues are still out there but you never know.
Click to expand...
Click to collapse
1. Buy your nook color
2. Turn it on, and register the device
3. Update to 1.1 using Sideload or wait for your device to update itself
4. Use AutoNooter 3.0 to root it
5. Enjoy yourself until CM7 comes out
therealguppy said:
I just Updated to 1.1 via B&N normal update path, used Autonooter 3.0 and then Used a CWR SD Card to flash the 1.1ghz Kernel . Easy as Pie.
Click to expand...
Click to collapse
However, can you backup your NC with that bootable CWR? If you used one of the images from Monster RootPack 0.5, backup is not working yet.
Still, I rather have CWR right on the NC instead of having to keep a separate bootable CWR handy.
fugitoid said:
However, can you backup your NC with that bootable CWR? If you used one of the images from Monster RootPack 0.5, backup is not working yet.
Still, I rather have CWR right on the NC instead of having to keep a separate bootable CWR handy.
Click to expand...
Click to collapse
okay...noob question again...what is CWR and what does it do?
Omega Ra said:
okay...noob question again...what is CWR and what does it do?
Click to expand...
Click to collapse
No worries.
CWR is short for ClockworkMod Recovery. It's basically a recovery platform for many, such as the NOOKcolor, but not all Android devices. A very watered down analogy is CWR is like using a Windows Repair CD (or better yet Hiren's Boot CD, if you're familiar with that) for Android devices.
A lot of the modifications (such as dalingrin's overclocking kernels) and development ROMs (such as cicada's Nookie Froyo) use CWR to make mod'ing much easier.
CWR is a must have tool for those who root and flash frequently. It will get you out of a lot of jams.
oh okay, so since I only really plan to root once and more or less leave it at that it shouldn't be that important for me then.
Omega Ra said:
oh okay, so since I only really plan to root once and more or less leave it at that it shouldn't be that important for me then.
Click to expand...
Click to collapse
i'd still do it. something may get screwed up and it would be nice to have a nandroid available to restore.
I have heard there are problems with CWR and AutoNooter 3...so we'll see.
Omega Ra said:
I have heard there are problems with CWR and AutoNooter 3...so we'll see.
Click to expand...
Click to collapse
Yeah its not Autonooter 3 its the 1.1 update, if you flash CWR to your device instead of using a stand alone card, you will get stuck in the CWR next time you boot and you will have to re-flash your boot partition before you can boot normally again.
You can still use the Stand alone CWR SD card to use the tool.
So, picked up the ol Nook this evening and proceeded with a very slightly modified version of my afore mentioned steps (thanks to fug for the input!). Here's what I did exactly:
1) Fired up and ran through OOBE - Registered device with BN
2) Once the OOBE finishes, immediately turned off wireless.
3) If not already on 1.0.1, download updates and install (I was already on 1.0.1 so was able to skip this step).
4) Root using audonooter 2.12.25
6) Fired up wireless again and installed ROM Manager and Clockwork Recovery via market.
5) Flashed Decad3nce's V1.1.0_r2 ROM
7) Created nandroid (CWR backup)
6) Flashed 1.1ghz OC Kernel
So far so good! Will report any problems if if/as I encounter them!!
I bought a nook color yesterday so I could get in on the rooting and roming fun as well. It came with 1.0, which I've already rooted and am now running HC from an SD card. A bit slow, so I'm planning on trying to install it internally. 2 Questions:
1. Is their any reason I should stay at 1.0? Or should I upgrade to 1.01 or 1.1? Will I be able to go back to 1.0 if I want using the 8 reboot method?
2. If I install HC to the internal memory, will I be able to restore to stock? I'm not sure I'm going to keep this device yet so I don't want to do something that will make it impossible to return to stock.
Thanks
1: No, there is no benefit to staying at 1.0.0. If you want to stick with stock eclair then upgrade to 1.1.0, the update fixed some WiFi issues. To revert back to an older "save" install clockwork mod via rom manager and make a backup. That backup can be reflashed whenever from whatever.
2:I don't know what you're confusing GB for but so far only Eclair/Froyo/HoneyComb currently run on the nook color. Yes you can revert back to any older CWM backup from any install on your eMMC. There are stock flashable images in the dev forum, so don't worry about not being able to go back to stock.
Good luck. Have fun.
woot1524 said:
1: No, there is no benefit to staying at 1.0.0. If you want to stick with stock eclair then upgrade to 1.1.0, the update fixed some WiFi issues. To revert back to an older "save" install clockwork mod via rom manager and make a backup. That backup can be reflashed whenever from whatever.
2:I don't know what you're confusing GB for but so far only Eclair/Froyo/HoneyComb currently run on the nook color. Yes you can revert back to any older CWM backup from any install on your eMMC. There are stock flashable images in the dev forum, so don't worry about not being able to go back to stock.
Good luck. Have fun.
Click to expand...
Click to collapse
sorry, typo, i meant HC not GB. who can keep them straight these days? thanks for your answers. i've read reports of people having various problems with 1.1.0, it seems the consensus is 1.01 is the version to be on.
OneStepAhead said:
sorry, typo, i meant HC not GB. who can keep them straight these days? thanks for your answers. i've read reports of people having various problems with 1.1.0, it seems the consensus is 1.01 is the version to be on.
Click to expand...
Click to collapse
I think the problems you're talking about stem from upgrading an already rooted 1.0.0 or 1.0.1 with clockwork mod installed. If you start with a fresh(no root/CWM) 1.0.0 install then upgrade to 1.1.0 via b&n, then root it; you're in the clear.
But why bother with all of that when nookie Froyo 6.8 on eMMC is stable and performing beautifully.
OneStepAhead said:
I bought a nook color yesterday so I could get in on the rooting and roming fun as well. It came with 1.0, which I've already rooted and am now running HC from an SD card. A bit slow, so I'm planning on trying to install it internally. 2 Questions:
1. Is their any reason I should stay at 1.0? Or should I upgrade to 1.01 or 1.1? Will I be able to go back to 1.0 if I want using the 8 reboot method?
2. If I install HC to the internal memory, will I be able to restore to stock? I'm not sure I'm going to keep this device yet so I don't want to do something that will make it impossible to return to stock.
Thanks
Click to expand...
Click to collapse
1. none that I could ever see... must've fixed something to warrant two updates although I believe that both were mostly for WiFi but I never had problems with 1.0 or 1.01...
...now I'm just wondering where the new B&N updates are as IIRC they had TWO slated for February and it's getting to be kind of late in the month to push out two updates... might just as well do one big one now... hope that they're skipping Android 2.2 and going straight to 2.3 or 3.0...
woot1524 said:
I think the problems you're talking about stem from upgrading an already rooted 1.0.0 or 1.0.1 with clockwork mod installed. If you start with a fresh(no root/CWM) 1.0.0 install then upgrade to 1.1.0 via b&n, then root it; you're in the clear.
But why bother with all of that when nookie Froyo 6.8 on eMMC is stable and performing beautifully.
Click to expand...
Click to collapse
Well the only reason I bought a Nook Color was to play with Honeycomb, dont have much interest in running Froyo, I can do that on my EVO already
One reason to stay with one of the stock ROMs is if you want to use the B&N reader and B&N kids functionality, which are not part of the froyo or HC ROMs. I personally use it a lot and hope they'll get ported over.
eyecrispy said:
One reason to stay with one of the stock ROMs is if you want to use the B&N reader and B&N kids functionality, which are not part of the froyo or HC ROMs. I personally use it a lot and hope they'll get ported over.
Click to expand...
Click to collapse
Im sure thats important to many people, although I strictly bought this to play with Honeycomb. Now that I've got it running, I'm wondering what I'll actually use this device for? I can already do all this stuff on my EVO and the screen size isn't that much bigger. It sure had been fun messing with it though! Why B&N didnt enable some of this functionality out of the box I'll never understand!
I'm sorry if this is has been answered before but i'm a noob, but an actively learning noob =) There is so much information in these forums but it can be highly overwhelming with so much info out there and hundreds of pages, it's like finding a needle in a hay stack.
1. I'm unsure exactly what a kernel is.
2. I am currently running CWR 3.0.0.5 w/ (Nookie Froyo Custom 0.6.8). Can I / Should I update to CWR 3.0.1.0 even if I stick w/ Froyo? Will the update overwrite my system forcing me to reinstall everything?
3. I saw something about Tablet tools (or something similar in name). Does that get installed in CWR just like Google Apps? Do I install before or after the ROM (Froyo Custom / CM7)?
I would like to go to CM7. But am curious about different Kernels such as Darlingtons OC. Any other recommendations? I currently use SetCPU at 1.1 in Froyo w/ no problems.
Thank you for your help in advanced and to all the amazing devlopers out there!
~J
First off, read more before attempting anything. I cannot stress enough that you should always be sure you understand exactly what you are doing, even if you're unsure how the process works, otherwise if something goes wrong and you weren't sure what exactly was happening you'll be kicking yourself later.
The kernel is the part of an operating system that actually makes the software and hardware talk to eachother in a sane manner, read: it makes everyone play nice hopefully. CM7 does include one in the image but if you read further on how to flash stuff you can replace the stock one with an overclockable version if you'd like.
Some of the documentation I've found can be a touch confusing if you're new to Android to be sure, I'd reccommend reading thinkgs a few more times and asking questions about specific tutorials, it will help get you started in the direction you'd like to go.
OP Modified question to be better suited, new response to match:
jabrams said:
1. I'm unsure exactly what a kernel is.
Click to expand...
Click to collapse
Kernel, in OS terms I answered above, in Android terms it's basically the same except how it is updated vs on say a Linux PC is different, isnted of just installing it normally you have to "Flash" a separate file, more on that in response to #4.
jabrams said:
2. I am currently running CWR 3.0.0.5 w/ (Nookie Froyo Custom 0.6.8). Can I / Should I update to CWR 3.0.1.0 even if I stick w/ Froyo? Will the update overwrite my system forcing me to reinstall everything?
Click to expand...
Click to collapse
I have CWR 3.0.1.0 and it works great, I am not aware of it overwriting previously installed ROMs but I'm not a CWR dev so take that with a large grain of salt.
jabrams said:
3. I saw something about Tablet tools (or something similar in name). Does that get installed in CWR just like Google Apps? Do I install before or after the ROM (Froyo Custom / CM7)?
Click to expand...
Click to collapse
Link to the thread in question, I'm not sure what you're asking about on this one.
jabrams said:
I would like to go to CM7. But am curious about different Kernels such as Darlingtons OC. Any other recommendations? I currently use SetCPU at 1.1 in Froyo w/ no problems.
Click to expand...
Click to collapse
CM7 comes with its own kernel but Darlington's OC kernel works amazingly well, he has packages that you can flash via CMR just like you would GApps, just make sure you grab the one that is right for your install of CM7 (SD or EMMC depending).
Hope that helps
Hello,
I got an NC recently from a friend who had already rooted and installed CM7 nightly version.
I want to remove all data and application and install a fresh CM7 stable version. I would like to know how I should go about achieving that. I've read a little about updating to new version and flashing back to clean stock ROM. should I flash back to stock ROM and re-root the device and install CM7 stable version or update? and if so which method should I use?
Any help is appreciated. Thanks!
I would just follow this link and install fresh. This ROM seems very stable and darned fast for me that is!
http://forum.xda-developers.com/showthread.php?t=954902
A fresh install will allow you to learn and ensure previous data is gone....Enjoy!
skeeterpro said:
I would just follow this link and install fresh. This ROM seems very stable and darned fast for me that is!
http://forum.xda-developers.com/showthread.php?t=954902
A fresh install will allow you to learn and ensure previous data is gone....Enjoy!
Click to expand...
Click to collapse
If I proceed with this, I wouldn't be able to flash back to stock ROM? would that be an issue in the future? and how is the battery usage while running phiremod v6?
Thanks for the quick reply!
skorph said:
Hello,
I got an NC recently from a friend who had already rooted and installed CM7 nightly version.
I want to remove all data and application and install a fresh CM7 stable version. I would like to know how I should go about achieving that. I've read a little about updating to new version and flashing back to clean stock ROM. should I flash back to stock ROM and re-root the device and install CM7 stable version or update? and if so which method should I use?
Any help is appreciated. Thanks!
Click to expand...
Click to collapse
I've been doing nothing but updates since nightly 30 and my nook runs great.
If you want to do a fresh install, just boot into CWR and wipe the /system /data and /cache partitions before installing CM7.
It's not necessary to return to stock unless you mangled your boot partition somehow (or wiped it by accident like I did lol).
After having used cm7 why in the world would you want to use stock?? Unless of course you wanted to return the nc for some reason, then yeah you need to go back to stock.
I've had several tablets and for the money you can't beat the nc, especially running cm7. If I had unlimited funds I'm sure I could find something better, but really I'm rather in love with this device even compared to tablets cosing twice as much.
cshehan said:
After having used cm7 why in the world would you want to use stock?? Unless of course you wanted to return the nc for some reason, then yeah you need to go back to stock.
I've had several tablets and for the money you can't beat the nc, especially running cm7. If I had unlimited funds I'm sure I could find something better, but really I'm rather in love with this device even compared to tablets cosing twice as much.
Click to expand...
Click to collapse
I'm getting my NC ready for phiremod
Thanks
skorph said:
I'm getting my NC ready for phiremod
Thanks
Click to expand...
Click to collapse
How'd it go? I just flashed the phiremod v6 myself.
Changing Model Number
I need to change the name of my NookColor to to something like AndroidTablet. Does anybody know of an app. that will do this?
When you say change the name.. where? The network ssid? In about this phone? Somewhere else?
Sent from my HTC Vision using XDA App
skeeterpro said:
How'd it go? I just flashed the phiremod v6 myself.
Click to expand...
Click to collapse
It went pretty smooth. thanks!
skorph said:
It went pretty smooth. thanks!
Click to expand...
Click to collapse
My pleasure! Enjoy!
Hey all, I'm running CM7 7.1 rc-1... I just installed dalingrin's latest oc kernel... And it killed my wifi.. It's really bugging me. My nc is currently oc'd @ 1200.. With a min speed of 600. Is the kernel killing my wifi? Or is it the overclocking?
Thanks in advance.
Hi,
interesting. I had the same experience. My case went a little bit further than that as I lost my whole config after trying to fix it ... long story short, after fixing my nook and re-installing back to stock (1.0.1 then upgrade to 1.3). I tried again, installed same distro on SD but I put all the zip files at the same time on the sd card for install (7.1, gapps and OC); everything got installed and no more wifi problems. I also upgraded to full nightly 212. So far, so good.
I also noticed something: after testing a few apps, I would get a weird behavior. In rom manager, fix permissions would fix most of the issues.
Olivier! said:
Hi,
interesting. I had the same experience. My case went a little bit further than that as I lost my whole config after trying to fix it ... long story short, after fixing my nook and re-installing back to stock (1.0.1 then upgrade to 1.3). I tried again, installed same distro on SD but I put all the zip files at the same time on the sd card for install (7.1, gapps and OC); everything got installed and no more wifi problems. I also upgraded to full nightly 212. So far, so good.
I also noticed something: after testing a few apps, I would get a weird behavior. In rom manager, fix permissions would fix most of the issues.
Click to expand...
Click to collapse
hmm.. interesting. I'll give that a try and tell you what happens.
update:
I tried to install the stock firmware by deleting cwm, repartitioning boot to stock (after installing stock 1.1)... now it just loops on the "nook color by bn" screen. any suggestions?
Follow the instructions here and start all over. Choose nightly 200 or higher and make sure you use the latest version of CWR (3.2.0.1): http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
patruns said:
Follow the instructions here and start all over. Choose nightly 200 or higher and make sure you use the latest version of CWR (3.2.0.1): http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
Click to expand...
Click to collapse
brilliant! that worked wonderfully. for future reference, the latest version of CWR seemed to do the trick. thanks!