Hello Nookers,
I myself and pndo1 of XDA have posted guides for dual booting CM7 and Stock 1.2. My first one was crappy, my second one was a little less crappy, and pndo1's was pretty good, but had too many steps. So yeah, I decided to clear this up once and for all. Alright, enough of that garbage, let's get on with the guide!
0. Make a CWM sd card using these instructions.
1. Download CM7 to your sd card. I recommend the latest version from here. Also, if you would like to overclock download this. Lastly, if you would like to remap Volume + and - to Menu and Back, download this too. Also, your gonna want (duh) have a copy of Nook Color Stock 1.2. This one is the best in my opinion. Also, if you would like to root Stock 1.2, get this. Now get gapps from here. Almost! Download thishere. And now the multiuboot! Grr... this is tiring... but lasties! Get it here. Put ALL the files you downloaded on your SD Card.
1. Boot into CWM. Go into Backup+Restore and create a backup. Then go into Mounts+Storage and unmount the sd card. Put in an MicroSD reader in your computer. Navigate to /sdcard/clockworkmod/ and find the backup. Copy it to your computer. You can now delete it from the SD Card. Put the SD Card back in the nook. Go into Mounts+Storage and hit "Mount sd card" Now from the same place, wipe system, data, and cache. Now go to the root menu (hit the power button once). Hit "Install zip from sd card" then "Choose zip from sd card" Select prep.dualboot.zip. Then redo the choose zip Select your downloaded 1.2 Zip. It should be called "update_nc_stock_1.2_keepcwm.zip" Flash that. Now wait for it to install. Reboot your Nook. It will boot and will ask you to setup the Nook. Set it up but if you don't have wifi, follow these instructions. After setting up, boot back into CWM using your sd card.
2. Now Choose the zip from sd again, but select ManualNooter. That will take one minute to flash. Reboot again. Make sure your root is setup. To confirm, download an app from the market. Any app.
3. Once that is done, boot back into CWM. Flash the zip "eclair-to-dualboot-0.2.zip" It will duplicate Stock 1.2 to the Second partition. Now go into Mounts+Storage, and wipe system+data+cache. Now choose zip again, but this time pick CM7. Then Choose again, pick GAPPS. Then anything else, like that KeysMod or OC kernel. Now flash Multi-Uboot-0.3.zip. Now reboot without holding anything. It should boot CM7. Reboot, but this time hold the home button. BAM! Stock 1.2. Hope it worked for ya!
To those whom it doesn't work:
yelloguy said:
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
Click to expand...
Click to collapse
Credits:
@GirLuvsDroid for the feedback and testing
@GabrialDestruir for 1.2 Manual Nooter
@Koush for ROM Manager and CWM Flashes
@yellowguy for telling us to flash prep.dualboot
@Anyone else who helped but escapes my mind at the moment
@pndo1 (Who has moved on to better things than our little NC's... aka Flyer) for this orignal project
I've been wanting to dual boot my NC for a while now, but I've read several sets of instructions and kept getting twisted up in them. I was also concerned that having a dual boot would make it difficult to impossible to continue installing the CM7 nightlies and the latest Dal kernels.
These instructions look really clear and easy to follow and I thank you for that!
I just want to clarify my understanding: both CM7 and stock 1.2 are run from eMMC, correct? And, because stock 1.2 is on the second partition, it's just business as usual to install the nightlies and the latest kernel on the first partition, right?
Again, thanks for taking the time to rework your instructions again. Your contributions are much appreciated!
Why a special uboot? Stock cm7 uboot (based on bn 1.2) already does multiboot... (hold down n on boot for info) and dalingrin's nook tweaks lets you set up default options from prefs menu...
That said, I didn't read the instructions carefully so maybe there's a reason...
@GirLuvsDroid Your welcome, and yes both run from the emmc. Flash nightlies and kernel like anything. Just nothing to the dual boot partition.
@fattire For me the CM7 Alternate boot option hangs. But again, that's me.
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
MHotovec said:
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
Click to expand...
Click to collapse
MH, it's the link in the OP that says this: "Last one (yes, really!) here." It's not the Multi-Boot-Uboot-0.3.zip but the eclair-to-dualboot-0.2.zip.
Disgregard this post -- I'm an idiot and apparently blind, as well.
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
MHotovec said:
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
Click to expand...
Click to collapse
I must be blind -- I don't see where it says to flash both. I only see the eclair-to-dualboot in the instructions.
Nevermind -- I found it. It's the last step. I stand corrected and I'm glad I do because I'm planning to do this when I get home from work tonight. Thanks for setting me straight!
Reflashing the eclair to dualboot wasn't the answer, now is doesn't even TRY to boot the stock 1.2.
Now where did I leave that drawing board....
I found the download link for the Multi-Boot-Uboot-0.3.zip:
http://api.viglink.com/api/click?fo...dified u-boot.bin based on B&N 1.2 source
GLD, if anyone tells you that you're not a goddess, you tell them that I said you are.
Of course, that didn't solve the problem. (sigh)
I ran the entire routine again, and this time used the v.03 multi-boot that you found, same problem. It will boot into CM7 just fine, but it hangs up when booting into stock.
ahhhhhh, that's just so sweet, MH!
I just went through the whole process myself and everything went perfectly right up until I tried to boot into stock 1.2. Exactly like you, it hangs on the N and won't boot up. CM7 boots just fine, though.
Well, at least I know it's not just me.
By any chance, have you run the app that changes your Nooks RAM from 'new way' to 'old way'? (1gb data, 5gb apps).
I have, I wondering if that has something to do with it (just fishing of course, it's not like I actually KNOW anything).
Yes, I had a blue dot NC that I repartioned, but I did it using the custom partition (around 2GB data).
Well, multi-boot link added.
Oh, to those whom it doesn't work (stuck on N), try flashing 1.2 zip and manual nooter without rebooting and then eclair2dualboot then wipe system,data, and cache. Then flash cm7 and goodies. Not one reboot. Try it and only then say if it works or doesn't.
I'll try this no-boot method when I get a chance tomorrow. One question for you -- assuming I get this to work, is there any reason I can't restore /data from the CWM backup of my original setup that I made before I started the dual boot process?
I get the same result with the no boot method. CM7 boots fine, Nook stock hangs on the 'N' screen.
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
@GLD Yes, I think you can restore safely.
@yellowguy You don't need prep dual boot because eclair2dualboot already takes care of that. And if my instructions didn't work, try yellowguys, a slightly refined method.
Related
Hello, everyone!
How do I flash this .zip?
http://forum.xda-developers.com/showthread.php?t=682828
HTc hero 2.1
Thanks
Do you have root access on your phone?
Word of advice: If you have superuser 2.1 or 2.2.2 or whatever already working well, I wouldn't install 2.3.1 until more people verify it works flawlessly or unless there is something specific about 2.3.1 that you need. 2.3.1 came out just a day or 2 ago, and many apps already had issues with 2.2.2... I personally still use 2.1. If you do choose to use 2.3.1, tell us how it goes.
I've been following that thread for a few days, and many people had issues getting 2.3 working, but it looks like the dev fixed the bugs and made 2.3.1 flashable.
In general, to flash any zip:
Copy zip to root of sdcard (i.e., sdcard main directory, not inside a folder)
Boot to recovery: turn phone off, hold home+power
Backup/Restore > nandroid + ext backup!! (just in case you don't like post-flash results)
Flash zip from sdcard, choose the zip you want to flash
Reboot
i did that it said installed fine but nothing showedup
You don't see superuser in your app drawer anymore? Or what?
You should see 'Superuser Permissions' in your app drawer. But the SU program doesn't actually 'show up' unless it's actively being called -- in other words, you'll basically only see it when another program requests superuser permissions....programs like setcpu, Autokiller, file explorers.
c00ller said:
Word of advice: If you have superuser 2.1 or 2.2.2 or whatever already working well, I wouldn't install 2.3.1 until more people verify it works flawlessly or unless there is something specific about 2.3.1 that you need. 2.3.1 came out just a day or 2 ago, and many apps already had issues with 2.2.2... I personally still use 2.1. If you do choose to use 2.3.1, tell us how it goes.
I've been following that thread for a few days, and many people had issues getting 2.3 working, but it looks like the dev fixed the bugs and made 2.3.1 flashable.
In general, to flash any zip:
Copy zip to root of sdcard (i.e., sdcard main directory, not inside a folder)
Boot to recovery: turn phone off, hold home+power
Backup/Restore > nandroid + ext backup!! (just in case you don't like post-flash results)
Flash zip from sdcard, choose the zip you want to flash
Reboot
Click to expand...
Click to collapse
i see the su app but when i do this it only boot loops and stays looping forever unless i pull battery
what am i missing im using clockworkmod recovery
Are you using a custom ROM or kernel? Or do you still just have the stock 2.1 on your phone? If you're using an overclocked (OC) kernel or a ROM that is built with an OC kernel in it, this could be the reason for the bootloops. Some phones aren't capable of booting up at OC speeds.
stock 2.1 although rooted obciously
I'm new to using non stock ROMs and have heard good things about the Cyanogenmod and wanted to give it a try. I rooted my phone using Super One Click, I installed Clockworkmod to install the ROM and backup my settings, then I got the stable version of Cyanogenmod for my phone HTC Hero CDMA (update-cm-6.0.0-Heroc-signed.zip). I then followed the steps from the WIKI I updated the Radio, wiped my phone's data, then the cache, I selected the ROM to install from the root directory of my SD card, let it run through then told it to reboot the system. thats where the problem shows up it comes to the first HTC screen and will just sit there forever I even tried leaving it on overnight. I tried to flash it with different versions of Cyanogenmod and all had the same result, however I was able to get a version of damagecontrol to flash correctly on my phone so I know its not a brick.
I have searched quite a few posts but have not found anything that helps I have tried wiping multiple times and even wiped Dalvik cache. I ran a logcat to see if it might help me debug whats going on and it appears to be looping through the same things over and over I rebooted it again and had the same results. I can supply any info needed from the logcat needed but not sure what parts might help.
the different versions of ROMs I have tried to use are:
update-cm-6.0.0-Heroc-RC1-signed
update-cm-6.0.0-Heroc-signed
update-cm-6.1.0-RC1-Heroc-signed
Also tried Cyanogenmod nightly 87, 95, & 99
fresh-cdma-hero-1.1
DamageControlv2.08.1
adrazar said:
I'm new to using non stock ROMs and have heard good things about the Cyanogenmod and wanted to give it a try. I rooted my phone using Super One Click, I installed Clockworkmod to install the ROM and backup my settings, then I got the stable version of Cyanogenmod for my phone HTC Hero CDMA (update-cm-6.0.0-Heroc-signed.zip). I then followed the steps from the WIKI I updated the Radio, wiped my phone's data, then the cache, I selected the ROM to install from the root directory of my SD card, let it run through then told it to reboot the system. thats where the problem shows up it comes to the first HTC screen and will just sit there forever I even tried leaving it on overnight. I tried to flash it with different versions of Cyanogenmod and all had the same result, however I was able to get a version of damagecontrol to flash correctly on my phone so I know its not a brick.
I have searched quite a few posts but have not found anything that helps I have tried wiping multiple times and even wiped Dalvik cache. I ran a logcat to see if it might help me debug whats going on and it appears to be looping through the same things over and over I rebooted it again and had the same results. I can supply any info needed from the logcat needed but not sure what parts might help.
the different versions of ROMs I have tried to use are:
update-cm-6.0.0-Heroc-RC1-signed
update-cm-6.0.0-Heroc-signed
update-cm-6.1.0-RC1-Heroc-signed
Also tried Cyanogenmod nightly 87, 95, & 99
fresh-cdma-hero-1.1
DamageControlv2.08.1
Click to expand...
Click to collapse
try this:
using a rom that works flash a new recovery image using ROM Manager (find it in the market)
Tell ROM Manager to flash the recovery for ClockworkMod 2.5.0.1
Then Reboot to recovery.
**********NANDROID FIRST!!*********
Starting the flash:
1. Choose the "Wipe data/factory reset" then click "wipe cache partition"
2. Choose "install zip from sdcard" and choose "choose zip from sdcard"
3. Pick the zip file with the CM6 make sure it completes and the installer confirms that it is complete.
4. Reboot phone. This might take more then 5 mins on the initial boot, when it boots up all the way and everything has loaded, do one more reboot to clear out the cache from the initial boot and you are good to go
**If this doesnt work for you, follow step one, select a DIFFERENT ROM, reboot, then reboot into recovery, then wipe again, and flash back CM6.
I tried this, I already had Rom Manager installed but checked to make sure it was all up to date, flashed it to 2.5.0.1 and rebooted to recovery. I wiped the data and cache and installed the CM6 and rebooted with teh same results of it being stuck at the HTC screen and logcat showed it cycling through the same actions over and over, I then tried to just reboot it and it did same thing. I then wiped and installed a different ROM (the Damage Control one) and it worked fine got all the way booted up. I then rebooted to the recovery manager again, wiped and reinstalled with the CM6and had the same results as the first time. out of curiosity I even tried installing the damage control and then installed CM6 without the wipe and it still did not work.
adrazar said:
I tried this, I already had Rom Manager installed but checked to make sure it was all up to date, flashed it to 2.5.0.1 and rebooted to recovery. I wiped the data and cache and installed the CM6 and rebooted with teh same results of it being stuck at the HTC screen and logcat showed it cycling through the same actions over and over, I then tried to just reboot it and it did same thing. I then wiped and installed a different ROM (the Damage Control one) and it worked fine got all the way booted up. I then rebooted to the recovery manager again, wiped and reinstalled with the CM6and had the same results as the first time. out of curiosity I even tried installing the damage control and then installed CM6 without the wipe and it still did not work.
Click to expand...
Click to collapse
Find a new download of CM6, the one you downloaded was corrupt, try finding the thread, its in Development so find the extreme blue or redglass version.
I tried both the Extremely Blue CM6 Build (EXTBLUE_09NOV.zip) and the Red Glass CM6 Build (REDGLASS_09NOV.zip) that I got from the development area, a poste named
[ROM] (UPDATED 09-NOV) FroYo 2.2 - CM6 Extremely Blue, BlackMod, Red, Purple, Vanilla
the results as far as it looks are exactly the same as when I tried the other ROMs. I know two lines that kinda stand out to me in the endlessly repeating messages I get from logcat are:
E/dalvikvm( 326): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 326): Unable to process classpath element '/system/framework/framework.jar'
I'm not fully sure if these are the issue or if it is just random information about it failing to load the ROMs.
Does anyone know what those error messages could be caused by or a way to get around this issue?
adrazar said:
I tried both the Extremely Blue CM6 Build (EXTBLUE_09NOV.zip) and the Red Glass CM6 Build (REDGLASS_09NOV.zip) that I got from the development area, a poste named
[ROM] (UPDATED 09-NOV) FroYo 2.2 - CM6 Extremely Blue, BlackMod, Red, Purple, Vanilla
the results as far as it looks are exactly the same as when I tried the other ROMs. I know two lines that kinda stand out to me in the endlessly repeating messages I get from logcat are:
E/dalvikvm( 326): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 326): Unable to process classpath element '/system/framework/framework.jar'
I'm not fully sure if these are the issue or if it is just random information about it failing to load the ROMs.
Click to expand...
Click to collapse
adrazar said:
Does anyone know what those error messages could be caused by or a way to get around this issue?
Click to expand...
Click to collapse
What recovery are you using?
I use Rom Manager (clockwork mod) for installing the ROMs and its currently flashed to version 2.5.0.1 to recover my phone to the way it was before I flashed to to the cyanogenmod I use nandroid
adrazar said:
I use Rom Manager (clockwork mod) for installing the ROMs and its currently flashed to version 2.5.0.1 to recover my phone to the way it was before I flashed to to the cyanogenmod I use nandroid
Click to expand...
Click to collapse
That's probably the problem, try the 1.7 Darch RA, much better IMHO
Also ive noticed sometimes when I download a rom onto my computer for some reason it doesnt download the whole file correctly. So just make sure that when you download your rom to your computer the the size of the file is correct.If the rom is 50 mb make sure your download is the same.
I found a post that I believe I got that one from (RA-Darchstar.img) but it is an img file and i am having trouble getting that to install. i found another post elsewhere telling me to use commands from the SDK, it said to use
cd C:\android-sdk-windows\tools
adb devices
adb shell
flash_image recovery /sdcard/RA-Darchstar.img
exit
adb shell reboot recovery
which seems like it should work however when I do the flash_image recovery /sdcard/RA-Darchstar.img it tells me that the flash_image cannot be found. is this the wrong command line? and i do have the file on my phone's SD card in the root directory. or is there another way to get the 1.7 Darch RA?
never mind on my last question I figured it out, I wasn't in the Recovery program I already had when trying to do it. I got the 1.7 Darch RA on and working then tried to flash some of the ROMs again and every one of them failed with the same logcat errors as before.
Try backing up ur SD then taking out ur SD and formatting it on ur CPU then put it back in ur phone and format it threw the recovery I have a 28 MB swap and the rest for the system them go to ext and upgrade/update ur ext from ext2 to ext3 then try and flash CM6.1 hope this helps good luck.
Root-Hack-Mod-Always™
I formatted my card via the computer, formatted everything that RA-Darchstar will let me format, I then set up the partitions and upgraded to ext3, and then copped the CM6.1 to the phone and installed it (also tried EXTBLUE_09NOV). the end result was the same as each other time I have tried to install any of them CM6 ROMs.
Ok I ended up getting it to work by following some of the things I read on
http://forum.cyanogenmod.com/topic/...-cm-build-but-cm-6-nightly-tests/page__st__20
the part where they told this other person to extract the framework.jar to the PC and point adb to it.
Hi Everyone,
Sorry for this long-winded post. I've spent hours reading posts here, AndroidCentral and AndroidTablets.net forums, but have not found answers that work for me.
I hope someone can sort out the mess I've created on my rooted 1.1 Nook. Everything worked for 4-5 weeks after I rooted with Decad3nce method until...
A few days ago I decided to try 1.1G kernel. Read many threads about issues with Root Manager/ CWM; 3.0.0.5/3.0.0.6/SD CWM/EMMC CWM/Nook/Nook (old). When I booted into CWM, the version was 3.0.0.5. If I tried flashing CWM through Rom Manager, it said it 'flashed' 3.0.0.6 (tried both "Nook" and "Nook(old)"), but it never changed version of CWM I booted into. I also tried nemiths' "[RECOVERY] Official CWM 3.0.0.6 Update [BROKEN] (new fix soon!)" method to flash 3.0.0.6, but "adb shell busybox" always gave a 'can't get root' type error, so I gave up on that. I ended up using my current CWM to flash 1.1G kernel, and it worked very well. So I ignored the the CWM issues.
Then, I decided to try rookie1's dual-boot method so I could try out Honeycomb. I could never get 'prep_dualboot' zip to flash. It always gave an 'error in zip (status 0)'. His thread showed a few others getting same error, but none of the fixes given worked for me. I re-flashed that zip and ran the 'un-dualboot' zip many times with same result. I then found a "EMMC_CWM_3.0.0.6" zip and flashed that with my CWM. That actually gave me 3.0.0.6 CWM, but flashing dualboot still didn't work. I also again un-dualbooted, wipe cache partition, wipe dalvik cache, fix permissions with same result. So I gave up on that for now.
Then this morning, I found Market updates and downloads don't work anymore. It says 'about to download', then shows the arrows in status bar and nothing else happens. Saw threads regarding this issue and tried clearing Market cache and wiping whatever I could in CWM. Nothing I've found has helped so far.
As a side note in Rom Manager, "Recovery" section now shows 3.0.0.5 (before it wanted to flash 3.0.0.6). Tried flashing 3.0.0.5 there, but it doesn't seem to do anything (same as when it tried to flash 3.0.0.6). I can't understand the logic in Rom Manager. I also have Fascinate phone and RM has issues on that phone also.
I do have CWM backups and Titanium backups of all my stuff, so at worst I can do those. Looking for possibly easier way to get back to 'normal' so Market works and I can download the 'dual boot' zip and be happy again.
Some additional questions I have:
1) I saw in Decad3nce post that he left out 'root' for busybox in an early release, so that may be why mine won't work. I know I had used busybox before, but that may have been on earlier rooted 1.0.1. Is there a way to fix my current busybox without re-rooting?
2) What is the correct CWM I should use for 1.1 and will let me flash dual-boot zip? Also, where can I download it from and how can I replace the one I have?
3) I have saved my SD card to my computer many times and then re-formated it on the Nook. Is there some partition on it that format isn't cleaning that may contain some CWM image(s) causing at least some of my headaches?
Thanks in advance to anyone that can help with these issues. I may have tried a few other 'fixes' that I've since forgotten in the 5 hours last night trying to setup dual boot and quick hour this morning before work trying to sort out Market. Sorry (in advance) if you suggest something and I then say I tried it already. Possibly, just doing all the fixes I've tried previously in the correct sequence is what I need.
I seem to back to where I was before 'bad' versions of CWM skewered Market on me.
1) busybox: found that I just had to 'chmod 755' on my /system/xbin/busybox.
2) Saw that nemith posted a 3.0.0.9 version of CWM. Flashed that using his manual method. Didn't flash his kernel. Rebooted.
3) Tried clearing Market cache and didn't help. Wiped partition cache in CWM (or possibly Dalvik cache, not sure now...was going to do both but rebooted by mistake). After reboot, Market is working again.
Not sure if any of these affected Market, but I also unchecked/checked "Allow Non-Market Apps" and Unchecked/Checked "USB Debugging" and Unchecked "Auto Mount" in Settings.
Can't post in Dev area, so hope some there having same issue as me Market see this.
Now, gonna try the dual-boot again.
Alas, still getting (status 0) error flashing dual boot prep zip. Project for another night.
Sent from my LogicPD Zoom2 using XDA App
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
jhoward88 said:
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
Click to expand...
Click to collapse
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
vinal said:
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
Click to expand...
Click to collapse
No luck getting this to work
vinal said:
No luck getting this to work
Click to expand...
Click to collapse
Got a suggestion from Rookie1 to reformat my media partition. Prep now succeeded!
newfs_msdos -F 32 -L media /dev/block/mmcblk0p8
***Nook Colors manufactured after May 2011 shipped with a different partition scheme, see post 2 for information about it, or just go ahead with the guide since it doesn't affect much! You can identify these nooks as they have a blue dot sticker on the box***
A gentle reminder, this thread should only be for discussion related to the guide itself. Any CM7/10 related issues should be discussed in the appropriate threads either in General or the Development forum. Thanks!
On with the good stuff:
Prologue
This guide is intended to take you through the (mostly windows-based) steps needed to replace your internal nook color rom with CM7/CM9, gapps and clockworkmod or TWRP recovery all on EMMC. This will work coming from any previous rom, including the latest stock software (excluding dual boot set ups, not supporting that here), no previous rooting is needed for a new nook, however don't forget to boot stock and register the device before flashing to CM7/10.
At this point in CM7 development I am recommending installing a CM7.2 build by mrg666 from this thread or an official nightly/stable 7.2 directly from CyanogenMod: http://get.cm/?device=encore
CM10 is based on Android 4.1 (Jellybean) and builds can be found here: http://get.cm/?device=encore or mirrored here: http://techerrata.com/browse/cm/encore/nightly
If you want to run CM7/10 from the sdcard.. you're in the wrong place! Go check out verygreen's thread here for CM7 or here for CM10.
ALWAYS check the md5 hash for the files you are downloading to make sure you don't have corrupted files. This is a great windows utility to do that: http://code.kliu.org/hashcheck/
On with the guide:
Download 1gb TWRP image from here OR 1gb CWM 3.2.0.1 sdcard image from here. MD5 of .zip: 1319739d33642ed860e8044c3d55aa56. (I made this based on work in this thread. credit: to cmstlist and DizzyDen, and kevank for hosting). You really only need the 1gb image for this guide, no matter what the size of your card is. A smaller image will burn faster, and when you're done with the guide you can reformat the card anyway.
Extract the twrp or clockworkmod .img (if you can't open the file use 7zip)and burn to sdcard using win32diskimager (free). These apps will need to be "run as administrator." If you're not sure how to do this see step 3 here. ***Some internal laptop/desktop readers will not work to do this, you may need an external USB reader if you run into problems.***
While that's burning:
Download CM7 or CM10 from the links above.
Download either CWM 3.2.0.1 flashable .zip from here or TWRP 2.x flashable zip from here.
For CM7 -Download the latest gapps gingerbread needed for market/google services) from http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
For CM10 download gapps-jb-20121011-signed.zip from here or here
Once your sdcard is done, copy all those files to the sdcard - DO NOT unzip them
Power off your nook. Put the sdcard in, and power on, the nook will boot from sdcard into TWRP or clockworkmod depeding on which you used. TWRP is touch based and easy to use. Navigate in CWM using the vol up/down keys, N button to accept, power button to go back.
Optional: At this point if you want to make a backup of your current EMMC rom (stock or whatever else you're running) you can. Just go to backup.
Go back and navigate to Install .zip from sdcard/Choose .zip
Flash the files in this order:
1. cm .zip
2. gapps
3. Clockworkmod or TWRP .zip
Once you've flashed the files; in the clockworkmod main menu select "wipe data/factory reset" or in TWRP choose factory reset from the wipe menu.
Go back to the main menu, remove the sdcard
Format the sdcard in your computer as fat32 (or use another sdcard) and put it back in the nook and then press reboot system. (CM7 requires the use of an sdcard for storage - thanks pmilford for the tip)
Once you boot into CM7/10, you'll be presented with a welcome screen and you can add your google acct. You need to have wifi access here (obviously..) so hit menu on the status bar and you can set up wifi.
DONE!
Epilogue:
Now you can format the sdcard to use as a storage card in your nook.
To boot into recovery in the future (in order to update to a newer cm7 build/new kernel or make backups) simply hold down power and then choose reboot - recovery from the menu.
If you want to *gasp* restore to stock 1.2.0 flash nemith's stock image (update-nc-stock-1.2-signed.zip) from here using a recovery sdcard.
In CM7: For those looking to get a honeycomb feel to their Nook, I'd recommend this theme. Download the .apk and install it with file manager (or another of your choice), then go to the Theme Chooser app and scroll all the way left and select the theme (name/picture is broken but theme works). Once you've applied it, reboot. (Credits mad-murdock, Bawb3, haxzamatic and joenathane)
In CM7: To set your CPU/Overclock options go to Menu-Settings-CyanogenMod Settings-Performance.
CM7 for the nook color includes mad-murdock's tablet tweaks, so be sure to set up your preferences in the tablet tweak settings also found in the CM settings menu. Some apps, or you, will hide the status bar (eg watching a full screen video) so I like to set "unhide key" to home so that the N button will show the status bar again.
If you're having market problems see this thread for fixes. (Thanks jalexishg)
Want to say thanks? Hit the thanks button below
For more information on CM7 and latest issues/fixes/workarounds please check out the Nightly discussion thread here.
For more information on CM10 and latest issues/fixes/workarounds please check out the Nightly user discussion thread here and the development thread here.
Updating to a newer nightly build
Download latest nightly from CM and put it on the sdcard that's in the nook. Easiest way is to either download it directly on the nook itself, or download on pc and use usb drive mode to copy it to the nook sdcard.
Reboot to recovery (from power menu)
Wipe cache
Install zip from sdcard, flash the new nightly .zip
Reboot
I will try to maintain this guide with new information when needed. If anyone has any comments/suggestions feel free to suggest them below or PM me.
For additional help or just Nook Color related chat join us in #nookcolor on Freenode IRC. (if you have no idea what IRC is click here)
Information for new nook partitions
B+N have made a change as to how they partition the internal storage space on the nook. New nooks are now shipping with new partitions and you can identify these as they have a blue sticker on the box.
Old partitions: 1GB for data (i.e. apps), 5GB for media (books/music/whatever else)
New partitions: 5GB for data, 1GB for media (if you need more media space you use your sdcard)
Clockworkmod 3.2.0.1 (released 6/5/11) is now able to flash roms on the new partition scheme, however you may prefer to restore the old partition method if you like more onboard space for your own files and don't need 5GB for data (apps)
Current options for installing CM7 on the newer partitioned nook are:
1) Just follow the guide above with cwm 3.2.0.1, keep 5GB /data and 1GB /media
2) Follow this guide http://forum.xda-developers.com/showthread.php?t=1094371 to repartition your nook into the older 1GB data/5GB media, and then go back to the top and follow my guide. If you want to repartition using the .zips in DeanGibson's thread, you can flash them using the CWM SD you make in steps 1+2 of my guide above, then go on and flash CM7.
Awesome! I was *just* starting to look for a guide for getting up to 3.0 now that school is done You rock! Perfect timing.
This needs to get pinned if it isn't! Thank you so much!
Can you include instructions how to revert to stock for those "just in case" moments?
Also, maybe include a step if a person wants to install tweaks?
detonate said:
This needs to get pinned if it isn't! Thank you so much!
Can you include instructions how to revert to stock for those "just in case" moments?
Also, maybe include a step if a person wants to install tweaks?
Click to expand...
Click to collapse
Added a link which covers that. Thanks.
goodwork.. and with the bot too.. now we dont have to search for links everytime a noob needs help!
Sent via Cyanogenmod7 Encore RC4 n37/Tapatalk Pro
Mind if I post this guide over on Android Central forums? The one I have posted over there has gotten kind of unwieldy and I was wanting to start from scratch, but these are good!
KitF said:
Mind if I post this guide over on Android Central forums? The one I have posted over there has gotten kind of unwieldy and I was wanting to start from scratch, but these are good!
Click to expand...
Click to collapse
Go for it
Thanks for the clear and concise step by steps. Running off SD right now but tagging just for the day when I decide to go eMMC.
eyeballer said:
DONE!
Click to expand...
Click to collapse
The link to Muffinworld.net does not work. Do you know of another place we can go?
swapdotavi said:
The link to Muffinworld.net does not work. Do you know of another place we can go?
Click to expand...
Click to collapse
Updated OP with a mediafire mirror for now.
Nice guide.
awesome clean strait forward guide! =D thanks!
So this updates to 2.3? I thought this CM7 image was for 3.0? Is there another one I can use to get the 3.0 features?
swapdotavi said:
So this updates to 2.3? I thought this CM7 image was for 3.0? Is there another one I can use to get the 3.0 features?
Click to expand...
Click to collapse
CM7 has always been 2.3, not sure where you read otherwise. There's some honeycomb ports available built from the sdk as source isn't out, feel free to try them, although IMO CM7 is the most stable rom for the nook.
I tried to install CM7 on my nook color and i didnt follow the proper method and instead saved the CM7 file to the root of my sd card and installed the zip through clockworkrecovery without wiping or cache and now im stuck at the android boot screen. It isnt the CM7 skateboard android boot but rather the plain android root boot screen. If anyone could help it would be helpful thank you! IM crying right now about it
ikryptic said:
I tried to install CM7 on my nook color and i didnt follow the proper method and instead saved the CM7 file to the root of my sd card and installed the zip through clockworkrecovery without wiping or cache and now im stuck at the android boot screen. It isnt the CM7 skateboard android boot but rather the plain android root boot screen. If anyone could help it would be helpful thank you! IM crying right now about it
Click to expand...
Click to collapse
This isn't really the place for this post, but if you go back to the first post and look under Epilogue no.4, there's a link to the restore thread.
I've been trying to make a backup of my froyo system in recovery and it keeps on saying that the /system cannot be mounted. Any help would be appreciated.
eyeballer said:
This isn't really the place for this post, but if you go back to the first post and look under Epilogue no.4, there's a link to the restore thread.
Click to expand...
Click to collapse
Thanks a lot!
I'm currently auto-nooted, which leaves the default Nook reader software intact. Will installing CM7 also leave the default Nook reader intact?
Hi all,
I've recently rooted my nook color. I installed CM7 through rom manager and it installed, etc and then when it boots up it stays stuck on the android screen with the android logo and rays.
Sorry, but I'm new to nook color and modding. Can anyone help?
Thanks,
Brett
bdws1975 said:
Hi all,
I've recently rooted my nook color. I installed CM7 through rom manager and it installed, etc and then when it boots up it stays stuck on the android screen with the android logo and rays.
Sorry, but I'm new to nook color and modding. Can anyone help?
Thanks,
Brett
Click to expand...
Click to collapse
Which version of CM7 did you install? Sounds to me like you installed a corrupt copy. Make sure the download is correct. If you can open the .zip file, then the file is OK.
Also, did you wipe cache partition before installing CM7? Then wipe Dalvik cache?
CM7 boot gets stuck
I had the same problem when i first installed cm7 on my nook, but for some miraculous and unknown (at least to me) reason, after i plugged it into my computer (while the boot screen was stuck) it booted up no problem. idk what causes it to happen, but plugging it into my computer made it get past the stalled boot.
Fwiw the android screen suggests the kernel has loaded. Are you able to capture a log w adb logcat?
Sent from my HTC Vision using XDA App
Did you wipe data/clear cache?
the android and rays sound like you rooted the stock right(autonooter)?
I had the same issue, i used the 8 fails boots to get to the CWR then wipe data and clear cache and tada boots up to CM7 correctly.
Hi all
I ended up tajing it back to stock, rerooting and flashing cm7 again. All is well now.
I believe i wiped the boot accidentally and thats what started it all.
Thanks for your help.
Brett
Sent from my HTC Desire HD using XDA Premium App
I updated my NC to run the latest CM7 release on the SD card. When I tried to add the latest Dalingrin OC kernel it appears to boot but doesn't get to the CM animation screen. Do I need to clear the cache before updating the kernel? Is this the correct way to do it? "rm -rf /data/dalvik-cache/*"? Will I loose any data or apps?
jmak10 said:
I updated my NC to run the latest CM7 release on the SD card. When I tried to add the latest Dalingrin OC kernel it appears to boot but doesn't get to the CM animation screen. Do I need to clear the cache before updating the kernel? Is this the correct way to do it? "rm -rf /data/dalvik-cache/*"? Will I loose any data or apps?
Click to expand...
Click to collapse
I had the same thing happen to me yesterday , and then realized that I had downloaded the wrong OC version - the emmc instead of the sd. I reflashed the CM7 build, then copied the correct uimage and all was well
Is factory reset recommended before flashing cm7?
sent from PinoyNook
wrdoss said:
I had the same thing happen to me yesterday , and then realized that I had downloaded the wrong OC version - the emmc instead of the sd. I reflashed the CM7 build, then copied the correct uimage and all was well
Click to expand...
Click to collapse
Thanks for the reply. I double checked it and I did download the latest SD version (SD-041811c) but it didn't work. I then tried the SD-040411 version and it worked fine. Note that I didn't clear the cache either time.
wrdoss said:
I had the same thing happen to me yesterday , and then realized that I had downloaded the wrong OC version - the emmc instead of the sd. I reflashed the CM7 build, then copied the correct uimage and all was well
Click to expand...
Click to collapse
Did you replace the uImage file from the 040411 version? Or the latest experimental build which is 041811C?
My CM7 was installed using verygreen's size agnostic installer, and all the while it was easy to install the OC kernels by just swapping uImage.
But 4/18C can't be installed by just swapping the uImage unlike all the previous kernels. If you do that it will hang just before the bootanimation appears.
Can anyone please explain how to install the 4/18C kernel to CM7 (nightly 41) running on SD card?
robot8 said:
Did you replace the uImage file from the 040411 version? Or the latest experimental build which is 041811C?
My CM7 was installed using verygreen's size agnostic installer, and all the while it was easy to install the OC kernels by just swapping uImage.
But 4/18C can't be installed by just swapping the uImage unlike all the previous kernels. If you do that it will hang just before the bootanimation appears.
Can anyone please explain how to install the 4/18C kernel to CM7 (nightly 41) running on SD card?
Click to expand...
Click to collapse
This is the exact same setup and problem that I experienced.
robot8 said:
Did you replace the uImage file from the 040411 version? Or the latest experimental build which is 041811C?
My CM7 was installed using verygreen's size agnostic installer, and all the while it was easy to install the OC kernels by just swapping uImage.
But 4/18C can't be installed by just swapping the uImage unlike all the previous kernels. If you do that it will hang just before the bootanimation appears.
Can anyone please explain how to install the 4/18C kernel to CM7 (nightly 41) running on SD card?
Click to expand...
Click to collapse
Have you tried posting this issue in the development forum?
Yes I did, and it seems there's no easy way. Need to install the SDK and then adb push system from the extracted zip file then swap uImage.
edit: not that it's all that difficult but compared to just swapping uImage previously, well I'll probably wait a bit for the final update. Seems to be some issues with wi-fi.
edit:
Well I couldn't wait so I went ahead and popped 4/18C in. No issues so far.
robot8 said:
Yes I did, and it seems there's no easy way. Need to install the SDK and then adb push system from the extracted zip file then swap uImage.
Click to expand...
Click to collapse
Well that is unfortunate because you have to reinstall the OC kernal every time you install a new CM7 version.
I think I am going to stay with the latest CM7 nightly build and the SD-040411 OC kernel. I ran it some last night and it appeared stable and I didn't experience any of the video issues that people were reporting.
jmak10 said:
Well that is unfortunate because you have to reinstall the OC kernal every time you install a new CM7 release.
Click to expand...
Click to collapse
All this while when you update CM7 you'd need to reinstall the OC kernel, but it was way easy as you just needed to swap uImage. But not with the new test kernels.
Correct me if I'm wrong but I suppose once it's finalized I suppose the system stuff will be merged with main CM7 and we'd be able to swap OC kernels just like before.
robot8 said:
All this while when you update CM7 you'd need to reinstall the OC kernel, but it was way easy as you just needed to swap uImage. But not with the new test kernels.
Correct me if I'm wrong but I suppose once it's finalized I suppose the system stuff will be merged with main CM7 and we'd be able to swap OC kernels just like before.
Click to expand...
Click to collapse
I don't have any idea what is being planned but I hope the developers make this as easy as it was before.
I'm in the same boat. I know wiping the cache will fix it but I'm just stuck again if I reboot.
I'm running CM7, I wiped system, data, cach, dalvik, and did a factory reset before flashing.
Right now I'm just making sure my batter never runs out because reboot = wipe cache and then waste my time restoring apps and settings