yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] topcaser:
Yeah, it worked again - i just tried n107 and the loop appeared again. But after your recomendation, i flashed the last working one (n99) and it works again.

Nevertheless, what do you recommed me to get n108 running? Just flashing again?

verygreen, i have to say that i appreciate your excellent support here.
[Nook Color Android Development] verygreen:
Without logcat output to see what is failing I cannot tell you much as the cause is unknown.

I have not tried any recent nightlies, but I did a few rebuilds of the CM7 repo from yesterday and from two days ago and both worked without any significant problems (aside from starting up wifi on startup).

Of course you can try flashing again and see what happens, as you know how to restore to a working system.
[Nook Color Android Development] lschroeder:
Black Screen install Kernel 061811

VG... I was running MN from EMMC. I replaced a data SDcard with a card containing nightly 99 plus your USB HOST kernel. I then used NookColorUtility to load 1st partition (boot) and dropped Dal's 061811 sd Kernel containing OC plus USB Host kernel. I then powered off. Then restarted using the power button. I then got the black screen. I thought something wrong, so I tried power + N trick. When I left it reboot I used ROM option to boot into Recovery (thinking it would be yours). Finally on another normal boot I used the NookColorUtility to notice that that Dal's Kernel was gone. Then used Nook Tweaks to realize I had the black screen install, since I could up the speeds.

VG... Think I might want to install nightly 108 for Microphone - Webcam - Skype. Then add Dal's overclock, plus repatch of vold.fstab. Is there anything I can do to eliminate the black screens for these?

Edit: I used ROM Manager Reboot into Recovery after loading nightly 108, then again after loading OC 061811. I had the black screen install in both situations. I used wireless adb and my post 220 in the USB Host support thread to update vold.fstab for flash drive and fat 32 support.

http://xdaforums.com/showpost.php?p=14648163&postcount=220

Does this "If you have the "loading..." white text when booting, try updating the u-boot.bin file with the one from update 1.3 referenced in the first post." apply to me since I have it.
[Nook Color Android Development] verygreen:
Note that for webcam you need to use the specific nightly I build with a patch supporting it.

For microphone support you need to use at least the alsa.omap3.so that I referenced. The audio-enabled kernel might be a plus too, but probably will work without it (don't try to use skype calles while no usb audio device is connected, though).

Well, what I meant to say is if there is just the "loading..." message and no green cyanogen above it then you run off some installed u-boot that was supposed to be replaced by one provided in the nightly and should not really be happening.
[Nook Color Android Development] cpedley:
NO Keyboard to install WIFI
[Nook Color Android Development] androidmonkey:
For some reason I cannot edit my build.prop. ES Explorer gets root access but fails to write to the file.

Any ideas?
[Nook Color Android Development] lschroeder:
Yes this must be the case. I have the black screen install so I am not sure what is happening. Everything with just the "loading..." seems to work ok. Should I try to fix it?
[Nook Color Android Development] ionepig:
it worked... thanks a million.... :D
[Nook Color Android Development] Grogck:
Just picked up a 16GB Class 4 Sandisk from Radio Shack and was hoping I could knock this out fairly quickly over my lunch break, but seems I'm already stuck at the first step.

I downloaded the installer and extracted the image, but I can' t write it to my SD card from WinXP. I tried using WinImage, but the only partition it's showing I can write to is my hard drive. Tried Win32 Disk Imager and while it sees the SD drive it gives me an error saying there's not enough space on the disk. I'm searching back through the thread, but having a hard time figuring out the issue.

N/M: Somehow I got an older version of WinImage and didn't see/have the "restore virtual hard disk image on physical drive" option. Going to leave my question up though just in case someone else searches for it later on.
[Nook Color Android Development] androidmonkey:
Format your SD card in Windows, then run Win32 Disk Imager again.
[Nook Color Android Development] Grogck:
(original instructions for installing Gapps)

"shutdown your nook and take the SD card out, insert it into your computer.

Copy the gapps-... file to the SD card on the first partition (titled boot) without changing the file name."

When I take the SD card out of the nook and put it back in my computer it prompts me to format the card in order to be able to explore it. What step did I screw up previously?
[Nook Color Android Development] topcaser:
Hi

I have problems after booting:

First of all SwiftKey is not active any more. I have to go to settings, activate the keyboard and switch to it again every time after booting. The same is valid for gmail sync. Gmail is the only I want to sync with google servers but the setting gets lost after a boot.

Do You have similar problems?
[Nook Color Android Development] Anseri:
What is the "see above"? What should we be looking for? Also, I've replaced the stock cm7 recovery with clockwork recovery, manually via adb, would this still work as it's described here or do I need to do something different?
[Nook Color Android Development] topcaser:
Its me again - I have not solved my problems, two posts above, the next happen again:

I flashed n108 coming from n99 - and again: i get this loop during booting: CM sign with rotating arrow and after a while screen goes black and CM sign again.

Is there something i can do???
[Nook Color Android Development] verygreen:
"see above" for instructions on entering recovery.

If you installed CWR instead of supplied installer then of course you need to work with CWM instructions from then on.
[Nook Color Android Development] verygreen:
Connect with adb and do logcat, save output somewhere where others can see it.

Publish the link.
[Nook Color Android Development] topcaser:
OK, verygreen, Thanks for your help. I have to find out how to do that. In the meantime I want to address those problems again (see quote).

Thanks again for the help
[Nook Color Android Development] verygreen:
gmail sync (I assume that it just fetches mail) works for me.

I don't use swift keys so don't know bout that.
[Nook Color Android Development] androidmonkey:
Has anyone done a comparison of speed when running from internal memory vs uSD card?
[Nook Color Android Development] topcaser:
Hi verygreen,

attached find the catlog. Hope you can find the problem of the loop.
[Nook Color Android Development] fastoy:
http://humbleville.blogspot.com/2011/05/nook-color-update.html
[Nook Color Android Development] topcaser:
verygreen, did you find time to have a look in the logcat file? Would appreciate your help.
[Nook Color Android Development] verygreen:
The log file is way too short, you should have waited a couple of iterations of black screen and then boot anim replacing it I would think.

What I see in the log so far the biggest thing jumping at me is this and I am not sure how normal this is:

E/AndroidRuntime( 1386): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy^M

E/AndroidRuntime( 1386): java.lang.NullPointerException^ME/AndroidRuntime( 1386): at com.android.internal.policy.impl.LockScreen.<init>(LockScreen.java:346)^M

Do you have anything funny going on with your lockscreen I wonder?

Also if you used pastebin to upload the log
[Nook Color Android Development] topcaser:
Ha, that's a hint: I use widget locker. Maybe this is the problem? I will flash the old ROM again, deactivate widget locker and flash n110 again.

I will come back then with new info.
[Nook Color Android Development] topcaser:
Arrrggggh, that dont works. What i have done:

1. normally, when i go back to n99 it worked well for me.

2. n99 isn't available on the CM servers any more -> so i downloaded n103

3. n103 installed well and worked fine during boot. No problems at all

4. I deactivated widget locker (an app with personalized lock screen)

5. flashed n111 but still this silly loop

So, what can be the difference between these nightlies? Any idea, what i can do next. Do you need another longer logcat?

PS: The only changes on lockscreen are performed at n106: click.

It is this change: click. Maybe i have to change an option in lockscreen settings in a nightly which boots fine?

Personally i dont know, what i can do next to get it running

Edit: i can safely say, that n105 also works fine. I also believe that it has something to do with the lockscreen (imho), since the boot is as follows:

1. CM icon appears with rotating arrow.

2. This icon with the rotating arrow appears very long on the boot screen

3. after a while the screen is getting a little darker

4. Shortly after screen is getting darker, the lockscreen appears (with a nightly which works fine)

When i try it with a nightly with the boot loop i get also to 3. but instead showing the lockscreen it repeats showing 1.

Edit2: In normal CM lockscreen settings i did setup a google Reader link as linked app. The string of the google Reader link is very, very, very long. Probably this causes the problems which would match to this change in n106: http://review.cyanogenmod.com/#change,6132

I will be back when i removed the link and tried the newest nightly.

Edit3: This also did not help. I dont know, what to do next. Maybe someone can advise me. Last known working nighlty is n105. Deactivating the long google reader link dont helps for newer nighlties. Still getting this loop.

Edit4: It works now again with the latest nightly. verygreen - big big thanks for your hint - your work here is great. Solution was:

I have just deactivated the google reader link (defined as linked app in lock screen) in step Edit2 instead to delete it completely. In a second try i have set the linked app to a CM setting and deactivated it afterwards and now it boots properly in n111.

For me it looks like the feature added in n106 is very buggy. I dont know, how i can tell this the developer!!??
[Nook Color Android Development] dundun1701:
Anyone have problem with Market download? I cannot download any app from market. It keep saying that unable to download ( my wifi works fine).
[Nook Color Android Development] verygreen:
Glad it worked out in the end.

You can email the developer listed as author in the change you referenced.

Or you can register at that website and leave a negative review and state your problems there. that way both he and the person who approved the feature will both get an email about it (and possibly will include you for further testing when the fix is ready).
[Nook Color Android Development] DizzyDen:
I discovered the black screen update issue. Apparantly the same thing in you 1.1 script made it into the cm7 nightlies. Using your recovery and selecting Alt Boot... everything works as expected. Selecting Recovery I get black screen updates.

YCGIYWG
[Nook Color Android Development] Wifflepig:
I have to give big props to verygreen for making this happen. This is, by far, the easiest way to get a full-fledged android OS up and running without risking your NC.

I wouldn't mind increasing my system partition a bit, though. I tried with EASUS Partition Manager, but it won't let me resize any of the linux partitions (only BOOT and SDCARD). I would like to give some of my SDCARD space into the system (more room for apps and crap that I market DL).

Do I run into any risks flashing other ROMs in recovery mode? Is there a reason I can't just grab a Phiremod ROM zip and drop it in BOOT and do a reboot-to-recovery? Do my flashable zips need to be tweaked somehow, so the recovery/installer doesn't try writing it to the EMMC? I'm thinking things like UOT Kitchen's cooked up ZIPs, or flashing custom boot animations, etc. I get a little gunshy about flashing ZIPs and ROMs outside CM nightlies or gapps, in case there's some sort of special condition where these files might end up going into EMMC or something...
[Nook Color Android Development] verygreen:
Well, I did not get any input from anybody about possible sizing so I based it off the old nook layout. That could be changed if desired, I guess.

You can even partition (and format) the card beforehand and then do the install part and the installer would stick to the layout you created. Just use the flashed image as the baseline on top of which you create and format the extra partitions.

You can try to flash any ROms you like without any risks to EMMC.

The worst that would happen is a rom might be installed only half way because it was created in an incompatible manner.

Compatible manner is to emulate the CM7 updates as closely as possible - directory structure in the zip must reflect that of on the real device (aside from kernel and uRamdisk), no strange scripts that pull random archives from the zip and then try to unpack them by themselves and such.
[Nook Color Android Development] Wifflepig:
Thanks, verygreen - last question:

How would one reset battery stats with your installer/bootloader. With no interface to speak of (in recovery mode), is there some magic to it, or is there some adb command I can throw at the machine? Any help is appreciated.

edit: never mind -- i found an app for it on the Market, "Battery Recalibration" or some such.
[Nook Color Android Development] verygreen:
you can erase the /rom/battery.bin or whatever was the file name in adb, I guess.

You probably don't need to do it since modern nighties should know how to properly update it already I believe.
[Nook Color Android Development] DizzyDen:
If you want a larger system partition... the secret is to use Easus or Mini Tools partition manager and resize it BEFORE running it in the nook....

1. write image

2. resize the partition

3. put it in nook and let it run to create the other partitions

If I recall right from my doing this... you must keep the boot partition under 2 gig for it to boot in the nook.
[Nook Color Android Development] androidmonkey:
I followed the guide and have CM7 running great off my mSD card. How can I get phiremod running with this? What about the overclock kernel?
[Nook Color Android Development] Wifflepig:
Thanks, DizzyDen (and verygreen). Great answers. I appreciate the help.
[Nook Color Android Development] seclm193:
This worked perfectly. After this, how do you go about updating cm7m
[Nook Color Android Development] cybertimber2007:
I'm on VG v1.1 and CM7.0.2... If I wanted to update to one of the latest nightly, what do I need to do? Do I need to upgrade to VG1.3 and then latest nightly, or latest nightly and then VG 1.3?
[Nook Color Android Development] verygreen:
to installer 1.3, and then to the latest nightly.
[Nook Color Android Development] danbutter:
How is this setup different from standard android or even CM7 on emmc?

Is it this method of installing to SD card or is it CM7?

I'm trying to use file explorers, but none can change permissions to RW.

I thought that by running CM7 I already had root correct?

Also trying to work with brianf21 to figure out why his netflix fixer (changes build.prop) won't work. Any commands I type in via terminal emulator just say permission denied (are you root?).

Any ideas?

By far the easiest way to get CM7 on the uSD card...just trying to figure out why certain things don't work.
[Nook Color Android Development] verygreen:
nope. You get the same CM7 only on SD card.

To get root in terminal emulator, type su as the first thing

The prompt must change to "#" from "$".
[Nook Color Android Development] danbutter:
Doesn't work.

It just says Permission denied.

This isn't the first build I've had this issue with either.

I didn't do anything to terminal emulator, but what should it show when it starts up? Mine looks like this when I first start it up:

export PATH=/data/local/bin:$PATH

$ export PATH=/data/local/bin:$PATH

$

--------------------------------------EDIT----------------------------------------------

I updated to the newest RC and got root.

No idea what was going on that I didn't have it for the last two updates I did, but I have it now.
[Nook Color Android Development] philliyxx:
I'm having trouble getting into recovery to flash OC kernal. When I enter boot menu and choose SD-Recovery screen will just go black and it will never come up.

Same as if I reboot into recovery with the nook already on. Any suggestions?
[Nook Color Android Development] DizzyDen:
I copied the uRecImg and uRecRam to uAltImg and uAltRam and placed on uSD

Then

Press and hold Vol + and Vol - keys... power on... the boot menu will tell you booting into alternate... release the keys... you will see the penguin and the update process.

The black screen you are seeing is actually doing the update... you just don't see it.
[Nook Color Android Development] philliyxx:
Thanks man, got it installed.

I was thinking I would have to see a menu like CWM and go through menu's and choose flash .zip or whatever.
[Nook Color Android Development] hd2brick:
this is amazing, working flawlessly

used nightly 116 flashed kernel and gapps, ran app

used a micro usb to female usb, logitech k120 keyboard, and logitech m510 (not bluetooth !)
[Nook Color Android Development] AReynante:
How do I fix a card that I had used for this? I was using a 4g, switched to a 16g, and now my 4g card, after formatting only shows as 117mb available. Any ideas?
[Nook Color Android Development] dcharleyultra:
I think it's okay. Something similar happened to me. Try it and see.

Swyped from my Evo 4G using Tapatalk
[Nook Color Android Development] jacjar1:
use sd formatter it will get rid of the unseen partitions and give you back a full sized fat or fat 32 sd card...
[Nook Color Android Development] dc52317:
uboot.bin to stock?

I did not see any mention in the first post, but is there a way to boot to stock nook? Is there a uboot.bin file I need to install to make this an option?
[Nook Color Android Development] DizzyDen:
IF your using CM7 (the latest nightlies or 7.1.0RC1) you can power on... then press and hold "n" key to get the boot menu... then select EMMC... "Normal" and then boot.
[Nook Color Android Development] chumpster:
I don't see that option. Am I missing something? If I hold the "n", all I get the latest apps I used. I would be great if I could boot between EMMC and SD...
[Nook Color Android Development] wwejr4540:
What worked for me: hold down "n" button, power on and continue to hold "n" button until boot menu screen appears.
[Nook Color Android Development] dcharleyultra:
Power down NC.

Press power button until you see the "white power on quiver".

Immediately press n until you get the boot menu.

Swyped from my Evo 4G using Tapatalk
[Nook Color Android Development] chumpster:
Thanks for the replies. That worked. In the other post when it said turn device on I thought it meant fully booted up... that is just my lack of understanding...
[Nook Color Android Development] BJNK:
Hello .... I have tried searching but can't seem to find the answer to this problem.

I dl v1.3 and was able to get the SD card formatted and burned.

I dl CM 7.1 RC1 and put it on the disk. Booted up the NC and it appeared to install properly, it shut down when finished as per the instructions.

But now when I turn it on, it says loading and then goes into the linux shell and appears to have some error regarding the kernel (I cant read it as it scrolls to fast) and then says preparing to shutdown and then powers off. The screen is up for about 10 seconds.

The SD card after all this has a boot partition, a CM 7 partition, a 1GB partition and a 485mb partition when I look at it on my PC.

If I reboot the Nook without the SD card it loads the regular version normally.

Where have I gone wrong here?

Thanks
[Nook Color Android Development] dcharleyultra:
Did you initially put RC1 on the boot partition?

Swyped from my NookColor using Tapatalk
[Nook Color Android Development] BJNK:
EDIT: I Just want to say.. I am an idiot. I accidentally copied over the CM update for my Nexus S instead of the Nook.. LOL.

I reformatted the card and went through the process again and it works now!

Thanks for your help anyways!
[Nook Color Android Development] a4diziac:
I just wanted to say thanks! After an hour of messing with File Expert, I finally went to Root Explorer and was done in minutes. This worked perfectly. Thanks! :)
[Nook Color Android Development] pk74:
Feeling quite dull this morning...

bought a new NC yesterday (convinced local SM at Staples to take a 20% off coupon, woot!)...

Have a 2GB sd card. downloaded wnimage, downloaded generic-sdcard-v1.3.img.gz and extracted it. Used winimage to push generic-sdcard.img to the card, ejected it and reinserted it into my card reader, it has 4 files on it:

mlo

u-boot.bin

uImage

uRamdisk

downloaded and write cm_encore_full-121.zip to the root of the sd card, making 5 files there now. Ejected the card, put it in my powered down NC and turned it on...and it boots into stock.

Rebooted it, it went to stock. Gave it an angry look, it booted to stock.

What am i doing wrong? I thought it would boot from the sd card automatically the first time?

edit - tried two different known good SD cards (4gb and 2gb sandisk, one out of my phone), 2 different card readers with the same results..
[Nook Color Android Development] dcharleyultra:
With power off, hold down n key. (Do not release the n key until you see "Booting into recovery" under the Cyanogen Mod logo.)

Press the power key until you see the "white power on quiver" across the screen.

Immediately release the power key, and then immediately repress the key until you see "Booting into recovery".

Release power key and n key.

Once recovery shuts down the NC, power the NC up normally.
[Nook Color Android Development] jbinbi:
Ok. I have followed the steps to get cy7 up an going (cm703). have that, but don't have the apps showing up. can't figure out to get this to happen. have a thread going on andriodforums, and they have been very helpful in getting me to this point, but need some help.

i downloaded the cyanmod7 apps at the bottom of the wikipage gapps-..062311.zip, copied to sd card where I see the boot files etc, followed instructions for reboot into recovery mode, then reboot, but I see nothing for any apps. i click the little 4 square button on the bottom next to the browser icon, and nothing in there that wasn't from before.

I am not copying the files with the nc attached to my computer, i see that it gives me 2 disks, which when reading xda it says it should.

Any ideas on how to get it get me the apps? thanks.
[Nook Color Android Development] jbinbi:
update:

ok. in rom manger, updated, did a download, told me there was rc7.1, i downloaded, it pulled up the gapps. however, now it seems to be stuck in a loop where it tells me there is an update available. . says press ok to update rom to latest version. says rom addons, gapps, i check that box. gives me pre rom installation diaglog, wipe dalvik cache. i do that. dialog to reboot into clock recovery and contineu. i say ok. it reboots, but does nothing new, getting me back to same screen to say it has new rom available.

in other words, it isn't ever booting into recovery and doing the install.
[Nook Color Android Development] pk74:
All this did for me was power it down after I released the power button and pressed it again and held...
[Nook Color Android Development] dcharleyultra:
Did you have the n key pressed the entire time?

Edit: Which partition did you copy the ROM zip?

Swyped from my Evo 4G using Tapatalk
[Nook Color Android Development] pk74:
Yes, had the n key pressed the entire time..

I copied the rom to the only partition that my PC saw on the card, the same one with the 4 files that the img put..

EDIT - following the instructions here, http://xdaforums.com/showpost.php?p=11452450&postcount=19, I was able to make a bootable card...not sure I want to install it to emmc tho..but if it fails horribly, I can just failboot 8 times and go back to stock, right?