yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Awats:
What you want to do is take the uImage file and System folder from the 424 overclock zip file and put them into the new build zip file and THEN copy that to the SD card. However, the uImage file in the overclock zip file needs to be renamed to "kernel" for the Nook to pick it up.

Load WinRAR or your favorite zip program and upzip the build. You will see the System folder and a uImage file in both. You are taking the OC stuff and inserting it into the build. What does this all mean? It means the dffference in overlocking is in that uImage file and System folder. What specifically, I don't know.

Once done, zip it up and copy that to the SD card.

As mentioned above, you can skip the build unzip step and just add the new "kernel" and replacement System folder directly. I didn't show that so people would see what was really happening. Maybe some don't want to know that part.

I can do it for people but where do I host the 100MB file? Also, don't assume I will do it for all future builds. I can't commit to that.

Actually, once the OC uImage/kernel and System folders are extracted a simple DOS batch file could do all of the work using pretty much any of the zip file programs.
[Nook Color Android Development] Taosaur:
I've seen a few people miss this from Awats' post: YOU'RE NOT PUTTING ANYTHING ON THE SD CARD UNTIL STEP 5.

"Build" refers to the "update-cm-...zip" file on your PC. You are going to unzip this file, make some changes, then zip it back up and drop the updated .zip file on your SD's boot partition.

HOWEVER

Racks says the OC kernels in his thread are already ext4 and should work out of the box: http://xdaforums.com/showthread.php?t=998861
[Nook Color Android Development] gregh77:
thx for the instructions, i will try this at lunch and report back....
[Nook Color Android Development] japzone:
Hold N+Power for 6 "alligators" then release and it should work.

____________________________________________________

Sent from NookColor CM7 uSD using Tapatalk
[Nook Color Android Development] DizzyDen:
ok... do this....

1. Extract OC kernel zip to its own folder... I guess you have already done this....

2. (I copied and pasted uImage in same folder... gave me file called uImage - copy) rename uImage (uImage - copy in my case) to kernel

3. open cm7 - update zip file in 7zip, winzip, winrar... whatever program you use...

4. from the OC kernel folder... drag and drop kernel and the folder called system into the program you have the cm7 update zip open in... it should ask about adding/updating files/folders.... tell it yes

5. you now have a cm7 update zip file with the OC kernel and all files it needs.

You are updating the system folder in the CM7 zip file... nothing on the SD... and DEFINATELY NOT the meta folder (we use the cm7 update script to install this along with cm7.
[Nook Color Android Development] TheTodFather:
Thanks so much. It is so clear as day now. Sorry if i mucked the thread up.

I had already changed the OC kernel myself to ext4 so at least that part was done. This is my second day with having a os on the sd card and it was just a little overwhelming. I really appreciate all the help for all you. Thanks
[Nook Color Android Development] SiL3nTKiLL:
downloading this now!!!!
[Nook Color Android Development] TheTodFather:
Ok I got it to work!

I have a much much easier way to do this for anyone else trying to do this.

1. Download your ext4 Kernel for use with the more recent nightly(s)

2. Open it up and delete the meta folder!

3. Rename uimage to kernel. (done)!!!!!

now just drop the original ext4 kernel that I just had you fix up and place it on your SD card.

When you boot you must boot into recovery while Sd card is in. It will load your kernel....B-O-O-M Headshot!!!!!

*make sure that you don't rename the original file you download and just drop it on your SD card!!!!! so easy.

So just download Kernel,open it, delete the meta folder, rename uimage, then place it on sd card. This way is by far the ez way to do it.
[Nook Color Android Development] TheTodFather:
Ok now that i got that down to a science.

So how do we replace the u-boot 1.2 over the 1.1? For when i feel like upgrading kernel to .32!!!!
[Nook Color Android Development] Taosaur:
So no joy dropping in Racks' ext4 SD kernels as-is?
[Nook Color Android Development] gregh77:
so dont zip it back up before putting on the card? just the system folder and kernel(uImage) file?
[Nook Color Android Development] Taosaur:
You don't have to unzip it in the first place. Just open it in winrar, make the changes, update, then drop the zip file on the SD's boot partition, but yes the final product needs to be a zip file.
[Nook Color Android Development] gregh77:
got it, will try tonight. thx
[Nook Color Android Development] TabletConnect:
thanks. I was not releasing the power button first. that was my mistake. Now it works.
[Nook Color Android Development] brandner:
Removing Phone.apk and Telephony.apk

Hey, I helped a friend get their Nook Color up and running with this great option. It was perfect for them to evaluate CM7, and they love it. We've been playing around with CM7 ROMs on our Android phones, so this was a neat experience. :)

We're wondering if anyone using this size-agnostic CM7 SD card option has tried removing Phone.apk and Telephony.apk? It's supposed to help improve battery life, since the Nook Color doesn't have the phone capabilities.

For example, see: http://xdaforums.com/showthread.php?t=1072271

Has anyone else tried this? How do you do it, since the SD card is mounted read-only? We tried using terminal and ADB, both being dead ends due to the permissions problems. :confused:

Would it possible to create a variation of the CM7 update zip that does not contain those APKs and apply that?
[Nook Color Android Development] rhester72:
You need Root Explorer, but it's a waste of time - there is no measurable improvement in battery life from removing them.

Rodney
[Nook Color Android Development] Taosaur:
Another method would be to go into the cm-update...zip file on your PC and delete the .apk files, then update, but yeah, there's probably no point. I looked at my battery use and saw phone idle and cell standby sucking a wopping 40% of my battery usage...10 minutes after I'd turned on the machine. After actually using the NC to do some stuff, they'd subsided to a combined 7%, with the vast majority of power drain going to the display, OS and system.
[Nook Color Android Development] gregh77:
this loads the OC zip file?
[Nook Color Android Development] gregh77:
it can't be that difficult, but i put the zip file on the boot partition and it doesnt find it...

EDIT... finally worked after 4 tries....ridiculous
[Nook Color Android Development] TheTodFather:
anyone have any luck with the .32 kernel with 1.2 uboot?
[Nook Color Android Development] khaytsus:
I've been using the u-boot.bin from this SD installer with 2.6.32, the original test version as well as the first 7.1.0 RC0. I didn't try beta2, and beta3 today I have weird problems. Just flash of white and reboots after 30s.

I have not tried the u-boot.bin 1.2.0 on this without changing the overall ROM.. I could be mistaken but I'm thinking that verygreen modified the u-boot.bin to handle the flashing of zips (N pushed, call CWM or such).. Could be something else though.
[Nook Color Android Development] rhester72:
You're exactly right, VG's u-boot is modified from 1.1.0 stock and will need to be re-modified and re-compiled from 1.2.0 sources.

Technically speaking, the 1.2.0-compatible u-boot is NOT needed to run the latest betas (I have beta 2 running from a fresh VG image), but IS needed for video/YouTube to work properly without stuttering.

Rodney
[Nook Color Android Development] case-sensitive:
I've updated my NC to stock 1.2 and no CWM. Questions: (1) I assume I now have the new u-boot installed? (2) would I still have problem using evergreen's script to install beta 3.1?

I think the answers are Y & N, but I want to be sure.

Thanks!
[Nook Color Android Development] rhester72:
Actually, it's the opposite - VG's image contains the modified 1.1.0 u-boot and you will have video and YouTube issues with 3.1, until someone produces a 1.2.0-based u-boot compatible with VG's method.

Rodney
[Nook Color Android Development] zombieflanders:
Quick question: Does Awat's method of renaming/replacing "kernel" and "/system" still work with both beta3 and the new (05132011) OC kernel?
[Nook Color Android Development] thepodgod:
Original link is dead, anyone have a mirror?
[Nook Color Android Development] LBN1:
I am on a CM7 Nightly 67 with the 1.1 overclock on uSD from the OP, and it seems to run really well, is fast and does just about everything I need it to.

Can someone tell me the benefits of going from the .29 kernel, to the .32 kernel which requires a CM7 Beta (instead of a nightly or stable), other than the all important Sleep being fixed? I read that the Beta still has some kinks in it, and am trying to decide if I should just wait until the .32 kernel is part of the stable or nightly releases.

** Edit: I was able to get the 1.3 kernel running on a nightly, and it worked fine, but once I took the uSD out and made an image of it; after putting it back in the Nook would not reboot and would get stuck on the "Touch the Future of Reading" screen.

** Edit: Back to the 1.1 kernel, and now can't get it to reboot into recovery. Is there an easier way to boot into recovery other than the hold the N and Power buttons, wait 6 seconds, and hope it works?

Thanks developers for all your work!
[Nook Color Android Development] Robodude288:
Ill second that
[Nook Color Android Development] robot8:
Try again? Just checked and original link to VG's installer .img seems fine to me.
[Nook Color Android Development] robot8:
VG drops in occasionally, let's hope he updates a 1.2.0-based u-boot soon. Maybe he's waiting for .32 beta to be ironed out first? I'm still on 7.0.2 with OC 4/24, everything's running rock steady and I'm reluctant to update but the fixed sleep is calling so loudly :(
[Nook Color Android Development] angomy:
Updated:

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

Nookie1, not VG though. Does it matter? I've been using Nookie1's u-boot.bin for a while with VG's SD install. Or do you mean a different file?

*edit: Bah, just updated to 1.2 u-boot file and it's not working, so I guess it does :|*
[Nook Color Android Development] dweezilz:
that did it. I had to rename those files back to their original name and now it boots...got market, etc...! Nice. Not sure what happened though.
[Nook Color Android Development] cybertimber2007:
adb logcat

Alternatively, you can use "adb logcat > something.txt" and it will write the logs to a file ;)

Ctrl+C stops the logging.
[Nook Color Android Development] verygreen:
If you are not using v1.1 installer, did you update u-boot.bin? The u-boot.bin in the first image is not recovery-enabled it seems.
[Nook Color Android Development] verygreen:
Yes, you need to rename .bak back if you do not update with the cm7 nightly zip because the gapps package does not contain the new kernel.

Best of all to do this is to upgrade to v1.1 then you can boot into "recovery" which will install all the stuff you throw into first partition as long as the naming in conforming to expected values (outlined in the first post).
[Nook Color Android Development] BigBadSloth:
I tried adb logcat, this is all I get:

- exec '/system/bin/sh' failed: No such file or directory (2) -
[Nook Color Android Development] SCWells72:
I actually did use the v1.1 installer but then restored a TitaniumBackup of apps & settings from the previous installer to get my apps and settings moved over. I downloaded the u-boot.bin from the first post and there are differences, so I put that on and tried again. Still no luck. Any other thoughts?
[Nook Color Android Development] verygreen:
Hm, I verified that the new u-boot works. It was kind of tricky to enter recovery mode and I managed to do it not from a first try, but it's definitely possible.

(after you have uRecRam and uRecImg properly named unlike what v1 did)

If you mean that after you rename the uRecImg and uRecRam to uImage and uRamdisk and then try to install something that is not full nightly update you cannot get into the android until you restore old uImage and uRamdisk, this is supposed to happen since the installer does not know where to get the proper kernel image and ramdisk if not supplied by the installed packages.
[Nook Color Android Development] SCWells72:
Aha! Breakthrough! I didn't realize I had to rename that direction to get it to pick up the new build. I'm golden now! Thanks for bearing with an Android newb!
[Nook Color Android Development] FrayAdjacent:
Awsome work.

Having SERIOUS difficulty getting into recovery to get the Market loaded. Out of about 20-30 reboots, I got it in (what I think is) recovery once. It went to the 'android _ ' prompt and blinked there for about 10 minutes. Then I powered it off and started it back up the 'normal' way. Went back to the same prompt. Kept doing it until I removed the gapps....zip from the boot partition.

I have not been able to get it back into recovery since. I've re-downloaded the gapps zip file, deleted it from the SD card and copied it back over a couple times.

Also ADB from my Windows box doesn't work. Device Mangler shows the composite ADB device, but ADB from the command line never sees the Nook.

As a suggestion, Green, perhaps update the utility to not only unpack/install CM7, but have it also install the gapps zip from the SD card at the same time?
[Nook Color Android Development] verygreen:
It's not a recovery.

The same installer thing with a penguin would constitute recovery mode.

You really need to hold power and N button all together and then keep holding for a second or two after the "Touch the future of reading" message,

then release the power button (or the unit would poweroff).

It will work as in even on the first install it would unpack everything including the gapps if you put it there.

In my experience if you put gapps together with the initial install image, the boot will fail (will just sit at the ANDROID_ screen) and the traces look like it's due to gapps unable to register or something due to wifi not setup.

If your ADB does not recognize nook, make sure you added the nook device id to known devices list, check the wiki for instructions.
[Nook Color Android Development] FrayAdjacent:
Well, I got ADB working. Missed a step. RIF failure on my part.

Also re-read this thread and went through it with the 1.1 version of the utility and booting with the renamed uImage and uRamdisk. Worked like a charm!

Now all I need is a faster uSD card. Class 6 is still slow!
[Nook Color Android Development] ADude:
NC does not play well with Class 10, according to the reports. Class 6 is as fast as it gets at the moment.

Try doing other things, like Dalingrin's Overclocking Kernel.
[Nook Color Android Development] DizzyDen:
Never had a problem with class 10 cards myself...

Some information regarding 16 gig SD's with this message... may help figure out what's going on with them....

Worked perfect on my class 10 8 gig card....

When trying on class 10 16 gig card went through with one error not seen on 8 gig card:

Partitioning the card ...

The number of cylinders for this disk is set to 1946.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Done partitioning, creating filesystems

Went through everything else just fine until:

Writing superblocks and filesystem accounting information

Sat there eternally...

hard power off then power on...

goes through extracting with some errors in /tmp/backuptool.sh's not existing...

Sat at Android_ eternally.. nothing could get past this

Can get into recovery... just not boot CM7.
[Nook Color Android Development] MarkE08:
Thanks for making an easy way to test CM7 on SD :)
[Nook Color Android Development] verygreen:
This is harmless.

Ok, this is the problem. If formatting failed, the script does not check the status (and mount too).

So then the mount fails too, the unpacking happens to ramdisk.

Then when you reboot, your /system partition is not populated.

Also on next reboot the script blindly assumes that if the partition is really there, it must be suitably formatted already and does not reformat it.

Can you insert this sdcard into a computer now and format second partition with mkfs.ext4 (also 3rd just in case).

(hm, now that I think about it, there were two mkfs, for /system and /data,

which one hung?)

after that boot into "recovery" with the full CM .zip present. and it'd should be able to mount the freshly formatted stuff and unpack there.

[/quote]

these are normal.
[Nook Color Android Development] cybertimber2007:
It might indeed be a problem.

There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

I've noticed in other threads people reporting that 16gb cards didn't work. Kernel issue?
[Nook Color Android Development] verygreen:
I don't have 16g card myself.

Can you boot into emmc, insert 16g card and try mkfs.ext4 on 2nd and 3rd partitions of the sd card, then see what kernel messages do you get if any?
[Nook Color Android Development] cybertimber2007:
Unfortunatley I don't have one either.

Btw, seems my post edit didn't save, but I mean to word it as "the problem might be at boot time", though I thought those issues were only for really old kernels and such. I'll try to get my hands on a 16gb if I can and test it out though, since I know what you are talking about ;)
[Nook Color Android Development] DizzyDen:
I will do more testing as you asked when I get home this evening... I was just trying to provide you as much information as I could as to what I was seeing as it went through its process.

However, to answer the question as to which mkfs failed... I didn't see either one fail.

Will try the 16 gig test again tonight and try to take a pic of the screen when it is in the eternal hang up... you will be able to see all the text on the screen that way... IF the pic comes out good enough.
[Nook Color Android Development] smartmind:
Will your work can be used with the bottom status bar mod? And how?
[Nook Color Android Development] thepodgod:
Yeah, it's working again.
[Nook Color Android Development] verygreen:
I've got a number of question about 2.6.32 not working with video/youtube properly.

I installed the latest update from dalingrin today (working on unrelated usb crash) and when I try to play a youtube video, I do not see any problems with the original u-boot binary.

I'd really like to better understand what the problem is and how to reproduce it before I blindly go and start changing things.
[Nook Color Android Development] victle:
verygreen, people reported, in the beta .32 kernel thread, problem with .32 and the old u-boot in youtube and other video and the new u-boot seems to solve it, I flashed the new CM7 test build with .32 kernel on SD and it slowed everything like hell. Replaced the u-boot.bin with new version but it didn't work. I guess u-booot in BN 1.2 doesn't load firmware in SD anymore. Could you have a look?

Thanks!!!
[Nook Color Android Development] verygreen:
When you say slowed, what do you mean?

The playback seems to work just fine for me.
[Nook Color Android Development] victle:
It's much slower than the nightly #67. I got Quadrant score under 1000. I only wiped cache and dalvik cache, didn't wipe system though.

Sent from my HTC Vision
[Nook Color Android Development] verygreen:
Ok, I can see that.

The stock 1.2 u-boot should be working fine, btw, but it cnnot find "BCB" and decides to power off instead.

I'll see what I can do to relieve that and I guess a new image version is indeed forthcoming.
[Nook Color Android Development] case-sensitive:
Noob question: How do you clear cache and dalvik if run CM7 on sdcard -- do I need to install CWM on emmc first? For various reasons I'd prefer to leave emmc alone for now...

Thanks!
[Nook Color Android Development] verygreen:
I just boot into sdcard, connect with adb shell and then do rm -rf /cache/*

then reboot and you are golden.
[Nook Color Android Development] verygreen:
Ok, I guess it's sort of a poll.

How many people are really interested in the recovery that is called with power + N key combination at startup?

If I replace it with ability to reboot into recovery from CM7 (press and hold power, choose reboot, choose recovery), is there still demand for the old way of triggering recovery by pressing the keys?
[Nook Color Android Development] angomy:
If it doesn't affect the original updating method (drop zip in /boot, enter recovery) I don't care either way. I was ending up using power + volume keys anyway since I had nookie1's multiboot installed. Will it affect whether or not modded u-boot.bin files work? Just curious since nookie1's 1.2 updated multi booter isn't working on the current image. I don't really know how this stuff works since I'm just a multimedia geek. :|
[Nook Color Android Development] lschroeder:
Phiremod's V6.2 ROM based on CM7 has the (press and hold power, choose reboot, choose recovery) option. It does not work and I must use the power + N key combination with finger release to boot into recovery. I like having the power + N key standard hardware option available.
[Nook Color Android Development] lschroeder:
@verygreen I have loaded dal's beta 3.1 ROM into first petition.

I can not get it to load into your recovery. I was able to get 2.6.32 ROM's to work earlier (test-encore and 2.6.32 signed) but starting with beta2 and now beta 3.1 I can not get power + N to boot into your recovery. When I release it never gets out of initial boot screen.

I flashed from Phiremod's V6.2 the new uboot.bin using Update-BN1.2-uboot.bin.zip. New message does not show when I boot from update-cm-7.1.0-RC0-encore-2.6.32-signed.zip on your sd card.

Do you have a new u-boot.bin and other files that I can replace since his new beta's and OC's need the 1.2 u-boot? Is this my problem? Do we need a new image to work with the lastest 2.6.32 ROM's and OC's?
[Nook Color Android Development] victle:
@verygreen, thanks for looking into this. As for recovery boot option, either way works for me.

Thank you and others talent devs for the new kernel and all the amazing works.
[Nook Color Android Development] bugeyed1:
having issues with latest "stable" rel

the 5/8 release is giving me fits.

Issues:

Nook reader, FC & slugging response to library selections.

Pulse Reader, Was working poorly & now FC at launch.

After reboots, get "problem loading widget. This sometimes just takes some time, but often does not resolve.

WiFi doesn't survive sleep. May depend on how long it sleeps.

If I switch from Zeam to ADW launcher & launch Pulse, I get FC & then am back to Zeam (default)???

BTW I had been running an earlier release on CM7 using Zeam & Pulse worked fine & so did WiFi.(of course it didn't sleep).

I am using a Patriot 8Gb class10 uSD that worked OK with previous CM7 rel.

Edit: Seems like after any app FC, I can't launch anything without getting a FC of Zeam Launcher. Even trying to move something around on the screen.

Think I will update to the latest nightly & see what happens. Couldn't be any worse!

kev
[Nook Color Android Development] japzone:
If you can get the Recovery Reboot working that'd be great but I also would like the N+Power(or equivalent) just in case my card won't boot.

____________________________________________________

Sent from NookColor CM7 uSD using Tapatalk
[Nook Color Android Development] GTT1:
After doing the power n boot for what seems like an eternity and never getting it correct I now have it down and usually can do it first time. I would have loved the option to do this from the screen and am sure many other new to NC's in the future would be appreciative.