Related
Thinking about getting a nook color, before I jump in I'd like to know if froyo is stable and useable, does copy and paste work?
I wish i had time to do more research, but I'm getting ready for a trip and I'm thinking I may go ahead and get a nook. Did a bit of searching before asking here, found nothing definitive.
Also whats the state of Flash 10.1? any success?
So in Summary:
Is Froyo doable/useable?
Can I copy and paste?
Can I get Flash running?
Can anyone recommend a combination of rom/apps that will fit the bill?
Thanks
Honeycomb on Nook is awesome, the work done here is impressive. Congratulations!
I want to try it out, giving a Nook Honeycomb, and use it instead of a Moto Xoom (it's impressive, but I doesn't need the big screen, HDMI, cameras, dual-core CPU...)
what I need is a small tablet so that I can:
# browse and read news etc.
# use Gmail
# watch a few videos (YouTube or files)
# maybe read e-books (Kindle, B&N)
# run various small apps (maybe some games) - from Android Market
And I want:
# 6" or 7" display
# low weight
# long battery life
# WiFi
# 3G through a Bluetooth connection to my phone
# and low cost
Thats not an 800 USD Xoom for that. But a Nook with HoneyComb!
I'm not a developer but a relatively technical user, so I'm not afraid of buying a Nook and try out some stuff.
But I have som questions and would like some input. I may have misunderstood things and I apologize for stupid questions.
First decisions/questions:
1; what is eMMC? I can see that I should choose between SD or EmmC, so this is probably a fairly basic decision.
2; I gather I need to choose which port of Honeycomb to use. Right? (I have listed a few below).
3; it appears to be possible to either boot Android Honeycomb from the SD-card. Does that mean I can use the Nook as it was delivered if the SD card isn't present?
4; Is there any other basic decisions I need to take?
There's lots of posts here, and I've been reading back and forth, and from what I see this is what I need:
# get a Nook
# get a microSD card. Is there any recommendations?
# get a Honeycomb image/build. Could be:
-http://forum.xda-developers.com/showthread.php?t=936995 by deeper-blue
-http://forum.xda-developers.com/showthread.php?t=925451 by dalingrin
-http://forum.xda-developers.com/showthread.php?t=954902 by phiredrop
# overclock the Nook to 1 or 1.1 GHz
# Disabling B&N OTA updates (or is this done automatically?)
# Dualboot?
# Installing various apps
# Network using Bluetooth - how?
Is this too deep water for me or should I plunge in?!
I personally think that you should dive in. Now first emmc is the name of the nooks internal memory.
I would recommend buying one and first using a micro SD to boot honeycomb and decide if you want to run it. It's a great port and great os but its not prime time yet on the nook.. I use it only, and even with its faults it is too 'tablet friendly' for me to switch.
YouTube is tricky at best. Ill let someone with more experience post about it. In my experience it's not real reliable for some reason
Sent from one of those missing Droids
I love my nook color, and it has a bright future. But u mentioned you wanted 3g and Bluetooth. Those are not available as of yet on nook color. I'm not sure if it has those internal components or not.
But it is a very capable device. Mine is setup comparable to the galaxy tab I would say, after rooting it and adding a custom rom.
Sent from my Droid using Tapatalk
Thanks for the answers so far!
I can live without 3G/BlueTooth.
And I can live without YouTube. That will probably fixed along the way.
Is the current Honeycomb builds based on a prerelease SDK or is considered a final release?
Caspar07 said:
Thanks for the answers so far!
I can live without 3G/BlueTooth.
And I can live without YouTube. That will probably fixed along the way.
Is the current Honeycomb builds based on a prerelease SDK or is considered a final release?
Click to expand...
Click to collapse
You can't use bluetooth for data, but you could certainly tether your nook to your smartphone. That's what I plan to do when I find myself without a wireless connection.
EDIT: Oh and you could visit the actual youtube website if you have flash installed (on a 2.2 or higher ROM).
Definately dive in. Buy a few microSD cards. Start by rooting the stock firmware and play with a launcher and the market. It's the most stable.
Install Honeycomb on an SD card and boot it. It's not bad but will be much improved in the next few weeks.
No bluetooth yet but you can wifi tether to your phone if your phone supports it.
BanditRider said:
Start by rooting the stock firmware and play with a launcher and the market. It's the most stable.
Install Honeycomb on an SD card and boot it. It's not bad but will be much improved in the next few weeks.
No bluetooth yet but you can wifi tether to your phone if your phone supports it.
Click to expand...
Click to collapse
"Rooting stock firmware"?
Does that mean sort of copying the firmware, so You can restore later?
Again: good replies, much appreciated
To get you started.
At $250, the Nook Color sucks as an eReader. But as an android tablet, its the best purchase you could make. Nothing else comes close. Some notes on your comments.
1. The Nook Color(NC) has a boot priority to the microSD card, making it nearly impossible to 'brick.' I'd reccommend having two sd cards. A good class 10 one for your daily use, and a cheap 1gb one to keep a copy of clockwork recovery for quick repairs.
2. The bluetooth doesn't work, even though the device has the hardware. At this point, there is no speculation of it working in the forseeable future. HOWEVER, it works great using the WiFi hotspot on my HTC evo.
3. The device will run android 2.1 (eclair), 2.2 (froyo), 2.3 (gingerbread), and 3.0 (Honeycomb). All four have their issues. I've tested them all thoroughly, and prefer the standard 2.1 (also called stock NC) build for its stability. Feel free to try them all.
IF YOU SHOULD BUY ONE:
Instructions to root
Instructions to build a recovery SD card
Instructions on how to make root stock NC work well for you
Remember these links. They'll save you the hours of time I lost.
YouTube and Flash work perfectly for me on the 2.2 phiremod beta2 rom. I would say it is pretty stable. But if one is new to root they should just get used to rooting first. We are also over at androidtablets if you need help http://www.androidtablets.net/forum/nook/
The above link for rooting seems broken. Here is the NookDevs links http://nookdevs.com/NookColor_Rooting *edit nevermind it's working sorry
Thank you
I've not yet done any recover steps after auto nootering a few weeks ago. This is going to help me go do these steps this weekend.
Tethering is going to be something i need come summer vacation where there's no connection any place, i have the MOTO Droid, and PDANet, so i'll try that some day soon, see if it holds up.
admiralnorman said:
At $250, the Nook Color sucks as an eReader. But as an android tablet, its the best purchase you could make. Nothing else comes close. Some notes on your comments.
1. The Nook Color(NC) has a boot priority to the microSD card, making it nearly impossible to 'brick.' I'd reccommend having two sd cards. A good class 10 one for your daily use, and a cheap 1gb one to keep a copy of clockwork recovery for quick repairs.
2. The bluetooth doesn't work, even though the device has the hardware. At this point, there is no speculation of it working in the forseeable future. HOWEVER, it works great using the WiFi hotspot on my HTC evo.
3. The device will run android 2.1 (eclair), 2.2 (froyo), 2.3 (gingerbread), and 3.0 (Honeycomb). All four have their issues. I've tested them all thoroughly, and prefer the standard 2.1 (also called stock NC) build for its stability. Feel free to try them all.
IF YOU SHOULD BUY ONE:
Instructions to root
Instructions to build a recovery SD card
Instructions on how to make root stock NC work well for you
Remember these links. They'll save you the hours of time I lost.
Click to expand...
Click to collapse
You need to use an Adhoc method to tether droid to autonootered nook I believe. It doesn't work as is right off the bat with a 2.1 nook color and droid1.
Caspar07 said:
....But I have som questions and would like some input. I may have misunderstood things and I apologize for stupid questions.
First decisions/questions:
1; what is eMMC? I can see that I should choose between SD or EmmC, so this is probably a fairly basic decision.
2; I gather I need to choose which port of Honeycomb to use. Right? (I have listed a few below).
3; it appears to be possible to either boot Android Honeycomb from the SD-card. Does that mean I can use the Nook as it was delivered if the SD card isn't present?
4; Is there any other basic decisions I need to take?
Click to expand...
Click to collapse
I was in the same boat... wanted a tablet to do pretty much what you are looking for... after reading the threads here, I got a Nookcolor...
1.. eMMC is the Nook's internal memory, where its current/stock B&N OS and apps are stored and run from. If you wanted to use a "custom rom" like Froyo, Gingerbread, Honeycomb, you could install it to eMMC, overwriting the stock B&N stuff... BUT you don't have to.
2. Right now, the honeycomb ports out there are based on the Pre-Release SDK (software dev kit), and made to work on an actual device, i.e. the NookColor. Because of this, it has some limits and bugs. The best HC Ports will come once HC goes AOSP (hopefully soon since the XOOM, which uses HC, is now for sale).
3. The NookColor is setup to try and boot from MicroSD card first, and if no OS on MicroSD, then boot off the eMMC. So, you could load up a card with another OS, play with it, and NOT TOUCH the stock B&N stuff... just pop the card in when you want to boot the other OS, and pop it out when you want to go "stock" (that is what I'm doing now).
This also means you can make up a MicroSD card strictly for the purpose of recovering/reloading the OS on your NookColor if something goes wrong when trying to install an alternate OS to the eMMC. (i.e. helps you "unbrick" your device).
Note: when getting a MicroSD card to boot an alternate OS from, its generally better to get a higher class card as they are usually faster (means the OS runs faster/smoother). But some of the lessor known brands often don't live up to their class ratings. And there have been issues with some people getting certain Class 10 (fastest) 16gig cards, so you'll have to do some home work, searching and reading the threads to decide on which card to buy.
4. You have many choices to make. Do you want to run stock B&N os/firmware (Eclair/2.1) as is out of the box? Do you want to root the stock OS and add your own apps? Do you want to try one of the Froyo (2.2), Gingerbread (2.3, the CM7 builds) or Honeycomb (3.0) ports and do you want to run them from MicroSD (slower) or eMMC (faster)?
While Wifi works with each Froyo and HC build I've tried, Bluetooth doesn't work with any of them.
Each port of Froyo, Gingerbread and HC has its own positives and negatives, so you have to investigate and figure out which one works best for you as a daily driver.
Me, I left the stock B&N NookColor OS and Apps untouched, and loaded up one MicroSD (Sandisk 8G class4) with Froyo following this thread -> http://forum.xda-developers.com/showthread.php?t=922324
And I loaded up another MicroSD card using the HC Preview v4, but it didn't meet my needs, so I'm waiting on the AOSP of HC to try again.
admiralnorman said:
...
3. The device will run android 2.1 (eclair), 2.2 (froyo), 2.3 (gingerbread), and 3.0 (Honeycomb). All four have their issues. I've tested them all thoroughly, and prefer the standard 2.1 (also called stock NC) build for its stability. Feel free to try them all.
....
Remember these links. They'll save you the hours of time I lost.
Click to expand...
Click to collapse
Great help - thanks.
Still one question:
Is lack of stability in Honeycomb due to the fact that it's still early and very new, or is it due to incompatible hardware?
This is getting increasingly interesting
Caspar07 said:
Great help - thanks.
Still one question:
Is lack of stability in Honeycomb due to the fact that it's still early and very new, or is it due to incompatible hardware?
This is getting increasingly interesting
Click to expand...
Click to collapse
Not really. Its kind of a developer's platform. So its made to run on a generic android device. As the programmer type people around here play with it, it gets better and better.
Sent from my HTC Evo 4g using XDA App
KidJoe said:
I was in the same boat... wanted a tablet to do pretty much what you are looking for... after reading the threads here, I got a Nookcolor...
...
And I loaded up another MicroSD card using the HC Preview v4, but it didn't meet my needs, so I'm waiting on the AOSP of HC to try again.
Click to expand...
Click to collapse
Thanks for the lengthy answer. That was a helpful explanation.
Caspar07 said:
Great help - thanks.
Still one question:
Is lack of stability in Honeycomb due to the fact that it's still early and very new, or is it due to incompatible hardware?
This is getting increasingly interesting
Click to expand...
Click to collapse
The devs currently do not have the Honeycomb source. What exists now has been pieced together from the emulator and is glitchy. Once they have the source (which should be soon as the XOOM is out now) we should begin to see improvements in HC roms.
Also, please recognize that not everyone has stability issues. I've been running the initial version of Sam's "flashable" Deeper Bulue image for 2 weeks, and don't have any stability issues.
It really depends on what apps you want to run. I have market working fine, with lots of apps downloaded. I did the ADHOC tweak early on, and can connect to wireless networks pretty much at will.
I read quite a bit, and spend a lot of "nook time" using it as an eReadr. I've worked my way through a number of books using the B&B Reader, Kindle, and Aldiko without any issues.
It's not a "production" image, but for me it works well.
admiralnorman said:
The bluetooth doesn't work, even though the device has the hardware. At this point, there is no speculation of it working in the forseeable future. HOWEVER, it works great using the WiFi hotspot on my HTC evo.
Click to expand...
Click to collapse
Just got an execuse to buy myself a new gadget - a HTC Evo or similar
"Is the Nook Color the right Android tablet for me?"
I think the easiest way to answer this question is by how much you enjoy tinkering with things. If you want a tablet that "just works" then you'll want a Xoom or Galaxy Tab. But if you love playing and learning about how your gadgets work 'under the hood' then the Nook Color will be the best gadget purchase you've made in awhile.
I've honestly spent more time "getting it to work perfectly" than I have actually using it, but I've loved every minute of it. I won't lie, Java and/or Linux experience is a big plus, but by no means necessary.
admiralnorman said:
At $250, the Nook Color sucks as an eReader. But as an android tablet, its the best purchase you could make. Nothing else comes close.
Click to expand...
Click to collapse
I just bought a Nook Color about a half hour ago and this post made me feel so much better about it. I've been debating it for some time and decided to take the plunge. I was worried that I might be late to the game but it has only been out for like 3 months.
Can anyone point me in the direction of Honeycomb for the NC? EDIT: Unless someone recommends a better ROM for now?
By the way, my name is Raj and I'll be spending lots of time here!
I've seen modifying build.prop, using sqllite, and changing the name of the otacerts file. Doesn't seem build.prop is valid here until someone gets a hold of one with the new update. But I don't want to lose my root. So, what's the consensus? (please vote in the poll)
Here are the 3 mentioned:
1. Rename OTA Certs
2. Use Sqllite
3. Edit Build Prop
The build.prop is sort of experimental but seems to be working so far from reports.
The consensus is definitely to read the other 1000 threads on the subject before starting yet another one.
Really? There are 1000 other threads that compare all 3 options?
All the ones I read are where someone brings up one thing and then a few other people chime in on a different one. I was trying to find out, in one place, what the most recommended one was.
It is my fault for not creating a poll at first.
It is your fault for being a jackass.
ADude said:
The consensus is definitely to read the other 1000 threads on the subject before starting yet another one.
Click to expand...
Click to collapse
I'd say he's read the 1000 threads, given the fact that he rattle off a list of suggested solutions from those threads.
FWIW, I too am interested in knowing if this issue has been settled. Just rooted my NC the other night, am really enjoying all teh apps I've downloaded and would be happy to block updates and wait for a rooted 2.2 update.
So if anyone knows the definitive answer ot the OP's question, please do let us know.
for what it's worth
doncaruana said:
I've seen modifying build.prop, using sqllite, and changing the name of the otacerts file. Doesn't seem build.prop is valid here until someone gets a hold of one with the new update. But I don't want to lose my root. So, what's the consensus?
Click to expand...
Click to collapse
Don,
I haven't read the reputed 1,000 other posts on this topic, so I don't know what consensus may have been reached there, but this is my take on it:
- otacerts renaming isn't going to be reliable
- the sqllite fix (modding the fota.mode item) is a permanent fix, which eliminates any possibility of OTA updates creating problems
- modding build.props may work, even if you don't have a master to reference from.
I.e., some reasonable higher settings for ro.build.version.incremental, ro.build.description, and ro.build.date MAY do the trick, even if they're not a clone from a legit updated version. I don't know (perhaps someone else does) if perhaps only one of those is really necessary, E.g., something like ro.build.description=2.1.0.428.int.enc.rrdp.s39975 may be enough to do the trick, since it holds the main versioning string (currently at 1.1.0.328).
So my recommendation if you want to be sure would be to do the sqllite fix.
- Mark
Flash CM7..... problem solved
I added links to the 3 methods I mentioned, for everyone's reference anyway. I did also read somewhere that someone said that installing CMR would stop OTA updates as well. But didn't see a lot of discussion about that.
xwint3rxmut3x said:
Flash CM7..... problem solved
Click to expand...
Click to collapse
I don't think CM7 is ready for prime time on the NC. Last I saw video driver and flash still had issues. I too would like to see a 2.2 stock update so it could be rooted. BTW I am running Nookie Froyo right now and it is pretty sweet.
I tried the CM7 Agnostic SDCard option and nightly build and, well... did I mention it isn't ready for prime time?
But I am one of those fringe lunatics that never says anything important, never gets noticed, and is instantly marginalized. I'll likely die an early death and no one will notice...
Sorry, to get back on topic, I don't think CM7 is ready yet for Nook Color.
Nothing to see here, move along.
migrax
Agree. CM7 is not quite up to where it needs to be as a daily driver.
build.prop flat out works... End of story.
Of course someone needs to get the build.prop from the new one when it's released, so if you're really scared about it, stay off wifi I suppose. But it usually takes a while before people start getting it.
khaytsus said:
build.prop flat out works... End of story.
Of course someone needs to get the build.prop from the new one when it's released, so if you're really scared about it, stay off wifi I suppose. But it usually takes a while before people start getting it.
Click to expand...
Click to collapse
The build prop only blocks one update. In order to block the Froyo update, you'd need the build prop for the Froyo update. That would only work until there is another update. Then you need the build prop from that update to block it. It becomes a vicious, never ending cycle. I may be incorrect in my understanding though.
I don't think anyone really knows at this point which is why there are "1000 threads" on the topic. We just all have to sit back, drink a beer or 7, and wait until the next update is being pushed out. I personally went with the SQlite edit in Root Explorer. Seemed like the easiest way to me.
Pre-dawn raid said:
I don't think anyone really knows at this point which is why there are "1000 threads" on the topic. We just all have to sit back, drink a beer or 7, and wait until the next update is being pushed out. I personally went with the SQlite edit in Root Explorer. Seemed like the easiest way to me.
Click to expand...
Click to collapse
That's what I'm going to try. I found the entry, but haven't changed it to "manual" from "auto" yet.
Update questions
I'm running Android 2.1 on my rooted Nook Color. What will happen if I don't block Barnes & Noble's upcoming update in April? Will my NC merely become unrooted and operate like a regular stock Nook Color? Is it possible that any damage will be done to the NC?
I'm actually curious to see exactly what an updated, unrooted NC will look like and how it will operate. I know that somebody eventually will come up with a way to root an Android 2.2 Nook.
My rooted 1.0.0 NC (Dec. ~8 autoroot) ignores the updates *DOING NOTHING AT ALL*. I can use the Market, download books from BN, etc.
Knock on wood!
cameraz said:
I'm running Android 2.1 on my rooted Nook Color. What will happen if I don't block Barnes & Noble's upcoming update in April? Will my NC merely become unrooted and operate like a regular stock Nook Color? Is it possible that any damage will be done to the NC?
I'm actually curious to see exactly what an updated, unrooted NC will look like and how it will operate. I know that somebody eventually will come up with a way to root an Android 2.2 Nook.
Click to expand...
Click to collapse
From what I've read on other Andriod devices, it relocks the device and you lose superuser. Still, I'm curious if all the apps I downloaded with root will work after the update. The device was a b-day gift for my sister and she really loves the e-reader aspect, hence why HC and nookie froyo haven't been slapped on there.
Well, if you run the stock launcher on a rooted Nook, you still see all the apps you have downloaded from Market in Extras. So I would assume that the 2.2 upgrade could preserve the apps you have on there. Though, I would always recommend doing a backup, getting updated, wait for whatever exploit is employed and re-enable your apps.
colorado_al said:
Agree. CM7 is not quite up to where it needs to be as a daily driver.
Click to expand...
Click to collapse
Don't tell that the to hundreds of CM7 users running this as a daily.
Honestly, the only functionality "hurting" right now is video performance, as caused by an audio wierdity. Past that, I can't think of alot of broken stuff CM7 needs fixed. Sleep battery performance can be improved i guess... as it is, i like CM7 ALOT more than Froyo (no more SOD!)
migrax said:
I don't think CM7 is ready for prime time on the NC. Last I saw video driver and flash still had issues. I too would like to see a 2.2 stock update so it could be rooted. BTW I am running Nookie Froyo right now and it is pretty sweet.
I tried the CM7 Agnostic SDCard option and nightly build and, well... did I mention it isn't ready for prime time?
But I am one of those fringe lunatics that never says anything important, never gets noticed, and is instantly marginalized. I'll likely die an early death and no one will notice...
Sorry, to get back on topic, I don't think CM7 is ready yet for Nook Color.
Nothing to see here, move along.
migrax
Click to expand...
Click to collapse
I'm with you. Tried the CM7 from SDCard yesterday. It was okay, but it didn't exactly rock my world. Waiting for all the bugs to get worked out. In the meantime, sticking with Nookie Froyo.
Divine_Madcat said:
Don't tell that the to hundreds of CM7 users running this as a daily.
Honestly, the only functionality "hurting" right now is video performance, as caused by an audio wierdity. Past that, I can't think of alot of broken stuff CM7 needs fixed. Sleep battery performance can be improved i guess... as it is, i like CM7 ALOT more than Froyo (no more SOD!)
Click to expand...
Click to collapse
I skipped over Nookie Froyo, but I used stock Root for awhile, and i've been on Cm7 for awhile and I love it. I agree video is not at 100% on cm7, but I really don't spend alot of time watching video on my nc at all. I downloaded the nook app from the market, and the tablet works great. The devs have done a great job, I have no issues using CM7 as my daily driver.
Gotta back you up madcat since we're the only pro CM7 users on this thread
Hi all,
Im looking to get a nook color from the states ( i live in the UK) and was wondering/slightly confused, if they are still "rootable"
I was reading the blog entries at nookdevs and it indicates that the latest generation isnt rootable.. .or am I wrong?
What I plan to do is get a friend of mine to order it online, and then bring it over when they come to the UK, hence we cant really check the firmware etc...
is it a safe bet?
Many thanks
Angelo
Currently b&n has done nothing to stop us from rooting the nook color. You may have been confused with the original nook, which they did attempt to prevent rooting.
But anyways long story short, yes all nook colors are rootable as of today.
Just got mu NC thru B&N eBay sale... and just rooted it!
So far nothing has been heard or rumored that they are going to try and prevent rooting on future NCs.
There IS an update coming out for the stock OS which is currently Eclair. The known additions are apparently some form of Froyo, Flash and a B&N App Market.
I do know quite a few people are waiting to see what the updates does before the root and/or install custom roms.
rogerdugans said:
I do know quite a few people are waiting to see what the updates does before the root and/or install custom roms.
Click to expand...
Click to collapse
Count me in there. If it has a good market, then I'm staying stock. If not, rooted stock.
awesome thanks
So I'm getting a NookColor sent over to the UK in a week or so and wanted some general advice etc. I've got to admit I don't really care for e-readers that much, at least not enough to pay full price. Anyway, I recently got an offer through work to get a NC from Barnes & Noble with 50% off so I figured it might be nice to have another gadget to play with. Then I stumbled across this forum and a few others and I have been really impressed with the potential of the NC as a tablet, so for $125/£75 I'd be a fool to miss out. Anyway, I'm looking for some opinions from your good selves:
Is it worth registering with B&N when I first get the NC? I'd more than likely use the Kindle book store if I was to purchase ebooks so I'm thinking I don't really need to register. How does this affect system updates and the warranty though?
I'm pretty much set on installing CM7 as soon as I get the NC but is it worth replacing the stock OS or just booting from an SD card? I'm guessing that it performs better from the internal memory and the process seems fairly simple, but is there any good reason to keep the stock OS loaded?
Will I need to root the device before attempting to install CM7? I've read mixed things about this so I am a little confused.
Any advice is greatly appreciated, and I apologize in advance for the boring noob questions!
DubiousPig said:
So I'm getting a NookColor sent over to the UK in a week or so and wanted some general advice etc. I've got to admit I don't really care for e-readers that much, at least not enough to pay full price. Anyway, I recently got an offer through work to get a NC from Barnes & Noble with 50% off so I figured it might be nice to have another gadget to play with. Then I stumbled across this forum and a few others and I have been really impressed with the potential of the NC as a tablet, so for $125/£75 I'd be a fool to miss out. Anyway, I'm looking for some opinions from your good selves:
Is it worth registering with B&N when I first get the NC? I'd more than likely use the Kindle book store if I was to purchase ebooks so I'm thinking I don't really need to register. How does this affect system updates and the warranty though?
I'm pretty much set on installing CM7 as soon as I get the NC but is it worth replacing the stock OS or just booting from an SD card? I'm guessing that it performs better from the internal memory and the process seems fairly simple, but is there any good reason to keep the stock OS loaded?
Will I need to root the device before attempting to install CM7? I've read mixed things about this so I am a little confused.
Any advice is greatly appreciated, and I apologize in advance for the boring noob questions!
Click to expand...
Click to collapse
Welcome to the NC community!
You seem to have a pretty good handle on things. Nothing on the warranty page (http://www.barnesandnoble.com/nook/protectionplan/standard/index.asp) mentions that registration is necessary to be eligible. However, once you install CM7, it's a moot point, as that will certainly void the warranty. But it's near impossible to break the software beyond repair, so you can generally restore to stock if for some reason you need to submit a warranty repair.
Replacing the stock OS is a matter of personal preference. I personally tried running CM7 on the SD card temporarily and decided that since I was never using stock, that I would just get rid of it. Give it a try and see if you like it; it isn't too hard to install internally if you decide to get rid of stock, and as I said, restoring stock isn't too difficult either.
As far as I know, you don't need to root stock to install CM7. http://forum.xda-developers.com/showthread.php?p=12801192 is a guide to install it internally without root.
You have a couple of options avaliable to you. If you want to use it as a stock reader for the barnes and noble book store maybe you should consider Cm7. I curently run Cm7 on a class 6 8 gig card and i get very little lag.If you find its still not fast enough you also have the option of using dalingrins over clock kernel which will boost the performance.
Running off the sd card will give you the best of both worlds win/win.