Database Users

Booting into clockwork recovery

I don't know how I did it, but everyone else is trying to boot into Clockwork Recovery mode successfully...and the whole pull the battery mode doesn't work 100% of the time...buuuut...I CANT STOP!
I can't stop booting into Clockwork. Every time I turn my phone on, it boots into the Clockwork Recovery, without fault. I've rebooted almost 30 times now and every time its done the same thing. Once it reboots into recovery, it will allow me to reboot the phone and then it boots normally. I really want to fix it, its annoying. The phone still works without any issues, its just really annoying that I have to sit there and watch it boot up to get it to the actual phone.
I don't want to unroot and start over with it all because I've made so many small changes to the phone and made it my own.
Sooo, pleeeeeeeeeease anyone with any info or fixes; let me know!

Mine did that too so I flashed the SBF and started over from scratch. I am afraid to try the D2 Bootstrap again for that reason. For now I can live with it. Did you find a fix yet?
How does this work?
When your device boots up, there is a init.rc script in your boot image that runs various components found in /system. The Droid X recovery bootstrap mimics the "logwrapper" binary. The hijacker then looks for "/data/.recovery_mode", and if it finds it, it unmounts /system to prevent android from starting. It then starts up recovery instead.
That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?

Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.

kwheel596 said:
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
Click to expand...
Click to collapse
Glad it worked. It happened to me too and I just used the sbf file to restore everything. Did you use any mount adb commands before you had that problem?

To be honest I have no idea, I've had android phones for a while so I was just flying through the commands and don't remember what was typed

Unable to remove "ClockworkMod Recovery"
[/QUOTE]That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?[/QUOTE]
So, I looked throughout my sd card, and have been unable to find any ".recover_mode" file.. I still get the ClockworkMod Recover screen EVERY time I reboot my device.. I have rooted and unrooted multiple times to try and figure out this problem, as well as searched through this website for answers.. I am not finding any.. HELP!?
Ultimately, I would like to just restore my phone to factory so I can pass it on to a friend..
Thanks in advance for everyone's help!
Chenoaem

Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!

enkrypt3d said:
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
Click to expand...
Click to collapse
nevermind... forgot to hit the search key! doh!

[Q] MyTouch 4g: Multiple problems... PLEASE help.

Okay, I've searched and searched and no one seems to have the specific problem that I'm having with my phone, so I'm taking to the forums myself. I've been rooting since the G1, I know how to adb push things, I have used google and multiple forums to try to fix this problem. So here goes, anyone that can help I thank you in advance.
1-My phone, like some other MT4G users, reboots itself each time it's plugged in. Initially I thought this was because I was using a Kindle cord to plug it into the pc, so I bought an MT4G usb cable from tmobile, and still it boot loops (just the first white screen for maybe 4 seconds, then black then again and again). The only way to charge it is to let it start boot looping, take the battery out, turn it on, and if I'm lucky enough that it begins to boot up correctly I plug it in mid boot. If I wait til it's fulled loaded it just starts rebooting again.
2-It will not at all from any angle go into Recovery mode. If I try to go to recovery from Rom Manager, or from the screen you get when holding power and lower volume key or by flashing a rom through Rom Manager, it just boot loops just like mentioned above, until I pull the battery for a while (it is currently sitting next to me with the battery out) and then put it back in.
3-If by chance it's on, and plugged into the computer, it is not at all recognized. Ever. While it's booting up my computer finds something, but doesn't know what it is, and doesn't allow me to view any folders on the SD card. Yes I've installed the HTC drivers file. I've adb'ed things to this phone before, now it says device not found. I don't know when it stopped being recognized...
4-I've even tried to fastboot something over to it, but to no avail, still not found.
If I try to do a factory reset, it boot loops. If I sneeze it boot loops.... I don't know what to do, and if I trade it in under warranty, I have to reset it to stock rom, or they're going to charge me for a new phone. Any ideas!?
I have Cyanogen mod 7 on here.

have you tried a fastboot wipe? or have you tried to reboot to recovery from adb?

First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Edit: I didn't realize you tried to enter recovery, oops. But yeah try what the buy above me said. Try re-installing the latest CWM recovery, if that still fails then try heading into there via ADB.

mackster248 said:
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Click to expand...
Click to collapse
I second that, flashing ROMs from ROM Manager a terrible idea.

Well...if all else fails and if you are really thinking about returning it and still under warranty...few seconds in the microwave method should work just fine. They wont be able to see that its rooted if the phone wouldn't turn on, would they???

glimmer of hope...
So by the grace of god I did get it flashed back to unrooted, stock 2.2 by putting it as pd15img.zip on my sd card and going into bootloader. Once that was done I thought I would be out of the woods... I even plugged it in last night and no boot loop!! but this morning I unpllugged it (and I'm using a tmobile cable for the phone attached to my pc) and here it sits, next to me again with the battery out of it because everytime I try to turn it on (for over 40 minutes now) it boot loops to that stupid white screen (that is honestly driving me insane at this point). I know that it isn't rooted (because I dl'ed rom manager and it won't let me do anything without being rooted) so do we think that I'm safe to go to the store today to request a new one be sent? Thoughts? And thanks for the help thus far!

yeah I would send that back

Bad emmc chip? I'm sorry man, that's a terrible story.
Sent from my HTC Glacier using XDA App

boot loops upon reboot, NC 1.2, MN root

I have a NC 1.2. I am able to root using a CWM 3.0.2.8 Msd card with Manual Nooter no problem. The problem occurs when I shut it off and then reboot. It gets to the part where the words "Nook Color" start scrolling across the screen. "Nook Color" completes one time successfully and when it starts scrolling again, it stops halfway through the first "o" in "Color", and just repeats indefinitely. The only thing I could do is completely reset, eight failed boots. At first I thought it may be an older version of CWM on my Msd card so I made a new one with v. 3.0.2.8 and rooted successfully, but first time I shut it off and rebooted, it happened again. I am thinking only thing to do is never turn it off. Any ideas would be greatly appreciated.

reebz said:
I have a NC 1.2. I am able to root using a CWM 3.0.2.8 Msd card with Manual Nooter no problem. The problem occurs when I shut it off and then reboot. It gets to the part where the words "Nook Color" start scrolling across the screen. "Nook Color" completes one time successfully and when it starts scrolling again, it stops halfway through the first "o" in "Color", and just repeats indefinitely. The only thing I could do is completely reset, eight failed boots. At first I thought it may be an older version of CWM on my Msd card so I made a new one with v. 3.0.2.8 and rooted successfully, but first time I shut it off and rebooted, it happened again. I am thinking only thing to do is never turn it off. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
What version MN are you using? You’re not wiping anything when you flash MN, right?
reebz said:
…At first I thought it may be an older version of CWM on my Msd card so I made a new one with v. 3.0.2.8 and rooted successfully, but first time I shut it off and rebooted, it happened again. I am thinking only thing to do is never turn it off.
Click to expand...
Click to collapse
Are you saying that after you flash MN, you remove the SD card, it will fully boot up into the OS, then when you turn off the device and try to turn it back on, it will then not boot up? Or, are you saying that after you flash MN, you remove the SD card, and then the device fails to boot?
It sounds to me like you are wiping the system before you flash MN, but until I get the answers to the above questions, I can’t say for sure. MN is a add on pack for the stock OS, not a full rom, so you don’t wipe before you flash.

I have latest version of MN. I do not wipe anything. I boot into CWM and install MN with a msd card. Upon successful installation of MN, I remove msd card and reboot successfully that one time into a rooted NC. I can use Gmail app, download and install from both Android and Amazon markets. However, if I power down completely and reboot, it loops as explained in my OP.

reebz said:
I have latest version of MN. I do not wipe anything. I boot into CWM and install MN with a msd card. Upon successful installation of MN, I remove msd card and reboot successfully that one time into a rooted NC. I can use Gmail app, download and install from both Android and Amazon markets. However, if I power down completely and reboot, it loops as explained in my OP.
Click to expand...
Click to collapse
Are you updating Adobe Flash? You can't directly update Adobe Flash from the Nook Color. The most common issues that will cause a boot loop on a NC after having a fully working device, are installing the wrong kernel, and updating Adobe Flash from the Market. If you updated Adobe Flash, download the attached file, and flash with CWM. The file should delete the old flash player, and install the updated one. This should give you a working device again. If it does work for you, please report back here so others will know what the fix it.

GMPOWER said:
Are you updating Adobe Flash? You can't directly update Adobe Flash from the Nook Color. The most common issues that will cause a boot loop on a NC after having a fully working device, are installing the wrong kernel, and updating Adobe Flash from the Market. If you updated Adobe Flash, download the attached file, and flash with CWM. The file should delete the old flash player, and install the updated one. This should give you a working device again. If it does work for you, please report back here so others will know what the fix it.
Click to expand...
Click to collapse
I have updated Flash Player from the Market after rooting. If I remember correctly, I've powered down after rooting and installing numerous apps, including Flash, and rebooted . Maybe that's the culprit. I have not installed a different kernel. I'll go ahead and install the attached zip, with much thanks, but I don't know if I want to power off and reboot, for fear of dreaded boot loop.
Ok, I installed Flash Fix and rebooted, and the same boot loop is occurring. Looks like time to reset and reroot, and for now, never turn it off.

reebz said:
I have updated Flash Player from the Market after rooting. If I remember correctly, I've powered down after rooting and installing numerous apps, including Flash, and rebooted . Maybe that's the culprit. I have not installed a different kernel. I'll go ahead and install the attached zip, with much thanks, but I don't know if I want to power off and reboot, for fear of dreaded boot loop.
Ok, I installed Flash Fix and rebooted, and the same boot loop is occurring. Looks like time to reset and reroot, and for now, never turn it off.
Click to expand...
Click to collapse
I just realized that I missed a step in the install script for that file, that is why it did not work for you. Yes, adobe flash is your problem. To update Adobe Flash on the nook color, you have to uninstall the old version, and then install the new adobe flash.

For all future references, I have attached the working Adobe Flash fix file. It includes flash version 10.3.186.3, that was released today. It has been tested to work, and you can allow auto-update in the market without future problems.

Ok, thanks, I will reluctantly give this a try when I get home from work.
Edit: Ok, now. I'm trying to uninstall Flash Player and having difficulties. It doesn't show up in the app drawer, so I go to Market to see if there is an uninstall option, but there is only an update option, so I updated, and then uninstalled to see if that would work, but it still showed up in "my apps", in market. I opened up app drawer and selected manage apps and found it, but selecting the uninstall button does nothing. I then tried installing Titanium Backup and after installing, Titanium Backup won't open and doesn't even show up in my app drawer. So, I'm a little stymied now. Unsure what to do next

reebz said:
Ok, thanks, I will reluctantly give this a try when I get home from work.
Edit: Ok, now. I'm trying to uninstall Flash Player and having difficulties. It doesn't show up in the app drawer, so I go to Market to see if there is an uninstall option, but there is only an update option, so I updated, and then uninstalled to see if that would work, but it still showed up in "my apps", in market. I opened up app drawer and selected manage apps and found it, but selecting the uninstall button does nothing. I then tried installing Titanium Backup and after installing, Titanium Backup won't open and doesn't even show up in my app drawer. So, I'm a little stymied now. Unsure what to do next
Click to expand...
Click to collapse
Titanium Backup is going to be your best bet to do the uninstall process. When you selected update Flash from the market, then went and uninstalled it, you were only uninstalling the update. If TB installed, then it should show up in the app drawer of Zeam launcher. You can go into the market, and select to open it from there. Sometime it will not open on first attempt, because it is trying to ask you to give it root permission. If you still have trouble with it not opening, then uninstall it, and try to install it again. You can also open up the “Superuser” app to make sure that it has not been denied root permission.

TB definitely didn't appear in Zeam app drawer. I'm charging now and give it another shot in a bit.
Edit: Success. I got TB installed. I made a stupid error. I only installed the paid app, not the free also. I got Flash uninstalled and installed your Flash Fix.zip with numerous reboots with no boot loops.
GMPOWER, Thanks for your assistance

GMPOWER said:
For all future references, I have attached the working Adobe Flash fix file. It includes flash version 10.3.186.3, that was released today. It has been tested to work, and you can allow auto-update in the market without future problems.
Click to expand...
Click to collapse
I don't normally bump old threads, but this just saved me
Thanks a lot, I was at wits end figuring out why it was boot looping.

dreadwing said:
I don't normally bump old threads, but this just saved me
Thanks a lot, I was at wits end figuring out why it was boot looping.
Click to expand...
Click to collapse
Same here. Big thanks to GMPower! (My first post here, now I can use the Thanks button!)

Total noob question. This is my first time rooting. I got the root to work fine but updated Flash before finding out about the loop. I'm not sure what I'm supposed to do to fix this problem. OP in this thread said he reinstalled MN 4.6.16 via bootable SD with CWM and could get his nook to boot up. I tried that and rebooted but I'm still getting stuck in the loop.
Do I need to wipe my nook before reapplying MN?

dahcheet said:
Total noob question. This is my first time rooting. I got the root to work fine but updated Flash before finding out about the loop. I'm not sure what I'm supposed to do to fix this problem. OP in this thread said he reinstalled MN 4.6.16 via bootable SD with CWM and could get his nook to boot up. I tried that and rebooted but I'm still getting stuck in the loop.
Do I need to wipe my nook before reapplying MN?
Click to expand...
Click to collapse
Use the zip file in post #7 (in this thread). Drop it onto the same SD card you used to load MN 4.6.16. Put the SD card in and it'll boot to CWM....then flash that zip file the same way you flashed MN. Then, power off the NC, remove the CWM SD card and put in your regular SD and turn the NC back on. That should be it...no more boot loop.

I've got the same issue as the thread started and I downloaded the zip from post 7 and flashed it just like I flashed MN, but it's still boot looping. It gets a bit farther into the "Nook Color" logo but keeps repeating.

Boot Loops NC 1.3
GMPOWER said:
For all future references, I have attached the working Adobe Flash fix file. It includes flash version 10.3.186.3, that was released today. It has been tested to work, and you can allow auto-update in the market without future problems.
Click to expand...
Click to collapse
This problem started for me on Rooted 1.3. October 5th, Applied this fix.
Thanks GMPOWER

I figure I will explain my problem in more detail. I am working with my girlfriend's Nook trying to get it rooted. The first time I did she had 1.2 stock and I rooted it successfully. She updated flash not knowing that it would cause a boot loop. I had no idea how to fix it so she set it back to factory settings and procedded to update to 1.3 to see if that would solve the boot loop. I rooted it again and it started boot looping again. I found this thread and the flash fix. I flashed it onto the Nook and it fixed the loop problem.
Well she found out that the marketplace has limited visibility with 1.3 and wanted to go back to 1.2 to have her full visibility back. So she factory reset it again, I rooted it again and it started boot looping again. This time though the fix from post 7 isn't helping. I flash it and then reboot and it loads the "Nook Color" logo once fully and then stops and starts it over again and gets stuck at "Nook Col".
Is there anyone who might be able to help me with what the problem is, or am I gonna have to reset it back to stock, use Titanium Backup to remove flash and then use the zip from post 7? I know that it's not a root problem because I successfully rooted my mom's Nook before my girlfriends and her's is working fine.

Followed your instructions and my problem solved, many thanks!
johnny15 said:
Use the zip file in post #7 (in this thread). Drop it onto the same SD card you used to load MN 4.6.16. Put the SD card in and it'll boot to CWM....then flash that zip file the same way you flashed MN. Then, power off the NC, remove the CWM SD card and put in your regular SD and turn the NC back on. That should be it...no more boot loop.
Click to expand...
Click to collapse

my first post. thanks GMpower

just had this happen to me too. I've tried the flash update, and I get slightly more of the nook color boot graphic but it still hangs.
any thoughts?

[Q] Nook stuck on loading on Cyanoboot screen

Hello,
I was running one of the CM9 nightlies and decided to try one of eyeballer's with OpenGL, and was able to make the switch without any problems, but after a while wanted to go to a non-openGL build and after flashing it my Nook won't boot past the loading screen.
I have a 1GB card with CMW which I'm able to boot to, I've tried wiping data, format boot and format system and reinstalling one of the builds that had previously worked, but still get stuck on Cyanoboot's loading screen. Even tried going back down to CM7 to see if that helped, but stuck on that loading screen as well.
What am I missing here? I've formatted boot, system, cache, data, everything, but the issue persists.
Any suggestions as to how I can make my Nook come back to live.

ryuz4ki said:
Hello,
I was running one of the CM9 nightlies and decided to try one of eyeballer's with OpenGL, and was able to make the switch without any problems, but after a while wanted to go to a non-openGL build and after flashing it my Nook won't boot past the loading screen.
I have a 1GB card with CMW which I'm able to boot to, I've tried wiping data, format boot and format system and reinstalling one of the builds that had previously worked, but still get stuck on Cyanoboot's loading screen. Even tried going back down to CM7 to see if that helped, but stuck on that loading screen as well.
What am I missing here? I've formatted boot, system, cache, data, everything, but the issue persists.
Any suggestions as to how I can make my Nook come back to live.
Click to expand...
Click to collapse
Well, for one thing, never format boot.
After trying cm7, you still get cyanoboot? It should have changed to the green cyanogenmod logo. If not then your flashes are not working.
Sent from my Nook Color running ICS and Tapatalk

After flashing CM7 I get the green boot screen, but my Nook also gets stuck on that loading screen.
When flashing CM9 I can press the ''N'' button and scroll the available boot methods, but when I choose one I get stuck on loading again.
So on both CMs I'm getting stucked on ''loading'', which started to happen on Monday after going from one of the openGL builds to the latest non-openGL build.

ryuz4ki said:
After flashing CM7 I get the green boot screen, but my Nook also gets stuck on that loading screen.
When flashing CM9 I can press the ''N'' button and scroll the available boot methods, but when I choose one I get stuck on loading again.
So on both CMs I'm getting stucked on ''loading'', which started to happen on Monday after going from one of the openGL builds to the latest non-openGL build.
Click to expand...
Click to collapse
Ok, that means that CWM is putting the boot files on the boot partition since they change CM7 vs CM9.
Which version is your CWM on the SD?
You can't boot to anything, not even emmc recovery? Or you just can't boot to 'normal'? Do you even have emmc recovery installed? If you don't, get the first file on this post and flash it with your CWM card. You may be in a recovery bootloop, without a recovery.
http://forum.xda-developers.com/showthread.php?p=21932561
Sent from my Nook Color running ICS and Tapatalk

Thank you leapinlar, seems like it was me having an old CWM on my boot card that wasn't helping me, installed the recovery zip and manage to boot into that from cyanoboot's loading screen and reflashed and managed to boot my Nook.
I'm still intrigue as to how this happened, do you think that when switching between openGL and non-openGL the boot partition got corrupted or something? I've been flashing many roms for almost a year and had never had this issue happen to me before.
Thanks a million for taking time to help me, you're a life saver.

ryuz4ki said:
Thank you leapinlar, seems like it was me having an old CWM on my boot card that wasn't helping me, installed the recovery zip and manage to boot into that from cyanoboot's loading screen and reflashed and managed to boot my Nook.
I'm still intrigue as to how this happened, do you think that when switching between openGL and non-openGL the boot partition got corrupted or something? I've been flashing many roms for almost a year and had never had this issue happen to me before.
Thanks a million for taking time to help me, you're a life saver.
Click to expand...
Click to collapse
It's possible your recovery somehow got corrupted during the flash. If that happens, it does not clear the recovery boot flag and it keeps trying to boot to recovery and it can't because it is corrupted. And it just bootloops forever.
Also, make sure your CWM bootable card is a recent version. If you have a newer nook and an old CWM and you try to clear data, it fails and you have a mess.

Hi, I am totally new at this but I been having a nook color for over a year now and been running CM7 on it for the longest time. Tonight I wanted to put CM9 on and for whatever I did now I just can't seem to get pass the Cyanoboot screen. Doesnt matter what I do it just gives me a blank screen and stays there. What do I gotta do to fix it or get rid of this cyanoboot and back to CWM so i can re flash everything. Any help would be great. Thanks

huyroy said:
Hi, I am totally new at this but I been having a nook color for over a year now and been running CM7 on it for the longest time. Tonight I wanted to put CM9 on and for whatever I did now I just can't seem to get pass the Cyanoboot screen. Doesnt matter what I do it just gives me a blank screen and stays there. What do I gotta do to fix it or get rid of this cyanoboot and back to CWM so i can re flash everything. Any help would be great. Thanks
Click to expand...
Click to collapse
Try flashing latest CM7 then CM9 over the top. Might want to format Data and wipe caches in between.

DizzyDen said:
Try flashing latest CM7 then CM9 over the top. Might want to format Data and wipe caches in between.
Click to expand...
Click to collapse
I cant flash anything right now. I cant go into CWM and it just stuck at the cyanoboot screen and whatever choice i pick from that screen will give me a blank screen.

huyroy said:
I cant flash anything right now. I cant go into CWM and it just stuck at the cyanoboot screen and whatever choice i pick from that screen will give me a blank screen.
Click to expand...
Click to collapse
Try using my bootable CWM card in my tips thread in my signature. It works fine under ordinary circumstances, but I have been wanting someone to try it to see if it gets you out of that bootloop.
Edit: Just a question out of curiosity. When you finished flashing that new ROM with your CWM, were you able to reboot from CWM normally using the menu choice? Or was there some lockup or something where you had to reboot from CWM by hard powering off?

leapinlar said:
Try using my bootable CWM card in my tips thread in my signature. It works fine under ordinary circumstances, but I have been wanting someone to try it to see if it gets you out of that bootloop.
Edit: Just a question out of curiosity. When you finished flashing that new ROM with your CWM, were you able to reboot from CWM normally using the menu choice? Or was there some lockup or something where you had to reboot from CWM by hard powering off?
Click to expand...
Click to collapse
I believe i had to powering off. I'm sorry but I didnt quite understand what you told me to do with the bootable CWM. I am fairly new to all this flashing ROMS crap. If u can explain it a lil bit better that would be greatly appreciated.

huyroy said:
I believe i had to powering off. I'm sorry but I didnt quite understand what you told me to do with the bootable CWM. I am fairly new to all this flashing ROMS crap. If u can explain it a lil bit better that would be greatly appreciated.
Click to expand...
Click to collapse
Just follow the directions in the thread to make the card. Then put it in the nook and try booting. If it boots to CWM, just use it to flash like DizzyDen said. And when you exit, use the menu to choose re-boot.
PS, the hard powering off caused the problem. CWM was not able to clear the recovery flag and you ended up in a recovery bootloop. Let me know if my card boots.

leapinlar said:
Just follow the directions in the thread to make the card. Then put it in the nook and try booting. If it boots to CWM, just use it to flash like DizzyDen said. And when you exit, use the menu to choose re-boot.
PS, the hard powering off caused the problem. CWM was not able to clear the recovery flag and you ended up in a recovery bootloop. Let me know if my card boots.
Click to expand...
Click to collapse
Ok I read the instruction, i know i gotta put the bootable CMW Recovery SD. you said the file is attached to the board... what board? where can i get this file? lol thanks

huyroy said:
Ok I read the instruction, i know i gotta put the bootable CMW Recovery SD. you said the file is attached to the board... what board? where can i get this file? lol thanks
Click to expand...
Click to collapse
Look at the link in my signature. If you read the instructions, scroll to the bottom. Attached to that post.

leapinlar said:
Look at the link in my signature. If you read the instructions, scroll to the bottom. Attached to that post.
Click to expand...
Click to collapse
I got it to work, thanks alot running 4.0.4 now. Slightly choppier than the CM7 I had on but whatever lol

huyroy said:
I got it to work, thanks alot running 4.0.4 now. Slightly choppier than the CM7 I had on but whatever lol
Click to expand...
Click to collapse
Thank YOU for testing my card and proving that gets you out of the recovery bootloop you were in.
You need to take one more step. You need to put a new CWM back on your internal memory so it is there ready for the next time you want to install a ROM. If you go back to my tips thread, there is a link to a new flashable CWM zip (version 5.5.0.4) that can be put on your internal memory. The link is in item B1. Just download that zip file, then boot one more time to my bootable CWM card and install that zip. You should not need my card anymore after that unless you get in a bootloop again.

I've had something similar going on. I believe my nook has been using the EMMC to boot. It was on CM7. I grabbed the latest open GL CM9 because I plan on giving this to my parents. I wanted them to be able to use the TWC TV/DVR app which only works on ICS. I am stuck in a loop where it keeps going to recovery and neither flashing cm9 again nor recovering to an old back up is working. Is the recovery SD card the suggested method for fixing this? I'm not stuck in a loop but I am stuck and having to go into recovery every boot.
For awhile, the N menu gave me both EMMC and SD card boot options. Now it only has EMMC ones.

NapalmDawn said:
I've had something similar going on. I believe my nook has been using the EMMC to boot. It was on CM7. I grabbed the latest open GL CM9 because I plan on giving this to my parents. I wanted them to be able to use the TWC TV/DVR app which only works on ICS. I am stuck in a loop where it keeps going to recovery and neither flashing cm9 again nor recovering to an old back up is working. Is the recovery SD card the suggested method for fixing this? I'm not stuck in a loop but I am stuck and having to go into recovery every boot.
For awhile, the N menu gave me both EMMC and SD card boot options. Now it only has EMMC ones.
Click to expand...
Click to collapse
You could try the new CWM SD. Just make sure when you finish using CWM to exit from that by using the 'reboot' choice in the menu. Do not just hard power off.

leapinlar said:
You could try the new CWM SD. Just make sure when you finish using CWM to exit from that by using the 'reboot' choice in the menu. Do not just hard power off.
Click to expand...
Click to collapse
So slap the image on a clean SD card and boot up from it. After it's done and I hit reboot, what would I do to get back to CM7 or CM9? I haven't had to do something like this yet. Any time I've had issues, I've been lucky enough to go back to a saved clockwork backup and restore things back to how they should be

NapalmDawn said:
So slap the image on a clean SD card and boot up from it. After it's done and I hit reboot, what would I do to get back to CM7 or CM9? I haven't had to do something like this yet. Any time I've had issues, I've been lucky enough to go back to a saved clockwork backup and restore things back to how they should be
Click to expand...
Click to collapse
First thing I would try is just to exit the new CWM via the menu to see if it gets you out of the bootloop. Retry booting without the SD in. If it will still only boot to recovery, I would again boot to my CWM and flash the new recovery to emmc. Next I would try to restore your old nandroid backup with the new CWM. If none of that works, flash a new CM to emmc with the new CWM.

[Q] A500 Boot hang on 4.1.2 cm10-flex ROM

Hello all,
I realize you all are busy but I'm at my wits end here. I installed my bootloader and recovery using afterOTA. This worked really well, I installed Thor 1.7.3 recovery and ICS V8 bootloader using the utility. I then booted into recovery and did a factory reset (really), reset cache and dalvik, battery settings as well... I then went to install ZIP (JB 4.1.2 CM10-FLEX v6supercharged_Aroma-Rev3.4) from internal storage (download folder). I customized the ROM then went back and installed the random apps...
After this was done I hit next and installed the ROM. It didn't take as long as I thought it would, and I hit reboot when it was done, but came to a screen that I could press next on. The installer screen said it was installing permissions, it didn't say that it was completely finished, just installing permissions or something, but I was able to press next.
After rebooting, it started the stock android boot animation, got to the upgrading applications screen, after the applications were done "optimizing" it went back into the stock android boot animation. It never came out of it.
I'm confused as to what I am doing wrong.. I've flashed ROMs multiple times and I thought this one would be the easiest out of all of them considering I didn't care about the data on it and I'm just playing around.
Any help would be appreciated. Thanks!

Fixed.. I'm an idiot
GermanDoerksen said:
Hello all,
I realize you all are busy but I'm at my wits end here. I installed my bootloader and recovery using afterOTA. This worked really well, I installed Thor 1.7.3 recovery and ICS V8 bootloader using the utility. I then booted into recovery and did a factory reset (really), reset cache and dalvik, battery settings as well... I then went to install ZIP (JB 4.1.2 CM10-FLEX v6supercharged_Aroma-Rev3.4) from internal storage (download folder). I customized the ROM then went back and installed the random apps...
After this was done I hit next and installed the ROM. It didn't take as long as I thought it would, and I hit reboot when it was done, but came to a screen that I could press next on. The installer screen said it was installing permissions, it didn't say that it was completely finished, just installing permissions or something, but I was able to press next.
After rebooting, it started the stock android boot animation, got to the upgrading applications screen, after the applications were done "optimizing" it went back into the stock android boot animation. It never came out of it.
I'm confused as to what I am doing wrong.. I've flashed ROMs multiple times and I thought this one would be the easiest out of all of them considering I didn't care about the data on it and I'm just playing around.
Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Well, I kept working on it and I think I was just impatient. Maybe. Either way I went back and tried to reflash several times, doing the wipes from the wipe screen each time. No luck. Eventually I went and formatted the /system /data and all the other options in the mount/storage menu. I then did all the "wipes" again and reflashed. It worked this time! Running incredibly smoothly.
Thanks for reading everyone.