Related
Ive been pretty active in the xperia forums here and at htcpedia, but on sunday my xperia got stolen. I was hoping to get the Rhodium but Vodafone Insurance are up tight, in the end I bartered myself to a Vodafone Htc Magic. I like using Andoid and loved playing on the Hero, so I thought it was worth a shot.
I've been trailing through the internet looking for how tos and all sorts, but it seems with Android there are thousands of different ways of doing everything! I went on the Unlockr which gave me a really useful guide to flashing and rooting etc, but it seems that a lot of the stuff is now not in fashion and superceded by other methods.
I'd like to know how to root (heard there was a Cyanogen app on the market), backup (not sure why I should backup but there we go), partition (whether I use Linux swap or W/E, apparently something else is faster, and I don't have Ubuntu) and flash a new rom or update. Finally I'd like to know what sort of rom would be recommended, obviously Ive looked at Cyanogen and would like to flash it, as well as Donut.
Thanks in advance!
update: seen a similar thread but the link provided as a solution looks way too compliacted for me. There are some who ask you to download SDK and stuff, but the Unlockr didnt seem to say that. Also reading Cyanogen's thread, his barebones rom won't include google apps. How can we back these up? Argh I'm so lost.
http://forum.xda-developers.com/showthread.php?t=563679
that is the most up to date guide for rooting your phone. also it has screen shots and all so you know what you are looking at, for what you are doing.
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
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).
Hello xda. I've been a big selfish user of the stuff provided here for a while, as have many. I own an XPERIA X8 and it's the best phone I've ever owned (ehem.. perhaps because it's the first smartphone I've ever owned). I just wish it was a little better. I enjoyed the stock stuff for a while until my internal storage filled up too much, then I rooted and upgraded it to an easy to install Froyo ROM as it was my first time doing such things (as good as I am with programming PC's, I thought I would surely screw that up). It was great and had kept me happy for over a year, but I didn't realise how old Froyo was until I heard about Jellybean and 'Project Butter' and how it even outperforms old versions of Android. I've been limited in Froyo to relatively basic stuff anyway so I thought since I'd basically installed an android version only one step up from the stock Eclair, there'd be a lot of better versions out there.
This is where my nightmare begun. Since I already had xRecovery, I thought the process would be as simple as "download rom, install in xRecovery". A bit too ambitious, I ended up "soft bricking" my phone and having to fix it by going back to Eclair. Then, somehow, I could not even root the damn thing under the guidance of any tutorial. It's like it suddenly caught an immunity. After ages of meddling I managed to do so and get to the next step. Then the problem occurred that Superuser wasn't kicking in and allowing anything root access. I also had problems getting a new kernel on the phone and ended up only managing to install some random kernels I wasn't even sure supported the rom I was trying to install. I had some more problems trying to install CWM and it was around then I noticed another occurring problem. Apparently for installation of Jellybean, I needed to unlock bootloader, which apparently can't be done on devices with a certain version of motherboard. Mine is 11W41. I heard that this sometimes doesn't matter depending on the specific version, but after all the problems and reading up how hard it would be to recover from a problem if it occurred. So after a long time not finding alternate solutions, I decided to go for something lower.
Ice Cream Sandwich apparently had a similar problem, but I didn't spend long looking (by that time it was really late at night and I just wanted to at least get rid of Eclair again). Eventually I installed Gingerbread, which managed to work well... the second time I tried. The first time I mucked something up and ended up going back to Eclair yet again. Well, now I at least have the GingerXperia Revolution V3 rom installed, but I'm still wondering if this is the best I can do according to the X8. So yeah, that's the rant of my nightmarish story, but this is, ehem, a Q&A... so my question is, before I get too settled with my current phone set-up, is there any better option for my phone? Have I misunderstood some things and I actually do have a way of updating my kernel in order to install a better rom? From a rom, I obviously just want a well-packed version of android (Froyo was way to simplistic, having very few options to improve the experience), which is fast and suitable for every day use. As a bonus I would like it to be swappable so I can increase the RAM with SD memory and increase internal storage size (even with the ability to move apps to the SD, the phone fills up way too fast). I'd be very surprised if I've managed to pick the best way to upgrade my phone.
I know this heavily depends on opinion, so I just want to hear it. If there is better things I can do to it, I could do with a point in the right direction!
i honestly read that long post. welcome to xda mate.
tbh, i haven't tried that particular rom yet. so i can't tell you rom is "better" (which is subjective, if you ask me), so i'll try to answer the other points in your post.
since you have a locked bootloader, we're limited to roms, apps, and tweaks. a different kernel would do wonders to your phone, but since that's out of the question i think the best way to go is how to improve performance using other methods. please note that whatever i write here is my opinion. other users may think differently.
apps: i use mounts2sd for swap and a better alternative to our native app2sd feature. greenify is another app that is getting great reviews, though i try to not use task killers as much as i can. if you're into mobile gaming chainfire 3d is another app you could use.
tweaks: crossbreeder and v6 supercharger. i've personally used (using CB right now) try them and see. remember to make a backup to be safe.
that's all i can think of in short notice. i'm sure there are others and you just need to look in xda more. also, try a couple of roms before you get settled on one.
Deji666 said:
Hello xda. I've been a big selfish user of the stuff provided here for a while, as have many. I own an XPERIA X8 and it's the best phone I've ever owned (ehem.. perhaps because it's the first smartphone I've ever owned). I just wish it was a little better. I enjoyed the stock stuff for a while until my internal storage filled up too much, then I rooted and upgraded it to an easy to install Froyo ROM as it was my first time doing such things (as good as I am with programming PC's, I thought I would surely screw that up). It was great and had kept me happy for over a year, but I didn't realise how old Froyo was until I heard about Jellybean and 'Project Butter' and how it even outperforms old versions of Android. I've been limited in Froyo to relatively basic stuff anyway so I thought since I'd basically installed an android version only one step up from the stock Eclair, there'd be a lot of better versions out there.
This is where my nightmare begun. Since I already had xRecovery, I thought the process would be as simple as "download rom, install in xRecovery". A bit too ambitious, I ended up "soft bricking" my phone and having to fix it by going back to Eclair. Then, somehow, I could not even root the damn thing under the guidance of any tutorial. It's like it suddenly caught an immunity. After ages of meddling I managed to do so and get to the next step. Then the problem occurred that Superuser wasn't kicking in and allowing anything root access. I also had problems getting a new kernel on the phone and ended up only managing to install some random kernels I wasn't even sure supported the rom I was trying to install. I had some more problems trying to install CWM and it was around then I noticed another occurring problem. Apparently for installation of Jellybean, I needed to unlock bootloader, which apparently can't be done on devices with a certain version of motherboard. Mine is 11W41. I heard that this sometimes doesn't matter depending on the specific version, but after all the problems and reading up how hard it would be to recover from a problem if it occurred. So after a long time not finding alternate solutions, I decided to go for something lower.
Ice Cream Sandwich apparently had a similar problem, but I didn't spend long looking (by that time it was really late at night and I just wanted to at least get rid of Eclair again). Eventually I installed Gingerbread, which managed to work well... the second time I tried. The first time I mucked something up and ended up going back to Eclair yet again. Well, now I at least have the GingerXperia Revolution V3 rom installed, but I'm still wondering if this is the best I can do according to the X8. So yeah, that's the rant of my nightmarish story, but this is, ehem, a Q&A... so my question is, before I get too settled with my current phone set-up, is there any better option for my phone? Have I misunderstood some things and I actually do have a way of updating my kernel in order to install a better rom? From a rom, I obviously just want a well-packed version of android (Froyo was way to simplistic, having very few options to improve the experience), which is fast and suitable for every day use. As a bonus I would like it to be swappable so I can increase the RAM with SD memory and increase internal storage size (even with the ability to move apps to the SD, the phone fills up way too fast). I'd be very surprised if I've managed to pick the best way to upgrade my phone.
I know this heavily depends on opinion, so I just want to hear it. If there is better things I can do to it, I could do with a point in the right direction!
Click to expand...
Click to collapse
why made you think that you needed to post that bolded part?
just read....read....read...the rom threads and use the search button
CnC-ROCK said:
why made you think that you needed to post that bolded part?
just read....read....read...the rom threads and use the search button
Click to expand...
Click to collapse
Maybe I was feeling sociable and friendly and wanted to share my story? Why made you think that you needed to quote and bolden it?
And what do the threads and search functions have to do about anything? Im asking for help specific to my phone and what I've done to it, so unless you're gonna help I just dont see the logic in going into all this effort to reply to my topic. I mean really, don't bother, I'm not worth it...
@cascabel
Installed that mounts2sd but on launching it I got a message about root permissions not being granted. It's a common problem I'm noticing. Only some apps achieve root access. I think the problem might be to do with an outdated SU binary, but the topic for the ROM said not to update it after installing. I updated it beforehand but the ROM must have its own binaries or something.
Deji666 said:
Maybe I was feeling sociable and friendly and wanted to share my story? Why made you think that you needed to quote and bolden it?
And what do the threads and search functions have to do about anything? Im asking for help specific to my phone and what I've done to it, so unless you're gonna help I just dont see the logic in going into all this effort to reply to my topic. I mean really, don't bother, I'm not worth it...
@cascabel
Installed that mounts2sd but on launching it I got a message about root permissions not being granted. It's a common problem I'm noticing. Only some apps achieve root access. I think the problem might be to do with an outdated SU binary, but the topic for the ROM said not to update it after installing. I updated it beforehand but the ROM must have its own binaries or something.
Click to expand...
Click to collapse
you asked for some help...but did you search or read other people's posts before that?
that was my point...:silly:
if you're using superuser, try switching to supersu. the update the binaries. it should work then :thumbup:
btw, i'm not sure but i think swap is only for custom kernels. my bad.
cascabel said:
if you're using superuser, try switching to supersu. the update the binaries. it should work then :thumbup:
btw, i'm not sure but i think swap is only for custom kernels. my bad.
Click to expand...
Click to collapse
Yes, swap works only on custom kernel
work hard, play hard
CnC-ROCK said:
you asked for some help...but did you search or read other people's posts before that?
that was my point...:silly:
Click to expand...
Click to collapse
Yes, asking for help, not info. The help would be specific to my phone, rom, lack of bootloader unlock etc
I did manage to flash a new kernel with flashtool but only certain ones work and im not sure why.
However I installed crossbreed as suggested and it was successful, so thats nice. I'll try some more suggestions later.