Stuck in CWR and SD won't mount - Nook Color General

So i rooted my nook 1.1.0, installed CWR, booted into CWR to do a nandroid back up but got an error that it could not mount the /sdcard. Now i'm stuck in a continous boot into CWR w/ no access to the /sdcard. Any help is greatly appreciated.

yeah it's a bug with cwr, you should have choosen "nook (old)" instead of "nook" in rom manager.
in this thread you can D/L a cwr removal than you can apply from cwr (lucky you're in!)
http://forum.xda-developers.com/showthread.php?t=971570&highlight=CWR-removal.zip

Why are these two threads not STICKYS!!!
Dummies Guide to Fixing 'My Nook Won't Boot'
[RECOVERY][ZIP] Nook Color Restore to stock
This is the 2nd Person tonight with this issue.

onclebob said:
yeah it's a bug with cwr, you should have choosen "nook (old)" instead of "nook" in rom manager.
in this thread you can D/L a cwr removal than you can apply from cwr (lucky you're in!)
http://forum.xda-developers.com/showthread.php?t=971570&highlight=CWR-removal.zip
Click to expand...
Click to collapse
I completely restored to stock twice in the first 2 days because after I downloaded ROM Manager from the market I got stuck into CWR. Just so I understand correctly (sorry I'm a dumb n00b with this device), the problem I've been having with ROM Manager and CWR boot looping on my rooted 1.1 NC is because I was selecting "Nook" instead of "old Nook"? The solution seems too easy!

Related

Dummies Guide to Fixing 'My Nook Won't Boot'

First off, I need to address credit where credit is due. All credit goes out to Samuelhalff, Nootered, thecubed, iomonster, Decad3nce and anyone else involved with any of the methods I will mention.
As always, everything in this guide is completely at your own risk, I am not responsible for you messing up your device further nor am I responsible in the event that your Nook Color explodes and kills your cat, grandma, etc.
The Fatal Black Screen:
This is the issue where your Nook "refuses to boot up" usually after running Froyo (or possibly HC) off of your internal memory. This is usually caused by, but is not limited too, formatting your sdcard from within Froyo (or versions of HC prior to the flashable zip).
99.99% of the time, this does not mean your Nook is bricked in any way, what simply happened is your boot partition has become corrupted. For you newbies out there, the boot partition is what allows your Nook Color to turn on. The boot partition contains the instructions for what your Nook Color needs to do in order to start up and run.
The Fix:
Thanks to the guys that developed this neat toy, the Nook is set to boot from the sdcard before booting from the internal memory. What this means is, your nook will first search for a boot partition on the sdcard before searching for a boot partition on your Nook's internal memory. Because of this, we are able to boot and run OS software directly from the SDcard. This is how we will be fixing your "bricked" Nook Color.
First visit this link:
http://forum.xda-developers.com/showthread.php?t=922870
Download either the Rootpack, or the Clockwork Recovery image (1gb).
Next visit this link and download the 1.0.0 or 1.0.1 restore to stock files:
http://forum.xda-developers.com/showthread.php?t=914690
From this link you should also download the very last zip on the page. It is titled-flashable boot repartition zip. or something of the like. If you followed all these steps and still nothing, I would recommend flashing this as it can fix a completely screwed boot partition.
If you wish to instead restore to a pre-rooted 1.1, visit this link:
http://forum.xda-developers.com/showthread.php?t=932145
Once you have the either version of the bootable Clockwork Recovery (Rootpack or normal standard Clockwork Recovery) and a software version you would like to restore to, you must write your clockwork recovery to an sdcard to make it bootable in the Nook.
In order to do this, you must use Win32DiskImager on Windows or the command line on Mac and Linux. Follow theses instructions for writing the file to an sdcard (substitute the Clockwork file in place of Nooter):
http://nookdevs.com/NookColor_Rooting
Once the image is done writing, open up your sdcard on your computer and copy whichever restore to stock zip you choose earlier onto the card.
Now with your Nook Color unplugged from the computer, insert the sdcard and plug the Nook into the computer. Your screen should flash to life. After a short loading screen you will see a menu, using the volume keys, you are able to navigate up and down. Navigate down to the menu item that reads "mounts and storage." Navigate down and press "Format Data" then "Yes." Next do the same thing except format system. Using the power button to go back to a previous menu, return to the "mounts and storage" menu, make sure the sdcard is mounted. (If your sdcard is mounted, you will see the option to 'unmount /sdcard'. If it is not mounted you will see 'mount /sdcard'. In this case you would want to press the 'mount /sdcard' option in order to mount it. Again using the power button as the back button, navigate back to the main menu. You will see a menu item that reads "Install zip from sdcard." Select it. Now select 'choose zip from sdcard.' Now pick the zip you placed on the sdcard earlier. Scroll down to the 'Yes' option and select it. Clockwork Recovery will begin flashing the stock image to your internal memory. After a few minutes, the process should complete and you will see a message that says 'Done. Installation Complete.' From here you should remove your sdcard and navigate back to the main menu. Select the 'Reboot Now' option.
Note: Sometimes after you see the 'Done. Installation Complete.' message, Clockwork will freeze up and you will be unable to navigate back to the main menu in order to reboot. If this is the case do a hard reboot (hold the power button for 15 or so seconds so the screen turns off, then hold the power button again till it turns on).
Congratulations, you've unbricked your bricked Nook Color
TO EVERYONE STILL HAVING PROBLEMS AFTER THIS, YOU MAY/SHOULD FLASH SAMUELHALFF'S REPARTITION ZIP MENTIONED EARLIER. (LOOK UP A FEW LINES, SAME LINK AS THE 1.0.0 AND 1.0.1 RESTORE TO STOCK ZIPS)
UPDATE:
IF YOUR STILL HAVING PROBLEMS, USE THIS LINK TO INSTALL 3.0.1.0 ON INTERNAL EMMC AND THEN BOOT TO IT.
http://forum.xda-developers.com/showthread.php?t=958748
note: to do this, you need to be able to atleast boot to the N screen.
MORE UPDATE:
This link has an updated bootable CWM version on it with ext4 support. Write this to your sdcard, format /system and /data and flash CM7.
http://forum.xda-developers.com/showthread.php?t=959240
If anyone has anything to add to this tutorial, post here or IM me and I will edit the OP.
So I was doing the 'restore to stock' method earlier today and accidentely reformatted my boot partition is there a fix for this or am I completely hosed now?
bartimeus said:
So I was doing the 'restore to stock' method earlier today and accidentely reformatted my boot partition is there a fix for this or am I completely hosed now?
Click to expand...
Click to collapse
Not hosed at all, all you did was format the internal boot partition. When you insert the sdcard and turn the power on, your Nook will find the boot partition on the Clockwork Recovery sd card and boot to that, enabling you to do a full restore.
Well then there may be something more wrong with my nook. I have performed this 3 times and I am still just stuck at a blank black screen.
Are you sure you wrote the image to the sdcard right? Have you plugged in your nook and let it sit for a while? The Nook does have a pretty strange way of running its battery completely dead. What OS were you running before you went to restore to stock?
bartimeus said:
So I was doing the 'restore to stock' method earlier today and accidentely reformatted my boot partition is there a fix for this or am I completely hosed now?
Click to expand...
Click to collapse
Yes, it is totally effed. Just send me the nook, it's garbage now anyhow.
nootered said:
yes, it is totally effed. Just send me the nook, it's garbage now anyhow.
Click to expand...
Click to collapse
lmfao .
Oh dear god this just happened to me today. Thank you for posting this up.
nootered said:
Yes, it is totally effed. Just send me the nook, it's garbage now anyhow.
Click to expand...
Click to collapse
lolololololololololololol
Sorry. But if the boot partition is corrupt these files wont suffice. You'll need to flash my boot repartiton zip..
Sent from my HTC Desire using XDA App
Hi, thanks for putting this topic up and of course full credit goes to everyone who's been so helpful replying to bricked NC posts.
After 4 days of searching and trying to revive my bricked NC (tried the conventional 8 reboots, power+n methods), I believe I have a unique situation where I:
1) Can't load 128MB/1GB CWR SD ('loading' word appears, then black screen of death appears)
--tested a variation of power + n + up/down arrows (for 2-3mins or more)
--used PC USB / AC to turn device on
--used a Sandisk 256MB/2GB/4GB-CL4 and Transcend 8GB-CL6 uSDs
--used Win7, Ubuntu, EASEUS Partition Master, SD Formatter and another Android device to format the uSDs
--burned the .img using both Win32DiskImager and WinImage
2) Can't load any Froyo/HC SD roms (same results as above)
--same conditions as above
--plus tried every available version of NookieFroyo/HC out there
3) Can't access ADB at any given point. devmgmt.msc does not show any hardware with any VID of 2080. When the NC is powered on by USB, windows detects it and chimes, but that connection disconnects instantly.
Simply put, how it happened was:
OOBE -> BN 1.01 -> Autonooter -> block OTA -> Root + gApps > Rom Mgr'd CWR into eMMC -> HC v4 SD -> gApps -> manual su -> dalingrin's 1.1ghz oc kernel -> reboot success > checking on symlinks -> sudden auto-reboot to stock -> reboot done -> HC loads ok -> blacks out, unable to reboot anymore.
Has anyone else encountered this scenario? In my searches I've not come across anyone with this failure. Is it possible that my CPU has fried due to the OC to 1.1?
P.S. Sam, not able to try your methods as I'm not able to even boot anything from the SD.
I'mm in the same boat (nook) tried everything here as well as a similar guide on androidtablets and nothing. I can't boot at all. No power on, just a black screen. Any help at all would be welcome.
samuelhalff said:
Sorry. But if the boot partition is corrupt these files wont suffice. You'll need to flash my boot repartiton zip..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Ya, I realized that I forgot that, I'll add it in when I get home today, Thanks.
I flashed the 1.1 CWR image and all is fine now.
RileyGrant said:
Ya, I realized that I forgot that, I'll add it in when I get home today, Thanks.
Click to expand...
Click to collapse
The second link in your original post has a link to it as part of step 5.
It took a couple times of me re-writing the CWR image before I could get it to boot. Now I have it booting into CWR but when I flash the 1.0.1 recovery the nook refuses to boot. Any ideas?
edit: I am removing the micro SD before I reboot
edit 2: sam's repartition boot FTW....I think
LocalStain said:
I'mm in the same boat (nook) tried everything here as well as a similar guide on androidtablets and nothing. I can't boot at all. No power on, just a black screen. Any help at all would be welcome.
Click to expand...
Click to collapse
Glad you found this, it was my next recommendation after the charge break.
Sent from my LogicPD Zoom2 using Tapatalk
How about a dummies guide to the dummies guide for the dummies?
Or, better, WTF! ITS BRICKED!
Already did all the things suggested. Twice. Purchased last Nook Color from Best Buy yesterday, brought it home, charged it to 100%, played with it and ran Auto-Nooter 2.12.25. When I plugged in the cable to boot, it came up with the battery low-wait 15min screen. (Battery was at 100%) Tried again, same thing. Re-flashed Auto-Nooter and tried again, black screen. Nothing. Bricked. What I do get is a black screen with a flash of backlight every 20 seconds or so. Tried to re flash Auto-Nooter and boot, nothing.
Today same story, just wasted 5 hours trying: Auto-Nooter, Clockwork Recovery image, Nookie-Froyo, complete restore-1.0.1.......nothing brings up any life in the nook.
Suggestions? (Ready to return......)
Cant boot to SD
I am running the HC v4 flashed rom and I have tried numerous .img files. It is like it doest see the boot image I just created and boots into Honeycomb everytime? Any thoughts or help please sorry I am a noob.
< snip >
RileyGrant said:
Clockwork Recovery will begin flashing the stock image to your internal memory. After a few minutes, the process should complete and you will see a message that says 'Done. Installation Complete.' From here you should remove your sdcard and navigate back to the main menu. Select the 'Reboot Now' option.
Click to expand...
Click to collapse
< /snip >
After spending the better part of four hours trying to solve a fatal error with my reverted-to-stock NC, I ran across the fix for the problem.
First of all, the problem: After diagnosing a bad NC USB cable that was causing USB device mounting issues within Windows, I began to encounter a fatal error modal dialog that stated, "Your NOOKcolor encountered a problem that requires a system restart" at the home screen. No matter what I did in terms of formatting & re-imaging, the message remained. In an effort to fix it, I decided to restore to stock 1.1 using a bootable CWR SD image. After following the instructions to the letter, including formatting /System and /Data after shooting the stock 1.1 image onto the NC, the message persisted. I then attempted to back-rev to 1.01 and 1.0, with similar results.
I suspect that what happened to me was that during the process of diagnosing the USB cable issues, I booted from a uSD card that had AutoNooter 3.0 on it, and interrupted the process mid-stream, thus causing data or partition corruption. I'm not a Nook expert, so I'm not certain of this, but based on my general experience level, that's what it 'felt' like.
How did I finally recover? As a last step to the standard revert-to-stock process, after rebooting from CWR, I used a three-finger salute to reset the device. It was only after I did this that the fatal error disappeared.
Just thought that I'd post this in case anyone has a similar experience and is desperate for something else to try.
DS

autonooter 3 fails

I went to update to use autonooter 3.0.0 with nook 1.1.0 software. I went through the process of installing the autonooter 3 and it booted up with the Android splash screen but it kept replaying the android sequence (spelling android) and it would keep restarting sometimes not getting through the entire spelling of android.
I went to reset to factory defaults and now it constantly reboots after "installing a new software update is being installed..." completes. Autonooter no longer boots it justs sits blank forever.
Please help!
hmmm...
Autonooter seemed to work for me. I just had to make sure that I was on stock 1.1 and it worked.
Try to obtain another microSD card. A 1GB will work just fine for the Autonook img.
Also, I would download another copy of the image. What you are going through seems to be a bad image either burned to the microSD or from the source.
Just my 2 cents.
I am sure that it works but for some reason I seem to be in some exception case and I need input how to get out of this mode. My nook is essentially bricked right now.
Have you tried to restore to stock using these instructions?
http://nookdevs.com/Flash_back_to_clean_stock_ROM
I could not get the 8 times failed boot to happen, no matter what the nook boot always happens, I could not get ADB to recognize the device to for the failed boot, I tried the new SD card and image. I give up. I bought it from BN last week so I will just exchange it. thanks for the help.
I have the same issue. The Nook loops the boot screen. The first time it gets through the boot animation afterwards it stops at AND then it pukes. I'm going to try taking it back to stock.
To all of you stuck in this boot loop use my guide posted here to return to stock.
It even includes the link to decadences pre-rooted 1.1 so you can use that instead of flashing back to stock 1.0 or 1.0.1. Good luck and have fun!
Note: Make sure to format /data /system and probably /boot if you are going to flash one of these. Its always best to start from a clean build.
Try the CWR bootable SD...?
quickwitt said:
I have the same issue. The Nook loops the boot screen. The first time it gets through the boot animation afterwards it stops at AND then it pukes. I'm going to try taking it back to stock.
Click to expand...
Click to collapse
Try this... if you have 2 SD cards...
1) Download iMonster's bootable CWR image... (1GB card should be plenty)
2) Download the stock kernel/image from XDA forums and copy onto card #2
3) Using the bootable imaged SD, hold the "n" + power to boot up... you should see two crossbone/skulls image and in-between them, the words "loading"
4) Once it boots into CWR, go to "install from sd"
5) Select the stock image from the SD card...
It should boot back up into stock. Then try the nooter again... try to re-download the file, re-image, and start process over.
Out of curiosity... did you get your nook before or after the who "temporary pulling off of the shelves" incident? I'm wondering if these devices have been reworked at their factory? I know there have been articles that mention that this is just a rumor... BUT you never know.
I used winimage to write the 1.1 image here to an sd card
http://forum.xda-developers.com/showthread.php?t=945838
Put the sd card in the Nook and rebooted. It booted into CWR, I followed the onscreen instructions and now I'm back to stock 1.1.
Reflashed Nooter 3.0.
Back in business.
hvuong2 said:
Try this... if you have 2 SD cards...
1) Download iMonster's bootable CWR image... (1GB card should be plenty)
2) Download the stock kernel/image from XDA forums and copy onto card #2
3) Using the bootable imaged SD, hold the "n" + power to boot up... you should see two crossbone/skulls image and in-between them, the words "loading"
4) Once it boots into CWR, go to "install from sd"
5) Select the stock image from the SD card...
It should boot back up into stock. Then try the nooter again... try to re-download the file, re-image, and start process over.
Out of curiosity... did you get your nook before or after the who "temporary pulling off of the shelves" incident? I'm wondering if these devices have been reworked at their factory? I know there have been articles that mention that this is just a rumor... BUT you never know.
Click to expand...
Click to collapse
I think the "pulling off the shelves" is a myth but I purchased my nook the 1st week of January. I've loaded every version of Autonooter as well as Froyo and Honeycomb without incident until now. I'm sure I screwed something up in the process or just had a bad write to the sd. I'm pleased that you can't really brick this great little tablet.

[Q] Nook Color Won't Boot-Been trying stuff

I have a Nook Color that was running the Cyanogenmod nightlies. After shutting it down, it would not boot again.
Since it still boots into recovery, I tried reflashing cyanogenmod, a recovery zipp that was supposed to restore the boot partition, dding boot.img and system.img to the internal memory, a total wipe of every partition, flashing with the latest version of clockwork, along with .7, the stuff mentioned here http://forum.xda-developers.com/showthread.php?t=949699, and flashing "nook color return to stock".
Although all flashes completed successfully, the device still won't boot without the sd card. Is there a method I'm missing?
Been in the same boat myself as well as many others. I found that to get it to boot correctly again do this. Use this link (http://forum.xda-developers.com/showthread.php?t=914690) and downlaod the "Remove CWR" file, you'll also want to download the repartition-boot-with-stock.zip which is the last link in the OP right under the Remove CWR link. Once you download each file copy them to a bootable sdcard. Then pop the bootable card into the nook and power it up to into CWR off the sdcard. After that install the Remove CWR zip first, then follow up by installing the repartition-boot-with-stock.zip. Once all is said and done power the Nook off by holding the power button in. take the sdcard out and then power it on. Odds are it will get stuck again but you should be stuck on the N screen. If so power it off and then put your bootable sdcard back in the device so you can start fresh reinstalling CM7 & gapps.
If you repartition boot, cwr will be removed in the process. No need for the second file..
Sent from my HTC Desire using XDA App
samuelhalff said:
If you repartition boot, cwr will be removed in the process. No need for the second file..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
In theory it should and you are totally right on but I've personally seen it where even after repartitioning the boot it still will not boot correctly for whatever reason. That said personally I've found it just as easy to take the extra step to make sure it gets cleared up as it takes a matter of a couple extra seconds to do it.
Thanks, I'll try that.
Followed instructions exactly, but the thing still won't boot. I must have F'd up my /boot partition pretty badly.
Edit: Wiped every single partition and cache, then flashed, now it works. Thanks guys
I am having this same problem and have a question about the options to fix it. I have CM7 stable on my NC and it worked untill I formatted the SD card and rebooted.. now it just gets stuck at "touch the future of reading" screen.
Is it possible to remove CWM without harming the CM7 install? and still be able to boot to CM7?

[Q] How to get CM7 after 1.1 Root, directions?

I had my 1.1 NC rooted using the GMPower method (there's also the monster rootpack?). I once tried to install CWM from the market but that caused an infinite reboot into recovery. Since then, a lot of things changed and I'm clueless on how to proceed especially with CM7.
I would like to install CM7 but which method is applicable. I found two:
http://forum.xda-developers.com/showthread.php?t=960542&page=16
http://forum.xda-developers.com/showthread.php?t=1000957
My questions are will these work for my 1.1 rooted NC (GMPower method)? What's the difference and which is better? Can the latest CWM be installed onto my NC without causing the infinite reboot?
I appreciate any help.
This link may help: http://forum.xda-developers.com/showthread.php?t=960542&page=16
Second link in your post for installing CM7 on SD card.
I did that, infinite loop. When I install CM from the sd card, it installs fine, but as soon as it reboots, it goes into CM 3.0.0.5 from the internal memory. Should I just wipe /boot?
definitely don't wipe /boot or it won't boot up. So what process are you following exactly? You created a bootable SD card with CM 3.0.10 right? You'll need that for a ext4 system (which CM7 is). That's step #1 in the post nthesame already linked to. Then copy the CM7 .zip (the one for encore final, should be about 90mb) to the SD card and install it using CM recovery (install .zip from location on sd card). If you do this, it will boot into CM7.... make sure to remove your SD card though after installing it, as the default is to boot to SD if it finds any boot files on it.
I used an 8gb image from one of those running 3.0.0.6, not 3.0.0.10, so I'd assume it was good.
It used to be a dual boot, but I removed that and just tried to overwrite stock with no success.
When I tried to install first, I followed the wiki to the tee, nothing.
I just got my nook today, and am about to start the process tonight... but from what i have read so far, your trouble may be that you used CWM 3.0.0.6 vice 3.0.10... seems something was changed to stop the infinate loop...

[Q] Problem with rooted Nook and ROM Manager

Hi all,
I hope this is the right place to put this - I'm not sure if it's a Nook Color, Cyanogenmod, ROM Manager, or Clockworkmod issue. I just rooted my NC to CM7 using Clockworkmod and it seems to work fine. I tried installing the GoogleApps .zip file at the same time. It said it was successful, but I don't see any of the Google apps in the apps drawer.
So, I went to ROM Manager to try and fix this. When I first opened ROM Manager it said I needed an SD Card installed to use it (I had removed it after the successful flash). So I inserted the card and mounted it in Settings->Storage and tried again. Now when I click on anything it says "You must have ClockworkMod Recovery installed before continuing! Install the recovery through ROM Manager first."
If I click the Install button, the dialog closes and nothing happens. If I click the menu option "Flash ClockworkMod Recovery" the title of the screen (ROM Manager v4.2.0.0) flashes for a split second. That's it. Nothing is installed.
If I reboot while holding the upside-down U button I eventually get an "Update failed!" screen that looks like it comes from the standard Nook UI. If I try to reboot into recovery using the Power button it just reboots as normal.
I've found a large amount of resources online regarding the "unable to reboot into recovery" issue, but I feel like I don't know enough about what I'm actually doing to implement them. I also don't know how the inability to flash ClockworkMod fits into this. It's especially strange how selecting the option to flash it actually does nothing.
Anyone have ideas?
[EDIT]
Since I'm a new user and apparently can't post links, I followed the instructions on the Cyanogenmod site's wiki.
SkittlesAreYum said:
Hi all,
I hope this is the right place to put this - I'm not sure if it's a Nook Color, Cyanogenmod, ROM Manager, or Clockworkmod issue. I just rooted my NC to CM7 using Clockworkmod and it seems to work fine. I tried installing the GoogleApps .zip file at the same time. It said it was successful, but I don't see any of the Google apps in the apps drawer.
So, I went to ROM Manager to try and fix this. When I first opened ROM Manager it said I needed an SD Card installed to use it (I had removed it after the successful flash). So I inserted the card and mounted it in Settings->Storage and tried again. Now when I click on anything it says "You must have ClockworkMod Recovery installed before continuing! Install the recovery through ROM Manager first."
If I click the Install button, the dialog closes and nothing happens. If I click the menu option "Flash ClockworkMod Recovery" the title of the screen (ROM Manager v4.2.0.0) flashes for a split second. That's it. Nothing is installed.
If I reboot while holding the upside-down U button I eventually get an "Update failed!" screen that looks like it comes from the standard Nook UI. If I try to reboot into recovery using the Power button it just reboots as normal.
I've found a large amount of resources online regarding the "unable to reboot into recovery" issue, but I feel like I don't know enough about what I'm actually doing to implement them. I also don't know how the inability to flash ClockworkMod fits into this. It's especially strange how selecting the option to flash it actually does nothing.
Anyone have ideas?
[EDIT]
Since I'm a new user and apparently can't post links, I followed the instructions on the Cyanogenmod site's wiki.
Click to expand...
Click to collapse
Question, did you have clockworkmod installed on your sd when you flashed cm7 or was it installed internally? Can you boot into recovery with rom manager? If clockwork is on sd, find the newest clockwork zip and flash it with your card internally. That should allow you to update to the newest version in Rom Manager. Try reflashing gapps.
bdcrim said:
Question, did you have clockworkmod installed on your sd when you flashed cm7 or was it installed internally? Can you boot into recovery with rom manager? If clockwork is on sd, find the newest clockwork zip and flash it with your card internally. That should allow you to update to the newest version in Rom Manager. Try reflashing gapps.
Click to expand...
Click to collapse
Clockworkmod was installed on the SD card.
I cannot boot into recovery using ROM Manager. It just restarts the device as normal.
I believe I have the latest CWM because I grabbed it from their website yesterday (4.2.0.0). How do I flash it internally? That's what I was attempting to do with ROM Manager. I followed the steps listed in thread #922870 on this forum (still can't post links) and I believe that results in CWM on internal memory, but ROM Manager still behaves the same way.
I did reflash gapps twice, but there is still no Maps, Market, Gmail, etc.
I just noticed something else. When I mount my SD card on the NC it shows up as empty: /mnt/sdcard has no contents. Does this indicate an error with the SD card and/or partitions? I am using the 8 GB image of CWM on my 16 GB card (because there is no 16 GB version).
SkittlesAreYum said:
I just noticed something else. When I mount my SD card on the NC it shows up as empty: /mnt/sdcard has no contents. Does this indicate an error with the SD card and/or partitions? I am using the 8 GB image of CWM on my 16 GB card (because there is no 16 GB version).
Click to expand...
Click to collapse
Your SD card has clockwork burned as an image which the nook cannot read. You can format the card later for use (go to nookdevs website). I am attaching a zip file for clockworkmod 3.0.1.0 (credit goes to Mistar Muffin). Put that on your SD card, insert it into the nook and boot it up. It should take you into recovery. You can then flash the zip file and get Clockworkmod on your emmc. You should be able to update to the new version 3.0.2.8 from Rom Manager at that point. I think the nook is confused with the absence of Clockwork internally. As far as your rom goes, I would boot into recovery when the Clockworkmod issue is resolved and reflash the CM7 build, reboot, go back into recovery and flash the gapps. You can repeat the process with an overclocked kernel if you choose. This zip is a file that floated around the forum for awhile. It was removed when Clockworkmod got an update. I have used it on my nook. It should be safe. Good luck
bdcrim said:
Your SD card has clockwork burned as an image which the nook cannot read. You can format the card later for use (go to nookdevs website). I am attaching a zip file for clockworkmod 3.0.1.0 (credit goes to Mistar Muffin). Put that on your SD card, insert it into the nook and boot it up. It should take you into recovery. You can then flash the zip file and get Clockworkmod on your emmc. You should be able to update to the new version 3.0.2.8 from Rom Manager at that point. I think the nook is confused with the absence of Clockwork internally. As far as your rom goes, I would boot into recovery when the Clockworkmod issue is resolved and reflash the CM7 build, reboot, go back into recovery and flash the gapps. You can repeat the process with an overclocked kernel if you choose. This zip is a file that floated around the forum for awhile. It was removed when Clockworkmod got an update. I have used it on my nook. It should be safe. Good luck
Click to expand...
Click to collapse
Thanks for your help; unfortunately this did not work. Nothing has changed. I placed the zip file in my SD card that already has CWM imaged. I went to "Install zip from SD card" and installed the zip. It completely successfully. Then I rebooted and entered ROM Manager, which told me I needed the SD card back in. I mounted the SD card and am encountering the same issues as before.
What could I have possibly done to mess this up? I followed all the steps listed on the Cyanogenmod website and they never mention anything about flashing CWM internally. Another question - why do I need the SD card for ROM Manager if that app is downloading things from the internet?
Thanks!
SkittlesAreYum said:
Thanks for your help; unfortunately this did not work. Nothing has changed. I placed the zip file in my SD card that already has CWM imaged. I went to "Install zip from SD card" and installed the zip. It completely successfully. Then I rebooted and entered ROM Manager, which told me I needed the SD card back in. I mounted the SD card and am encountering the same issues as before.
What could I have possibly done to mess this up? I followed all the steps listed on the Cyanogenmod website and they never mention anything about flashing CWM internally. Another question - why do I need the SD card for ROM Manager if that app is downloading things from the internet?
Thanks!
Click to expand...
Click to collapse
Try uninstalling and reinstalling Rom Manager. Dont know if that will help or not.
bdcrim said:
Try uninstalling and reinstalling Rom Manager. Dont know if that will help or not.
Click to expand...
Click to collapse
How would I reinstall ROM manager? I don't have any sort of Market on the device.
Best best bet is going back to stock and trying from scratch
SkittlesAreYum said:
How would I reinstall ROM manager? I don't have any sort of Market on the device.
Click to expand...
Click to collapse
Sorry, my bad. I forget that Rom Manager is part of the CM7 package. You should not need the sd card for Rom Manager to work properly. I am not sure why it is calling for it. Can you reboot into recovery with the power+n method, not the SD card? If you can do that, it tells me clockwork installed correctly. If you can get there, I would do your formats (data, system) and reflash the rom. Another option, if Titanium Backup is part of the rom package try to wipe data in rom manager and give it another try. You may can do that in manage applications (I don't have my nook with me). The link below may or may not help. Look at option 3. The 3.0.1.0 zip it is calling for is the one I sent you prior. I am about out of options. Good luck.
http://forum.xda-developers.com/showpost.php?p=12674682&postcount=355
AHA! I solved it, and it wasn't directly an issue with anything except my stupidity. I was connecting to my company's guest wireless, which as it turns out requires a username/password before you get anything other than the login screen. That is why the ROM manager was failing to flash itself - it had a worthless wifi connection. When I switched to another wireless access point it works just fine.
Thanks for your assistance bdcrim! Sorry it wasn't a more satisfying conclusion.
SkittlesAreYum said:
AHA! I solved it, and it wasn't directly an issue with anything except my stupidity. I was connecting to my company's guest wireless, which as it turns out requires a username/password before you get anything other than the login screen. That is why the ROM manager was failing to flash itself - it had a worthless wifi connection. When I switched to another wireless access point it works just fine.
Thanks for your assistance bdcrim! Sorry it wasn't a more satisfying conclusion.
Click to expand...
Click to collapse
Thats okay, glad you got it going. Made me dig a bit, which probably helped both of us be a little more educated for future issues. Have a great day.

Categories

Resources