yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] heavenlydemonic:
Not bashing you or trying to start a flame war, but the planets must have aligned for you if you got any type of good performance at all with a Kingston Class 6. I tried three different Kingston SD cards and not only did the install take about 10x as long as using a Sandisk (Class 2 or 4), but I was BARELY able to get GAPPS installed, much less working without a ton of Force Closes and other crappiness.

I have used Verygreen's awesome Installer on five Nooks, and to be honest, Verygreen's installer was the sole reason four other people bought a Nook, once they had a chance to play with mine.

So moral of this story: Thanks Verygreen 100x. Don't use a Kingston, and if you do, what is the exact Model you are using?
[Nook Color Android Development] verygreen:
Updating just MLO should be enough.

You can update u-boot.bin too, since it should contain all my changes too.

I guess time to make another release with the new MLO, I long suspected that we should have upadted MLO along with u-boot from the very beginning, but did not have hard evidence.
[Nook Color Android Development] verygreen:
Install the entire update...zip by copying it to the first partition of the SD card and rebooting into recovery.

Just updating the uImage will break wifi because you also need the updated tiwlan module that is provided in the zip file, but you did not copy in the proper place.
[Nook Color Android Development] zombieflanders:
Looking forward to the 1.2.2. I might even install the OC kernel alongside.
[Nook Color Android Development] charm1718:
Help needed. I have a new NC that's running the 1.2 update. I installed CM7 7.0.2 stable & it woorks fine. I tried the overclcok kernel 4/24/11 & it goes past the screen that says Android in the corner but stays on a black screen with a dash in the op left corner.

All I did was unzip the 4/24/11 sd kernel and moved the uImage file to my boot partition on sd & replaced the other Uimage file. was this the correct step? Was I supposed to do more?
[Nook Color Android Development] Taosaur:
Racks' SD thread has versions of all dal's kernels that will install properly with verygreen's installer. Just scroll down the OP and grab the 4/24 .zip to drop in your boot partition:

http://xdaforums.com/showthread.php?t=998861
[Nook Color Android Development] joe2262:
You also need to adb push the /system folder to the Nook.
[Nook Color Android Development] charm1718:
The kernel I used is from that thread.

@joe2262- Is there a way to do this without using adb?
[Nook Color Android Development] zombieflanders:
Actually, I believe you don't need to do either the uimage replacement or the adb push if you're using the 1.2.1 updater. It should just work like the other ZIP files.
[Nook Color Android Development] charm1718:
When you say it should work just like the other zip files, does that mean I should just drop the whole kernel zip file in the boot partition & put the usd back in the Nook & it will replace the kernel?

I installed CM7 using the 1.2.1 updater. Now what step is next to use the oc kernel without using Adb?
[Nook Color Android Development] khaytsus:
No kidding, VG's stuff is awesome. You can just pop the card in, boot up, and show someone what their NC can really do!

Oops! I was using a Transcend 8G class 6 apparently.... I have a Kingston somewhere too, but I was clearly confused. I popped my old SD CM7 in a case and into my cargo pants "just in case".

So probably haven't used a Kingston.. Not sure at this point, I have too many damn microSD cards. ;)
[Nook Color Android Development] shumash:
Did that originally, and it broke, but I'll try again.

Thanks....
[Nook Color Android Development] joe2262:
Look for a 4/24 kernel with ext4 in the name, problem is the install script.

EDIT: Msg #2814 in http://xdaforums.com/showthread.php?t=925451&page=282
[Nook Color Android Development] charm1718:
Thanks for the link & the help. I downloaded that kernel. Do I unzip it and just place the uImage on my boot partition to replace the one already there or do I place the whole zip on the boot partition & flash through recovery?
[Nook Color Android Development] Taosaur:
You just need to put the entire zip file, unmodified, into the SD card's boot partition and boot to recovery. Verygreen's installer will do the rest.

The OC kernels in the thread I linked are already ext4, even though it's not in the file name. Ext4 versions of all of Dal's kernels are linked in the OP if you scroll down: http://xdaforums.com/showthread.php?t=998861
[Nook Color Android Development] charm1718:
Thanks again
[Nook Color Android Development] Thirtybird:
VG - I've done a complete wipe and reload of the 1.2.1 with beta 3.1 and still no adb. Then I reflashed the card with the 1.1 and put the beta 3.1 on, and adb works. I still think there is something not quite right...

Every other device or build combination I have works on this machine (and I tested on my laptop with the same results) - I cannot get adb working with the new image.
[Nook Color Android Development] Homer_S_xda:
I can second this, adb seems to have dropped out for me as well. Running 1.2.1 and latest beta from sdcard.

Homer
[Nook Color Android Development] doncaruana:
I'm trying to piece together and follow along enough to take the leap and get CM7 strictly on the SD card. Is this problem with the SD card process or with the beta 3.1 build itself? Sorry if this is a dumb question...
[Nook Color Android Development] Thirtybird:
The only thing different between working and non-working adb was the version of the sd card image (and its contents obviously).

If someone has adb working on the new load, maybe we could compare drivers? If something has been updated that requires newer drivers, lets figure that out...

BTW - Wireless ADB works just fine, it's only the USB portion that isn't
[Nook Color Android Development] verygreen:
This really is strange. Did it work with v1.2?

I did the install with 1.2 and the build specified in the first post and it does work for me.

If any of you for whom adb does not work have a Linux box where you can plug a nook running CM7 with non-working adb, I am interested to see a bit of dmesg output from the Linux box that describes the connected device.

Also if you do a wireless adb (or just in terminal) and do cat /proc/version, I hope it does not tell you the kernel was built by green@fatbox1 because if it does, that means you somehow ended up with recovery kernel being loaded as main one (and the recovery kernel does not have adb compiled in)
[Nook Color Android Development] hogasswild:
I feel pretty stupid here. I just got the nook color today just so I could do this dual boot process. I thought this was simple enough to do, but I'm still stock. Am I supposed to already be rooted to do this whole process? I placed the cm7 zip, gapps zip and the installer image all on the external, but I'm thinking the install image is supposed to go on the internal memory. Please sort me out.
[Nook Color Android Development] Taosaur:
You're mixed up on several things. This blog has a more step-by-step breakdown including videos: http://www.anamardoll.com/2011/04/ereader-running-cm7-firmware-on-nook.html

You can skip the long, rambling intro straight down to "Ready? Let's get started."
[Nook Color Android Development] kz121:
hogasswild,

i've sorta been in a similar boat as you regarding ADB - i've never gotten it to work ever... I've all but given up on it entirely... (believe me, that's an issue cause i want to run gapps in honeycomb 3 badly enough that i'm about to buy a xoom if i can find the money)...

i finally came to a point though... here's the exact file names, as downloaded i'm currently using and is about the only fully stable set up i can seem to keep running off the SD without rooting the NC or using ADB or putting anything in to EMMC (internal memory)

install vg's sd card image 1.2 to your SD card (generic-sdcard-v1.2.1.img you must unpack the .gz file so that it is just a .img file then write it to the SD - there are a ton of tutorials on this)

once it has formatted your sd card and you re-mount it (should happen automatically on your computer) then you put the following in to your "BOOT" folder on the SD:

i'm using:

update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip

gapps-gb-20110307-signed.zip

once you do this and get up and running you will shut down the nook and put the SD back in the computer - place the OC kernel listed below in to the boot directory - unmount the card put it back in the nook and boot back up.

now you will be able to use VG's bootloader to flash the new kernel which is accessible via holding the power button and selecting REBOOT and subsequently hitting "recovery"

update-cm7-dalingrin-2.6.32-sdcard-051311.zip (this file contains the new overclocking kernel needed to run netflix and will boost your device's performance)

I would suggest that you make sure you install titanium backup and make sure you are running the latest clockwork rom manager as well which you can also use to create backups with (downloadable from the app store)

sorry i couldn't include links to each of these files directly but you should be able to find them online via a google search or xda search...

some people will say there are issues running the beta i suggested above...

from what i have been reading over the last few days it would seem that the nightly builds are being built around the beta kernel and the OC kernel now - running the older signed "stable" cm7 releases (like 7.0.3) ran me in to issues when i got tired of FCs (force closes) and attempted to run a nightly build where by i totally screwed up my images and my SD card so that nothing i did would resolve the FCs... so far so good using the beta...

best of luck... PM me if you need to...

p.s. - i was you just about 1 month ago...

-chris (kz121) - sorry for the novel - but this whole process of getting straight info lately about what goes with what has made my head numb!!!
[Nook Color Android Development] hogasswild:
Good to go, thanks much! I'm so used to doing things on my DX, I was way overthinking it.
[Nook Color Android Development] lschroeder:
I did the following to have battery display correct low and no charge messages (did not change mlo but used Stock 1.2 to initialize values):

http://xdaforums.com/showpost.php?p=14008953&postcount=2372

Has anybody tried using nightly 82 over beta3.1 with verygreen's recovery? I guess we would need to to also do OC again?
[Nook Color Android Development] FRSP:
Sorry if this has been covered, but I could not find it.

The v1.1 image works fine for me, but if I try to do an install with the v1.2.1 on a brand new sandisk 16gb class 4, it never gets beyond the "Loading" screen on the initial boot (ie, booting the 128mb partition which should then create the real layout).

Is there a dependence on something on the EMMC? I have cm 7.02 on mine...
[Nook Color Android Development] verygreen:
Likely the BCB in EMMC contains a recovery request.

About easiest way to clear it is to boot from EMMC (it'll probably go into recovery), and then boot again from emmc into CM7.02, after that just do a poweroff and then boot from SD
[Nook Color Android Development] FRSP:
Am I mistaken, or does CM running under this (by which I mean version 1.1) still use an emmc partition for /cache? At lest that's what mount seems to show.

Trying an SD card with this script seems to destabilize my emmc install - which is what I would expect if it's trying to share a dalvik cache with another android version.
[Nook Color Android Development] FRSP:
Perhaps I'm misunderstanding, but I thought the point of installing an an sdcard was to be independent of the internal install. Wouldn't it make more sense to ignore everything on the EMMC by supplying your own BCB? Or is there a reason that can't be done?
[Nook Color Android Development] doncaruana:
For me it took an EXTREMELY long time the first go around there. I thought it was screwed but I was busy doing something else and just let it run. It eventually made it through.
[Nook Color Android Development] verygreen:
BCB is just a switch to trigger recovery on next boot. It's located on 2nd partition on eMMC and is mounted under /rom

We don't have space for it on SDcard with the current partition layout and there are no problems in reusing the on-MMC switch for the purpose I think.

When I update the installer for the next version I'll make it ignore the BCB on the original boot, but obeying BCB on eMMC when booting into SD still has its own benefits (right now it allows for the "reboot into recovery from CM7" to work, for example).
[Nook Color Android Development] Thirtybird:
I don't have the 1.2 installer - only 1.2.1 that is linked in the first post....

the proc version is erik@myhost - which makes since since wireless adb works... I will be able to hook it up to a linux box at work on monday and let you know what dmesg says.

I don't know if this helps, but I can mount partitions natively in CM7 onto the windows machines, I can charge through the USB port, I can get Wireless ADB to work, I just don't get hooked up with ADB over the USB cable...
[Nook Color Android Development] Taosaur:
I can't guarantee this guy isn't having other issues, but thought I'd bring this up:

Has anyone had success running the SD install on a NC with the new partitions? Any reason it wouldn't work? There's a breakdown of the new partitioning here: http://xdaforums.com/showpost.php?p=13962169&postcount=17
[Nook Color Android Development] Windsor1959:
Here's a slightly bizarre newbie question: could verygreen's installer install B&N's stock 1.2 on an SD card? I'm currently running CM7 off an SD, thanks to verygreen's fine work. I wondered if it could work in reverse : CM7 on internal and stock on SD.

Thanks for any thoughts. Once I get a couple more SD cards (including a SanDisk), I may try an experiment. The worst that can happen is nothing!
[Nook Color Android Development] verygreen:
New partitioning scheme did not change number of partitions or their meaning, just the sizes, so SD install is unaffected (not that I tried, but I don't expect any problems).
[Nook Color Android Development] verygreen:
While it's possible to prepare an installable stock image to install onto SD card, if you just grab the zip image of the latest update (or make one from existing install), it's won't work with the current installer because some file that need to be updated are named a bit differently and so would not be updated.
[Nook Color Android Development] angomy:
Just updated from stable to nightly 82 w/o any issues, was able to flash OC kernel at first try. No wireless issues, Adobe Flash 10.3 running great for my streaming video sites (disabled device Netflix giving chipmunk voices again but it's a hack. (doh, nightly 83 came out, time to flash again).

Would you consider adding the option to multiboot (SD, EMMC, recovery) at some point, verygreen? I'm very grateful for the work you've put into this already, so I totally understand if it would be something you didn't feel like doing.
[Nook Color Android Development] verygreen:
It seems multiboot-capable u-boot would be shipped with CM7.1 soon, so I'll just add some logic to copy provided u-boot from the update file (in 1.3, once this stuff is committed into CM7 repo in the few coming days) and that's it.
[Nook Color Android Development] Windsor1959:
That makes sense to me. Thanks for your response.

Right now, I'm running CM7 on a PNY card. It's actually not bad at all. I want to try a SanDisk card and see how that works.
[Nook Color Android Development] angomy:
Thanks man, good to know re: 7.1 changes and planned updates for this excellent image.
[Nook Color Android Development] topcaser:
Iam running also nightly 83. Do you mean that you was able to run newest OC Kernel with this built?

Iam so confused which OC Kernel is to get to work with latest nightly. I found a post here which mentions an existing ext4 Version...
[Nook Color Android Development] joe2262:
For nightly 82 and I suppose 83 you want OC kernel 5/13, whhich tops out at 1200mhz.
[Nook Color Android Development] cfrock:
Bit of a problem. I just can't get into recovery using this no matter what I do.

I've tried both methods: the power up holding N + power, let go power etc.. as well as letting it boot normally and selecting Recovery from the power down menu (even tried thru rom manager) but it just reboots normally. I don't get it!! I've started from scratch 3 times in reburning the image etc.

Any ideas?
[Nook Color Android Development] celticchrys:
This file, when decompressed, does not include a .img file. Where can I get the .img file to write to my SD card?
[Nook Color Android Development] dexx0008:
a little bit farther down in the OP verygreen links to nightlies or the beta, you could grab a stable build as well.

download that and drop it in the boot partition after writing the image generic 121 image.
[Nook Color Android Development] celticchrys:
duh. nevermind. I grabbed the wrong file, it seems.
[Nook Color Android Development] lanzagas:
Sorry if there is an answer for this.

Netflix without checking device for n83?

I updated to n83 and have the chipmunk issue with the apk one that does not check the device. I just don't like to change the properties back and forth.
[Nook Color Android Development] angomy:
Yes (05/13/2011 kernel). That kernel should be ext4 afaik? I just peeked at the updater-script in the zip and it says ext4.

Re: Netflix on n83:

I haven't found a solution for that. Didn't want to edit build.prop so tried running either of the two disabled-device apks (still chipmunk issue).
[Nook Color Android Development] celticchrys:
I'm just posting this in case it might help out someone else. I was getting error messages that there was not enough room on the card to write the image. This was with an empty 8 gig card.

I had been trying to use win32diskimager-RELEASE-0.2-r23-win32 to write the image and getting this error.

I switched to the older version, which is win32diskimager-RELEASE-0.1-r15-win32, and the image wrote perfectly on the first try.

I suggest to anyone using a newer win32diskimager version, who is getting error messages saying their large empty card is too small, to try this one instead: http://launchpad.net/win32-image-writer/0.1/0.1/+download/win32diskimager-RELEASE-0.1-r15-win32.zip
[Nook Color Android Development] LBN1:
Just an FYI, the Netflix w/o checking device apk, runs perfectly on my install of Nightly 78.
[Nook Color Android Development] topcaser:
OC 051311 Kernel works with n82. Nevertheless - wifi is not running any more. I have read here from netflix and some other fixes, but found no description how to install. What do you recommend me?

PS: n83 change log describes something about radio setting: http://cm-nightlies.appspot.com/?device=encore

Would that help me?
[Nook Color Android Development] topcaser:
Got it running by copying the entire update file of the OC Kernel to SD Card and booted into recovery. Some pages before one has already posted this solution.

Nevertheless, system lags sometimes (iam on a pny card), e.g. when i want to read an Email in gapp the app needs some seconds to show the content of the email. This is not with my HTC Desire. I would say, the speed of showing the content is not much better than with the stock Kernel and 900 MHz overclock.

As soon as iam in back in germany i will buy a sandisk. Someone has posted here, that he is happy with the pny card. Does your system lags also sometimes?
[Nook Color Android Development] FRSP:
Tried n84, gave up due to extreme instability - constant crashes of browser, etc with an address in libskia, plus some wifi weirdness partially stabilized by booting with it off and then re-enabling.

But the point I want to make here is that on trying to go back I could no longer boot into recovery on the sdcard - I found that the recovery kernel from verygreen's script had been replaced on the sdcard by the one in n84, though the recovery ramdisk remained unchanged. That didn't seem to happen with earlier cm builds? Putting the one from 1.2.1 image back on the sdcard fixed that problem.

I still seem to have an extremely unstable nook... and whatever install is on the EMMC gets broken by running anything from SDCARD with this script - I suspect sharing the /cache partition is not really workable - some of it gets recreated on boot, but apparently not all.
[Nook Color Android Development] pchoi94:
hi all, i'm running the latest stable build (2.6.32) with the Dalingrin OC kernel for it (051311) off of SD card on my nook color. OC'd to 1200 with smartass. i ensured i got a decent performing sandisk 16gb class 4 (approx. 0.5 - 0.8Mbps 4k random write speed 32 depth). using launcher pro plus.

first off, changing to this sd card from my older kingston made a WORLD of difference. everything feels INSTANT... for the first day or so of operation. after a while the system seems to get laggy, but it's not the same kind of laggy i used to experience with the older sd card, it is a general overall UI lag, no force closes. it usually happens after i run some app i'm testing, like some type of video player, netflix, or flash in browser, game, or something. a reboot fixes it. running advanced task killer and OSmonitor it doesn't seem like anything weird is running. OSmonitor reports that the CPU is only under about 40 - 50% load.

is this normal? is anyone else experiencing this?

thanks!
[Nook Color Android Development] angomy:
Nightly 78 runs on the .29 kernel, which is why it works fine. I haven't tried a .32 based nightly where it's worked (either chipmunk voices or severe system slowdown/video stuttering).
[Nook Color Android Development] lschroeder:
If you are loading the 5/23 OC kernel and attempt to install update-genimage-1.2.1.zip at the same time it will hang. For 1.2 versions you must boot into recovery with update-genimage-1.2.1 only. Then boot into recovery again with 5/23 OC kernel.

@verygreen - do we need a new or recompile of your boot loader with Dal's 5/23 OC kernel? I took stock 1.2 all they way down to 15% warning and then reboot, charged back to 100%, then did 15% warning 1% reboot with this SDcard version of beta3.1 previous OC kernel? Don't know if that has any effect?
[Nook Color Android Development] verygreen:
I am not sure what are you asking about.

The uboot should not change (aside from apparently need to update kernel cmdline to enable overlay)
[Nook Color Android Development] verygreen:
I have not seen any ill-effects so far (but I run stock on emmc).

If it proves to be real problem, I guess we can move sdcard cache into a subdir on /cache
[Nook Color Android Development] LBN1:
Oh I knew that. :) I was just reporting so others know that if they really wanted that Netflix app to run, which Nightly did work. I've been staying on this build cause it really works well, while I wait for the next Stable release.
[Nook Color Android Development] topcaser:
Hi,

i have a question to get into the recovery mode - especially to verygreens sequence:

i have tried it and it dont work for me. So, when do i have to release the nook-button exactly between the first and the second power switch hold down? Or do i have to press it constantly?

Edit: Got it now: Here a description:

I have done:

1. pressed and hold nook button

2. pressed and hold power button until Loading disappears

3. released both power button and nook button

4. wait a second or so

5. pressed and hold power button again for 5 sec

6. released power button

7. pressed and hold nook button until screen went off
[Nook Color Android Development] topcaser:
n83 + new kernel OC 052311 Kernel breaks my WIFI. Flashed then n85 but WIFI is still broken.

Going back to n83 now. Hopefully WIFI works again.
[Nook Color Android Development] Homer_S_xda:
Did you flash in one reboot or two? I had 84 and OC working having flashed them one after the other. I then went to 85 and the same kernel but let it flash both in the same reboot cycle. My WiFi did the spinning and connecting but never connecting.

I flashed the OC again by itself and after forgetting the connection and redetecting/reentering password it was fine. Currently on 85 and OC.

Homer