yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] case-sensitive:
I have clumsy fingers and I can't always time the power+N combo correctly; if this alternative method could make it easier to go into recovery then I'm all for it.

Thanks!
[Nook Color Android Development] zombieflanders:
Count me in for including both methods as well. I've gotten power+n down to where I get the timing right most of the time, but any way to make it easier while also retaining the original is fine by me.
[Nook Color Android Development] LBN1:
Yes please! Thanks for asking and all your work.
[Nook Color Android Development] jtbnet:
Though I've gotten used to using j3mm4r' menu u-boot for 1.x, I do like to keep the the PWR+N functionality for when needed...
[Nook Color Android Development] angomy:
Two noob questions:

1. With the u-boot.bin file updated to 1.2 in the next image, will I be able to use nookie1's updated multi-booter based on 1.2?

2. " ", will I be able to install and run 2.6.32 versions of CM7 with dalingrin's OC 2.6.32 kernel? (i.e. will your recovery method convert it for SD install). This is re: "The image would correctly detect unmodified CM7 builds and would make necessary adjustments to make them work on SD card.". When I tried using this image for the beta 2.6.32 install (dropped in the 1.2 u-boot.bin file from nookie1's multiboot) I got a NC stock error (rectangle with !) so I wasn't sure if it was trying to write to the card or to EMMC.
[Nook Color Android Development] verygreen:
It's really one or the other.

Works for me. (tested on update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip)
[Nook Color Android Development] verygreen:
I uploaded the v1.2 update and updated the first post.

Check the "recovery boot" instructions, they are changed and I believe together with the updated u-boot binary the triggering of it should be easier (even with older u-boot binary updated sequence of events is probably more robust).

For those who want to upgrade I provide update zip that would do the updating, no need to replace files by hand anymore.

I tested the upgrade and it works. Also supported is simultaneous u-boot upgrade + update to .32-kernel based image from dalingrin.

The new image with 2.6.29 kernels is untested! But it might still work, i guess.

Enjoy.
[Nook Color Android Development] angomy:
Thanks so much! I really appreciate the time and effort you've put into this. Wish I could buy you a beer. (Or a bratwurst).
[Nook Color Android Development] TheTodFather:
You should changer your name from verygreen to veryNICE! high five!
[Nook Color Android Development] zombieflanders:
Holy crap. The 1.2 update+2.6.32 kernel worked on the first try. You and dalingrin have a lifetime of good karma coming your way. May there be many free drinks and hotties in your futures.
[Nook Color Android Development] bonzer2u:
I will second that notion...

thanks again.
[Nook Color Android Development] surfer1010:
Sorry for the NOOB question, searched to no avail, image installed fine, but I cannot get past the cyanogen7 android boot screen. Tried to circumvent by going to CWM recovery, just shut down. Used the 26.32-3.1beta. Thanks for any help.
[Nook Color Android Development] verygreen:
How long did you wait? First boot takes quite a bit of time, esp. with slower SDcards.

You can connect with adb and check logcat to see what the system is doing.
[Nook Color Android Development] zentex:
nevermind...
[Nook Color Android Development] surfer1010:
About 25 minutes, I'll try adb, Thanks
[Nook Color Android Development] Taosaur:
+1 I would love for the in-OS Recovery Reboot options to work, but having the failsafe is a higher priority.
[Nook Color Android Development] neoshi:
I seem to have a few odd problems after doing this size agnostic uSD CM7 after running the former non-size agnostic uSD CM7..

1) Had to reinstall adb drivers... adb devices no longer detected the nook color

2) After reinstalling, device showed, but is no longer named 11223344etc that it used to be

3) adb shell mount yields "mount: not found"

Any help would be appreciated. Thanks!
[Nook Color Android Development] verygreen:
The symptoms mean either mount failed (do you have 16G+ sd card that did not work at first during the format phase?) (I assume you do not get to GUI as well)

or you have some wrong ramdisk-kernel combination (like unmodified kernel from stock and cm7 ramdisk or the other way around).

if you don't have any valuable data yet, I'd think full reinstall would be best.
[Nook Color Android Development] neoshi:
thanks for the quick response verygreen :)

it's an 8GB card that has been working fine with your previous uSD CM7 work. by not getting to the GUI, i'm assuming you mean that the NC isn't booting into the visual interface portion of the OS, but it is. it's working great, aside from the fact that i can't mount now :( i followed your OP instructions to the letter (using the recommended .32)
[Nook Color Android Development] verygreen:
Well, if it boots to gui, then everything is mounted correctly for sure.

I am not sure what is the mount error then.

Looking at your previous message, what are you trying to do with "adb shell mount"?

"adb shell" would bring you to adb shell if that's what you need.
[Nook Color Android Development] lschroeder:
I did the upgrade for installed v1.1 with update-gemimage-1.2.zip in first partition. It worked perfectly. Thank you.

When I attempted earlier to load with a fresh install using generic-sdcard-v1.1.img with .32-kernel beta3 + cm7 gapps + OC kernel update-cm7-dalingrin-2.6.32-sdcard-051311.zip it hung with at OC with /etc/init.d/S99Inital install: /tmp/updarescript: line 1: sytax error: unexpected word (expecting")". I tried again, leaving out the OC kernel and everything went fine. After installing Titanium Backup and restoring files this is what I upgrade with update-gemimage-1.2.zip in first partition..

What is procedure for installing OC kernel update-cm7-dalingrin-2.6.32-sdcard-051311.zip? It contains META-INF folder, system folder, and uImage. Do I need more then copying over uImage? Was Dal's script for OC missing a closing ")" the problem that caused it to fail?
[Nook Color Android Development] verygreen:
Supposedly you can just drop the update zip with the kernel and boot into recovery and it'll install it. This was not tested, but I don't see why not.

You'll still get the same syntax error, though. Just ignore it in this case. This is because the update script in META-INF is in some other language, I have a hackish interpreter for it good enough to handle simple cases like installing a full update, but unsupported commands will result in syntax error.

It did not work before because the kernel had unconventional name (read not the same as in normal update)
[Nook Color Android Development] lschroeder:
Thanks. It still gives the same error and hard boot will return us to recovery because the file did not get erased. At this point I pulled the sd card, install in the computer and removed the OC file. Inserted it back in Nook while still in recovery. Hard boot and returned one more time to recovery. This time no errors. The next hard boot worked and used setting to OC to 1200. Thanks again for your work and help.
[Nook Color Android Development] robot8:
verygreen, thank you very much indeed for the updates! :D
[Nook Color Android Development] dexx0008:
thanks verygreen, this worked perfect on my 16gb class4 sandisk
[Nook Color Android Development] Shuu:
Thanks for the updates, but now when I try to add my google account, any time I use a number it kicks me back a screen. It doesn't matter if I hold the qwerty keys until the number appears or use the ?123 button. Any tips?

Using: update-cm-7.1.0-RC0-encore-2.6.32-beta3.1 and gapps-gb-20110307-signed.zip
[Nook Color Android Development] verygreen:
I found installing gapps and the cm7 in one go to be problematic, so I still woud recommend to install the cm7 first, then setup your wireless and only then install gapps. Otherwise I get some pretty weird behavior.
[Nook Color Android Development] victle:
Thanks verygreen for the updated version. I still got sluggish problem after using youtube, the whole system was slowing down a lot, similar to the previous u-boot.bin. Anyone have the same problem?

Thanks!!!
[Nook Color Android Development] angomy:
No, but I'm not using the OC kernel (just CM7 925Mhz OC) so my setup may be different from yours. Haven't had any youtube or flash issues.

The battery life difference between .29 and .32 is astounding! I'm so glad to have switched. Thanks again verygreen for updating your image file.
[Nook Color Android Development] GTT1:
Posted this on Dalingrin's OC kernel thread but it was suggested I would get better help here

I am using SD card and the following build

update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip which I got from latest OP here and updated from my previous CM7.03 build.

I took this OC , update-cm7-dalingrin-2.6.32-sdcard-051311.zip which I believed was a match for it.

When I go to the nightly/stable builds I don't see the cm-7.1.0-RC0-encore-2.6.32-beta3.1 ROM listed, can someone tell me which nightly it is closest to?

Also the new image from new OP I assume is for setting up new and cannot be used if you are now updating. Is there anyway to add the new updater that eliminates using the power(n) combo?
[Nook Color Android Development] angomy:
Quote from Verygreen's updated OP:

"How to update if you already installed using v1 or v1.1 of the installer and don't want to reinstall (understandably):

Get update zip from http://nook.handhelds.ru/sdimage/upd...nimage-1.2.zip

Put the zip file as is onto the first partition of your sdcard..

reboot into recovery (triggered by the keys, the reboot into recovery does not work yet).

The new version would be installed and you are done.

You can combine this installation together with updating to .32 kernel in one step. Just put the update-cm file and the update-genimage-1.2.zip to the first partition. Make sure there is still at least 1M of space left!

"
[Nook Color Android Development] Andy53:
Posted this also on Dalingrin's OC thread, but this may be a better place since I don't know were the source for my problem is:

I had on may SD card stable 7.0.3 without OC installed with the 1.1 Size-agnostic...

Today I upgraded to the 1.2 u-boot.bin by means of Update-BN1.2-uboot.bin.zip and then updated to the CM7.1 2.6.32 RC0 beta 3.1 using update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip. All went well and all data and settings were saved.

After copying the overclocked kernel uImage from update-cm7-dalingrin-2.6.32-sdcard-051311.zip, which was the scope of all my updates, it seemed all is well, except I was not able to start the WiFi. When checking the WiFi I always got an "error" in the settings with 800MHz and also 1100MHz, and even after some reboots and also running set_permissions I belive (read this somewere) nothing helped. Only after switching back to the original 2.6.32 kernel (by copying it) the WiFi started working again.

May be somebody can look into this if it can be reproduced.

Thanks to all devs for the wonderful work!

***Edited*** Works perfectly after updating also the WiFi Drivers found in the OC package. After upgrading 1.2.1 sd image from these threat the installation of OC kernel can be performed easly by starting in recovery mode. This takes also care of the drivers update.
[Nook Color Android Development] joe2262:
After copying the OC kernel to /boot I too got a WIFI error which was cleared up by reverting to the original kernel. I wonder if the system folder needs to be pushed to the Nook?
[Nook Color Android Development] verygreen:
The kernel is now supplied with updated wifi driver.

If you only updated the uImage then you need the wifi driver too.

Supposedly just installing the entire update thing should work, but I got reports of it not working, so you can just get system/lib/modules/tiwlan_drv.ko from the kernel update zi and push it to /system/lib/modules/tiwlan_drv.ko on the nook

(make sure to remount /system as read-write first).
[Nook Color Android Development] verygreen:
Well, v1.2.1 of the installer is up, this time I really made sure that dalingrin kernels are installable. No other changes of notice so if you are not into installing other kernels, you can totally skip this update.
[Nook Color Android Development] jtbnet:
At least as far as going from a stable 7.0.2 (.29) to Beta 3.1 (.32). I used my current version on SDcard and used your original 1.x installer/updater booted from j3mm4r's 1.x menu-uboot and all was flawless... wait 10 minutes after first boot for cache to get rebuilt then used existing gapps already installed previously in 7.0.2 and updated all (21 apps) in a flash!

I have not yet had need to test out newer 1.2 uboot versions yet as basic movie playing was smooth as silk for me with rockplayer using stock 925/300 ondemand settings... granted just a quick pass/fail test but it passed with flying colors so far...

Thanx for all your hard work!
[Nook Color Android Development] angomy:
Tried to update via your instructions here:

You can combine this installation together with updating to .32 kernel in one step. Just put the update-cm file and the update-genimage-1.2.zip to the first partition. Make sure there is still at least 1M of space left!

Used update-genimage-1.2.zip from your update link and update-cm7-dalingrin-2.6.32-sdcard-051311.zip from Dalingrin's site.

Hangs on error:

/etc/init.d/S99initialinstall: /tmp/updatescript: Line 1: syntax error: unexpected word (expecting ")")

Going to re-flash base beta1 zip and try again with using just the 1.2.1 updater first.
[Nook Color Android Development] GTT1:
Thanks for clarifying, I confused myself due to reading so many threads and not concentrating, for some reason I was associating my BN 1.2 to the

v1 or v1.1 of the installer thinking my installer version was 1.2 when I guess it is 1.1. I will use the updater and get up to date.
[Nook Color Android Development] verygreen:
There is a problem with update 1.2, and 1.2.1 should fix it.
[Nook Color Android Development] angomy:
Sorry, I miswrote. I used the 1.2.1 updater in conjunction, not 1.2. Actually ignore this until I make sure I actually used the right one. I have the old one saved in the same download directory, probably was user error.
[Nook Color Android Development] GTT1:
Running CM7.1 beta from SD, have read about 1.2 u-boot.bin on Dalingrin's OC kernel thread.

Can someone explain what this is and whether I need it. Does the installer put this on your SD card or EMMC?

If I need it where can I download the Update-BN1.2-uboot.bin.zip

Would it be what is from the OP " http://nook.handhelds.ru/sdimage/upd...mage-1.2.1.zip"
[Nook Color Android Development] lschroeder:
It is not needed as verygreen update-genimage-1.2.1zip put its own version of BN1.2-uboot.bin. It says "Loading" instead of "READ FOREVER" whenever you boot from a cm7 sd ROM.
[Nook Color Android Development] lschroeder:
Before 1.2.1 was around, 1.2 does install the kernel before the error. My fix was while in recovery with error showing, remove sd card, insert in computer and delete kernel file, reinsert in nook, hard reboot twice and everything will be fine.
[Nook Color Android Development] thegameksk:
Wireless wont connect

I ran off my sd card and restarted so I could set up my wireless before putting market on. It gets stuck at obtaining wireless address. I know my passcode is correct and my routor is working fine. When I boot without the sd card in the nook my wireless works fine. Can anyone help?
[Nook Color Android Development] zombieflanders:
By dalingrin kernels, are you talking about the 2.6.32 or the 0513 OC kernel, or both? Your 1.2 worked just fine for me, but if I need to update I will. Also, is the OC kernel now flashable via recovery, or do we still need to do the "copy uimage+ADB push /system" method from the OP?

Once again, thanks many many times over for all the fantastic job you guys are putting in getting this stuff to work for all of us. It's hard to believe that you're willing to do all of this for no particular compensation. If you guys don't already have steady awesome jobs, I hope someone at Google is thinking of putting you guys to work making Android an even better OS.
[Nook Color Android Development] thegameksk:
Never mind I as able to fix my issue. Is there a hack to make the volume louder? Also is there anyway to remove the phone stuff that is in the rom?

Also I cant get the market on the phone. I download encore from here http://wiki.cyanogenmod.com/index.php?title=Latest_Version. I see no Gapps. Only thing next to nook color is encore.

Once I mount my sd card to my computer only the following show up

MLO u-boot (which is a vlc file) uimage uramdisk urchimg and urecram and they arnet folders so I cant put any files in them. I dont know what to do next with the encore file. Please help.
[Nook Color Android Development] joe2262:
I tried to update to 1.2.1 and OC kernel at the same time, it failed trying to install the kernel first. So... 1. I installed the 1.2.1 update. 2. I installed the OC kernel.
[Nook Color Android Development] verygreen:
1.2.1 is only for those who want to install stand-alone dalingrin kernels (like OC kernels), not the whole nightly update.

It's entire purpose is so that you cn install those kernels via recovery, not the copy uImage
[Nook Color Android Development] verygreen:
Actually this is expected and you lucked out that the 1.2.1 update was found before the kernel update.

The first update is happening with the old 1.2 code that crashes trying to install the stand-alone kernels.
[Nook Color Android Development] verygreen:
Scroll to the very bottom, the last table has what you need. (first entry there in the CM7 line)

Once you get gapps zip, put it alongside those other files you already have.
[Nook Color Android Development] angomy:
Ah, I had misunderstood you then (thus resulting in the error I posted about earlier). I had updated to 1.2 and flashed the .32 beta1 successfully, and then I tried flashing 1.2.1 in conjunction with the .32 OC standalone kernel because I had misread:

After my error, I ended up reflashing beta1 to get it back to the way it was before, then flashing 1.2.1 first, then standalone OC .32 kernel successfully.
[Nook Color Android Development] Taosaur:
Is it necessary or helpful to do these updates (ROM, kernel, or image) on a full battery? Or does it make no difference?
[Nook Color Android Development] verygreen:
Naturally you better do it with enough battery to last through update.

I suspect when you are doing the update you have ability to do it with usb cable attached which is even better. After all who updates those things on the go?
[Nook Color Android Development] robot8:
I think what Taosaur meant was if it would affect the battery calibration if it wasn't done with a full battery.

Don't think he should worry, if it felt off it's easy to re-calibrate the battery anyway.
[Nook Color Android Development] Taosaur:
I just did the 1.2.1/7.1/2.6.32 upgrade, and I'm just blown away how easy you made it, verygreen. It was literally drag-drop-boot, drag-drop-boot, and done. Thank you, sir.

HOWEVER

I'm seeing overall more sluggish performance, especially shifting from portrait to landscape, and several games aren't working (all white screens in NOVA, force closes in Speedx 3D). Results were identical with or without Dal's kernel. I think I'll go back to 7.0.3 and 4/24 until this build is more mature.
[Nook Color Android Development] waktasz:
Just tried today for the first time to venture into Nook-land. Everything seems to have worked, but the Market seems like it may take a week to download a single app. I've tried searching but can't find many relevant threads to this problem.

Is there a fix for slow Market downloads?
[Nook Color Android Development] robot8:
This may cure slow market downloads, amongst other things:

http://xdaforums.com/showthread.php?p=12964262
[Nook Color Android Development] Taosaur:
FYI, no problems flashing back to 7.0.3 and installing one of dal's ext4 OC kernels from racks' thread with the new uboot. Both "Boot to Recovery" in ROM Manager and p+n work for triggering an install. Everything's snappy again :D

+1 Sounds like your SD card is too high class. The NC don't have no truck with them high-falutin SDs.
[Nook Color Android Development] LBN1:
Question - how long does it stay at the "Loading" screen on the first boot after installing the 1.2.1 image with the recommended .32 build? It seems stuck there for several minutes.

Doing a fresh install from the beginning, and mine is not even getting to the CM7 boot screen, just the white "Loading..." message in the middle of the screen. This is when I am just doing a regular boot (not a recovery type boot).
[Nook Color Android Development] waktasz:
Thanks for the tip about the SD card. I was using a 2GB class 4 card I bought at Best Buy today and everything about CM7 was sloooow.

I switched to my 8gb class 4 Sandisk card from my Atrix and everything seems MUCH snappier.

I'm installing the Google Apps now so I'll know for sure in a few minutes.
[Nook Color Android Development] verygreen:
Did you finish the install yet or is this your first attempt with this particular card?

If it is first, boot into stock on mmc as there might be a "Recovery" boot request set in BCB there and we now obey that except there is no recovery image ritten on freshly written image before the install happened.
[Nook Color Android Development] LBN1:
Yes, that did the trick. (Rebooted into stock 1.2, then shutdown; then tried booting the new uSD and it loaded). Great tip, thank you.
[Nook Color Android Development] Thirtybird:
Partially the same problem here :

1st SD card (Sandisk 8 GB class 2) with the 1.1 bootloader and 7.1 RC0 beta 3.1 and 5/13 OC kernal boots up and works fine

2nd SD card (Sandisk 8 GB class 4) with the 1.2.1 bootloader and 7.1 RC0 beta 3.1 and 5/13 OC kernal boots up and works fine

3rd SD Card (Transcend 8 GB class 6) with the 1.1 bootloard and 7.0.3 stable and the 4/24 OC kernal boots up and works fine

on the first card and third card, my machine can identify the device in ADB, (as it can with my Droid phone), on the second card, the same machine cannot see the device with ADB

Reinstalling drivers (which worked for this poster) seems silly as the device is recognizable in two other installations, and the only difference between 1 and 2 is the bootloader.

Any thoughts or ideas what to look at? Re-setting the ADB flag in settings didn't make any difference, nor has reboots.
[Nook Color Android Development] verygreen:
New kernel has a bit different usb init, but still remains same 0x2080 id.

Still works for me with both new and old kernels too.
[Nook Color Android Development] LBN1:
Same here. Overall performance is more sluggish, but it is a beta build so I can't be that surprised. Running Smartxxx governor on 300/1200 settings; Linpack averages under 10, and Quadrant scores about 1200. Also, does not always wake up by pressing the N button, and had a random reboot when trying to wake up.

On a positive note though, getting to Recovery is much easier, upgrading is therefore easier, and standard USB mounting works again (was broken in recent nightlies).
[Nook Color Android Development] angomy:
My Market is conking out on the downloads as well. Gonna flash gapps to see if that fixes it.

Another thing I've noticed is if the screen is off (or the nook is asleep) when I unplug it from being charged pressing N doesn't do anything, I have to hit the power button to get it to wake up.
[Nook Color Android Development] souja:
Anyone have any experience with Wintec class 10 16g cards? The reason I ask is that I tried multiple combination's of verygreens image and different cm7 builds on my 16g card and it always seems to loop the boot animation endlessly. Tried the same thing with a sandisk class 4 8g and had no issues.

Would love to have the class 10 working =/
[Nook Color Android Development] mrmark93:
On the previous page of this thread was this post, the linked thread in that post has very good information about what's really necessary using an Micro-SD card for an operating system--
[Nook Color Android Development] khaytsus:
No-name Class 10? Unlikely. Get a decent card.