I am attempting to install Nookie Comb onto my Nook. I have read asnd attempted to follow the instructions given at:
http://forum.xda-developers.com/showthread.php?t=1016115
The problem is: it appears that the instructions are not entirely complete.
The instructions include the following steps:
NOTE: Flash with the latest ClockworkMod Recovery/via ClockworkMod Recovery SD or standard Clockwork Recovery 3.0.1.0. This version is fully compatible with any Clockwork used for Nookie Froyo 0.6.8 (see the Nookie Froyo page here)
* Copy "NookieCombvXXX.zip" to the root of your SD
* Place SD in nook and power on
* Format SYSTEM, DATA and CACHE (You do not need to wipe if coming from a previous version!)
* Flash Nookie Comb
* Once finished flashing, unmount your sdcard, remove from the slot and reboot.
after searching for several hours, I was able to find a Clockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
I performed the necessary work with imaging, copied the NookieComb zip file (0.4.13) to the SD crd, and used it to boot my Nook. That is when I ran into the other problem: how on Earth do I "flash" the Nookie Comb???
Using various searches, I have been looking for instructions on how to do this. I have fond none, on this site or anywhere else. There are no "flash" commands on the Recovery application. I am seeing people referring to having done the "flashing" but no one describes how this was done. Worse: without this "flashing" my Nook will not boot to the new OS.
Will someone *please* tell me what I need to do in order to do this "flashing"???
Thank you...
factor3 said:
I am attempting to install Nookie Comb onto my Nook. I have read asnd attempted to follow the instructions given at:
http://forum.xda-developers.com/showthread.php?t=1016115
The problem is: it appears that the instructions are not entirely complete.
The instructions include the following steps:
NOTE: Flash with the latest ClockworkMod Recovery/via ClockworkMod Recovery SD or standard Clockwork Recovery 3.0.1.0. This version is fully compatible with any Clockwork used for Nookie Froyo 0.6.8 (see the Nookie Froyo page here)
* Copy "NookieCombvXXX.zip" to the root of your SD
* Place SD in nook and power on
* Format SYSTEM, DATA and CACHE (You do not need to wipe if coming from a previous version!)
* Flash Nookie Comb
* Once finished flashing, unmount your sdcard, remove from the slot and reboot.
after searching for several hours, I was able to find a Clockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
I performed the necessary work with imaging, copied the NookieComb zip file (0.4.13) to the SD crd, and used it to boot my Nook. That is when I ran into the other problem: how on Earth do I "flash" the Nookie Comb???
Using various searches, I have been looking for instructions on how to do this. I have fond none, on this site or anywhere else. There are no "flash" commands on the Recovery application. I am seeing people referring to having done the "flashing" but no one describes how this was done. Worse: without this "flashing" my Nook will not boot to the new OS.
Will someone *please* tell me what I need to do in order to do this "flashing"???
Thank you...
Click to expand...
Click to collapse
Install zip from SD card option in CWR
lockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
Click to expand...
Click to collapse
That is the only one you need.
The procedures were written in March, it was right at that time but a bit outdated now since CwM has released few more newer versions and B&N did release new versions of NC.
"flash/flashing ROM" refers to replace/replacing the currently stock ROM (by saying)
However, by doing, it is the "install/choose zip from the SD card"
Then I have a real problem...
I was able to do the "Choose Zip from SD card" operation (which is apparently no different from my previous successful installation of the Phiremod system), and successfully installed the Nookie Comb zip file.
The problem seems to occur when I remove my SD card (as instructed) and do the reboot. The Nook briefly shows the Cyanogen logo (!??) and then it appears to hang!
Am I missing something here? The Nook becomes totally unresponsive and its screen looks like it is off...
Please advise.
lockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
patruns said:
That is the only one you need.
Click to expand...
Click to collapse
Pat:
Actually, I disagree. I want to put different zips on the SD card for research purposes (I want to develop some Android applications and test them using different software configurations). With a 1 GB limit, granted the zips are relatively small but if I have a bunch of them for different Android versions, plus backups of different user and system configurations, a 1 Gb SD card will run out of space fairly quickly.
There really does need to be different images for different SD card sizes.
How are these images made? Maybe I can make some and make them available... ?
factor3 said:
lockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
Pat:
Actually, I disagree. I want to put different zips on the SD card for research purposes (I want to develop some Android applications and test them using different software configurations). With a 1 GB limit, granted the zips are relatively small but if I have a bunch of them for different Android versions, plus backups of different user and system configurations, a 1 Gb SD card will run out of space fairly quickly.
There really does need to be different images for different SD card sizes.
How are these images made? Maybe I can make some and make them available... ?
Click to expand...
Click to collapse
Just use that .zip and then use something like EaseUs Partition Manager (free) to stretch the partition to the size that you need and to create additional partitions. Earlier versions have issues with the blue dot device partitions as well as doing proper data/system and cache wipes.
factor3 said:
lockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
Pat:
Actually, I disagree. I want to put different zips on the SD card for research purposes (I want to develop some Android applications and test them using different software configurations). With a 1 GB limit, granted the zips are relatively small but if I have a bunch of them for different Android versions, plus backups of different user and system configurations, a 1 Gb SD card will run out of space fairly quickly.
There really does need to be different images for different SD card sizes.
How are these images made? Maybe I can make some and make them available... ?
Click to expand...
Click to collapse
All you have to do is use EASUS or MiniTools Partition Manager to resize to claim the rest of the SD space.
Personally I wouldn't install Nookie Comb as it is outdated and made from an Incomplete SDK as Honeycomb was never Open-Sourced. Better to install CM7.1 while we wait for the Andtoid 4.0 ICS source to be released in Nov. and the inevitable Port of it to the Nook come Dec/Jan if not sooner. CM7 is more then enough for now and includes special "tablet tweaks" just for the Nook Color including "Honeycomb-esque" Bar buttons for Home, Menu, Back, ect...
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Successfully Installed...
I did solve my installation problems. I ended up doing a restore of the original Nook system, then running the reinstall once again.
It turned out that there was apparently something on my original Phiremod installation that screwed up the Nookie install...
In any event: japzone, I am wondering about the "incomplete" SDK that Nookie Comb is based on. Would that incompleteness include non- working location capabilities? Apparently, not only do they always seem to fail on this OS, but there are some minor network and email annoyances,as well (and I really don't like the awful keyboard!).
One thing that is good, though: some of the more advanced readers and Honeycomb- based applications seem to work well on Nookie Comb. Also: with Nookie Comb's booting off the Nook instead of the SD card, I have more space for things I want to put on it. Nookie Comb's power handling is better, too. With Phiremod I needed to charge my Nook every day. With Nookie Comb I am doing a charge every third day -- even when I am heavily using my Nook.
In all, aside from the annoyance of failing location services and a bad keyboard, I am pretty happy with Nookie Comb...
I am, however, open to looking at better installations. What version of Android does the CM7 you are suggesting run? If it isn't Honeycomb (and you seem to be implying it isn't) then aside from it being based on a stable Android version, what advantages does it have over Nookie Comb?
FYI, Pat:
EASUS does not work. It does allow you to change partition sizes on different devices, but it does not do this for FAT partitions -- which are the only partition that you can boot a Nook on...
factor3 said:
In any event: japzone, I am wondering about the "incomplete" SDK that Nookie Comb is based on. Would that incompleteness include non- working location capabilities? Apparently, not only do they always seem to fail on this OS, but there are some minor network and email annoyances,as well (and I really don't like the awful keyboard!).
One thing that is good, though: some of the more advanced readers and Honeycomb- based applications seem to work well on Nookie Comb. Also: with Nookie Comb's booting off the Nook instead of the SD card, I have more space for things I want to put on it. Nookie Comb's power handling is better, too. With Phiremod I needed to charge my Nook every day. With Nookie Comb I am doing a charge every third day -- even when I am heavily using my Nook.
In all, aside from the annoyance of failing location services and a bad keyboard, I am pretty happy with Nookie Comb...
I am, however, open to looking at better installations. What version of Android does the CM7 you are suggesting run? If it isn't Honeycomb (and you seem to be implying it isn't) then aside from it being based on a stable Android version, what advantages does it have over Nookie Comb?
Click to expand...
Click to collapse
Nookie Comb is built on the SDK of Honeycomb and not the AOSP source since the source for it wasn't available until a few days ago when Google decided to dump it at the same time they released the Source for it's successor 4.0 ICS. Theoretically NookieComb could be patched using the now released source but most Developers are focusing on ICS now that it's out as Honeycomb was long ago marked as a Stop-gap by Google and lost cause to make a stable port by Devs. If you really want tablet specific apps on your Nook NookieComb is your only option right now but other than that there is no Reason to switch to the Far more Stable and more Advanced CM7.1.
It's up to you. If NookieComb fufills what you need and you can live with the Bugs which will most likely never be fixed, go ahead and stick with it until ICS is ported to the Nook. However I and most other people here would reccomend switching to CM7.1(built on Android 2.3.x) as it has far more support, larger feature set, and is much more stable.
PS: If you were wondering, yes, CM7 has the Notification Soft-Keys just like NookieComb so no need for Softkeys or Button Savior.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
I forgot, Another thing CM7 has that NookieComb doesn't is Bluetooth.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Some quick questions
Japzone:
1. Does CM7 run off the nook or off the SD card? My previous Phiremod installation needed an SD card in order to run; Nookie Comb does not. Does CM7?
2. How is CM7 for power? Phiremod ate up power so fast that I had to charge my Nook every day. How long can you run CM7 between charges?
3. The Phiremod installation also had Bluetooth and Location services. The location services worked but Bluetooth apps and configuration always crashed when I tried to use them. How well do they work on CM7?
factor3 said:
Japzone:
1. Does CM7 run off the nook or off the SD card? My previous Phiremod installation needed an SD card in order to run; Nookie Comb does not. Does CM7?
2. How is CM7 for power? Phiremod ate up power so fast that I had to charge my Nook every day. How long can you run CM7 between charges?
3. The Phiremod installation also had Bluetooth and Location services. The location services worked but Bluetooth apps and configuration always crashed when I tried to use them. How well do they work on CM7?
Click to expand...
Click to collapse
1- CM7 can be installed to Nook internal emmc or by using verygreen's "size agnostic installer" can be installed to MicroSD. verygreen's installer auto sizes the install to fill entire SD no matter the size and allows easy updates to CM7
2- CM7 has had most of the battery issues ironed out for awhile now.
3- Bluetooth works fine on CM7, I've used a Wii Remote as a game controller without issue and pairing with other Bluetooth devices posed no issue. Only problems are the Short range(caused by the lack of a Bluetooth antenna in the Nook), and it will sometimes refuse to come on because of the hardware situation, solution is to turn off wifi and do a hard reboot then turn Bluetooth on first before WiFi.
I personally boot off SD because it allows me to easily switch to the StockOS if I feel like it and if something happens to my Nook I have less things I have to do before taking it in for repair. I've never really noticed a difference in speed because of usind an SD. A Class 4 Sandisk or Class 6 Generic cards work fine.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
japzone said:
Nookie Comb is built on the SDK of Honeycomb and not the AOSP source since the source for it wasn't available until a few days ago when Google decided to dump it at the same time they released the Source for it's successor 4.0 ICS. Theoretically NookieComb could be patched using the now released source but most Developers are focusing on ICS now that it's out as Honeycomb was long ago marked as a Stop-gap by Google and lost cause to make a stable port by Devs. If you really want tablet specific apps on your Nook NookieComb is your only option right now but other than that there is no Reason to switch to the Far more Stable and more Advanced CM7.1.
It's up to you. If NookieComb fufills what you need and you can live with the Bugs which will most likely never be fixed, go ahead and stick with it until ICS is ported to the Nook. However I and most other people here would reccomend switching to CM7.1(built on Android 2.3.x) as it has far more support, larger feature set, and is much more stable.
PS: If you were wondering, yes, CM7 has the Notification Soft-Keys just like NookieComb so no need for Softkeys or Button Savior.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Click to expand...
Click to collapse
you know if you read the nookiecomb thread it says its based off of nookiefroyo(WHICH IS FROYO BASED) but themed to look like honeycomb
just saying
Incorrect Version???
luigi90210:
I'm a little lost here.
Are you saying that NokieComb is actually *not* Android 3 based? That Froyo is actually an earlier Android version???
This is important for me to know, because my main reason for even looking at NookieComb was I was looking for a later Android version. I had thought that Froyo was based on Android 3. Was this an incorrect belief???
factor3 said:
luigi90210:
I'm a little lost here.
Are you saying that NokieComb is actually *not* Android 3 based? That Froyo is actually an earlier Android version???
This is important for me to know, because my main reason for even looking at NookieComb was I was looking for a later Android version. I had thought that Froyo was based on Android 3. Was this an incorrect belief???
Click to expand...
Click to collapse
No I was saying that Honeycomb wasn't OpenSourced until recently. NookieComb was based off of the Android 3.x SDK(SoftwareDevelopementKit) for Honeycomb and SDKs don't include alot of important pieces of code. IceCreamSandwich however has been OpenSourced and released under AOSP(AndroidOpenSouceProject) so it'll be much more stable within a few months of Devs working on it.
Here are Android versions by number:
2.1=Eclair(AOSP)
2.2=Froyo(AOSP)
2.3=Gingerbread(AOSP)
3.0/3.1/3.2=Honeycomb(Closed-Source Tablet Only)
4.0=IceCreamSandwich(AOSP)
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Japzone:
1. My last question wasn't directed at you. It was directed at luigi90210, who seems to be saying that no: Nookie Comb is not based on Honeycomb, but on Froyo.
2. And it sounds like you are incorrect. If what luigi90210 says is true, and if Froyo is actually the base for Nookie Comb, then Nookie Comb is actually based on Android 2.2 (since, as you point out, Froyo *is* Android 2.2).
3. My problem was that I didn't know what Froyo was. I only knew about Android 2 and Honeycomb -- I didn't know the names of the different point versions. As it turns out, what luigi90210 said is correct (since I first received the instructions that I was complaining about from the Nookie Comb Thread): Nookie Comb is, as its author says in the Nokie Comb thread, based on Froyo, not Honeycomb.
In actual fact, luigi90210 has given me the best reason for following your suggestion of switching to CM7: that Nookie Comb is based on an even earlier version of Android, meaning that there are actually no Honeycomb- based systems available for the Nook. There is, consequently, no reason for me not to go to CM7...
factor3 said:
In actual fact, luigi90210 has given me the best reason for following your suggestion of switching to CM7: that Nookie Comb is based on an even earlier version of Android, meaning that there are actually no Honeycomb- based systems available for the Nook. There is, consequently, no reason for me not to go to CM7...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=936995
is the honeycomb based rom for Nook. (though extremely buggy)
it's essentially at the same place as the ICS build but the ICS build is going to continue to improve.
Related
My head is aching with the sheer amount of information it is trying to process. I got a Nook Color about a month ago but have been putting off using it because I am still trying to figure out how to do what I want to do.
I've been going over the threads on the dev forum and after reading a lot of the threads, I still can't find exactly what I need (or maybe I've found it but I just haven't realized it yet).
My Nook Color is running latest official update from B&N (meaning 2.2 and B&N apps).
Anyway here's what I need:
1. I need to be able to dual boot into either HC or a rooted gingerbread-based version of android (is this the clockwork 7 thing?) solely from an SD card
2. Should not do anything to the Nooks internal memory (meaning: won't void warranty)
3. The dual boot manager, HC and and gingerbread-based version of android should all run on sd card. nothing will be placed/done on the nook (is this it? i'm so confused i'm not even sure anymore --- http://forum.xda-developers.com/showthread.php?t=1045018)
4. The dual boot manager will still have the ability to install other custom roms on to the sd card when i put the zip file of the image on to the sd card (something like this: http://forum.xda-developers.com/showthread.php?t=1000957)
5. Should have the overclock thingamajig
Anyway, are there any solutions to this? the "Dualboot Phiremod / Honeycomb Image for SDcard" seems the closest so far but I can't figure out if it installs a rom manager into the SD card with which I can install newer versions of the overclock kernel or newer versions of the custom ROMS based on HC preview or newer version of the CM7 nightly image. gaaaah.
Please help >_<. I promise I'm not stupid. This is just like information overload and I seriously am having a real headache (not just figuratively) right now.
Follow the thread below. From it, you can install plain CM7 (the best known gingerbread rom) strictly onto your SD card. If you have multiple cards, you can try out the different flavors of CM7:
CM7 Stable (latest is 7.0.3); OR
CM7 Nightly (latest is 76); OR
Beta CM7 .32 kernel, though this one is still has some bugs.
Phiremod is a themed CM7 which I haven't tried, while the above are more plain vanilla android. Also use a Sandisk card if you have one as they seem to have better overall speed regardless of Class, at least 2gb size or bigger.
http://forum.xda-developers.com/showthread.php?t=1000957
Hi LBN1, thanks for the quick reply.
Does this work process allow me to install HoneyComb as well as a separate boot option?
I just realized that I'm actually looking for an SD dual boot of HC and CM7 w/ OC. Does this exist? >.<
Oh, this process is not for a dual booting SD card. It allows a rom on a SD card, and then take out the SD card and you can boot to stock B&N software, so it is a quasi dual boot so to speak. There are some actual dual boot options out there but I don't have any experience with any of them...
Same thing with Honeycomb roms, never tried any of them since from what I read they are still in early, beta stages meaning they really don't work as well as CM7.
LBN1 said:
Oh, this process is not for a dual booting SD card. It allows a rom on a SD card, and then take out the SD card and you can boot to stock B&N software, so it is a quasi dual boot so to speak. There are some actual dual boot options out there but I don't have any experience with any of them...
Same thing with Honeycomb roms, never tried any of them since from what I read they are still in early, beta stages meaning they really don't work as well as CM7.
Click to expand...
Click to collapse
Hehe... yeah I kinda figured that out What I had in mind was something along the lines of dual booting HC/CM7 via SD card and removing the SD card if I wanted to boot to the stock 1.2 (so it's a quasi triple boot) >_<
But thanks for your help!
I think the easiest thing you can do right now is to try the Phiremod/Honeycomb Dual boot sd image which I see you already found out. It wont change or touch your internal system so you are safe. Also its already prepared for you so you just need to burn the img into the sd.
If inserted, the sd image will boot to either Phiremod (which is really a themed version of CM7 7.02 - with the update provided in the same thread or to Honeycomb). I use it and works quite well!!!! It is fast also (provided you use the recommended Sandisk class 4 sd card) as it is overclocked from the sd which you also want.
When I want to use stock BN I just boot without the sd and thats it! I also rooted the internal BN as well to add overclock to the stock BN 2.2 and it is quite snappy when OC to 1.1 mhz.
Hi Garoto! that's good to hear! can you point me to the thread for rooting the internal BN and adding overclock to the stock 2.2? i want to try that as well
pryonix said:
Hi Garoto! that's good to hear! can you point me to the thread for rooting the internal BN and adding overclock to the stock 2.2? i want to try that as well
Click to expand...
Click to collapse
Sure no problem:
1. To root the 1.2 version Nook just follow the steps in this thread, it is not as complicated as it sounds:
http://forum.xda-developers.com/showthread.php?t=1054027
2. To install the OC Kernel I used this thread. Pretty simple process. After you root , go to the market and install ROM manager, then do flash clockwork and then reboot to recovery, then do update from zip in sd card and flash the OC Kernel. I used the 1,1 mhz as it is stable and really speed things up:
http://forum.xda-developers.com/showthread.php?t=1064095
pryonix said:
Hi Garoto! that's good to hear! can you point me to the thread for rooting the internal BN and adding overclock to the stock 2.2? i want to try that as well
Click to expand...
Click to collapse
Keep in mind, overclocking definitely technically voids the warranty (as does rooting). Since you mentioned it. Just as bad as installing stuff on the internal EMMC.
greenmky said:
Keep in mind, overclocking definitely technically voids the warranty (as does rooting). Since you mentioned it. Just as bad as installing stuff on the internal EMMC.
Click to expand...
Click to collapse
Haha yup... just wanted to know as a "just in case I feel brave enough to void my warranty" haha!
I have a nook color rooted (1.1) and i am trying to figure out how to go to 1.2. what i dont understand is the distinction/differences between manual nooting to froyo (going back to stock, doing the B&N upgrade, then the manual nooter to reroot) VS using CM7. What are the differences, advantages, disadvantages... would either get me froyo? do i have to go back to stock for either? or is it just two different approaches to the same end. can anyone can point me to a place to read up on this without having to read the entire site would be highly appreciated. thanks
Try this
I autonooted my NC back in February and avoided the upgrade, renooter process waiting until a new autonooter program came out (which it has not). So about 2 weeks ago I tried verygreen's sd-card mount of CM7 together with Dalingren's OC kernel. It is fantastic! Not at all hard to do either.
The Nook application from the android market is better than the native version, and, of course, I am also running Kindle and about 20 apps.
So while I cannot really answer the specifics of your question, I can encourage your through my own personal experience to try what I did.
Good luck.
ddd22 said:
I have a nook color rooted (1.1) and i am trying to figure out how to go to 1.2. what i dont understand is the distinction/differences between manual nooting to froyo (going back to stock, doing the B&N upgrade, then the manual nooter to reroot) VS using CM7. What are the differences, advantages, disadvantages... would either get me froyo? do i have to go back to stock for either? or is it just two different approaches to the same end. can anyone can point me to a place to read up on this without having to read the entire site would be highly appreciated. thanks
Click to expand...
Click to collapse
CM7 is gingerbread, or Android 2.3 and is a whole new OS. Your current 1.1 is Eclair (Android 2.1) and the new 1.2 stock is actually Froyo (Android 2.2).
The best way to go to 1.2, if that is your destination, is to go back to stock first, then upgrade to 1.2 via B&N and then do manual nooter. There are instructions on that whole process in the manual nooter link.
If you want to go to CM7, there's no point in even talking about 1.2 - they are completely different animals. You can either use a dual boot, CM7 on an SD card, or flash CM7 directly to the nook. I've never messed with dual boot, but you'll need a bootable SD card for most of the above anyway (look in the CM7 link above or here)
Now - the differences...
CM7 is pretty much wide open. The devs pour a lot of time into it so it has bluetooth, usb hosting and all kinds of other stuff. However, it's a whole different interface and isn't really meant to be a reader (the B&N android market app/reader just don't cut it compared to the stock ones, by most accounts). I like to think of it as CM7 is a cheap tablet that can be a reader and rooted stock as a reader than can double as a tablet. Both have overclocking kernels.
Personally, I prefer rooted stock, which is what's on all 3 of the ones in my family. But to each his own. Hope that helps you...
Yes, I should just read the threads, but...
Anyone wanna comment on...
1) dualbooting (nooted) stock w/CM7 on SD card, vs 2) CM7 flashed to NC...
...and 3) dualbooting CM7 flashed to NC, with (nooted) 'stock' on SD card?
I believe I read you can put stock on the SD card? Can you put (nooted) stock on SD?
Is there much difference/advantage to running CM7 flashed vs on SD card?
(not talking about stock OS availability, just the CM7 installation method/residence.)
How much SD space used by OS? Any hardware diffs/limits besides perhaps speed?
If dualbooting with SD card... such as 32GB ...can you use full capacity for OS, apps, storage? whether CM7 or stock is on SD card.
With stock on the NC... it's neatly official/updatable/resellable, with extra value SD card(s).
With stock on SD, it's a fallback... for a modded added-value 90+% 'tablet'.
Guess I'd lean toward (nooted) stock on NC, with CM7 (etc!) on SD's... unless CM7 flashed to NC would operate USB/bluetooth... so much better...?
CM7 on SD card will run slower than internal. Depending on your SD card, it may or may not be acceptably slow.
Here is something for the best of both worlds:
http://forum.xda-developers.com/showthread.php?t=1156909
Or you can take the easy way and use stock for a few days. Then root it for a few days. And then try CM7 for a few. See which one you like most and keep it.
Ah, multi-boot...
Thanks for the multiboot link... now, there's a project. Have to take me NookC down for a bit... set aside time for that! Titanium bkp first. Test a spare SD card setup. Then plunge.
cm7 vs stock rooting
Thank you all.i set up cm7 on a16GB SD card and I would never go back. It is a much fuller and richer tablet experience. and bluetooth works though range is so short as to be unusable. starrting to get force close errors so I fixed permissions with root explorer which helped some. Now I have decided to flash cm7 to nook directly. speed has not been a problem but want to overclock... and other posts indicated that doing so will largely eliminate the fc errors.. the addiction begins. Thank you all again for the advice and encouragement. Btw one of the biggest pluses is that with cm7 I could install dsp and the sound from the speaker can now be easily heard. I actually h ave to turn it down sometimes because too loud if u can believe that!
Ok My wife bought me a nook color and I'd like to make it into a tablet. I found a video on youtube that has it running cm7 on a micro SD card but then then runs the stock NC software so as to not void the warranty.
I've tried reading the nook devs, and multiple how to's but feel a bit lost. Can someone point me to
1) step by step instructions even an idiot can follow
2) a link to the different mods and how they are different
3) where these mods are found.
I'd like a way to do this using free software. One place i found to just buy the mod on an SD card and just install it. One other place gave some instruction but needed software that had to be bought (unzippers or something along that line).
thanks for any information I'm feeling a bit overwhelmed..
Shaun
I started my NC journey by reading some good, but outdated, guide on how to do root and flash custom ROM to the NC. It took me some time to find the correct program to use.
manualnooter: http://forum.xda-developers.com/showthread.php?t=1054027
This post has a rather detailed instruction. Note that you will be installing a custom ROM onto NC and will void warranty... but you can also flash the stock ROM back to the NC in case you need to use that warranty so you don't really lose much.
I forgot which ROM the manualnooter procedure would install, but I think the current most popular and stable ROM is cyanogenmod 7.
Unfortunately the entire procedure will take beginners more than 10 hours to have a grasp on how to do things and maybe poking around and see why some things work that way.
Welcome!
I've personally installed CM7 to emmc (internal memory) using these steps:
http://forum.xda-developers.com/showpost.php?p=11452450&postcount=19
I was also using the microSD card method, and the steps below are good to follow:
http://forum.xda-developers.com/showthread.php?t=1000957
I would recommend using the latest nightly vs a labeled "stable" release. The nightlies have a lot of improvements and are in fact very stable these days. The only thing you'll need is a microSD card, a card reader, and a little bit of patience. It's really not hard, but just make sure to follow all of the steps. If you have any more questions, feel free to ask or search previous threads
I was considering a nightly build.. the nightly builds I need to find the encore build right? (wonder why we call these units encore). Secondly I was wondering if theres an option out there that allows a plain version of gingerbread without the cm7 markation all over the place. Is there functionality in the CM7 builds that I wouldn't get with a pure gingerbread build?
Yeah - encore is the codename for the Nook Color. I think it came from the initials NC....encore. You can always find them at
http://download.cyanogenmod.com/?device=encore
I'm actually not sure if there is a pure gingerbread rom out there. CM7 is based on the official release of GB, and adds some nice things for the nook -- one big one is the honeycomb style soft keys at the bottom since the NC doesn't have the normal android hardware keys.
For newbie, I strongly recommend installing and running CM7 off the uSD first.
Play with it for a while, get used to it, familiar with it while spending more time reading threads/posts in here then thinking about switching it to eMMC or rooted NC later.
Installing and running off uSD are much more simple and easier.
The requirement is: a good (SanDisk class 4 reported as very good) uSD, 8GB or 16GB.
Then follow this: http://forum.xda-developers.com/showthread.php?t=1000957
Cyanogen has this quirky little tradition of naming the software release after the original code name of the device. The Nook Color was code named "Project Encore" (http://www.droiddog.com/android-blog/2010/10/nook-color-likely-dropping-this-week-image-leaked/) by the developers, so the NC is the Encore in CM7. (Similarly, my old Motorola Cliq is called "Morrison" and my T-Mobile G2 is called "Vision")
And Stock Gingerbread doesn't have a number of things which are very useful for Tablets, such as the taskbar "soft buttons" for back, search, home, and menu, as well as the ability to put the taskbar on the bottom, and adjust the lock screen as you see fit. CM7 has all of these, plus the ever popular "much, much more!" The CM7 developers and mods have really outdone themselves and made the Nook Color a massively useful device.
votinh said:
For newbie, I strongly recommend installing and running CM7 off the uSD first.
Play with it for a while, get used to it, familiar with it while spending more time reading threads/posts in here then thinking about switching it to eMMC or rooted NC later.
Installing and running off uSD are much more simple and easier.
The requirement is: a good (SanDisk class 4 reported as very good) uSD, 8GB or 16GB.
Then follow this: http://forum.xda-developers.com/showthread.php?t=1000957
Click to expand...
Click to collapse
+1 This.
Follow the instructions in that link and you should have a working microSD CM7 installation. 3 things to add to those instructions though:
1.) Try using Win32DiskImager instead of WinImage. People have had problems writing the image with WinImage. The only problem I've seen reported with Win32DiskImager is that sometimes you cannot create a good usable image of a disk greater than 4GB.
2.) If you are looking for a good usable card, get this one. It includes a good USB microSD reader to use when writing the image.
3.) This one is optional. The default SD card image writes an approximately 120MB boot partition to the microSD. With the latest nightly releases of CM7 you can run into issues if you are trying to install both CM7 and gapps at the same time. It is recommended to resize the initial partition upwards in size. Some folks put it over a GB but in my mind a few hundred MB should be fine. The most popular tool to do this with is EASUS Partition Master. I haven't personally done this since it is something that has to be done before the initial install and I had mine up and running before running into this problem.
- Aerlock
oI bought a microSD from merit line. Its an ADATA BRAND 16GB CLASS 10. it had good reviews and some places I read to stay with above a class 6 or better. I hope this doesn't cause a problem or my wife will be upset... LOL
I was watching a video on youtube about this process and they mentioned not having all the memory on the microSD available due to the partitions. they used the same partition manager to maximize the storage on the card. Will this be needed or does something happen automatically to use make all the uSD card usable?
With that brand, with that speed, keep all of your fingers crossed and prayed.
And after few weeks of enjoy the CM7, if you start seeing weird things, you then can start blaming the uSD.
does it matter what version software i start with? I've been reading around and see everything from making sure that your on 1.0.1 to 1.3? I'm lost?
Also since I'm wanting to do this all on the MicroSD then this may not be an issue but I've heard some say also to log on first and make sure I sign in with barnes and noble before doing anything. is that important or not?
Lastly. does rooting or anything leave a permanent record in turn voiding warranty or can it be taken back so the factory doesn't know.
Rooting does not leave any records. All you need is to return to factory stock before sending in for warranty
ok I've tried the version 1.3 over and over and each time I get the same problem. after reboot it comes to the blue android on a skateboard it it just keeps running in circles. it will go black occasionally but then right back to the android on the skate board.. what might I have done wrong?
I used the installer in verygreens 1.3 posts and cm_encore_full-209 nightly build
calixt0 said:
ok I've tried the version 1.3 over and over and each time I get the same problem. after reboot it comes to the blue android on a skateboard it it just keeps running in circles. it will go black occasionally but then right back to the android on the skate board.. what might I have done wrong?
I used the installer in verygreens 1.3 posts and cm_encore_full-209 nightly build
Click to expand...
Click to collapse
Lets test that card and make sure it's gonna work. Go here and get Crystal Disk Mark. Install it and plug your microSD card into your computer. Run the default tests and post them here. We're looking for the 4k read/write speeds in particular. If they aren't around 1.0 then you're likely to have a problem running CM7 off the card.
My suspicion is that since its a Class 10 card it's optimized for large block writes and not small block writes. Card manufacturers will trade off small block write speed to get the higher class ratings instead of going for overall speed. SanDisk seems to be the exception to this in that they do not tweak their cards to get the high speeds which why they're the recommended card for SD install of CM7.
- Aerlock
Hi,
I just bought a nook color. I'm trying to install nightly cm9 on it. i have been reading and i have some questions .. please help i don't wanna turn my new nook into paperweight lol. I understand i need to make a bootable sd card with CWR on it. i understand there are newer version CWR out there now but I am only able to find 4gb version of 3.0.2.8. Will that cause a problem ? Do i have to use 4gb version CWR? I can find 1gb CWM 3.2.0.1 ( i have a 4g micro sd card ). About wiping, i know with android phones you always wipe before you flash roms but i have been reading, posts suggest to wipe cach and dalvik AFTER flashing cm and gapps. Is that the correct order to wipe? [GUIDE] Install CM7 or CM9(!) + Clockworkmod to EMMC - ALL NOOKS! (Updated:1/16/12) - xda-developers This post don't even mention wiping dalvik. So what exactly should i wipe and in what order? Also in that post it says after you flash, without rebooting you are to remove sd card and format it on a computer... since its a bootable CRW, the nook color doesnt even have the recovery on it , will removing the sd just cause it to crush ? Please help ~ Thank you.
Best advice is to go to the "development forum" and read the CM9/ICS nightly thread.Everything you need is in the first post.I would suggest you test your SD card with CrystalDiskMark 3.0(free program,google it up)first to see if it is suitable for a ROM install.
See the SD card strange thread in this forum first.
Don't worry too much about bricking your Nook Color. It is pretty much impossible to get it in a state which you can't recover from as it has priority on booting from the SD card.
That's not say you shouldn't try to get it right to avoid any hassle.
For an internal install use the Eyeballer SD clockwork recovery method as detailed in the development forum. When you image this to an SD then you always end up with a 1GB partition on the card irrespective of the real SD size. Don't worry about that as this is just a staging post and you just need space to put on the zips you want to install.
For CM9 use the "unofficial" nightly builds and put the main ROM, Gapps, and the telephony permissions fix on.
When you boot from this card you will be in Clockwork recovery. First time you want to format system, data, and cache then install ROM, Gapps and telephony fix in that order.
After that you want to put in a cleanly formatted single partition SD card, either by reformatting partitioning the installation one or a different one if you wanted to keep the original. It won't crash but some apps expect the Sd card to be present.
Once rebooted then you should be in CM9. You can install clockwork recovery to the internal memory as well by using the ROM Manager app. This means that if you reboot with the N key held down you get into a boot menu and can choose to go into recovery. That is very convenient for subsequent updates as you can just copy zips onto the SD card via USB or Wifi without having to remove the card (ES File Explorr app helps a lot here).
For small updates you can normally just format system and cache then reapply the set of zips. This will leave your set up and installed apps alone. You don't need to do Dalvik separately as it is in the cache partition.
Thanks and what is the "telephony permission fix" ?
bobtidey said:
Don't worry too much about bricking your Nook Color. It is pretty much impossible to get it in a state which you can't recover from as it has priority on booting from the SD card.
That's not say you shouldn't try to get it right to avoid any hassle.
For an internal install use the Eyeballer SD clockwork recovery method as detailed in the development forum. When you image this to an SD then you always end up with a 1GB partition on the card irrespective of the real SD size. Don't worry about that as this is just a staging post and you just need space to put on the zips you want to install.
For CM9 use the "unofficial" nightly builds and put the main ROM, Gapps, and the telephony permissions fix on.
When you boot from this card you will be in Clockwork recovery. First time you want to format system, data, and cache then install ROM, Gapps and telephony fix in that order.
After that you want to put in a cleanly formatted single partition SD card, either by reformatting partitioning the installation one or a different one if you wanted to keep the original. It won't crash but some apps expect the Sd card to be present.
Once rebooted then you should be in CM9. You can install clockwork recovery to the internal memory as well by using the ROM Manager app. This means that if you reboot with the N key held down you get into a boot menu and can choose to go into recovery. That is very convenient for subsequent updates as you can just copy zips onto the SD card via USB or Wifi without having to remove the card (ES File Explorr app helps a lot here).
For small updates you can normally just format system and cache then reapply the set of zips. This will leave your set up and installed apps alone. You don't need to do Dalvik separately as it is in the cache partition.
Click to expand...
Click to collapse
Found the telephony fix thanks
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
You might consider simply using the SD card boot ROM's, and leaving the internal Nook alone for the present. That would allow you to try out the various Rom's available and find one that works best for you. I'm currently running CM7.2 Kang on my emmc partition, but booting on SD card from the CM9 nightly builds. The CM7.2 Kang is quite stable, but not as much fun as the alpha ICS CM9 stuff. Best of both worlds.
I already have cm7 on my phone , hopefully its not gonna be the same thing lol . i was hoping to put cm9 on there so it will entertain me for a while but if its really that buggy mb i will consider just running on cm7.
mr72 said:
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
Click to expand...
Click to collapse
Thanks. I already have bobzhome 7.2 on my phone. The reason why i wanna cm* on my nook is because i don't read(i read enough for school XD ) haha so the nook factory rom will be kinda pointless for me. Also just booting from sd and flashing roms seem really straight forward to me so that's why i want to flash cm* on internal memory. As im not that knowledgeble about nook colors, running on a bootable rom still seem complicated for me but i sure will think about it .
brentb636 said:
You might consider simply using the SD card boot ROM's, and leaving the internal Nook alone for the present. That would allow you to try out the various Rom's available and find one that works best for you. I'm currently running CM7.2 Kang on my emmc partition, but booting on SD card from the CM9 nightly builds. The CM7.2 Kang is quite stable, but not as much fun as the alpha ICS CM9 stuff. Best of both worlds.
Click to expand...
Click to collapse
when i was downloading cm7 roms , my anti virus kept saying there were viruses in the roms ... is that normal ?
optimusv45 said:
when i was downloading cm7 roms , my anti virus kept saying there were viruses in the roms ... is that normal ?
Click to expand...
Click to collapse
How many places you going to ask this?
It is a false positive.
Normal? No. Crappy antivirus? Yes.
As long as you are downloading from links from the developers here you're safe.
Sent from my NookColor using XDA App
just making sure since im not very knowledge about nook colors. i rather ask more than do something stupid on my device and cause myself problems.
Benzoman said:
How many places you going to ask this?
It is a false positive.
Normal? No. Crappy antivirus? Yes.
As long as you are downloading from links from the developers here you're safe.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
No problem. Just noticed it was in a separate thread already.
Please post what A/V you are talking about so others having the same issue will take note.
I'll also give a +1 to the people who suggested that you work off an SD card until you are really comfortable with the process. You can always recover your Nook, but why go through that hassle when the SD card is so easy.
Just my $.02
Dual booting SD
I agree with try the Dual boot off the SD card to see what you like. Check out http://forum.xda-developers.com/showthread.php?t=1000957Verygreens process was simple to follow and I am newer at rooting also. Cheers.
I posted what a/v already. its kaspersky internet security. i guess i never look into running off SD. I don't read much so i just don't need nook color stock ROM, i guess that's also part of why i wanna run on internal memory. oh and i bought a refurbished nook color from BNs website and it came defective. part of the screen didn't work. To those who wanna buy it from them i suggest to buy from a retail store so u don't have to pay shipping and waste time I think all they did was a factory restore on a return and sell it again for 149.
TL2000 said:
Please post what A/V you are talking about so others having the same issue will take note.
I'll also give a +1 to the people who suggested that you work off an SD card until you are really comfortable with the process. You can always recover your Nook, but why go through that hassle when the SD card is so easy.
Just my $.02
Click to expand...
Click to collapse
Im gonna buy a new nook color and i read that newer ones have different hardware. newer hardware aren't supported by CM7. I guess I'll have to try a nightly CM9 build.
The1Power said:
I agree with try the Dual boot off the SD card to see what you like. Check out http://forum.xda-developers.com/showthread.php?t=1000957Verygreens process was simple to follow and I am newer at rooting also. Cheers.
Click to expand...
Click to collapse
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
mr72 said:
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
Click to expand...
Click to collapse
optimusv45 said:
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
Click to expand...
Click to collapse
I just bought my nook color Dec. 30th, 2011 and I have ran cm7 as well as cm9. Like the others are saying, set up cm7 off of a SD card until you learn what you are doing then consider moving to the emmc.
optimusv45 said:
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
Click to expand...
Click to collapse
I believe that is CM9, not 7 that was having issues with the new nook color touch screen drivers.
Here's a post about it:http://forum.xda-developers.com/showthread.php?p=21333209&highlight=touchscreen#post21333209
Looks like it may already be fixed: http://forum.xda-developers.com/showthread.php?p=21353661&highlight=touchscreen#post21353661
I have seen instructions on how to apply CM9/ICS to eMMC and to also set up a dual boot sd card that contains it.
I would prefer at this point to set up an sd card with the most recent and/or stable nightly CM9/ICS only to see what it is all about and what the state of development is.
Could someone provide me with that info, please?
FYI: I am running my original NC having updated my v 1.3 with 5.12.20 instead of going the 1.4.1 route. It pretty much works in terms of my usage and I got the added benefit of having HBO Go work! Still not willing to give up my ability to "read in store".
Thanks in advance for any/all help with this
All the info is here. You just have to read, read some more, and then just read some more.
It all gets so much easier if you do this. Plus you'll find the threads you want to keep an eye on for new info.
Sent from my GT-P7510 using Tapatalk
Use the size-agnostic procedure that discusses putting CM7 on an SD card.. just rename the zip file to be compatible for flash. It is in the Dev section
Benzoman said:
All the info is here. You just have to read, read some more, and then just read some more.
It all gets so much easier if you do this. Plus you'll find the threads you want to keep an eye on for new info.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Having done numerous iterations of various CM and others both internally and on sd cards, I was able to do all of that because I do read this website rather thoroughly!
However, doing this specific task (as a standalone) just did not appear to come up.
I had assumed I could do it the same way I had done CM7 but was not certain due to apps and other issues at this stage.
davidr415 said:
Use the size-agnostic procedure that discusses putting CM7 on an SD card.. just rename the zip file to be compatible for flash. It is in the Dev section
Click to expand...
Click to collapse
Thanks...any suggestions for which version to try?
Just get the latest nightly on the samiam303 post. http://forum.xda-developers.com/showthread.php?t=1444943At this point there is nothing that is "stable". Make sure you use the large ics image or you'll need to expand boot. Finally I found I had to load the update and gaaps at the same time without a recovery boot in between to get the google calendar to sync. Runs real nice.
If I may suggest, try Racks triple boot of CM7 and CM9 from SD card -- see his thread
elsewhere on XDA -- I've been running it for several weeks, including latest update fro OC, and everything works fine. ICS is of course still "in process" but you might be surprised at how well it runs. And the CM7 is stable as a rock and swift, especially with the supercharger script installed. And you will still have your original B&N stock in emcc.
Thanks...I saw that and since I had already used CM7 off and on both internally and via an sdcard just didn't want to get into another dual boot scenario.
This time around, I just wanted a simple ICS steup on a dedicated sdcard that I would install when wanting to try it out and replace with my storage sdcard when operating normally with my rooted (5.12.20) 1.3.