Database Users

Moving from Cyanogen to Super D

Hi Peeps,
I have searched in vain for a guide to changing from cm 4.2.15.1 to super d stable, but I cant seem to find one.
can someone advise me what to do so I dont brick my phone, and is it really worth moving to super d I hear its faster.
I am running cyanogen 4.2.15.1 H&E red I have the ra-dream 1.5.2 recovery, I have ext2 partition on sd card and I have a PVT board
Also I am worried about the ext2 partition because I have heard you have to remove it first and there is a certain way to do it??
Thanks in Advance

I was able to flash SuperD over Cyanogen without wiping or repartitioning. This is with an sdcard partitioned the usual way, fat32 and ext2.
The only issue I ran into was the battery meter - had to remove /data/system/batterystats.bin. Not sure of the exact procedure, so I did that from the recovery console and then booted up with a full charge.
Works great and really is a lot faster.

I would always wipe when moving from one rom to another. You never know what's could be hanging around.
I go thru this same process every time and never had problems:
1. Nandroid or Bart backup
2. Copy backup from SDcard to PC just in case SD card gets corrupted somehow
3. Wipe
4. Install new rom
5. Fix apk mismatch
6. Reboot
7. Check to see if Gapps are working, namely market, talk, sync, and of course google voice

nmw407 said:
I would always wipe when moving from one rom to another. You never know what's could be hanging around.
I go thru this same process every time and never had problems:
1. Nandroid or Bart backup
2. Copy backup from SDcard to PC just in case SD card gets corrupted somehow
3. Wipe
4. Install new rom
5. Fix apk mismatch
6. Reboot
7. Check to see if Gapps are working, namely market, talk, sync, and of course google voice
Click to expand...
Click to collapse
5. When you say "fix apk mismatch"....what do you mean?
7. I did the same thing (went from Cyanogen to SuperD) and I can boot into SuperD fine, but it won't connect to T-mobile's network and I am missing the Market. Any help?

shuboy00 said:
5. When you say "fix apk mismatch"....what do you mean?
Click to expand...
Click to collapse
It's an option in Amon_RA's recovery
shuboy00 said:
7. I did the same thing (went from Cyanogen to SuperD) and I can boot into SuperD fine, but it won't connect to T-mobile's network and I am missing the Market. Any help?
Click to expand...
Click to collapse
Wipe, Flash the DRC83_Base_Defrangled, the flash SuperD. Since both are legal, they need to pull the google apps from the base. And you would probably be fine without a wipe from SuperD to CM since they are similar donut builds. Wipes are recommended if you go from eclair to donut (and donut to eclair, elcair to sense, sense to dount.....). Cyanogen fixed it so you don't need to wipe as in the olden days...

mejorguille said:
It's an option in Amon_RA's recovery
Wipe, Flash the DRC83_Base_Defrangled, the flash SuperD. Since both are legal, they need to pull the google apps from the base. And you would probably be fine without a wipe from SuperD to CM since they are similar donut builds. Wipes are recommended if you go from eclair to donut (and donut to eclair, elcair to sense, sense to dount.....). Cyanogen fixed it so you don't need to wipe as in the olden days...
Click to expand...
Click to collapse
I see. So I am already running the DRC83_Base_Defrangled. Here is what I am doing:
I am currently running Cyanogen 4.1.99. My build number is DRC83. But my model number says "Android Dev Phone 1" <-- could that be why I don't have the Market in my roms?
So anyways this is what I do from Cyanogen 4.1.99: I backup, wipe, flash the DRC83, flash SuperD, then flash the 26I radio. Like I mentioned, rom boots up fine, just no market and no network access. Am I doing something wrong?

Absolutely no reason to flash the radio. The only thing that I can think of is that you have a bad download? Download this. Go to recovery, backup, flash the base, flash the rom. That should be all you have to do. Also, try CM 4.2.15.1 if SuperD isn't working for you. You are using a version of cyanogen about 4 months old and there have been 20 something releases since.

mejorguille said:
You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
Click to expand...
Click to collapse
i believe he said that he is running latest cyan rom. try backing up your fat32 partition and reformat, that should do the trick

b0ricuaguerrero said:
i believe he said that he is running latest cyan rom. try backing up your fat32 partition and reformat, that should do the trick
Click to expand...
Click to collapse
I was referring to the poster above my post

mejorguille said:
Absolutely no reason to flash the radio. The only thing that I can think of is that you have a bad download? Download <removed>. Go to recovery, backup, flash the base, flash the rom. That should be all you have to do. Also, try CM 4.2.15.1 if SuperD isn't working for you. You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
Click to expand...
Click to collapse
K. Did what you said. Downloaded the base you provided. Flashed. Then flashed the SuperD rom. Booted up. First I see is "!Sorry - The process com.google.process.gapps has stopped unexpectedly. Please try again." Still no network and still no Market. Urgh. Frustrating!!
Also, I tried CM 4.2.15.1 after the SuperD didn't work and it hung on the G1 screen. IDK why 4.1.99 works but not 4.2.15.1.

i guess it didnt hung, you just have to wait a bit longer.

[Q] MT4G iced glacier; clockwork mod recovery problem

hey guys im having a big and really annoying problem i cant fix hopin in can get some help...
i have the iced glacier 1.1.6 with clockwork 3.0.0.5(rom managerv3.0.1.0). i want to make a backup nanDroid.. so i do and it completes and everythings fine... until i to the restoring part. after it "successfully" restores(yes, i did wipe cache, wipe dalvik, and even wiped eveything in everyorder possible. i restart my phone and it freezes on the mytouch 4g bootup logo. everytime. no matter what. it does let me reinstall the fresh ice glacier rom...
note: when i wipe the dalvik, its almost instantaneous wipe, like it doesnt do it?
there is an error about e:/ not mounted (sd-ext) or something close to that. but still says it worked.
things ive tried...
renaming the file.
moved the file.
reformatted SD.
wipe data...etc twice in a row to make sure it wiped.
any ideas?

You have to revert back to older Recovery 2.5.1.2 or you can install the new 3.0.0.6 as normal CWM won't able to handle it. This same issue has been covered many times. Read the quote below to better understand if you still have problem well then post back ill help.
jggimi said:
you are using the wrong version of Recovery to install the new kernel. I'm guessing #2, because it's very common for people to assume a higher number is better, and use CWM Recovery 3.0.0.5 with Froyo-based ROMs and hose things up really well.
Restoration options, if you are using CWM 3.0.0.5:
a) Restore from the Nandroid backup you made before overlaying your kernel. Oh, yeah, you can't, you didn't make one, otherwise you'd have already done that and wouldn't have posted....
b) Flash the appropriate CWM Recovery (2.5.1.2 for Froyo-based ROMs) using adb from your PC. Reboot into it, find the kernel you wanted to use, and reinstall it.
c) Install a Gingerbread-based ROM, such as CM7.
Pick a,b, or c. If you have any specific questions, please ask.
Click to expand...
Click to collapse

i did the 2.5.1.2 first but it didnt work so i thought id try the newest one...but 3.0.0.6? where do i get 3.0.0.6? its not in rom manager. ( i really hate rom manager it never works for me...) and ive never done adb? or anything on my pc. everything ive done is on my phone...

drpepper4lf said:
i did the 2.5.1.2 first but it didnt work so i thought id try the newest one...but 3.0.0.6? where do i get 3.0.0.6? its not in rom manager. ( i really hate rom manager it never works for me...) and ive never done adb? or anything on my pc. everything ive done is on my phone...
Click to expand...
Click to collapse
Sorry I was asleep but if you still looking for the solution.
http://forum.xda-developers.com/showthread.php?t=952433
Go to option's thread and follow his instructions on howto install 3.0.0.6 as it works also.

[ROM] Bonsai User Discussion

This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor

Yes this try to keep this thread open.
Sent From My Evo Killer!

So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App

I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk

Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?

abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far

I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0

bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?

forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.

I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force

forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.

olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.

Duplicate... Sorry

forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.

Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted

Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3

[Q] Eyeballer mostly working, Gapps not working

I installed CM9 Eyeballer the other day on my NC. It pretty much works, but if I go into the web browser or any other factory-installed app, hitting the "N" button takes me back to the factory-installed home screen, and I can't find any way to get back to the Android home screen, short of rebooting the device. Is this normal?
Also, I flashed Gapps using gapps-20120429-ics-signed.zip, and the only Google App that appears is Play Store -- I was able to sign in, but the next screen gave me a "Server Error," and that's all it's done since. I verified the md5sum, and also tried again to install it. No change. Is there some version conflict, or something like that?
Edit: did not install CM9, after all. I now have.

What is the 'factory installed home screen'? You mean stock? That is not possible if you installed CM9 over the top of stock on emmc. Can you explain a little more how you installed it and what you mean.

Well...
I followed the directions as closely as I could: create a recovery chip, copy over the zip file (manualnooter-5.08.20-apps2sd.zip), reboot, install from zip file, install Manual Nooter, flash update-Froyo1.2-dalingrin-OC-emmc-090111.zip, install Gapps, reboot again. As far as I could tell, my results were consistent with the directions, up until the symptoms I described. For example, the splash (smash) screen is right, and the rainbow-y thing, and so on.
This partial success is even more frustrating than a total failure.

estebandido said:
I followed the directions as closely as I could: create a recovery chip, copy over the zip file (manualnooter-5.08.20-apps2sd.zip), reboot, install from zip file, install Manual Nooter, flash update-Froyo1.2-dalingrin-OC-emmc-090111.zip, install Gapps, reboot again. As far as I could tell, my results were consistent with the directions, up until the symptoms I described. For example, the splash (smash) screen is right, and the rainbow-y thing, and so on.
This partial success is even more frustrating than a total failure.
Click to expand...
Click to collapse
Your original post said you installed CM9. You did not. You just rooted your stock rom. You might want to edit the title of the post to 'Manual Nooter installed properly, Gapps not working. Then take that CM9 Eyeballer statement out of the text in the first post and you might get some proper responses from folks.

Sure enough.
leapinlar said:
Your original post said you installed CM9. You did not. You just rooted your stock rom.
Click to expand...
Click to collapse
Ah... I was under the impression that Eyeballer was a version name of CM9. None of the sets of instructions I read made it clear to me that wasn't the case.
I ended up doing a factory reset, then reinstalling everything. The picture is far rosier now -- it finally looks the way I pictured!
Thanks!

estebandido said:
Ah... I was under the impression that Eyeballer was a version name of CM9.
Click to expand...
Click to collapse
Eyeballer does build a version of CM9. But that has nothing to do with what you did. You ran Manual Nooter, which is a tool to root your stock installation. CM9 is a completely different version of Android than stock is. And when you install CM9, your stock is completely removed and replaced by CM9.
You do not have CM9 installed, you have just rooted your stock rom.
Anyway, I'm glad you got it working.
Edit: I see you modified your original post to say you did later install CM9.

[ROM][NC] Unofficial CM9 Nightly builds - with/without OpenGL
I don't have enough posts in XDA to post in the (goo dot gl/vPJcM) actual ROM thread so I'm hoping someone will see it here.
After installing the CM7 ROM a long time ago. they Nook wasn't able to boot into CWM. I can only access the recovery using a bootable SD card. That may or may not matter.
Yesterday I installed both the 3 SEP OpenGL and 4 SEP versions of Eyeballers CM9 ROM along with GAPPS. In both versions I cannot get bast the Setup Wizard since it "unfortunately Closed" every time I "touch the Android".
I did install the ROM w/o GAPPS as a temporary fix but will need to eventually access the Play Store.
I did notice that CWM still wont boot into recovery and the Cyanoboot won't either. Cyanoboot takes me to what appears to be a stock Nook screen claiming that an install has failed and that I should power on/off or contact customer service.
Does anybody have any suggestions?
Thanks!
JC

jerrycrabb said:
I did notice that CWM still wont boot into recovery and the Cyanoboot won't either. Cyanoboot takes me to what appears to be a stock Nook screen claiming that an install has failed and that I should power on/off or contact customer service.
Click to expand...
Click to collapse
You do not have CWM installed on internal memory (emmc). That message you are getting means you still have the stock recovery there. You need to flash a CWM to emmc using your bootable CWM card. Look in my tips thread linked in my signature. Look at item A8 and the subheading 'to fix a corrupted or missing recovery on emmc'.
I don't know how to solve your other problem with gapps, other than to do a factory reset with CWM.

From what I can tell, Eyeballer is mostly drinking.

leapinlar said:
You do not have CWM installed on internal memory (emmc). That message you are getting means you still have the stock recovery there. You need to flash a CWM to emmc using your bootable CWM card. Look in my tips thread linked in my signature. Look at item A8 and the subheading 'to fix a corrupted or missing recovery on emmc'.
I don't know how to solve your other problem with gapps, other than to do a factory reset with CWM.
Click to expand...
Click to collapse
Thank you very much for the response, I will try this as soon as I get some time (I have a selfish new baby) and get back.

leapinlar said:
You do not have CWM installed on internal memory (emmc). That message you are getting means you still have the stock recovery there. You need to flash a CWM to emmc using your bootable CWM card. Look in my tips thread linked in my signature. Look at item A8 and the subheading 'to fix a corrupted or missing recovery on emmc'.
I don't know how to solve your other problem with gapps, other than to do a factory reset with CWM.
Click to expand...
Click to collapse
Success! errr..sort of.
Prior to flashing gapps I was able to reboot into CWM. Thank you so much for your help!
Still having the same issue with setup manager after factory reset and wipe of all cache.
If anyone has a work around or another suggestions for CM9 on the NC I'd much appreciate it.
Thanks again.

[Q] HELP- CM nightly 10.1.2 20130813 nook color wont boot properly!!!!!

ive done this a few times and never had a problem when putting CM on my nook color. but when i decided to flash a newer version. CM 10.1.2 20130813 NIGHTLY it was workjing fine for a few hours while i redownload all the apps i had previously then it just shut off and booted up to nook not CM. i tried restarting, reseting through menu and the "8 boot method" and then reflashing CM 10.1.2 encore stable and it still keeps booting to nook not CM. ive tried looking everywhere for a fix and no1 seems to have ever had this problem. its like its stuck in nook mode (stock 1.4.3). any ideas??????? PLLZZZZZZ HEEEEEELLLLLPPPPP. thx:crying:

newbtrigger69 said:
ive done this a few times and never had a problem when putting CM on my nook color. but when i decided to flash a newer version. CM 10.1.2 20130813 NIGHTLY it was workjing fine for a few hours while i redownload all the apps i had previously then it just shut off and booted up to nook not CM. i tried restarting, reseting through menu and the "8 boot method" and then reflashing CM 10.1.2 encore stable and it still keeps booting to nook not CM. ive tried looking everywhere for a fix and no1 seems to have ever had this problem. its like its stuck in nook mode (stock 1.4.3). any ideas??????? PLLZZZZZZ HEEEEEELLLLLPPPPP. thx:crying:
Click to expand...
Click to collapse
Before flashing, did you do a full wipe?
CWM > Wipe data & factory reset, wipe cache, wipe dalvik cache, and wipe your system partition?
I have a Nook Color as well, but I'm running CM7. I read somewhere that your CWM must be version 6.xxx to properly flash CM10 based roms. I believe that is your problem. Btw, CM7 has better performance on this old device.

flashing
i actually never flashed clockwork. all i did was use winimage to partition the card, then just dragged and dropped gapps and cm 10.1.2 20130815 nightly. then it broke after installing a few apps. ive been looking for CWM to wipe everything. from wut i understand CWM wipes it COMPLETELY unlike the 2 stock methods i used before. its like it just wont boot from the sd card anymore. it installs the CM but after its done it just boots up to nook. if you or anyone can tell me where to find CWM it would be much appreciated. i dont understand their site layout and the youtube directions dont have working links for CWM. any ideas? and thx so much for the response. i know from reading now that cm7 was wut i shud have installed instead of the newer extremely unstable cm9 and cm 10.2.
ALSO, im reading about CWM software is related to SD card size? i only have a 32gb sd which is not mentioned in any of the tutorials on how to use CWM. does it rly matter?

newbtrigger69 said:
i actually never flashed clockwork. all i did was use winimage to partition the card, then just dragged and dropped gapps and cm 10.1.2 20130815 nightly. then it broke after installing a few apps. ive been looking for CWM to wipe everything. from wut i understand CWM wipes it COMPLETELY unlike the 2 stock methods i used before. its like it just wont boot from the sd card anymore. it installs the CM but after its done it just boots up to nook. if you or anyone can tell me where to find CWM it would be much appreciated. i dont understand their site layout and the youtube directions dont have working links for CWM. any ideas? and thx so much for the response. i know from reading now that cm7 was wut i shud have installed instead of the newer extremely unstable cm9 and cm 10.2.
ALSO, im reading about CWM software is related to SD card size? i only have a 32gb sd which is not mentioned in any of the tutorials on how to use CWM. does it rly matter?
Click to expand...
Click to collapse
Sure thing. Here are the instructions for flashing CWM to your internal flash using a microSD card. You'll need a microSD card reader for this. Look on Amazon for the IOGear MicroSD card reader, I bought it recently for $6 in total.
Read this thread thoroughly, it is simple enough. http://forum.xda-developers.com/showthread.php?p=12797652
Also, I would suggest you install CM7 MiRaGe rom instead of stock CM7. It performs really well, and I have it overclocked to 1.2GHz stable. Here is the MiRaGe thread. http://forum.xda-developers.com/showthread.php?t=1344873
If ya need more help, leave a reply.

sagirfahmid3 said:
Sure thing. Here are the instructions for flashing CWM to your internal flash using a microSD card. You'll need a microSD card reader for this. Look on Amazon for the IOGear MicroSD card reader, I bought it recently for $6 in total.
Read this thread thoroughly, it is simple enough. http://forum.xda-developers.com/showthread.php?p=12797652
Also, I would suggest you install CM7 MiRaGe rom instead of stock CM7. It performs really well, and I have it overclocked to 1.2GHz stable. Here is the MiRaGe thread. http://forum.xda-developers.com/showthread.php?t=1344873
If ya need more help, leave a reply.
Click to expand...
Click to collapse
hmmmmmm well i did wut u said everything works fine but it wont connect via wifi....btw thx soo much for getting me back to android.

newbtrigger69 said:
hmmmmmm well i did wut u said everything works fine but it wont connect via wifi....btw thx soo much for getting me back to android.
Click to expand...
Click to collapse
Nah, it works man. There's just a little bug you need to take care of. Go to the Mirage thread again, on the bottom of the first post, you'll see it says "wifi disconnecting? Read <link>". It's an easy fix. I had it too.