Related
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Well, after a few weeks of reading posts, even opening up the hardware and taking the nook apart, here I am asking a question. I figure I would go to the source rather than those other place I was reading and tryign to get info from (mot os those places link here anyway). I know that everyone says that the nook is "unbrickable;" while I want to believe it, I may be in a place where it may be true.
I do want to add a thanks as well, since the NC "tablet" has been very handy, and my wife and I have really enjoyed it. Wouldn't have happened without you all. I wish I had more time to participate in developing, but working 80+ hours/week in a hospital limits my free time, as you can imagine.
I rooted the NC and installed Cyanogenmod 7 back in July 2011. It was a 1.1 model (if I recall correctly). I installed the mod to EMMC, along with CWM. Things ran fine for 6 months. Literally no issues. Then, one night the battery was dead, so I plugged it into the computer USB to charge while the machine was off. Didn't touch it at all. When I went to turn it on again, I was stuck in a bootloop. It would go to the cyanogenmod screen and say "Loading" then would start over again. So, I naturally made a bootable SD card, and tried going into CWR to fix things. However, the SD card had the bootloop as well. It would get to the two skulls and "Loading", flash blank, then start over again.
That went on for a while. I couldn't boot into anything, not into recovery, alternate images, literally nothing. So, I tried different images --- nothing. Finally, I did the power+n and got into the only screen that wouldn't keep resetting. It has blue text and says "Entering boot menu". The menu says "Encore U-boot Menu by j4mmr. 1.2 port+ extras by fattire." From this screen, I can navigate and change the boot options. However, once again, whatever I try does not actually boot, regardless of what I set it to. The only thing that I got from getting here was no more boot loops. After getting it to this point, I can try loading anything, and it will start, then the screen goes black/blank, and nothing happens. Left it on for hours to test.
Since that point, I have switched cards (SanDisk 2 GB class 4, Patriot 8 GB and a generic 8 GB microSD). I know that cards work correctly because I got a hold of a second nook, and they work fine on it. Below are a list of all the images I have tried to run off the SD. Again, nothing will boot, not even clockwork recovery/clockworkmod.
128 mb rootpack (IOMonster)
clockwork 3.0.2.8
clockwork 3.2.0.1 eyeballer
Nooter
Mirage_CM7_ICS_CM9_DualbootSD (this card works great on the working NC)
TWRP 2.0 RC0
Generic SD
Clockwork 0.7 -> starts boot loops again
I also tried ADB, connecting to the computer and using putty over SSH. Didn't work. 8 interrupted boots with 9th holding power+n. Nope. I even took the nook apart and disconnected the battery. Still no go.
If I recall, I think I had CWM 3.0.0.5 installed to the card and to the emmc.
If anyone has any other ideas, I could really use the help. I consider myself pretty computer literate (build my machines, coded in my spare time in the past, hacked a lot of my electronics). I have read many guides/sites and even tried the outdated stuff. Once again, I cannot get into clockwork recovery, so any guide that says to do that as the first step will not work. I also cannot boot off of the SD on cards that I know function.
Would using an older version of CWM (prior to 3.0.0.5) work? I think I remember reading a bunch of stuff about problems people were having with that version. The thing is, I wasn't installing or flashing anything new. I wish I was, because then I would know what was happening when everything got screwed up.
Thanks a bunch in advance for your guy's (gals?) time. This has been really painful.
Wow, that must be frustrating. First make sure you didn't change the boot settings to something other than the SD card when you were in the boot menu. As long as the Nook is powering on and doing something you can probably save it from being a brick.
I would start with a newer version of ClockWork Mod Recovery here: http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
There is a contradiction in the file names but the actual version should be 3.2.0.8. If that doesn't work then you may want to go back to an older version. In that case I would still load a newer version's zip file onto that card, so that if you do get the older version to boot you can use it to flash the newer version.
Before going back to older CWM versions though give this a try if the new CWM above doesn't work http://forum.xda-developers.com/showthread.php?t=958748
JP
Yeah, it has been frustrating, especially not knowing what happened in the first place. I actually did try the version from that first link (where I put 3.0.2.8). Again, the big issue I am having is that I cannot even get into the CWM. If I could, I could fix it. I also saw and read through that xda thread you kinked to (open right now in my browser), but the problem remains that I cannot even get to the point where I can flash something.
Thanks at least for responding. I'll try a few more things and see if it works, but I am running out of ideas.
In theory creating a bootable CWM card will get you into recovery even though you can't access the Recovery on the internal. Once you reach Recovery from the SD card you can flash whatever you need. It is just a matter of making a bootable recovery card that boots far enough to get you there.
In theory, yes, but as I said in my first post, I tried all the bootable cards without any luck. When I try to set the SD card as primary boot from that one screen from fattire, it locks and never restarts.
J515OP said:
Wow, that must be frustrating. First make sure you didn't change the boot settings to something other than the SD card when you were in the boot menu. As long as the Nook is powering on and doing something you can probably save it from being a brick.
I would start with a newer version of ClockWork Mod Recovery here: http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
There is a contradiction in the file names but the actual version should be 3.2.0.8. If that doesn't work then you may want to go back to an older version. In that case I would still load a newer version's zip file onto that card, so that if you do get the older version to boot you can use it to flash the newer version.
Before going back to older CWM versions though give this a try if the new CWM above doesn't work http://forum.xda-developers.com/showthread.php?t=958748
JP
Click to expand...
Click to collapse
This happened to me a couple of times on CM7. Don't know why, but I believe I used the last method listed to repair it. There was an older version of CWM that would cause this sometimes. When you get it going again, you must update CMW to the new one.
DigitalMD said:
This happened to me a couple of times on CM7. Don't know why, but I believe I used the last method listed to repair it. There was an older version of CWM that would cause this sometimes. When you get it going again, you must update CMW to the new one.
Click to expand...
Click to collapse
How did you get it to boot into CWM in the first place in order to flash? That is my current problem. Any method of fixing relies on the ability to boot into CWM from the SD card, which (for whatever reason) isn't working at the moment.
Well, tried to use the native Nook u-boot. Get the "Touch the Future of Reading" screen, then black, just like with any of the other cards. On the good nook, it boots into a linux file and runs the recovery script, so it is not the card reader or the SD card.
Well, still doesn't work. I guess I officially bricked it without even knowing what happened. Bummer.
czarofthefrozentundra said:
Well, still doesn't work. I guess I officially bricked it without even knowing what happened. Bummer.
Click to expand...
Click to collapse
You said you tried eyeballers 3.2.0.1 CWM. Did you mean the 1GB image file he posted on his thread? And how did you burn the image to the card? You should be using win32diskimager running in administrator mode on Windows. And it is best to use a cheap card reader rather than any card reader built into your PC. The nook can be really finicky about how the card is written.
leapinlar said:
You said you tried eyeballers 3.2.0.1 CWM. Did you mean the 1GB image file he posted on his thread? And how did you burn the image to the card? You should be using win32diskimager running in administrator mode on Windows. And it is best to use a cheap card reader rather than any card reader built into your PC. The nook can be really finicky about how the card is written.
Click to expand...
Click to collapse
Yes, I tried that image from his thread. I always use win32diskimager and use a card reader. I have working cards (I have a second NC that runs fine); there is just something wrong with the boot process, and I cannot get into CWR to fix it. It starts, but then never makes it in or reboots. Only time I can keep it from rebooting is by holding "n" and going into the boot option menu.
czarofthefrozentundra said:
Yes, I tried that image from his thread. I always use win32diskimager and use a card reader. I have working cards (I have a second NC that runs fine); there is just something wrong with the boot process, and I cannot get into CWR to fix it. It starts, but then never makes it in or reboots. Only time I can keep it from rebooting is by holding "n" and going into the boot option menu.
Click to expand...
Click to collapse
It goes to the boot menu when you hold n with eyeballers image burned to SD? What happens when you select SD and normal? Just a hang? With 'loading' showing?
Edit: I just thought of another reason that could be causing this. There is a flag set in /rom that tells the system to try to boot into recovery. It tries no matter what you tell it to do in the boot menu. ROM Manager uses that flag to boot to recovery when you tell it to. Then after you successfully get into recovery and exit it by telling CWM to reboot, CWM clears that flag. If your recovery is borked up, you never get that flag cleared and it's an endless loop.
There are two solutions I can think of. First, use racks dual boot SD that you already have and go into the boot menu with that. Tell it to go to SD and recovery. Hopefully his recovery will load. Then immediately exit by the menu. That should clear the flag. If that fixes it and it boots to CM7, go to ROM Manager and flash a new CWM to emmc.
If that does not fix it search xda for 'fix recovery'. There is a nook thread telling how to fix the recovery on emmc.
Edit2: I just thought of a third way to try to get it to boot. Take eyeballers 3.2.0.1 CWM SD and put it in your PC. There should be two files there named uImage and uRamdisk. Make a copy of them on the SD and rename the copies to uRecImg and uRecRam. Then put back in nook and reboot to see what you get.
Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.
czarofthefrozentundra said:
Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.
Click to expand...
Click to collapse
See my edit2 above for a third way to try to clear the flag.
Sent from my NookColor running ICS and Tapatalk
czarofthefrozentundra said:
Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.
Click to expand...
Click to collapse
Hello? Feedback?
Sent from my Nook Color running ICS and Tapatalk
Ha, I tried the quick reply function, and it didn't work. Here is what I wrote yesterday (verbatim, since I still had the window open):
"Well, so far no luck. Here is what I have tried, and the new information that I learned.
Used dual boot SD that I know works and booted into bootloader menu. Tried all different options on the SD card. What happens is that it thinks for a bit, then turns the screen black, but the boot screen never comes up (i.e. the Cyanogenmod logo that usually starts before things boot). So there must be some problem there.
If I hold down power, it will restart. Again, the screen turns black after the loading screen is on for a while (happens no matter which image I burned to the card).
I still need to try the other method (eyeballer one). I don't think the EMMC reset will work with my particular issue, as I had read that thread earlier."
czarofthefrozentundra said:
I still need to try the other method (eyeballer one).
Click to expand...
Click to collapse
If the problem is the recovery flag, the mods to the eyeballer CWM SD should work. If it does not work, it may be something else. If it does work you can flash a new CWM to emmc using another eyeballer zip. Get it here:
http://forum.xda-developers.com/showthread.php?p=21932561
You would want the first choice.
Sent from my Nook Color running ICS and Tapatalk
Cool. Will give it a try tonight and report back. Just have to find my spare SD card.
So, tried with the eyeballer, and I couldn't get it to work. One thing I did notice, though (actually by chance) is that even though the screen is black, the nook is on. I saw this because it all of the sudden started flashing the low battery screen and then turned off.
Anyhow, still looks like I am in the same position. The EMMC fix doesn't work for me because I cannot even boot of an SD card.
EDIT: Actually, I just reread your post. I didn't do it right. I am going to try again and report back.
EIDT 2: Nope, didn't work. Do I need to hold all the buttons down while booting or do something else special?
czarofthefrozentundra said:
So, tried with the eyeballer, and I couldn't get it to work. One thing I did notice, though (actually by chance) is that even though the screen is black, the nook is on. I saw this because it all of the sudden started flashing the low battery screen and then turned off.
Anyhow, still looks like I am in the same position. The EMMC fix doesn't work for me because I cannot even boot of an SD card.
EDIT: Actually, I just reread your post. I didn't do it right. I am going to try again and report back.
EIDT 2: Nope, didn't work. Do I need to hold all the buttons down while booting or do something else special?
Click to expand...
Click to collapse
I'm not sure what to tell you to do next. I guess I am going to send you to a post that tells pretty plainly how to do the 8 failed boots. I know you tried that, but timing is very critical with that procedure. Worth a try to me.
http://forum.xda-developers.com/showthread.php?p=25405429
How do you do the 8 failed boot deal with the cyanogenmod screen running. I am not sure about the timing of things. Also, which buttons? I have seen people do it with just the power button. Other places say with the power+n+vol up.
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.
I installed CM9 Eyeballer the other day on my NC. It pretty much works, but if I go into the web browser or any other factory-installed app, hitting the "N" button takes me back to the factory-installed home screen, and I can't find any way to get back to the Android home screen, short of rebooting the device. Is this normal?
Also, I flashed Gapps using gapps-20120429-ics-signed.zip, and the only Google App that appears is Play Store -- I was able to sign in, but the next screen gave me a "Server Error," and that's all it's done since. I verified the md5sum, and also tried again to install it. No change. Is there some version conflict, or something like that?
Edit: did not install CM9, after all. I now have.
What is the 'factory installed home screen'? You mean stock? That is not possible if you installed CM9 over the top of stock on emmc. Can you explain a little more how you installed it and what you mean.
Well...
I followed the directions as closely as I could: create a recovery chip, copy over the zip file (manualnooter-5.08.20-apps2sd.zip), reboot, install from zip file, install Manual Nooter, flash update-Froyo1.2-dalingrin-OC-emmc-090111.zip, install Gapps, reboot again. As far as I could tell, my results were consistent with the directions, up until the symptoms I described. For example, the splash (smash) screen is right, and the rainbow-y thing, and so on.
This partial success is even more frustrating than a total failure.
estebandido said:
I followed the directions as closely as I could: create a recovery chip, copy over the zip file (manualnooter-5.08.20-apps2sd.zip), reboot, install from zip file, install Manual Nooter, flash update-Froyo1.2-dalingrin-OC-emmc-090111.zip, install Gapps, reboot again. As far as I could tell, my results were consistent with the directions, up until the symptoms I described. For example, the splash (smash) screen is right, and the rainbow-y thing, and so on.
This partial success is even more frustrating than a total failure.
Click to expand...
Click to collapse
Your original post said you installed CM9. You did not. You just rooted your stock rom. You might want to edit the title of the post to 'Manual Nooter installed properly, Gapps not working. Then take that CM9 Eyeballer statement out of the text in the first post and you might get some proper responses from folks.
Sure enough.
leapinlar said:
Your original post said you installed CM9. You did not. You just rooted your stock rom.
Click to expand...
Click to collapse
Ah... I was under the impression that Eyeballer was a version name of CM9. None of the sets of instructions I read made it clear to me that wasn't the case.
I ended up doing a factory reset, then reinstalling everything. The picture is far rosier now -- it finally looks the way I pictured!
Thanks!
estebandido said:
Ah... I was under the impression that Eyeballer was a version name of CM9.
Click to expand...
Click to collapse
Eyeballer does build a version of CM9. But that has nothing to do with what you did. You ran Manual Nooter, which is a tool to root your stock installation. CM9 is a completely different version of Android than stock is. And when you install CM9, your stock is completely removed and replaced by CM9.
You do not have CM9 installed, you have just rooted your stock rom.
Anyway, I'm glad you got it working.
Edit: I see you modified your original post to say you did later install CM9.
[ROM][NC] Unofficial CM9 Nightly builds - with/without OpenGL
I don't have enough posts in XDA to post in the (goo dot gl/vPJcM) actual ROM thread so I'm hoping someone will see it here.
After installing the CM7 ROM a long time ago. they Nook wasn't able to boot into CWM. I can only access the recovery using a bootable SD card. That may or may not matter.
Yesterday I installed both the 3 SEP OpenGL and 4 SEP versions of Eyeballers CM9 ROM along with GAPPS. In both versions I cannot get bast the Setup Wizard since it "unfortunately Closed" every time I "touch the Android".
I did install the ROM w/o GAPPS as a temporary fix but will need to eventually access the Play Store.
I did notice that CWM still wont boot into recovery and the Cyanoboot won't either. Cyanoboot takes me to what appears to be a stock Nook screen claiming that an install has failed and that I should power on/off or contact customer service.
Does anybody have any suggestions?
Thanks!
JC
jerrycrabb said:
I did notice that CWM still wont boot into recovery and the Cyanoboot won't either. Cyanoboot takes me to what appears to be a stock Nook screen claiming that an install has failed and that I should power on/off or contact customer service.
Click to expand...
Click to collapse
You do not have CWM installed on internal memory (emmc). That message you are getting means you still have the stock recovery there. You need to flash a CWM to emmc using your bootable CWM card. Look in my tips thread linked in my signature. Look at item A8 and the subheading 'to fix a corrupted or missing recovery on emmc'.
I don't know how to solve your other problem with gapps, other than to do a factory reset with CWM.
From what I can tell, Eyeballer is mostly drinking.
leapinlar said:
You do not have CWM installed on internal memory (emmc). That message you are getting means you still have the stock recovery there. You need to flash a CWM to emmc using your bootable CWM card. Look in my tips thread linked in my signature. Look at item A8 and the subheading 'to fix a corrupted or missing recovery on emmc'.
I don't know how to solve your other problem with gapps, other than to do a factory reset with CWM.
Click to expand...
Click to collapse
Thank you very much for the response, I will try this as soon as I get some time (I have a selfish new baby) and get back.
leapinlar said:
You do not have CWM installed on internal memory (emmc). That message you are getting means you still have the stock recovery there. You need to flash a CWM to emmc using your bootable CWM card. Look in my tips thread linked in my signature. Look at item A8 and the subheading 'to fix a corrupted or missing recovery on emmc'.
I don't know how to solve your other problem with gapps, other than to do a factory reset with CWM.
Click to expand...
Click to collapse
Success! errr..sort of.
Prior to flashing gapps I was able to reboot into CWM. Thank you so much for your help!
Still having the same issue with setup manager after factory reset and wipe of all cache.
If anyone has a work around or another suggestions for CM9 on the NC I'd much appreciate it.
Thanks again.