yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] :
Did you make sure that you flashed the ext4 version?
[Nook Color Android Development] JohnnyDanger:
AH Haaaa good sir, I did not. Let me check that.

Sent from my MB860
[Nook Color Android Development] :
Hey very green. Just saw the above regarding emmc install. Is the above something that can be implemented into the SD card install or is it emmc only? That loading text is kind of an eyesore. Especially that background color that doesnt blend in and sticks out like a sore thumb.
[Nook Color Android Development] vratner:
My apologies in advance if this question has been asked before, but I can't figure out how to do a search within this topic. In any case, I've been running autonooter for a while now, and have been generally happy with it. Recently, I found out that I can put Netflix on my NC, and of course dove right in. Turned out that I need a different version of Android, so I figured I can kill 2 birds with one stone, and will try CM7. I did (created a bootable SD card, and ran it off of it), and was able to successfully install, and watch Netflix on my NC. No problems there. In fact, it's frigging awesome!!! However, in the process my 4GB SD card became a 150MB (or something like that) card. I wanted to install several other apps on CM7 that require cache to be put in Android\data folder on SD card, but can't put more than a 100MB in there. I thought that this procedure automatically partitions the SD card, and leaves space for data, etc... Or am I just misunderstanding something here? Could someone please explain? Any help is greatly appreciated... Oh, and I want to leave the current setup, i.e. I want to leave autonooter, and run CM7 off of SD card for now, since I don't want to loose any BN features, just want to have more than Netflix when I'm running CM7. Thank you...
[Nook Color Android Development] DizzyDen:
To do what you want... write the original img to SD... prior to booting up in the NC.... use partition manager to resize the only partition on it at that point... something less than 2GB (bigger than 2GB and NC won't boot off it)

Then do the rest of the process... It will create partition 2,3 and 4... leaving "boot" (partition 1) the bigger size.
[Nook Color Android Development] JohnnyDanger:
So I cant find the ext4 version. Ive been looking and dont see that. Where do I get it?

And I need to claify, is there a stable cm7 release that says ext4 of it or just the kernel. I have the kernel that says ext4 in the title.
[Nook Color Android Development] :
Sorry I meant the kernel. Did you flash the ext4 version of the oc kernel?
[Nook Color Android Development] JohnnyDanger:
Yeah, I did flash the ext4 kernel. I just copy the uimage file to the root directory on the card, put it back in and turn on the nook, right?

Sent from my MB860
[Nook Color Android Development] :
That method from the OP never worked for me. I always flash the kernel using the same method as when updating the cm7 build. Copy the update.zip kernel file into the boot partition and go to recovery mode using power + n button.
[Nook Color Android Development] pryonix:
okay this is driving me crazy... :confused:

i installed the latest nightly (87 i think) and the 5/23 OC kernel of dalgrin without any problems.

however, i want to be able to install clockwork recovery (the one that lets you backup, restore, wipe cache, dalvik cache, etc etc) but i cannot figure out how.

also, is this installer compatible with either jammer's multiboot menu or the multiboot from this thread? (http://xdaforums.com/showthread.php?t=947698)

thanks
[Nook Color Android Development] JohnnyDanger:
That worked. Thanks a bunch. I appreciate your help.

Sent from my MB860
[Nook Color Android Development] cfrock:
Me either. Posted a question on how to a few days ago on this thread but never got a response. I understand the process as I've flashed, wiped, nandroid countless times on my evo and a few others. However, no dice here.
[Nook Color Android Development] :
I don't use it so don't quote me on this but I think it comes preinstalled under your apps. Check out the app labeled rom manager.

Sent from my Nook Color
[Nook Color Android Development] verygreen:
The v1.3 (hopefully tomorrow, still some testing left to do) will introduce the ability to pick u-boot from the new nightlies.
[Nook Color Android Development] verygreen:
the CWM is not compatible with the installer as they both kind of compete for the same "Recovery" mechanism to be called.

The altimage in practice could be compatible, but some of the two needs to be changed to go into alt image instead of the rec image.

The new nightly (after -87) will have a nice multiboot capable u-boot with menu that you'll really like, just wait for it.
[Nook Color Android Development] cannondale0815:
I tried the last two OC kernels (052311 and 051311), and both break WiFi. I didn't try any older kernels.

Thanks for all the hard work -- I just got my NC and tried various different ways to boot from the SD card, and your approach is by far the easiest.

Any way this could be done for Phiremod as well?

Thanks!

-J
[Nook Color Android Development] :
Rubbing my hands together in anticipation. Will finally be rid of that infernal loading screen.

Sent from my Nook Color
[Nook Color Android Development] :
I think phiremod is slightly larger in size so you'd need a larger boot partition. You should be able to resize the boot partition and flash phiremod the same exact way though?

Sent from my Nook Color
[Nook Color Android Development] danvee:
Agreed! All of VG's and Dahingrin's work is greatly appreciated...

On the WiFi front, though, I've run both kernels with the last 6 nightllies and have no real issues other than a slow wakeup of the WiFi radio (about 30 seconds) after the NC has been asleep.

I can't complain about that all.:D
[Nook Color Android Development] verygreen:
Ok, v1.3 update is there, first post updated.

Also a bit of an update on the new nicer u-boot.

Nightly -87 and a few after it will just have u-boot with nicer logo.

The super-nice one with menu and alt-boot is being held up while there are some investigations into the nature of premature poweroff problem.

So contrary to what I thought it's going to appear in nightlies somewhat later.
[Nook Color Android Development] :
Performed an upgrade to v1.3 but the same "Loading..." text is there at startup. Did I mis-interpret the changelog or do I have to start from scratch to get the updated logo?
[Nook Color Android Development] verygreen:
After you update to 1.3 it still retains the old u-boot.

Now you need to install a fresh nightly (like -87, even if you already had it installed) and the new install script would pick up the updated MLO and u-boot.
[Nook Color Android Development] :
Ugly loading screen begone. Worked like a charm. Thanks again!
[Nook Color Android Development] prehistorical:
Had no issues updating via recovery from fresh 1.2 with 7.0.2 stable, to 1.2.1 with update-cm-7.1.0-RC0-encore-2.6.32-beta3.1. But upgrading via recovery to this latest 1.3 with cm_encore_full-87.zip ended up with a recovery bootloop; pulling SD card and booting in emmc results in Orange recovery. :confused:
[Nook Color Android Development] verygreen:
Sounds like BCB-requested recovery.

But the 1.2.1 (and 1.3 too) are clearing the BCB before reboot.

You can tell the orange recovery (if it is what I think it is and you run some sort of stock in emmc) to abort the reset and then boot normally.

Hopefully after that the boot from sd card will also work.
[Nook Color Android Development] prehistorical:
Thanks,

verygreen

-- forgot to add details on the emmc -- I was on rooted stock 1.0.1 apparently with an old Orange recovery 3.0.0.5. I could not clear the condition, so I eventually gave up and restored the emmc to Stock 1.2 with data and cache wipes (using SD-based 3.0.2.8 recovery). Stock froyo is not too impressive!

I decided to try a fresh 1.3 image write of an 8GB SD Card, and plunked in the same nightly 87 then eventually gapps. I am experiencing a lof of FCs first with market, then installing/opening apps. Or even when trying to play certain office docs and move formats. Definitely a learning experience. Might go back to 1.2 with 7.0.2 stable?

Thanks for all the good work!
[Nook Color Android Development] TabletConnect:
How can I reclaim the unused partition on my SD card? I have a 4GB card but about 2GB shows unused and I cannot access it to add apps or media.

I tried using the Disk Management program on my Windows 7 but does not allow me to do anything to that "lost" partition.

thanks!
[Nook Color Android Development] Homer_S_xda:
EASEUS Partition Master xxx Home Edition, whatever the latest version is.

Homer
[Nook Color Android Development] cannondale0815:
Even with the latest 1.3 version and 87 nightly build, the OC kernels just don't work -- they break my Nook's WiFi completely. Am I the only one having this problem? The kernel included in the .87 nightly works just fine.

-J
[Nook Color Android Development] TabletConnect:
i updated to nightly 85 and OC 052311. My wifi is really slow so I am also having this issue.

How do I go back to the CM7 stable version? Can I just reformat my SD card and start from scratch (steps from post #1)? Not sure if anything is saved on the internal memory on the NC that would get screwed up.

thanks
[Nook Color Android Development] cannondale0815:
You are still better off than me -- my WiFi is completely broken with the OC kernels (it says "Error" in the settings and I cannot turn it on).
[Nook Color Android Development] bonzer2u:
Would this method work with the new phiremod 6.3 zip????
[Nook Color Android Development] Homer_S_xda:
How did you install the kernel? There is an updated WiFi driver in with it as well. You have to flash it or install the WiFi driver manually.

Homer
[Nook Color Android Development] cannondale0815:
I followed the instructions on the first post of this thread -- basically just copying the image file to the boot partition of the sd card. I didn't realize I had to install an updated WiFi driver as well... let me research it a bit more. But if you have a link handy, that would be great :)
[Nook Color Android Development] :
Did you guys try flashing the oc kernel using the same method you would a new build of CM7? (i.e. place in boot partition, reboot in recovery mode using power+n button)

Simply replacing the image file never worked for me once. Are those instructions outdated for the newer kernels verygreen?
[Nook Color Android Development] topcaser:
just put the entire zip file on boot instead of the single file and you are all set.
[Nook Color Android Development] topcaser:
Hallo Homer_S_xda,

just a question: The initial preperation of the SD card ends in 3 partitions:

1st is boot.

2nd is 463 MB

3rd is 965 MB

4th is 2,18 GB and labeled CM7 SDCARD

which partition shall i increase in size? I will not touch the boot partition. So there is 2nd, third and 4th left! Which partition is for what?? :confused:

Probably the 4th one, right? But what is with 2nd and third and why are they there?
[Nook Color Android Development] verygreen:
2nd is /system - your android installation live there

3rd is /data - program data lives there.

4th is /mnt/sdcard - this is the rest of space and is seen as an external sdcaed that you can load with whatever you like.
[Nook Color Android Development] cannondale0815:
Thank you -- that did the trick. The instructions on the first page were outdated.

-J
[Nook Color Android Development] verygreen:
Yeah, indeed. I just updated the 1st post to reflect that no special installation steps for OC kernels are now needed.
[Nook Color Android Development] TabletConnect:
On the 4th partition, I noticed i cannot access via my computer. Therefore I can't transfer media to the card. (I am using a card reader but my W7 only sees the 1st partition. Any way to access this so I can transfer media. And also my computer refuses to recognize my NC. I tried updating drivers but nothing works.

Thanks.
[Nook Color Android Development] satawat.thongsawat:
Yes, I have this very same problem, Nook cannot see the 4th partition, and Windows doesn't recognize it, no way to media to it and use it.:mad:
[Nook Color Android Development] Homer_S_xda:
Several choices for Windows:

1) Linux Live CD or dual boot such as Ubuntu.

2) Nook Color UMS, search the forum for it. It lets you set the two mount points on the Nook to whatever you want. Windows will then see them when you connect to USB.

3) ADB, search the forum.

I use a mix of all three, but primarily #2.

When you say the Nook won't see it, I assume you mean when booted from EMMC? This will require some editing of the vold.something or other on the EMMC system partition. Do some searching to see if anyone has clear instructions that are "modern" and work. By modern, I mean post Verygreen image.

If you find it, please post a link as I would like to do the same.

Homer
[Nook Color Android Development] DizzyDen:
This issue has already been addressed in the thread... it is a Windows limitation only utilizing the first *ACTIVE partition on a drive. A work around is to use a partition manager... (windows drive manager may even work) make the 4th partition the ACTIVE partition and copy the files to it.... YOU MUST MAKE PARTITION 1 ACTIVE AGAIN BEFORE IT WORK IN THE NOOK

Other options are to adb, ftp, web file manager, etc... the files to the SD while it is in your nook. There are free and paid apps in market to facilitate this.
[Nook Color Android Development] prehistorical:
Windows people just need some FREE software - 4th partition

+1

A lot of folks here recommend "Easeus Partition Master Home Edition".

http://www.download.com/easeus-partition-master-home/3000-2248_4-10863346.html

I personally like "Partition Wizard Home Edition".

http://www.download.com/partition-wizard-home-edition/3000-2094_4-10962200.html

Both are free and simple to use (cf. Windows). If the links above don't work, just go to download.com and do a search.

Hope this helps!
[Nook Color Android Development] dejavecu:
I just realized something as I am repeating these instructions for a new 16 gb card. I made a mistake and went to format it to redo this. It still only shows the small boot partition, after formatting it. I had a 4 gb card that I was running this on and sold it, after a quick format. Does that 4 gb card still contain my google account information on the partitions hidden from windows so someone can access everything that synced up to the nook despite the quick format?
[Nook Color Android Development] smully1:
Does this provide alternate boot option so you can boot stock nook without removing SD card?
[Nook Color Android Development] verygreen:
not yet.

But once such u-boot is included into CM7 nightlies, you'll get the ability.
[Nook Color Android Development] smully1:
Is there a good uboot.bin that i can put in place of this one?
[Nook Color Android Development] verygreen:
Check here: http://xdaforums.com/showpost.php?p=14083586&postcount=2486

and read the rest of the thread as there might be an updated version too
[Nook Color Android Development] smully1:
do i need cwm on my sd card? if so, where do I get it?
[Nook Color Android Development] dejavecu:
Is my personal information still accessible on this sd card?
[Nook Color Android Development] verygreen:
no, you don't.
[Nook Color Android Development] pulsorock:
I'm running latest CM7 stable (update-cm-7.0.3-encore-signed.zip) on with the latest installer (1.3) on a SanDisk 8GB Class 4 MicroSD. Is running pretty smooth, I'm liking it a lot.

I would like to try a OC Kernel to see how it goes, but I'm not sure what to do. I've seen posts mentioning dalingrin's kernel, but not sure which one to choose.

update-CM7-dalingrin-OC-sd-052311.zip

update-cm7-dalingrin-2.6.32-sdcard-051311.zip

or any other?

after choosing the right one, I just need to drop it to the boot partition and boot the Nook and it should install it, just like it installed the CM7, right?

thanks!
[Nook Color Android Development] verygreen:
For 7.0.3 you need to stick with 2.6.29 kernels, so the ones with 2.6.32 in the name don't work for you.
[Nook Color Android Development] pulsorock:
Thanks... I'll wait a while and when a new stable release of CM7 that supports it, I'll give it a try.

Or do you know if the latest nightly builds are stable enough? What is the process of upgrading from 7.0.3? Just dropping the .zip file to boot partition in the SD and load it to the Nook, like a normal install?
[Nook Color Android Development] verygreen:
I only tried -87 and have not seen any problems. I don't do too much with it, though.

Yes, just drop the update to the root of the 1st partition and then boot into recovery.
[Nook Color Android Development] :
042411 kernel worked pretty well for me when I was on 7.0.3. Phiremod 6.3 is based on 7.0.3 stable and I think that stock kernel for it. Allows overclocks up to 1.3Ghz.
[Nook Color Android Development] pulsorock:
When you say "boot into recovery", you mean by turning it on after inserting the SD card or the n+power key combo?

Because I can't never do the key combo, it never works for me. The stable install I did drop the update-cm-7.0.3-encore-signed.zip and gapps-gb-20110307-signed.zip and turned it on, and the loader picked them up without any problems. I did see other people having the same problem going to recovery as me on other forum, but still no answer there to our issue.

Thanks
[Nook Color Android Development] verygreen:
yes, the n+power

Read the first post for updated instructions. With the changed uboot in 1.2+ version I think I made it much easier to reproduce.

Alternatively when you do "reboot" in CM7 you can choose "recovery" as the target and then you don't need to nail the key pressing timing, it'd just boot there all by itself.

The "drop update zip on the root of 1st partition" only works when you install for the first time.
[Nook Color Android Development] seth.i.simmons:
Edit: I had broken something in the process if slimming down the rom, that didn't have any impact on my installations that already have gapps. Once I just flashed the stock N87, it worked fine. Can't wait to try out USB host once my adapter gets in!
[Nook Color Android Development] pulsorock:
I tried the "recovery" option from the power menu's reboot option and it just reboots normally, not to recovery. I tried several ways to boot to recovery after installing CM7, and noting happened. That's when I found that thread on Android Central of some users having the same issue.
[Nook Color Android Development] :
I can't remember where I read this but IIRC this feature is not currently functional.
[Nook Color Android Development] pulsorock:
I made a video of what happens when I try to reboot into recovery from power menu:

http://www.youtube.com/watch?v=hJHyonxQzwA
[Nook Color Android Development] verygreen:
It is functional. It works for me and for others.
[Nook Color Android Development] verygreen:
Do you run u-boot derived from installer v1.2 or v1.2.1?

(i.e. what was your original install image?)

If your original install image was 1.3 and you used .29 based CM7, then the u-boot in v1.3 is not a general purpose one and is only suitable for initial install.

Pick a u-boot.bin from a recent nightly or from v1.2.1 update zip file, put it on your first partition and the functionality will be back.
[Nook Color Android Development] pulsorock:
Thanks!

My original install image was 1.3 and I used the stable build of CM7 (yes, I believe is kernel .29).

I think I now understand my problem. Install image 1.3 is for the latest nightly builds and for the stable version I need install image prior than that (1.2.1).

I think I'll give it a try again from scratch tomorrow, this time using the latest nightly-87 and install image 1.3.

That should be correct, right?

Or should I use better install image 1.2.1 (instead of 1.3) with the latest nightly-87 build?

Edit:

Maybe instead of doing everything from scratch once again, maybe I could just do as you mentioned, copy u-boot.bin from the nightly-87, and drop it in the first boot partition. Then copy the latest nightly build to that partition and then boot to recovery mode and upgrade to the nightly-87 build. Then I could try the OC kernel later.

That should work too? would that be a correct way to do it?

thanks
[Nook Color Android Development] pulsorock:
I was able to install a nightly 87 build successfully from scratch, now the recovery mode works. I also installed Dalingrin's OC kernel (update-CM7-dalingrin-OC-sd-052311.zip).

However in the Cyanogenmod settings, under CPU governor, I can only see two: conservative and performance. Is that ok, or there should be more options there? Which one should I choose?
[Nook Color Android Development] lightbike:
@pulsorock Thanks for posting your issue as I was also spending hours trying to get into recovery only to find out that the 1.3 image doesn't play nice with CM7 stable 7.0.3

It might be helpful to mention in the OP that the later version Nightly is best to use with this image.

My quick newb question: I'm going to start from scratch. Is it cool to just re-write the image to my SD card? or will I need a special utility to re-format the card first. Windows doesn't recognize the full capacity of the card anymore.
[Nook Color Android Development] verygreen:
It's in there.

Twice.

Just rewrite the image and you are fine.
[Nook Color Android Development] pulsorock:
I used a program called: SDFormatter for formatting my entire SD to its full size.

http://www.sdcard.org/consumers/formatter_3/

it worked great...
[Nook Color Android Development] pulsorock:
Yes, I saw it just after you replied my post yesterday... :o
[Nook Color Android Development] gordesky1:
I just got my nook today and so far liking it, I install this on my SD card and every thing went great so I wanted too try Daigrins of kernel too see if 1.1 or 1.2 ghz is stable . so I put the zip file on the root of the SD card, than told it too boot in recovery which it did and installed the zip, but after the cm7 boot screen it goes on a lighted blank black screen and just stays there, any idea why?

I'm back on this stock Tom now but would love too get more overclocking options than 925.
[Nook Color Android Development] glitch2500:
Unable to mount /system r/w - weird problems

I apologize if I missed this somewhere, but I did dig around and didn't this specifically addressed.

I built an SD card per post #1 with the 1.3 installer and CM7 nightly build 87, and everything seems to work ok in general. However, for some reason, I can't use various root exploring apps to mount /system as r/w. I get the superuser request, and I choose allow, but all of the ones I've tried either fail or say they did it, but don't really do it. I've tried ES Explorer and File Expert. I've also tried "forgetting" the superuser request for the apps and letting it re-request, and no change.

One way I figured out how to mount the system r/w is to use the terminal app to do a remount of the partition via mount -o rw,remount etc etc., which I verified works except for one thing... even r/w, the files still have r/o permissions, and I have to do a chmod by hand per file to get them writable.

My whole point in doing this was to change my build.prop to fix the chipmunk Netflix issue, and I can do it the long way, but it seems like something is wrong somewhere that, firstly, I can't use normal root explorer apps to mount r/w, and secondly even after finding a way to remount the partition, I still have to update the permissions on the files before I can write them.

What am I missing?

Thanks