yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] jtbnet:
You should be able to just drop the latest nitely on partition and 1 and you SD/Alt to boot Verygreen's install/updater... If you have a working older version then the only thing that changed was I expanded the The first boot partition

to allow 120MB+ free as with a nitely/stable releases were getting very close to the Ninety MB free on the older versions... any of the other changes you obviously worked around already to get you prior version running...

Even with the older version you can free up ~10MB more by removing the saved copy files, Any files with a dash in the name... I had them there so folks could easily distinquish which files were which after they had been renamed to their appropriate uImage, uRecImg, uAltImg... names...
[Nook Color Android Development] jtbnet:
I use Easeus Partition Master on Windows to copy and resize partitions from one card to another same or larger all the time... the trick to remember is it will easily resize and copy to the Last Partition on a new card so you have to think about what you want to resize if it's not just a straight copy... thus to resize the 1st partition I have to start with a freshly formatted sdcard copy resize each partition individually, vs simple copy disk...
[Nook Color Android Development] s52m3:
Just wanted to say thank you, I am using your method to dual book the latest CM7 on a Kingston 4GB Class 6 and it's very nice.

My understanding is that when the next stable comes out, I would be able to drop it to the boot partition and restart right? Does this erase anything I already have, applications etc? Also I did not install dal's latest OC kernel. If I decide to do so, could I simply drop it in the boot as well?
[Nook Color Android Development] jtbnet:
I'm glad you found it useful... For CM7 updates you just copy file to the 1st /boot partition and boot with SD/Alternate again to have Verygreens installer seemlessly upgrade your version while maintaining all your hard work :)... Dal's kernel zips seem to choke VG's install lately but they upgrade fine by copy the kernel zip to the 4th /sdcard partition and booting SD/Recovery and using CWR to install zip from sdcard...
[Nook Color Android Development] s52m3:
When you say boot with SD/Alternate, that does mean that I have to press a button to get into that boot menu app right? Because right now I already have it on SD/Alternate as per your instructions, I just never get into that boot selection menu anymore.
[Nook Color Android Development] jtbnet:
Yes, by default without pressing any key when the query for 'Press Any key to Enter Boot Menu' comes up you will by default boot to SD/Normal... So to Upgrade you do need to 'Press Any key...' and choose SD/Alternate to select Verygreen's Install/Upgrader to run using the Nitely or Stable CM7 version you placed on the /boot partition....
[Nook Color Android Development] srinivas29:
Installing CM7 variants.

Firstly I would like to say Thank you very much. I now have rooted 1.1 on emmc and Cm7 stable version installed on the SD card.

I would like to find out if can install phiremod 6.1 using your method. What are the additional steps to be followed to install this into the sd card?

I tried the following after installing the CM7 on my SD card.

1) I placed phiremod 6.1 on the first partition of SD card.

2) Booted into the clockwork recovery using boot loader.

3) installed phiremod 6.1 using the options avaliable.

This corrupted my emmc parition and 1.1 was not booting. Am I doing something wrong here?
[Nook Color Android Development] jtbnet:
You should be able to Install phiremore the same as CM7 nitely, as it is just a themed/modded version of CM7, using Verygreen's SD/Alternate Install/Updater which does the appropriate eMMC->SDcard conversion on the Fly... CWM Recovery doesn't do any conversions thus would install the package to eMMC as that's what the package was originally built to run on.
[Nook Color Android Development] Shortyred:
I'm having a little problem. My boot disk is a 4gig card the boot partition is:

Boot = 117.63

2nd = 462.81

3rd = 964.84

4th = 2.18gb

Problem is I have 89.11 meg free on the boot partition and the cm7 7.02 update zip is 94 mb's what do I do for this to update?
[Nook Color Android Development] jtbnet:
Yes, that's why I resized the template to allow 120MB free for /boot in v6... you can pick up 10MB in the old /boot partition by deleting the saved versions of originial files, all the files with a '-'/dash in their names except for u-boot.bin, as these are just a saved copy of the original -verygreen, -cwr, -sdcard files that were moved around to become the SD/normal,recovery,alternate boot choices...
[Nook Color Android Development] Shortyred:
Thanks for the quick reply. Where can I get the v6 zip? Did I miss it in the post? By the way this boot is a life saver!! Thanks so much for it!!
[Nook Color Android Development] jtbnet:
v6 is available from the links in the OP... though I received a message from dropbox this morning that my public dropbox access was suspended until tuesday due to more than 10GB/day activity on the free account... but the link to nook.handhelds.ru mirror is working...
[Nook Color Android Development] Shortyred:
I do have v6. Ok are these safe to delete because of the dash?

uRecImg-cwr

uRecImg-verygreen

uRecRam-cwr3006sdcard

uRecRam-cwr3010sdcard

uRecRam-verygreen
[Nook Color Android Development] Shortyred:
Umm where is the old /boot partition???
[Nook Color Android Development] jtbnet:
Yes... they are they only in case you want to reconfigure Which is Which boot selection... But the 10MB they free by delete allows for installing the current over 90MB updates...
[Nook Color Android Development] jtbnet:
The OLD /boot partition is the 117MB one this all started with... I increased this to ~150MB to have 120MB+ Free space in v6 of the template SDcard...
[Nook Color Android Development] joe2262:
What would happen if u-boot.bin were deleted ?
[Nook Color Android Development] jtbnet:
Sounds like an OPPS :) Seemingly nothing would happen while you are still running... BUT as u-boot.bin is the actual first stage boot loader then if you were to try to power off/on or reload without it you won't boot... I had worried folks might mess up sometimes trying to move their files around to juggle the boot choice options so I posted all the files in a small zip just in case anyone needed to get the originals back;

http://dl.dropbox.com/u/6922721/jtbnet-modified-bootfiles.zip

and luckily as you only need the first partition /boot mounted to fix these you can just plug the sdcard into you PC and copy a missing file back to /boot...
[Nook Color Android Development] HarleyChick:
Just want to make sure.....

Thanks for the great thread and for all of your responses to questions. I have read the entire thread through at least twice. I'm fairly certain I know what to do, but I just want to be sure.

I am currently running Phiremod v6.2 of off the emmc. But I want to play around with various ROM (specifically NookieComb) from the sd card. I downloaded your "v6" and burned it to my sd card, and expanded the 4th partition. I downloaded the sd version of NookieComb and copied it to the "boot" of the sd card.

Now this is where I'm a little unsure. Do I just power off my Nook, insert the sd card, and turn it on and it boots off the sd card into NookieComb, or is there an extra step in there that I'm missing, i.e. do I need to boot into recovery first? And as long as I'm booting off the sd card, anything and everthing I download will stay on the card, correct? I have backups of everthing I am running now so I know I won't lose everything, I just don't want to mess with my emmc if at all possible.

Thanking you in advance for your patience. :)
[Nook Color Android Development] jtbnet:
I'd suggest only using CM7 builds via VG's installer/updater on /boot... other already converted to SDcard roms via CWR 3.0.1.0 by putting files on 4th partition /sdcard and using CWR/Recovery to install...
[Nook Color Android Development] HarleyChick:
Thanks for the response, but I'm not sure I understand. Only CM7 builds should go on the boot, but all other ROM's go on the 4th partition? That's not clear in your instructions at all.

I don't know how to place things in the partitions, so I think I'll just let this one go.
[Nook Color Android Development] jtbnet:
I'm sorry this is confusing, I though these comments in OP#2 would be enough to explain the options of using using VG's installer/updater for CM7 on files in /boot or CWR 3010 for normal recovery install on files in /sdcard, pr at least mention enough of where these vcame from to steer someone to say verygreen's thread?

How verygreen's Installer/updater differs from CWR... With vg's installer you place the installable files on the /boot partition... this installer will install SDcard ready or agnostic installables AND will install eMMC designed version CM7 builds and do on the fly conversion to SDcard version during the install seemlessly...

CWR 3.0.1.0 for SDcard will expect the install zip or backup file to be on the 4th/sdcard partition and expects these to be agnostic installs as it doesn't do anything on the fly to make these run on SDcard... It they are built or modifed to run on SDcard thats fine and installing from this Recovery works as would be expected...
[Nook Color Android Development] angomy:
I'm not sure why but this particular install gave me problems on a 16GB class 4 Sandisk card but not on either one of my 8GB cards (Transcend class 6 and Sandisk class 4). I kept getting numerous FCs and error messages.

It might have something to do with having to manually expand the 4th partition with Easeus versus the other SD install I tried that does it for you during the install process, but I'm not sure (not a dev :x)

Just thought I'd let you know, don't know if anyone else has had the same issue. It's only with the larger capacity card that I've had problems, the 8GB installs have been very smooth with no issues at all.
[Nook Color Android Development] jtbnet:
You are not the only one who had a problem with 16 and above GB cards... I did have a problem with one 16GB I made, but re-made it and it worked... I then tried a 32GB card and that worked... but I'v eheard a few other folks made one that didn't work also so just too bad none of seem to have repeatable steps that fail then we could figure out where it goes wrong... One card I saw the layout for had a FAT vs. FAT32 FS for fourth partition but that makes sense it wouldn't extend but thus v6 has FAT32 so should extend fine for card you can purchase today...
[Nook Color Android Development] fuzzynco:
[Q] TJBNET modified bootfiles zip

Which files would I need to move to /boot (SD card p1) to

get a CWR that understands the SD card partitioning for

Nookie Froyo?

u-boot.bin-sd-card > /boot/u-boot.bin

uRecImg-cwr > /boot/uRecImg

uRecRam-cwr3010-sdcard > /boot/uRecRam

Will that uBoot do standard boot (SD) and

hold power/home keys for recovery (SD)

from the boot device?

My hope is to be able to use nandroid backup and

flashable's from /sdcard/ (p4). /boot (p1) is small

and having to copy to it to install is an issue.

I already have a CWR 3.0.2.8 bootable SD that I use

to maintain the eMMC partitions.

I wondered if CWR is aware where it booted from

(as a way to where to do its work with, eMMC

or SD)? That is, is there a way to make CWR

'know' (or to be told) which file-systems it should

be updating / backing up / restoring? As I understand

it now, we need a different uRecImg/uRecRam for each

target (eMMC/SD).

Will there be a 3.0.2.8 for SD card available?

thanks
[Nook Color Android Development] rhester72:
jtbnet,

You've probably read about the troubles getting the B&N 1.2.0 u-boot.bin to play nice with VG's image - and unfortunately that particular u-boot (or one based on it) is necessary for video to work properly with the new kernel betas.

Is it safe to assume that the custom u-boot.bin you use for multiboot is also based (originally) on B&N's 1.1.0 and will have the same problem, and that it can't simply be replaced by the stock B&N 1.2.0 version without breaking everything?

Any suggestions welcomed!

Rodney
[Nook Color Android Development] TDO:
boot partition contains

u-boot.bin

u-boot.bin-multi-v0.4

u-boot.bin-sdcard

u-boot.bin and u-boot.bin-multi-v0.4 are ident.

rookie1 has made an updated multi-boot bases an u-boot 1.2 http://xdaforums.com/showthread.php?t=947698

Can this be used with this image and which files have to be replaced?
[Nook Color Android Development] jtbnet:
Yes you have the correct files list... and yes on the pwr+home keys for rcovery boot and I have successffuly made backups though I usually find it easiest to just save the entire image off for a backup using W32DiskImager.

CWR uses the recovery.fstab file to understand the partition layout and FS types so this file in the uRecRam is what needs to be modified to use CWR on Sdcard... I just haven't seen a need yet to do the the same thing for 3.0.2.8
[Nook Color Android Development] jtbnet:
There are 2 uboot.bin files on the card so folks could swap if desired. uboot.bin-sdcard is the original B&N 1.x one and u-boot.bin-multi-v0.4 is j4mm3r's multi-uboot for v1.x ... I haven't yet tried to do anything with newest beta's due to being buried at work but probably will find time soon and then maybe it will justify putting out a v7 with additional uboot and CWR options in place.
[Nook Color Android Development] jtbnet:
Yes, I left 2 flavors of uboot.bin on the v6 boot partition, both the B&N 1.x uboot which worked to boot Recovery with PWR+Home presses and j4mm3r's Menu based v 1.x multi-boot uboot.bin which is copied to be the default used. I haven't had the time this week to try and newer 1.2ish builds but probably will soon so will look around for 1.2 compatible uboots to include on a v7 image when I can find time... but it sure look like all you should need to do would be to copy rookie1's multi boot over to an exisiting /boot partition and try it out...
[Nook Color Android Development] fuzzynco:
Will W32DiskImager see the whole SD (I thought it manipulated drive letters?)?

I'd been booting a linux to use DD on the /dev/sd? to get the whole disk?

When I have the SD card (p1) mounted in linux, can I loop mount the uRecRam

file and fix its file to agree with SD card's files systems and layout with an editor

like nano?
[Nook Color Android Development] jtbnet:
It's the Easeus Partition Master for maniplulating logical Drives and FSs, while W32DiskImager works down at the raw device/physical level so yes it equates with dd on linux only in it's rawest form...
[Nook Color Android Development] fuzzynco:
I always used gparted for partitioning, figuring Android is a Linux

so a Linux tool would work. So I can use W32DiskImager to img

the whole SD card for a backup?
[Nook Color Android Development] jtbnet:
Yes... That's how I keep live configured snapshots in case I mess up :)
[Nook Color Android Development] TDO:
Can you give me a hint how to update the u-boots to 1.2?

All the necessary new files are here -

a 1.2 mod of j4mm3r's u-boot with menu

a 1.2 version of verygreens installer

...

Your Boot Partition contains:

u-boot.bin

u-boot.bin-multi-v0.4

u-boot.bin-sdcard

So which should go where and should anything else be modified?
[Nook Color Android Development] TDO:
I got it to work, but still have a lot of questions.

Why is there a uRecRam-cwr3006 which is identical to uRecRam-3010sdcard?

Why any of them as CWR 3.0.10 is includes as uRecImg and uRecRam?

Why exists uRecImg-verygreen and uRecRam-verygreen? They are already included as uAltImg and uAltRam.

The same goes for uImage und uRamdisk and their counterpart with *-m7-rc4.
[Nook Color Android Development] jtbnet:
Yes, there are duplicate copies of the normal named files with the extended named files showing what version they came from just to make it easier to swap files around... This is about due an update to .v7 once the newest fattire 1.2 menu u-boot-bin settles down, but the 1.1 .v6 still is working just fine for me with the .32 image and kernel for verygreen converted installs so I'm takeing the time to let things settle before doing a .v7 with 1.2 updated mlo and menu u-boot.bin and 1.2.1 verygreen installer/updater.
[Nook Color Android Development] TDO:
Thanks for the clarification - it really confused me.

If anybody else wants to run the new nightly (.32) without video/wifi, ... problems you have to do the following.

Replace the MLO with the 1.2er MLO.

Replace u-boot.bin with the new Multiboot http://xdaforums.com/showpost.php?p=14084162&postcount=64

Get verygreen's 1.2.1 installer and replace uAltImg/Ram.

However there is a drawback - the included CWM is not working and I have not found any working replacement yet.
[Nook Color Android Development] smully1:
This worked awesome. Thanks!!:)
[Nook Color Android Development] TDO:
If you want to switch to kernel .32 just grab this package and replace your files on the boot partition.

http://www.megaupload.com/?d=JM092G4G

You will get:

MLO from 1.2

u-boot.bin cyan edition from fattire (multiboot based on 1.2)

verygreen's updater V1.2.1 as alternate boot option

CWM 3.0.2.8 modified by me for SD as recovery boot option

If you want to upgrade an existing SD card without installing a new Android build don't override uImage and uRamdisk!
[Nook Color Android Development] pryonix:
hi tdo, will this allow me to put unmodified CM7 nightlies on to the sd card and boot as sd alternate to install them AND have the option to us CWM to install the nightlies instead?
[Nook Color Android Development] jtbnet:
THANX! You did the one original piece I didn't have time for... the updated CWR 3.2.0.8 cleanup version to give both relevant EXT# FS versions... I haven't the time to test fully but will update the OP tomorrow with a pointer to your update once a couple folks confirm their success with the CWR update... THANX AGAIN...
[Nook Color Android Development] pryonix:
Feedback so far on TDO's update:

What I did ---

I already had a verygreen's sd installer

1. I used jtbnet's bootfiles only to copy over vg's /boot files

2. I used TDO's modified bootfiles to copy over jtb's boot files

3. Alt booted. Recovery booted. Normal wouldnt boot. After the boot logo, I would just get a blank screen (not sure why... it seemed like the boot couldnt find where my CM7 OS was)

4. Deleted the extra u-files from JTB/TDO boot files to clear up space for CM87N

5. Reinstalled 87n from alternate

6. Done.

THANK YOU! :)

-------------

EDIT: I have a BIG problem. I cannot mount /system. I tried su-ing but I keep getting the error mount: not found :(

EDIT2: I was able to get mount to work but only by typing "busybox mount" and then it would keep giving me an /etc/fstab not found error.
[Nook Color Android Development] TDO:
Replacing an existing install will not work.

It's for the image, to start fresh over.

It includes jtbnets uImage and uRamdisk. The get overriden with installing CM7.

So if you want to update your existing installation you must not override this two files.

But I don't know if it is a good idea to run .29er kernel with the new u-boot and MLO.

It also relies on the partitioning of this image. Actually I only took the recovery.fstab from the modified CWM 3.0.1.0 an replaced the one on the CWM 3.0.2.8.

So you need the following layout on your sdcard.

1 /boot FAT32

2 /system EXT3

3 /data EXT3

4 /sdcard FAT32

Maybe it would be a goot idea to switch to the 1.2er layout and make /system EXT2.

If any one wants to try it I can provide a CWM with EXT2 for system.

I have not done any excessiv tests of CWM. I only used it to make a backup and reinstall it and installed the overclocking kernel from /sdcard after I installed the new nightly via AltBoot.

@pryonix

Ah you are talking about CM87N. Just checked in CWM and it worked.

Best to get over to the CM7 thread and ask how the .32er kernel now handels mounting.
[Nook Color Android Development] pryonix:
Apparently it wasn't a problem with the mounting. The google backup cloud services "restored" my apps on my first boot after flashing 87N and the "restored" apps couldn't find the system folder properly.

I solved it by uninstalling and reinstalling from the market.
[Nook Color Android Development] TDO:
Yes with verygreens installer you can use unmodified builds (it ist doing this on the fly) - you can find more infos in verygreens thread.

CWM does not alter install scripts. You need the proper version if you use CWM.

It has been explained in this thread.

I only updated the used components so you can use .32 kernels without a problem.
[Nook Color Android Development] pryonix:
Yup thanks. It was the uRamdisk and the uImage that came with the zip that really did me in the first few tries but I'm running the latest nightly now and i love how jtbnet placed cwm on recovery and vg's installer on alt. very useful.

thanks again
[Nook Color Android Development] fuzzynco:
Is this setup compatable with CM7 stable?

The latest packaging with B&N 1.2 boot loader and cyan boot menu?

I was concerned about /system & /data ext3 vs ext4 setup?

I wondered if I could use the distributed support utilities

and install the CM7 stable package to be at that release?
[Nook Color Android Development] TDO:
They are only there to get overriden by installing your OS and are never used.

I haven't tried it, but I think they aren't needed at all.

Maybe jtbnet, who put this image together, has more experience with this.
[Nook Color Android Development] jtbnet:
They really aren't important but were good enough to boot versions that were current at the time...
[Nook Color Android Development] TDO:
Here is an updated version.

http://www.megaupload.com/?d=C2U0AVHZ

verygreen's updater V1.3 as alternate boot option

I also removed uImage und uRamdisk - so you cannot harm your existing installation.
[Nook Color Android Development] pryonix:
this is so awesome TDO. thanks so much. now i'm gonna be more late for the meeting i have to go to in a few mins hahaha

edit: nvm ill try it later. megaupload keeps giving me an error :| hehe
[Nook Color Android Development] smully1:
How does this work? It doesn't appear to work with win image?
[Nook Color Android Development] peaceridge:
file won't unzip

I'm so sorry to be such a noob - but after I download verygreen's mirror, it won't unzip - it says the file is either of unknown format or damaged. I've downloaded it 3 times and still gets that message. I can't use the dropbox copy as it says you are overextended and so it is unavailable. I've searched via google and can't find another dl site. Am I doing something wrong?

Well, evidently 4th time is a charm - it now works!
[Nook Color Android Development] rabi347:
I did all the process, when the nook reboots, it says "booting, please wait" and nothing happens.

Could someone please HELP!!!!
[Nook Color Android Development] thunder2132:
I have the same problem with nightly 146 and a blue-dot nook color.
[Nook Color Android Development] thunder2132:
Just to clarify, my specific issue is "Booting Selected Option, please wait...." and it'll freeze there. I am running a brand new "blue-dot" nook with a class 4 microSD from my Evo. It is formatted and I have tried both resizing the sdcard partition and leaving it at default. My nook is unrooted.
[Nook Color Android Development] TDO:
Just to be sure.

You have selected alternate boot and verygreens installing script is not loading?
[Nook Color Android Development] bhrich902:
Ok, so i've read the last 2 pages of this post and wanted to make sure i got this right before i alter my existing sd setup. I'm running off verygreen's 1.3 sd card installer with nightly 144 setup and running and all i want is to be able to boot to cwr without damaging my setup.

So, do i take the jtbnet-modified-bootfiles.zip contents and copy them to the /boot partition and then copy the last posted MultibootSD.zip contents and copy over on the /boot partition too?. Thanks in advance.
[Nook Color Android Development] TDO:
if your sd card has the following layout.

1 /boot FAT32

2 /system EXT3

3 /data EXT3

4 /sdcard FAT32

you only need to put the files from http://xdaforums.com/showpost.php?p=14241487&postcount=141 to your boot partition.