Related
My head is aching with the sheer amount of information it is trying to process. I got a Nook Color about a month ago but have been putting off using it because I am still trying to figure out how to do what I want to do.
I've been going over the threads on the dev forum and after reading a lot of the threads, I still can't find exactly what I need (or maybe I've found it but I just haven't realized it yet).
My Nook Color is running latest official update from B&N (meaning 2.2 and B&N apps).
Anyway here's what I need:
1. I need to be able to dual boot into either HC or a rooted gingerbread-based version of android (is this the clockwork 7 thing?) solely from an SD card
2. Should not do anything to the Nooks internal memory (meaning: won't void warranty)
3. The dual boot manager, HC and and gingerbread-based version of android should all run on sd card. nothing will be placed/done on the nook (is this it? i'm so confused i'm not even sure anymore --- http://forum.xda-developers.com/showthread.php?t=1045018)
4. The dual boot manager will still have the ability to install other custom roms on to the sd card when i put the zip file of the image on to the sd card (something like this: http://forum.xda-developers.com/showthread.php?t=1000957)
5. Should have the overclock thingamajig
Anyway, are there any solutions to this? the "Dualboot Phiremod / Honeycomb Image for SDcard" seems the closest so far but I can't figure out if it installs a rom manager into the SD card with which I can install newer versions of the overclock kernel or newer versions of the custom ROMS based on HC preview or newer version of the CM7 nightly image. gaaaah.
Please help >_<. I promise I'm not stupid. This is just like information overload and I seriously am having a real headache (not just figuratively) right now.
Follow the thread below. From it, you can install plain CM7 (the best known gingerbread rom) strictly onto your SD card. If you have multiple cards, you can try out the different flavors of CM7:
CM7 Stable (latest is 7.0.3); OR
CM7 Nightly (latest is 76); OR
Beta CM7 .32 kernel, though this one is still has some bugs.
Phiremod is a themed CM7 which I haven't tried, while the above are more plain vanilla android. Also use a Sandisk card if you have one as they seem to have better overall speed regardless of Class, at least 2gb size or bigger.
http://forum.xda-developers.com/showthread.php?t=1000957
Hi LBN1, thanks for the quick reply.
Does this work process allow me to install HoneyComb as well as a separate boot option?
I just realized that I'm actually looking for an SD dual boot of HC and CM7 w/ OC. Does this exist? >.<
Oh, this process is not for a dual booting SD card. It allows a rom on a SD card, and then take out the SD card and you can boot to stock B&N software, so it is a quasi dual boot so to speak. There are some actual dual boot options out there but I don't have any experience with any of them...
Same thing with Honeycomb roms, never tried any of them since from what I read they are still in early, beta stages meaning they really don't work as well as CM7.
LBN1 said:
Oh, this process is not for a dual booting SD card. It allows a rom on a SD card, and then take out the SD card and you can boot to stock B&N software, so it is a quasi dual boot so to speak. There are some actual dual boot options out there but I don't have any experience with any of them...
Same thing with Honeycomb roms, never tried any of them since from what I read they are still in early, beta stages meaning they really don't work as well as CM7.
Click to expand...
Click to collapse
Hehe... yeah I kinda figured that out What I had in mind was something along the lines of dual booting HC/CM7 via SD card and removing the SD card if I wanted to boot to the stock 1.2 (so it's a quasi triple boot) >_<
But thanks for your help!
I think the easiest thing you can do right now is to try the Phiremod/Honeycomb Dual boot sd image which I see you already found out. It wont change or touch your internal system so you are safe. Also its already prepared for you so you just need to burn the img into the sd.
If inserted, the sd image will boot to either Phiremod (which is really a themed version of CM7 7.02 - with the update provided in the same thread or to Honeycomb). I use it and works quite well!!!! It is fast also (provided you use the recommended Sandisk class 4 sd card) as it is overclocked from the sd which you also want.
When I want to use stock BN I just boot without the sd and thats it! I also rooted the internal BN as well to add overclock to the stock BN 2.2 and it is quite snappy when OC to 1.1 mhz.
Hi Garoto! that's good to hear! can you point me to the thread for rooting the internal BN and adding overclock to the stock 2.2? i want to try that as well
pryonix said:
Hi Garoto! that's good to hear! can you point me to the thread for rooting the internal BN and adding overclock to the stock 2.2? i want to try that as well
Click to expand...
Click to collapse
Sure no problem:
1. To root the 1.2 version Nook just follow the steps in this thread, it is not as complicated as it sounds:
http://forum.xda-developers.com/showthread.php?t=1054027
2. To install the OC Kernel I used this thread. Pretty simple process. After you root , go to the market and install ROM manager, then do flash clockwork and then reboot to recovery, then do update from zip in sd card and flash the OC Kernel. I used the 1,1 mhz as it is stable and really speed things up:
http://forum.xda-developers.com/showthread.php?t=1064095
pryonix said:
Hi Garoto! that's good to hear! can you point me to the thread for rooting the internal BN and adding overclock to the stock 2.2? i want to try that as well
Click to expand...
Click to collapse
Keep in mind, overclocking definitely technically voids the warranty (as does rooting). Since you mentioned it. Just as bad as installing stuff on the internal EMMC.
greenmky said:
Keep in mind, overclocking definitely technically voids the warranty (as does rooting). Since you mentioned it. Just as bad as installing stuff on the internal EMMC.
Click to expand...
Click to collapse
Haha yup... just wanted to know as a "just in case I feel brave enough to void my warranty" haha!
Gr, I have at this for hours.
I wanted to get the ICS sneakpeek running up on my nook. I had CM7 running on it. Here's exactly what I did.
1. I had CM7 on the SD card, using verygreens image. I've been using it for months, no problem, but decided I wanted ICS on it. So I backed up my apps and copied important stuff to my laptop.
2. Plugged the SD card into my laptop, and ran win32diskimager. I was planning on picking "Read" instead of "write", but it wanted me to write it to an image file.. Stupidly, I wrote it to verygreen's "generic_sdcard" image file. It probably won't work to reflash, but who care, I can just start over.
3. I put the SD card into the nook, to see what happened. It booted up, the linux penguin showed, couldn't find install image (obviously), blah blah blah...
4. Popped the SD card into the computer, and dropped sneakpeek fullofbugs1 on there. Booted up, fine, got into ICS.
5. Shutdown, SD card back in the computer, dropped fullofbugs2 on there. "Not enough space on the SD card".
6. Started Easus partition manager, with the intentions of resizing the BOOT partition. However, this is where the problems started. It would not let me resize it. I tried everything, and I could not, for the life of me, get it to resize. Is there something special I have to do? resize before placing CM9 on there? before ever placing it in the nook? I'm worried I'll mess it up and just have a normal nook again.
I'm no noob, I wrote this awhile ago. I'm pretty experienced in android.
Can anyone suggest anything? I'm pretty sure I probably need to resize before running the card in the nook.
TL;DR How can I expand the boot partition of my verygreen SD card? Do I have to do it before first inserting it into the nook after the image is written?
Thanks for any help!
I think you have to do it before
bcvictory said:
I think you have to do it before
Click to expand...
Click to collapse
Thanks! Got it running this morning! Its pretty sweet.
Tapatalkin it from my IHO CM7.1'd, MIUI Themed Optimus V
kcls said:
Thanks! Got it running this morning! Its pretty sweet.
Tapatalkin it from my IHO CM7.1'd, MIUI Themed Optimus V
Click to expand...
Click to collapse
I would also like to do as you have done. What size did you have to make the boot partition for ics to fit properly? This is new for me since I didn't have to resize at all for cm7. I've been using cm7 for a few months but would really like to try ics on another micro sd I got just for this. Do I follow verygreens instructions except for adding sneekpeak as the nightly?
kbuster2 said:
I would also like to do as you have done. What size did you have to make the boot partition for ics to fit properly? This is new for me since I didn't have to resize at all for cm7. I've been using cm7 for a few months but would really like to try ics on another micro sd I got just for this. Do I follow verygreens instructions except for adding sneekpeak as the nightly?
Click to expand...
Click to collapse
Make the boot partition about 200mbs, if I remember correctly the image defaults it to 117mbs. It only needs a little more space.
Also, yes you can follow verygreens instructions to make a bootable ICS micro card. I made and ran ics this way for about a week before commiting to the emmc install with nightly build 14 which is still rocking as my daily driver!
kbuster2 said:
I would also like to do as you have done. What size did you have to make the boot partition for ics to fit properly? This is new for me since I didn't have to resize at all for cm7. I've been using cm7 for a few months but would really like to try ics on another micro sd I got just for this. Do I follow verygreens instructions except for adding sneekpeak as the nightly?
Click to expand...
Click to collapse
I believe that in the ICS Nightly thread, there is a modified version of the image file with all that pre done for the SD card.
Tapatalkin it from my IHO CM7.1'd, MIUI Themed Optimus V
Hi,
I just bought a nook color. I'm trying to install nightly cm9 on it. i have been reading and i have some questions .. please help i don't wanna turn my new nook into paperweight lol. I understand i need to make a bootable sd card with CWR on it. i understand there are newer version CWR out there now but I am only able to find 4gb version of 3.0.2.8. Will that cause a problem ? Do i have to use 4gb version CWR? I can find 1gb CWM 3.2.0.1 ( i have a 4g micro sd card ). About wiping, i know with android phones you always wipe before you flash roms but i have been reading, posts suggest to wipe cach and dalvik AFTER flashing cm and gapps. Is that the correct order to wipe? [GUIDE] Install CM7 or CM9(!) + Clockworkmod to EMMC - ALL NOOKS! (Updated:1/16/12) - xda-developers This post don't even mention wiping dalvik. So what exactly should i wipe and in what order? Also in that post it says after you flash, without rebooting you are to remove sd card and format it on a computer... since its a bootable CRW, the nook color doesnt even have the recovery on it , will removing the sd just cause it to crush ? Please help ~ Thank you.
Best advice is to go to the "development forum" and read the CM9/ICS nightly thread.Everything you need is in the first post.I would suggest you test your SD card with CrystalDiskMark 3.0(free program,google it up)first to see if it is suitable for a ROM install.
See the SD card strange thread in this forum first.
Don't worry too much about bricking your Nook Color. It is pretty much impossible to get it in a state which you can't recover from as it has priority on booting from the SD card.
That's not say you shouldn't try to get it right to avoid any hassle.
For an internal install use the Eyeballer SD clockwork recovery method as detailed in the development forum. When you image this to an SD then you always end up with a 1GB partition on the card irrespective of the real SD size. Don't worry about that as this is just a staging post and you just need space to put on the zips you want to install.
For CM9 use the "unofficial" nightly builds and put the main ROM, Gapps, and the telephony permissions fix on.
When you boot from this card you will be in Clockwork recovery. First time you want to format system, data, and cache then install ROM, Gapps and telephony fix in that order.
After that you want to put in a cleanly formatted single partition SD card, either by reformatting partitioning the installation one or a different one if you wanted to keep the original. It won't crash but some apps expect the Sd card to be present.
Once rebooted then you should be in CM9. You can install clockwork recovery to the internal memory as well by using the ROM Manager app. This means that if you reboot with the N key held down you get into a boot menu and can choose to go into recovery. That is very convenient for subsequent updates as you can just copy zips onto the SD card via USB or Wifi without having to remove the card (ES File Explorr app helps a lot here).
For small updates you can normally just format system and cache then reapply the set of zips. This will leave your set up and installed apps alone. You don't need to do Dalvik separately as it is in the cache partition.
Thanks and what is the "telephony permission fix" ?
bobtidey said:
Don't worry too much about bricking your Nook Color. It is pretty much impossible to get it in a state which you can't recover from as it has priority on booting from the SD card.
That's not say you shouldn't try to get it right to avoid any hassle.
For an internal install use the Eyeballer SD clockwork recovery method as detailed in the development forum. When you image this to an SD then you always end up with a 1GB partition on the card irrespective of the real SD size. Don't worry about that as this is just a staging post and you just need space to put on the zips you want to install.
For CM9 use the "unofficial" nightly builds and put the main ROM, Gapps, and the telephony permissions fix on.
When you boot from this card you will be in Clockwork recovery. First time you want to format system, data, and cache then install ROM, Gapps and telephony fix in that order.
After that you want to put in a cleanly formatted single partition SD card, either by reformatting partitioning the installation one or a different one if you wanted to keep the original. It won't crash but some apps expect the Sd card to be present.
Once rebooted then you should be in CM9. You can install clockwork recovery to the internal memory as well by using the ROM Manager app. This means that if you reboot with the N key held down you get into a boot menu and can choose to go into recovery. That is very convenient for subsequent updates as you can just copy zips onto the SD card via USB or Wifi without having to remove the card (ES File Explorr app helps a lot here).
For small updates you can normally just format system and cache then reapply the set of zips. This will leave your set up and installed apps alone. You don't need to do Dalvik separately as it is in the cache partition.
Click to expand...
Click to collapse
Found the telephony fix thanks
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
You might consider simply using the SD card boot ROM's, and leaving the internal Nook alone for the present. That would allow you to try out the various Rom's available and find one that works best for you. I'm currently running CM7.2 Kang on my emmc partition, but booting on SD card from the CM9 nightly builds. The CM7.2 Kang is quite stable, but not as much fun as the alpha ICS CM9 stuff. Best of both worlds.
I already have cm7 on my phone , hopefully its not gonna be the same thing lol . i was hoping to put cm9 on there so it will entertain me for a while but if its really that buggy mb i will consider just running on cm7.
mr72 said:
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
Click to expand...
Click to collapse
Thanks. I already have bobzhome 7.2 on my phone. The reason why i wanna cm* on my nook is because i don't read(i read enough for school XD ) haha so the nook factory rom will be kinda pointless for me. Also just booting from sd and flashing roms seem really straight forward to me so that's why i want to flash cm* on internal memory. As im not that knowledgeble about nook colors, running on a bootable rom still seem complicated for me but i sure will think about it .
brentb636 said:
You might consider simply using the SD card boot ROM's, and leaving the internal Nook alone for the present. That would allow you to try out the various Rom's available and find one that works best for you. I'm currently running CM7.2 Kang on my emmc partition, but booting on SD card from the CM9 nightly builds. The CM7.2 Kang is quite stable, but not as much fun as the alpha ICS CM9 stuff. Best of both worlds.
Click to expand...
Click to collapse
when i was downloading cm7 roms , my anti virus kept saying there were viruses in the roms ... is that normal ?
optimusv45 said:
when i was downloading cm7 roms , my anti virus kept saying there were viruses in the roms ... is that normal ?
Click to expand...
Click to collapse
How many places you going to ask this?
It is a false positive.
Normal? No. Crappy antivirus? Yes.
As long as you are downloading from links from the developers here you're safe.
Sent from my NookColor using XDA App
just making sure since im not very knowledge about nook colors. i rather ask more than do something stupid on my device and cause myself problems.
Benzoman said:
How many places you going to ask this?
It is a false positive.
Normal? No. Crappy antivirus? Yes.
As long as you are downloading from links from the developers here you're safe.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
No problem. Just noticed it was in a separate thread already.
Please post what A/V you are talking about so others having the same issue will take note.
I'll also give a +1 to the people who suggested that you work off an SD card until you are really comfortable with the process. You can always recover your Nook, but why go through that hassle when the SD card is so easy.
Just my $.02
Dual booting SD
I agree with try the Dual boot off the SD card to see what you like. Check out http://forum.xda-developers.com/showthread.php?t=1000957Verygreens process was simple to follow and I am newer at rooting also. Cheers.
I posted what a/v already. its kaspersky internet security. i guess i never look into running off SD. I don't read much so i just don't need nook color stock ROM, i guess that's also part of why i wanna run on internal memory. oh and i bought a refurbished nook color from BNs website and it came defective. part of the screen didn't work. To those who wanna buy it from them i suggest to buy from a retail store so u don't have to pay shipping and waste time I think all they did was a factory restore on a return and sell it again for 149.
TL2000 said:
Please post what A/V you are talking about so others having the same issue will take note.
I'll also give a +1 to the people who suggested that you work off an SD card until you are really comfortable with the process. You can always recover your Nook, but why go through that hassle when the SD card is so easy.
Just my $.02
Click to expand...
Click to collapse
Im gonna buy a new nook color and i read that newer ones have different hardware. newer hardware aren't supported by CM7. I guess I'll have to try a nightly CM9 build.
The1Power said:
I agree with try the Dual boot off the SD card to see what you like. Check out http://forum.xda-developers.com/showthread.php?t=1000957Verygreens process was simple to follow and I am newer at rooting also. Cheers.
Click to expand...
Click to collapse
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
mr72 said:
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
Click to expand...
Click to collapse
optimusv45 said:
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
Click to expand...
Click to collapse
I just bought my nook color Dec. 30th, 2011 and I have ran cm7 as well as cm9. Like the others are saying, set up cm7 off of a SD card until you learn what you are doing then consider moving to the emmc.
optimusv45 said:
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
Click to expand...
Click to collapse
I believe that is CM9, not 7 that was having issues with the new nook color touch screen drivers.
Here's a post about it:http://forum.xda-developers.com/showthread.php?p=21333209&highlight=touchscreen#post21333209
Looks like it may already be fixed: http://forum.xda-developers.com/showthread.php?p=21353661&highlight=touchscreen#post21353661
I have seen instructions on how to apply CM9/ICS to eMMC and to also set up a dual boot sd card that contains it.
I would prefer at this point to set up an sd card with the most recent and/or stable nightly CM9/ICS only to see what it is all about and what the state of development is.
Could someone provide me with that info, please?
FYI: I am running my original NC having updated my v 1.3 with 5.12.20 instead of going the 1.4.1 route. It pretty much works in terms of my usage and I got the added benefit of having HBO Go work! Still not willing to give up my ability to "read in store".
Thanks in advance for any/all help with this
All the info is here. You just have to read, read some more, and then just read some more.
It all gets so much easier if you do this. Plus you'll find the threads you want to keep an eye on for new info.
Sent from my GT-P7510 using Tapatalk
Use the size-agnostic procedure that discusses putting CM7 on an SD card.. just rename the zip file to be compatible for flash. It is in the Dev section
Benzoman said:
All the info is here. You just have to read, read some more, and then just read some more.
It all gets so much easier if you do this. Plus you'll find the threads you want to keep an eye on for new info.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Having done numerous iterations of various CM and others both internally and on sd cards, I was able to do all of that because I do read this website rather thoroughly!
However, doing this specific task (as a standalone) just did not appear to come up.
I had assumed I could do it the same way I had done CM7 but was not certain due to apps and other issues at this stage.
davidr415 said:
Use the size-agnostic procedure that discusses putting CM7 on an SD card.. just rename the zip file to be compatible for flash. It is in the Dev section
Click to expand...
Click to collapse
Thanks...any suggestions for which version to try?
Just get the latest nightly on the samiam303 post. http://forum.xda-developers.com/showthread.php?t=1444943At this point there is nothing that is "stable". Make sure you use the large ics image or you'll need to expand boot. Finally I found I had to load the update and gaaps at the same time without a recovery boot in between to get the google calendar to sync. Runs real nice.
If I may suggest, try Racks triple boot of CM7 and CM9 from SD card -- see his thread
elsewhere on XDA -- I've been running it for several weeks, including latest update fro OC, and everything works fine. ICS is of course still "in process" but you might be surprised at how well it runs. And the CM7 is stable as a rock and swift, especially with the supercharger script installed. And you will still have your original B&N stock in emcc.
Thanks...I saw that and since I had already used CM7 off and on both internally and via an sdcard just didn't want to get into another dual boot scenario.
This time around, I just wanted a simple ICS steup on a dedicated sdcard that I would install when wanting to try it out and replace with my storage sdcard when operating normally with my rooted (5.12.20) 1.3.
hey guys, i browsed quite a while to see if there was a thread with a similar question but couldn't get a solid answer.
just got a nook color, version 1.3.0. my goal was to get [CM7.2-RC1] MiRaGe - KANG build of CyanogenMod on it, so my first step was putting UNooter on my micro sd.
after rebooting my nook color with the unooted sd, my nook still looked stock, but there was a menu asking me to choose "Home" or "Zeam Launcher." every time i
hit my N button, i get the complete action using Home or Zeam Launcher as well. I took out the sd card, and my options are the same- did i install completely internally? Was i not supposed to UNoot at all, and just put the CM Mod zip on my sd?
not sure where to go from here- maybe make a recovery card and retry? any suggestions would be appreciated.
thanks!
So you got the NC 1.3.0. First step, MAKE SURE it is the NC, not the NT.
You want to get CM7.2-RC1 KANG. OK, next step, where do you intend to run that custom ROM from? eMMC or uSD?
When you decided to run a custom ROM, there is NO NEED to root it first.
Instructions or help will follow when you provide enough info and what you try to accomplish.
votinh said:
So you got the NC 1.3.0. First step, MAKE SURE it is the NC, not the NT.
You want to get CM7.2-RC1 KANG. OK, next step, where do you intend to run that custom ROM from? eMMC or uSD?
When you decided to run a custom ROM, there is NO NEED to root it first.
Instructions or help will follow when you provide enough info and what you try to accomplish.
Click to expand...
Click to collapse
thanks for the quick response! i was trying to get CM7.2-RC1 KANG on my uSD. so i can just put the cm7 file on my sd card and reboot and forget UNooter altogether? eventually i'd like to get eMMC back to stock, but i'm not really concerned about that right now.
ChrisMMcD said:
thanks for the quick response! i was trying to get CM7.2-RC1 KANG on my uSD. so i can just put the cm7 file on my sd card and reboot and forget UNooter altogether? eventually i'd like to get eMMC back to stock, but i'm not really concerned about that right now.
Click to expand...
Click to collapse
If you are just looking to run KANG on your SD card, then just follow the directions HERE. You will need to rename the KANG zip file to update-cm- when you put it on your SD card.
That's it.
GMpower has provided the link.
Following it and you should be good to go.
Note:leapinar (spelling?) does have a better (more storage) version of the image. Search in that thread.