Just wondering why there are no "full" roms out that get rid of all the original nook stuff.
Probably showing my complete lack of knowledge here but thats ok
If anyone who has the skillz could let me know why this isn't possible yet I would love to know. Thanks!
lafester said:
Just wondering why there are no "full" roms out that get rid of all the original nook stuff.
Probably showing my complete lack of knowledge here but thats ok
If anyone who has the skillz could let me know why this isn't possible yet I would love to know. Thanks!
Click to expand...
Click to collapse
I don't have the skills, but my guess (guess, opinion...fwiw ) is that while it might be possible, many users still want the functionality of the NC as a reader is some fashion.
You can always flash a rom then use Titanium Backup to freeze "nook stuff". Freeze apps one at a time, make sure the basics are still working, then keep going.
Nookie Froyo and CM7 are both under active development.
Neither is ready for general use.
I knew about cm7 but hadn't heard much about nooki froyo other then its current state.
thanks for the info
I understand there are driver issues and such to deal with on froyo and gingerbread but would it be easier to create a 'clean' 2.1 rom? this is kind of what I was thinking when I made the thread.
My guess is there's some stuff like Settings or Frameworks that would need to be edited, not just easily removed.
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'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
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.
Im buying a new NC of craigslist today. I want to make it into an andriod tablet. I just want to know if i should watch the youtube videos for it, or maybe go through a forum on here.
Not sure what the best is right now. Any help is appreciated!!!
Thanksss
Congrats!
this was the way i rooted my NC and it was way easy.
http://www.youtube.com/user/huskermania#p/a/87190C927F09F6EE/1/MUoHALWvPts
btw im running cm7 and loving it
Video might be good to get a visual idea of what to do, but I suggest reading up as well. It's been a while since I rooted and there seem to be slightly different methods to get what you want on there. I started off just updating and rooting stock, that's pretty painless and simple if you've never done any sort of flashing. Then you can try out dual booting or CM7 or whatever you feel. Just my 2 cents. Good luck!