I followed [ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards and got to the installation of GApps. When I reboot the nook into recovery, it doesn't work(both through the key button combos and through the reboot into recovery option once its booted up)
Has anyone else had this issue? I've tried it several times and even with the OC kernels I can never get it into recovery.
Sorry i would have posted this in the dev section but I am fairly new.
Thanks,
extremepizza
If all else fails add a boot menu. It couldn't hurt anything.
Open the attached file and copy the uboot.bin onto the boot partition of your sd card AFTER BACKING UP THE UBOOT FILE THAT YOU FIND THERE. You will now have a boot menu that will let you choose to boot sd to recovery. It will be overwritten any time you flash but you can always reinstall it AFTER BACKING UP THE FILE ALREADY ON THE CARD. After you're done installing you can either leave the menu uboot in place or replace it with the original file that you backed up. So far it hasn't caused me any problems during installations.
Thanks j4mm3r for the super handy piece of code.
http://forum.xda-developers.com/showpost.php?p=11512863&postcount=1
I frequently have the same issue. The combination and timing that I found to work most of the time is below. This is when first using the CM7 SDCard image. If your device already boots with the green CM logo then this doesn't apply.
Press and hold the 'n' key
Press and hold the power key
Wait for Loading... to appear (or whatever it says in your version)
Count to 3 and release the power key
Count to 3 and release the 'n' key
Wait for the Linux Penguin to appear
toddz
irisclara said:
If all else fails add a boot menu. It couldn't hurt anything.
Open the attached file and copy the uboot.bin onto the boot partition of your sd card AFTER BACKING UP THE UBOOT FILE THAT YOU FIND THERE. You will now have a boot menu that will let you choose to boot sd to recovery. It will be overwritten any time you flash but you can always reinstall it AFTER BACKING UP THE FILE ALREADY ON THE CARD. After you're done installing you can either leave the menu uboot in place or replace it with the original file that you backed up. So far it hasn't caused me any problems during installations.
Thanks j4mm3r for the super handy piece of code.
http://forum.xda-developers.com/showpost.php?p=11512863&postcount=1
Click to expand...
Click to collapse
Maybe you can help me out with this:
I am using the boot menu program.
My NC currently has 7.0.3-encore-signed and I tried to do an update to one of the newer nightlies.
I placed the cm zip file in the boot directory on the sd card and then on the boot menu selected sd and recovery but all it does is hang. Am I doing something wrong? I really would like to update to the new 7.1.0-RC1-encore-signed.
What i found out was that the installer v1.3 has an issue when using the 7.0.3 stable release. I instead restarted the process but installed the latest nightly and now i can use recovery fine to install gapps and newer nightlies.
Thanks for the help though.
If you need to install gapps, just put the gapps file with the Rom image and it will be install at the same time. you don't need to boot into recovery again. Btw, Im using the installer v1.3 and 7.0.3 stable release after a long time playing with nightly builds. Since 136 build, it can't boot from sdcard anymore.
I updated to the 7.2 RC Kang via CWM, but now my Nook will only boot to CWM. I was already on a 7.2 beta and working fine. Flashed the newest release, cleared cache and dalvik, now all it will do is boot to CWM.
I have taken the SD card right out and its doing the same thing. I have the Cyanogen boot loader on there (shows Cy logo instead of "The Future...").
Appreciate any guidance.
bluevolume said:
I updated to the 7.2 RC Kang via CWM, but now my Nook will only boot to CWM. I was already on a 7.2 beta and working fine. Flashed the newest release, cleared cache and dalvik, now all it will do is boot to CWM.
I have taken the SD card right out and its doing the same thing. I have the Cyanogen boot loader on there (shows Cy logo instead of "The Future...").
Appreciate any guidance.
Click to expand...
Click to collapse
If it is booting to CWM recovery and not locking up, that means the 'boot to recovery' flag is set and is not clearing when you leave CWM like it should. Try doing some things in CWM before you exit, like wiping cache or something. And when you exit, exit by the menu, not just powering off.
You can also try using the boot menu to try to force you to emmc. Hold the n button while booting and when the boot menu comes up, pick emmc and normal and reboot.
Edit: You say you take the SD out and it does the same. Why would you expect it to be different? Are you running from SD? If so you should not be flashing things with CWM, that puts things on emmc. Or did you mean you take the bootable CWM SD out? You should always take that out after flashing to emmc. And if your already running CM7 from emmc, you should be flashing with the CWM on emmc, not a bootable CWM SD. I'm confused as to what you were doing and what your configuration was.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
If it is booting to CWM recovery and not locking up, that means the 'boot to recovery' flag is set and is not clearing when you leave CWM like it should. Try doing some things in CWM before you exit, like wiping cache or something. And when you exit, exit by the menu, not just powering off.
You can also try using the boot menu to try to force you to emmc. Hold the n button while booting and when the boot menu comes up, pick emmc and normal and reboot.
Edit: You say you take the SD out and it does the same. Why would you expect it to be different? Are you running from SD? If so you should not be flashing things with CWM, that puts things on emmc. Or did you mean you take the bootable CWM SD out? You should always take that out after flashing to emmc. And if your already running CM7 from emmc, you should be flashing with the CWM on emmc, not a bootable CWM SD. I'm confused as to what you were doing and what your configuration was.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
I took the SD card out as someone had suggested that in the ROM thread. No, it doesn't make sense that if would just start booting from the SD card when it wasn't before, but it eliminated a variable.
I have gone into the boot menu and checked that it is booting from emmc. I've even changed it to SD and back just to make sure it took.
bluevolume said:
I took the SD card out as someone had suggested that in the ROM thread. No, it doesn't make sense that if would just start booting from the SD card when it wasn't before, but it eliminated a variable.
I have gone into the boot menu and checked that it is booting from emmc. I've even changed it to SD and back just to make sure it took.
Click to expand...
Click to collapse
Then it is the set flag issue I mentioned in the first part of my post. Not sure how to get it cleared. Just exercising CWM? Try flashing something else. Gapps again maybe. It won't hurt to flash them twice.
Edit: btw, what version of CWM are you running?
Sent from my Nook Color running ICS and Tapatalk
CWM v3.2.0.1
I installed gapps again, same problem. Gremlins!
I had this problem, but the only way I found to fix it was to flash a stock recovery zip from CWM recovery SD card, then CM7 again
cmendonc2 said:
I had this problem, but the only way I found to fix it was to flash a stock recovery zip from CWM recovery SD card, then CM7 again
Click to expand...
Click to collapse
But in his case it is not locking up. It is cleanly rebooting to CWM. A little different scenario than yours.
leapinlar said:
But in his case it is not locking up. It is cleanly rebooting to CWM. A little different scenario than yours.
Click to expand...
Click to collapse
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
votinh said:
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
Click to expand...
Click to collapse
Yes, I've had CWM flashed into the emmc for a while. So I could use the boot menu utility to boot to CWM if needed.
BTW - this is the ROM i'm using: http://forum.xda-developers.com/showthread.php?t=1344873
votinh said:
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
Click to expand...
Click to collapse
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Edit: @bluevolume - a possible solution is to make a bootable CWM SD and boot to that. That may reset the flag when it exits.
Edit 2: I found where the recovery flag is stored on the nook. There is a separate partition (2) called /rom that stores basic information like your model number, date of manufacture, serial number, etc. Also there is a file named BCB which is usually an empty file. But if the word 'recovery' is written there properly, it will always boot into recovery. Recovery is supposed to write the empty file back when finished so that on next boot it boots normally to emmc. I'm not sure how much good this information is going to do you, but if you are proficient with adb, you can modify the file even if in recovery.
leapinlar said:
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Edit: @bluevolume - a possible solution is to make a bootable CWM SD and boot to that. That may reset the flag when it exits.
Edit 2: I found where the recovery flag is stored on the nook. There is a separate partition (2) called /rom that stores basic information like your model number, date of manufacture, serial number, etc. Also there is a file named BCB which is usually an empty file. But if the word 'recovery' is written there properly, it will always boot into recovery. Recovery is supposed to write the empty file back when finished so that on next boot it boots normally to emmc. I'm not sure how much good this information is going to do you, but if you are proficient with adb, you can modify the file even if in recovery.
Click to expand...
Click to collapse
That is good info, thank you. I have not been able to get ADB working in the past (i'm on Win 7 64); I think its a driver issue. I'll revisit that later today.
bluevolume said:
That is good info, thank you. I have not been able to get ADB working in the past (i'm on Win 7 64); I think its a driver issue.
Click to expand...
Click to collapse
If you can get adb working in CWM, this is what you want to do in at the dos prompt, one line at a time:
adb shell mount -t vfat /dev/block/mmcblk0p2 /rom
adb shell dd if=/dev/zero of=/rom/bcb bs=512 count=1
adb shell reboot
Edit: if you want help getting adb working this post may help:
http://forum.xda-developers.com/showthread.php?p=21665649
Edit2: I've been doing a lot of experimenting. It is not what's in the bcb file. It's what the file size is. If the file size is 512 bytes or larger it will boot to normal emmc. If it is smaller than 512 bytes or MISSING, it will boot to recovery. It could be yours is missing. But recovery is supposed to create a new big one if it is. Could be a permissions problem. If you get adb going you can fix that.
On a side note I was thinking it could be corrupted boot files causing this, but I purposely messed with them and it does not boot into recovery, it just hangs.
leapinlar said:
If you can get adb working in CWM, this is what you want to do in at the dos prompt, one line at a time:
adb shell mount -t vfat /dev/block/mmcblk0p2 /rom
adb shell dd if=/dev/zero of=/rom/bcb bs=512 count=1
adb shell reboot
Edit: if you want help getting adb working this post may help:
http://forum.xda-developers.com/showthread.php?p=21665649
Edit2: I've been doing a lot of experimenting. It is not what's in the bcb file. It's what the file size is. If the file size is 512 bytes or larger it will boot to normal emmc. If it is smaller than 512 bytes or MISSING, it will boot to recovery. It could be yours is missing. But recovery is supposed to create a new big one if it is. Could be a permissions problem. If you get adb going you can fix that.
On a side note I was thinking it could be corrupted boot files causing this, but I purposely messed with them and it does not boot into recovery, it just hangs.
Click to expand...
Click to collapse
Let me first thank you for your time and support on this; its people like you that make these forums such a great resource.
I'm not that comfortable with adb commands so I starting looking for other solutions. Since you mentioned that its the actual boot files that are missing/corrupted, I searched around and found this:
http://forum.xda-developers.com/showthread.php?t=958748
I loaded the RecoveryFix.zip on my SD card and flashed it with CWM. Rebooted, and I was back to the 'Future of reading..." boot logo, but it still went straight to CWM. So I flashed the ROM again (the ROM I listed earlier in the thread), wiped cache, fixed permissions. Rebooted, and the "Cyanogenmod" boot logo was back. And instead of going right to CWM, the screen was blank for quite a while then I saw the little Android guy skate by... And I'm back in business.
I know other people have had this problem and this seems like a pretty simple solution. I'm good at this point, and hopefully some other people will find this thread helpful.
bluevolume said:
Let me first thank you for your time and support on this; its people like you that make these forums such a great resource.
I know other people have had this problem and this seems like a pretty simple solution. I'm good at this point, and hopefully some other people will find this thread helpful.
Click to expand...
Click to collapse
The next step I was going suggest if you could not fix it was to flash a new CWM to your boot files. Good job finding that.
Glad you got it running. I learned a lot myself and maybe that info will help others.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Click to expand...
Click to collapse
Got it, thanks m8
That clears up my mind.
I had the same problem, followed the thread you found. Did the same thing, now I'm back in business too. Thanks!
Just wanted to say thanks for figuring this out! I was in a similar situation after downgrading from cm9 back to cm7. Installed CWM using recoveryfix_3.0.2.8.zip from the thread above, and was back up and running after a restore of a cwm backup. Headed on vacation tomorrow and the wife would have had my head for being such an FW... you're a lifesaver!
Ok I followed a walk through on a different blog (as requested by my friend who's phone it is). I unlocked the bootloader with no issues. I also installed CWM. Now I loaded a new ROM to flash on the external SD card. However when I boot into CWR it only reads the internal storage. I cant get it to read the external SD so I cant flash the new ROM. Any tips or suggestions? I can't get the phone to boot into anything right now.
Go fine romracers cwm are touch recovery are try twrp ..
You fine them in Development thread..
Which recovery are you using?
I wouldn't go for Touch recovery. It's easier to do something in error when using the touch screen.
Install the Romracer recovery from the following link. You can install from fastboot:
http://forum.xda-developers.com/showthread.php?t=1204500
I've got a NC running stock 1.4.3 that's stuck in a boot loop. I've tried everything to either (1) root it to CM7.2 or (2) restore stock Nook os, including trying to fix the partitions as suggested by leapinlar. I think the problem is that there is no eMMC recovery, so when I try to reboot to recovery to fix the partitions, I get bounced back into the bootloop. I tried installing CWM recovery to eMMC using a bootable microSD with CM7 and RomMgr premium, as well as using CWM with some of the eMMC recovery .zip files found in other posts, and it looks like it gets flashed, but when I then try to boot into recovery I get an error "Install Failed (with an icon of the NC and !). I was thinking of trying to flash recovery to eMMC using adb. When I boot with the CM7 microSD, I'm able to access adb from my desktop. Can't seem to find the right files or instructions on how to flash CWM recovery to eMMC using adb. Any suggestions?
judgerey said:
I've got a NC running stock 1.4.3 that's stuck in a boot loop. I've tried everything to either (1) root it to CM7.2 or (2) restore stock Nook os, including trying to fix the partitions as suggested by leapinlar. I think the problem is that there is no eMMC recovery, so when I try to reboot to recovery to fix the partitions, I get bounced back into the bootloop. I tried installing CWM recovery to eMMC using a bootable microSD with CM7 and RomMgr premium, as well as using CWM with some of the eMMC recovery .zip files found in other posts, and it looks like it gets flashed, but when I then try to boot into recovery I get an error "Install Failed (with an icon of the NC and !). I was thinking of trying to flash recovery to eMMC using adb. When I boot with the CM7 microSD, I'm able to access adb from my desktop. Can't seem to find the right files or instructions on how to flash CWM recovery to eMMC using adb. Any suggestions?
Click to expand...
Click to collapse
You need to get my bootable CWM card from my tips thread linked in my signature. Then you can flash a new 1.4.3 that I have also in my tips thread. I also have flashable CWM zips there to put CWM on emmc. And if that does not fix it run my partition repair zips using my CWM. ROM Manager does not always install the CWM to emmc properly.
Sent from my HD+ running CM10 on SD with XDA Premium
judgerey said:
I've got a NC running stock 1.4.3 that's stuck in a boot loop. I've tried everything to either (1) root it to CM7.2 or (2) restore stock Nook os, including trying to fix the partitions as suggested by leapinlar. I think the problem is that there is no eMMC recovery, so when I try to reboot to recovery to fix the partitions, I get bounced back into the bootloop. I tried installing CWM recovery to eMMC using a bootable microSD with CM7 and RomMgr premium, as well as using CWM with some of the eMMC recovery .zip files found in other posts, and it looks like it gets flashed, but when I then try to boot into recovery I get an error "Install Failed (with an icon of the NC and !). I was thinking of trying to flash recovery to eMMC using adb. When I boot with the CM7 microSD, I'm able to access adb from my desktop. Can't seem to find the right files or instructions on how to flash CWM recovery to eMMC using adb. Any suggestions?
Click to expand...
Click to collapse
You ever get it working? This is my underlying issue EXACTLY except I have working ADB when booted from SD card.
40Glock said:
You ever get it working? This is my underlying issue EXACTLY except I have working ADB when booted from SD card.
Click to expand...
Click to collapse
Nope. Never got it working.
Specs:
Nook Color Tablet bought off of ebay with CM10 on the internal memory (that "didn't work") and ClockworkMod Recovery v3.2.0.1
2gb bootable CM10 card
What i've done:
wiped the 2gb CM10 sd card.
Flashed internal memory (via the youtube tutorial) and put cm10 nightly from 03132013 and gapps
Installed netflix and hulu plus
Installed a blank 8gb sd card for apps and storage
So here's the problem. Last weekend I was watching a tv series on netflix. Drained the battery completely. Plugged it up for about two hours to recharge. Apparently When I plugged it up it decided to boot. >at this point it should be noted that the properly formated 8gb sdcard was in it, and not the bootable recovery sd card that was at the house<. When it booted it went straight into the ClockworkMod Recovery v3.2.0.1 menu. When I got back from the run we were on I tried rebooting it. It came up with the cyanoboot universal bootloader main screen, screen flashed and it went straight into the ClockworkMod Recovery v3.2.0.1 menu again. I tried rebooting several times. Same thing.
So tonight I got online, did a search, didn't find the answers i was looking for and settled on installing [ROM][JB 4.1.2][04MAR13 v1.20] SCHIZOID all-in-one (CM10+AOKP M1+PA 2.55). I flashed the /system, /data and /cache. Installed the new rom. Used the nook button + power to power it down, removed the boot card, and rebooted. Can you guess what it did? (see above).
So now i'm stuck. I DO NOT want to use a sd card to boot my nook. I want the OS in the main memory. Suggestions?
it should be noted, as i left this out of my OP, that I had tried to reflash CM10 back onto it. after that didn't work I tried the other rom. I've now tried reflashing CM10 and NOTHING is working.
vikingmedic said:
Specs:
Nook Color Tablet bought off of ebay with CM10 on the internal memory (that "didn't work") and ClockworkMod Recovery v3.2.0.1
2gb bootable CM10 card
What i've done:
wiped the 2gb CM10 sd card.
Flashed internal memory (via the youtube tutorial) and put cm10 nightly from 03132013 and gapps
Installed netflix and hulu plus
Installed a blank 8gb sd card for apps and storage
So here's the problem. Last weekend I was watching a tv series on netflix. Drained the battery completely. Plugged it up for about two hours to recharge. Apparently When I plugged it up it decided to boot. >at this point it should be noted that the properly formated 8gb sdcard was in it, and not the bootable recovery sd card that was at the house<. When it booted it went straight into the ClockworkMod Recovery v3.2.0.1 menu. When I got back from the run we were on I tried rebooting it. It came up with the cyanoboot universal bootloader main screen, screen flashed and it went straight into the ClockworkMod Recovery v3.2.0.1 menu again. I tried rebooting several times. Same thing.
So tonight I got online, did a search, didn't find the answers i was looking for and settled on installing [ROM][JB 4.1.2][04MAR13 v1.20] SCHIZOID all-in-one (CM10+AOKP M1+PA 2.55). I flashed the /system, /data and /cache. Installed the new rom. Used the nook button + power to power it down, removed the boot card, and rebooted. Can you guess what it did? (see above).
So now i'm stuck. I DO NOT want to use a sd card to boot my nook. I want the OS in the main memory. Suggestions?
Click to expand...
Click to collapse
You are in a recovery bootloop. Look at my NC Tips thread linked in my signature. See item A8 and A12. I suspect given your symptoms, you need to flash the romsrestore.zip file. It is trying to boot to stock recovery and repair itself.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
You are in a recovery bootloop. Look at my NC Tips thread linked in my signature. See item A8 and A12. I suspect given your symptoms, you need to flash the romsrestore.zip file. It is trying to boot to stock recovery and repair itself.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
flashed [romrestore-CWMflashable.zip - ] rebooted. same thing. straight back to the clockworkmod recovery menu.
created the CWM-5.5.0.4 bootable sd card and tried it that way. all that did was change the CWM menu blue instead of orange.
vikingmedic said:
flashed [romrestore-CWMflashable.zip - ] rebooted. same thing. straight back to the clockworkmod recovery menu.
created the CWM-5.5.0.4 bootable sd card and tried it that way. all that did was change the CWM menu blue instead of orange.
Click to expand...
Click to collapse
so here's a new one for you. I was going through the three finger salute method and screwed it up. low and behold I actually got to the cyanogenmod circle screen. Think we might be good to go.
vikingmedic said:
flashed [romrestore-CWMflashable.zip - ] rebooted. same thing. straight back to the clockworkmod recovery menu.
created the CWM-5.5.0.4 bootable sd card and tried it that way. all that did was change the CWM menu blue instead of orange.
Click to expand...
Click to collapse
I suggest you flash my zip for putting stock recovery back on the system. Then boot and let it do what it had been trying to do, whatever that is. It could be trying to do the 8 failed boot reset.Then when it has finished, put a new rom on it.
Either that or put stock on it (A15) and it will put everything back to virgin. Then you can put your own rom on it.
Sent from my Nook HD+ running CM10 on Hybrid SD