yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Snyperx:
So I decided to go back to 7.0.3 with Dal's OC'd kernel. No go. Apparently the legacy .29 kernels do not like the new uboot version since the system would not boot after flash the OC kernel. Was working fine up to that point. Not sure what I'mm going to do now.
[Nook Color Android Development] miniaturepeddler:
Notice that the 76 file is 92mb versus the 88 of previous nightlies. They must have really crammed some new stuff into it. :<
[Nook Color Android Development] oldman_58:
Live Wall papers are back in the release
[Nook Color Android Development] Ronin3178:
Did you install the modified, to ext4, OC kernel? I had 7.0.2 N70 running on uboot 1.2 with dals 4/24 OC (modified ext4)
[Nook Color Android Development] oldman_58:
I redownloaded #76 with Google apps, same no boot result

#75 with uboot 1.2 works great, has anyone succesfilly loaded #76?
[Nook Color Android Development] aasoror:
Same here, reverted to #75 running without a problem.

Not sure if its uboot related because I am replacing the kernel with "ext4-CM7-dalingrin-OC-emmc-042411" any way.

OK that further proves that its not uboot related.
[Nook Color Android Development] Snyperx:
What the link to that? I couldn't find the modified one on his site.
[Nook Color Android Development] Ronin3178:
Just go into the zip and find the update script, open as a txt file, find the ext 3 and change to a 4, flash.

Zip/meta-inf/com/Google/update.script
[Nook Color Android Development] chisleu:
make sure it doesn't have CR/LF if you are on windows. I use this app called "EOL converter"
[Nook Color Android Development] mmtoman:
Nightly 76 won't boot for me I get stuck right before the boot animation

Sent from my Tesla Coil + leanKernel Thunderbolt using XD Premium
[Nook Color Android Development] residentorca:
Sorry to hear about those who had problems with 76. I've decided to stay on 75 and could live with it a long time if needed as everything continues to work well. I've only experienced what may be a battery calibration issue -- the plug glows green at less than 100% charge. I've been upgrading to these nightlies on nearly a daily basis, before a full discharge cycle can take place thanks to the extended battery life which the deeper sleep provides.
[Nook Color Android Development] aasoror:
Here you are.
[Nook Color Android Development] ADude:
Or use Notepad++ (free Windows application) which is designed to edit Linux files without that problem.
[Nook Color Android Development] BitingChaos:
Don't delete any apps.

If you want to get rid of them, rename them. Root Explorer makes it easy.

Just rename "Whatever.apk" to "Whatever.apk.bak". They will disappear from the app list then.

Many apps expect other apps to be there. Even though the Nook Color can never use "Camera.apk", Gallery will expect it to still be there, etc.
[Nook Color Android Development] oldman_58:
Tried #77 - FAILED

Loaded #77 will not boot..

Loaded uboot 1.1 "Touch the future of reading" then loaded 7.0.3 booted all the way up everything functioning.

Tried #77 with the 1.1 uboot -- will not boot.

DEVS- is there something we need to know about the latest nightlies?

I don't think I am alone with no boot on 76 and 77

@dalingrin

HELP!!!!, Please
[Nook Color Android Development] Snyperx:
Sending out and S.O.S....I'm sending out an S.O.S........

#77 is not booting for me either. Something is seriously a miss.
[Nook Color Android Development] oldman_58:
I am beginning to think the new kernel is required... I am trying the 7.1 Beta now... I'll let you know how it goes...
[Nook Color Android Development] whatsinaname:
I am going to try 77 but not holding my breath, I am in same boat as the above people. Almost time to rebuild anyway, but I am just lazy :)

Hmm only thing I have done different recently was change the boot animation. I may try switching it back. Its the only thing I can think of that is not "stock" cm7
[Nook Color Android Development] :
Anyone on the 1.2 bootloader?
[Nook Color Android Development] furius:
I'm on 7.0.2 and now I would like to update to a new nightly build... I'm reading here that #76 and #77 are giving problems on boot... witch nightly version do you suggest? the #75 ?

thanks!
[Nook Color Android Development] seth.i.simmons:
Just downloaded it so I could check out the updaterscript and the kernel, and its still EXT4 and 2.6.29 kernel based. Sooooo, not really sure what's causing the problems for people. Maybe something in these nightlys is broken?? Idk just thought I'd post up what I found.
[Nook Color Android Development] yourm0m1:
just flashed n77 and dalingrins .32 51311 OC kernel and booted just fine...with .29 0424 no boot like everyone else but with .32 its fine...so try that out all
[Nook Color Android Development] oldman_58:
Where are you getting just the kernel?
[Nook Color Android Development] seth.i.simmons:
Hmm, that's weird, since the kernel file in the nightly said it was 2.6.29.... Must have been talking about something else.
[Nook Color Android Development] aasoror:
oldman is :

So you must have uboot 1.2 for that kernel to boot, right ?!
[Nook Color Android Development] whatsinaname:
How do I update to the 1.2 uboot? trying to find instructions but not finding anything.
[Nook Color Android Development] MadMikeSS:
I tried to update to 77 from 70, boots, shows "Read Forever" screen, then shows android on the screen then goes to what is essentially a solid cursor in the top right. Tried 76 also, did the same thing. Reverted back to 70 and all is back to normal again. I'm guessing that I'm running into the same issue as others here? I am not using any of the OC kernels, just the CM7 nightly.
[Nook Color Android Development] JimCanaday:
No luck with 77 for me...

I just tried updating from 72 to 77 with Dalingrin 040411. After the "A N D R O I D _" in the lower left screen, I went to an un-blinking underscore in the upper left screen (landscape). Fortunately, I was able to go back to 72 without issue.

Anything I'm doing wrong? Should there be a flush cache or anything else before flashing this or anything newer? My Bootable SD card reports CWR 3.0.0.6 but if I boot my encore into recovery, it says 3.0.1.0 (??). Should I update my SD to a newer CWR?

Side Note: This is the first time I've ever had a problem with flashing the Nook Color!
[Nook Color Android Development] oldman_58:
This is known issue, we have not heard from the DEVS on this as yet.

After fighting the last 2 nightlies without success, I am now running the new Beta 3.1 release with the new .32 kernel, you can find in the Developer's thread works pretty well so far, no overclocking yet but not too bad.

Any time you load a new ROM you should always wipe cache and Dalvik... those 2 can cause some odd issues..
[Nook Color Android Development] JimCanaday:
Oh! Funny that I've never done that before. I will start doing that now. Thanks for the info.... I'm finally starting to get the hang of some the other comments here. Lot's of "shorthand" notation I'm not used to. I think I'll hang back until overclocking is back.

Thanks for the reply!

(Sorry, quote unchecked - Thanks to oldman_58)
[Nook Color Android Development] Nburnes:
Go to the kernel thread, and there is .32 OC kernels.

Edit: Actually I linked them. http://coachz.inetpro.org/~dalingrin/nook/kernels/051311/ go up to 1.2GHz max
[Nook Color Android Development] Awats:
I tried 77 via SD card using the generic image + build 77 + gapps 0311 and it just sits at the "Touch the Future of Reading Screen" and never proceeds.

I tried build 74 again and it works. So for some reason the later builds don't load.

I haven't tried swapping in the 0424 OC kernel on build 77 but it didn't work any different on build 76. It hung too so I don't think it's going to help on 77.

I did try dropping build 76 zip onto my working build 74 and it hung up too the same way. Fresh install or updating - neither work.

So I will wait to see what the issue is.
[Nook Color Android Development] Ronin3178:
Ok, a few things. I am going to share a few dropbox links from my personal (free) folder. Last time I did this, I got so much traffic my account got suspended for three days.... SO if you really need this, or cant put up a link somewhere that others can freely d/l, don't.

First the recovery fix for 3.0.1.0 : http://db.tt/gDlb5mw

Update from 1.1 to 1.2 uboot : http://db.tt/1SKhhzQ

Dal's .32 OC kernel 5/13 : http://db.tt/TjtmN68
[Nook Color Android Development] oldman_58:
Thank you very much
[Nook Color Android Development] whatsinaname:
Thanks for the links, but just curious, to install 1.2 uboot is it just install zip by clockwork?
[Nook Color Android Development] Nburnes:
Yes.

<10char>
[Nook Color Android Development] JimCanaday:
Oh. When there was no "OC" in the name, I just assumed (there's that dirty word) it was not an OverClocked kernel. Thanks!
[Nook Color Android Development] Ronin3178:
It is an OC kernel, the beta only goes to 925MHz, that kernel allows up to 1200MHz
[Nook Color Android Development] skwalas:
I can confirm successful flash of N77 with the 0.32 kernel.

Note I started at N75 with 1.2 uboot. Flashed N77 and 0.32 kernel together (no reboot in between), and wiped cache only (no dalvik).

N77 flashed by itself: no joy

N77 + .29 OC kernel: no joy

N77 + .32 OC kernel: Success!

Not sure the implications of this. If N77 went to 0.32 kernel, would still expect it to at least flash on its own. So perhaps the bootloader change starting in N76 caused it to want to reference a .32 kernel? but it's still being bundled with the .29 kernel?

In any case, looks like I've now fully made the switch to .32 kernel on N77 nightly.

(under About Tablet, Kernel version 2.6.32.9 #166)
[Nook Color Android Development] ddgarcia05:
New to the nook, not to rooting and rooted phones. I"m gonna flash CM7 on my NC's eMMC, just need to know if I need to flash anything speical?

Also, I know its not related but how would I know if i have 1.1 or 1.2? Is it worth the upgrade? Will it break my root? Is upgrading as simple as flashing a zip on recovery like phones? Sorry for the noob question. Like I said, I'm not new to android.
[Nook Color Android Development] xawen:
If you're just going to flash CM7, not try to root the stock image then you don't need anything special. Just download one of the available SD bootable ClockworkMod images and use that to install a CM7 zip. Just make sure to wipe data, system and cache (*NOT* boot) when you do the install the first time. You can find the stable and nightly versions of CM7 here.

After CM7 is installed, you can use Rom Manager to install ClockworkMod to your emmc so you don't need the SD card in the future.

And the 1.1 vs. 1.2 thing should show up in the About screen under settings (don't have a stock image available so I can't give you the exact menu).
[Nook Color Android Development] Ronin3178:
1.1 "future of reading" 1.2 "Read Forever"

There currently seems to be a ghost battery problem with 1.2

No

Yes
[Nook Color Android Development] ddgarcia05:
The stock image is rooted. The NC is rooted. I bought it rooted with Phiremod's CM7 installed onto the eMMC. I simply want to update to the latest version of CM7 which would be nightly 77. Can I just flash nightly 77 and the OC kernel along with it and be good to go? I see links to uboot and recovery fix. Screw it. I'm just gonna back up and flash. And revert back if something goes wrong.

Edit: Thanks guys for the answers above. Appears that I'm on 1.2. I got that ghost battery problem.
[Nook Color Android Development] bekyndnunwind:
That's awesome!

Just wondering can you comment on performance? Have you tried the 3.1 beta w/ the .32 kernel, and if so how does N77 compare?
[Nook Color Android Development] whatsinaname:
Working now

Well as someone suggested, I flashed to the 1.2 uboot, and then installed 77. No luck. So then I downloaded Dalingrins .32 kernel, flashed the nightly 77 and Dals .32 and its working fine now.

They must have moved the nightly to .32? but odd that it installs for some, but not others.

Oh well, If I didn't want to tinker with it I wouldn't have bought the Nook, but I love to tinker and all these devs makes the nook a tinkerers paradise, keep up the great work!!!!
[Nook Color Android Development] Snyperx:
Just tried this. Downloaded #77 and Dal's .32 kernel. Flashed build 77 followed by the kernel. REbooted. Nothing. Still will not boot.
[Nook Color Android Development] wpnyc2009:
Same here

Same here mate, luckily I can get into CWR to flash back to CM 7.0.3.

Also, I had added u-Boot 1.2, IDK if that makes a difference. I'm in over my head with this.

Good luck m8s!
[Nook Color Android Development] whatsinaname:
This is really odd. I am on uboot 1.2, nightly #77 and Got Dals kernel from

http://coachz.inetpro.org/~dalingrin/nook/kernels/051311/

the emmc one. I cleared cache, flashed 77 and in the same session flashed the 051311 kernel. I am just glad its working for me, but sad its not for others :(
[Nook Color Android Development] Snyperx:
Got it working!!! Make sure you have a bootable SD card with the latest CWR (3.0.2.8). Also download the latest .32 kernel from Dalingrin (http://coachz.inetpro.org/~dalingrin/nook/kernels/051311/) as well as the latest build for CM7 (#77). Try this:

*I AM NOT LIABLE FOR ANYTHING YOU TRY AND DO TO YOUR DEVICE*

1. Boot into CWR 3.0.2.8

2. Format /system

3. Format /data

4. Format /cache

5. WIPE DAVLIK CACHE

6. Flash the CM7 build #77

7. Flash Dalingrin's .32 kernel

8. Remove SD card

9. Reboot

This worked for me.
[Nook Color Android Development] whatsinaname:
phew, glad I am not the only one with it working, I was getting a complex there for a minute :)
[Nook Color Android Development] Snyperx:
Someone needs to communicate this better. There is no mention that the new builds went to the .32 kernel. At least not that I saw.
[Nook Color Android Development] whatsinaname:
I thought they released a new stable, not for nook, but for other devices. maybe we are close to a new stable.
[Nook Color Android Development] :
You need to flash the 1.2 bootloader.
[Nook Color Android Development] Paul22000:
Wait, so nightly 75-77 = uboot 1.2 needed??? :eek: :confused:
[Nook Color Android Development] EverythingNook:
i need the 1.2 uboot? how would i flash that?
[Nook Color Android Development] jkurl:
This way works just fine no need for a bootable CWM SDcard though it never hurts to have one just incase.

I flash uboot 1.2, N77 and .32 Kernel and then wiped cache. Rebooted and it took a few mins to boot but it booted just fine.

Thanks for the fix.

here is uboot 1.2 http://www.megaupload.com/?d=SFX0W4KM flash via CWM
[Nook Color Android Development] EverythingNook:
alright before i flash i need 1.2 uboot AND the .32 kernel?
[Nook Color Android Development] Awats:
Yeah, I think that sums it up. At the risk of getting jumped on, if this is true, it needed to be pointed out. Why isn't the right uboot in the build?

Or is it saving it from the original generic image?
[Nook Color Android Development] camalus:
You need 1.2 and. 32 kernel.

Simple as that.

If you don't know how to do this... or how to search or read to find the links.... you probably shouldn't be messing with this stuff.
[Nook Color Android Development] adma84:
Does anyone's NC take forever to charge on CM7? Thinking it might just be my charger but thought I would ask
[Nook Color Android Development] digitalslacker:
if i'm not using the stock charger it takes forever but I don't think it's cm7 specific.

I noticed the same thing stock and w/ HC.
[Nook Color Android Development] adma84:
my NC charger makes a sparking sound and smells like it is on fire. It's done it several times. So, yeah, I am using my wifes iPad charger...but it's weird, it's only pulling 40mA. Her charger can source 2Amps, so I don't get it. I let it charge for over 8 hours last night and it went up 40%...It may not have been a speed demon to charge before, but it wasn't like that
[Nook Color Android Development] jkurl:
I would take it off the I pad charger. Even though the have the same amp output it probably uses a different type of circuit to charge the device. It could be as simple as how the connector is grounded plus the ipad might have circuits that help match it up w/ the charger sort of like when you have a stereo amp that has to match the speakers ohms. To high ohms it will over work the amp circuits to little ohms the speaker will blow. You nook may be working to hard to match that and over working.
[Nook Color Android Development] adma84:
Well, it's a standard USB charger. Speakers are a different issue because if you don't match impedences correctly, then yes, you can draw too much power from your stereo. If there was anything to worry about, it would be the NC drawing too much power (which it's not drawing enough). Apple has done special things in the past, so they could be limiting power output to the NC. At least it isn't catching on fire like my NC charger (which by the way, happened even with stock Eclair)
[Nook Color Android Development] donballz:
The status bar process force close on boot. Meaning I have no notification bar. I am on nightly 6. Anyone else having this problem?

Also, is there a way to map the volume keys to back/menu? THanks
[Nook Color Android Development] claudius753:
Yes, multiple people have reported that nightly is borked.

You can use Button Savior in the mean time.

I've never done it, but here is a thread on how to remap the volume keys:

http://xdaforums.com/showthread.php?t=965023
[Nook Color Android Development] jimmy87lee:
New nightly is up at cyanogen.

After flashing, I could not connect to my wifi because Settings kept crashing when I selected "Wireless & Networks"

Here's the workaround: Add "Custom Shortcut" to home screen -> "Pick your activity" -> "Settings" -> "Wi-Fi settings"
[Nook Color Android Development] superkevx:
good tip, thought everything was good with the new nightly but hadn't tried wifi yet till I read this.
[Nook Color Android Development] pavlos46:
I think you did it .. with v7

I flashed it over v5 and now wifi connected no problem status bar didn't crash and market works shows payed apps installs everything and shows my apps with no crashes.

Also I am not sure what you did with touch but works better.

Will do a coupleof rebooted just to make sure things stay that way.

Device is superfast.
[Nook Color Android Development] superkevx:
in settings or any menu when I select something the 'depressed' button color has a weird blue line through it. dont remember seeing this in earlier nightlys but i really havent played around with the other builds much.
[Nook Color Android Development] jimmy87lee:
Can't figure out how to install gmail from market... I installed the latest gapps from the cyanogen wiki, but market can't find gmail to install. Tips?
[Nook Color Android Development] superkevx:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=238802989b888e9c&hl=en

gmail seems to be taken off the market for now, that might be the cause of your problem.
[Nook Color Android Development] M@XLOL:
Oh sweet its spicy tuna!
[Nook Color Android Development] adma84:
spicy working for my EVO and my NC sounds too good to be true!
[Nook Color Android Development] digitalslacker:
v7 worked great initially but I started noticing new issues.

I read that a complete wipe was recommended but I took it a step further and installed v7 as if it was a first install. format system/data/cache.

Market worked for the most part. I had all my purchased apps and some of the free ones...but not everything. They all did pull down and install from Google after signing in to the market.

Wifi did seem much more stable, maybe that was just me though. v5 was giving me issues on wake reconnecting to wifi but i'm not sure I gave v7 long enough to truly test that.

maps worked! didn't expect that so that was nice.

but then I started to get force closes in apps that were working before, Rom Manager for instance.

I completely re-installed again, this time skipping things like the OC script, button remapping etc. Just v7 and gapps. I also didn't do any restored with Titanium the second time.

I had a new issue opening the wireless settings, force closed every time.

Something new I saw when selection menu options, settings, market etc was an orange accent with a blue bar down the middle...happened on the first and second tries.

Just wanted to report those for the devs and folks looking to go to v7.

For now i'm going to nandroid back to v5.

great work, look forward to jumping in here every morning and trying out the latest and greatest!

thanks!
[Nook Color Android Development] spikey911:
I did an upgrade from 5 to 7...

7 seems to have a slight difference in dpi.. I am getting FC when trying to enter wireless settings, so I can't change networks.

Other than that, runs ok.
[Nook Color Android Development] superkevx:
changing the theme fixed the blue bar problem for me.
[Nook Color Android Development] newellj79:
How were you able to make a backup of cm7? Complete details please. Did you make it on the ext4 sd card? How was there enough room if so. Thanks!
[Nook Color Android Development] newellj79:
***previously posted wifi work around... add short cut to home screen, settings, wifi. It should pull it up no problem.
[Nook Color Android Development] Awats:
Thanks dad. I can handle it now that I understand the issue.
[Nook Color Android Development] Paul22000:
Agree. It's one thing to have a beta build with the caveat that it has some issues, but switching the uboot like this without saying anything is kind of odd :eek: If it were more dangerous, people might have bricked their devices.
[Nook Color Android Development] EverythingNook:
but i like my 1.3 overclock ):
[Nook Color Android Development] ddgarcia05:
DAMNIT i'm pissed. I have CM7 build 77 on my device. I wasn't able to flash the kernel before it booted. I rebooted but now I can't access recovery or the rom. Just that blue line on top.

what the heck do i do now.
[Nook Color Android Development] EverythingNook:
do you think every new nightlie will require .32 kernel and 1.2 uboot? and to update uboot its just a simple cwm flash right?
[Nook Color Android Development] Paul22000:
Turn off Nook. Hold Nook button while turning on and hope it gets into CWM.

You have to hold BOTH for a while: Hold power for like 5 sec (not too long or it will auto-shut off again) and after that KEEP holding the Nook button for like 20 sec.

Other than that, make a CWM SD card as that will work 100% of the time :) No bricks on the Nook :cool:
[Nook Color Android Development] ddgarcia05:
Looks like I gotta make a CWM SD card got a link? I see several
[Nook Color Android Development] Paul22000:
Try this (step 1): http://xdaforums.com/showthread.php?t=1030227
[Nook Color Android Development] :
1.2 is way faster with .32 than 1.3 was with .29
[Nook Color Android Development] EverythingNook:
with the smartass govener too, right?
[Nook Color Android Development] :
Meh.

Smartass isn't perfected yet (IMO). But still damn snappy. Sometimes just a bit weird, though.

Ondemend is good.
[Nook Color Android Development] helloelan:
What's the Android version of the latest nightly? Should I just upgrade to this from the "beta" CM7.1 build (formerly?) needed for the .32 kernel?
[Nook Color Android Development] jkurl:
The N77 is 2.3.4
[Nook Color Android Development] MadMikeSS:
Put 77 on with dalingrin's OC .32 kernel, worked this time. I think the CM7 install instructions for using the latest nightly should include the need to install the .32 OC Kernel in the instructions. 70 and at least 75, the only 2 builds I installed on the NC up to this point worked perfectly fine without the OC Kernel at all. I only ran into trouble with 76 and 77. I think folks just need to be aware that they will need to install with the OC Kernel, that's all.
[Nook Color Android Development] EverythingNook:
how do you fix "batterystatus" in CWM? also everything went fine! would you recommend ondemand over smartass?