[DEV] CM7 Developers Thread

Search This thread

gudism

Senior Member
Jul 18, 2010
103
2
Launceston Tasmania
Part of this is due to over-the-top enthusiasm about each little fix and new version, that it will cure cancer, establish world peace, and get you a weekend alone with the supermodel of your choice. ;)

The result is that word-of-mouth gets around, and so hundreds of people who have no clue about technical issues are flashing things they do not understand.

In the case of this Beta 3.1, as I type this, nandroid restore is re-installing 7.0-stable on my Nook, because I use the Nook to remind me about appointments, and when it is frozen (locked up), it doesn't do that.

That does not mean that the development is going wrong, in fact, it is labeled Beta in a Development Forum, and the purpose of the build is to find bugs.

However, earlier in the thread, someone who probably should only be running Stable asked "so is it okay to install this?". The answer to that question for anything other than Stable should be no. But someone answered "sure, go ahead, it's great". That answer leads to the results you observed.

I agree with this entirely. I am a noob at all this, but I can get around fairly well when it comes to doing stuff like this.

But, I am not going to flash any Beta stuff, as I would rather let the dev's and the really really knowledgeable folks do the testing etc for the devs feedback. (also cos I have 4 young kids and just dont have the time to be testing things etc)

For now, I will sit back, read these threads, and when the smoke has cleared and its ready to rock as a stable....then I'll jump on it! (cant wait!)
 

gteo

Member
Jul 10, 2008
10
1
Hi installed the Beta 3.1 to Nook color, working well and battery life is good, but there is no gmail and adroid market apps there, after flash with gapps-gb-20110307-signed.zip, indicated installed ok, when re-boot, still not seeing gmail and android market apps, have tried few times, still same. Am i doing the wrong procedures or wrong zip file ?

Pls help
 

ADude

Senior Member
Mar 5, 2011
528
59
Okay, I did the same uses of wifi just now with 7.00 stable (.29) that I did with 7.10 Beta 3.1 (.32) last night, in the same location.

The result is that wifi worked flawlessly with 7.00 (and I previously reported wifi failures with 7.10 Beta 3.1, the same thing reported by others in this thread).

So, there is a data point that there is some new wifi problem introduced by 7.10 Beta 3.1, as I have never had wifi problems before.
 
  • Like
Reactions: chli

360Razir

Senior Member
Jan 6, 2011
564
86
Hi installed the Beta 3.1 to Nook color, working well and battery life is good, but there is no gmail and adroid market apps there, after flash with gapps-gb-20110307-signed.zip, indicated installed ok, when re-boot, still not seeing gmail and android market apps, have tried few times, still same. Am i doing the wrong procedures or wrong zip file ?

Pls help

Gmail is now a standalone app and is downloadable from the Market, therefore it is not included in the Gapps file that you used (which, btw, is the correct one).

What "market apps" are you referring to?
 

mjb413

Senior Member
Aug 22, 2010
467
37
South Carolina
beta 3.1 with overclock kernel works great here. 3 days, 87% battery. simply amazing.
only issue is, i believe, app specific. I have tried to use the modified netflix apps and it seems as if it is playing at double speed? anyway. thanks for the great work dal. hardware video decoding works well for me. hulu streaming is a bit stuttered. most other flash video streams fine.
 

moesasin

Senior Member
Dec 1, 2010
53
5
Noob Friendly Instructions(1.2 UBoot+Overclock+ CM7 beta 3.1)

all required files are already on the bootable CWR image.
Requirements:
Nook Color
atleast 1GB micro SD card
CM7.1-beta-3.1-mrm3.net.zip
Win32 Disk Imager
USB SD card reader(a must have, you cannot use the nook for writing to the SD card during this process)


Instructions

1. Download all of the above files and put them in a convenient location. only extract the files Win32 Disk Imager, and CM7.1-beta-3.1-mrm3.net.zip
2. Open Win32 Disk Imager, select CM7.1-beta-3.1-mrm3.net.img and write the image to your SD card.WARNING THIS WIPES THE ENTIRE SD CARD
3. Wait for it to finish.
4. Reboot your nook color with the SD card in. It should now boot into clockworkmod(CWR)
5. clockwork mod is an environment to install roms and programs before the operating system boots to navigate use the volume buttons for up and down. home to select and power as the back button.
6. Navigate to Mounts and Storage. format all of the following: data, system,and cache. Each require you to separately navigate down to YES to wipe.
7. After you have formatted the above. Go back to the home screen using the power button and select install zip from SD card, choose zip from sdcard, update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip
8. After it has finished the install from SD. Hit the power button until you can select reboot system now DON’T CLICK IT. Remove the SD card. Select reboot system now.
10. Your device will now reboot with Gingerbread installed. The first boot up should take about 5 minutes and on the screen you will see in this order…loading…android…then a fancy boot animation.
11. Insert SD card again and boot into CWR. Now install these files in this order….Update-BN1.2-uboot.bin.zip…..update-cm7-dalingrin-2.6.32-emmc-051311.zip……Nook Color Google Apps.zip
12. Reboot, then login to market
13. To overclock: Settings>cyanogenmod settings>performance> CPU Settings> set max to 1200mhz>governor on demand.


For more noob friendly how to guides check out my site in the signature.
 
Last edited:

hockeyfamily737

Senior Member
Apr 3, 2011
2,240
2,758
Connecticut
beta 3.1 with overclock kernel works great here. 3 days, 87% battery. simply amazing.
only issue is, i believe, app specific. I have tried to use the modified netflix apps and it seems as if it is playing at double speed? anyway. thanks for the great work dal. hardware video decoding works well for me. hulu streaming is a bit stuttered. most other flash video streams fine.

Here's the thread regarding the Netflix app and how to get it to work correctly. There are a couple of different build.props you can use......http://xdaforums.com/showthread.php?t=1078123
 
  • Like
Reactions: mjb413

fattire

Inactive Recognized Developer
Oct 11, 2010
2,281
6,473
www.eff.org
This u-boot.bin needs some testing by developer-types. It's a custom 1.2 u-boot with a new splash and some small modifications from verygreen to hopefully work on SD as well as EMMC, easier power-button down on start, and other nice things like some debug stuff removed.

(The B&W "skulls" version a couple months back was easy. Turns out, a slightly larger graphic w/the right palette is harder. Even now the colors are a little Miami Vicey. But it beats plain ol' "Loading...")

This is still in development. I have not been able to test the screen when you run out of battery, for example.

It's based on 1.2 u-boot source generously provided by BN. Try at your own risk (have a backup bootable SD and consider an archival u-boot too, JIC). See the GPL for terms. I promise nothing :) If you don't know what to do with a u-boot.bin file, don't worry about it.

thx to verygreen for his contributions and bandroidx for testing.


u-boot.tar.gz
 
Last edited:
  • Like
Reactions: Colchiro

hockeyfamily737

Senior Member
Apr 3, 2011
2,240
2,758
Connecticut
Noob Friendly Instructions(1.2 UBoot+Overclock+ CM7 beta 3.1)

all required files are already on the bootable CWR image.
Requirements:
Nook Color
atleast 1GB micro SD card
CM7.1-beta-3.1-mrm3.net.zip
Win32 Disk Imager
USB SD card reader(a must have, you cannot use the nook for writing to the SD card during this process)


Instructions

1. Download all of the above files and put them in a convenient location. only extract the files Win32 Disk Imager, and CM7.1-beta-3.1-mrm3.net.zip
2. Open Win32 Disk Imager, select CM7.1-beta-3.1-mrm3.net.img and write the image to your SD card.WARNING THIS WIPES THE ENTIRE SD CARD
3. Wait for it to finish.
4. Reboot your nook color with the SD card in. It should now boot into clockworkmod(CWR)
5. clockwork mod is an environment to install roms and programs before the operating system boots to navigate use the volume buttons for up and down. home to select and power as the back button.
6. Navigate to Mounts and Storage. format all of the following: data, system,and cache. Each require you to separately navigate down to YES to wipe.
7. After you have formatted the above. Go back to the home screen using the power button and select install zip from SD card, choose zip from sdcard, update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip
8. After it has finished the install from SD. Hit the power button until you can select reboot system now DON’T CLICK IT. Remove the SD card. Select reboot system now.
10. Your device will now reboot with Gingerbread installed. The first boot up should take about 5 minutes and on the screen you will see in this order…loading…android…then a fancy boot animation.
11. Insert SD card again and boot into CWR. Now install these files in this order….Update-BN1.2-uboot.bin.zip…..update-cm7-dalingrin-2.6.32-emmc-051311.zip……Nook Color Google Apps.zip
12. Reboot, then login to market
13. To overclock: Settings>cyanogenmod settings>performance> CPU Settings> set max to 1200mhz>governor on demand.


For more noob friendly how to guides check out my site in the signature.

This is a very nice guide, but it doesn't belong here. It's going to become lost in obscurity within 48 hours. That being said.....Most "noobs" should not be flashing a beta anything anyways....Just my opinion.
 

gteo

Member
Jul 10, 2008
10
1
Tks for advise. There is no Android marketplace in Nook Color, and not asking to setup gmail's login and etc after done Gapps.

Gmail is now a standalone app and is downloadable from the Market, therefore it is not included in the Gapps file that you used (which, btw, is the correct one).

What "market apps" are you referring to?
 

mjb413

Senior Member
Aug 22, 2010
467
37
South Carolina

chisleu

Senior Member
Mar 7, 2011
1,042
105
Myrtle Beach SC
Just wanted to pop in and say this has been 100% stable for me and to thank everyone for all of their work. Sleep is working great, no lockups, running 300/1200 smartass, I think ondemand runs better, but the battery seems to go down surprisingly quick with ondemand.

I think the performance of on demand is better than smart ass. It's way less than the old interactive on .29.
 

gteo

Member
Jul 10, 2008
10
1
I managed to get the Gmail 2.3.4 and market 2.3.4 and installed ok, but unable to run, when click, white screen appear and close. If i get the correct gmail and market apps or need to do setting in Nook color.

Pls help.

Tks for advise. There is no Android marketplace in Nook Color, and not asking to setup gmail's login and etc after done Gapps.
 

jmak10

Member
Apr 14, 2011
29
1
I'm running the 5/13 beta, with the 5/13 OC kernel (300/1200, On Demand) and the 1.2 u-boot and have noticed the following issues;

1. WiFi sometimes drops out
2. The screen will shut off sometimes upon completion of a flash video running from Dolphin HD. It acts like the power button was pressed to put the unit into standby. Pressing the power button turns the screen back on. I am using Flash version 10.3.
3. Had one SOD that required holding the power button in for over a minute to get the unit to boot up.

I have changed the OC kernel to 300/1100, On Demand and haven't experienced any issues yet but have only been using this setting for a short time.

Thanks,
jmak
 

RoboRay

Senior Member
Nov 25, 2010
544
50
This is a very nice guide, but it doesn't belong here. It's going to become lost in obscurity within 48 hours. That being said.....Most "noobs" should not be flashing a beta anything anyways....Just my opinion.

NOT just your opinion, it's a fact. A Dev forum is not the place to teach or learn the basics. A step-by-step "Newbie Guide" should be in the General thread, not the Developer thread.

And, of course, Test build information does not belong in the General thread at all.
 

Ronin3178

Senior Member
Oct 26, 2010
505
65
I'm running the 5/13 beta, with the 5/13 OC kernel (300/1200, On Demand) and the 1.2 u-boot and have noticed the following issues;

1. WiFi sometimes drops out
2. The screen will shut off sometimes upon completion of a flash video running from Dolphin HD. It acts like the power button was pressed to put the unit into standby. Pressing the power button turns the screen back on. I am using Flash version 10.3.
3. Had one SOD that required holding the power button in for over a minute to get the unit to boot up.

I have changed the OC kernel to 300/1100, On Demand and haven't experienced any issues yet but have only been using this setting for a short time.

Thanks,
jmak

I just did a test on dolphin HD, watched a flash video, my screen did not turn off after the video was over. I have 10.1 installed it looks like. What are you settings for screen timeout? Mine is like 10 mins.

5/13 oc 300/1200 smartass

EDIT : Also just had my second early shutoff, this time battery was showing 13% and just shutdown, the time before that was @ like 9% I think. 7.0.2 was going until at least 5% for me before.
 
Last edited:

seth.i.simmons

Senior Member
Apr 13, 2011
364
68
Lynchburg, VA
I think the performance of on demand is better than smart ass. It's way less than the old interactive on .29.

Same here, smartass seems a little laggy compared to ondemand, personally. Especially when scrolling. Is there any way you (dalingrin) could include interactive in the next kernel update?? So we could have ondemand, smartass, AND interactive?? That would be awesome, since interactive worked so well for me in .29 kernels.
 

jmak10

Member
Apr 14, 2011
29
1
I just did a test on dolphin HD, watched a flash video, my screen did not turn off after the video was over. I have 10.1 installed it looks like. What are you settings for screen timeout? Mine is like 10 mins.

5/13 oc 300/1200 smartass

EDIT : Also just had my second early shutoff, this time battery was showing 13% and just shutdown, the time before that was @ like 9% I think. 7.0.2 was going until at least 5% for me before.

My screen timeout delay is set to 5 seconds. Also, this is an intermittent problem and doesn't happen all the time.
 

Divine_Madcat

Retired Forum Moderator
Sep 9, 2005
2,936
2,608
USA
Same here, smartass seems a little laggy compared to ondemand, personally. Especially when scrolling. Is there any way you (dalingrin) could include interactive in the next kernel update?? So we could have ondemand, smartass, AND interactive?? That would be awesome, since interactive worked so well for me in .29 kernels.

In watching other phones (specifically the Incredible), the smartass gov went through several changes and tweaks by many people to get things right. I am not surprised that the first release of it here is exhibiting the same issues it has elsewhere...
 

Canadoc

Senior Member
Nov 29, 2010
1,828
133
Samsung Galaxy S23 Ultra
I'm running the 5/13 beta, with the 5/13 OC kernel (300/1200, On Demand) and the 1.2 u-boot and have noticed the following issues;

1. WiFi sometimes drops out
2. The screen will shut off sometimes upon completion of a flash video running from Dolphin HD. It acts like the power button was pressed to put the unit into standby. Pressing the power button turns the screen back on. I am using Flash version 10.3.
3. Had one SOD that required holding the power button in for over a minute to get the unit to boot up.

I have changed the OC kernel to 300/1100, On Demand and haven't experienced any issues yet but have only been using this setting for a short time.

Thanks,
jmak

Having similar.issueshere. have had a few SOD. SometimesI close.the screen an furlough nothing is showing onscreen it is still illuminatedall black.
So far this has not been much better than when we had first gotten nookie froyo in terms of stability

Sent from my NookColor using Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 97
    Please limit this thread to development comments and questions!
    The users thread is for all other posts.
    When in doubt, post in the users thread.


    After many long nights of banging our heads against keyboard, the CM7 port is finally shaping up.
    In addition to nightly releases, we may from time to time be releasing test builds here for your feedback and enjoyment. If you find issues please feel free to post here in this thread. Leave all other feedback for the user thread.

    Where to get progress news:

    I will tweet progress from time to time.
    Twitter: @dalingrin

    We are usually in #nookie on freenode.

    You can always check the Cyanogen git@ http://github.com/cyanogenmod

    Current Issues

    DO NOT FORMAT YOUR SD CARD IN CM7. DUE TO A VOLD ISSUE THIS WILL FORMAT YOUR /BOOT INSTEAD OF THE SD CARD!
    ****Should be fixed in nightly 13****

    -Standy battery life is not as good as stock
    Because of a kernel bug CM7 does not fully sleep. The result
    is ~1% battery drain per hour while the screen is off. With normal use I usually go
    1 - 2 days between charging.
    ***fixed in 2.6.32 builds***

    -A few apps do not scale to full screen
    In order to get Market and Maps to work fully the lcddensity has to be
    set to something other than 160 causing a few apps not to scale properly.

    -Wifi slow to reconnect at times
    ****fixed****


    -Video playback is slow
    ****fixed****

    -Default rotary lockscreen does not fit screen
    ****fixed****

    -Market partially works
    ****fixed****

    -Bluetooth does not work
    ****Update**** Bluetooth now works in CM7.
    Bluetooth is working seemingly perfect except for the range. Unfortunately, the range is terrible.
    Depending on the device you are paried with, the range is between 1-5ft. Any ideas on how to
    fix the range issue would be much appreciated.

    -Do not use SetCPU profiles
    If you enable SetCPU profiles it will become a runaway process eating 100% cpu.
    Setting your cpu clock can be done in Cyanogenmod Settings. Under Performance->CPU Settings

    -Internal storage partition is not mounted on boot and is not shareable via USB
    ****fixed****


    Download and Install

    MUST USE 3.0.1.0+ RECOVERY:
    This is installable ONLY with an ext4 aware Clockwork Mod Recovery.

    *** Also it is critical to be aware that installing CM7 will write to the internal emmc of your device. You are advised NOT to try it. But if you choose to do so, understand you do so entirely at your own risk. Read sections 15-17 of the GPL for the gist of this disclaimer. There is no warranty or claim of usefulness or fitness for any particular purpose. No one but you shall accepts responsibility for what may happen if you download or try to use this development software. ***


    Download for CM7:

    Nightlies
    :
    http://mirror.teamdouche.net/?device=encore

    Install instructions:
    http://xdaforums.com/showpost.php?p=11452450&postcount=19
    30
    ENCORE 2.6.32 BETA QUICK FAQ
    ----------------------------


    WHAT'S THIS?

    Tonight, we can report to the American people and to the world, the CM7 team has conducted an operation that killed the "Sleep of Death" responsible for the senseless battery consumption of thousands of encore devices.

    Or put another way, the CM7 for encore team is proud to release a beta .32 kernel to play with. Try at your own risk.​


    WHO IS RESPONSIBLE FOR THIS?

    Verygreen, FatTire, and Dalingrin did most of the work on this update. Verygreen worked tirelessly on 2.6.32 and 2.6.35 ports of the kernel. An extra special thanks should go to him.
    We hope to use his work to eventually get newer 2.6.35+ kernels for the Nook Color.​


    WHY DO I CARE ABOUT THE .32 KERNEL? HOW'S IT BETTER THAN THE .29 KERNEL?

    It's .03 better, obviously.

    Beyond the sleep improvements, most benefits are "behind the scenes" technical fixes.

    Still, you may notice that the On/Off animation now works and that you experience subtle performance benefits that come from a new kernel. For a generic writeup of .32 features (much of which doesn't apply to the encore), see:

    http://kernelnewbies.org/Linux_2_6_32


    SO WHAT WORKS?

    * basic CM7
    * sound
    * accelerometer
    * backlight
    * wifi
    * EXPERIMENTAL bluetooth (uses new uim/kim method and .bts files)
    * video w/overlay
    * Screenshots
    * usb mounting to your computer
    * sdcard support


    WHAT DOESN'T WORK?

    * Sleep while while charging or connected to USB
    Workaround: Settings->Applications->Development->Stay Awake

    Maybe more, you tell us. Is it stable? Can you make it crash/reboot?

    Probably. This is a beta for a reason.​


    CAN I DROP THE UIMAGE KERNEL FILE INTO A 2.6.29 CM7 SYSTEM?

    No.​


    WHY NOT?

    There are several changes to the installation which make .32 incompatable with previous CM7 installations. Among them are:

    * The kernel's orientation is now native to the encore's screen. No android rotation is needed
    * The WIFI module is different
    * The method of installing BT is different.
    * The GFX (2D acceleration) drivers are different​


    IS THIS .32 KERNEL OVERCLOCKED?

    Not by default. The clock options are the same as the .29 kernel... for now.​


    WHAT ARE THE CHANGES TO BLUETOOTH?

    Bluetooth now uses the wilink driver with a "shared-transport" system that allows both bluetooth and the FM radio to work. Right now, the FM radio isn't enabled at all, as reports say the hardware support (antenna) is not connected. However, this new system makes it at least conceivably possible to use.

    Also, the new system utilizes Texas Instrument's .bts (bluetooth script) method for installing the bt firmware.​


    SO DOES THIS FIX THE BT RANGE ISSUE?

    This is all brand new-- Bluetooth range has not been extensively tested. That is for you to test.

    There are several versions of TI's bluetooth initialization script, called the "bts" script. You can get them here:

    https://gforge.ti.com/gf/project/wilink_drivers/

    The .bts files (such as TIInit_7.2.31.bts) may be placed in:

    /system/etc/firmware

    and will automatically be loaded when needed. Try different versions and experiment to see if some work better others. (Watch the log and dmesg to verify that the bts script is running properly)​


    CAN I MAKE THE FM RADIO WORK?

    The encore device is reported to not have a physical antenna connection to allow the FM radio to function.

    However, this is unexplored territory. If you are a developer and would like to experiment, you may notice that TI makes the following additional firmware files available:

    fm_rx_init_1273.2.bts
    fm_tx_init_1273.2.bts
    fmc_init_1273.2.bts

    These scripts are now potentially loadable into the wifi chip. To make CM7 believe that there is a working FM radio, add to the board file:

    https://github.com/CyanogenMod/android_device_bn_encore/blob/gingerbread/BoardConfig.mk

    the following line:

    BOARD_HAVE_FM_RADIO := true

    And recompile. Good luck!​

    IS THE BRAINFUCK SCHEDULER (BFS) INCLUDED?

    Not yet. We're investigating whether this would be worthwhile.​


    WHERE CAN I GET SOME OF THE KERNEL SOURCE FOR THIS BETA TEST?



    WHAT HAPPENED TO VERYGREEN'S 32 PORT?

    When BN released their .32 kernel, portions were migrated to Verygreen's in-progress .32 kernel source, which in turn was a modification of the .32 kernel from omapzoom.com. At the same time, fixes that were in verygreen's repository were migrated over to the BN source.

    Thus, the CM7 team ended up with *TWO* working versions of the .32 kernel.

    After some discussion, it was decided (for now) to use the source that originated from BN. This will hopefully free us to move to 2.6.35+ quicker.​
    17
    Some eye catching changes in CM7 as of late,

    Not entirely sure if these changes are what I think they are... hardware acceleration in Gingerbread?
    http://review.cyanogenmod.com/6831
    http://review.cyanogenmod.com/7062

    And an update to the Nook kernel, from Dalingrins twitter it seems it may only be one change having to do with USB support...

    http://review.cyanogenmod.com/6995

    any thoughts?

    We are in the middle of merging OMAPZoom framework changes primarily for OMAP4 device support(3D, new DSP, etc) but much of it affects the Nook as well. Media playback should improve somewhat for the Nook. Thus far I have new DSP codecs working but the overlay still needs some work.

    The kernel commit that was finally merged is just some kernel clean up to eliminate possible causes of instability and SOD. No new features yet.

    My 1st priority is to get the OMAPZoom framework changes merged because it affects multiple devices. After that I will focus back on the kernel hopefully figure out SoD and such.

    Longer term, TI has been working on an OMAP3 2.6.35 kernel finally and I would like to look into that for the Nook down the road.
    13
    Beta testers come free, I'm using Firefox 8.0 alpha1 as my primary browser just to illustrate and have participated in beta testing Windows Vista and Windows 7; As far as employing developers, the "upline" Cyanogen Mod team is made up of around 10 members plus about 5 maintainers for the Nook. I'd imagine that about 5-6 full time employed developers could handle that workload(someone correct me if I'm wrong) at about $90,000 a year per developer, that's about half a million a year for a team. B&N 2010 revenue was 6.92 billion dollars just for example, I think they can afford a few full time developers, not to mention the much bigger companies like Samsung and Motorola.

    Even with that said, Google does a good deal of the work, it seems companies must spend more time stripping out the features Google includes in AOSP than implementing useful features...

    Maybe I'm missing something, but it seems to me that these companies could be doing a much better job with their Android ports, considering what some hobbyist and skilled developers produce in their free time...

    One thing that I think the big OEMs need to change is how they organize their device development. If you look at how CM works, it is one source for all devices. All devices use the same branch. Instead of hacking up the Android framework to get feature X to work on device Y, we make it work in a device agnostic way. This is something that Samsung and others don't seem to always do. They have separate trees/branches for even the same devices(all the galaxy S variants). The end result is a mess and it makes it much more difficult to get timely updates to your devices. Additionally, some random person may decide to contribute a new feature to Android and with very little effort all CM devices reap the benefits(such as the recent boot speed up). Fixing problems at the device level can be more difficult than hacking the framework in the short term but in the long term it makes maintaining and improving Android much easier.

    I haven't been a part of CM for that long but I am definitely proud of how a small group of folks that work on something part time have been able to achieve what they have. While it can be aggravating that CyanogenMod gets kanged so much with little or no credit, I guess its better than no one wanting your work.
    11
    Developer Tips

    (Standard do-at-your-own-risk-and-responsibility disclaimers apply.)

    * For those developers building from source:

    In $OUT, you'll find a few files:

    recovery.img --> rename to uRecRam
    kernel --> rename to uRecImg

    Now you've got the ext4 clockworkmod for mmc built from source.

    * Also, there's also a script in $OUT called:

    sd_ramdisk_packer.sh

    Assuming this works, it should repack your $OUT/root (mmc ramdisk) into a uRamdisk that can be used with a bootable SDcard. The stuff in /system would go in the /system partition of the SD card (p2).

    The result: a bootable CM7 on SD. It may not be wise to distribute as Cyanogenmod for encore is a fast-moving target-- unless you plan to create a new one every day or something.

    * If you don't like the buttons at the top for some reason, there's the SoftKeys app as well as Button Savior.

    * There is a slightly-themed u-boot.bin in device/bn/encore/prebuilt/boot/. It is simply a recompiled u-boot from BN's source.​

    encoreboot.png


    Info about emmc geometry

    If your emmc is hosed and you want to start COMPLETELY from scratch, understand that the underlying geometry (before any partitions are created) of your emmc must be set up correctly on OMAP machines such as the nook before any partitions are created.

    You can read more about that stuff here. If you are booted into an "emergency" SD card and have a totally hosed emmc, you can use fdisk to format /dev/block/mmcblk0 to the correct geometry, and then create the partitions one at a time, with a vfat partition as your /boot partition (p1). Then put mlo, u-boot.bin, uImage, uRamdisk, uRecImg, and uRecRam in /boot (p1) and you should have a bootable system.

    Read the link above about SD/MMC formatting for OMAP3. Your nook is an OMAP3621, so you gotta get that geometry right, otherwise it won't boot. Luckily, the instructions on using fdisk are pretty good.

    More info:

    your emmc: /dev/block/mmcblk0
    your sd: /dev/block/mmcblk1

    Partition Info

    the partitions you should have created are at:

    /dev/block/mmcblk0p1 == /boot
    /dev/block/mmcblk0p5 == /system
    etc

    /boot, /rom, and /media are of type "vfat"
    /system, /data, and /cache are of type "ext4"

    /factory (p3) isn't used by cm7

    partition 4 is just there to allow you to create partitions 5-8

    Sample instructions for copying files from cm7 update.zip on local computer to emmc /boot

    You should be able to copy those four files simply by getting the lastest cm7, unzipping it on your computer, then once you boot into your bootable SD card, do:

    Code:
    COMPUTER> adb shell
    # mkdir /data/bootmountpoint
    # mkdir /data/systemmountpoint
    # mount /dev/block/mmcblk0p1 /data/bootmountpoint
    # mount /dev/block/mmcblk0p5 /data/systemmountpoint
    # exit
    COMPUTER> adb push mlo /data/bootmountpoint/
    COMPUTER> adb push u-boot.bin /data/bootmountpoint/
    COMPUTER> adb push uImage /data/bootmountpoint/
    COMPUTER> adb push uRamdisk /data/bootmountoint/
    COMPUTER> adb push  my/path/to/sdcard/system /data/systemmountpoint/