Related
I now have jf adp 1.5, but I want an apps2sd firmware, but I can't decide which one is the best! probably both are the best, I know!
which are the difference between Lucid Rem and the Dude?
JF's firmware comes already supporting Apps2SD. In fact you can do it all right from the terminal on your phone. And where did you d/l from again? Because I know for a fact JF not only states this fact on his blog (the page you probably got it from) but also links to a page of concise and easy to follow instructions. Personally I think you should try all 3 (be sure to READ everything TWICE when using any firmware w/ unionfs).
Also it dosen't hurt to search as I know EVERY freaking bit of this info is w/in the first 2 pages of this forum or on JF's site....RTFM
yes I know JF is compatible to app2sd, but the process to have apps2sd is not so concise and easy: lucid Rem and the Dudes seem to be more easy!
I'm sorry if I asked: I actually red the first 3 pages, not only 2, but it is not so easy to summarize tons of information!
i went through about 8 hours worth of wiping upgrading and testing the builds.
first thing i did was wipe the ext2 partition onthe card using gparted on linux. (i actually removed the partition and repartitioned it to do so. for more stability in case of bad partitioning from before] and then i wiped the phone. before upgrading.
- original JF 1.5 stable. but apps2sd was a bit complicated.
rewipe. repartition.
- thedude's rom is stable, but i found that i could not for the life of me install games. at all. it kept coming up as con.[game].whatever and i couldn't run any of them. [tested with jewellust and tangram pro]. also, the apps2sd is in collaboration with marcusmaximus and while i love the way he did the apps2sd, there wasn't much in instructions on how to make upgrading to thedude's build + marcus' app2sd work perfectly. [i got it to work, but it was w/o it's share of problems]
another rewipe. repartition.
- using Lucidrem's modded 1.5 + apps2sd steps laid out by mailman. simple perfect. 73mb free. apps2sd and stable as hell. i would recommend this.
but most of all, just wipe the ext2 partition for stability reasons. the move from rc33 to 1.5 was not a simple upgrade with apps2sd involved.
Exegence said:
i went through about 8 hours worth of wiping upgrading and testing the builds.
first thing i did was wipe the ext2 partition onthe card using gparted on linux. (i actually removed the partition and repartitioned it to do so. for more stability in case of bad partitioning from before] and then i wiped the phone. before upgrading.
- original JF 1.5 stable. but apps2sd was a bit complicated.
rewipe. repartition.
- thedude's rom is stable, but i found that i could not for the life of me install games. at all. it kept coming up as con.[game].whatever and i couldn't run any of them. [tested with jewellust and tangram pro]. also, the apps2sd is in collaboration with marcusmaximus and while i love the way he did the apps2sd, there wasn't much in instructions on how to make upgrading to thedude's build + marcus' app2sd work perfectly. [i got it to work, but it was w/o it's share of problems]
another rewipe. repartition.
- using Lucidrem's modded 1.5 + apps2sd steps laid out by mailman. simple perfect. 73mb free. apps2sd and stable as hell. i would recommend this.
but most of all, just wipe the ext2 partition for stability reasons. the move from rc33 to 1.5 was not a simple upgrade with apps2sd involved.
Click to expand...
Click to collapse
really thanks a lot! it answers to my question!
just a dubt: my G1 is from uk, so originally it had the RC9, and after few change I came up to adp jf 1.5., the sd card (a trascendent 8gb class 6) is brand new, I just partitioned it for making ext2 partition and I didn't write anything on it. Should I wipe it as well? if yes how I should do?
if lucid rem is rteally smooth I'll go for it!
Hey there, I have the same card, if you already partitioned it but havent written anything to EXT2 you should be good. As for Lucidrem I have been using the modded JFRC33 since day one and props to all the other methods and designers of apps to sd but lucid's was the easiest for me since I dont have a home CPU. I was able to use terminal emulator to run the commands and it was extremely quick & simple. If you're unsure or not able to run adb shell on a cpu like me I would definately go with his modded version
Just to add to this mess
I am using Dude's build (mainly because I had it since .05) and once you update the script in 1.1 your games and protected apps should be fine.
MarcusMaximus states that unionfs method is much more stable an powerfull but I am yet to be convinced in that. It has a HUGE potential (move individual apps back and forth, boot up without sd, etc) and I see why everybody seems to jump on that boat but the question is... do we need it? If you're putting your apps on SD you probably don't want them back on your phone, and, honestly, why do you need to boot your phone without SD? I also think (and this only MY opinion as noone else stated this) that unionfs slows down you system slightly, I could be wrong. At this point, I find it more of the hassle to use it so I'm going back to JF firmware and doing sym-links.
Re-inforcing Exegence's statement, I've used sym-links (Lucid's way) since December with absolutely no problems (app, app-private, dalvik-cache, and caches for market, browser, maps and streetview).
I may see where unionfs goes in few months but at this I'll stick with true and tried.
Good luck to everyone
borodin1 said:
Just to add to this mess
I am using Dude's build (mainly because I had it since .05) and once you update the script in 1.1 your games and protected apps should be fine.
MarcusMaximus states that unionfs method is much more stable an powerfull but I am yet to be convinced in that. It has a HUGE potential (move individual apps back and forth, boot up without sd, etc) and I see why everybody seems to jump on that boat but the question is... do we need it? If you're putting your apps on SD you probably don't want them back on your phone, and, honestly, why do you need to boot your phone without SD? I also think (and this only MY opinion as noone else stated this) that unionfs slows down you system slightly, I could be wrong. At this point, I find it more of the hassle to use it so I'm going back to JF firmware and doing sym-links.
Re-inforcing Exegence's statement, I've used sym-links (Lucid's way) since December with absolutely no problems (app, app-private, dalvik-cache, and caches for market, browser, maps and streetview).
I may see where unionfs goes in few months but at this I'll stick with true and tried.
Good luck to everyone
Click to expand...
Click to collapse
I do agree that the dudes build is awsome but is it faster at first it was fast but now that i have almost 100 apps on my class 6 sd card I see the phone almost pausing when I oper certian apps. emample it I go to bettercut and try to change an icon and click on use icon pack if i have one or two icon packs its fine but if I have 6 or 8 it has a hard time opening the pop up window with the different icon packs... I have no tryed JF with apps to sd only without apps to sd and it was fine maybe i need to give it a shot and see which one is faster!!!!
borodin1 said:
Just to add to this mess
I am using Dude's build (mainly because I had it since .05) and once you update the script in 1.1 your games and protected apps should be fine.
MarcusMaximus states that unionfs method is much more stable an powerfull but I am yet to be convinced in that. It has a HUGE potential (move individual apps back and forth, boot up without sd, etc) and I see why everybody seems to jump on that boat but the question is... do we need it? If you're putting your apps on SD you probably don't want them back on your phone, and, honestly, why do you need to boot your phone without SD? I also think (and this only MY opinion as noone else stated this) that unionfs slows down you system slightly, I could be wrong. At this point, I find it more of the hassle to use it so I'm going back to JF firmware and doing sym-links.
Re-inforcing Exegence's statement, I've used sym-links (Lucid's way) since December with absolutely no problems (app, app-private, dalvik-cache, and caches for market, browser, maps and streetview).
I may see where unionfs goes in few months but at this I'll stick with true and tried.
Good luck to everyone
Click to expand...
Click to collapse
A slight oversimplification of my reasoning in using unionfs, so I'll try to explain my motivations here. My primary motivation was to make the process of moving apps to the sd card more stable. Unfortunately, I think many have misunderstood what I mean by that. I don't actually mean that it will have fewer problems, it pretty much has an equal amount from what I've seen.
What I mean by it is that in the case of a problem, the phone will still start. With the symlink method I was seeing constant problems of boot looping for no clear reason. It seemed to work *most* of the time but when it didn't the system crashed... hard. With unionfs it's extremely rare that I get any reports of problems causing the phone to not start, and when I do it's always a corrupted file system on the sd card. By far the most common problems have been certain specific apps not working(at this point togglesettings is the only one I know of that just straight doesn't work with this method... and it actually works, it just force closes on boot) and some apps having to be re-downloaded when the method is applied. There's no more than a handful of more serious problems(such as apps showing up perfectly in their correct locations on the filesystem but not showing up in the launcher... wtf) which I definitely couldn't say for the symlink method. Actually even problems with a corrupted file system are massively down from the symlink method now that mine won't let you move the app caches(responsible for every single freakin' report of stale nfs handles).
Aside from that was the ability to have some apps/storage on the sd card. This is primarily for stability reasons, just in case there's any apps that freak out(or go really slow) from being on the sd card, they can be moved to the internal memory without having to undo the whole process.
At any rate, I'm not mad at anyone(just in case anyone thought I'm upset about anything said about the unionfs method), just explaining my motivations behind making it a reality.
Maybe I'm missing something, but I really don't understand why there's umpteen different threads about moving apps to the SD card, why there are *paid* apps to do this, etc.
Is it really that hard to type:
cp -a /data/app /system/sd
cp -a /data/app-private /system/sd
rm -r /data/app
rm -r /data/app-private
ln -s /system/sd/app /data/app
ln -s /system/sd/app-private /data/app-private
Why do people make this complicated?
As for instability with the symlink method, I haven't experienced any, and I think it's specifically because I did NOT move the dalvik cache, and there are a number of good reasons for leaving it in place regardless of the method used.
ok, now everything is more... clear but complicate
another question (remember I'm a noob): what is the dalvik cache? why I shouldn't move it? is it huge?
anbd the last (for now ) which is the difference between unionsf and symlink methods?
iso67 said:
ok, now everything is more... clear but complicate
another question (remember I'm a noob): what is the dalvik cache? why I shouldn't move it? is it huge?
anbd the last (for now ) which is the difference between unionsf and symlink methods?
Click to expand...
Click to collapse
Dalvik is the name of the Java VM on Android. It's what's used to run all of the Java programs.
Dalvik-cache is a directory on the filesystem that stores optimized versions of the dex files that are contained within an application's apk archive (think of the dex file as the executable and the apk as a zip file that contains the dex file and other files).
The reason moving it can cause problems is that if dalvik-cache is not accessible, no Java programs (including system programs) can run.
I have tried every combo of build and SD card mods and must say.........they all work, and I think 90% of problems are user error, I know 9 out of 10 of my mistakes were.
My biggest advice, if you dont understand what is happening you will always make dumb mistakes and be "that guy". Try to understand what you are doing before you do it and it you may be able to understand how to fix your own problem.
brandenk said:
I have tried every combo of build and SD card mods and must say.........they all work, and I think 90% of problems are user error, I know 9 out of 10 of my mistakes were.
My biggest advice, if you dont understand what is happening you will always make dumb mistakes and be "that guy". Try to understand what you are doing before you do it and it you may be able to understand how to fix your own problem.
Click to expand...
Click to collapse
While I completely agree with you, I still think that this community needs to agree on whichever way is better and stick with it. This would make it better for developers and users.
I thinks that a pro (hint: MarcusMaximuss) needs to do some bench testing and see if both ways are equal in speed and reliability. If we prove that unionfs method is as fast as symlink onem and stays that way after few weeks of use we can conclude that it is ready for prime time and gear all efforts towards using only that method.
I am in the process of doing a so called "user test". Dude's 1.1a with unionfs apps2sd felt slow to me. At this point I switched to JF1.50 and did symlinks and it's blazing fast!!! Give me couple of days and I'll convert JFs build to unionfs and see if that stays that fast or slows down. I'll do the same thing on Dude's build once 1.2 comes out. But these will be just my impressions, no solid data to back them up.
As always, thank god for Nandroid and good luck to everyone.
I think MarcusMaximus does enough. He doesn't need more work, especially since he's not being paid (only donations).
I think another group interested in advancing these methods should come together and do a test that is more "third-party", so we can have clear and unbiased results.
Having said that, I feel that this method (unionfs) will continue to stabilize as he works on it. Especially since he has commissioned the guidance of the 3 top ROM devs. Very promising in its infancy and just needs to be refined.
cal3thousand said:
I think MarcusMaximus does enough. He doesn't need more work, especially since he's not being paid (only donations).
.
Click to expand...
Click to collapse
Agreed !!!
cal3thousand said:
I think MarcusMaximus does enough. He doesn't need more work, especially since he's not being paid (only donations).
I think another group interested in advancing these methods should come together and do a test that is more "third-party", so we can have clear and unbiased results.
Having said that, I feel that this method (unionfs) will continue to stabilize as he works on it. Especially since he has commissioned the guidance of the 3 top ROM devs. Very promising in its infancy and just needs to be refined.
Click to expand...
Click to collapse
Well... I haven't quite gotten Haykuro on board yet.
Hi all...
I've been getting a lot of suspicious errors recently (force closes and app shortcut names disappearing) and I'd like to go from apps2sd back to just a normal setup with my apps on the internal phone storage.
Can somebody please verify that the instructions here are up to date? I'm a little nervous about wiping my data (or bricking my phone).
http://wiki.cyanogenmod.com/index.php/Apps2SD
Also, can somebody tell me whether doing this will wipe out the (single) app I paid for from the Marketplace? If so, can I redownload it, or will I need to pay for it a second time?
I originally got apps2sd set up by using the recovery ROM prior to flashing Modaco's custom ROM v1.1.
The easiest thing to do would be to load the new RA 1.5.1 recovery image.
Then boot into it.
Go to Partiton SD
Select FAT EXT3 SWAP
and then set the partition sizes of EXT3 and SWAP to 0
Is there a reason you want to do this???
This runs a very very minimal chances of bricking your phone. The other method on that Wiki page has more potential to get you in trouble.
Did see the market place question.
There is a method laying around somewhere to copy all of your apps back to the phone instead of loosing them. Restoring a Nandroid backup would likly put them all back into the /apps/ directory sd card or not. apps2sd just changes the location of that directory really.
But the market does keep track of your google account and what apps you purchase, you wont have to re purchase (maybe on a totaly new handset).
hope my jiberish has made sense
jashdlfjasdhfjablgjkasgjlkasfhlajshf
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
mkhopper said:
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
Click to expand...
Click to collapse
The possibilities of bricking the phone are very slim, but they still exist. If a phone is truly a brick, not even RUU can help. RUU has to be able to detect the phone is there in Windows, so if its beyond that RUU is useless.
Nothing to worry about as long as follow the *usually* very well written step by steps across the interweb.
If it makes you feel any better I have only heard of one or two people to brick the Hero. Most things are recoverable.
Yeah, sorry, I didn't expect it would brick the phone so much as badly mess it up - like if it expects to run apps from the SD card and they aren't there I could see the phone being tough to use as a phone, but it wouldn't really be "bricked" in the sense of not responding to user input at all.
As far as why I want to do this, I haven't really seen a huge need for apps2sd yet, and when I was recently helping an app developer to debug their app it was just one more weird variable that seemed like a possible source of problems. I'm also hoping to start developing apps myself soon, so having a more vanilla phone seems like a good idea. (I also was influenced by the Fresh ROM apps2sd rant, to be honest.)
Anyhow, thanks for your replies. I'll probably repartition the card from RUU and then restore from Nandroid at that point. Will a repartition wipe the card filesystems out, or is the partitioner smart enough to preserve the existing data?
What I did is RUUed back to 1.2, OTA updated to 1.6
Flashed to the 1.5.1 image
(At this point I went to mess with the partitions and there was no ext)
Flashed to Fresh 1.0
Hi all,
I've been lurking on these boards for sometime, taking in lots and lots of info. I have to say first of all that this place is great. Thanks to all the devs and hard working individuals who make our devices unique (esp. the HD2)
To get to the point, I have a TMOUS HD2 and had xbmod's WP7 and android on sd dual booting. all was running smooth (after A LOT of mistakes) and I vowed never to touch it again...well that didn't happen because I wanted to upgrade to xbmod's NoDo update. I read another thread on here that said you can backup partitions from the SD card to another hard drive, then copy them back to restore everything, but that did not work for me at all.
So the question is, is there a way to update between similar builds (in my case, xbmod 1.04 to 1.10) without losing data/apps/etc. I know that since it's on NAND it'll be tougher than SD Android but I figured I would ask. While we're on the subject...is anyone trying to develop running WP7 on SD? That'd be sweet. Thanks!
I would love to just update my rom too but I guess that is not possible for our HD2 as of yet or else everybody would be doing it. As from what I understand is that all your apps that you have downloaded from the market gets repopulated. Apps that were sideloaded are lost, but I believe if you search you can find that one person who made an app to automatically re-install all your apps once flashed to a new rom. As far as settings and other stuff you would have to redo them.
soapbox23 said:
Hi all,
I've been lurking on these boards for sometime, taking in lots and lots of info. I have to say first of all that this place is great. Thanks to all the devs and hard working individuals who make our devices unique (esp. the HD2)
To get to the point, I have a TMOUS HD2 and had xbmod's WP7 and android on sd dual booting. all was running smooth (after A LOT of mistakes) and I vowed never to touch it again...well that didn't happen because I wanted to upgrade to xbmod's NoDo update. I read another thread on here that said you can backup partitions from the SD card to another hard drive, then copy them back to restore everything, but that did not work for me at all.
So the question is, is there a way to update between similar builds (in my case, xbmod 1.04 to 1.10) without losing data/apps/etc. I know that since it's on NAND it'll be tougher than SD Android but I figured I would ask. While we're on the subject...is anyone trying to develop running WP7 on SD? That'd be sweet. Thanks!
Click to expand...
Click to collapse
there is a way of backing up the data for the appps but not the apps them selves, if you wait for a week there should be a backup utility that may work
im not talking full rom backups, i know they are there, im talking app and data backup....maybe will know soon
Any movement on this data backup scheme?
ojaidave said:
Any movement on this data backup scheme?
Click to expand...
Click to collapse
aye its working fine, its in beta just now, i dont think him made a public release yet
it backs up all the DATA from each app, it doesnt however backup the apps them selves, so you would do the following
run the backup
flash your device
install all the apps you want
restore the backup
it does not backup SMS
i made a thread about doing this manually which works as well, but the app makes it a lot easier.
http://forum.xda-developers.com/showthread.php?t=1082343
Haven't heard anything...still waiting also want my Mango already!
Newbie here - used search feature, searched across forums. Did not find my problem addressed.
Putting CM7 on wife's NC 1.2.0. Followed huskermania's steps exactly. Everything installed fine until I got to the part where I selected format data. Then I received message, "error formatting data!" Everything stops right there and I have to power the unit down.
Re-downloaded the file twice - went through the complete process two times across several different times so as to avoid frustration causing more trouble! Using a Sandisk 8g class 4 card.
Using 7zip, cm7.0.3, and win32diskimager, and google add-ons, downloaded as directed by the husker dude.
In one section of his video, Huskermania moves files to the mSD - his files are shown as yellow folders. Mine show up as a small stack of books. When I look at the properties of my files, they are winrar zip archive files.
Please help! I'm so close!!
Thank you,
Jim
I believe your issue has been addressed more than one, maybe not exactly the same but pretty close.
Anyway, your NC is v1.2.0, often called "blue dot" which B&N decided to change the partition mapping, used to be 1GB /data & 5GB /media in v1.1, now be 5GB /data & 1GB /media in v1.2.0.
If you don't have a bootable uSD card with CwM Recovery 3.2.x.x or above, it will give you that error "cannot format /data". However, in my specific case, I did have the issue but my NC actually continued to next step, not hung and no need to force reboot.
I suggest you get the newer CwM (v 3.2.0.1) and give it a try again.
Votinh,
Thank you for your reply. As I learn, I am finding that sometimes I don't understand what to ask to find the solution!
I will try this today and report back.
Thank you again,
Jim
Wait!
I checked the version of the file I had used to install cwr and it is 3.2.0.1 - the same file that I was encouraged to try. To be more precise, it is "recovery-clockwork-3.2.0.1-bravo.
So, I'm still stuck.
HELP!
Thank you,
Jim
Can't offer anymore help, m8 but I don't think you should be panic.
If I were you, I would try to re-partition/re-format to 1GB /data 5GB /media, then using CwMR v3.0.2.8 and try again.
Great! Now, can you tell me how to do that?
Thank you,
Jim
I would suggest reading This first. Important info if you are going to muck around in the internal memory partitions.
Then I would go Here and see if this will help.
If not, This, This, or This might be your next best steps as far as reading and/or trying.
Also, This Sticky could shortcut you to the solution you need.
All these links go to XDA threads here in the Nook Color forums. They aren't all the recovery threads, but most of the more recent ones that could help you.
I haven't had to deal with what you're trying to handle, but this should be a great start/solution to solving your problem.
It's gonna take some reading and absorbing to comprehend what you're trying to accomplish, given the level familiarity you seem to have with your device and it's internal file structure.
(I mean no slight by this, the fact that you are here trying to learn and figure out your issue says much - welcome to the community btw )
Tcandroid,
Thank you for your input. I solved the problem by following votinh directions about partitioning. I'm finally up and running cm7!
Two concerns remain:
1. Do I need to worry about OTH updates from barnes and noble messing up my efforts? My hunch is no, just want to make sure. If so, how do I turn that off?
2. Can I over clock to 950 with what has already been installed, or do I need to download and install something else?
Thank you all so much!
Jim
Jim1970 said:
I'm finally up and running cm7!
Click to expand...
Click to collapse
This put a smile on my face, i'm glad to hear you got your issue resolved.
Nothing worse then having a wonderful piece of technology right in your hands that you can't use.
I have no doubt you are going to have a blast with it.
Cruise through the 'themes and apps' subforum here in Nook Color Forums, and you'll find some gems that are out there in the market.
I am not sure about the answers to either of your questions, but I do know that:
Some people have had to do some funky things to block B&N updates, and there have been conflicting answers on this. Again, only have seen in passing - so not sure what the whole story is here.
B&N doesn't push updates that often, so it's likely you have some time to figure this out.
I see people mentioning overclocking to 1200 a lot, so 950 shouldn't put too much stress on your machine. Depending on what version of CM7 you are running, you shouldn't use an external app to overclock. I've been using mine at the standard 800 and can play games like Samurai 2 (with chainfire installed) and it's no problem for the machine.
If your CM7 version provides you overclock settings, use those and not an outside app like SetCPU.
Some random info gleaned from browsing through this forum. Not too specific in addressing your query, yet maybe helpful in your continuing Android education.
Jim1970 said:
Tcandroid,
Thank you for your input. I solved the problem by following votinh directions about partitioning. I'm finally up and running cm7!
Two concerns remain:
1. Do I need to worry about OTH updates from barnes and noble messing up my efforts? My hunch is no, just want to make sure. If so, how do I turn that off?
2. Can I over clock to 950 with what has already been installed, or do I need to download and install something else?
Thank you all so much!
Jim
Click to expand...
Click to collapse
I help many people in many threads and tend not to remember the OP's original issue, so I have to re-read again
Firstly, congrats to you, do enjoy the NC running CM7. I bet by now, you are not a noob or newbie anymore, experience learnt.
Secondly,
1. since the NC is running CM7 ROM now, you don't have to worry about anything from B&N, even their new release probably won't be as good as the CM7.
2. by default, CM7 comes with kernel that can be overclocked to 925MHz (at least true on the v123 nightly build, not sure the latest) and again, it runs at 800MHz by default. You can set it under ??? (not on top of my head now and I don't have the NC in front of me, will update later).
If you want to run faster than 925MHz, you must install Dalingrin latest work - build on 06302011. Be sure download the "emmc" version since you run the CM7 off the internal memory.
Hi everyone,
I'm new to this and sorry if some of my questions are redundant, but can anyone tell me their experiences with hacking the Nook Color? I'm still deciding on getting it and I want to put Cyanogenmod 7(Gingerbread) in it( if I buy one), but I'm not 100 percent sure. Can someone tell me if it's easy, hard, any complications, etc? Also any links or information on how to dual boot it( is that the one where it doesn't void your warranty?) would be greatly appreciated.
Sorry for all the noobness.
Welcome! There are a lot of threads here and in the Android Development sub-forum on getting started along with answers to most of your questions. See this post of mine for links on getting CM7 installed:
http://forum.xda-developers.com/showthread.php?p=16779145#post16779145
Frankly, everyone here will say that the nook is pretty awesome, especially with CM7. It's quite easy. The first time you install it might take a while (under 1 hour easy), but after a while it could really be done in a few minutes. At this point you just need to copy files mostly. Technically, I think running CM7 could void your warranty, but that said, the Nook is nearly unbrickable. You can pretty much always restore to stock if need be. The safest way to get started is to follow the SD card method from the link above.
Good luck!
It's just like learn how to swim or learn how to ride a bike.
No one ever able to do and do good first time, it takes time, always.
Someone picks things up fairly quick, some others learn at slower pace but they all get better at some points.
The only requirements are able to read and understand English and able to follow the instruction then you're off to go .......... and go far.
Lastly, if I can do it, you can do it.
Look into starting from the SDCard install options, before overwriting internal memory. If something goes wrong, you simply power off, remove the SDCard, and power up again, and you have your stock Nook Color working perfectly.
In my sig, click the link to "SD Install" for the best way to prep the MicroSD card for whatever ROM you want.
I highly recommend CM7, it's simply the best thing going for it. Again, installing to the MicroSD card is a painless way to test it out, links in verygreen's thread.
Make sure you have a SanDisk card, links in my sig to find out why if you're curious.
To this day, I still have my stock Nook Color B&N software updated and running on the internal memory - but for the life of me I can't figure out why I haven't taken the step to move CM7 to internal at this point. It's that good.
Point being, with a SanDisk MicroSD card, and CM7 installed to it, you really unlock the powerful user experience this device is capable of. Best part is, it's not a permanent thing. You simply power off, remove the MicroSD card, then power back up and you are back to stock.
Easy, painless, and tons of fun.
Thank You so much everyone for the responses. Sorry if I took too long to reply. I'm going to read over the directions right now Oh and do anyone have the list of some of the words? I'm still new to this and I don't know what "partition" or "kernel" means.
partition = dedicated space for specific usage.
kernel = sets of drivers, it is a brain of the ROM
i was a new nook owner and new to rooting as well. i had no trouble with following instructions and have been very happy with the outcome. it also helps to read a lot of other posts to see what issues may arise and how to fix things. as long as you can follow instructions properly its a breeze
Thank You all so much. I got one more question, I've been reading somewhere online that it's possible that you can go back to the original version of the nook without having to remove the SD card, and I just want to confirm if this is possible? If it's can you give me a link? Thank You sorry for so much question
Marid said:
Thank You all so much. I got one more question, I've been reading somewhere online that it's possible that you can go back to the original version of the nook without having to remove the SD card, and I just want to confirm if this is possible? If it's can you give me a link? Thank You sorry for so much question
Click to expand...
Click to collapse
On the newer nightlies, you can press the nook 'n' button while the first green cyanogenmod logo is showing and it will take you to a boot menu. You can then select to boot from emmc (internal) or the sd card, and also choose normal or recovery mode.
Sorry about this but 1 more small question, will bn update( i think ota) affect the rooted nook? If so, can you tell me how to fix it?