yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] shumash:
Well, I've tried it again with a brand new card, and the image that is in the update ...zip shows as .32, but overclocks to 925 max. I've tried Dal's other kernels (4/24 and 5/23 for sd) by just dropping the uImage onto the sd, and they will work fine except that wifi is broken. I've tried flashing the zip files (I'm using j4mm3r's multiboot on the sd) using both the alternate boot (your installer) and recovery (CWM) and they either report errors or don't work, respectively. What am I doing wrong?

Incidentally, I noted a bug in the wallpaper installer in the rom. Where should I report that?
[Nook Color Android Development] smartmind:
I downloaded Dalingrin's OC kernel, it is in to forms, one is the kernel for emmc and the other is for sd, both of them have the name of update-xxxx. I unpack the zip files and there are no kernel file insides them but with a Uimage instead. Shall I just put that Uimage file to replace the one in sd card or just put the zip file in the sd's boot partition and then enter into recvoery and the let the recovery do the flash?
[Nook Color Android Development] verygreen:
Just put the uImage to the first partition instead of the one already there and you are good to go.

Recovery in this image is very picky about file names, so if the kernel is not named "kernel" it won't be updated.
[Nook Color Android Development] verygreen:
If it is available in the update-*.zip way that just unpacks to system/ then you should be able to install it in "recovery install mode".
[Nook Color Android Development] ADude:
Bottom status bar is currently a Preview build in order to test how it affects everything else.

When it is stable, it may be added to the main CM7 code (and with a "top/bottom" option switch, I would hope).
[Nook Color Android Development] DizzyDen:
Green... before I left for work... I ran the process again on the 16 gig card... looked like all partitions other than 4th.... remaining partition that should be fat32 is created fine....

The process does not go into the extracting files as I noted previously... and when hard boot it the files get extracted as expected... since I do get the Android_ prompt... just doesn't go any further...

When I take the card out and check the partitions (using Easus Partition Manager in Win7)... they are sized as expected according to your description of what they should be... other than partition 4 not being created.

Anything else you want me to try... let me know.
[Nook Color Android Development] lekofraggle:
Hey all, I am sorry for the Noob question. I have your BT version 4 image working extremely well, but I am always looking for improvements. I installed gapps and most other things through adb, so I am enjoying my image. However, there are starting to be some major improvents in the nightlies and I am dying to try out the bottom status bar.

Anyway, if I follow those instructions, will it write to the sd card?

I do not want to flash accidentally to the emmc.

And, I do not currently have cwm anymore on my rooted 1.1 emmc image. That is okay right, because the command just invokes your clockwork?

Thank you for all your hard work. This is truly amazing. It is also stable enough for me to grade on and run rehearsals with.

Cheers,

~Leko
[Nook Color Android Development] cybertimber2007:
Hmm, first thought:

Don't boots (in linux based things) normally fail when /etc/fstab reffers to a parition and it doesn't exist or can't be mounted?

If parition 4 is mounted but can't be located, it should fail. Good catch on partition 4 being missing!
[Nook Color Android Development] verygreen:
I think the creation aprt is easy. It's the mkfs part that is tricky. Was mkfs ran succesfully or what was the last message you saw before power cycling the nook?

make sure you not only have the partitions, but also the actual filesystems in those partitions.

If the filesystems are not there, then the unacking that you see is happening to ramdisk due to the failed mount.

The "ANDROID_" prompt is displayed from ramdisk image that is unpacked from the image located on the partition 1, so it does not prove anything aside from the fact that the unpacking really did happen somewhere nd the kernel and ramdisk were copied to a correct place.
[Nook Color Android Development] verygreen:
Yes, these instructions should work for upgrading the older image too.

Though if you want the actual installation to be happening, you need to grab uImage and uRamdisk files from http://nook.handhelds.ru/sdimage,

name them uRecImg and uRecRam and put to the 1st partition instead of the files with those names already there because the files already there are in fact real recovery ramdisk and kernel that would write to the emmc.

my installer does not touch emmc at all.

It's not a real clockwork, it's just a bunch of scripts that are just able to unpack certain packages (like the nightly zip) and install them on the sd card.
[Nook Color Android Development] smartmind:
Many thanks!

I saw in another thread saying that we can update gapps and kernels by firstly burning a CMW sd card and a normal CM7-sd which is the one in your thread, then boot nook with CMW sd card and put the zip files( gapps, kernels) into the CM7-sd card, after booting nook into recovery mod ,switch the cmw sd card with CM7-sd, and choose install zip files from sd card, then the kernel or apps can be updated. I wonder if I want to update a new cm7 rom build, for example the build with bottom status bar, will this method work?
[Nook Color Android Development] verygreen:
You can use a special build and CWM-enabled SD card, or you can use image referenced in the first post of this thread and then you can use unmodified CM7 builds to be installed on the SD card
[Nook Color Android Development] acme2ajax:
Hi Verygreen,

Firstly....Thanx for the absolutely awesome CM7 card bootable version...

I am using your very first version, which has CM 7 ver 11....as I posses a 16gb card...and well, your newest creation, sadly doesnt work.. :(

However, I want to update my initial build.....

Just a small doubt,

After I change the uRecRam and uRecImg....do i need to have a CM7 update file in the first partition? Its a noob Q...but u gotta be careful :)

Do i need to place the cm7 update file in the first partition and boot up? So that the update is applied....

Once you claarify....i cn go about updating CM7 on my card...

Thanks again for your efforts.......
[Nook Color Android Development] acme2ajax:
Also, one more doubt...

How do we update the CM7 build....that is, is there any specific 'update' file or will a full CM7 nightly do?

I was unable to find any update files on the CM7 files.....
[Nook Color Android Development] DizzyDen:
acme... to update... do as you described with the uRec files then just download the latest nightly and copy it to the root of the first partition then boot into recovery install mode by holding power and "n" buttons until about 3 seconds after seeing the touch the future screen... It should automatically update the files for you.

You do not need to rename the nightly files... Green was very diligent about being able to catch nightlies and any update type of files.
[Nook Color Android Development] acme2ajax:
Ok....I dunno what I am doing wrong....

Here are the steps...

1. Downloaded the uboot.bin file and replaced it in sd card root

2. Downloaded the img and ram file and renamed them urecimg and urecram; replaced them in the sd card root

3. Placed the cm7 nightly in sd card root...

4. Booted the nook color....and as soon as touch future reading screen came up.....

5. Press Power+n for 3 sec (first try), 4 sec (2nd try)....>5sec (3rd try)

Yet, the clockwork image doesnt come up....Nook boots up to my previous BT CM7 installation...

Pls Help!!!!!!!!
[Nook Color Android Development] DizzyDen:
Don't wait until you see the touch the future screen to press the buttons....

With nook off.... hold N button... and Power button both... keep holding for 3 or 4 seconds after the touch the future screen appears... you won't see a clockwork screen that you are used to... you should see the penguin... and it should start extracting files.
[Nook Color Android Development] aludal:
I had similar experience -- unless I do everything from the start of verygreen's procedure, there's no "updating" occurs. Must be some typo in verygreen's ROM updating script, or I don't know. Hate to start everything again, with Gapps, 3rd or 4th time

In any case, I would love to see verygreen's own CM7 n30+ build at his repo, to start making my CM7 bootable SD anew, as there were lots of interesting commits today. Sure, I can wait till tomorrow, but still...
[Nook Color Android Development] DizzyDen:
Green... first let me point out, I only started documenting my test results due to other report of 16 gig cards failing and trying to help figure out what the cause is...

This is everything that gets displayed:

Initializing random number generator... done.
modprobe: chdir(2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
Partitioning the card ...

The number of cylinders for this disk is set to 1946.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Done partitioning, creating filesystems.
mkfs2fs 1.41.12 (17-May-2010) [COLOR="Red"]Sits here longer than on smaller SD's maybe expected due to size[/COLOR]
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
118784 inodes, 473916 blocks
23695 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
58 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Suberblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

Writing inode tables: done
Creating journal (8192 blocks): done
Writing suberblocks and filesystem accounting information: [COLOR="red"]Sits here eternally... this is where I have to hard boot to resume[/COLOR]

That looks to me like it is failing on the first mkfs command... but I could certainly be wrong.

Trying to find out how I can see IF the filesystems are there... In Aesus the partition info looks exactly the same... but that is irrelevant. Partition lables in ()'s

8 GB uSD:

Partition1 117.63MB FAT32 105.48 MB Unused (boot)

Partition2 462.81MB Other 0 bytes Unused (NO LABEL)

Partition3 964.84MB Other 0 Bytes Unused (NO LABEL)

Partition4 5.94GB FAT32 5.91 GB Unused (CM7 SDCARD)

16 GB uSD (AFTER HANG PRIOR TO REBOOT)

Partition1 117.63MB FAT32 25.24 MB Unused (boot)

Partition2 462.81MB Other 0 bytes Unused (NO LABEL)

Partition3 964.84MB Other 0 Bytes Unused (NO LABEL)

Partition4 13.40GB FAT32 13.38 GB Unused (NO LABEL) (but this time it is being created.. I don't know... lol)

16 GB uSD (AFTER REBOOT and extraction)

Partition1 117.63MB FAT32 25.24 MB Unused (boot)

Partition2 462.81MB Other 0 bytes Unused (NO LABEL)

Partition3 964.84MB Other 0 Bytes Unused (NO LABEL)

Partition4 13.40GB FAT32 13.38 GB Unused (NO LABEL)

When the Android_ screen is there... I can see it in ADB but cannot shell into it...

C:\>adb devices

List of devices attached

11223344556677 device

C:\>adb shell

- exec '/system/bin/sh' failed: No such file or directory (2) -

I understand your point on this... since the boot partition is already created... the script works in extracting the CM7 files over the ones already there. Right now, I have no way of verifying if the Filesystems are populated or not... will keep trying for you though.
[Nook Color Android Development] verygreen:
My images are the same as nightlies so far so just use a nightly and you'd get the same stuff.

The booting into the recovery is somewhat tricky I agree, I cannot make it always work on the first time myself.

as long as you have correct u-boot.bin and uRecRam and uRecImg that are named properly and contain proper images, the boot with N and power both pressed should work.
[Nook Color Android Development] verygreen:
Ah, Thanks.

Yes, it does fail on the first mkfs command indeed.

So if you boot into an emmc nook image, can you do

mkfs.ext4 (or if you don't have this command, just mke3fs -j ) /dev/mmcblk1p2

and then mkfs.ext4 /dev/mmcblk1p3

all from adb

if it hung, then reconect with adb again without rebooting and see what's there in the dmesg output.

Probably the easisest way is to boot into emmc and do your stuff from there if you don't have a Linuxbox where you can insert this SD card.

booted from emmc from adb shell you can try to mount those partitions and if the mount fails, you will kno that the filesystem was not created

(though we figured that out just by the location of the initial install hang it seem).
[Nook Color Android Development] verygreen:
What error do you get from my installer?

to rom or wallpaper package author I would suspect?
[Nook Color Android Development] :
In the EMMC threads I see a lot of posts about clearing cache, Dalvik cache etc. before/after updates. Does this also apply to SD card installs, if so what is the easiest way to do it? Most of the instructions I've seen for EMMC reference ClockworkMOD.

A little confused as to whether or not all of that still applies for SD card installs or how we use CWM in conjunction. Or should I not be touching CWM or ROM Manager apps at all? Sorry if this has been asked before...still trying to separate all of the relevant info.
[Nook Color Android Development] joe2262:
I installed 1.2 of your installer then installed 7.1 beta and 5/13 OC kernel and all was fine. Upgraded to N82 and things still seemed fine, but upggrading to OC kernel 5/23 or N84 and N85 I seem to have lost the upgrade output, no penguin info screen. I've tried initiating recovery from cold start and reboot.

Oh yeah, I did upgrade to 1.2.1 using the zip file when you released it.
[Nook Color Android Development] rhester72:
For what it's worth, using VG's SDcard image, I've yet to have to clear any sort of caches and have had no related issues.

Rodney
[Nook Color Android Development] :
I've noticed that the boot screens on some of the nightlies are different. For upgrades via recovery, it looks like some of the newer builds no longer have the linux penguin but instead show a "loading" screen with partial text output on the screen.
[Nook Color Android Development] :
No issues here as well. I'm just a little wary because I've been jumping between stable and nightlies/oc kernels quite a bit to try and find the best setup that fixes my misc. issues.
[Nook Color Android Development] Homer_S_xda:
IIRC vg's installer clears caches after updating, before it reboots. If you are watching the text fly by, any you are aren't you? you can see the cache clears right before the rebooting note.

Homer
[Nook Color Android Development] :
Thanks. I can't always decipher what's going on. And on the newer builds its harder to see whats happening as the text only show up partially on the screen. (yes I know I'm full of excuses) :p
[Nook Color Android Development] joe2262:
I get nothing, blank screen but looking closely I can see the backlight. When the backlight goes off I know the install is done.:confused:
[Nook Color Android Development] :
I haven't tried the most recent nightlies. On N82 myself. I do agree that its hard to tell sometimes if you are booting into recovery and flashing successfully. A few times I have thought that my NC had locked up. :rolleyes:
[Nook Color Android Development] shumash:
I don't want to rerun it at this point, but I don't think it's your installer. It stops with an error that it expected a parentheses ) or period . or similar in the dalingren zip file installation script. When I just use the method in the OP of copying the kernel image to the /boot partition, it works like I described. Incidentally, I also installed the latest CM7 85 nightly, and tried dal's 5/23 OC uImage with it, and the wifi was broken in the nightly, too.

I wasn't able to change the wallpaper after I tried a Live Wallpaper. I had to rename the live wallpaper apk to keep it from loading, and then I could change the wallpaper using the Gallery.
[Nook Color Android Development] verygreen:
the "flushing caches" message you see has nothing to do with davlik cache. It's just pushing in-memory cached info to the sd-card before a reboot.

It does not clear /cache and I have seen no need so far. Besides it's a bit risky to just clear a somewhat random partition during update.

If you think you need davlik cache cleared, just boot into android, connect with adb shell and run

"rm -rf /cache/*"
[Nook Color Android Development] verygreen:
Hm, this is certainly unexpected, there should be a penguin screen no matter what CM7 version you are installing or have installed in the past. The installer kernel is different from that of the actual CM7
[Nook Color Android Development] verygreen:
The "unexpected parenthesis" error is in fact a combination for pre-1.2.1 installer and a script in the dalingrin's update.

If you update to 1.2.1 that particular issue should go away and installations should work.

Just copying the kernel file is not enough, though. You also need to copy the new wifi driver.
[Nook Color Android Development] Homer_S_xda:
Well... there it is. :o

Homer
[Nook Color Android Development] topcaser:
I have added a guides section in Wiki and linked this thread:

xdaforums.com/wiki/index.php?title=Nook_Color
[Nook Color Android Development] angomy:
Actually, that is what has been happening to me when booting using power + n. I've flashed 2 different nightlies and kernels with it now, just got used to peering closely to see when it's actually finished. (checked ver etc. in tablet info to make sure it was actually installing)

If I try to boot to recovery from Rom Manager it's a crapshoot -- sometimes the Linux penguin pops and I see actual steps scrolling up, sometimes it just goes blank and then shuts off when it's done. At least it's installing everything in either case?
[Nook Color Android Development] Awats:
Is this 5/23 emmc only? For SD, the latest I have is 5/13. Just checking.
[Nook Color Android Development] joe2262:
I just updated to N86 and upon rebooting I'm seeing the skateboarder logo and not fattires graphic. Is this because we use your u-boot? Once multiboot is included in the nightlies will we get to use it?
[Nook Color Android Development] Windsor1959:
Here's another newbie question. I have CM7 running beautifully on my SD card, thanks to verygreen's installer. I decided to backup my ROM, so I installed CWM with ROM manager.

So here's my question. Will CWM interfere with verygreen's installer if I want to update my CM7? If not, I'm fine! If so, is there any way to fix it, short of wiping my card and starting over?
[Nook Color Android Development] DizzyDen:
That is because CM7 has a new u-boot.bin and MLO included as of Nightly86... Once fattire's newest u-boot.bin is committed... it should be included and the menu will be back.

In the meantime.... IF you need the boot menu... you can place fattire's u-boot.bin in the root of the zip file... replacing CM7 stock so it will install it instead... OR you can copy it to the root of the SD after the Nightly update if you prefer that method.
[Nook Color Android Development] jared_c:
I wanted to dogpile on and say that I've seen this behavior too, but it was a while ago, like pre-nightly 59, which is the nightly I got impatient and held down the power button before it was done flashing and jacked up the uRecImg... had to copy over a fresh uRecImg extracted from the zip file to get recovery capability back. That brought back the penguin.

A complicating facter here is that I'm running off a class 6 card, so the slow randow write speed might be causing unexpected behavior.
[Nook Color Android Development] stolenmoment:
OK, I'm ready to install CM7 on the emmc; I've been running off SD for awhile now, how do I go about it?

Do I just install CM7 (steps?), then copy the old /data partition, take a new empty SD card and copy the old /sdcard partition (aka /mnt/sdcard) onto it?

I don't want to mess up, I've got several apps all nicely configured!

Thanks!

Dennis
[Nook Color Android Development] shumash:
I used the 1.2.1 update zip file to update the image. Apparently, it didn't take originally, but after applying it again, everything works. Thanks for your help and patience.
[Nook Color Android Development] DizzyDen:
What I have discovered is that when I use recovery mode to install an update... the uRecImg is replaced for some reason... thus next time the black screen updating occurs. To be fair... I use a weird mix... SASD 1.2.1 with fattire's 1.2 for the menu... with dal's OC... modified build.prop for playing and modified framework.jar also for playing.... but it seems to happen every time I update new nightly...

Tested with JUST updating dal's OC kernel... the uRecImg was not modified.
[Nook Color Android Development] angomy:
That makes sense, and explains why every fresh install I have of the image uses the recovery screen and thereafter doesn't after updating to the latest nightly.

Is there an appreciable difference (or problem) with _not_ seeing the regular screen? I haven't run into any visible issues and I've updated my main uSD from 7.0.2 -> nightly 87 + 05/23/2011 OC kernel (and all iterations between).
[Nook Color Android Development] DizzyDen:
I haven't found any issues once you know about it....

You can always copy the original uRecImg over when you copy the new nightly.

I have resorted to trying uAltRam and uAltImg to see if it will prevent it on my next round of testing....
[Nook Color Android Development] verygreen:
You know what, you are totally right and I just found the bug in the installer script that causes this.

A fixed version is forthcoming.

Thanks.
[Nook Color Android Development] jakewalker:
"Wifi error"

So I followed the OP's directions, and everything is fine until I install one of the OC kernels from darlings thread, my wifi does not want to work at all. "Wifi error"... Does anyone know what i;'m doing wrong? maybe the CM7 file the OP suggests is outdated??
[Nook Color Android Development] :
Is it really necessary to charge to 100% before you flash a new rom?
[Nook Color Android Development] verygreen:
No, it's not.

But you better have enough charge for the entire process to finish.
[Nook Color Android Development] :
I normally have my NC plugged into the charger whenever I'm flashing. :)

So this stuff about charging to 100% to insure properly battery calibration (mentioned in a few guides) is just hogwash?
[Nook Color Android Development] JohnnyDanger:
Hi everyone. I installed CM7 onto a SD Card and it has been working perfect for a good month and half. I decided to try a newer build and kernel, but now I cant get past the boot screen with the Droid guy on the skateboard. The circle just keeps spinning and spinning.

Im going to format my card and start over. I wanted to know if anyone can recommend the best, most stable, build and the best OC kernal to use with that build. I appreciate any help.

Thanks.
[Nook Color Android Development] :
7.0.3 STABLE :P

In all seriousness though, most of the nightlies seem to cause some people random issues. And what's stable for some causes issues for others (for example wireless problems). 7.0.3 + 042411 OC kernel worked well for me but I like to try out the latest and greatest. ::shrugs::
[Nook Color Android Development] JohnnyDanger:
Thank you. I will try that. Hopefully I dont screw it up. LOL

**Edit**

Ok, so I installed the stable 7.0.3 build and then put the 04/24/11 kernel on the card. Its not working.

When I turn on the Nook in turns on and says "Loading...", then it says Android on the top left side (bottom left if holding horizontal), then it small white line appears on the top right corner (top left corner if holding horizontal) and it just hangs right there. Nothing else happens.

Does anyone have any recommendations on how to correct this?
[Nook Color Android Development] JowBe:
Works like a charm. Thanks!