Related
i bought my nook today based on all the stuff happening here, been on xda since just before evo launch. i see alot of methods for rooting etc. i'm just confused. all i'd really like to do is get root with su, and get market, gmail working along with everything else i use. whats the easiest way to do this.
oh and i have totally forgotten how to use adb......been to long since i needed to. again sorry for the noob questions, i just want to do whatever works best and i can't tell what does. on and i'm running 1.0.0 should i upgrade or what???
oh and keeping the B&N software isn't a must, but would be nice
Update to 1.01, then use the latest build of autonooter. No need to use adb, as Android Market will be installed by autonooter. Your B&N stuff will still work, except for in-store reading.
nookdevs.com/Portal:NookColor[/url]
This should be a good resource for you.
IMO, I would suggest updating to 1.01 as the above poster said, and then rooting using autonooter. But in addition I would also update to the new Market.
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.
B&N Update Next Week?
Just showing you the link:
http://androidos.in/2011/04/nook-co...-update-on-april-25-froyo-incoming-with-apps/
Doubt it. Would be all over the internet if it was (Engadget etc). Seems like a shady site.
I saw the same thread earlier today on the Barnes and Noble site.
I cannot post the link but title of the thread is "Monday it is"
http://bookclubs.barnesandnoble.com/t5/NOOKcolor-General-Discussion/Monday-it-is/td-p/970372
Look at post #6 in that thread. "Go to B&N if you need help with anything." Yeah right im going to make a trip to Barnes and Noble and tell a representative that i don't fully understand how to use the new update LOL.
I too heard the chatter, it might actually be monday. Let's hope they come out with a newer kernel. The one we have is kind of getting old.
I just hope the update contains something of use to the community that it doesn't already know -- like being able to use Bluetooth beyond a couple of feet.
Just as interesting as the date is the content. If you keep reading that thread, you get a link to another thread where they say a manager actually saw (and shared) the update: She shared what she saw....WOW. Flash, new PDF and lots of aps.
Monday will be interesting: if the updates actually comes, will it manage to get past the OTA blocking?
Just calm down and relax,if you're looking on the B&N Community board there's daily some folks that fool around those update.
Does anyone know if this update could maybe increase app compatibilty due to an official update to froyo such as Homerun battle when we get it rooted with android market and/or sideloading? Cause that would be the only reason I'd have for updating.
It will be interesting
Agree. It will be what it will be. But to be on the safe side, I've flashed back to stock 1.1.0 for a couple people at work who rooted. That should allow the OTA (whatever it will be) to install as BN designs.
And so it goes....
I really hope it's 2.2 and not 2.1 with an app store. I wonder if they're going to release a new kernel (and its source)? That would really help out the CM7 people...
I would think the likelihood of an update this week is very high. Remember they're taking on a major retail partner in Staples starting May 1st. If they have an update, they would want to make sure that it's finished before Staples start selling them, it'd make things a lot easier for their new partner.
buzz killington said:
Remember they're taking on a major retail partner in Staples starting May 1st.
Click to expand...
Click to collapse
Where did you hear/read this?
I think one of the most exciting features of the upcoming update will be an official froyo build that will have full aceess to all of the internal storage. That and an overclocked kernel plus being rooted will be pretty damn awesome in my opinion. I can't wait, time to backup my nook and revert to stock in preparation.
BN
Paul22000 said:
Where did you hear/read this?
Click to expand...
Click to collapse
Straight from a BN press release
http://www.barnesandnobleinc.com/pr...aples_announces_plans_to_sell_nook_color.html
Also the fiscal year for BN ends on 4/30. There may be things you want announced before year end or if it is bad news after year end. The NC product distribution strategy is beginning to resemble the Apple one. However, BN does not have its app developer support strategy in place.
Auto Update came through today (despite devicemanager editing and OTA certs renaming)
I was using my nook today, when all of a sudden a B&N permissions dialog screen popped up (specifically, it said something like "permissions error, rebooting". Then it rebooted into clockwork(???) which formated my data and cache partitions, pulled up a list of errors trying to change other things (possibly because I am rooted with an OC kernel?), and then rebooted.
Despite this, it managed to reboot into stock. I didn't get any further than the setup, before I decided to flash my nandroid backup. I'm actually kind of regretting that a bit now, since it would have been interesting to see what the new stock was like (presuming it worked correctly), but ultimately, I think it is probably best to wait for XDA to tell me what to do about updating or otherwise. In the meantime I'll be leaving my wifi off.
I've been debating upgrading to CM7, but the sleep / battery issue has prevented me. If this update really is froyo, and the devs here get it rooted nicely soon, I may not make that step at all, or at the least I may be able to wait much longer for the sleep issue to be fixed.
Also of interest is the fact that I had renamed the OTA certs and used sqlite editor to tweak the devicemanager.db file. I don't recall if I had spoofed the build.prop or not. But this seems to imply that we don't really have any reliable way of preventing OTA updates at this point, other than installing a completely new rom. That alone might be enough to warrant switching to CM7. I'm so confused!
I'll have to grab my NC and turn it off and take out the sd card.
I don't think I've turned it off for a couple of weeks...running CM7.
Nothing new showing up here yet:
http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/?cds2Pid=35758
CM7 won't auto-update, will it? I was running stock 1.0 rooted (and now that I've flashed my nandroid backup, I am again, though I lost two weeks worth of tweaking).
I'm the original owner of a Nook Color that's been jail-broken since day one.
I've had tremendous fun using it, following the ROM development work, and trying out new ROMs over time. It's also terrific for reading Kindle books ;-)
But it's time pass it on.
My question: should I leave it jail-broken (currently fresh, unregistered Phiremod v7 Test 2 + GApps) or return-to-stock for the next owner?
I guess you could let the buyer make that decision, that way you could probably sell it faster.
First off, Android devices are rooted, not jailbroken.... Meh.
Second, agreed, leave it to the buyer. If you want to sell it Stock (ie: buyer fears modification) then move it to stock. If you want to sell it with CM7, put CM7 on there and sell it.
When I sold my last Android tab, I said in the ad it was running cm7 but that I would restore it to stock. The guy who bought it didn't care one way our the other.
Sent from my NookColor using xda premium
Return to stock and offer rooting as a free optional service.
i would restore it to stock just to make sure none of my sensitive data is left inside, then ask the buyer if he wants it rooted or stock, and if he needs help rooting, do it for him
jgaf said:
I guess you could let the buyer make that decision, that way you could probably sell it faster.
Click to expand...
Click to collapse
Agreed... either way you should disclose you've modified the ROM.
khaytsus said:
First off, Android devices are rooted, not jailbroken.... Meh.
Click to expand...
Click to collapse
Second off, his device is neither--while it has root, it's more accurate and descriptive to say he's flashed a custom ROM. To say it's rooted implies heavily that it's still running the original software. ROM is even inaccurate, being a linux holdover from older tech, but it's the most broadly accepted term. If you want to be really correct, he's running an alternate OS with root access.
All of which is beside the point. I would advertise it (assuming you're putting up ads) as "Rooted Android Tablet (7-inch)" and explain in the description that it's a Nook Color running Phiremod, mentioning the quality screen and unlocked bluetooth. You can throw in a bit at the end that it "Can be reset to stock firmware or alternate ROM if desired," assuming that doing so is a trivial effort for you, which it should be. Doing it that way gets you the broadest pool of prospects and uses the custom ROM as a selling point.
If you want to be really correct, he's running an alternate OS with root access.
Click to expand...
Click to collapse
At that point you could say he running CFW!!
PSP!
captainskyhawk said:
At that point you could say he running CFW!!
PSP!
Click to expand...
Click to collapse
If you want to drag in more esoteric but still accurate acronyms, sho 'nuff.