Related
It looks like the 1.1.0 update is now available. Not sure what it includes yet.
h t t p ://w w w.barnesandnoble.com/u/nookcolor-support-software-update/379002520/?cds2Pid=35505
Thanks,
Matt
Now with froyo. I am probably not going to try out this update.
It looks like there is a lengthy discussion about this in the Developer section, you should probably check that out for more info.
Thanks,
Matt
Can I install ver. 1.1.0 after rooting or it's dangerous for Nook Color?
It indeed seems to break rooting.
However for me most important it has sorted out the Sound Issue once and for all. Now I can put it in and out of standby, and sound is always there after it wakes.
Also flickering has been addressed seemingly by upping the refresh rate.
It would be nice to see 1.1 version rooted soon ... I think blocking OTA updates is kind of an option no one wants - especially if there are bugs to address.
I have not rooted my nook col. as it is going to be a gift to my brother who does not care about tablet - but reading 100%... however, getting another one is very likely to be an option for my life which I will probably root... Now, if something comes our way like it did for HD2 where we can load SD Card based Android builds - it would be AWESOME
eenbox said:
Now, if something comes our way like it did for HD2 where we can load SD Card based Android builds - it would be AWESOME
Click to expand...
Click to collapse
Umm, unless I don't understand what you are asking for, we already have SD Card based Android builds that work just fine!
http://forum.xda-developers.com/showthread.php?t=883175
http://forum.xda-developers.com/showthread.php?t=922324
Damn. How do I block this update for good? It looks like it's an automatic thing.
A. Nonymous said:
Damn. How do I block this update for good? It looks like it's an automatic thing.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=930382
Try that, but nobody is 100% sure it'll actually not download and install the OTA.
Do delete the file in /media if it's already downloaded though.
Not real confident any of the re-editing approaches are going to actually prevent the update. If they do, great. Fortunately, it looks like a couple of developers are already working on methods of rooting 1.1. They seem mostly to be using CWM and update.zips though. Haven't heard anything from the Autonooter developer yet, but he may be working on solutions as well.
Ok, here's the deal.
Fiancee got me a NC for my birthday because she read that it can be rooted and made into a formidable tablet. I agree with her and am stoked.
I don't have any dev experience, but I'm very familiar with rooting and flashing ROMs to our EVO 4Gs.
However, after reading through the developmental forum, I'm confused as to what steps I need to follow to turn my NC into a CM7 tablet.
Do I run autonooter? (The B&N store updated my NC to the 1.1.0 software yesterday in-store) Which one? Do I run it first?
After that, how do I flash CM7? Is there a more stable system\ROM\build?
With dealing with SD cards, I know this will be a bit against the grain for me because Rooting\Flashing the EVO is so easy and simple.
Any and all help will be appreciated.
(Side note question: Has anyone used a Steinheil Screen Protector on their nook? I see that SGP makes one for the Galaxy Tab, which has similar dimensions as the NC. Anyone?)
This seems like easiest to follow:
http://forum.xda-developers.com/showpost.php?p=9816724&postcount=64
kapurcell said:
This seems like easiest to follow:
http://forum.xda-developers.com/showpost.php?p=9816724&postcount=64
Click to expand...
Click to collapse
Awesome.
So that "roots" the nook, like SimpleRoot does to my EVO?
And then I go through the process in the CM7 Phiremod post in the Dev forum?
Also - should I go buy a second MicroSD card to use, leaving the current one in the nook as a clean backup?
It's useful to have multiple microSD. I have a couple 2GB microSD for nootering and flashing new rom. I use a 16GB for main use as backup and data storage.
If you're new to Android, I recommend just nootering your stock 1.1 NC because it's most stable. Froyo, Honeycomb, and Gingerbread built are still in development and are being tested.
Sent from my NC using Tapatalk
I'm not new to Android, as I've been using various CyanogenMod and MIUI builds on my EVO since I bought it last year.
What I am new to is the use of SD cards for flashing. That's where I'm a bit shaky on the steps.
Before you can get a good answer we need more infromation.
1) do you care about the B&N stuff that your Nook came with?
2) what is your goal?
a) e-reader that can do tablet functions
b) Tablet that can do e-reader functions
Do you want to run the alt OS from the SDcard or from the flash memory?
So far there are 2.1, 2.2, 2.3, and 3.0 ROMS for the Nook. Where do you want to be?
painter_ said:
Before you can get a good answer we need more infromation.
1) do you care about the B&N stuff that your Nook came with? - Not really. As long as I have a way to read books that I get off demonoid.
2) what is your goal?
a) e-reader that can do tablet functions
b) Tablet that can do e-reader functions Preferably this.
Do you want to run the alt OS from the SDcard or from the flash memory?
So far there are 2.1, 2.2, 2.3, and 3.0 ROMS for the Nook. Where do you want to be?Are there advantages\disadvantages? Which is the most stable solution to rooting\flashing? I have CM7 on my EVO now, though I'll probably be switching over to the latest MIUI later tonight. I wouldn't mind something similar to CM7 on my NC.
Click to expand...
Click to collapse
Does the above help at all?
Bump for some help. Thanks guys.
I've only been a NC owner for a week. From my experience, you need to play a bit. Usual disclaimers apply:
1. spend time playing with the default B&N config. Enjoy. Ok, for me that got boring after about 1 hour.
2. Autonooter 3.0 (since you are on 1.1.0). Then just play with your rooted NC. Enjoy. I was amazed at what this little guy could do after only a root. Test a bunch of apps. Read a bunch on this website. Test more apps that you read about. Try different backup software. Get comfortable with Eclair. Run Quadrant. Enjoy.
3. Dahlingren's OC kernel. Make sure you get the Eclair kernel. I installed the 1100 MHz one, and monitored for overheating and random reboots/force closes etc. This one worked well for me, and amazed me again at how much faster it was (run Quadrant again). Get comfortable with the procedure to flash a rom with CWR. Enjoy.
4. CM7 with OC kernel. Play, test, enjoy. If the current bugs are deal breakers, revert back to Eclair, or try Froyo or some other flavour. Enjoy.
It seems to be darn near impossible to brick this guy, so I haven't worried too much. Worst case scenario is I have a $250 paper weight, but the best case has been worth the risk to me.
Enjoy.
...I lucked out and got a brand new one with 1.0.0 firmware, so I stuck with it and used the AutoNooter for that version, then blocked B&N from pushing updates. I have the whole thing running basically how I want it to now and I'm very happy, but I have one burning question:
Is it worthwhile to overclock it and would that really enhance my user experience at this point? I've never overclocked anything before and the last thing I want to do now, after all the tweaking I did and money spent, is to destroy the little guy.
So, experts hereabouts:
Given my hardware, firmware, etc., do you think it's safe and worth the effort to use a kernel to push it to 1.1Ghz or 1.0Ghz? Are these kernels stable or am I going to regret it when something really wacky happens?
I keep mulling it over, so any help is greatly appreciated.
Most people seem to report that 950 Mhz is tops for 2.1 (the android version currently on your nook). It highly unlikely that it will harm the hardware and you will see a modest increase in performance.
For 2.2 and 2.3 (CM7) people are going as high as 1.1 GHz without issue. I'm currently at 1 Ghz and am enjoying it. No problems (knock on wood).
Thanks for the response! I was also concerned that staying at 1.0.0 was unwise or that, perhaps, I should try using Android 2.2, but that all seemed to be fairly experimental/scary to me.
junkrobot said:
Thanks for the response! I was also concerned that staying at 1.0.0 was unwise or that, perhaps, I should try using Android 2.2, but that all seemed to be fairly experimental/scary to me.
Click to expand...
Click to collapse
I have only had my NC for a little over a week now and have had all the popular roms installed. I have tried CM7, Froyo and Honeycomb. It's all pretty easy just make sure you read all the install instructions and you should be fine. Also I made nandroid backup as well as a titanium pro backup of my apps. So it is pretty easy to revert back to my stock rom if I wanted. My suggestion is to read through the threads for all the different roms in the development section, it will give you a good grasp of how to install and what bugs are still existing. A good start for you is to get titanium backup and rom manager so you can do the backups first then start experimenting to see what you like.
From my limited testing I don't think CM7 and Honeycomb are quite ready yet, they still need a couple things worked out which I am sure will happen soon especially with the SDK released for Honeycomb now. I liked Honeycomb the best but a couple apps I use regularly wouldn't run for me at the present stage(Aldiko and IMDB, I didn't try much else as I really use those apps alot and couldn't live without them). As for CM7, everything I tried worked well but the battery drain seemed rather high for my liking compared to stock. I am now running Froyo customized 0.6.8ver2, I loaded it on last night so haven't had much time to play around with it yet but so far it seems to run pretty well, all apps I have tried work. Not sure on the battery drain yet but will keep an eye on it.
If you need some help let me know, I am not an expert but haven't bricked my NC yet and I don't mind helping out where I can.
kevin
Thanks a ton, Kevin! This seems like a really nice community. I'm going to keep researching and see what I can conclude. I made a back-up with Clockwork the other day just in case something weird happened, so I'm weighing out the pros and cons while sifting through these threads. Honestly, I don't have a problem with how things are running now, but making a little snappier, in the parlance of the boards, would be nice. I wonder if there's a way I can up the performance without overclocking it?
Also, this is the method I used to block B&N updates:
http://forum.xda-developers.com/showthread.php?t=946969
It seems there was a bit of debate as to if this would actually do the trick, so I'm kind of worried. My NC has been connected to wifi constantly since day one, so I don't know if this is/isnot working. Anyone have any advice in this regard or experience? How do updates get pushed?
junkrobot said:
Thanks a ton, Kevin! This seems like a really nice community. I'm going to keep researching and see what I can conclude. I made a back-up with Clockwork the other day just in case something weird happened, so I'm weighing out the pros and cons while sifting through these threads. Honestly, I don't have a problem with how things are running now, but making a little snappier, in the parlance of the boards, would be nice. I wonder if there's a way I can up the performance without overclocking it?
Click to expand...
Click to collapse
Hey Junkrobot - Just take your time. It takes a little while to get a feel for things. I have been rooting and installing roms on Android phones since they came out. At first, I would worry a lot but as I gained experience, I felt more comfortable. Now I think I enjoy trying ROMs more than actually using the device like a normal person.
The Nook Color is a great device to get started because it boots from the sd card which means it is nearly impossible to brick. If something gets messed up, you can always boot from a bootable sd card and install a rom or restore a backed up image. That said, if you enjoy the device as it is, there is no rush to upgrade.
I think part of my anxiety is just the sheer amount of time it took me to get things in order since I was so new at it. Day one was pretty stressful, as I'm sure it was for most folks.
Just an FYI, the Nook is really hard to brick since it boots up first from the SD card. You can always make a CWR card which should allow you to flash it back to stock or another ROM.
Does backing up in Clockwork also preserve my apps and settings?
I'd be really stoked if I could also somehow be sure that OTA can't push an update on me. In my mind, B&N is out there, waiting to strike.
No, use Titanium Backup or MyBackUp
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
Doing a lot of reading on the changes that B&N is doing to the partitions of the Nook Color. Wondering now how it will affect those of us who are about to buy them with the intent to root and use a new ROM.
Details on the changes in my post linked below.
http://forum.xda-developers.com/showpost.php?p=13962169&postcount=17
Considering most people probably buy the NC for an actual e-reader, it won't affect them, but for us at XDA, it may stop a few people who are lazy, or people it think it's too much trouble.
If rooted builds don't have access to the 7GB partition for non-B&N content, it will make rooting pretty worthless, but then rooting is already pretty worthless compared to CM7.
A CM7(or whatever ROM) install to eMMC can probably treat most of that 7GB as system space, which could be even more beneficial to CM7 than B&N, given the order of magnitude more apps available for CM7.
A CM7 install to SD is straight up losing 4GB of storage (as well as the flexibility of sharing that storage with whatever OS is on the eMMC), but is otherwise unaffected.
I suppose it could be seen as a sneaky way of making the non-B&N options look less appealing to new owners.
My guess is that this was done in an attempt to keep the ROM installs isolated to just the SD card.
That way B&N can claim that their device isn't being affected by rogue hackers!
I Am Marino said:
Considering most people probably buy the NC for an actual e-reader, it won't affect them, but for us at XDA, it may stop a few people who are lazy, or people it think it's too much trouble.
Click to expand...
Click to collapse
Please clarify your statements! It is Impossible to install a Rom to the EMMC of a newly partitioned NC! Don't generalize all of us with new nooks into a catagory of Lazyness!
Also, 2 days ago you post this--Quote
I'll be honest. The NC confuses me slightly when it comes to how to root, flash ROMs, etc. compared to my Incredible, it feels like day and night.
I made a thread about a month ago about wanting to learn the process but since then it has changed greatly with the 1.2 update.
I would really like if someone could detail out to me the steps I need to root and have CM7 on the NC.
I have questions that are probably answered right in front of me but they get lost in the vast amount of posts.
•Since the eMMC is pretty much canceled out for the time being, I want to run CM7 off the SD card, I've already read a Sandisk Class 2 8 or 16GB is the right card for this, how the hell do I put CWM, CM7, etc on this one SD card or am I supposed to use 2-3 different cards for the process? Then what do I do from there?
•What is the most stable, but feature packed release of CM7 at this point in time, like what build, which kernel, etc.? Market and GAPPS working?
•Assuming the SD card is good, does running off the SD card impact performance or is it as slick as running off the internal?
Pretty much I'm starting from dead scratch when it comes to the NC and I feel the guide threads don't do enough justice to explain certain questions fully enough or at all?
If it helps at all, I just plan to download apps, internet browse, stream music from Mougg, little or no game playing, and overclock.
So someone please help me out? It's not like I know nothing, as I have a rooted and kept up to date phone but for some reason, the NC confuses me and I may be overthinking.
If I remember any more questions, I'll list them. Thanks.
Sounds like to me, you are a Bit Hypocritical!!!!
Jimbo67 said:
Please clarify your statements! It is Impossible to install a Rom to the EMMC of a newly partitioned NC! Don't generalize all of us with new nooks into a catagory of Lazyness!
Also, 2 days ago you post this--Quote
I'll be honest. The NC confuses me slightly when it comes to how to root, flash ROMs, etc. compared to my Incredible, it feels like day and night.
I made a thread about a month ago about wanting to learn the process but since then it has changed greatly with the 1.2 update.
I would really like if someone could detail out to me the steps I need to root and have CM7 on the NC.
I have questions that are probably answered right in front of me but they get lost in the vast amount of posts.
•Since the eMMC is pretty much canceled out for the time being, I want to run CM7 off the SD card, I've already read a Sandisk Class 2 8 or 16GB is the right card for this, how the hell do I put CWM, CM7, etc on this one SD card or am I supposed to use 2-3 different cards for the process? Then what do I do from there?
•What is the most stable, but feature packed release of CM7 at this point in time, like what build, which kernel, etc.? Market and GAPPS working?
•Assuming the SD card is good, does running off the SD card impact performance or is it as slick as running off the internal?
Pretty much I'm starting from dead scratch when it comes to the NC and I feel the guide threads don't do enough justice to explain certain questions fully enough or at all?
If it helps at all, I just plan to download apps, internet browse, stream music from Mougg, little or no game playing, and overclock.
So someone please help me out? It's not like I know nothing, as I have a rooted and kept up to date phone but for some reason, the NC confuses me and I may be overthinking.
If I remember any more questions, I'll list them. Thanks.
Sounds like to me, you are a Bit Hypocritical!!!!
Click to expand...
Click to collapse
What did quoting me prove?
Nothing.
I said the new partitioned NCs may lead to people not wanting to root because those people may be scared of going through the trouble to try to learn how to do root stuff otherwise or people too lazy to work around it. Had nothing to do with generalizations, before you try and make me look foolish, stop doing it to yourself.
By no means am I an expert at the content on this website and I'm quite new to the NC scene but that doesn't make me stupid and doesn't give you the right to try and throw me under the bus for some e-cred.
Besides all of the reading, like how hard is it to root a NC really?
Step 1. Put file on SD Card
Step 2. Boot up
Step 3. Um...like thats it!
I've had a harder time opening the front door when I've had a few drinks
*Just to clarify...the above was an attempt to difuse the situation with brevity*
Carry on!
Richard
I thought I was keeping current on Nook Color issues (rooting, ROMs, etc) but this is the first I've heard about changed partitions and how it may effect rooting the device. I'm running CM7 stable on internal memory and love it. I've got a microSD that boots the Nook into clockwork recovery or whatever that's called, I wipe everything and then install CM7 and gapps from the SD card, reboot and I'm done. I've installed the same setup on Nooks for two friends who envied my tablet. A third is about to go buy a Nook so I can do the same. if the Nook she buys has these new partitions will this process NOT work?
If you guys get the new partition, give this a try. I've done it myself since I had the new partition.
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110
Works perfectly
So I got my refurbed Nook today and it has the changes to the partitions (blue sticker on box). I tried to load CM7 via CWM on the SD card and it won't boot at all. Is this because of the changes to the partitions?
cheez99 said:
So I got my refurbed Nook today and it has the changes to the partitions (blue sticker on box). I tried to load CM7 via CWM on the SD card and it won't boot at all. Is this because of the changes to the partitions?
Click to expand...
Click to collapse
Yes....and see the post right above yours on how to solve it.
I just bought a nook yesterday; It was an older one still running the 1.1 upgrade. If I upgrade to 1.2, will my nook be repartitioned automatically?
schaan383 said:
I just bought a nook yesterday; It was an older one still running the 1.1 upgrade. If I upgrade to 1.2, will my nook be repartitioned automatically?
Click to expand...
Click to collapse
As far as I know, No, it will not be.
I don't understand why B&N is putting so much effort into this. Rooting doesn't violate any carrier agreements, since this is a wi-fi only device, and their store is still available for use after a root. If they're worried about book piracy, that can be done without root. Any insights?
Sent from my CLIQ using Tapatalk
Deegan87 said:
I don't understand why B&N is putting so much effort into this. Rooting doesn't violate any carrier agreements, since this is a wi-fi only device, and their store is still available for use after a root. If they're worried about book piracy, that can be done without root. Any insights?
Sent from my CLIQ using Tapatalk
Click to expand...
Click to collapse
B&N discourages rooting for many reasons, including the fact that they only paid Google specific licensing fees and now most of us are running the full OS.
There is also the fear that we will damage the device and return it, which will directly affect their bottom line.
Whether or not WE think rooting is good may have nothing to do with how B&N and its investors thinks this affects their image.
No matter what, rooting is an out of control rogue operation in the eyes of any company. That lack of control scares them.
Secretly they may be fine with us rooting, but they are under a business obligation to their partners to protect the original design specs.
Sent from my rooted Nook Color acting as a Galaxy Tab.
Well for me, I would not have bought the Nook Color unless the root and full android install was an option.
I think there is probably a lot of people in the same boat that bought the device because it was primarily a nice way to get into a tablet with the added bonus it is a very good size for an e-reader.
Bottom line, there probably is a substantial increase in sales because of what people have done here making this a full android tablet.
It would be ill-advised for BN to impact this capability.
tbXDA said:
Bottom line, there probably is a substantial increase in sales because of what people have done here making this a full android tablet.
It would be ill-advised for BN to impact this capability.
Click to expand...
Click to collapse
I don't know about that.
Remember although like 9/10 of the people here root and mod things, we're still a very small minority, most people probably actually did buy the NC for the e-reader, only as people keep word of mouth going do they figure out more about what they can do.
I Am Marino said:
I don't know about that.
Remember although like 9/10 of the people here root and mod things, we're still a very small minority, most people probably actually did buy the NC for the e-reader, only as people keep word of mouth going do they figure out more about what they can do.
Click to expand...
Click to collapse
Absolutely right. There have been over 3 million sales of the Nook Color so far. We may be a very large community but we are a drop in the profit bucket, and most likely considered a risk in comparison.
Sent from my PC36100 using XDA Premium App
I just got a new blue sticker nook color and am having some issues. I understand that the software for installing images hasn't been modified to reflect these partitions yet but does it make sense that running from sd shouldn't work? I've been following verygreen's guide and using the exact versions and links that he has there but it hangs on "Loading...". If I try to use the nightlies instead I can sometimes make it to the cyanogenmod animation but every one I've tried freezes either there or earlier. Has something changed with the blue sticker nooks that would make us expect either generic-sdcard-v1.2.1 or update-cm-7.1.0-RC0-encore-2.6.32-beta3.1 to no longer work properly? I thought that this might be relevant to post in verygreen's thread but I haven't made enough posts to do that yet.
Help Please
Ok, so I've had a rooted NC since February and have ran most everything at one point or another thanks to the good people at XDA. I currently have CM7 .32 on mine.
My buddy saw my system and decided he liked it and bought one. I ran clockwork mod and flashed CM7 .32 on his NC. There was no notification bar on his and the cyanogen settings were force closing. I think he may have had the partitions on his. I'm trying to create an SD card CM7 for him, but I would like to fix his emmc as well. The adb partition fixes are really above my head as I have never been able to get adb to work.
Any help is greatly appreciated.
Thanks.