Guide to installing honeycomb? - Nook Color General

Sorry guys kinda new to this. Is there a step by step for installing honeycomb internally? Thanks
Sent from my SCH-I500 using XDA App

If you're not sure, do it from sd.
Sent from my NookColor

I really Just need a guide on a few things. I'm good with flashing anything else. Plus I don't have a class 6 SD just class 2. :/
Sent from my SCH-I500 using XDA App

Use the monster file thread link to build a 1 gig cwr boot disk with your sd. Drag and drop that file in the v4 emmc flashable.. Follow the instructions to boot from sd, wipe system, data (boot is optional, some say they do it without wiping boot, but I myself wiped) it will crash when wiping boot, just hold the power button and turn it back on. Then flash like any rom in cwr and when its finished take the sd out then select reboot... It will take you into honey comb... Check the threads for more help
Sent from one of those missing Droids

I've got HC v04 preview running on eMMC (not SD card), and for me it is very stable.
I followed the instructions over on AndroidCentral. Here is the link:
http://forum.androidcentral.com/barn...ook-color.html
The actual zip was produced by samuelhalff, whose thread can be found here: http://forum.xda-developers.com/showthread.php?t=947071
I've got access to the market, apps seem to install fine, and all my old B&N stuff is still available. Frankly I prefer the free B&N Reader I downloaded from the market to what I had with the stock Nook. Even better, the kernal included in the package was already OC'd to 1.1Mhz, and I'm consistently getting 1,500 to 1,600 on Quadrant.
For me the total install was pretty smooth...just remember to follow instructions exactly.
FYI: The above link also includes instructions on installing to an SD card.

DeadlyDa said:
I've got HC v04 preview running on eMMC (not SD card), and for me it is very stable.
I followed the instructions over on AndroidCentral. Here is the link:
http://forum.androidcentral.com/barn...ook-color.html
The actual zip was produced by samuelhalff, whose thread can be found here: http://forum.xda-developers.com/showthread.php?t=947071
I've got access to the market, apps seem to install fine, and all my old B&N stuff is still available. Frankly I prefer the free B&N Reader I downloaded from the market to what I had with the stock Nook. Even better, the kernal included in the package was already OC'd to 1.1Mhz, and I'm consistently getting 1,500 to 1,600 on Quadrant.
For me the total install was pretty smooth...just remember to follow instructions exactly.
FYI: The above link also includes instructions on installing to an SD card.
Click to expand...
Click to collapse
did u do anything special to get your market to run? I cannot get it to download anything and after I cleared the cache stuff, the market wont even open.

When I first installed HC, I had the dreaded "market problem".
I can't find the original post to give proper credit, but I followed the following steps which resolved the problem.
Go to Settings=>Applications=>Manage Applications and select Google Services Framework. Under Storage, press the "Clear Data" button, then "Force Stop".
Still in Settings=>Applications=>Manage Applications, select Market. Press the "Force Stop" button.
Then reboot and it should work...at least it did for me

not for me lol, just keep getting a error has occured try again later, thanks tho.

I strongly advise flashing the internal memory instead of using the SD. You can try the SD route once, but if it fails, don't waste your time. I've bought 4 different microSD cards just to try getting honeycomb working on NC. I read some of the recommendation in xda and purchased the cards with higher success rate. But after 4 days of fruitless efforts, I gave up today. Then I thought, what could go wrong, I don't use the Nook to read anyway, and went on to flashing the internal memory. Holy S*it. 10 minutes and I got honeycomb running.

I have somewhat reached a standstill in my NC endeavors, because I do want to continue using the device as an e-reader and keep the B&N in store features + stock apps that come with the Nook. I also really want to run Honeycomb from eMMC (class 4 sd card is cool for a bit but not really cutting it in terms of every day usability), as I am an android enthusiast, and this was one of the main reasons I bought the NC in the first place. Does anyone know if it's possible to do a dualboot of the two, without severely messing something up?
Another option I can imagine is having the stock Rom running from an SD card for B&N needs, if that is known to work any better. I'm hoping someone with more knowledge can add to my initial brainstorming of possibilities for this guy...

I had the same market problem. Then I flashed this zip through Clockwork Recovery and that seemed to fix things. Make sure and do the v003
http://forum.xda-developers.com/showthread.php?t=953603

Related

[Q] Nook Color honeycomb

Does anyone know how to test if a bootable sdcard with nookie honeycomb actually works before you test it out on the nook color? thnx
btw i used the process that was on this site http://theunlockr.com/2011/02/07/how-to-load-honeycomb-android-3-0-on-the-nook-color-usd-method/
Not sure why you need to test it before putting it in the nook. If you're worried about doing any harm to the nook it's really not possible. Just put the card in and try to boot. If it doesn't boot take the card out and boot up normally, no harm no foul.
ryspy8492 said:
Not sure why you need to test it before putting it in the nook. If you're worried about doing any harm to the nook it's really not possible. Just put the card in and try to boot. If it doesn't boot take the card out and boot up normally, no harm no foul.
Click to expand...
Click to collapse
I second this. By default, all the Main Roms for Nookie Froyo and Nookie Honeycomb have no features enabled that will touch your Nook Color. The only thing it touches on the NC is the Cache Partition in order to prevent too many writes to the SD and to also speed things up. Anything done there won't screw up your NC in a Million years and Switching back to Stock and doing a few things will wipe any evidence. Or if really paranoid you can Flash back to Factory to ensure all is wiped.
____________________________________________________
Sent from Nookie Froyo using Tapatalk
thnx u guys, But i have another problem. i succesfully installed the honeycomb and got it to work on the nook color. But when I go to my computer with the sd card plugged in, it says that i only have 115 mb of data on the card. I have an 8 gb card. It's not left on the card, it says 115 mb out of 115 mb of data, even after i deleted everything. Anybody know how to restore it back to the 8 gb data amount thnxx
NookColor Format and partition your SD card back to a usable state
Opinion
Since the OP seems to have been answered, I'd like to piggy back a bit
Been doing some reading on the forums and I have started to vision myself getting in to the nook color honeycomb idea.
But a few questions first...
How well has it worked for anyone who has tried, is it a daily driver yet or too many issues? I have a SGS captivate so I am not too worried about having to mess with it before it works and I can use my phone to access email and all that.
But is it quick and snappy or will I feel like i'm using an underpowered device after using my phone.
And battery life, is it good, acceptable, or what?
Sorry if these have been answered somewhere else i tried to find the answers, but it's getting late and I have work yet to do tonight.
I installed it to emmc..over clocked it's still sluggish. Kinda cool but not a keeper to me.my droid x blows it away on performance. I will be back on phiremod beta 2 soon. Honeycomb is fun to tinker but not primetime. Remember it is not from aosp..missing features. It is amazing how good it isconsidering.
Well...its very promising for being in the early stages of development
Sent from my ncusing XDA App
Will i still have honeycomb on my NC if i format it?
Sent from my NC using XDA App
jlt220 said:
Since the OP seems to have been answered, I'd like to piggy back a bit
Been doing some reading on the forums and I have started to vision myself getting in to the nook color honeycomb idea.
But a few questions first...
How well has it worked for anyone who has tried, is it a daily driver yet or too many issues? I have a SGS captivate so I am not too worried about having to mess with it before it works and I can use my phone to access email and all that.
But is it quick and snappy or will I feel like i'm using an underpowered device after using my phone.
And battery life, is it good, acceptable, or what?
Sorry if these have been answered somewhere else i tried to find the answers, but it's getting late and I have work yet to do tonight.
Click to expand...
Click to collapse
i use honeycomb as a daily driver and if you install V2 on the emmc from samuallhaff(not 100% sure of his username off the top of my head) it runs smooth and it is really clean
i get the stock all day battery life(mainly it just sits in my bag when im in class but i have wifi always on so i dont disconnect from my schools wifi) and web browsing is amazing(it doesnt have flash though not a deal breaker though imo)
just dont use live wall papers and set CPU because they drain battery life faster and they diminish performance big time
bratliff said:
I installed it to emmc..over clocked it's still sluggish. Kinda cool but not a keeper to me.my droid x blows it away on performance. I will be back on phiremod beta 2 soon. Honeycomb is fun to tinker but not primetime. Remember it is not from aosp..missing features. It is amazing how good it isconsidering.
Click to expand...
Click to collapse
if you have setCPU or a live wallpaper installed on honeycomb it diminishes performance by 100%
i noticed this performance boost after i uninstalled setCPU and removed my live wallpaper from my honeycomb install and so far it has been great
luigi90210 said:
i use honeycomb as a daily driver and if you install V2 on the emmc from samuallhaff(not 100% sure of his username off the top of my head) it runs smooth and it is really clean
i get the stock all day battery life(mainly it just sits in my bag when im in class but i have wifi always on so i dont disconnect from my schools wifi) and web browsing is amazing(it doesnt have flash though not a deal breaker though imo)
just dont use live wall papers and set CPU because they drain battery life faster and they diminish performance big time
if you have setCPU or a live wallpaper installed on honeycomb it diminishes performance by 100%
i noticed this performance boost after i uninstalled setCPU and removed my live wallpaper from my honeycomb install and so far it has been great
Click to expand...
Click to collapse
I will remove set cpu and report back. I thought it was needed for oc.
tylrdoan said:
Will i still have honeycomb on my NC if i format it?
Sent from my NC using XDA App
Click to expand...
Click to collapse
I just realized that you are running HC from your SD card.
No, if you format that SD card, you lose HC. It actually mentions that in the procedure you linked in your original post.
The reason you only see 115MB on the card when you mount it on your Windows computer is because Windows can only see the first partition, the boot partition, that was written to that SD card as part of the procedure you followed. The rest of the space is taken up by partitions Windows can't see without help.
So if you want to continue to run HC off the SD card you have to dedicate that SD card just for running HC.
SD Card Partitions
while installing the image 3 patitions will be written on your sd-card.
1) root partition
2) honeycomb
3) fat32-partition
to use the full size of the sd-card use a partition manager to extend the fat32-partition.
installed apps can than transferred to the fat32-partition
fugitoid said:
I just realized that you are running HC from your SD card.
No, if you format that SD card, you lose HC. It actually mentions that in the procedure you linked in your original post.
The reason you only see 115MB on the card when you mount it on your Windows computer is because Windows can only see the first partition, the boot partition, that was written to that SD card as part of the procedure you followed. The rest of the space is taken up by partitions Windows can't see without help.
So if you want to continue to run HC off the SD card you have to dedicate that SD card just for running HC.
Click to expand...
Click to collapse
i was wondering if i put honeycomb on my nook color, not on the sdcard, how would i do it. The instructions on that site only says how to make a bootable sd card. And i was using HC on a level 4 sd card and it said that u need a level 6. But i was still able to get it to run. The honeycomb on the sd card level 4 was pretty slow. i was wondering if i got it on my NC, would it be faster. If it would, can someone show me how?
Just follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=947071
bratliff said:
I will remove set cpu and report back. I thought it was needed for oc.
Click to expand...
Click to collapse
Nope lots of lag still. Its ok not complaining. Lots of fc in dolphin too. Back to phiremod 2.2 for awhile.
You have to remember that the Honeycomb that was Ported is the Preview Release, think Demo version. It wasn't ported from (pretty much)scratch like Froyo was. It is more of a Rom hack. For a better performing version we have to wait for Honeycomb's Official Full release. In perspective, it's amazing how much deeper-blue got done with just the Preview image.
____________________________________________________
Sent from Nookie Froyo using Tapatalk
GonzoTheNose said:
while installing the image 3 patitions will be written on your sd-card.
1) root partition
2) honeycomb
3) fat32-partition
to use the full size of the sd-card use a partition manager to extend the fat32-partition.
installed apps can than transferred to the fat32-partition
Click to expand...
Click to collapse
Not picking on you but it's actually 4 partitions.
1=Boot (Basically redirects to the Android on the SD)
2=System (Holds the main OS files of Honeycomb)
3=Data (Where all you're settings and other data are)
4=SDcard (This partition is used as a stand in for a Physical External SDcard)
Also the easiest/simplest way to access the 2, 3, and 4 partitions is to use linux. Burn a LiveCD if you don't want to Install, although Ubuntu can be Installed without Partitioning or other such normal 2nd OS needs. Just get the Windows installer from http://ubuntu.com
____________________________________________________
Sent from Nookie Froyo using Tapatalk
SD Card and Honeycomb 3.0 v4 image
I've been looking for an answer throughout the forums on this question but can't seem to find anything. The problem: I used the Honeycomb v4 image with WinImage. The SD card was originally 8 GB. The image file is 4 GB with approximately 600 MB or so of free space. Missing: 4 GB that was on the card.
1. Can I use a utility under Windows to get the free space allocated on the SD card that remains? If so, how?
2. Is there an option with WinImage to allocate the additional space on the SD card as free space and include it as part of the image that is being written to the SD card?
3. If I need to restore my SD card back to 8 GB, can that be done in Windows Explorer (not sure that Windows will pick up the full 8 GB as I haven't tried that yet).
Thanks.
Ohh, you have that problem. Don't know where you've been looking but that has been asked and answered many times. The problem is that when you install Froyo or Honey to the SD it makes 4 partitions like I listed above, but Windows can only see the First Partition and only Formats the First partition. The easiest way to fix is to put it in UnRooted Stock and Format it from Settings. If you don't have that you can Burn a Linux or GParted Live CD and Format it from their.
____________________________________________________
Sent from Nookie Froyo using Tapatalk

[Q] Reverting Nook Color HELP PLEASE

So I bought a used (barely) nook color off of craigslist today for 200 with a screen protector and 8 GB transcend class 6 microSD. The guy I bought it from had his google account on it though so I tried to remove it. Basically I did the imaging through terminal (i cantp ost a link) and put the new stuff on and now it says my memory stick is damaged (even though it mounts on my computer) and it freezes my NC whenever it is in
I'm basically wonder, HOW CAN I GET MY CM7 2.3 NC to reset itself so I can put my own account on it. I have searched but can't find anything that good, as I have clockwork, but the rom is installed ON the NC internal, not on the microSD...Please help me out in some kind of step by step way. I rooted my droid eris myself, but starting with it pre-rooted has messed me up.
http://forum.xda-developers.com/showthread.php?t=1030227 start with this thread.
You should have ROM manager on there already. Reflash CM7 and wipe data...should take you to a fresh install.
Sent from my NookColor using XDA Premium App
So what step do I start out if I have clockwork mod on there already? I dont have recovery though.
Go into your programs and open ROM Manager (this assumes that you already have clockworkmod installed). Make sure that you have a micro SD card in the Nook with your desired CM7 build (either nightly or stable). Then Click on Install ROM from SD Card. Click on the ROM that you want to flash. It will then give you the option to Backup Existing ROM and/or Wipe Data and Cache. Go ahead and select Wipe Data and Cache. Hit OK and the Nook will do the rest automagically. (ROM Manager may request Superuser status, go ahead and grant it or it will not work). After you regain control, you should have a fresh, clean install of CM7 to work from.

What is uNooter?

I just got my Nook Color and am looking into how to go about rooting it for CM7. I checked out CM's Wiki page on it here and it mentioned using uNooter. I haven't read about this tool anywhere else and Google searches for it turn up practically nothing. Is this not the right tool to use? The forums mostly seem to mention ManualNooter, Auto-Nooter, etc. Also is it possible to flash CM7 on the internal memory and avoid using an SD card altogether?
Never heard of unooter and I've been reading theses forums since December. Auto mooter was to root the older firmware 1.0 ,1.01,and 1.1. Manualnooter is for the newer froyo firmware.
Rooting stock is not required to install CM7.
You simply need to create a Clockworkmod recovery microSD card and you can then flash CM7 (which is pre-rooted) from Clockworkmod.
martian21 said:
Rooting stock is not required to install CM7.
You simply need to create a Clockworkmod recovery microSD card and you can then flash CM7 (which is pre-rooted) from Clockworkmod.
Click to expand...
Click to collapse
Thanks. I figured this would be relatively easy compared to rooting and putting CM7 on my EVO but reading on here there seemed to be a few different approaches. Will that method allow me to flash CM7 to the eMMC, and after that point will I no longer need the SD card to boot? I ask because I don't have a card on hand and am considering backing up the contents from my phone's card and using that.
xdp said:
Thanks. I figured this would be relatively easy compared to rooting and putting CM7 on my EVO but reading on here there seemed to be a few different approaches. Will that method allow me to flash CM7 to the eMMC, and after that point will I no longer need the SD card to boot? I ask because I don't have a card on hand and am considering backing up the contents from my phone's card and using that.
Click to expand...
Click to collapse
Correct.
You only need the SD to install a bootable CWM then you can flash CM7 from that. After words when CM7 is installed to eMMC you are able to use Rom Manager to install CWM to eMMC as well, so everything will be set up on the device's internal memory. SD is needed only for the initial boot of CWM to install CM7.
Nburnes said:
Correct.
You only need the SD to install a bootable CWM then you can flash CM7 from that. After words when CM7 is installed to eMMC you are able to use Rom Manager to install CWM to eMMC as well, so everything will be set up on the device's internal memory. SD is needed only for the initial boot of CWM to install CM7.
Click to expand...
Click to collapse
Thanks. From reading around it seems you can't use a phone or the Nook to mount the card and write the image, so I'll have to buy a reader and might as well get a card for the Nook at the same time. Since I'll be flashing CM7 to eMMC does it really matter if I get a class 4 or above card like many suggest? I'm not sure what's in my EVO but that is my benchmark. Class 2 seems to be what comes up in searches the most.
The general consensus it's to stick with Sandisk SD cards for the Nook. There are others that work as well but Sandisk it's pretty much a guarantee of zero issues. You can usually score an 8 GB class 4 Sandisk at Wal-mart for a Jackson.
Sent from my NookColor using XDA App
martian21 said:
The general consensus it's to stick with Sandisk SD cards for the Nook. There are others that work as well but Sandisk it's pretty much a guarantee of zero issues. You can usually score an 8 GB class 4 Sandisk at Wal-mart for a Jackson.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
Transcend 8 GBs have worked beautifully on all 3 NC's in my house.
xdp said:
I just got my Nook Color and am looking into how to go about rooting it for CM7. I checked out CM's Wiki page on it here and it mentioned using uNooter. I haven't read about this tool anywhere else and Google searches for it turn up practically nothing. Is this not the right tool to use? The forums mostly seem to mention ManualNooter, Auto-Nooter, etc. Also is it possible to flash CM7 on the internal memory and avoid using an SD card altogether?
Click to expand...
Click to collapse
I was the one that put together uNooter after being contacted by the individual that maintains the CyanogenMod wiki. They wanted a universal Nooter that would only root the device, install Superuser, ADB, RomManger, and work on all versions of the NC software. They asked that it be called uNooter. It is not released anywhere else, so that is why you did not see any mention of it on a Google search.
martian21 said:
The general consensus it's to stick with Sandisk SD cards for the Nook. There are others that work as well but Sandisk it's pretty much a guarantee of zero issues. You can usually score an 8 GB class 4 Sandisk at Wal-mart for a Jackson.
Click to expand...
Click to collapse
That information is really only relevant to running a ROM from the SD card. If you're only using the card for storage, or to get CM7 on eMMC, manufacturer and card class don't matter.
xdp said:
Thanks. From reading around it seems you can't use a phone or the Nook to mount the card and write the image, so I'll have to buy a reader and might as well get a card for the Nook at the same time. Since I'll be flashing CM7 to eMMC does it really matter if I get a class 4 or above card like many suggest? I'm not sure what's in my EVO but that is my benchmark. Class 2 seems to be what comes up in searches the most.
Click to expand...
Click to collapse
I wrote my image over USB to a card in the NC without a card reader. I've seen wiki guides saying there's a greater chance of the write getting interrupted, rendering the card unusable at least in the short term, but it worked for me. It was only when I wanted to revert the card to storage that I ended up needing a card reader. The links in my sig have a little more info about using the NC as your card reader, but you're probably better off just grabbing one.
Also, while CM7 does not require an SD card, many apps do. Your experience will be somewhat limited without one.
GMPOWER said:
I was the one that put together uNooter after being contacted by the individual that maintains the CyanogenMod wiki. They wanted a universal Nooter that would only root the device, install Superuser, ADB, RomManger, and work on all versions of the NC software. They asked that it be called uNooter. It is not released anywhere else, so that is why you did not see any mention of it on a Google search.
Click to expand...
Click to collapse
Great to hear directly from the source, thanks! I'm surprised more people don't point to your tool on the forums given that it's right on the CM Wiki. At this point I'm a little confused about the various approaches to do this. Does your tool install ROM Manager directly into the stock Nook interface, and then I flash from there, versus booting CWM off the SD as people mentioned earlier in the thread? Sorry if that's completely off-base.
Taosaur said:
That information is really only relevant to running a ROM from the SD card. If you're only using the card for storage, or to get CM7 on eMMC, manufacturer and card class don't matter.
I wrote my image over USB to a card in the NC without a card reader. I've seen wiki guides saying there's a greater chance of the write getting interrupted, rendering the card unusable at least in the short term, but it worked for me. It was only when I wanted to revert the card to storage that I ended up needing a card reader. The links in my sig have a little more info about using the NC as your card reader, but you're probably better off just grabbing one.
Also, while CM7 does not require an SD card, many apps do. Your experience will be somewhat limited without one.
Click to expand...
Click to collapse
Yeah, I thought about this as well and figured I'd want a full-time card for the device so I ordered a card with SD adapter. I figured the specs didn't matter at all for a data card but picked up a class 4 Sandisk anyway.
xdp said:
Great to hear directly from the source, thanks! I'm surprised more people don't point to your tool on the forums given that it's right on the CM Wiki. At this point I'm a little confused about the various approaches to do this. Does your tool install ROM Manager directly into the stock Nook interface, and then I flash from there, versus booting CWM off the SD as people mentioned earlier in the thread? Sorry if that's completely off-base.
Click to expand...
Click to collapse
I received notice this past Monday that the cleaned up version of the CyanogenMod wiki was online, so not a whole lot of exposure for people to talk about it. I believe the old wiki had listed the different Auto-Nooter and Manual-Nooter that went with each software version, thus taking up a lot of space and confusion. AN and MN are more tailored to people that want to stick with the stock software, but enable full Android Market access. People that want to go from stock to CyanogenMod don’t need all the extra software that is bundled with AN and MN just to be able to flash CyanogenMod. By eliminating all the version specific software I was able to create a version that would work on all current, and hopefully future, software versions.
Yes, my versions will install Rom Manager directly into the interface. You would then allow Rom Manger to install CWM Recovery, and then you can download and install CyanogenMod from the device. You could also take a full backup of your current stock rom. Using uNooter or bootable CWM will both get you to where you want to go, it is really up to you on how you want to get there.
Instructions for installing CM7 to the eMMC using CWM on a SD card (which can later be reformatted for storage) is in this thread: http://forum.xda-developers.com/showthread.php?t=1030227.
GMPOWER and bigbob23: Thanks for the info, that was exactly what I needed to clear everything up. I suppose backing up the stock ROM would be useful in case I ever needed to restore it for warranty purposes or anything. I'm not sure which approach I'll go with, my SD card came today so I'll be reading over both techniques and giving one a shot!
Thanks again.
I went through the process with uNooter as outlined on the CM Wiki and it went perfectly. The only thing was I had to use SD Formatter and the earliest 0.1 version of Win32 Disk Imager to get the image to write to the SD card. Not sure if that problem is specific to Win7 64-bit but maybe I can mention it on the wiki.
xdp said:
I went through the process with uNooter as outlined on the CM Wiki and it went perfectly. The only thing was I had to use SD Formatter and the earliest 0.1 version of Win32 Disk Imager to get the image to write to the SD card. Not sure if that problem is specific to Win7 64-bit but maybe I can mention it on the wiki.
Click to expand...
Click to collapse
I am glad that you got everything to work right. I think the problems that you might have experienced are more associated with win7 x64. My replacement laptop with win7 x64 will not be here for another two weeks for me to test it on, but in the past I have had to use Unlocker almost every time to unlock the usb drive before I could proceed with flashing using Win32 disk imager. On my current windows 7 x86 setup, I have yet had to use Unlocker to be able to flash an image with the win32 program. HERE is a post with people having problems in the past with win32 disk imager on win7 x64, they took the same path that you did with Panasonic SD Card Formatter to fix it.
uNooter
I guess this worked for the latest firmware of 1.2.0? (I am about to root one soon!) thanks in advance!)
AF9210 said:
I guess this worked for the latest firmware of 1.2.0? (I am about to root one soon!) thanks in advance!)
Click to expand...
Click to collapse
I just got my nook last week so I'm assuming I had the latest factory firmware when rooting, but I didn't check.
xdp said:
I just got my nook last week so I'm assuming I had the latest factory firmware when rooting, but I didn't check.
Click to expand...
Click to collapse
If you see "Read Forever" when booting (stock) then "Yes" you have the latest firmware.
ADB after uNooter?
Above, GMPOWER mentioned ADB as one of the items uNooter installed. I've rooted with uNooter in part because *nothing* *else* I could find would actually boot on my NC and in part because I liked the idea of a relatively minimal root. I figured I could then push any apk's I wanted to add with adb.
Unfortunately, that doesn't seem to be working. I used "NookColor Tools -> All Settings -> Development" to enable USB debugging, but 'adb devices' shows nothing. If I plug in my G2 with CM7, adb finds it just fine, so I'm pretty sure I've got the computer side of things working. Any hints about getting the NC to play nice?

[Q] Newbie Nook Color owner needs guidance :-)

Hi all,
After reading all the great stuff about the NC recently, CM7, Phiremod and the honeycomb releases Ive convinced a mate of mine in California who's visting the UK to bring me one over to tinker with..
Now.. After doing some research Im overwhelmed with info and thought Id ask for "up to date" pointers..
1. Is there a straightforward guide to rooting and installing the NC, as I live in the UK Im not fussed about the original NC rom. I've seen Cyanogenmods wiki entry http://wiki.cyanogenmod.com/wiki/Barnes_&_Noble_Nook_Color:_Full_Update_Guide is this the best approach?
2. Which rom is best? Plain CM7, Phiremod or Honeycomb as posted by deeper blue?
3. Any other pointers?
Sorry for such basic questions, im just overloaded and not 100% sure which is the best process to take.
thanks all in advance
Angelo
Take a look in the stickies, there are comprehensive guides to root....just make sure you're using the correct version. If your mate is buying a brand new one for you, you'll most likely need the version for rooting with partitions. I have used all 3 of the roms you mentioned and my personal preference is CM. Phiremod is just a heavily themed version of CM and the honeycomb build is ok, but it lacks some features and is still a bit buggy because the source code has not been released for honeycomb
Sent from my DROIDX using XDA Premium App
If you decide on CM7 (which I personally recommend), I would look for "How to Install CynaogenMod 7 on the Nook Color" (can't post links) on YouTube. I personally found it very useful. If something seems off, make sure you look at the description and read some user comments. With the way this guy explains it it's practically idiot proof and it's unlikely you'll mess anything up.
thanks
Thanks Guys,
I've been doing more reading and yeah looks straightforward..
Considering Im not interested in the core B&N OS, I was thinking of installing CM7 to the internal memory and then perhaps installing Honeycomb (deeperblue version) on a memory stick to "play with".
From what I can tell the HC port is nice as a toy but not robust enough considering HC hasnt been released to AOSP.
Makes sense?
If you are looking to 'play with' honeycomb on a MicroSD install, check out http://forum.xda-developers.com/showthread.php?t=1045018
You get Honeycomb and Phiremod in a dual-boot image tailored for a MicroSD install.
Read through the thread and see if it's to your taste.
For the most usable ROM, go with CM7. Just follow this guide in this post. Very simple.
http://forum.xda-developers.com/showthread.php?t=1030227
The only issue is if you have a "blue dot" with the newer partition. Just read the RED text at the beginning of that post.
After you get this running, you can read up a little more and create a SD card w/ Honeycomb or Phiremod to play around with. But CM7 is the most stable out there (well, I guess Phiremod is good to, because it is a customized CM7).
Good Luck.
Use CM7, it's the best for now.
HC is beauty but still a lot of work to be done.
jasoraso said:
For the most usable ROM, go with CM7. Just follow this guide in this post. Very simple.
http://forum.xda-developers.com/showthread.php?t=1030227
The only issue is if you have a "blue dot" with the newer partition. Just read the RED text at the beginning of that post.
After you get this running, you can read up a little more and create a SD card w/ Honeycomb or Phiremod to play around with. But CM7 is the most stable out there (well, I guess Phiremod is good to, because it is a customized CM7).
Good Luck.
Click to expand...
Click to collapse
+1 for this guide!
"The only issue is if you have a "blue dot" with the newer partition. Just read the RED text at the beginning of that post."
For some reason I thought that statement was obsoleted, am I wrong?
It was valid if you have v1.2 NC and flashing with CwM Recovery prior to v3.2.xx.
But since the instructions do indicate using v3.2.0.1 CwM, then why care about blue-dot or not since it has been taken care off unless v3.2.x.x not properly does the job.
Maybe because you have a choice in partition schemes?
You really will want to repartition the new nook. 1 gb is a very small partition for your programs. 5gb works much better and the change is fairly painless.
Sent from my NexusOne using Tapatalk
IFLATLINEI said:
Maybe because you have a choice in partition schemes?
Click to expand...
Click to collapse
That's a reasonable reason but again, it shouldn't be highlighted in RED, ORANGE at best
In fact, since it's a choice of good, it should be in GREEN.
thanks guys
Thanks guys, Im in awe with all the feedback and comments this thread is getting..
yes, Ive received the NC today and its charging Also doing loads and loads of reading
My nook does have a bluedot so my partitions are 5gb Data/1Gb Media.
I'll probably leave it like so, considering CWM supports this now its ok, and put most of my media on an external 16gb microsd card..
If Im right I can still install apps into the 5gb partition right?
Also , if I understand it correctly I can actually install CM7 onto a microSD and simply boot from this right ,without rooting/installing CWM... ?
Angelo
asantaga said:
If Im right I can still install apps into the 5gb partition right?
Also , if I understand it correctly I can actually install CM7 onto a microSD and simply boot from this right ,without rooting/installing CWM... ?
Angelo
Click to expand...
Click to collapse
You can still install apps into the /data partition but pls note: if your NC isn't rooted, you can only install apps that offered by B&N. You do not have full access of Android Market.
About CM7, yes, you can run CM7 off uSD and not touching the eMMC (aka internal memory) at all. Be considered getting a Sandisk (class 2 or class 4)
B-i-g thanks
All,
BIG Thanks to everyone,
I've successfully (actually flawlessly), repartitioned my nook to the old standard and installed CM7 into the internal memory..
All flawlessly. Also ordered a sandisk 16gb memory card from amazon.co.uk, so that will hold most of the media..
I was considering making the main partition >1Gb (1.9Gb) but decided to leave it as it is for now.. It was so easy yo tweak I thought Id try it vanilla and then grow if I need to..
Awesome-ness
ok wheres my 5gb?
ok got one question now..
/media is supposed to have 5gb available..
CM7 doesnt appear to allow me to use it as a SD card.. but ive found it mounted as /mnt/emmc
How does one use it ??? I tried downloading pdfs and I was told that an SD card was required for this... :-( when i get home I was going to try mounting it via usb to a computer but is that the only way?
There are 2 things you need to know
1. If you're running CM7, you MUST have a uSD. "MUST" does seem to be a strong word but for some reason, that I still try to figure out, an external uSD is required. W/o it, you can still using it but there's some apps won't run if no uSD plugged. It means the NC works 99.9% w/o uSD. I guess I should take the "MUST" back, ehhh
2. If you're running the recently nightly-build CM7, the USB storage utitlity should already be implemented within the ROM. All you need to do is
1. Connect NC and PC via USB cable
2. by this time, the usb indicator should be appeared on the NC, tab on it
3. Tab on Connect USB to transfer .......
4. Turn USB Mass Storage on
5. by this time, PC should recognize the /media on the NOOK
6. do what you want to do
votinh said:
There are 2 things you need to know
1. If you're running CM7, you MUST have a uSD. "MUST" does seem to be a strong word but for some reason, that I still try to figure out, an external uSD is required. W/o it, you can still using it but there's some apps won't run if no uSD plugged. It means the NC works 99.9% w/o uSD. I guess I should take the "MUST" back, ehhh
2. If you're running the recently nightly-build CM7, the USB storage utitlity should already be implemented within the ROM. All you need to do is
1. Connect NC and PC via USB cable
2. by this time, the usb indicator should be appeared on the NC, tab on it
3. Tab on Connect USB to transfer .......
4. Turn USB Mass Storage on
5. by this time, PC should recognize the /media on the NOOK
6. do what you want to do
Click to expand...
Click to collapse
Wicked, yeah didnt see the little icon down below
thanks
Hey Angelo, I just wanted to share my experience.
I love gadgets, and tinkering with gadgets. I am an IT manager/minor programmer/webmaster, etc. etc... so no surprise that I feel right at home here BUT, I also love to read and I think that the Nook app for Android is bunk (e.g. "poor") compared to the stock NC experience.
I decided pretty early on that I wanted to keep the NC stock (partially due to warranty) and have a dual boot option for CM7. I had initially installed CM7 on my NC, replacing the stock rom all together. I ended up putting the stock ROM back on.
Here is a post from another thread where I outline that experience...and the guides that I use.
I talk about partitions in that post, since you have a new NC, don't even bother yourself with that...just note the guides there that will get you where you want to go, either way....
asantaga said:
ok got one question now..
/media is supposed to have 5gb available..
CM7 doesnt appear to allow me to use it as a SD card.. but ive found it mounted as /mnt/emmc
How does one use it ??? I tried downloading pdfs and I was told that an SD card was required for this... :-( when i get home I was going to try mounting it via usb to a computer but is that the only way?
Click to expand...
Click to collapse
Many (older) apps in on Android are designed to ONLY look for storage called "sdcard". So your 5gb of internal (emmc) called "Media" will not be able to be utilized by those Apps.
Apps that are better programmed and designed can access the memory called "Media".

[Q] CM7 boot from SD card - Problems!

Wish I could post this to the "Size agnostic SD Boot" thread, but as a Noob, I can't.
Have: New NC, had 1.2, updated to 1.3. Created bootable CM7.1 stable card on a new Sandisk 4GB, Class 4 card as per instructions in that thread. All seemed to go well. Upon start up, I see my new Android home page. After several seconds, I get an error: "Sorry! Process system is not responding". Gives me a choice between "Force Close", and "Wait". Choosing either seems to not make a difference. I have no WiFi connection, and going to settings I can't seem to enable it. After about 3 minutes, it freezes. But before so, I can interact with my new (impressive!) system.
Tried:
1. Numerous reboots.
2. Re-flash SD card. Three times. No good.
3. Went from 7.1 stable to latest Nightly.
Symptoms are always the same, right down to the time it takes to freeze.
If I don't interact with it after boot, the screen goes blank, but I detect a slight background light - is this perhaps the SOD problem?
Ideas?
What brand is your SD card?
Sent from my NookColor using Tapatalk
Sandisk 4GB, Class 4 card
I've read a bit about a Wifi driver patch, but I can't get the NC to run long enough to try and patch it in.
I recently bought a refurb Nook and install CM 7.1 Stable on a Sandisk Class 4 8gb card without issue. I'm actually shocked at how well it runs.
Maybe you got a bad card?
I'm sure somewhere you might find a utility to see if the card has issues? Check the SANDISK website.
Installing CM7 on the 4GB card was a temporary move, as I just had to try it. I have a 16GB card that should show up today. So, given that....
I installed CWM on the 4GB card, and it seems to work fine. However, I doubt that CWM "stresses" the card to the extent that running full Android would.
Keeping fingers crossed that a different card may work.
Hans.
I am using a 4gb class 2 Sandisk card and it works great. I have 8gb class 6 Transcend cards and they are not as good. I get force closes using them with certain apps.
Update: New SD card - *exactly* the same symptoms. Same error immediately after Home screen loads: "Sorry! Process system is not responding", and then it freezes solid in about 3 minutes regardless what I'm doing. And no Wifi.
Just as before.......
Try downloading the images again and start over.
"Try downloading the images again and start over. "
Well, in effect I did. I tried a couple of different versions of CM7. Also tried redoing the .img loader/boot file.
In every case, I get exactly the same symptoms.
4regt4 said:
"Try downloading the images again and start over. "
Well, in effect I did. I tried a couple of different versions of CM7. Also tried redoing the .img loader/boot file.
In every case, I get exactly the same symptoms.
Click to expand...
Click to collapse
Did you ever download the SASD image file again?
Also... since you don't specify... did you download the 1.3 image and not the 1.2 or the update?
DizzyDen said:
Did you ever download the SASD image file again?
Also... since you don't specify... did you download the 1.3 image and not the 1.2 or the update?
Click to expand...
Click to collapse
Yes, tried once to download the .img file. I'm reasonably sure it's 1.3, as that is in the file name. It took FOREVER to decompress - like an hour. Used gzip for the heavy lifting.
Just curious.... Would an even slightly corrupt .img loader file even work? I mean, it seems that it's job is to load CM7, and then after that is done, the rest is up to CM7. Is it possible that a bad .img file would basically work, but load a slightly corrupted CM7?
Don't know if it's an issue with the Nook itself. Has been running B&N 1.3 super stable, and for the last couple of days (with ~8 hours/day), I've been on a ManualNootered 1.3 with no problems or instabilities whatsoever. Did the MN install (as well as a bootable CWM) with the same SD, USB adapter, and PC with no problems.
Really scratching my head over this one.
Thanks.
Use this search on Google....there is some interesting stuff out there. One guy tracked it down to being an ALARM set on his clock.
Search google with this :
Sorry! Process system is not responding cyanogen
4regt4 said:
Yes, tried once to download the .img file. I'm reasonably sure it's 1.3, as that is in the file name. It took FOREVER to decompress - like an hour. Used gzip for the heavy lifting.
Click to expand...
Click to collapse
This is the part that gets me. I've made a few of these cards and all I ever did was unzip the image file with winzip and write the image to an sdcard with winimage. The unzipping process only took a few seconds.
4regt4 said:
Yes, tried once to download the .img file. I'm reasonably sure it's 1.3, as that is in the file name. It took FOREVER to decompress - like an hour. Used gzip for the heavy lifting.
Thanks.
Click to expand...
Click to collapse
Something wrong with that I just tested how long it takes to take the generic-sdcard-v1.1.img.gz file and decompress it to generic-sdcard.img and it took 15 seconds
What are you using I am using winrar 3.41 and my PC is like about 4 years old so not a fast processor.
Download winrar trial and start again
Again, I appreciate all the help. Here is what I've done:
1. Read a bunch of the stuff from the suggested Google search. (doh! - should have done this first). There is little Nook specific, but it seems that some apps on some devices seem to be the guilty culprit. I had only loaded 2 apps (Tweek and Priceline) on my NC before trying CM7.1, so if it is an app, it would have to be one of those, as the rest of the apps are pre-installed B&N, which (I assume...) the rest of you have. (Note: being new to all this, I'm surprised that their is no obvious way to uninstall an app. Seems I remember some sort of app manager on Market. I'll look.)
1a. There are several reports of alarms being set on alarm clock apps causing problems. On my fresh CM7.1 install, the clock did indeed have 2 alarms set. I deleted them and rebooted. No good.
2. Since there is a possibility of this being app related, I cleared the caches from CWM. Reinstall. It appears that this is a moot point, because I noticed in the install routine that it says "clearing caches". Oh well.
3. Got fresh copy of 1.3 .img file, and installed WinRAR. The unzip was a lot faster, but still not super speedy - about 1 minute (1GHz PC, WinXP)
4. Redid the SD chip again with my fresh files. Getting good at this. Win32Imager, safe remove, reinsert, copy CM7.zip, save remove, boot in NC.
5. No good. "Sorry! Process system is not responding". I've heard conflicting info whether "Wait" or "F/C" is better, but it doesn't seem to matter in my case.
So, short version: Tried new SD, new file downloads, new unzip utility. Meanwhile, over in eMMC land, rooted B&N 1.3 is cruising along just fine, with no errors or crashes.
Sure would like to try CM7, though.
At this point the only thing I can think of is that the sd card boot is conflicting with your rooted emmc. I've only created cm7 cards for stock nooks and never ran into any problems.
Malave said:
At this point the only thing I can think of is that the sd card boot is conflicting with your rooted emmc. I've only created cm7 cards for stock nooks and never ran into any problems.
Click to expand...
Click to collapse
Well, as I mentioned earlier, I did most of this messing around before rooting 1.3. I only applied ManualNooter after it was becoming clear that CM7 might be a long drawn out process. I was needing Market access. FWIW, the boot manager that you can boot into from the card (enabling selection of SD or eMMC) has been working with both 1.3 and rooted 1.3 - which I suppose it should. I mean, nothing got broke in that department.
Anyway, I really appreciate the comments.
Just a thought ----
Is the v1.3.img file shown in the original procedure compatible with B&N 1.3 and blue dot partitioning? Or does it even matter? I'm guessing that it shouldn't matter, as CM7 is supposed to be running from SD, but perhaps the partition sizes on the SD are mimicked from eMMC, and incompatible?
Boy, I'm really grasping at straws here.......
Ok last one, did you try formatting the sdcard?
Sent from my SCH-I510 using XDA App
Malave said:
Ok last one, did you try formatting the sdcard?
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Yes, no, kinda, and sorta. The various cards that I used were new. So I basically assumed they had a fresh 'virgin' chip that would tolarate most anything. Again, assume. However, burning an .img file I think would render a format moot. Don't know that, just making another assumption.

Categories

Resources