Database Users

[Q] Recovery installed to EMMC instead of SD

I did a search for 'boot recovery' and read a few thread going back to May, but none of them seem to quite fit what happened to me. If I have missed the instructions, please link to them and I'll check it out.
First the setup:
My NC is stock 1.2 on the EMMC. I then followed the instructions in the Size-agnostic SD Card image and CM7 installer for SD Cards. The only step I cheated on was copying both update-cm-7.0.3-encore-signed.zip and gapps-gb-20110613-signed.zip to the SD card after the card was imaged. The rom and gapps installed and work as intended.
Next it was my intent to install update-CM7-dalingrin-OC-sd-063011.zip for a little speed boost. But I couldn't get it to boot into recovery with the various hold this button timings and choosing reboot from the power button options. I then went into ROM Manager and Flash ClockworkMod recovery, which flashed 3.2.01 to the EMMC. I have confirmed that by removing my CM7 SD card and successfully booting to recovery.
So now what? I would have thought the Rom Manager should have flashed the CWM recovery to the SD card, as that is what I had booted from. How can I uninstall the CWM from EMMC and force it to installed to the SD card?
Thanks,
Zhin

Did you just say up there "which flashed 3.2.01 to the EMMC"? why did you expect it "should have flashed the CWM recovery to the SD card"?
Anyway, if you want to run from uSD, then anything related to eMMC or files that have "emmc" on file name, then ignore, discard it.
In your case, after you booted into recovery (using power button, and its options), you should be all set.
I don't now what makes you went into ROM Manager and flashed it

votinh said:
Did you just say up there "which flashed 3.2.01 to the EMMC"? why did you expect it "should have flashed the CWM recovery to the SD card"?
Click to expand...
Click to collapse
Because I thought that when you flashed a rom to the SD card and booted off the SD card it was treated the SD card as the 'local disk'. With the EMMC just being seen as additional storage when you where running off the SD. So when I booted from the SD card and opened Rom Manager while running from the SD card, I should think it would have flashed the CWM to the SD card.
votinh said:
Anyway, if you want to run from uSD, then anything related to eMMC or files that have "emmc" on file name, then ignore, discard it.
Click to expand...
Click to collapse
I didn't say anything about using files that said emmc in the OP.
votinh said:
In your case, after you booted into recovery (using power button, and its options), you should be all set.
Click to expand...
Click to collapse
The only way I can get to recovery is to remove the SD. How can I make sure to install update-CM7-dalingrin-OC-sd-063011.zip to the SD card? Can the SD card be put back in after booting to recovery?
votinh said:
I don't now what makes you went into ROM Manager and flashed it
Click to expand...
Click to collapse
When it wouldn't boot into recovery after the clean install from my OP, I started to look for other options. When I launched Rom Manager it said there was no recovery option installed.
-Zhin

Zhindel said:
I then went into ROM Manager and Flash ClockworkMod recovery, which flashed 3.2.01 to the EMMC. I have confirmed that by removing my CM7 SD card and successfully booting to recovery.
So now what? I would have thought the Rom Manager should have flashed the CWM recovery to the SD card, as that is what I had booted from. How can I uninstall the CWM from EMMC and force it to installed to the SD card?
Thanks,
Zhin
Click to expand...
Click to collapse
Rom Manager is useless for SD installs; just don't run it. It's not like most Android apps that only look at filesystem names (/sdcard, /emmc, etc), it uses the hardware device names (/dev/block/...) for its manipulations and pretty much assumes an emmc install.
Having CWM on emmc isn't a problem, it won't interfere with running the stock NC software from an emmc boot. I haven't run stock in forever, I don't know what they had for a recovery boot, but there are "restore to stock" threads that will show you how to find the parts if you want to put it back.
What were you intending to do by installing CWM? The recovery that comes with the SD install is what flashes new builds for you, so you don't want to mess with it. You can install CWM on the SD as an alternate boot instead of a recovery (uAltImg and uAltRam instead of uRecImg and uRecRam) and use the u-boot that comes with recent CM7 builds to boot it if you want to play with it.

stolenmoment said:
Rom Manager is useless for SD installs; just don't run it. It's not like most Android apps that only look at filesystem names (/sdcard, /emmc, etc), it uses the hardware device names (/dev/block/...) for its manipulations and pretty much assumes an emmc install.
Click to expand...
Click to collapse
Ahhh ha! That makes sense. I never knew that.
stolenmoment said:
Having CWM on emmc isn't a problem, it won't interfere with running the stock NC software from an emmc boot. I haven't run stock in forever, I don't know what they had for a recovery boot, but there are "restore to stock" threads that will show you how to find the parts if you want to put it back.
Click to expand...
Click to collapse
I can restore to stock easily enough. I have an image of the stock install for easy recover for just these circumstances.
stolenmoment said:
What were you intending to do by installing CWM? The recovery that comes with the SD install is what flashes new builds for you, so you don't want to mess with it. You can install CWM on the SD as an alternate boot instead of a recovery (uAltImg and uAltRam instead of uRecImg and uRecRam) and use the u-boot that comes with recent CM7 builds to boot it if you want to play with it.
Click to expand...
Click to collapse
The install instructions for the dalingrin kernels said they were CWM flashable. I wasn't going to get too fancy, but maybe I should look at some of the alternate boot options.
Thanks!
Zhin

I accidentally did the same exact thing before I realized VG included his own recovery on the SD. From what I've read, to uninstall CMW from the emmc, you need to create a separate CMW SD and do a full restore to stock.
http://forum.xda-developers.com/showthread.php?t=931720
As for putting CMW on the SD, IDK. VeryGreen's method of just appending "update-" to rom file names and placing them on the root of the SD has worked for me.

I didn't say anything about using files that said emmc in the OP.
Click to expand...
Click to collapse
Because you were confusing as indicated in your thread, I was just suggesting eliminating anything about "emmc" if you intended to run off uSD. I did not say you did it, I just recommend it. For instance, Dalingrin OC kernel, there are several versions out there and anything with "emmc", then you should ignore them. That's all
I can restore to stock easily enough. I have an image of the stock install for easy recover for just these circumstances.
Click to expand...
Click to collapse
I assume you are all set.
Am I right? or still need help

I did the same thing and am too wondering how to remove it for warranty purposes. My Nook came w/ 1.2...does that mean 'd have to restore to stock 1.0.1 and then upgrade to 1.2?

dna59 said:
I did the same thing and am too wondering how to remove it for warranty purposes. My Nook came w/ 1.2...does that mean 'd have to restore to stock 1.0.1 and then upgrade to 1.2?
Click to expand...
Click to collapse
Get one of those 2
http://forum.xda-developers.com/showthread.php?t=1050520

[Q] where to get original NC recovery?

I'm trying to update my original NC to 1.4.1 and when it boots to
recovery to install, it ends up in CWM ?!? How do I restore original
emmc recovery to emmc, so the update zip will run?
My card has Nookie Froyo (4 partitions) and
other than the accidental CWM on emmc its
vanilla.
I'm used to HTC's hboot's put a specially named
zip file in the external cards root to flash a new
recovery, (or fastboot flash recovery recovery.img).
How is it done for NC?
thanks

Without using an sdcard....
this may help. http://forum.xda-developers.com/showthread.php?t=1461172

[Q] Can only boot to CWM

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!

[Q] Need Recovery Help!

OK, so I flashed one of the new leaked ICS stock ROMs and it appears that everything is ok. I'm digging all of the features including the panoramic camera. I decide that I want to put on Taboonay for a little flavor. I try to boot into recovery and this is what I get:
Erasing cache before SD update
SD update cmd: recovery
--update_Package=SDCARD:update.zip
Booting recovery kernel image
(IN RED) Recovery verified failed
Yes, I tried to flash a recovery image through the ACER recovery install and the ROM Manager. Both of them flashed an image with no problem, until I actually tried to flash an image.
My question is this: How do I flash a recovery image if my bootloader is busted?
I do have ADB access , so it there a way I can copy a recovery image file directly onto the A500?
I appreciate the help!

xodus1914 said:
OK, so I flashed one of the new leaked ICS stock ROMs and it appears that everything is ok. I'm digging all of the features including the panoramic camera. I decide that I want to put on Taboonay for a little flavor. I try to boot into recovery and this is what I get:
Erasing cache before SD update
SD update cmd: recovery
--update_Package=SDCARD:update.zip
Booting recovery kernel image
(IN RED) Recovery verified failed
Yes, I tried to flash a recovery image through the ACER recovery install and the ROM Manager. Both of them flashed an image with no problem, until I actually tried to flash an image.
My question is this: How do I flash a recovery image if my bootloader is busted?
I do have ADB access , so it there a way I can copy a recovery image file directly onto the A500?
I appreciate the help!
Click to expand...
Click to collapse
Well, not sure if I can get you up and running. This is going to depend on if you followed traditional installation instructions that are posted on every thread that contains a Rom.
But first, let's cover where you went wrong. And that would probably be when you went back to Recovery. It seems, you didn't hit Vol - and PWR, but instead selected Vol + and PWR. And as such, it tried to run an update.zip file, which is a no-no. This resulted in a corrupted image.
Secondly, Rom Manager is a phone app. This will in most cases, bork your tab.
First, I would try Acer Installer (newest version) and try to install RA Recovery. If you were using CWM before, you probably can't flash it again.
If that doesn't work, then you will have to roll back from ICS, and you will need your original UID number. Hopefully you wrote this down somewhere. If you were using RA Recovery, you will find the UID number in the UID.txt on your SD Card in the Recovery folder (if you made a system backup before flashing ICS roms). If you were using CWM, well, it might be buried in one of the .img files in the clockwork folder (again, if you made a backup before flashing ICS). You will have to de-compile the image files to find it (hopefully).
If your ADB seems to be working, you may want to push the RA Recovery;
http://forum.xda-developers.com/showthread.php?t=1459821
If you have your original UID number, then you may want to try this;
http://forum.xda-developers.com/showthread.php?t=1522384
or this;
http://forum.xda-developers.com/showthread.php?t=1516012
Hope you get it going. From what I have seen, mostly when the people lose their recovery, they were using CWM. Haven't heard of any losing it when using RA Recovery. But anyhow, use Acer Recovery first, and try the RA Recovery.

Flash CWM Recovery using ADB to bootlooped NC running stock 1.4.3

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.