yashsingh1/xdaforums huggingface dataset:
[Thunderbolt General] rednoved:
That sucks considering the mic setup on the TB isn't too shabby. Maybe it can be fixed in a firmware update?
[Thunderbolt General] djcyph:
i dunno because from doing many searches, it seems like this happens on a lot of other devices for a long time now..

is this something a custom ROM could fix?
[Thunderbolt General] vitsdroid:
just ordered it, hope it works.
[G Tablet General] Sthur:
I have TNT Lite 4.2.4 installed on my Gtab, but probably did it the wrong way and it works.

Questions is if I install the 4.2.5 update does it whip anything? applications installed? Sorry for the newbie question.

Thanks so much for the great ROM Roebeet.
[G Tablet General] roebeet:
4.2.5 replaces the other 4.2.x supplements and should work A-OK. But, as always, doing a backup first is always a good idea.
[Touch Pro2, Tilt 2 Windows Mobile General] debulus:
touch pro tilt 2 ;) please write me...
[Nook Color Android Development] faceman66:
Nicely done... do you plan to update your flashable for each nightly?
[Nook Color Android Development] racks11479:
I might get a day or two behind if I'm busy, but yes those are my intentions. :)
[Nook Color Android Development] jtbnet:
Cool! Trying Now... Just need to ask... Was I on the right track as I asked in the CWR 3.0.1.0 thread earlier today?

http://xdaforums.com/showpost.php?p=12155685&postcount=299
[Nook Color Android Development] plariers:
Hey guys.

I prepared my CM7 SDcard [step one] via burning the .img to my SD via dd. Then, step 3 involves burning another .img to my card. Won't the two .imgs overwrite each other if I use dd?

Can I get a little more detail in these sections? Everything else makes perfect sense. Cheers.
[Nook Color Android Development] DizzyDen:
You're going to be using 2 different SD's.... one that has the original CM7 SD card version from verygreen... the other is for CWM....

Set the CM7 card to the side... burn a CWM SD... this is the one you will boot CWM from... is all it is used for.

Copy the update CM7 zip file to the root of the CM7 SD card to use for upgrading the same card.

Hopefully this cleared it up for you.
[Nook Color Android Development] plariers:
Perfect. Thanks for the explanation.
[Nook Color Android Development] racks11479:
Bump...

OP updated with latest nightly, gapps, and dalingrins OC kernel.

Please let me know how it works out for everyone. If there are any issues or what not so that I may make any needed corrections.

Thanks again everyone,

Racks
[Nook Color Android Development] ScratchSF:
Thanks for pulling this together. I was able to update my SDcard pretty easily. Although, I ran across two issues that I had to address that I thought I'd share:

1. I couldn't copy the file to my SDcard from my computer because the Boot partition (1) was only 117MB in size with about 1/2 of it used. Since the .zip file was 81MB, there wasn't enough room. My solution was to download the file directly into the Nook using the browser, following by using File Manager to copy it to the topmost location (or /sdcard). Although, when I went into CWM, I think I could have left it in the download directory rather than move it.

2. I previously edited my vold.fstab file in order for it to point to my fourth partition, which is about 2GB in size, rather than to my boot partition (1), which is only 117MB. I adb pushed it from my computer and all was fine. I may keep a copy of this file on my sdcard so that I can just replace it using file manager going forward. That way I can do the entire process without the need to connect to a computer.

Hope this is helpful.
[Nook Color Android Development] racks11479:
Glad you got it working. But doesn't the sdcard partition mount when you plug the sdcard into your pc using a micro sdcard reader? That's how i did mine. boot and sd should mount since they are vfat partitions. You shouldn't be copying to the boot partition because when using the Modded CWM from this thread and when mounting sdcard. It mounts the sdcard partition from your CM7 Sd. Which is where the CM7 zip should preside.

I do appreciate the feedback though.

Thanks,

Racks
[Nook Color Android Development] jtbnet:
I was planning to redo this just a bit to be able to put you uImage -> uRecImg and uRamdisk -> uRecRam on my normal CM7 SDcard to be able to get down to a single card with merged boot partition but figured that I would just verify what I thought you did to get CWR to install to the SDcard (/dev/block/mmcblk1p?) vs. EMMC (/dev/block/mmcblk0p?) and I'm thinking you missed an edit on the cache partition as I don't think you want to use the EMMC cache for the SDcard?

CWR 3.0.1.0 EMMC uRecRam: /etc/recovery.fstab

# mount point fstype device [device2] [fstype2]

/boot vfat /dev/block/mmcblk0p1

/system ext4 /dev/block/mmcblk0p5 NULL ext3

/data ext4 /dev/block/mmcblk0p6 NULL ext3

/cache ext4 /dev/block/mmcblk0p7 NULL ext3

/emmc vfat /dev/block/mmcblk0p8

/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

/sd-ext ext4 /dev/block/mmcblk1p2 NULL ext3

CWR 3.0.0.6 SDCard uRamdisk: /etc/recovery.fstab

# mount point fstype device

/boot vfat /dev/block/mmcblk1p1

/system ext4 /dev/block/mmcblk1p2

/data ext4 /dev/block/mmcblk1p3

/cache ext4 /dev/block/mmcblk0p7

^ ^^^^^

/emmc vfat /dev/block/mmcblk1p4

/sdcard vfat /dev/block/mmcblk1p4 /dev/block/mmcblk1

Edit: Thinking some more about this I guess it's pretty meaningless as I beleive the only thing CWR will do with /cache is flushing cache... so probably no big deal to flush EMMC cache except first boot takes longer...
[Nook Color Android Development] racks11479:
Yes you are correct regarding the cache. I left it as is , without creating tmp cache partition. I'll update when I get a chance next time around.

Thanks for the feedback,

Racks
[Nook Color Android Development] 12paq:
Hey! Thanks for this. This is going to save me a lot of time, but I was enjoying the research. lol

Two questions, If I have modified my 4th partition (sdcard) of my bootable CM-7 SD and modified the vold files accordingly, to utilize the existing space on my SD card, would this have any impact on running any of your procedures in the op? Would I loose my partition at any time during the process?
[Nook Color Android Development] TchnclFl:
Perhaps a dumb question:

If I use this method with CM7 nightly 25 on an SD card running nightly 19, will I lose my applications and data? Or just OC kernel?
[Nook Color Android Development] racks11479:
No it should'nt. You might have to redo your vold file, but your 4th partition should stay intact.
[Nook Color Android Development] racks11479:
Not a dumb question at all. I should mention this in my OP actually. It will not touch your data partition. So all your apps and setup should remain. Your Google apps should remain as well. Only /system files are updated. OC kernel will be replaced, that's why I included the flashable OC zip as well in the OP. Use the zip and flash with my modded CWM and it will update your kernel.

-Racks
[Nook Color Android Development] ADude:
No.

It only shows the first partition, regardless of what the file systems are.

However, one can do the same thing by using ADB to push the zip file to the /sdcard/ folder.
[Nook Color Android Development] TchnclFl:
Thanks! Haha I was unsure if you hadn't mentioned it because it was obvious, or because you hadn't thought of it :D. I'm pretty fresh to the Android scene, especially bootable uSD cards.
[Nook Color Android Development] racks11479:
OK. Thanks for the update. I run windows 7,Ubuntu, and OSX and boot and SD mount for me. Anyone else with only boot mounting? Is it just me?

Thanks,

Racks
[Nook Color Android Development] 12paq:
Drat. Nope, CWM SD will not allow me to mount my extended sdcard 4th partition.

Easy enough though, to start over. I have a current sd version I pulled and saved to my PC prior to extending my partition. So no biggie. But as a way to easily do nightlys, not so easy.

If indeed the SDcard partition is the issue, it would be nice if it was not limited to the 2gig image. The 2gig, as you know, is really intended as a Bluetooth test, not practical as a daily runner for me due to storage size limitations. In addition, Verigreen stated he might this weekend, write CM7 SD versions that will just fill the remaining space of a given sd card with the 4th SDcard partition.

I'll look for a work around and report back with any success. I wonder if will not mount because of the 4th part ion size or the High Capacity micro-SD card? Mine is a Sandisk 8gig.

Wonder how hard it would be to modify your CWM sd for variably sized SDcard partitions?
[Nook Color Android Development] racks11479:
Bump...

Sorry for the delay in posting updates.

-Uploaded latest CM7 v41 Nightly

-Latest OC kernel test build by Dalingrin 041811C

-Latest Phiremod Nook v6.1 (This will formate /system only, data stays intact)

-Alsa update for smoother video playback (only flash this for Phiremod and CM7 v39 or earlier, Alsa update has been merged from Nightly 40 and on)

Thanks,

Racks
[Nook Color Android Development] Hextall:
Based on the order in your OP, I assume CM7.0 needs the Alsa update (as it's before nightly 39). I can't remember when 7.0 was released relative to 39.
[Nook Color Android Development] racks11479:
Yes you are correct. It was CM7.0 Then nightly 39 and so on.
[Nook Color Android Development] dexx0008:
giving nightly 41 a try. picked up a wii controller for bt retro gaming...

oops thanked wrong post,, meh, deserve 2 thanks for keeping these updated for sd card. I'd be interested in knowing details on how you alter the nightly's for sd card use in case you get too busy and stop posting. If you don't mind sharing some instructions could you pm me?

pm replied.

uh oh,I think the last nightly 41 you put up was not quite right. it flashed my internal. Might need a little help getting back to stock. yep it did,

sd card shows:

boot

disk2s2

disk2s3

CM7 SDCARD,,,, this parition contains just the zip (cm7_SD_eccore_41.zip)

normally cm7 has my android installation.

boot partition on sd card contains: uRamdisk, u-boot.bin, uImage, MLO

hooking up nook now to see what i've got on internal. (it won't mount) just loops the cyanogen mod7 boot animation. --> i'm going to hit the returning to stock thread for some ideas.
[Nook Color Android Development] racks11479:
You are correct. If you downloaded nightly 41, please do not flash if you haven't yet. Script error. Reuploading correct version now. Sorry for the mess up.
[Nook Color Android Development] dexx0008:
To recover if you did flash 41 to internal due to script error. (I'm back)

Recovery Steps

1. grab 1.0.1 or 1.0.0 from method 1. I chose 1.0.1 (what my nook came with.)

http://xdaforums.com/showthread.php?t=914690

2. put it on the cm7 SD card partition on (4th partition) of one of your prepped cm7 cards.

3. boot to clockworkmod recovery. (i used Racks' cwr image like i always do)

4. mount and format /system

5. mount and format /data

note: I neglected to do steps 4. and 5. the first time and after flashing 1.0.1 nook would boot to nookcolor stock animation and loop. I thought this would be the issue but turns out it didn't matter. maybe if i formatted /system and /data the first time I could have avoided step 11.

6. swap sd cards and put in the cm7 card with 1.0.1 on 4th partition

7. mount sd card

8. choose install zip, choose zip file,,, select the restore file and then nagivate to 'yes'

9. it will restore /system, then boot files. then

10. after it is complete pull sd card and reboot.

11. At this point I'm still stuck in the nook color boot animation... (don't panic)

I then booted into factory rest,,, powerbutton ond holding n home button. It asked me if i wanted to do a factory reset. I said yes, when it was finished it booted into setup of the nook again. registered my device, and it downloaded my books.

-----

end steps

Also: I had copied down my model number/mac address and serial# a few days ago. It reports the same so everything should be fine.
[Nook Color Android Development] racks11479:
Corrected Nightly 41 updated in OP..

Thanks,

Racks
[Nook Color Android Development] :
For some reason the updated kernel wouldn't post for me.... kept hanging. I went back to 4/4 and it worked fine. Oh I flashed to the latest cyanogen and it worked fine.
[Nook Color Android Development] ADude:
I do not support porting these test kernels to SD card, or any other mirroring.

The general principle behind them is "Hey, I just had this idea, can someone test it ?" and there is a new one every few hours.

People should use the CM7 included kernel, or else use 3/31 or 4/4 if they want an OC kernel.
[Nook Color Android Development] racks11479:
Ummmm, why not? It's stated in my OP as "Test Build". I'm running it and it works fine for me, so why not go ahead and test it. Some might find it useful, some might not. Isn't the whole point of all this is to test and experiment so that we can further development?

I totally understand that the test builds were geared towards EMMC, but I enjoy pushing the limit of what my nook can do. :D
[Nook Color Android Development] Hextall:
I'm not a religious installer of every new custom kernal, but I appreciate you (racks) providing them for us CM7 sdcard users. I'd rather be given the choice to play around with them or not.

Plus, it appears you enjoy doing this stuff, so I want you to know that at least I appreciate it.
[Nook Color Android Development] dexx0008:
Are you referring to all the kernels/roms Racks provides or just the overclock ones??

I like having access to nightly builds that run off the sd card. I'm not yet comfortable building my own for sd card and the OP clearly states you are doing so at your own risk. I see nothing wrong with it. No one is forcing anyone to use them.

I also prefer keeping my nook stock for access to stock nook reader and i'm ready if/when b&n has a new update. Running of sd card is an excellent way to test multiple roms/builds quickly by popping in a new card.

If you don't like the idea of lots of roms being posted in the forums perhaps having official internal and sd card installs is the solution or sticking a thread with 'official releases' to avoid confusion.

there could even have a set of instructions for users to create their own sd card builds if they so choose to avoid anyone from having to provide sd card options. if people can flash internal and back to stock and recover from mistakes, etc i don't see having sd card installs as an issue, nor providing them for the benefit of others.
[Nook Color Android Development] ADude:
There are people reading the Kernel thread who are testing each build, and comparing the results to the previous ones. Some of the builds have had significant problems (eg 4/12 IIRC). So that is the appropriate place for those test builds. (And, it is also true that SD card users' testing results would not be of value, due to the additional factors.)

Dalingrin is about to move from porting the 29 kernel to porting the 32 kernel, so there should a final OC 29 kernel soon - I would guess by the end of the weekend, if not sooner.

Also, when it is mirrored other than in the Kernel thread, it doesn't have any of the disclaimers, such as that it has 16-bit colors instead of 24-bit colors (because it is faster to do so).

Otherwise, I certainly support the SD card versions (as should be apparent from earlier posts in the thread)_
[Nook Color Android Development] yazyazoo:
Thanks for the link for help. That got my missing partitions back! It lead to the recovery of my nook!
[Nook Color Android Development] racks11479:
Bump...

-Latest CM 7.0.2 Stable Up

-Latest test Kernel by Dalingrin 4/24 (**Please read the kernel thread for more info. Not everyone will be able to run @ 1300. It's been known to lockup on some devices. So use at your own risk**)

Thanks,

Racks
[Nook Color Android Development] dexx0008:
Hey Racks, just a quick question on how to apply the over clock kernal. do i just use cwm and flash that after i've flashed cm 7.0.2 for instance? I'd like to test 1300 to see if my chip can actually run it. Sort of as a test as to the quality of the chip in my nook. I haven't decided if i want to stick with 925 without any extra change in volting or if want to run 1100/1200/1300 on demand.

thanks

ryan
[Nook Color Android Development] racks11479:
Yeah, just flash it with my CWM as it will install some /system files as well.

Good luck!

Racks
[Nook Color Android Development] ADude:
If you try speeds above 1100, do NOT check "set at boot" !!

(otherwise you will have to flash back to stock kernel to escape lockups)
[Nook Color Android Development] racks11479:
Just an FYI. I'm running my duaoboot sdcard with phiremod 6.1 OC'ked to 1300 with set on boot. I say go for it if you're brave enough. Might be one of the lucky ones like myself. And if it does lock up. Just boot into recovery and flash an older kernel. :D

Its part of the fun.
[Nook Color Android Development] PMDColeslaw:
Can you create a SD flashable for Phiremod 6.2? Also I'd like to know what it is you do to make the rom install to the sd rather than to the emmc. If I knew I could try to make the changes myself and not have to pester you :)
[Nook Color Android Development] racks11479:
Man. I forgot that phiremod is updating only his new site now. Ill prep one by tonight. And never a bother. I'll also PM you the steps I go about preppin it for SD install. :)

Thanks,

Racks
[Nook Color Android Development] PMDColeslaw:
I understand! I think now he has said that he'll keep the xda thread up to date again. It can be confusing though, lol. TIA for the PM info as well!
[Nook Color Android Development] TchnclFl:
So I'm finding it hard to get the details: What are these CM7 "Stable" releases? Are the RCs? Why do they release nightlies if these are stable?
[Nook Color Android Development] racks11479:
Bump...

Check OP for updates:

-Latest Phiremod v6.2 Rom Updated (Check Phiremods thread for more info)

-Froyo 0.6.8 BT 3/13 Kernel Updated (Check HTCF4N thread for more info)

Remember, if you like the Roms and find the kernels useful. Please head over to the original dev's thread and say thank you! :D

Thanks,

Racks
[Nook Color Android Development] ChaOConnor:
I'm contemplating putting Stock 1.2 on my emmc, and running Phiremod 6.2 off my uSD. My question to those who have done it, what sort of performance hit do i get when I run off the SD Card? I suspect it would be a longer boot, but once it's loaded, how does it perform?

Thank you!
[Nook Color Android Development] ADude:
Racks -

If you can upload a version of Honeycomb SDK v2 5/5 for your SD card system, that would be great !

( I've been content with just CM7.02 stable on my Emmc, but I would like to try out this new Honeycomb SDK v2 5/5 and running from SD card seems ideal, since it still has a flaw or two. )

Thanks !
[Nook Color Android Development] racks11479:
Funny you should ask! :)

Bump...

-Uploaded latest CM7 Nightly 61

-Uploaded Divine Madcat's Honeycomb RC1v2 (This will format /system and /data)

Thanks,

Racks
[Nook Color Android Development] ADude:
Can you re-check that MD5 on your original ?

I downloaded it twice from two different site options, and the MD5 was the same each time, but different from the MD5 listed.
[Nook Color Android Development] racks11479:
Just checked the MD5 of the .zip on my computer again. It looks correct to me. I'll try downloading when i get home and see if I get a different one as well.
[Nook Color Android Development] ADude:
Actually, it might be a moot point, as in between my first request and your first response, an "RC2" was uploaded to their OP with "fixed market, SU and audio"... they are working fast...
[Nook Color Android Development] racks11479:
No, not a moot point at all. This has fixed market, su and audio. Check OP. I mislabeled it! :D
[Nook Color Android Development] ADude:
From what I can tell reading his thread, Divine Madcat is using the term "V2" to distinguish his new work from the February Honeycomp which is "V1".

Then he is using the term "RC2" to distinguish the version this afternoon that has markets from yesterday's version which was "RC1":
[Nook Color Android Development] ADude:
RC3 is out: :D
[Nook Color Android Development] tsukisan:
Just tried the honeycomb rc2 and it works great, few pauses from time to time, one thing though, when I power the device down and start up again the device pauses at the small blue "android" and wont boot again without really clashing, am I the only one with this problem?
[Nook Color Android Development] racks11479:
What do you mean by that?
[Nook Color Android Development] Arbelzapf:
I can't get this to work. My Nook is stuck at the ANDROID_ screen. Since verygreen's 2gb image ...well...does not fit on a 2gb card, I used the size-agnostic SD installer to get the CM7 card. I transferred your HC rom in CWM using the USB mount option and flashed it. Now it's stuck at the android screen for more than 5 minutes, so I guess something went wrong. Do you have an idea what I can do to make this work?
[Nook Color Android Development] racks11479:
Are you using my Modded CWM or jbtnet's card? You can only flash if the CWM Recovery mounts the correct /system and /data partitions. The normal CWM mounts your internal system. The CWM from this thread will mount your SDcard partitions for install.

Please advise above points.

Thanks,

Racks
[Nook Color Android Development] Arbelzapf:
Yes I used your modded CWM, of course. The only thing I can think of that differs from your guide in the OP is the different CM7 sd-rom I (had to) use.
[Nook Color Android Development] jtbnet:
My card is using a SDcard Modified CWR 3.0.1.0 with recovery.fstab as

# CWR 3.0.1.0 SDcard uRecRam: /etc/recovery.fstab

# mount point fstype device [device2] [fstype2]

/boot vfat /dev/block/mmcblk1p1

/system ext4 /dev/block/mmcblk1p2 NULL ext3

/data ext4 /dev/block/mmcblk1p3 NULL ext3

/cache ext4 /dev/block/mmcblk0p7 NULL ext3

/emmc vfat /dev/block/mmcblk1p4

/sdcard vfat /dev/block/mmcblk1p4 /dev/block/mmcblk1

/sd-ext ext4 /dev/block/mmcblk1p4 NULL ext3

This is good for CM7 installs and some others but not B&N as FS is ext2 I believe...
[Nook Color Android Development] ADude:
The simplest fix would be to replace it with RC3. ;)

Actually, Calendar is important to me lately, so the difference is non-trivial, at least in my case.
[Nook Color Android Development] 360Razir:
+1 for this...please and thank you.
[Nook Color Android Development] Techienana:
Thanks yet again, Racks! I so much wanted to run HC off an sd card and now I have two ways of trying it: your dual-boot and this thread. I had tried this method several times before, always unsuccessfully, until tonight. The secret to success: step by careful step, follow the directions. I am now running HC from an sd card and... loving it!

You do a great job of helping the members here; keep up the good work!
[Nook Color Android Development] RaZacs:
Thanks, it works great. I could install nookicomb on my sd.

So, I've a question : CM7 is installed on emmc of my nook. Is it possible use the 4th sd partition with CM7?

By default nook uses boot partition.
[Nook Color Android Development] racks11479:
Yes. Simple enough. You could either use adb to pull vold.fstab and push it back. Or use root explorer to edit the file. It resides in /system/etc/vold.fstab

Edit the line where it mounts /sdcard from auto to 4. Reboot and you should be good Togo.

Thanks,

Racks
[Nook Color Android Development] RaZacs:
Perfect. Thanks again.
[Nook Color Android Development] :
If I wanted to run the HC distro, do I need the CM7 sd initially? Can I just burn the bootable cwm, reformat the card in my computer, then install the hc onto it?
[Nook Color Android Development] racks11479:
The reason for the CM7 sd is so that you have an img with the correct partitions created for flashing. I'll prep a generic one when I can that will include the Modded CWM for flashing.
[Nook Color Android Development] RaZacs:
Problem again :

I assume with nookie comb on sd I can install apps from the market. So I tried that, no result : download starts and disappears and... nothing.