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!!
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!
OK. So I am sure I am missing something obvious here. I've done a ton of searching and reading, but I'm still at a bit of a loss.
I am running CM7 with dalingrin's OC kernel flashed over the top of it. I see tons of people overclocking to 1.0 and 1.1 GHz, yet I can't seem to options for doing so.
In CM7 settings under performance, I have options for 100-950. I can O/C to 950 and that's great, but how do people try settings above that? I tried setCPU, but it seems to cap out at 950 as well.
What am I missing?
You need to get a different kernel, such as Dalingrin's, from the android development forum.
Hi,
Looks like you didn't successfully install the overclock kernel, see:
http://forum.xda-developers.com/showthread.php?t=925451
for instructions.
I have been using the CWM install method and am running CWM7 RC4 with
the interactive governor between 300 and 1100MHz.
I usually install the updated CM7 along followed by GAPPS then the
latest OC kernel. Perhaps you installed the kernel before CM7? CM7
comes with its own kernel that overwrites existing kernel when you install CM7.
Hope this helps,
Peter
solinar said:
OK. So I am sure I am missing something obvious here. I've done a ton of searching and reading, but I'm still at a bit of a loss.
I am running CM7 with dalingrin's OC kernel flashed over the top of it. I see tons of people overclocking to 1.0 and 1.1 GHz, yet I can't seem to options for doing so.
In CM7 settings under performance, I have options for 100-950. I can O/C to 950 and that's great, but how do people try settings above that? I tried setCPU, but it seems to cap out at 950 as well.
What am I missing?
Click to expand...
Click to collapse
That is odd. I have never had any issue like that with any of the oc kernels.
My one and only question is if you a sure you flashed the right one successfully?
http://nook.handhelds.ru/dalingrin/kernels/033111/
Note that there are 2 kernels for each ROM-
one is for internally installed (emmc)
One is for sd card installations (sd)
I do not know if any errors would show up if you flashed the wrong one or if there was an error with the download.
My suggestion would be to try again and see if it works.
My response may be too basic- I don't know your knowledge level.
One thing though- IN CM7 it is best to NOT use SetCPU or other apps to change cpu speed, or at least that used to be the case. I don't use them anymore.
rogerdugans said:
Note that there are 2 kernels for each ROM-
one is for internally installed (emmc)
One is for sd card installations (sd)
Click to expand...
Click to collapse
Ding ding ding, we have a winner. I was using the SD version, as I had a bootable CWM SD that I used to get into recovery. Once I loaded the emmc onto the SD card and flashed that, they showed up.
Thanks for all of the replies.
Nice!
Glad I was able to help-
Usually I am just getting all kinds of info and help for my own stuff here. Being able to pay that back is a good thing.
Be sure not to flash a cm7 nightly after you flash the kernel. If you do, you will flash there stock cnn kernel over the oc'Ed kernel
1Enoch said:
Be sure not to flash a cm7 nightly after you flash the kernel. If you do, you will flash there stock cnn kernel over the oc'Ed kernel
Click to expand...
Click to collapse
Actually a good point-
Nothing wrong with updating to the latest nightly but you WILL go back to having the stock CM7 kernel again.
Re-flashing the oc kernel fixes that problem, of course, but you'll need to reset max cpu speed and governor again.
Just finished the manual nooter process. Downloaded setcpu. Just reead that I need a custom kernal for overclocking? I assume I am still on stock android system because I can still get to the nook home screen....???
Do I copy the overclock .zip to the sd. Boot into CW and install it? If so, anyone have a link to the kernal I need?
Yes just put the file in the root of your SD card boot into cwm and flash the zip. Since you are on stock 1.2 you should he using dals 06302011 stock froyo kernel on emmc. To get it just go to the development sub forum and click the kernel thread posted by Dal.
Ill ask one more question. I want to get n64oid but it wont show up in market. Do i need a froyo rom or is there a different method for making it show up in market?
Um Im not running stock 1.2 so not sure if your talking about the nook market or the android market. But I believe that all the emulators made by the maker of n64oid have been pulled from the market anyways. You can get the app directly from the developer at http://slideme.org/application/n64oid
Trying to download sam app and it says my phone does not allow non market installs. How do i fix this?
Also, when people say the "root" of my phone. Do you mean the sd?
You have to enable nonmarket app installs. It should be under settings ->applicatiins. Then check allow non market installs. I'm not sure how the manual nooter for 1.2 looks like cuz I never used it. You'll have to be at the android home screen not the nook home screen (assuming its similar to 1.1 when I had mine auto nootered.)
I am very much new on Rooting the NC. I finally updated to the 1.3 and then used the manual nooter to root it again. However, after doing quite a bit of research, I have been seeing people posting about flashing the
" Dalingrin Kernels" ??
What are these?? and if it would help my NC to be a little more stable, or faster, could I use these?? and if so, how would I do this??
Thanks!!
They are customized kernels that allow for overclocking, and some other "unlocked" features. They are actually included in the CM7 nightlies now, so you don't have to flash them separately. You can go into the Cyanogenmod Settings to change the CPU clock in the Performance section to overclock. Other stuff that's working include bluetooth and usb host mode.
I would highly recommend just using one of the latest nightly CM7 releases. If you want to stick with rooted stock, then you should still be able to flash the kernel, I believe.
Add on to what pony said,
+ it created by Dalingrin, that's why it gets the name.
+ Dalingrin recently release new set of kernels in September, but I have no clue what news, enhancements or any advanced features added. I hope he will post the log some days.
Rhonda19 said:
I am very much new on Rooting the NC. I finally updated to the 1.3 and then used the manual nooter to root it again. However, after doing quite a bit of research, I have been seeing people posting about flashing the
" Dalingrin Kernels" ??
What are these?? and if it would help my NC to be a little more stable, or faster, could I use these?? and if so, how would I do this??
Thanks!!
Click to expand...
Click to collapse
Find the Dalingrin post in the Development section that contains the link to kernals. Use the 090111 kernal (there are two so pick the one that is to be flashed from the SD card). You can use the same CWM SD card that was used to install Manualnooter. Put the zip on the card, the card in the Nook, boot to CWM and flash. Following a reboot, you will be in business.
I did this when I installed Manualnooter 4.6.16 but you should be able to do it at any time. I coud not tell you if it makes any difference as I did not run rooted 1.3 without it.