yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Hextall:
Is there anyway we can get a note in the title indicating when CWR is fixed (or that it needs fixing now)?

Putting this in the OP when most of us just check new posts is kind of hiding this important info.
[Nook Color Android Development] adma84:
I'm sure nemith will update the OP
[Nook Color Android Development] TheTodFather:
Chill hex! It's all good of course he will update when he gets the fix. He said ASAP. It's not nemiths fault. Don't shot the messanger dude!
[Nook Color Android Development] FletchF:
Can someone clarify: It's the ROM Manager implementation that's broken, not CWM itself right? So anyone who installs the CWM files in the OP using adb should be fine?
[Nook Color Android Development] bradasmith:
I had this problem as well, I reset my ROM to see if it was that, cleared cache, dalvik etc etc. To no avail.

Since I could not install anything from Market, I could not get to ROMManager, had to resort to the 'removeclockwork.zip' that was included in one of the recovery threads, this restored the stock recovery, relashed my ROM and now Market installs.
[Nook Color Android Development] davidukfl:
my market is also now not working. It starts downloading an app but then just stops. Thankfully i have applanet so I'm just using that for now

also i don't see version 3.0.0.5 in rom manager in alternate versions
[Nook Color Android Development] lafester:
If you read the new posts you would have seen it :p
[Nook Color Android Development] KitF:
This is correct.
[Nook Color Android Development] davidukfl:
any updates on this, or is there a way to easily flash the old version of CRW? I'd like to be able to download apps again from the market :cool:
[Nook Color Android Development] wpnyc2009:
not working on HC v4

I've tried manual and adb - no go!

Anyone get this to work on Honey Comb? How?

Thanks!
[Nook Color Android Development] mazook98:
does ANYONE have a working 3.0.0.6	they could provide an .img for? Help, pc borked, no adb access...

Sent from my PC36100
[Nook Color Android Development] dizx:
Couldn't do a proper search on xda app. Can someone tell me if this can be done through Terminal Emulator? Currently having problems with computer recognizing device via adb.
[Nook Color Android Development] adma84:
If what can be done? Manually flashing cwm?
[Nook Color Android Development] dizx:
Sorry, I meant if following the instructions to install the files manually as stated in the OP can be done via Terminal Emulator since I am having problems having my computer recognize the NC via adb.
[Nook Color Android Development] nemith:
Yes it can but you need to find another way to upload the files. You can mount your /sdcard to your compute and copy over the files and replace the 'adb push' commands with cp.

As far as your adb is concerned: have you set your adb_usb.ini?
[Nook Color Android Development] TheTodFather:
Again thank you nemith!

*edit...Omg i read the title and it said fixed,refreshed and it said broke. Thanks for caring enough to lend a hand.
[Nook Color Android Development] davidukfl:
whenever this is fully working, can it just be flashed over the top of my currently installed CRW? or should i remove CWR and then flash it?
[Nook Color Android Development] Snyperx:
nemith,

Hopefully you removed the download link form the main post???
[Nook Color Android Development] Homer_S_xda:
Should the original dev get with the person who provided the forked version and get it sorted out?

Homer
[Nook Color Android Development] eyecrispy:
just manually installed 3.0.0.9 and verified that i can boot straight into CWR and also go into CWR from ROM Manager. Thanks!
[Nook Color Android Development] davidukfl:
so can THIS version be installed from ROM manager right over 3.0.0.6?
[Nook Color Android Development] marclais:
fastboot

I have never messed with adb. Can I manually install cwm and the kernel with fastboot from my mac?
[Nook Color Android Development] crashdau:
Are we sure about this coz I've been flashing cm7 using 3.0.0.6 since you put the orig up and haven't had an issue?
[Nook Color Android Development] davidukfl:
also will this version fix the market download issue?
[Nook Color Android Development] nemith:
No. This is recovery. It has nothing to do with the market at all.
[Nook Color Android Development] nemith:
Yes. But if you want to work with ext4 filesystems you should manually update the kernel.

If you don't care about ext4 then just flash from rom manager.
[Nook Color Android Development] nemith:
No. No fastboot at all on this device.
[Nook Color Android Development] nemith:
You probably updated the kernel at some point to support it.
[Nook Color Android Development] davidukfl:
I and a couple of others haven't been able to install anything from the market since installing 3.0.0.6
[Nook Color Android Development] rainmaker002:
I flashed 3.0.0.9 through ROM Manager, and tried to do a backup. I got a "can't mount /data" error, though it backed up system/cache just fine. I have not seen that error before on previous versions.
[Nook Color Android Development] newellj79:
I'm still sort of a newibe. Can someone please help me with a few question. First of all I've been running cm7 over clocked for some time. This will be my first attempt at doing something with adb but I do have it setup right. 1) i seen that you have to install a kernel, can i still use my overclock kernel after that (r they even related?), 2) where do i put the two files once they are downloaded to push them with adb and which card my ext4 boot card or the one i use to store cm7 data., 3)where should i be at on the nook when i issue these commands via a command prompt on my pc?
[Nook Color Android Development] anurbanlegend:
Ok guys I posted this with the earlier 3.0.0.6 version and still have the same problem with this version. I've noticed a few others have posted the same issue but no tips on how to fix it...

Using the manual method to install and everything looks like it installs right but it NEVER boots into recovery. Can't do it from rom manager, can't do it from the reboot menu, can't do it with adb reboot recovery. No matter what I try I can not get it to boot into recovery mode. Anyone have any suggestions on how to get this fixed?? Thanks!
[Nook Color Android Development] wpnyc2009:
Working on Honey Comb?

Any one try?
[Nook Color Android Development] davidukfl:
I'm gonna try and install this when i get home. If it doesn't work, or my market still won't download I'll just be installing the old version as that seems to be the one that people have had most success with.

I only run the stock rom, and the only reason i need CWR is for the overclock kernel i installed, i don't plan on flashing custom roms or doing much else to it.
[Nook Color Android Development] JonFuego:
I am getting the same results.
[Nook Color Android Development] elwood1229:
Unfortunately, I have never done much with ADB and really don't understand it. I realize that means I am limited on a number of fronts working with Android. I installed it on my PC, used it once but am not sure even where to put the files on my PC so that they can be pushed to my NC. I searched but did not find simple instructions on this.

I am wondering though if the new version of CWM will be made into a flashable ROM that can be installed through CWM 3.0.0.6 as someone did when CWM 3.0.0.6 came out? That would be greatly appreciated among those of us who are ADB-challenged.

Edit: Alright, kept searching and I think I figured it out. CWM now shows 3.0.0.9 after pushing the new files. Is there a way to see whether the kernel actually updated? Thanks again.
[Nook Color Android Development] woot1524:
disregard. I fixed it by redoing the manual install as stated on the first page.

I am having this problem as well. I'm running nookie Froyo customized 0.6.7 (should I upgrade to 0.6.8? or is there still issues with Froyo and CWM) and I originally installed CWM 3.0.0.5. I both installed 3.0.0.9 using rom manager and the manual method (I used wireless adb but had no issue running the commands). I cannot get into recovery using rom manager, pwr+menu, or adb recovery.

Any help will be much thanked.
[Nook Color Android Development] eyecrispy:
Read the OP. He explains there.

Sent from my NookColor
[Nook Color Android Development] Hilbe:
I did a manual flash of 3.0.0.9 using your instructions. It worked, however ROM Manager still thinks I have 3.0.0.6. Any idea how to make ROM Manager not think I'm using some old recovery and popup the annoying upgrade message all the time?
[Nook Color Android Development] faceman66:
After being blasted for trying to explain what I thought the differences between the two nook devices listed in the ROM Manager list, can someone PLEASE explain what the differences are since there are still two devices to choose from?
[Nook Color Android Development] simon.ponder:
To affirm, flashed 9 over 6 through Rom Manager, booted into recovery from Rom Manager, backed up fine, and flashed CM7 nightly 11. No issues as of yet.
[Nook Color Android Development] eyeballer:
Is there a 1gb sdcard bootable CWM 3.0.0.9 image anywhere?
[Nook Color Android Development] painter_:
Rom Manager just informed me of an update to 3.0.1.0. What is new? I flashed it and and tested the nandroid, the backup said it was successful. I guess the ext4 Kernel in included. the backup was of CM7.

there was no errors in mounting anything like before. I was able to wipe both caches with out errors.
[Nook Color Android Development] davidukfl:
Updated to the new version from rom manager however market still isn't downloading anything.

Any ideas on what could be causing this? The market was working fine till I flashed the new cw recovery and kernel
[Nook Color Android Development] adma84:
Can I go back to using Dalingrins overclock kernels then if everything went ok?
[Nook Color Android Development] painter_:
What would a recovery; which operates at a much lower level then the OS; have to do with the market?

There is a fix for the market in the CM7 development thread. Search is your friend. Took me all of 30 seconds to find it.

http://xdaforums.com/showpost.php?p=11683478&postcount=285

Even though this fix is for CM7 it should fix market issues for whatever ROM you are running.
[Nook Color Android Development] dizx:
I've followed instructions I've read to a "t", but adb still won't recognize the NC. I've followed several links on the nookdevs site, but still a no go. Windows keeps overriding drivers.

Any tips? Also, can you clarify what you mean by have I set up my usb.ini specifically?
[Nook Color Android Development] newellj79:
U should still b overclocked.
[Nook Color Android Development] painter_:
Recovery uses a diffrent kernel then your Android OS. The Kernel refered to this this thread is the recovery kernel, not the kernel that Android uses when you boot normally.
[Nook Color Android Development] TJNooker:
So far so good

I manually installed CWM 3.0.0.9 this afternoon and so far everything seems to be functioning as it should. Even though RomManager still says 3.0.0.5, when I boot into recovery it says 3.0.0.9 just like it should. Market also appears to be functioning normally. To the OP, thanks for staying on top of this.
[Nook Color Android Development] jdellingson7:
Don't know if this is your issue but i had trouble with adb recognizing my nook too. I finally realized it was because my settings on screen timeout was at minute. My nook would not connect unless it was awake so i set my screen timeout to 10 minutes and my problem was solved.
[Nook Color Android Development] jdellingson7:
Ok So i ran the commands in adb and pushed kernel and new version but think i might have screwed up by flashing the newest recovery in Rom Manager. Now when i boot into recovery i'm on version 3.0.1.0. Is this ok? Also the only way i'm able to access recovery is through Rom Manager and three finger salute. Does that sound right? I'm on Phiremod v4 for Rom
[Nook Color Android Development] davidukfl:
im on 2.1 so i don't have a google services framework. Also i know I'm not the only one having this issue.

http://xdaforums.com/showthread.php?p=11742146#post11742146

I just cleared dalvik cache again and reflashed the OC kernel. Also uninstalled all market updates and cleared data. We'll see what happens
[Nook Color Android Development] davidukfl:
update: worked
[Nook Color Android Development] nemith:
This has nothing to do with the market. There may have been some changes in CM7 that broke that.
[Nook Color Android Development] nemith:
Old is old. Don't use it.
[Nook Color Android Development] nemith:
There are two kernels. uRecImg and uImage.

uRecImg is used for recovery only and uImage is used for your current rom only.

You shouldn't use a overclocked image for your recovery :(
[Nook Color Android Development] faceman66:
I appreciate that, but it doesn't explain anything. It also doesn't help those folks that had issues using one or the other and had to find out the hard way which one to use for their current ROM. Unless v3.0.0.9 corrected all those fluke issues and there is now no reason to ever use (old) in which case I don't understand why it is still included.

Since it is still included I am forced to believe there is a reason for it, and thus I am still wondering who to ask for an explanation of the two.

(Sorry if this is coming across rude or trite, I am just trying to understand this piece and how it plays with the rest of the puzzle)
[Nook Color Android Development] nemith:
Read the code and follow the commits if you really want to know.

I'll give you a hint: It has to do with device naming.
[Nook Color Android Development] cmstlist:
Has a bootable SD been released yet for this recovery? I'd like to get the SD card prepared in advance of receiving my NC.
[Nook Color Android Development] nemith:
Not that I am aware of but maintainers of those bootable SD are recommended to upgrade their images as well!
[Nook Color Android Development] faceman66:
Thanks but no thanks. I was trying to act as a buffer between the smart coders and the dumb users since I am dumb enough to get myself in trouble but smart enough to get out of it, but I can't decipher a simple answer from the code/commits.

I am running CM7 and thus have always used the 'Nook Color' device in the list and have had not problems updating my CWR via ROM Manager after initially manually installing v3.0.0.6; however the folks I work with on other forums and here that are running any ext3 based ROM had to use the 'Nook Color (old)' in order for CWR to operate properly. As such they are nervous about the later releases of CWR and are waiting for things to settle down. Can you tell me if a users current rom (ext3 v. ext4) has anything to do with which device they should be selecting?

I see there is a v3.0.1.0 now, which coincidentally matches the version of ROM Manager (hopefully we can now avoid the confusion that had caused for some folks). I also see that it's still a manual install, but I was able to update via ROM Manager without issue. Interestingly, as I looked back over my notes, when I manually installed the v3.0.0.6 I was never able to get the kernel to install but I can't read my notes as to the error I had gotten. I meant to post and ask but held off since things in v3.0.0.6 exploded anyway... and since then I forgot about it and have updated to 9 and now 10. With every version I have been able to use CWR, create and restore backups, etc... all without the kernel you gave in the OP, am i just a lucky user in this regard?

Edit - although I did do the flashable cwr 3.0.0.6 that was posted and I think that actually did the kernel, so forget that question.
[Nook Color Android Development] FletchF:
This will undoubtedly cause greater confusion. :P
[Nook Color Android Development] Chahk:
Could you please update the OP with instructions on how to fix the recovery that's been blown away by the "Format Boot" option of an older CWR? I did that right after first rooting my NC way back, and have not been able to get it to boot into recovery without using an SD Card image.
[Nook Color Android Development] cmstlist:
Okay thanks. So once we have a universal bootable SD, I figured I'd use this to backup my stock Nook firmware, then wipe and install Honeycomb on internal. Will keep watching for an update.
[Nook Color Android Development] lafester:
you take notes? :p

if people are seriously getting confused between clockwork and rom manager they need to SLOW DOWN and read for awhile before they start flashing anything. if not, big deal... you can't brick a nook.
[Nook Color Android Development] newellj79:
Wow... faceman is just trying to help people out. In fact he and his tutorials have helped me a few times.
[Nook Color Android Development] nemith:
Cause you are lazy read the front page but I will say it one more freaking time.

DO NOT USE "NOOKCOLOR (OLD)"!

I don't care about the silly thoughts and reasoning you have in your head on why it's still in the list.

Ext3 and Ext4 DO NOT MATTER on 3.0.0.9 and above!
[Nook Color Android Development] nemith:
No. This post isn't "I did something retarded in CWM, please fix it"
[Nook Color Android Development] faceman66:
Thanks for proving everything I was trying NOT to think about you. You won't be bothered by me anymore so you can chalk this up as a "Win" for yourself, i concede.

ps - The fact that the OP was edited to reflect my question and happened after I asked the question for the third or fourth time without an answer, does not exactly make me lazy, but despite my repeated viewing of the OP to follow along with the changes, I DID miss the recent change that included an answer, thank you for posting it.
[Nook Color Android Development] nemith:
Thats all that I could ever want :)

On a more serious note: Trying to repsond to everyone's post and keep up with th e OP is not the easiest of tasks. When someone demands changes it really doesn't sit with me well.

Feel free to take my free customer satisfaction survey! http://www.surveymonkey.com/s/WPWTVCC
[Nook Color Android Development] Dahsar:
Hey I updated rom manager through the market and its giving the correct version number so all I need to do is update the kernal manually now
[Nook Color Android Development] nemith:
Correct! :)
[Nook Color Android Development] Nanan00:
Rom manager still shows 3.0.0.6 as the latest version... Worst app ever, it sucks seriously...
[Nook Color Android Development] Dahsar:
Rude
[Nook Color Android Development] nemith:
You can have a full refund. RomManager is just a nice way to install stuff, you CAN do everything manually.

I would like to also add that RomManager was really designed for a classic Android phone. The way the NookColor operates and works is nearly completely different.

So adding support while still not breaking other phones has been difficult and requires some major rewriting. So although it's not perfect it's better than nothing.
[Nook Color Android Development] jstiel:
It's a great app!
[Nook Color Android Development] 360Razir:
Amazing work by the CWM crew for their hard work on it for the NC. Thrilled the team is working on it at all for this platform.

Completely agree.
[Nook Color Android Development] bratliff:
That's the great thing about android. You don't like it, uninstall and move on. Of course posting stuff like this always helps out..:mad:
[Nook Color Android Development] rainmaker002:
So I flashed 3.0.1.0 through ROM Manager, and I get the following messages while CWM is loading:

C:Can't mount /cache/recovery/command

C:Can't mount /cache/recovery/log

C:Can't open /cache/recovery/log

C:Can't mount /cache/recovery/last_log

C:Can't open /cache/recovery/last_log

When I try to manually mount /cache under Mounts and Storage Menu I get:

Error mounting /cache!

Ditto on /data

Error mounting /data!

When trying to run a backup, boot and system go fine but when it gets to backing up data I get:

Backing up data...

Can't mount /data!

C:Can't mount /cache/recovery/log

C:Can't open /cache/recovery/log

C:Can't mount /cache/recovery/last_log

C:Can't open /cache/recovery/last_log

I'm a little hesitant to try flashing a new nightly without a backup, also I'm worried that if CWM isn't mounting properly flashing might bork the existing install. Any suggestions?

minor edit: I had the same issue with 3.0.0.9 flashed through ROM Manager
[Nook Color Android Development] nemith:
Read the OP on how to grab a recovery.log. I can't even begin to guess without that.

Also need to know what rom you are running.
[Nook Color Android Development] KitF:
Please read the OP, you need to install the kernel from the OP manually to be able to mount partitions
[Galaxy S I9000 Q&A, Help & Troubleshooting] DennisDroid:
Hi Guys,

I'm looking for the best configuration for my galaxy s. I flashed the Vodoo Kernel 5.4.1 Stable from the officiel Site but Quadrant said my galaxy s has 999 Points o_O ..

How can i take the most points of my galaxy s?

Which Rom is the best? Which Kernel is the best?

Thanks for your help !
[Galaxy S I9000 Q&A, Help & Troubleshooting] Daneshm90:
My current configuration has 10,000 points in quadrant.

But it'll cost you $100

Why ? Cuz #stupidity-costs :p
[Galaxy S I9000 Q&A, Help & Troubleshooting] franklin01:
Quadrant benchmark does not says "real" scores...

Try things instead of relying on benchmarks.

A good start would be to run a recent rom (android 2.2.1 like JS5), something light if you want speed (like essential rom or doc kitchen if you want more stuff in it). About kernels some of them support OC/UV (like hardcore kernel) also ONE nand kernel are very smooth (but can be problematic if you plan to get thousands of app...).

So if you want real speed I would say Essential rom + trasig kernel (one nand).

If you want something fast and useful, go for doc kitchen rom and K13C kernel or laststufo super optimized.

Note:

Before flashing your final rom, make a clean flash with repartition using odin.
[Galaxy S I9000 Q&A, Help & Troubleshooting] dcarr622:
The best configuration is the one that you like best and works the best for what you want to do.

For me, that's either Doc's ROM with hardcore kernel or CM7 if I feel like it.

Thread reported, this is not dev, pointless discussion.

There is no BEST ROM
[Galaxy S I9000 Q&A, Help & Troubleshooting] gbohm:
this is not a post for android development!!

quadrant doesn't mean anything deinstall it!!! if it is running smooth be happy if it lags -> ext 4 lagfix

best config for me cm7

cm7 ftw

samsung galaxy s cm7 :-)

archos a101 urukdroid :-)

desire hd stock 2.2.1 :-(
[Galaxy S I9000 Q&A, Help & Troubleshooting] DennisDroid:
But CM7 for Galaxy S is beta and not stable?
[Galaxy S I9000 Q&A, Help & Troubleshooting] gbohm:
so what works super smooth would never go back i can live with those small bucks

why do you need a high quadrant? if it is just for your friends as a "contest" u could use some ext2 loops but it will just fake your results

cm7 ftw

samsung galaxy s cm7 :-)

archos a101 urukdroid :-)

desire hd stock 2.2.1 :-(
[Galaxy S I9000 Q&A, Help & Troubleshooting] Dark3n:
Move this to Questions section, so everyone can post the version he is using as the best configuration :D.
[Galaxy S I9000 Q&A, Help & Troubleshooting] schiphol:
+1 this thread doesn't belong here and ought to be moved
[G2 and Desire Z General] Chinam4n:
I've been wanting to update to Gingerbread for a while now. I see that theres 2 popular ROMs based off Gingerbread. I just wanted to see some pros and cons about each ROM before actually flashing to it. So if you would please give me some feedback :)
[G2 and Desire Z General] Utorrent76:
Not much of a difference, GingerVillan is based off of CM after all so they're pretty close. The one con that bothered me the most about GV was the constant random reboots. So as soon as CM 7 rc 1 was released I switched. Couldn't be happier. I've had no issues with this rom and its currently running problem free. For now.