yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] fattire:
clockworkmod v5.5.0.4-- HIGHLY EXPERIMENTAL

So did you know that aside from building cyanogenmod 9, you're also building clockworkmod? It's true. The recovery is part of the source code. After you build, it's in $OUT, in the recovery directory.

Now before you get all excited, I had to do a couple things to get it to work insofar as it IS working, so it's not exactly ready for prime-time, and your build at home ain't gonna work right out of the box.

But I figured I'd share what I have.

I was hesitant to do so at first, but nemith insisted and insisted and ultimately talked me into it.

** THIS IS EXPERIMENTAL. USE AT YOUR OWN RISK. DO NOT USE THIS FOR FLASHING STOCK, AS IT IS LIKELY NOT TO WORK. USING THIS RECOVERY IMAGE MAY CAUSE TERRIBLE THINGS TO HAPPEN, AND YOU ACCEPT ALL RESPONSIBILITY SHOULD THAT OCCUR. TERRIBLE THINGS INCLUDE SLOW PAINFUL DEATH OF THOSE YOU LOVE THE MOST, NOT THAT WE ALL DON'T DIE EVENTUALLY. YOU MAY ALSO COME DOWN WITH DROPSY, GILL ROT, COTTONMOUTH, AND/OR "THE ICK". LIFE WITHOUT A WORKING RECOVERY IS A SAD, LONELY BATAAN-LIKE MARCH TOWARDS INFINITE SADNESS **

If you're not sure how to use this, then maybe you shouldn't try. It goes in /boot though and should work with your current uRecImg. You should keep a backup of your recovery as well as this version is not fit for any purpose.

Again, unlike the cwm you've used previously,

this can't be used to install stock

as far as I can tell. Some stuff will have to be updated. It may not be good for installing anything actually. It's just for testing and such, and should be replaced with your original uRecRam when you are finished playing, which I do not recommend you do.

Thanks to scotty2 and racks11479 for testing. And to nemith for his endless trademark warm support ;)

uRecRam (aka CWM-based Recovery v5.5.0.4)
[Nook Color Android Development] crnkoj:
hey zequav im trying to get this party going on a gentoo build aswell, might you have some advice/links as to how to make it work? Im on a 64bit build with multilib enabled and with the ~amd64 keyword, i even used the crossdev toolchain a bit for some gentoo arm compiling. id really appreciate some input, thanks

my thoughts for this until now:

1. do i really need sun-java6-jdk or can i use icedtea6/7 ?

2. i cant seem to find a few of the libs (libesd0 , the sepcific zliblg) and packages (git-core is probably just git i figured and gnupg is it the app-vim or app-crypt?)

3. do i need to use gcc 4.3 or can i use a newer version 4.5/4.6

thanks again

edit aswell as build-essentials cant really decide which would fit in gentoo to it.

another edit, i probably need the 32bit sun-java6-jdk or will the 64bit one suffice aswell?

more edits, one needs to have python 2.7 selected for repo to work
[Nook Color Android Development] jschill31:
Hello,

This is actually happening to most of us at one time or another and easy to fix. One thing that will help you is to not have your USB plugged in, this is why it seems like it continues to reboot. For some reason one of the last builds erases the recovery, you just need to reload it. Hopefully you have a rom on a SD card like maybe Gingerbread or you may have a Clockwork Recovery SD card, either will work fine. If you have a Clockwork Recovery SD card, then boot from SD card into Clockwork and revive one of your saves. If you have a rom on a SD card, boot from SD card into your OS and open Rom Manager. Use Rom Manager to re-flash Clockwork, then boot into recovery. Remove your bootable SD card and insert your normal one, you may have to mount SD card. Now you are golden and can either re-flash a zip or revive one of your saves. If you do not have either a bootable SD card with a OS install or a Clockwork bootable SD card just follow the directions associated with creating one found in the forums.

Cheers
[Nook Color Android Development] crnkoj:
one more thing is there an irc channel where you guys gather and talk about it?
[Nook Color Android Development] newellj79:
Freenode, #nookcolor
[Nook Color Android Development] Homer_S_xda:
As always, you guys rock. If I could make a suggestion which is way above my pay grade. If while you guys were tweaking CWR, if it supported flash to an SDcard out of the box that would rock. Maybe with a parameter file or something.

Just thinking,

Homer
[Nook Color Android Development] andrewddickey:
Also tried changing git:// to http:// and no luck. Still same result.

Let it repo sync from 6:30pm last night until 9:30am this morning, still stuck at 99%

I am.....the 99 percent.

Read somewhere about using clone as a work around?
[Nook Color Android Development] zequav:
1. You do need sun-jdk. 64 bit is ok, just emerge sun-jdk (it has fetch restrictions).

2. You need app-crypt/gnupg. Don't install libesd, doesn't seem to be really needed. I use zlib-1.2.5.1-r2.

3. GCC 4.6.2 is ok too.

4. build-essentials is ubuntu-specific. We already have all the build-essentials we need. It's gentoo after all ;)

5. Python 2.7 is also ok.

Basically, the only things I emerged that I didn't have already in my system were pngcrush, gnupg, schedtool and sun-jdk. I didn't have to install different versions of any package that I already had in my system.

Oh, I had to export ANDROID_HAVA_HOME=/opt/sun-jdk-1.6.0.29/

HTH.

---------- Post added at 06:09 PM ---------- Previous post was at 06:00 PM ----------

BTW, does anybody else have repo sync hanging at 99% (242/244, or 241/243, or 243/245) almost ALL THE TIME? I usually have to retry the sync many times before I get synced. Different -jX don't help. Is it repo's fault? Python's fault? Some other package's version fault? Saturated server? PEBKAC?
[Nook Color Android Development] cchant:
I'm getting a lot of the following errors. Maybe something up with git?

Fetching projects: 94% (230/244) fatal: The remote end hung up unexpectedly

Fetching projects: 99% (242/244) fatal: The remote end hung up unexpectedly
[Nook Color Android Development] andrewddickey:
I was getting tons of those yesterday.

Haven't tried to sync today.
[Nook Color Android Development] zequav:
Looking back a couple of pages... many people with similar problems...

I'm trying syncing from scratch, after removing everything. Luckily I have a University connection, it'll take just a couple of minutes :P
[Nook Color Android Development] mrapollinax:
I was getting the "remote end hung up" errors yesterday as well. Just went with a sync with a "-j4" modifier. Took a bit longer but didn't error out. Built this morning with a new snapshot.
[Nook Color Android Development] HacDan:
I believe it's a problem with github, but you're definitely not doing anything wrong. The problem is wide-spread.

---------- Post added at 01:19 PM ---------- Previous post was at 01:10 PM ----------

No worries, issue now has a work-around. To fix the issue, you'll obviously have to flash back to ICS, then flash gapps. After flashing gapps, you'll need to mount /system in clockwork recovery.

Then

adb shell
cd /system/app/
rm OneTimeInitializer.apk

Reboot and things should work just fine. If not, post back or try out IRC again if you're feeling really adventurous.
[Nook Color Android Development] jschill31:
[/COLOR]

No worries, issue now has a work-around. To fix the issue, you'll obviously have to flash back to ICS, then flash gapps. After flashing gapps, you'll need to mount /system in clockwork recovery.

Then

adb shell
cd /system/app/
rm OneTimeInitializer.apk

Reboot and things should work just fine. If not, post back or try out IRC again if you're feeling really adventurous.[/QUOTE]

I saw you in there last night, just have no idea how to communicate.:) Maybe I will have some time after my son goes to sleep tonight to learn how IRC works...I am sure it is not that difficult. Back on topic, your fix above could actually be performed many ways depending on if the user is booted into the OS or Clockwork. Your fix suggests that the initial "Google Android" setup is conflicting with the launcher, is this a correct understanding?

Cheers
[Nook Color Android Development] botossi:
+1! Re did everything a couple of times and same error... good to know that is something wrong with github and not the instructions! Well, let sit and wait! Thanks for the devs for such work and to make us get out of our shells and start doing something called LEARN! :D
[Nook Color Android Development] foltz61:
I was getting the same errors at the same spot also. I wiped out everything and started over. Repo Sync completed.
[Nook Color Android Development] HacDan:
You actually cannot perform the same fix while booted into the OS, at least without clearing dalvik cache.

In regards to removing the OneTimeInitialization apk, I've wiped my nook twice now, flashed my compiled zip, flashed gapps, removed the OneTimeInitialization.apk and each time I was greeted with the setup screen. I'll be honest I don't know what that apk does, but it doesn't seem to be needed to complete 'first boot'.

It's not conflicting with the launcher per say, it is creating a dex file in dalvik-cache that is causing issues. Of course this is all on the assumption that you're experiencing the same problem as I am and a few others. And it's def. not a fix.
[Nook Color Android Development] wakeboarder8156:
7.

Type lunch. You should see a list of devices, including something like cm-encore-userdebug Select it by typing its number.

Helpful Tip! If you get a command not found error for lunch, be sure you’ve done the “. build/envsetup.sh” command as described in the regular instructions.

i've done everything up to this step but mine will not build or anything...it comes up with a file or directory doesn't exist or something, im currently in the middle of repo so i can't type the exact feed back it gives me. Just was wondering if i missed something.

After many hours of doing everything i can think of, im throwin in the towel!!

I appreciate everything the devs do a lot more now!!!!!

Keep up the good work and i will be patiently waiting for a final build!
[Nook Color Android Development] jschill31:
+1, "work-around" would have been a better word choice on my behalf than fix...and yes this is exactly what I am experiencing as well. As for removing the OneTimeInitialization.apk what I was meaning was a user could remove it after first boot/setup but before reboot but from what you are saying it is not needed anyway. Once removed does Trebruchet survive reboot? Also why is there two to begin with? I am going to strip the non CM one from my build just so I don't have to keep choosing 1 or the other.

On another note, has anyone figured out what is deleting Clockwork when switching from the ICS build back to CM7?

Cheers

---------- Post added at 02:44 PM ---------- Previous post was at 02:33 PM ----------

Hello,

Make sure you are executing from ~/android/system/ instead of somewhere else.

Cheers
[Nook Color Android Development] fattire:
Good news. As nemith's changes to the build have been merged into mainline cm9, there's no need for 3 of the 4 hand-done "git-fetch"es..

and the build gets that much simpler..

Updating the walkthrough now..
[Nook Color Android Development] wakeboarder8156:
It worked!!! Thank you!

It worked but now the nook isnt under the list and it won't build. this is getting frustrating
[Nook Color Android Development] HacDan:
Yes, you could remove it after, but as you mentioned, no need to, might as well do it all during installation. If I get ambitious maybe I'll make up a gapps pack with-out it.

Trebuchet, along with every other apk, has worked just fine for me after many reboots. And by many I mean 10+ so far. YMMV thought
[Nook Color Android Development] hazridi:
I'm amazed at how much better the CM9 I built is compared to the posted zip. It's pretty much usable as a daily driver at this point.
[Nook Color Android Development] gbohm:
it is great to hear about the progress sadly i only have a ssd in my laptop so not enough space to have more source on it than now....

i have 4.0 on my sgs2 and on my nexus i think even if both phones are technically more advanced the nook is running ics just fine :-)
[Nook Color Android Development] Nburnes:
I have actually known about this, and have been looking into how to get it working myself since basically 5.0.x.x sources where pushed. Was looking into this.

All because I saw that awesome "Rainbow Recovery" on someones twitter.

Edit: Clockworkmod Fabulous!
[Nook Color Android Development] fattire:
Yup, rainbow recovery (not to be confused with this one) was the brilliant work of Nathan G over at unstable apps, maker of the koush head app.
[Nook Color Android Development] newellj79:
For those having trouble with sync hanging, use system monitor to kill any python still up and then sync with -j4. I haven't had a problem in a couple weeks now.
[Nook Color Android Development] zequav:
No luck. As I said before I've tried a lot of -jX; always getting "fatal: The remote end hung up unexpectedly" and stuck at 242/244.

With -j1 I can see that the one that "hungs unexpectedly" is 235/244 (error: Cannot fetch CyanogenMod/android_prebuilt).
[Nook Color Android Development] fattire:
it's been confirmed that github is having some issues.

Another way to see repo sync progress:

repo --trace sync -j16
[Nook Color Android Development] saulhaul:
So i feel like a total "copy and paste" rom builder.. lol. But I'm having trouble initializing the repository. When I run the "repo init -u git://github.com/CyanogenMod/android.git -b ics" command I get an error:

jason@Jasons-Laptop:~/android/system$ repo init -u git://github.com/CyanogenMod/android.git -b ics

Traceback (most recent call last):

File "/home/jason/android/system/.repo/repo/main.py", line 366, in <module>

_Main(sys.argv[1:])

File "/home/jason/android/system/.repo/repo/main.py", line 346, in _Main

result = repo._Run(argv) or 0

File "/home/jason/android/system/.repo/repo/main.py", line 137, in _Run

result = cmd.Execute(copts, cargs)

File "/home/jason/android/system/.repo/repo/subcmds/init.py", line 285, in Execute

self._LinkManifest(opt.manifest_name)

File "/home/jason/android/system/.repo/repo/subcmds/init.py", line 173, in _LinkManifest

self.manifest.Link(name)

File "/home/jason/android/system/.repo/repo/manifest_xml.py", line 102, in Link

self.Override(name)

File "/home/jason/android/system/.repo/repo/manifest_xml.py", line 95, in Override

self._Load()

File "/home/jason/android/system/.repo/repo/manifest_xml.py", line 262, in _Load

self._ParseManifest(False)

File "/home/jason/android/system/.repo/repo/manifest_xml.py", line 273, in _ParseManifest

root = xml.dom.minidom.parse(self.manifestFile)

File "/usr/lib/python2.7/xml/dom/minidom.py", line 1914, in parse

return expatbuilder.parse(file)

File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 924, in parse

result = builder.parseFile(fp)

File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 207, in parseFile

parser.Parse(buffer, 0)

xml.parsers.expat.ExpatError: XML or text declaration not at start of entity: line 1, column 4

After first downloading the "make executable the "repo" binary" i restarted my computer and accidentally ran the above "repo init" command from the /home directory instead of the /android/system directory and but it actually ran and didn't give me the above error. I'm not sure if i messed something up or not.

Any help? I really need to figure out what I'm doing so I feel less stupid about this. lol
[Nook Color Android Development] fattire:
all the stuff about xml and parsing and such makes me think that there are extra characters or something in your local_manifest.xml file..

check it out, clean it up, and try it again...
[Nook Color Android Development] fjevel:
Have you followed the URL and copied the

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<!-- note: no longer need to replace CM9 Trebuchet launcher with AOSP's Launcher 2 -->

<remote name = "gh"
fetch="git://github.com/" />

<project path="device/bn/encore"
name="fat-tire/android_device_bn_encore"
remote="gh"
revision="ics"/>

</manifest>

into the correct file? Looks like it's complaining about the content of the file.

-KJ
[Nook Color Android Development] J-ROCK:
I cant get ADB to work is there a work around for step 5?

Next, install the proprietary files per the original instructions and run the ./setup-makefiles.sh script in android/system/device/bn/encore. (if that doesn’t work for some reason, try typing add_lunch_combo cm_encore-userdebug manually.
[Nook Color Android Development] inportb:
If you already have those files, just copy them into place. There's also another file to be created, and a script to be run afterwards. See what extract-files.sh does...
[Nook Color Android Development] 911jason:
Is there a way in this build process that I can remove apps that I don't want and add in apps that I do want to save on the re-install process after every flash?

For instance, can I get rid of all launcher apps and put in ADW EX? Can I throw in my favorite reader apps etc?
[Nook Color Android Development] inportb:
You could just modify the update.zip when it's ready, and re-sign it if you want to. But keep in mind that it all gets installed to /system.
[Nook Color Android Development] roger_n:
Hey guys I have a Gapps zipfile that I stripped the OneTimeInitializer.apk if you think it will help try it out. I haven't experienced the issue myself because I'm currently on CM7 waiting for the repo sync issue to get resolved. I cannot verify this fixes the issue a couple of you are having. I'm just trying to be helpful.

http://dl.dropbox.com/u/55126518/gapps-ics-20111125-2-OTI_Removed.zip

MD5SUM:

d13c8e67b01eb88c81b8500d52164505 gapps-ics-20111125-2-OTI_Removed.zip

Roger:cool:
[Nook Color Android Development] dascud:
I had the same problem. Couldnt get my mandriva box to get adb working with Nook Color no matter what I did. I just "pulled" the required files off the Nook and copied them into the correct folder ~/android/system/vendor/bn/encore/proprietary

Here is the link to the files. The archive already contains the proprietary folder so extract it at ~/android/system/vendor/bn/encore/

http://dl.dropbox.com/u/16190398/proprietary.zip

Next open the extract.sh file and comment out all the lines starting with adb pull as you have already copied the files over.

Just run extract.sh and do a sanity check that the files are correctly created e.g. device-vendor-blobs.mk etc.

HTH.
[Nook Color Android Development] saulhaul:
Thanks. That did it. I guess I'm not the "copy and paste" rom builder i thought I was.
[Nook Color Android Development] fattire:
Hah! :)

(Thissentenceaddsnothing.)
[Nook Color Android Development] fahadayaz:
Unfortunately, I don't have a backup as it was meant to backup before flashing. The problem is that it didn't even get into recovery, so it couldn't make a backup.
[Nook Color Android Development] roger_n:
Fattire, Do you know of a link that shows the status of the github server that is if one exist? I've been getting the dreaded "fatal: The remote end hung up unexpectedly" all day, or the only way is to keep trying "repo sync"?

Roger:cool:
[Nook Color Android Development] 911jason:
THIS THREAD

is probably the reason GIT is having so many problems! :D

I just tried to sync and it crashed at 37%, so I retried at -j1 and it got to 91% before crashing again. It's really frustrating when you're trying to learn and this keeps happening, because it makes you doubt yourself and wonder if the problem is from something you did wrong.
[Nook Color Android Development] roger_n:
Hmm, you may be correct github is getting hammered by everyone trying to syn. I hope that's not the reason I hope its a little more robust. Anyway mine hangs at 93% and fails at 99%.

Roger:cool:
[Nook Color Android Development] Bawb3:
I've found that if your repo sync seems like its stopped and hanging- just wait and eventually it will get through and finish the sync, it just takes forever.

Fattire I'm going to need some more help after I get back in town to my build machine. I've been out of town itching to get this stupid thing working :)
[Nook Color Android Development] 911jason:
I don't think most of us are quitting the sync, it's failing and ending itself.
[Nook Color Android Development] oppy:
Another thing has me confused - should a repo sync change the contents of local_manifest.xml? I've had the sync issues others are having, and, in the process of trying to figure it out, I took a look at the file and it was completely different from what was pasted in originally. If I changed it back I got a bunch of sync errors. I went so far as wiping everything and starting over and the same thing happens. Any ideas?
[Nook Color Android Development] Razor1973:
I saw a few people complaining about WiFi not connecting and I am having the same problem connecting to mine with WPA2-Personal/AES type security. It saves the network, but never connects to it. I can however connect to open networks. I tried using a static IP as someone suggested, but still no luck.
[Nook Color Android Development] Dj-Gutz:
can anyone compile for me fuse.ko compatible with our kernel?

I'm trying to get ntfs working and I can't find a compatible module for the nook ( don't have a build machine atm )

the closest I could find ( 2.6.32.9 ) is still not compatible , after insmod

<3>fuse: version magic '2.6.32.9 SMP preempt mod_unload modversions ARMv7 ' shou
ld be '2.6.32.9 preempt mod_unload ARMv7 '

also tried Drive Mount - and it says it can't mount :)

Other devices for reference ,

GS2 - http://xdaforums.com/showthread.php?p=15167790

Xoom - http://xdaforums.com/showthread.php?t=1020174
[Nook Color Android Development] sednafx:
Set router to wireless g only.
[Nook Color Android Development] wakeboarder8156:
when i type the "brunch" command the encore device isn't in the list... what do i do or need to do in order for it to show up. It appeared when i typed the lunch command.

uh oh!!!

system/core/toolbox/Android.mk:98: warning: overriding commands for target `out/target/product/generic/system/bin/lsof'

build/core/base_rules.mk:523: warning: ignoring old commands for target `out/target/product/generic/system/bin/lsof'

make: *** No rule to make target `bacon'. Stop.
[Nook Color Android Development] HacDan:
You'll need to type brunch encore. Not sure why that's not in the document. The point of brunch is to skip the list and start compiling immediately.
[Nook Color Android Development] crnkoj:
Thanks for the input, guess i had all but the sun jdk eselected :) i do have to wait for repo sync to work again since we all have the same problem. I will however try with icedtea first :D
[Nook Color Android Development] fattire:
So two ideas for fix while github gets its act together. The first is to temporarily replace cm's prebuilt project with AOSP's prebuilt project. Add this to local_manifest.xml (for the time being):

<remove-project name="CyanogenMod/android_prebuilt"/>
<project path="prebuilt" name="platform/prebuilt"
remote="aosp" revision="refs/tags/android-4.0.3_r1"/>

It goes somewhere in the middle where the other similar stuff goes.

Perhaps a better suggestion I'll quote verbatim from a PM I got:

Thanks, Drakmors!
[Nook Color Android Development] zequav:
Your workaround works. Drakmors's solution doesn't for me (at least as it is), since prebuilt.git/config is overwritten during a repo sync (so https:// automagically becomes git:// again during sync).
[Nook Color Android Development] fattire:
Ah, and he updated me...

Thank you!
[Nook Color Android Development] MrColdbird:
I hope its okay to ask, but fattire is it true that you got audio running?
[Nook Color Android Development] rabshear:
Kept posting wrong stuff. Too early and not enough coffee yet.
[Nook Color Android Development] roger_n:
Worked for me.
[Nook Color Android Development] jschill31:
Hello,

You need to execute the lunch command from ~/android/system/ all other locations will error.

cheers