• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM7 Nightly builds/custom kernels

TheAmazingDave said:
It's a PITA, or at least it was for me. I just included my kernel on the SD card with the ROM image on that first boot, and it automatically installed it. To flash it in after the SD has been set up, you'll need to get into recovery mode with the correct button combo, which isn't necessarily easy when running off the card (for whatever reason).
Click to expand...
Actually, it looks like I'd either gotten hold of outdated info, or was making things much more difficult for myself than they needed to be. I just found instructions here
OverClocking NC W/ CM7-35 - CyanogenMod Forum
and it worked fine. Except there is already a uimage file when you unpack the kernel file, so no need to rename the kernel. I just copied that file over the existing one on my card (using a card reader), put it back in the nook, and bam, I can overclock! :cool: (At least, in Cyanogenmod performance settings I can now go as high as 1200, and I think the max was 900ish before. Also I'm seeing "stepping" settings in Nook Tweaks, and it's no longer telling me I have the wrong kernel.)

I did try it on my spare card first just in case. ;)

Edited to add: Curses, I spoke too soon. Getting a wireless error.
 
wayrad said:
I just copied that file over the existing one on my card (using a card reader), put it back in the nook, and bam, I can overclock! :cool: (At least, in Cyanogenmod performance settings I can now go as high as 1200, and I think the max was 900ish before. Also I'm seeing "stepping" settings in Nook Tweaks, and it's no longer telling me I have the wrong kernel.)

I did try it on my spare card first just in case. ;)

Edited to add: Curses, I spoke too soon. Getting a wireless error.
Click to expand...

This is exactly the way I tried and the same wireless error I've been getting :(
 
TheAmazingDave said:
It's a PITA, or at least it was for me. I just included my kernel on the SD card with the ROM image on that first boot, and it automatically installed it. To flash it in after the SD has been set up, you'll need to get into recovery mode with the correct button combo, which isn't necessarily easy when running off the card (for whatever reason).
Click to expand...
I just went back and flashed it in recovery as you suggested (holding the power button until the reboot option came up and then selecting recovery; I never practiced the 2-button method) and the wifi now works. Thanks!
 
I installed CM7 on an micro SD card a couple of months ago. I really like it and upgraded twice most recently to the RC1. RC1 seems to have really increased battery life and works like a charm. B&N seems to have also improved their nook app so that I like it as much as the stock reader.

I have never upgraded or tried a new kernel since the original install. Should I be updating the kernel too? Is that done in the same way as upgrading CM7?
 
wayrad said:
I just went back and flashed it in recovery as you suggested (holding the power button until the reboot option came up and then selecting recovery; I never practiced the 2-button method) and the wifi now works. Thanks!
Click to expand...

How do you go back to reflash it in recovery mode? Did you copy kernel's UImage file over the original one and then reboot it in recovery? Or something else? Just like to know more detail :) Thanks!
 
mntw said:
This is exactly the way I tried and the same wireless error I've been getting :(
Click to expand...
What worked for me in the end was to copy the zip file (without unpacking it) to the card's boot directory (using a card reader) and then go into recovery, same as if I was updating a nightly. Just copying the uImage file gave me the wifi error on both cards I tried.

Edited to add: Crossposted, but amazingly I seem to have answered your question...;)

PS. Once it goes into recovery it does its thing and then shuts down. Boot again and you'll have the new kernel.

Also, at one point I tried just copying back the old uImage file, and that also fixed the wifi error, although of course it gave me back the old kernel.
 
wayrad said:
I just went back and flashed it in recovery as you suggested (holding the power button until the reboot option came up and then selecting recovery; I never practiced the 2-button method) and the wifi now works. Thanks!
Click to expand...

No problem. :) Now go enjoy your new tablet.
 
bjadams44 said:
I installed CM7 on an micro SD card a couple of months ago. I really like it and upgraded twice most recently to the RC1. RC1 seems to have really increased battery life and works like a charm. B&N seems to have also improved their nook app so that I like it as much as the stock reader.

I have never upgraded or tried a new kernel since the original install. Should I be updating the kernel too? Is that done in the same way as upgrading CM7?
Click to expand...

There's no need to update your kernel if you don't care to test all the latest features. You're not missing much, just USB host support which is still pretty experimental, and the ability to overclock beyond the 925 MHz available in a stock CM7 install.

Dalingrin, who is also a Nook dev for CM7, writes the OC kernels with the extra features. His kernels require you to use a current CM7 nightly or 7.1 RC1. Installing a new kernel on an old incompatible build of CM7 will render your device unbootable, be careful. I see you mentioned you're on RC1, but that's just a general note for anyone else reading.
 
wayrad said:
What worked for me in the end was to copy the zip file (without unpacking it) to the card's boot directory (using a card reader) and then go into recovery, same as if I was updating a nightly. Just copying the uImage file gave me the wifi error on both cards I tried.

Edited to add: Crossposted, but amazingly I seem to have answered your question...;)

PS. Once it goes into recovery it does its thing and then shuts down. Boot again and you'll have the new kernel.

Also, at one point I tried just copying back the old uImage file, and that also fixed the wifi error, although of course it gave me back the old kernel.
Click to expand...

At one point, I tried that too :) Copied the zip file then go into recovery like you just did. However it never booted it up successfully. It was hung and looping at the first green/yellow cm sign screen. Never got into the blue cm mod 7 little robot screen. Which version of the kernel you tried? I'm on cm7 102. I'll give it another shot tonight. Thank you for your answer!
 
mntw said:
At one point, I tried that too :) Copied the zip file then go into recovery like you just did. However it never booted it up successfully. It was hung and looping at the first green/yellow cm sign screen. Never got into the blue cm mod 7 little robot screen. Which version of the kernel you tried? I'm on cm7 102. I'll give it another shot tonight. Thank you for your answer!
Click to expand...
Bummer. :( FWIW, I am on Cyanogenmod-7-06252011-NIGHTLY-encore (which appears to be 113, I thought I was on 114 but apparently I wasn't) and the kernel is Dalingrin's 2.6.32.9 (filename was update-CM7-dalingrin-OC-sd-061811.zip). My NC is a "green dot" model (updated OS, old partitioning) and I get the green Cyanogenmod logo and "read forever" message, which is important somehow although my brain is too fried to remember why. I used the quinxy/verygreen instructions to put the original nightly (back around 104 I think, not sure) on the card and have upgraded in place once since then, I think.
 
wayrad said:
What worked for me in the end was to copy the zip file (without unpacking it) to the card's boot directory (using a card reader) and then go into recovery, same as if I was updating a nightly. Just copying the uImage file gave me the wifi error on both cards I tried.
Click to expand...

Ha! I got it to work this time. In fact I copied both cm7 latest nightly and OC kernel zip files to the boot directory then going into recovery. This time it went thru smoothly! I'm very happy now :) Just need to give it a few days to see if it is stable. Really appreciate your help!
 
mntw said:
Ha! I got it to work this time. In fact I copied both cm7 latest nightly and OC kernel zip files to the boot directory then going into recovery. This time it went thru smoothly! I'm very happy now :) Just need to give it a few days to see if it is stable. Really appreciate your help!
Click to expand...
Glad it's working! :D It was TheAmazingDave who gave me the necessary clue.
 
This is cool news from the guy doing most of the Nook kernels:

dalingrin said:
I'm about halfway through making changes to CM7 that will make it better optimized for OMAP SoC systems. Up until now Cyanogenmod has been mostly optimized for Qualcomm SoCs. I'm hoping these changes will improve video playback and such but I won't know till I get it done.
Click to expand...

I was having some instability problems with #103... sometimes my NC would reboot shortly after booting, but would be pretty solid after that. Hopefully that's fixed with #117, which I just installed.
 
GirLuvsDroid said:
If you're not on nightlies, then you're likely on CM7 stable. If you read Dalingrin's OP ([Kernel][Stock1.2][CM7] Dalingrin's OC kernel [6/18/11] - xda-developers), he says:

* 2.6.32 CM7 builds currently do not work with the stable CM7 builds until CM7.1. You need to use CM nightlies until 7.1 is released.

That means that you need to use nightlies or you need to use the 2.6.29 releases found here (or earlier): Index of /~dalingrin/nook/kernels/042411.
Click to expand...


Last 3 people, I just asked this and he already answered at the botttom.
 
Now running Dalingrin's 6/30 kernel on CM7.1 RC. Finally stable at 1.3 GHz now that I can tweak my voltages.

I perform several back-to-back quadrant benchmarks to check stability. Before the voltage tweak, I could make it through one test at 1.3 GHz before it would lock up, if I was lucky, and only using On Demand. Now no problem averaging 2,7xx on Quadrant Benchmark at the same speed set to Performance. :)

1.3 GHz @ 1.4 v

Nook Color becomes more fantastic by the day.
 
this is fun... :)

stepping:
1 - 300MHz @ 0.925v
2 - 600MHz @ 1.075v
3 - 900MHz @ 1.300v
4 - 1.15GHz @ 1.375v
5 - 1.30GHz @ 1.400v

I think that's a nice spread of clocks. First two steps are undervolted, and may help save more battery when idle. Stepping 3 is default voltage, but overclocked. Steps 4 and 5 both needed more power for stability at the higher clocks, but only the last step is set higher than the kernel's highest default max.
 
I tried the 0630 kernel and had no deep sleep in 8 hours. Previous builds would sleep at least half the time.

Going to update my wife's NC to RC1 tonight. Just not sure which kernel I'll use.
 
are you using the Interactive X governor? I haven't had a problem with deep sleep, but have experienced a SOD. It was my first ever. :(
 
Not yet. I just read today that it was similar to the pulled smartass governor, and limits speed to 300 when screen off (I think).
 
You must log in or register to reply here.
Back
Top Bottom