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!
Hey guys,
I am on CM7 i was on 7.0.2 official version. i downloaded and installed the beta update from dalingrin's so i am no on:
Cyanogenmod-7.1.0-RCO-encore-KANG
I then installed the OC kernel that i was under the impression should overclock to 1.2 but when i try to overclock in the CM7 settings, the most it will let me choose is 925. i'm wondering if i'm missing something?
i used the following zip for the kernel:
update-CM7-dalingrin-OC-sd-052311.zip
any help would be appreciated, i would post in the actual thread but i don't have enough posts.
thanks
EDIT: All fixed, needed to download and install the eMMC version so that it would install to internal memory instead of trying to boot off the sd card.
First off, glad you posted in the right section Already ahead of the curve!
So, did you install the beta to and SD or internal memory? I assume internal memory, in which case you need to download the OC that has eMMC in the title (which is the internal memory).
ace7196 said:
First off, glad you posted in the right section Already ahead of the curve!
So, did you install the beta to and SD or internal memory? I assume internal memory, in which case you need to download the OC that has eMMC in the title (which is the internal memory).
Click to expand...
Click to collapse
haha I know how the forums work I just haven't used this one that much
I installed both through the sd in the same clockwork session...should I have booted after installing cm then installed the oc kernel?
Sent from my DROIDX using Tapatalk
xjacobx said:
Hey guys,
I am on CM7 i was on 7.0.2 official version. i downloaded and installed the beta update from dalingrin's so i am no on:
Cyanogenmod-7.1.0-RCO-encore-KANG
I then installed the OC kernel that i was under the impression should overclock to 1.2 but when i try to overclock in the CM7 settings, the most it will let me choose is 925. i'm wondering if i'm missing something?
i used the following zip for the kernel:
update-CM7-dalingrin-OC-sd-052311.zip
any help would be appreciated, i would post in the actual thread but i don't have enough posts.
thanks
Click to expand...
Click to collapse
The zip for OC when you have CM7 installed to eMMC (internal memory) is update-CM7-dalingrin-OC-emmc-052311.zip
OC-sd nomenclature is for those who have CM7 installed and booting off their SD card, instead of just using it for storage space.
Nburnes said:
The zip for OC when you have CM7 installed to eMMC (internal memory) is update-CM7-dalingrin-OC-emmc-052311.zip
OC-sd nomenclature is for those who have CM7 installed and booting off their SD card, instead of just using it for storage space.
Click to expand...
Click to collapse
Oh ok, i thought that since i was installing through the sd that was the sd version. got it. i'll download the emmc version and install from the sd.
thanks so much guys
Thanks for your help guys running 1.1 now, 1.2 caused reboots but 1.1 is prefectly fine with me
thanks again still learning the whole sd card stuff. i'm coming from the dx and we just put the zip on the sd and install, no booting of sds and that stuff.
but i'm learning
I have searched diligently and have yet to find specific instruction for creating a bootable SD card for my NC with MIUI Nook Color 1.9.16 (or any version of MIUI for that matter).
I am currently running a fully rooted version of 1.3 on the emmc and "all is well" and I need it left that way so as to continue having access to "in store reading" which I use quite a bit.
Have previously had CM7 and Phiremod running both internally and on an SD card at various times and tried to do a previous version of MIUI on the card using the same process without any luck.
Thanks in advance.
You can use verygreens method here -
http://forum.xda-developers.com/showthread.php?t=1000957
Important part is to rename the miui zip like this -
'How to update to a new build:
put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)'
..and it should work fine
cheers,
Many thanks as that did the trick!
Loaded and running from SD card.
It installed/is using the new Market interface (3.1.3?).
Where are/is "My Apps" as I do not seem to be able to find it.
D/L Netflix and it runs just as it should but the soundlevel at max is quite a bit lower than on rooted 1.3.
Free Koi living wallpaper looks beautiful.
My Apps - strangely there isn't one, but this works nicely -
http://forum.xda-developers.com/showthread.php?t=1154299
Sound level - Download nook tweaks from market and change settings in that
Cheers,
What did you rename the MIUI file? I've tried it a couple different ways and checked the MD5's, but keep getting errors. Unless my SD card has been corrupted somehow (I used it for other SD boots before this, so not too likely), I can't think of anything else causing the problem.
Hi. I tried putting the MIUI zip in the root of the sd card and booted into recovery as stated. It was renamed as one of the cm7 updates and installation went as per normal. However, when I did boot up the nook was stuck looping the MIUI animation and did not finish. What did I do wrong?
PhoenixClaw said:
Hi. I tried putting the MIUI zip in the root of the sd card and booted into recovery as stated. It was renamed as one of the cm7 updates and installation went as per normal. However, when I did boot up the nook was stuck looping the MIUI animation and did not finish. What did I do wrong?
Click to expand...
Click to collapse
Maybe just didn't wait long enough... the first boot takes a long time since the update script clears cache and dalvik cache.
Of course... this is just a wild guess since you didn't provide a whole lot of information... more information may yeild different feedback.
DizzyDen said:
Maybe just didn't wait long enough... the first boot takes a long time since the update script clears cache and dalvik cache.
Of course... this is just a wild guess since you didn't provide a whole lot of information... more information may yeild different feedback.
Click to expand...
Click to collapse
What kind of information? My nook color originally had the latest CM7 nightly on the sd card. I followed verygreen's method when I installed that. I used the NC normally. Then, I followed this thread and applied verygreen's method. I downloaded the MIUI rom from the miui thread, renamed it like the cm7 nightly zip ("cm_encore_full-253.zip") and put it in the root of the sd card. I put the sd card back in and booted via recovery. It installed and shut down. I turned it on again, and reached the MIUI globe thing. It was looping and stuck there for 30 minutes.
I've been thinking of trying miui.
If anybody has got.it running from SD please give the step-by-step procedure for the rest of us.
Thanks
A search would show you....
http://forum.xda-developers.com/showthread.php?t=1271982&highlight=Miui+sd
I hate to revive a dead thread, but I have been trying everything I could read or download.
I am using the Size-agnostic installer from this thread: http://forum.xda-developers.com/showthread.php?t=1000957
I am trying to flash MIUI 1.9.16 (MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer) (http://goo-inside.me/miui/encore/)
I successfully installed CM7 to this Sandisk Class4 16gig microSD. Every time I try to flash MIUI, I re-burn the size agnostic card image, copy over the cm7-renamed MIUI ROM, and boot.
The installer seems to work, just like my CM7 installs. Then, when I try to reboot, it goes back to the installer (linux penguin at the top, goes through the motions of trying to flash another rom, when not finding anything, it shuts down).
I know I am missing something simple.
Am I to install CM7, then MIUI on top of it (without reburning the card)? Am I just using an SD-incompatible ROM? For those who were successful, where did you download the ROM from?
I know I have lots of questions, I hope you guys see my effort (that I don't just want someone to give me a quick fix), and I thank you in advance for your help.
Kind regards!
harryzee said:
Many thanks as that did the trick!
Loaded and running from SD card.
It installed/is using the new Market interface (3.1.3?).
Click to expand...
Click to collapse
I'm certainly no expert, but I have flashed two different versions of MiUi to micro SD cards adn then worked fine. You do not need to do i over CM7. Like you, I prepared a clean SD and used the size agnostic procedure. I renamed the MiUi file to some that started with update-cm-
I got my MiUi file here:
http://roms.miui.us/
I used a program called SD Formatter to format the card.. then I used the 1.3 version installer. I sometimes had problems using winimage to create this sd card . You have to select the drive letter for the sd card and then use the "restore" choice on the menu.
David, thanks for your response. I had already wiped it and installed CM7, but when I saw your post, I gave MIUI one last try. I downloaded from that site, and BAM, it installed perfectly! Thanks heaps!
I am attempting to install Nookie Comb onto my Nook. I have read asnd attempted to follow the instructions given at:
http://forum.xda-developers.com/showthread.php?t=1016115
The problem is: it appears that the instructions are not entirely complete.
The instructions include the following steps:
NOTE: Flash with the latest ClockworkMod Recovery/via ClockworkMod Recovery SD or standard Clockwork Recovery 3.0.1.0. This version is fully compatible with any Clockwork used for Nookie Froyo 0.6.8 (see the Nookie Froyo page here)
* Copy "NookieCombvXXX.zip" to the root of your SD
* Place SD in nook and power on
* Format SYSTEM, DATA and CACHE (You do not need to wipe if coming from a previous version!)
* Flash Nookie Comb
* Once finished flashing, unmount your sdcard, remove from the slot and reboot.
after searching for several hours, I was able to find a Clockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
I performed the necessary work with imaging, copied the NookieComb zip file (0.4.13) to the SD crd, and used it to boot my Nook. That is when I ran into the other problem: how on Earth do I "flash" the Nookie Comb???
Using various searches, I have been looking for instructions on how to do this. I have fond none, on this site or anywhere else. There are no "flash" commands on the Recovery application. I am seeing people referring to having done the "flashing" but no one describes how this was done. Worse: without this "flashing" my Nook will not boot to the new OS.
Will someone *please* tell me what I need to do in order to do this "flashing"???
Thank you...
factor3 said:
I am attempting to install Nookie Comb onto my Nook. I have read asnd attempted to follow the instructions given at:
http://forum.xda-developers.com/showthread.php?t=1016115
The problem is: it appears that the instructions are not entirely complete.
The instructions include the following steps:
NOTE: Flash with the latest ClockworkMod Recovery/via ClockworkMod Recovery SD or standard Clockwork Recovery 3.0.1.0. This version is fully compatible with any Clockwork used for Nookie Froyo 0.6.8 (see the Nookie Froyo page here)
* Copy "NookieCombvXXX.zip" to the root of your SD
* Place SD in nook and power on
* Format SYSTEM, DATA and CACHE (You do not need to wipe if coming from a previous version!)
* Flash Nookie Comb
* Once finished flashing, unmount your sdcard, remove from the slot and reboot.
after searching for several hours, I was able to find a Clockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
I performed the necessary work with imaging, copied the NookieComb zip file (0.4.13) to the SD crd, and used it to boot my Nook. That is when I ran into the other problem: how on Earth do I "flash" the Nookie Comb???
Using various searches, I have been looking for instructions on how to do this. I have fond none, on this site or anywhere else. There are no "flash" commands on the Recovery application. I am seeing people referring to having done the "flashing" but no one describes how this was done. Worse: without this "flashing" my Nook will not boot to the new OS.
Will someone *please* tell me what I need to do in order to do this "flashing"???
Thank you...
Click to expand...
Click to collapse
Install zip from SD card option in CWR
lockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
Click to expand...
Click to collapse
That is the only one you need.
The procedures were written in March, it was right at that time but a bit outdated now since CwM has released few more newer versions and B&N did release new versions of NC.
"flash/flashing ROM" refers to replace/replacing the currently stock ROM (by saying)
However, by doing, it is the "install/choose zip from the SD card"
Then I have a real problem...
I was able to do the "Choose Zip from SD card" operation (which is apparently no different from my previous successful installation of the Phiremod system), and successfully installed the Nookie Comb zip file.
The problem seems to occur when I remove my SD card (as instructed) and do the reboot. The Nook briefly shows the Cyanogen logo (!??) and then it appears to hang!
Am I missing something here? The Nook becomes totally unresponsive and its screen looks like it is off...
Please advise.
lockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
patruns said:
That is the only one you need.
Click to expand...
Click to collapse
Pat:
Actually, I disagree. I want to put different zips on the SD card for research purposes (I want to develop some Android applications and test them using different software configurations). With a 1 GB limit, granted the zips are relatively small but if I have a bunch of them for different Android versions, plus backups of different user and system configurations, a 1 Gb SD card will run out of space fairly quickly.
There really does need to be different images for different SD card sizes.
How are these images made? Maybe I can make some and make them available... ?
factor3 said:
lockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
Pat:
Actually, I disagree. I want to put different zips on the SD card for research purposes (I want to develop some Android applications and test them using different software configurations). With a 1 GB limit, granted the zips are relatively small but if I have a bunch of them for different Android versions, plus backups of different user and system configurations, a 1 Gb SD card will run out of space fairly quickly.
There really does need to be different images for different SD card sizes.
How are these images made? Maybe I can make some and make them available... ?
Click to expand...
Click to collapse
Just use that .zip and then use something like EaseUs Partition Manager (free) to stretch the partition to the size that you need and to create additional partitions. Earlier versions have issues with the blue dot device partitions as well as doing proper data/system and cache wipes.
factor3 said:
lockwork Recovery version 3.2.0.1 (though only for 1 GB! Are there any versions in existence for larger SD cards???).
Pat:
Actually, I disagree. I want to put different zips on the SD card for research purposes (I want to develop some Android applications and test them using different software configurations). With a 1 GB limit, granted the zips are relatively small but if I have a bunch of them for different Android versions, plus backups of different user and system configurations, a 1 Gb SD card will run out of space fairly quickly.
There really does need to be different images for different SD card sizes.
How are these images made? Maybe I can make some and make them available... ?
Click to expand...
Click to collapse
All you have to do is use EASUS or MiniTools Partition Manager to resize to claim the rest of the SD space.
Personally I wouldn't install Nookie Comb as it is outdated and made from an Incomplete SDK as Honeycomb was never Open-Sourced. Better to install CM7.1 while we wait for the Andtoid 4.0 ICS source to be released in Nov. and the inevitable Port of it to the Nook come Dec/Jan if not sooner. CM7 is more then enough for now and includes special "tablet tweaks" just for the Nook Color including "Honeycomb-esque" Bar buttons for Home, Menu, Back, ect...
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Successfully Installed...
I did solve my installation problems. I ended up doing a restore of the original Nook system, then running the reinstall once again.
It turned out that there was apparently something on my original Phiremod installation that screwed up the Nookie install...
In any event: japzone, I am wondering about the "incomplete" SDK that Nookie Comb is based on. Would that incompleteness include non- working location capabilities? Apparently, not only do they always seem to fail on this OS, but there are some minor network and email annoyances,as well (and I really don't like the awful keyboard!).
One thing that is good, though: some of the more advanced readers and Honeycomb- based applications seem to work well on Nookie Comb. Also: with Nookie Comb's booting off the Nook instead of the SD card, I have more space for things I want to put on it. Nookie Comb's power handling is better, too. With Phiremod I needed to charge my Nook every day. With Nookie Comb I am doing a charge every third day -- even when I am heavily using my Nook.
In all, aside from the annoyance of failing location services and a bad keyboard, I am pretty happy with Nookie Comb...
I am, however, open to looking at better installations. What version of Android does the CM7 you are suggesting run? If it isn't Honeycomb (and you seem to be implying it isn't) then aside from it being based on a stable Android version, what advantages does it have over Nookie Comb?
FYI, Pat:
EASUS does not work. It does allow you to change partition sizes on different devices, but it does not do this for FAT partitions -- which are the only partition that you can boot a Nook on...
factor3 said:
In any event: japzone, I am wondering about the "incomplete" SDK that Nookie Comb is based on. Would that incompleteness include non- working location capabilities? Apparently, not only do they always seem to fail on this OS, but there are some minor network and email annoyances,as well (and I really don't like the awful keyboard!).
One thing that is good, though: some of the more advanced readers and Honeycomb- based applications seem to work well on Nookie Comb. Also: with Nookie Comb's booting off the Nook instead of the SD card, I have more space for things I want to put on it. Nookie Comb's power handling is better, too. With Phiremod I needed to charge my Nook every day. With Nookie Comb I am doing a charge every third day -- even when I am heavily using my Nook.
In all, aside from the annoyance of failing location services and a bad keyboard, I am pretty happy with Nookie Comb...
I am, however, open to looking at better installations. What version of Android does the CM7 you are suggesting run? If it isn't Honeycomb (and you seem to be implying it isn't) then aside from it being based on a stable Android version, what advantages does it have over Nookie Comb?
Click to expand...
Click to collapse
Nookie Comb is built on the SDK of Honeycomb and not the AOSP source since the source for it wasn't available until a few days ago when Google decided to dump it at the same time they released the Source for it's successor 4.0 ICS. Theoretically NookieComb could be patched using the now released source but most Developers are focusing on ICS now that it's out as Honeycomb was long ago marked as a Stop-gap by Google and lost cause to make a stable port by Devs. If you really want tablet specific apps on your Nook NookieComb is your only option right now but other than that there is no Reason to switch to the Far more Stable and more Advanced CM7.1.
It's up to you. If NookieComb fufills what you need and you can live with the Bugs which will most likely never be fixed, go ahead and stick with it until ICS is ported to the Nook. However I and most other people here would reccomend switching to CM7.1(built on Android 2.3.x) as it has far more support, larger feature set, and is much more stable.
PS: If you were wondering, yes, CM7 has the Notification Soft-Keys just like NookieComb so no need for Softkeys or Button Savior.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
I forgot, Another thing CM7 has that NookieComb doesn't is Bluetooth.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Some quick questions
Japzone:
1. Does CM7 run off the nook or off the SD card? My previous Phiremod installation needed an SD card in order to run; Nookie Comb does not. Does CM7?
2. How is CM7 for power? Phiremod ate up power so fast that I had to charge my Nook every day. How long can you run CM7 between charges?
3. The Phiremod installation also had Bluetooth and Location services. The location services worked but Bluetooth apps and configuration always crashed when I tried to use them. How well do they work on CM7?
factor3 said:
Japzone:
1. Does CM7 run off the nook or off the SD card? My previous Phiremod installation needed an SD card in order to run; Nookie Comb does not. Does CM7?
2. How is CM7 for power? Phiremod ate up power so fast that I had to charge my Nook every day. How long can you run CM7 between charges?
3. The Phiremod installation also had Bluetooth and Location services. The location services worked but Bluetooth apps and configuration always crashed when I tried to use them. How well do they work on CM7?
Click to expand...
Click to collapse
1- CM7 can be installed to Nook internal emmc or by using verygreen's "size agnostic installer" can be installed to MicroSD. verygreen's installer auto sizes the install to fill entire SD no matter the size and allows easy updates to CM7
2- CM7 has had most of the battery issues ironed out for awhile now.
3- Bluetooth works fine on CM7, I've used a Wii Remote as a game controller without issue and pairing with other Bluetooth devices posed no issue. Only problems are the Short range(caused by the lack of a Bluetooth antenna in the Nook), and it will sometimes refuse to come on because of the hardware situation, solution is to turn off wifi and do a hard reboot then turn Bluetooth on first before WiFi.
I personally boot off SD because it allows me to easily switch to the StockOS if I feel like it and if something happens to my Nook I have less things I have to do before taking it in for repair. I've never really noticed a difference in speed because of usind an SD. A Class 4 Sandisk or Class 6 Generic cards work fine.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
japzone said:
Nookie Comb is built on the SDK of Honeycomb and not the AOSP source since the source for it wasn't available until a few days ago when Google decided to dump it at the same time they released the Source for it's successor 4.0 ICS. Theoretically NookieComb could be patched using the now released source but most Developers are focusing on ICS now that it's out as Honeycomb was long ago marked as a Stop-gap by Google and lost cause to make a stable port by Devs. If you really want tablet specific apps on your Nook NookieComb is your only option right now but other than that there is no Reason to switch to the Far more Stable and more Advanced CM7.1.
It's up to you. If NookieComb fufills what you need and you can live with the Bugs which will most likely never be fixed, go ahead and stick with it until ICS is ported to the Nook. However I and most other people here would reccomend switching to CM7.1(built on Android 2.3.x) as it has far more support, larger feature set, and is much more stable.
PS: If you were wondering, yes, CM7 has the Notification Soft-Keys just like NookieComb so no need for Softkeys or Button Savior.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Click to expand...
Click to collapse
you know if you read the nookiecomb thread it says its based off of nookiefroyo(WHICH IS FROYO BASED) but themed to look like honeycomb
just saying
Incorrect Version???
luigi90210:
I'm a little lost here.
Are you saying that NokieComb is actually *not* Android 3 based? That Froyo is actually an earlier Android version???
This is important for me to know, because my main reason for even looking at NookieComb was I was looking for a later Android version. I had thought that Froyo was based on Android 3. Was this an incorrect belief???
factor3 said:
luigi90210:
I'm a little lost here.
Are you saying that NokieComb is actually *not* Android 3 based? That Froyo is actually an earlier Android version???
This is important for me to know, because my main reason for even looking at NookieComb was I was looking for a later Android version. I had thought that Froyo was based on Android 3. Was this an incorrect belief???
Click to expand...
Click to collapse
No I was saying that Honeycomb wasn't OpenSourced until recently. NookieComb was based off of the Android 3.x SDK(SoftwareDevelopementKit) for Honeycomb and SDKs don't include alot of important pieces of code. IceCreamSandwich however has been OpenSourced and released under AOSP(AndroidOpenSouceProject) so it'll be much more stable within a few months of Devs working on it.
Here are Android versions by number:
2.1=Eclair(AOSP)
2.2=Froyo(AOSP)
2.3=Gingerbread(AOSP)
3.0/3.1/3.2=Honeycomb(Closed-Source Tablet Only)
4.0=IceCreamSandwich(AOSP)
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Japzone:
1. My last question wasn't directed at you. It was directed at luigi90210, who seems to be saying that no: Nookie Comb is not based on Honeycomb, but on Froyo.
2. And it sounds like you are incorrect. If what luigi90210 says is true, and if Froyo is actually the base for Nookie Comb, then Nookie Comb is actually based on Android 2.2 (since, as you point out, Froyo *is* Android 2.2).
3. My problem was that I didn't know what Froyo was. I only knew about Android 2 and Honeycomb -- I didn't know the names of the different point versions. As it turns out, what luigi90210 said is correct (since I first received the instructions that I was complaining about from the Nookie Comb Thread): Nookie Comb is, as its author says in the Nokie Comb thread, based on Froyo, not Honeycomb.
In actual fact, luigi90210 has given me the best reason for following your suggestion of switching to CM7: that Nookie Comb is based on an even earlier version of Android, meaning that there are actually no Honeycomb- based systems available for the Nook. There is, consequently, no reason for me not to go to CM7...
factor3 said:
In actual fact, luigi90210 has given me the best reason for following your suggestion of switching to CM7: that Nookie Comb is based on an even earlier version of Android, meaning that there are actually no Honeycomb- based systems available for the Nook. There is, consequently, no reason for me not to go to CM7...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=936995
is the honeycomb based rom for Nook. (though extremely buggy)
it's essentially at the same place as the ICS build but the ICS build is going to continue to improve.
Hey guys, I'm having a tough time getting the Mirage CM7 ROM to work on my Nook Color via SD.
First I went to the Mirage thread I found: http://forum.xda-developers.com/showthread.php?t=1344873
I downloaded the ROM from the first post. I heard there's a more recent build, 11102012, but I can't find it :\ (some help finding it would be nice). Also
Since Eyeballer's guide that was listed is for eMMC only, I went to the other thread, verygreen's guide, that was linked in his guide: http://forum.xda-developers.com/showthread.php?t=1000957
I got the .GZ from there, unpacked, and wrote the IMG on the SD card (using Win32DiskImager). Then I copied and pasted the ROM directly onto the SD.
I proceeded to boot my Nook with the SD card, and now all I get is
"Initial install files not found. Please download it from nook.linuxhacker.ru and put on first partition of this SD card the name should start with updatei-cm and end with .zip"
I also downloaded the file from the "How to update if you already installed using older version of the installer and don't want to reinstall (understandably):" part of verygreen's thread but no success