Related
I don't understand what's going on. I am not a noob; I've rooted 10+ android devices and have been in the mobile game since windows mobile 5.
I follow all instructions to the T from here
http://nookdevs.com/NookColor_Rooting
Everything goes as it should until it is time for the final reboot. Instead of displaying a new boot animation, it simply gets stuck at the screen with the lowercase "n" that says the blurb about adobe at the bottom.
Same both with the SD card in, and without it.
I am able to salvage the situation by doing the 8 interrupted boot plus the homescreen and power key. Started from scratch again - updated to 1.01, reflashed the sd card, etc.
Same result. This is a brand new device, just bought today.
Any ideas? You don't think they killed the root exploit, do you?
I believe I just figured out the problem. The link in the WIKI to the B&N 1.01 update is outdated and incorrect - it links to the incompatible 1.1 update instead, which is not autonooter supported.
Those instructions worked for me. It sounds as if your boot partition is completely empty. Are you using Auto-nooter 2.12.25? That is the version you need to use if your NC is already running 1.0.1.
edit:
Just saw your update. In that case in the B&N link replace 1.1.0 with 1.0.1 eg:
http://images.barnesandnoble.com/presources/download/nookcolor/v1.1/Sideload_update.zip
should be:
http://images.barnesandnoble.com/presources/download/nookcolor/v1.0.1/Sideload_update.zip
otherwise there are a couple other threads where people have thrown up the 1.0.1 sideload update.
computerpro3 said:
I believe I just figured out the problem. The link in the WIKI to the B&N 1.01 update is outdated and incorrect - it links to the incompatible 1.1 update instead, which is not autonooter supported.
Click to expand...
Click to collapse
The link has not changed, the B&N reference within it has. But perhaps something should be tweaked on the URL for now, or the instructions. Done.
Today B&N launched their latest update for the Nook Color and it's a Big one. It includes Android 2.2!
I'll be updating once I'm done here as I have unrooted stock for this very purpose. I'll be back with my opinions on what it's like. For now, if you have Unrooted stock you can update from the URL below. Everyone else, drool over the Update's details and imagine what this could do for our Custom ROMs.
Update page:
http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/?cds2Pid=35758
Details:
The NOOK Color Ver1.2.0 update contains new features and enhancements, including:
Access to shop a broad collection of popular NOOK Apps to enjoy great games, stay up to date on news and weather, and more
Full-featured free email to check and send web-based email (i.e., Yahoo, Gmail, Hotmail, AOL) all from one in-box
NOOK Color’s update to Android OS 2.2/Froyo offers system improvements, browser performance and a more complete Web experience giving customers access to enjoy even more video, interactive and animated content. NOOK Color now includes support for Adobe Flash Player
NOOK Kids exciting new Read and Play titles that bring animation, activities and stories together
NOOK Books Enhanced offer in-page video and audio in a growing number of titles
Enhancements to magazine navigation making it easier to enjoy even more of the growing selection of magazines in NOOK Newsstand
NOOK Friends (beta) to see your friends’ reading activities, swap books with LendMe, share recommendations and discover new titles
____________________________________________________
Sent from NookColor CM7 using Tapatalk
Does it have copy and paste for text fields?
Can you still boot to SD card? that is all I care about.
I want to know too did anyone confirm this?
is the zip off their website cwm flashable? i would assume not...
GorillaPimp said:
Does it have copy and paste for text fields?
Click to expand...
Click to collapse
Yes.
danbutter said:
Can you still boot to SD card? that is all I care about.
Click to expand...
Click to collapse
Yes. Dual booting with CM7 still works fine.
john10101 said:
is the zip off their website cwm flashable? i would assume not...
Click to expand...
Click to collapse
No.
Waiting for root.
epakrat75 said:
Yes. Dual booting with CM7 still works fine.
Click to expand...
Click to collapse
Sweet. I can not wait to update. CM7 runs perfectly off my Sandisk Class 4 8GB card, so even if they have blocked rooting, I am still willing to update. That said, as long as they allow dual booting, rooting should always be possible.
picopir8 said:
Sweet. I can not wait to update. CM7 runs perfectly off my Sandisk Class 4 8GB card, so even if they have blocked rooting, I am still willing to update. That said, as long as they allow dual booting, rooting should always be possible.
Click to expand...
Click to collapse
Dual booting from SD card is wired into the hardware, there is nothing they can do in software to stop it.
Will Rooted NC get the update?
I have rooted my NC.
I followed instructions for directly applying update with no luck.
Am I correct that the rooted NC will not receive update and that I must return to stock before I can get the new update?
PS If this is true, what is it about the rooted NC that prevents the update?
kernel version?
Can anyone post the kernel version after the update please?
leorob said:
I have rooted my NC.
I followed instructions for directly applying update with no luck.
Am I correct that the rooted NC will not receive update and that I must return to stock before I can get the new update?
PS If this is true, what is it about the rooted NC that prevents the update?
Click to expand...
Click to collapse
I would suggest flashing back to stock, re-register then applying the update from B&N. (That should remove the root) That what I am doing for a few people at work. Will report back on progress but logically that should work.
What's the point of going to 1.2 if it's not rooted yet?
Some important information from another Forum:
Successful download of update and install
File name: nookcolor_1_2_update.zip
File size: 190 MB (199,715,879 bytes) Size on disk: 190 MB (199,716,864 bytes)
MD5 checksum: D0B6323258F2793D19A1C9286E2AB753
Click to expand...
Click to collapse
if your 1.2 update fails, check the MD5 on the file against this one. If it is different, your downloaded update file is corrupt.
If I am rooted on just stock 1.1 using one of the autnooter methods what can I do to just flash back to stock and lose root. I saw one thread in the developer forum with a stock 1.1 zip file and figured I could try that. I do not mind losing root as I haven't really been keeping up with all the different roms being released lately and will be using it more for just reading books. Here is the thread I am referring to:
http://forum.xda-developers.com/showthread.php?t=945838
Stock 1.1 file works
I was rooted on 1.1 and installed the stock 1.1 file you refer to.
All went well and I was returned to stock 1.1.
Followed Barnes and Noble instructions for the downloaded update and file was recognized as soon as unit went to sleep.
Installation happened automatically and now I am at 1.2.
The kernel is 2.6.32.9... the os is froyo.
leorob said:
I have rooted my NC.
I followed instructions for directly applying update with no luck.
Am I correct that the rooted NC will not receive update and that I must return to stock before I can get the new update?
PS If this is true, what is it about the rooted NC that prevents the update?
Click to expand...
Click to collapse
I tried to install the update over an Autonootered 1.1. All that happened was the device rebooted and the update.zip file was deleted from the nook. I presume that I need to flash it back to an original version and then install the upgrade. I was hoping I could just layer this update on top of what I have so I wouldn't lose apps that are already installed.
If you have not modified anything after Autonooter, simply following the directions in the 'Flash back to clean stock ROM' wiki and you'll be presented with an out-of-the-box booting NC. After that, simply follow the 'Manual Download Instructions' posted at the Barnes & Noble website to update your NC to the official new stock v1.2.0 ROM.
If you're having trouble updating your NC with Unrooted Stock like me then here's what you need to do. You'll have to reflash to Factory Defaults.
Perform Step 1, Method 1; then Step 2, Method 1
http://nookdevs.com/Flash_back_to_clean_stock_ROM
This Reinstalls Stock v1.0 to System partition and then wipes your Data and EMMC partitions. You must perform both steps otherwise it won't work correctly.
Start up Your Nook and follow the Setup. Now download the Update ZIP and drop it on your EMMC's root. Tap the Power button to put the Nook to Sleep. Now Sit back as the Update is installed Automatically.
____________________________________________________
Sent from NookColor CM7 using Tapatalk
So I decided to root the nook this weekend and I'm having some issues that I can't get around.
I've rooted and ROM'd a few droids so far without an issue. I'm not an expert but I'm also not a noob.
I built up a bootable 1gb CWM and loaded up manualnooter-4-5-18 and manualnooter-4-6-16. CWM was pretty simple, and allowed me to load both of them up without an issue. (I've done both with and without a full wipe)
Once it reboots, it's perfect. market works, web works, rom manager permission fixes..everything works well.
The issue is once I power it off and back on, it's done. It hangs at the "Nook Color" splash screen (After the Read Everywhere and big grey N) and refuses to power up the OS. The onyl way i can get it back is to do a complete factory restore (power+vol button+N)
What am I doing wrong?
It sounds like you are suffering from the Flash / Air lockup problem. If you search the forums, there are links to download the zips that fix the issue.
I would also go to CWM 3.2.0.1 2.8 is rather old and 0.1 is a much easier experience especially on the new nooks.
I rooted two new nooks for my friend's kids Christmas presents last week. I used 3.2.0.1, Nooter 4-6-16 and used the adobe flash and air fixes and it went smooth.
Check this thread concerning the flash fix:
http://forum.xda-developers.com/showthread.php?t=1208896
Props to GMPOWER for his published answer.
Hope it works for you.
Ok cool, thanks OrionLTD. That sounds like my EXACT issue.
“jaromrnelson” continued the project, and has a more up to date version at the link below. His updated one will fix Adobe flash and Adobe Air. Once the fix has been applied, you should not have a problem whenever they update again.
LINK
Thanks GMPOWER, I'll try that one tonight.
Well... I tried these methods and I'm still boot looping as soon as Adobe updates from the Market.
el_bobbo said:
Well... I tried these methods and I'm still boot looping as soon as Adobe updates from the Market.
Click to expand...
Click to collapse
Take a look at http://forum.xda-developers.com/showpost.php?p=20456719&postcount=1631
Wiping and updating to 1.4.1 followed by the above should do nicely. It's working beyond expectations for me and some others.
That worked for me as well!
Although I had the old market at first after root.
I erased and deregistered and registered again and then applied the root 5-12-20 again and have newest market and so far so good, all is well
I might give that one a whirl, thanks guys.
The issue I had is that a newer version of Adobe had come out since GMPOWER's zip was released. There was another link in that thread to a newer zip (From another member) that ultimately resolved the issue.
There was one fix for boot loop involving Titanium backup, I used that one and never had the problem again.
I think that may be the one you are referring to?
Nook Rooting 101
Author’s Note: This may be long, but it provides useful info to those considering Rooting their Nook. It does NOT tell you how to root your Nook. (A sequel is intended to provide that information. But let’s start with this one.)
To the experts: feel free to post with your corrections and condemnations. The hope is that it will be improved and eventually turned into a Sticky for those new to the forum and the process.
“I got a new Nook for my birthday. What’s all this stuff about rooting?”
The Barnes & Noble Nook eReaders share some of the same electronic architecture as many smart phones and tablets. These devices work using the Android Operating system. The factory installed OS (Operating System) of the Nook limits many of the possible advanced features since it was designed primarily to be a reader. Some tech-savvy programmers have learned how to root the Nook devices to more closely emulate advanced features found on many of the Android devices.
Quick detour: Those wanting to root their Nooks are going to run into a lot of terminology. Here is a link to a glossary of many of these terms.
http://www.acertabletforum.com/foru...-dummies-guide-android-terminology-lingo.html
The number of terms addressed within this post will be a much smaller number. But these are terms that you really should understand before attempting to make changes in your Nook.
What is Rooting?
The term “root” comes from the Unix/Linux world and is used to describe a user who has “Superuser” rights or permissions to all the files and programs in the software OS. Regular users can use the software, but cannot make changes. Superuser privileges allow changes to the software code on the device.
“Rooting” means obtaining “superuser” rights to your Nook’s software. You gain the ability to load custom ROMs, install custom themes, increase performance, increase battery life, and the ability to install software that would otherwise cost extra. Rooting is essentially “hacking” your Nook.
ROMs
A stock ROM is the version of the device’s operating system that comes loaded on it when you buy it. The Nook Readers have a stock ROM.
A custom ROM is a fully standalone version of the OS, including the kernel (which makes everything run), apps, services, etc - everything you need to operate the device, except it's customized by someone in some way..
So what does the "customized" part mean? Since Android is open source, developers are free to take stock ROMs, modify them, remove garbage, optimize them, add things, and pretty much do whatever their imagination and skills allow. (And just so you know, they can also write bad programming too.)
Kernals
Another word you’ll frequently see on this site is kernel. Your Nook’s kernel controls much of the communication between the various electronic parts of the unit. An analogy is that the kernel is like programming stored in the Read Only Memory found on desktop and laptop computers. Think of the BIOS (Binary Input Output System). Some portions of the settings in this memory can be changed, such as when you install a hard disk drive. BIOS also allow other settings to be adjusted to suit the preferences of various users. But other portions of the BIOS should not be changed or your computer’s electronics cannot communicate with one another.
That is a pretty close approximation to how the kernel on your Nook is setup. Some portions of the programming were set at the factory and should not be changed. But other portions of the programming can be changed. And updates to the programming for kernels are made available.
Many of the custom ROMS you can load on your Nook will make at least some changes within the kernel of your unit. Just as there are various versions of the custom ROMs. There are versions of the programming for kernels as well. Let’s stop there for now. The subject can quickly get pretty deep. That should be enough for now.
Two Approaches
Some people who want to use one of these custom ROM systems on their Nook just install the MOD on a SD chip. (SD stands for Secure Digital.) All current Nook readers accept a Micro SD chip. A custom ROM can be loaded onto your Nook from this SD chip. Some people choose to Root their Nook with the Android Operating System operating from the SD chip. Then by powering down the Nook, they can remove the SD card. They can then restart their Nook and the regular Barnes & Noble system will operate.
At least some of the custom ROMs allow users to select whether to run the operating system (ROM) installed on the SD card, or run the native Nook operating system. You don’t need to go through the process of inserting or removing the SD card to change the OS. A series of keys are pressed as the Nook is starting to select the ROM you want it to run. This is called dual booting.
The other method of rooting consists of loading the custom ROM into the emmc. (This stands for Embedded Multi- Media Card.) This is the flash memory of your Nook that contains the original Barnes & Noble operating system. Loading the ROM into the emmc means the original B & N operating system is no longer available to run. Many advanced users report the ROMs operate a bit faster and that there are fewer problems when the Nook is run in this manner. But do remember that this means the original operating system on your Nook will no longer run. There are instructions located on this site that include steps to re-install the original system. So, this may not be as drastic a step as it might seem at first glance. There are also programs which will allow you to save all the data settings – including the OS settings currently loaded on your Nook so they can be restored later. That will not be covered in this post.
Those totally new and unfamiliar with Rooting may find it a little safer to use the SD chip method. As they gain more experience and know better what they are doing they may decide to venture out and try the emmc method for the potential advantages this method offers.
The Downside Of Custom ROMs
Of course, there are dangers of using custom ROMs which you should be aware of.
You May Void Your Warranty
As long as we’re talking about risks, this one needs to be mentioned. It's possible that custom rooting might void your warranty. The manufacturer might be able to tell that the Nook has had a custom ROM installed and not honor the warranty, in case you need to use it. Barnes & Noble hasn’t acted hostile to rooting yet, but that could change.
Something Could Go Wrong
First of all, something may go wrong with the flashing process (that's the process of installing a custom ROM) and leave your Nook in a bricked state. A Bricked Nook means it won’t operate. The chances of this are relatively low – especially if you use the SD chip method. And most of the time you can restore your Nook back to normal. Please take note of the phrase “most of the time”. You should understand that a bricked Nook is a possibility that can happen.
Try to go for a custom ROM that has been tested by time and has lots of positive feedback from users on this site. You are more likely to be successful with such a ROM.
Other Potential Problems
Custom ROMs could have bugs. Bugs are mistakes in the programming. Some are minor and won’t cause big problems. But others can be more serious.
There are appropriate locations on this site where you can post problems due to bugs. Those who post in the ROM forum will likely get an answer back and the bug will probably be acknowledged. Experienced users may even suggest methods to fix the problem.
So What‘s the Bottom Line?
Many of the people at this site have determined that the potential benefits of running these custom ROMs outweigh the risks. There are lots of experienced people here who will offer their advice if you decide to try this. But it is ultimately your responsibility to consider the risks and benefits in deciding what to do.
Quick detour: Let’s be realistic. Your Nook is never going to be an I-Phone. It was designed to be an eReader. (So was the Kindle.) Rooting can add features and capabilities to your Nook that Barnes & Noble probably won’t ever include in their stock ROMs. But rooting won’t really turn your Nook into a smart phone.
“But there are so many choices!”
Yes there are. Let’s try to understand why this is a good thing. Apple and Microsoft own the rights and hold patents on their operating systems. They jealously guard their secrets and strictly enforce their patents. And they make money selling their operating systems.
Unix is also a patented operating system. Linux is an open source operating system based on Unix. It isn’t really owned by anyone. The concept allows many users to tinker with it to improve it. The Android operating system is loosely based on Linux and is also open-source. Developers take stock ROMs and modify them to create their own unique versions. Developers of custom ROMs are able ptimize the software, unlock built-in features, and create an even better version of the Android software. The Android developers who make these custom ROMs release the software to the general public free of charge. We are fortunate to have these developers constantly working and freely sharing these custom ROMs available to everyone.
Stable versus Cool
Since ROMs are constantly being developed by many people, there are multiple flavors of ROMs available to us. Anyone who has ever done any programming knows that sometimes your new code fixes one problem but creates others. Programmers generally call these bugs.
A major portion of the ROMs may work OK, but there may be bugs in portions of the code. Groups of developers collaborate and post their versions of a MOD to be checked out and tested by other users to discover and fix all the bugs.
Then there are some general flavors of the Android system that have become established and are recognized by many. Let’s consider a few of those since you will see these mentioned frequently on this site.
Since April 2009, each Android version has been developed using a codename based on a dessert item. Released in alphabetical order, the names were Cupcake, Donut, Éclair, Froyo, Gingerbread, Honeycomb and Ice Cream Sandwich.
The Android versions distributed within the lifetime of the Nook include:
o Android 2.1 (codename Eclair)
o Android 2.2 (codename Froyo)
o Android 2.3 (codename Gingerbread)
o Android 3.0 (codename Honeycomb)
Quick detour: One further issue confusing to nubes is that at least some people will refer to a MOD by its Android number, example: 2.3. Others will use a number related to its codename, example CM7.0. Remember these people are really into this stuff. These numbers and differences really stick in their heads. Rule of thumb, if the number is below 4, it’s probably the Android number.
Let’s look at these individually. We’ll use the codenames in this list.
Eclair
Eclair is what your Barnes & Noble Nook Color runs as delivered. And even they are replacing it with Froyo.
Froyo
Many consider Froyo an improvement over Éclair. It has been in use for some time and is considered a stable platform for the Nook. Barnes & Noble is currently (as of 2/5/2012) loading this system using a method called push to update Nooks to run a stripped down version of Froyo. It is important to understand that the B & N version does not have all the features of some of the custom Froyo ROMs.
Gingerbread
The Gingerbread version that many people use has become known as CyanogenMod 7. That’s right – sometimes the system is called Gingerbread and sometimes it is called CyanogenMod 7, though many just refer to it as CM7. It was developed from the official Android Gingerbread source code, but was modified for many smart phones. There are many versions of this that will run on Nooks of various kinds. As of this writing, many consider this a good choice for a Nook operating system. It blends many recent features with at least some degree of stability. The CM 7 releases includes Bluetooth support for the Nook, meaning that you can use Bluetooth keyboards and headsets! It should be noted that Bluetooth support is still evolving.
Honeycomb
This Android system first showed up on the Motorola Xoom tablet. It offers some new features, but has not been released by the official development community. Because such development is constantly underway, some may post test versions for downloading. Be careful! This ROM is still very much in the developmental process. As an example, a few developers have been trying to take features of Honeycomb and include them in updated versions of Gingerbread. One of these versions has been given its own name: phiremod nook.
Generally, Éclair and Froyo, are considered to be stable and mostly bug free. Some versions of Gingerbread are close to being bug free, while other Gingerbread versions are still being sliced, diced, tweaked and tested. Honeycomb is still being tested. If this post stays on this site for a few months, there may be newer and more stable versions of Gingerbread. Or a stable version of Honeycomb for the Nook may become available. And some are experimenting with newer Android systems, like one called IceCreamSandwich. (Remember that this is being written in February of 2012.)
FYI: there are even new flavors of these general ROMS. There is also CM7.1 and CM7.2. And there is a version out there called CM9. So the development community is hard at work tinkering and tweaking.
Finally, as you start to explore and consider MODs for your Nook, you will often see some of these letters in the names of custom MODs.
Stable versions are those where all known issues have been addressed and resolved. This version is for everyday use.
-test / -RC versions are similar to the experimental versions, but are in the final stages of testing before being declared as "stable". There may be a few bugs left, but this version is usually stable enough for everyday use.
Experimental / -alpha versions are those where new features are being added, modified, and tweaked, and there are known bugs that are being worked on. This version is for beta / alpha testers.
Nightly builds are daily compiled builds from source. This version therefore has the latest features & tweaks, but it is also the mostly likely to have bugs and issues. These versions are probably poor choices for nubes.
So which do you want to use? Éclair came on your Nook. And currently, Barnes and Noble is pushing their stock version of Froyo out over the Internet automatically to your Nook. Gingerbread – going by the name of CyanogenMod7.0 – may be a good choice for starting out, as of the date of this writing. Yes, you can upgrade this to later versions as you become familiar with what is out there and how to root your Nook.
End of the lesson.
Hope this information was helpful. Happy Rooting!
Great info, and sure to be helpful to many. Here are a some suggestions:
A description of CM versions might be helpful, linking CM versions to Android versions.
CM 7.1 is the latest stable. You might mention nightlies, and the 7.2 RC0 Mirage release.
No mention of ICS? With all the buzz lately, I'd definitely include it in the list of Android versions, and mention it with CM9.
I think there are three choices:
Root stock B&N firmware.
Dual-boot with CM (or similar) on SD (external).
Over-write eMMC (internal) with CM (or similar).
I see a lot of confusion between these, and a lot of misconception that you have to root stock before loading either of the other options.
Was the NOOK color originally shipped with Eclair? I thought they were Froyo from day one. I know a lot of us were disappointed when B&N 1.4.1 shipped as Froyo.
Thanks for the feedback. Remember, this is Nook 101, not 201. I didn't want to provide so much info that it left folks feeling overwhelmed. I suggested they begin with CM7.0. I mentioned CM7.1 and CM7.2. This sucker is already long. I had to narrow the focus to keep from turning it into a novel.
ICS is Ice Cream Sandwich, isn't it? I mentioned that CM9 is under development, but I'm pretty sure nubes should not start with that. Besides, my understanding is that it is still very much in the RC testing phase. Isn't that right?
I said there were two approaches. But I said some MODs allow for dual booting. Again, I didn't want to overwhelm.
I read in two different places (not on XDA) that Eclair was the original OS for the Nook. I think they began to push Froyo in the Fall of 2011.
You will also note that I did not cover the various models of the Nook at all. And I didn't mention the change in the hardware of Nook Color that has happened in the past two or three months. I didn't feel qualified to explain those. I'm still a relative nube myself.
BO
First, thanks for all the hard work with the words. I saw your initial posts and can only figure you are a writer, to be so willing to set everything you have done down in an orderly manner.
I'd like to add a fourth choice to bobstro's list of possibles (and I am not so adept at all this Nooker stuff myself that I believe it is too much for beginners):
Triple boot using Racks' great info and files here in the developer's wing. That way a learner can get a very stable CM7 GB (Kang build) a working - and for an "in process" ROM - quite stable CM9 (ICS) both on one SD card, and still have an untouched B&N stock on their NC.
Believe me; it's not too hard to set up; it has the best of all worlds. And it increases the fun factor by a million!
You know what root is but I don't get a clear picture of why it is called root.
In the unix/linux world if you are a superuser you have root access. Rooting a device is gaining root access to the device. With root access there are no restrictions to what you can do to the device. Including brick it.
BTW: Bricking a device is just that. Turning a beautiful orchestration of electronic components into a paperweight or, brick.
I think I included that the term rooting comes from the unix/linux world and the business about the superuser. See, that's the problem with something so long. It's easy to miss stuff. But I wanted to be clear about some of the essential stuff. It's a balancing act. Anyway, thanks for the input.
Yes. I saw why it was called bricking. I can add that.
BO
Thanks for the suggestion. I'll look into Rack's method and see whether I can include it. Again - this post is intended to be 101, not 201 info.
I wrote some computer manuals for teachers at least for a few years. It's been awhile since I did that. I try to be clear. The problem is that sometimes I try to keep it so simple that I often go overboard - result - very long. Verbose is the word. I could never have worked for Reader's Digest.
I see that nearly 150 people have at least looked at the file (maybe at least scrolled through it), but I haven't seen all that much feedback so far.
Some are making suggestions for improvement. My concern really is have I been accurate about what I actually did include?
BO
BO
You start using the term MOD without having defined it partway down.
I found this bit potentially confusing:
FYI: there are even new flavors of these general ROMS. There is also CM7.1 and CM7.2. And there is a version out there called CM9.
What is CM if this is 101?
Thanks. I'll try to adjust the issue you raised about using MOD before it has been defined. I believe I did explain CM was CyanaMod, but I'll double check it.
BO
It's a sequence thing. You use CM before CyanogenMod, and don't link them together. You might try something like CyanogenMod (CM) to link them.
Maybe a mention of OTA updates?
Gotcha. I'll see what I can do.
Thanks!
BO
This is just purely a great, great post, especially for newbies.
Keep it up, bachon.
Back to bachon, here's a few things
1. "“Rooting” means obtaining “superuser” rights to your Nook’s software. You gain the ability to load custom ROMs, ....."
Rooting has nothing to do with loading custom ROM. In order to be able to install/loading custom ROM, the bootloader must be unsigned/unchecked. Short way of saying, you can root but it doesn't mean after root, you can install custom ROM. It's a function of the bootloader.
2. Personally, I think and I do believe some devs. think that the term "rooting" is only applied to the stock ROM/OS. When you installing/running a custom ROM, the term "rooting" is irrelevant and should not be used (since we already able to access the root directory of that OS/ROM)
3. Not a biggie, but pls rename "Kernals" to "Kernels"
The other way of saying the kernels: are the firmware drivers that handle all the communications between the hardware and the operating system.
4. If you have the "Two Approaches" sections, you should also have "Three Approaches"
5. In the "Downsides of Custom ROMs" you mentioned it will void the warranty. This is only true if you install a custom ROM in eMMC. If you're running one off uSD, you know by removing the uSD, it's back to stock. No warranty voided.
6. Since you listed "o Android 3.0 (codename Honeycomb)", you should add "Android 4.0.x (codename Ice Cream Sandwich), just to complete
7. I do think we should have a short paragraph about what CyanogenMod team and their codenames. I don't want to go way back but CM7, the "7" denotes for Gingerbread builds and on-going "9" is for Ice Cream Sandwich. Why do they skip "8"? 'Cuz "8" was reserved for Honeycomb.
I can't pass out the cigars yet, huh?
votinh said:
This is just purely a great, great post, especially for newbies.
Keep it up, bachon.
Thanks for the kind words, votinh.
Mod, you should sticky this thread.
Back to bachon, here's a few things
1. "“Rooting” means obtaining “superuser” rights to your Nook’s software. You gain the ability to load custom ROMs, ....."
Rooting has nothing to do with loading custom ROM. In order to be able to install/loading custom ROM, the bootloader must be unsigned/unchecked. Short way of saying, you can root but it doesn't mean after root, you can install custom ROM. It's a function of the bootloader.
2. Personally, I think and I do believe some devs. think that the term "rooting" is only applied to the stock ROM/OS. When you installing/running a custom ROM, the term "rooting" is irrelevant and should not be used (since we already able to access the root directory of that OS/ROM)
I'm afraid my understanding for what you are saying is insufficient to write this clearly. Can you say more about this to clarify things? I thought it was obtaining superuser rights that gave users the ability to load ROMs and other software on their Nooks. I'm going to need more information to correct this.
3. Not a biggie, but pls rename "Kernals" to "Kernels"
The other way of saying the kernels: are the firmware drivers that handle all the communications between the hardware and the operating system.
Oops! Good proof reading. Thanks. Is it OK to just add your addition to the final post, or is the rest of what I have said wrong?
4. If you have the "Two Approaches" sections, you should also have "Three Approaches"
OK. Here's my current understanding. 1. Running a custom MOD from the SD Card. 2. Installing a custom ROM in eMMC. 3. Having a dual boot capability.
Someone mentioned having two different ROMs loaded on an SD card. Does this allow the original Nook OS to run with no SD card inserted?
Any clarification needed there? I'm looking to make this VERY clear for newbies.
5. In the "Downsides of Custom ROMs" you mentioned it will void the warranty. This is only true if you install a custom ROM in eMMC. If you're running one off uSD, you know by removing the uSD, it's back to stock. No warranty voided.
Hmmm. Is there no way running or updating a ROM can brick a Nook? It seems to me that someone trying to upgrade from one custom ROM to another could follow the wrong steps and trash the contents of the emmc. Am I wrong?
6. Since you listed "o Android 3.0 (codename Honeycomb)", you should add "Android 4.0.x (codename Ice Cream Sandwich), just to be complete
7. I do think we should have a short paragraph about what CyanogenMod team and their codenames. I don't want to go way back but CM7, the "7" denotes for Gingerbread builds and on-going "9" is for Ice Cream Sandwich. Why do they skip "8"? 'Cuz "8" was reserved for Honeycomb.
Click to expand...
Click to collapse
I wondered what happened to CM8. Thanks for that. I'm so new here that I'm not sure I can really explain the CyanogenMod team and their codenames. Care to give me some tips? It would really help.
While I'm asking: why and when was the codename for Gingerbread changed to CyanogenMod?
I don't mind including Ice Cream Sandwich/CM9, but I don't know that much about it. Input from the seasoned veterans would help.
Frankly, most of the suggestions I've received seem to want to add more information. I wanted things to be clear without overwhelming. Truth is, I cannot write clearly about things I don't quite understand.
If folks will share and explain the info to me then I'm more than willing to try to put it in a form that neophytes can understand.
Finally, MOD and ROM seem to be used interchangeably by many in the Nook forums. Anybody willing to provide their 2 cents worth on the difference?
Thanks
BO
I'm afraid my understanding for what you are saying is insufficient to write this clearly. Can you say more about this to clarify things? I thought it was obtaining superuser rights that gave users the ability to load ROMs and other software on their Nooks. I'm going to need more information to correct this.
Click to expand...
Click to collapse
Obtaining superuser rights is NOT enough to load custom ROMs on the device. Take a look at the Nook Tablet as an example.
Obtaining superuser rights is enough to install other applications. It is still not 100% true. Take side-loading feature as an example, some devices, even rooted, still cannot sideloading.
OK. Here's my current understanding. 1. Running a custom MOD from the SD Card. 2. Installing a custom ROM in eMMC. 3. Having a dual boot capability.
Click to expand...
Click to collapse
What you said is MOST common mistake and should be changed.
Boot from eMMC along with running off uSD is NOT dual-booted, at least not TRUE dual-booted. People here love to call it as "dual-boot" so I go with that, but it isn't, really.
True dual-boot is one ROM in eMMC and another ROM also in eMMC. Same applied for uSD.
This is a true dual-boot:
http://forum.xda-developers.com/showthread.php?t=1448186
Someone mentioned having two different ROMs loaded on an SD card. Does this allow the original Nook OS to run with no SD card inserted?
Click to expand...
Click to collapse
The link I just provided up there is exactly what it for.
And yes, it is INDEPENDENT to eMMC. You can leave stock OS intact.
Hmmm. Is there no way running or updating a ROM can brick a Nook? It seems to me that someone trying to upgrade from one custom ROM to another could follow the wrong steps and trash the contents of the emmc. Am I wrong?
Click to expand...
Click to collapse
Dealing with eMMC, yes, if you screw it up, then you got what you have. If you only dealing with uSD and leave eMMC untouch, everything on eMMC should still be there, cleanly.
Note: the NC is virtually unbrickable unless the hardware parts broken.
While I'm asking: why and when was the codename for Gingerbread changed to CyanogenMod?
Click to expand...
Click to collapse
Gingerbread is Android mobile OS codename by Google.
CyanogenMod is a developer team. Their codename gets their teamname and as I said "7" is Gingerbread version of their work.
Note: CM7 widely known for custom ROMs, not only for NC but for many other devices
Link: http://www.cyanogenmod.com/
See their device list.
Finally, MOD and ROM seem to be used interchangeably by many in the Nook forums. Anybody willing to provide their 2 cents worth on the difference?
Click to expand...
Click to collapse
I rarely see MOD as refer to ROM but I would guess, MOD is shortcut for Modification/Modified.
ROM usually refers to OS.
Votinh (or anyone else),
When you write computer code, you have to break the instructions down into step-by-step commands. Computers have no common sense to guess what you’re telling them to do. You can’t just say, “Print”. You have to be a whole lot more specific.
I’m trying to get you to do that here. Because you (and many others on this site) understand this stuff so well, you’re using broader statements like “It’s a function of the bootloader.” I’m asking you these questions to break it back down into the step-by-step stuff. If you can get me to understand it, I think I can write it down so many other nubes will understand it and MAY stop bugging everybody by asking over and over. Please be patient and bear with me.
OK. Let’s take these one at a time. Rooting first:
You said:
“Rooting has nothing to do with loading custom ROM. In order to be able to install/loading custom ROM, the bootloader must be unsigned/unchecked.”
“Short way of saying, you can root but it doesn't mean after root, you can install custom ROM. It's a function of the bootloader.”
First, I’ve been under the impression that rooting is an absolutely essential first step in order to be able to do things like loading a custom ROM. It isn’t all that is required, but it is the FIRST requirement. Isn’t that correct?
Think of a Nook straight out of the box. If I stick a formatted SD chip in my Nook with no OS, the Nook loads the stock OS. If I stick a SD chip imaged using “generic-sd-v1.3.zip” and with the zipped archive, “Encore_CM72-MIRage-01262012.zip” loaded on the SD chip, then the Nook will expand the “MIRage*.zip” and run the CM7.2 custom ROM. Isn’t that right?
Which of these zipped archives (if any) actually contains the instructions that roots the Nook?
Which of these zipped archives (if any) actually contains the instructions that unchecks the bootloader?
Which of these zipped archives (if any) contains the instructions that alters the bootloader?
Which of these zipped archives (if any) actually loads the custom MOD?
Is it accurate to say that rooting the device is only the first step necessary before the bootloader can be unchecked?
If so, is it also accurate to say that the installation process for any custom ROMs must then uncheck and alter the bootloader before any custom ROM can be installed or loaded?
My way of thinking of it is as follows: rooting only unlocks the first lock on the device. Then the installation process for the custom ROM must unlock other locks before a custom ROM can be loaded or installed.
BO
bachon said:
[...] First, I’ve been under the impression that rooting is an absolutely essential first step in order to be able to do things like loading a custom ROM. It isn’t all that is required, but it is the FIRST requirement. Isn’t that correct?
Click to expand...
Click to collapse
No, that is not correct. Rooting is providing root access on a (in a sensible case) unrooted device. This is typically your stock firmware. You can root a NC which shipped with unrooted (locked) B&N 1.2, 1.3 or 1.4.1 firmware, for example. You can also root a NT which ships with 1.4.x firmware as well.
Loading alternate firmware is where the locked bootloader comes in. On the NC, with no locked bootloader, independent of rooting, you can install alternate firmware, either to SD card (leaving the internal eMMC firmware, rooted or not, unchanged), or over-write the internal eMMC firmware with something new. I'd expect that something new to be rooted in the case of alternate firmware, but I suppose it doesn't have to be. On the NT, this is all complicated (if B&N had their way, impossible) because of the locked bootloader, but progress is being made working around this. See the NT forums for details.
If you're going to load alternate firmware on a NC, rooting is not a requirement. In fact, a lot of people like dual-booting (sorry, the term is descriptive enough without getting into semantics, and I've yet to hear a better term) something like CyanogenMod off of SD while preserving their unrooted stock B&N firmware for "warranty purposes", since they are completely independent of each other. Boot off of SD and you get CM. Pull the SD out and boot and you get B&N.
To make it short, bachon,
bootloader is essentially a piece of low-level code that resides on the non-volatile on boards that handling how the system starts up and how it behaves during powering up. The other way to say: it is the very first thing to run soon the power provided.
If it is "signed/locked" then you have a hard time to manipulate it such loading custom ROM, even preventing alter the stock recovery, and in some case, not even allow us to touch the system kernel.
Think of a Nook straight out of the box. If I stick a formatted SD chip in my Nook with no OS, the Nook loads the stock OS. If I stick a SD chip imaged using “generic-sd-v1.3.zip” and with the zipped archive, “Encore_CM72-MIRage-01262012.zip” loaded on the SD chip, then the Nook will expand the “MIRage*.zip” and run the CM7.2 custom ROM. Isn’t that right?
Which of these zipped archives (if any) actually contains the instructions that roots the Nook?
Which of these zipped archives (if any) actually contains the instructions that unchecks the bootloader?
Which of these zipped archives (if any) contains the instructions that alters the bootloader?
Which of these zipped archives (if any) actually loads the custom MOD?
Click to expand...
Click to collapse
The "generic...." is just a container.
The "encore-...." is the actual custom ROM.
If so, is it also accurate to say that the installation process for any custom ROMs must then uncheck and alter the bootloader before any custom ROM can be installed or loaded?
Click to expand...
Click to collapse
Absolutely true.
---------- Post added at 10:21 AM ---------- Previous post was at 10:20 AM ----------
Oh, and bobstro have provided a very good example of it, down to the very specific case.
Bobstro,
So a lot of people who say "I rooted my Nook" aren't correct. They may have loaded another OS, like CyanogenMod 7.2, but that doesn't mean that they've necessarily rooted their Nook. Is that correct?
These folks would be more accurate to say "I hacked my Nook."
Is that closer to being accurate?
How and why did so many people start calling it rooting? I know about the root user in Unix. Do some of the OS installations go the extra step of actually rooting the Nook?
BO
I think you spelled Bacon wrong.
bachon said:
Bobstro,
So a lot of people who say "I rooted my Nook" aren't correct. They may have loaded another OS, like CyanogenMod 7.2, but that doesn't mean that they've necessarily rooted their Nook. Is that correct?
These folks would be more accurate to say "I hacked my Nook."
Is that closer to being accurate?
How and why did so many people start calling it rooting? I know about the root user in Unix. Do some of the OS installations go the extra step of actually rooting the Nook?
BO
Click to expand...
Click to collapse
I don't mean to jump on bobstro's toe, I hope he allows me to answer the question.
1. Again, I repeat, the term "root" should only be applied when you're dealing with STOCK ROM.
2. If you are running CM7 or any custom ROM such MIUI, .... you DON'T NEED to root since it ALREADY allows you accessing the root directory. Therefore "rooting" process is no need.
3. If you are running any custom ROM, ideally, you should not say "I'm rooting my device".
Why people using that? They say so and no one correct them so the term spreads.
can't believe my decrepit and all-but-abandoned nook color is humming along with kitkat. succulent is the bomb. he rightly credits all the developers he relied on, but he put it all together. download and flash the cwm update, then the rom and gapps and voila! i used a pc for downloading and the nook data cable and the "send to" option in downloads. great thanks to all.
I agree, it's great that so many people put in so much effort to bring Kitkat to the aging NC.
I do have one question. Would someone be so kind as to post a link to a suitable CWM for CM11 on the NC? I have 6.3.0.1 on mine, and can't find a link to anything newer for the life of me.
EDIT: I found it, but can't post a link because I'm a n00b. Google for cm11-encore-recovery.zip_links to find it on the Cyanogenmod wiki.
I'm booting CM11 for the first time now.
I have today reinstalled my two Nook Color from scratch with CM11 running on SD-card.
“generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8b” loaded on two” SanDisk Mobile Ultra Class4 16GB” with “win32diskimager-v0.9-binary”
“cm-11-20140131-NIGHTLY-encore” installed as OS, went fine. Runs fast & nice.
“gapps-kk-20140105” installed trough SD card recovery PowerOn & then “n” . There was Android upgrading-something 6/6 installed during boot after the recovery. But I cannot find any PlayStore and so on. But the Gmail icon is there now & maybe something more.
dfarquhar said:
I agree, it's great that so many people put in so much effort to bring Kitkat to the aging NC.
I do have one question. Would someone be so kind as to post a link to a suitable CWM for CM11 on the NC? I have 6.3.0.1 on mine, and can't find a link to anything newer for the life of me.
EDIT: I found it, but can't post a link because I'm a n00b. Google for cm11-encore-recovery.zip_links to find it on the Cyanogenmod wiki.
I'm booting CM11 for the first time now.
Click to expand...
Click to collapse
Best versions are here: http://forum.xda-developers.com/showpost.php?p=49915965&postcount=34
Homer
I have two (2) Nook Color devices. As I wrote above I reinstalled them both today with CM11. I got a problem except for the GAPPS that dosen't install the Play, it is that I coulden't use them at the same time with Wi-Fi. I found out that both have the same MAC address. Dosen't CM11 KitKat use the chip MAC address? Is it a software MAC?
How do I change so the CM11 use the Wi-Fi chip burned in original MAC address?
frav.se said:
“gapps-kk-20140105” installed trough SD card recovery PowerOn & then “n” . There was Android upgrading-something 6/6 installed during boot after the recovery. But I cannot find any PlayStore and so on. But the Gmail icon is there now & maybe something more.
Click to expand...
Click to collapse
That's odd. I used the same build and have the Play store and other Google apps. Maybe try re-flashing the gapps zip?
I found the 11-29 build to run much faster than any other 4.x version (no surprise) but occasionally would do odd things like change icons. These things happen of course with experimental builds. I'm upgrading to 1-31 now.
frav.se said:
I have two (2) Nook Color devices. As I wrote above I reinstalled them both today with CM11. I got a problem except for the GAPPS that dosen't install the Play, it is that I coulden't use them at the same time with Wi-Fi. I found out that both have the same MAC address. Dosen't CM11 KitKat use the chip MAC address? Is it a software MAC?
How do I change so the CM11 use the Wi-Fi chip burned in original MAC address?
Click to expand...
Click to collapse
I don't know how you could have installed them with the same wifi MAC address... when I look at my advanced internet settings on NC it says MAC address is not available... however when I look in my router it is seeing the hardware MAC address.
So CM isn't even reading the /rom/MACaddress file for the information... however it is not returning a MAC on polling either... perhaps this is why play store is giving you issues.
Now I have reinstalled both NCs again. This time it seems like it worked out well.
Regarding the MAC problem. It could maybe be like this, that I accidently did the first time install & boot with the same NC device. But anyhow I think it is strange if it doesn't use the h/w MAC as the default choice.
This time I did like this:
1. “generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8b” from http://forum.xda-developers.com/showthread.php?t=1941858 loaded on two” SanDisk Mobile Ultra Class4 16GB” with “win32diskimager-v0.9-binary”
2. "cm-11-20140131-NIGHTLY-encore.zip " from http://download.cyanogenmod.org/?device=encore&type=nightly
3. Removed Hangouts.apk and GoogleHome.apk according to this http://forum.xda-developers.com/showpost.php?p=49942253&postcount=529
4. Installed "gapps-kk-20140105-signed.zip" from http://wiki.cyanogenmod.org/w/Google_Apps (This time it was 20 "things" installing & not 6 like last time)
Upgraded both to "cm-11-20140201-NIGHTLY-encore.zip" , that worked out fine. Have installed approx 150 apps, more or less no problems more than that Play Store sometimes shuts down.
So I'm satisfied so far. Thank you to the Devs.
Upgraded both ny NCs today to "cm-11-20140202-NIGHTLY-encore.zip". On one of the devices it went fine, but on the second one something got wrong. The "desktop" is now not possible to slide sideways & the time/weather widget is not there. On the first one I got google maps, gmail & play store Icon on the first desktop screen, but they are not on the second device.
Anyone having a clue of what could have happened & how to solve it?
Tried to downgrade to 0101, but then i only got "Unfortunately, Trebuchet has stopped", so I upgraded to 0202 again. Then I don´t get this error, but the home screen is still not working properly.
If I understood that error message right it has something to do with the homescreen cache. And it is the home screen that is strange in my case. How do I reset the Trebuchet cache?
---------- Post added at 03:48 PM ---------- Previous post was at 03:36 PM ----------
Managed to solve it. Went in to settings/apps/all/Trebuchet, cleared data & voila the home screen is now working again.
can someone upload a movie about the performance of the tablet under kitkat? I gave my nook to a family member and want her to have a faster system, but don't want to delete all her data if it's not worth it
speedfreak007 said:
can someone upload a movie about the performance of the tablet under kitkat? I gave my nook to a family member and want her to have a faster system, but don't want to delete all her data if it's not worth it
Click to expand...
Click to collapse
If your running CM7, it's still snappier than CM11. CM11 is a huge improvement over the CM10.x versions, take up a smaller footprint on the Nook and has nice functionality.
Runs smooth...
...I have only been playing around with CM11 for a couple days now, but enjoy the overall OS and it out ways the minor performance loss in many ways.
- You can use YouTube off of Play, but might not have smooth HD viewing and will need to watch in non-HD
- You can manually install the newest Crackle TV (Play will not allow it due to incompatibility warning), but have to turn on Disable HW overlays (Always use GPU for screen compositing) to have it work properly
- You can either use the older 1.8.1 NetFlix flawlessly or use the workaround on here
That's about it for me. Everything else seems to work ok. haven't tried any performance or graphic intense games yet.
2-05-2014 Nightly
Anyone get this nightly to load?
f1jim
Nevermind...It's working now.
Kitkat on Nook Color
I flashed CM11 on my NC last week.
Android 4.4.2, but kernel 3.0 - it doesn't seem to be Kitkat.
To my phone running 4.2.2 with kernel 3.4 that higher than NC flashed CM 11, called Kitkat.
Sorry if I am wrong, but that's all I've found.
"I have no technical skill, so just a thought that higher is better"
stevedat said:
I flashed CM11 on my NC last week.
Android 4.4.2, but kernel 3.0 - it doesn't seem to be Kitkat.
To my phone running 4.2.2 with kernel 3.4 that higher than NC flashed CM 11, called Kitkat.
Sorry if I am wrong, but that's all I've found.
"I have no technical skill, so just a thought that higher is better"
Click to expand...
Click to collapse
Each device has its own version of kernel. Yours is right.
Sent from my BN NookHD+ using XDA Premium HD app
Kitkat 4 Nook Color
leapinlar said:
Each device has its own version of kernel. Yours is right.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks.
Anyway, CM 11 on my NC running very well. A big thank to CM developers & Nookies Dev.
Ak, only one thing bothering me that I cannot use my new external keyboard with it(Cover with usb keyboard). It worked on CM 7.2 with an 3rd tool.
Issue with recognizing external keyboard on NC running CM 11 Nightly
Does anyone know how to use an external keyboard (usb keyboard cover) on Nook Color running CM 11?
In past I could use the usb keyboard cover when using CM 7.2 on my NC with Nook Color tweak.
Last week, I decided to upgrade my NC to Kitkat by flashing CM 11 Nightly and from that point I haven't been able to use my usb keyboard cover with my NC any more.
Any tips, suggestions ... plz help.
Thanks.
stevedat said:
Does anyone know how to use an external keyboard (usb keyboard cover) on Nook Color running CM 11?
In past I could use the usb keyboard cover when using CM 7.2 on my NC with Nook Color tweak.
Last week, I decided to upgrade my NC to Kitkat by flashing CM 11 Nightly and from that point I haven't been able to use my usb keyboard cover with my NC any more.
Any tips, suggestions ... plz help.
Thanks.
Click to expand...
Click to collapse
I don't think Bluetooth is working yet. Not sure if it will get fixed, but it is in the change log that it is not working. Otherwise I am very happy with the performance. I just got my nook off craigslist and it is running much better than I ever imagined it could!
frav.se said:
Now I have reinstalled both NCs again. This time it seems like it worked out well.
Regarding the MAC problem. It could maybe be like this, that I accidently did the first time install & boot with the same NC device. But anyhow I think it is strange if it doesn't use the h/w MAC as the default choice.
This time I did like this:
1. “generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8b” from http://forum.xda-developers.com/showthread.php?t=1941858 loaded on two” SanDisk Mobile Ultra Class4 16GB” with “win32diskimager-v0.9-binary”
2. "cm-11-20140131-NIGHTLY-encore.zip " from http://download.cyanogenmod.org/?device=encore&type=nightly
3. Removed Hangouts.apk and GoogleHome.apk according to this http://forum.xda-developers.com/showpost.php?p=49942253&postcount=529
4. Installed "gapps-kk-20140105-signed.zip" from http://wiki.cyanogenmod.org/w/Google_Apps (This time it was 20 "things" installing & not 6 like last time)
Click to expand...
Click to collapse
So, using what you did, and the guide it came from. Does this root and install a CWM? Or do you need to do all those steps first. Just a bit confused as how to take my stock Nook Color and get it to CM11
Never mind; got it figured out and up and running. This process did root and get it up and running on CM11 for me.