I rooted my Nook Color, originally v. 1.3 (with Manual Nooter-4.5.18, -4.6.16). The rooting appeared to be successful, but was unstable in that it wouldn't survive a power-cycle. Eventually, I gave up, and decided to revert to straight B&N Nook. I did this by clearing data, root, system, and running "nook-complete-restore-1.0.1.zip. That worked, but with a couple of big flaws: 1) I now cannot "see" the NookColor internal rom when I plug its usb port into my computer! Cabling, computer software, etc., is in order, since when I have a microSD installed on the NC, it does mount on the computer (Mac), and allows file transfer to-and-from. (Also "invisible" on Linux and MSWin machines.)
2) A consequence is that I cannot copy "generic-sdcard-v1.3.img.zip" to NC for purposes of "upgrading" back to v.1.3; also when I attempt to download any archived books from N&B: the download starts, then abruptly stops, presumably because it can find no internal rom in which to store them.
In short, I've bricked the unbrickable NC! Anybody have any ideas?
Lol you cannot brick the Nook. You are using a firmware that your Nook was not designed to handle.
Flash this with clockwork to update to 1.2 and regain your internal storage: http://forum.xda-developers.com/showthread.php?t=1050520
---------------------------------
Sent from my LG Optimus V using Tapatalk
Can you revert straight to B&N 1.3 stock ROM? Why went all the way down to 1.0.1?
Indeed, koopakido8, it takes more of a Philistine than me to brick a NC! Your diagnosis and remedy were both spot on. Thanks
Related
I was reading this thread [RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD (1.1 Compatible!). But, since I am new to this forum I couldn't post there. I hope this is the right place to ask for help.
I upgraded my NC to 1.1.0 successfully. I put Autonooter 3.0.0 on a MicroSD card. With my NC off, I inserted the card and then plugged the NC into my PC. I got a black screen for over 5 minutes. It looked like nothing was happening, so, I disconnected the NC, removed the SD card and tired to turn the NC on. No joy, it won't turn on and won't boot at all. I think my Nook is bricked. Any ideas what went wrong?
I've read some other threads about similar problems. It seems there is a fix to get it back to stock (1.1.0). I hope the Recovery thread I mentioned above is where the answer lies. But, I'm a bit confused and don't want to make any more mistakes. I only have one 4GB SD card at my disposal right now.
My questions are as follows:
1. Is my NC bricked beyond hope of recovery?
2. If I follow the procedures in this post can I get it to boot from the sd card even though it won't turn on at all?
3. What is the difference between the Rootpack and the Clockwork Recovery Image?
4. This is the confusing part. Should I download the RootPack? Or, should I download a bootable Clockwork SD card (128mb, 1gb, 2gb, 4gb, 8gb)
5. Since I only have a 4GB card, what should I choose?
6. Should I opt for 1.0.1, or 1.1.0 where it was still working.
7. Can I get all of this on one 4GB card?
8. Is there anything else I should be weary of before starting this procedure?
If i have posted this in the wrong place, I am sorry. But, I hope someone can clear things up for me. Thanks.
This is the right place to ask general questions.
1. Most certainly not.
2. Yes, using a bootable CWR SD is the way to go.
3. Totally different. The Rootpack is the name given to a package that helps you root your Nook. CWR image is a recovery image. That means you can boot to this recovery utility and apply changes to you NC (like repairing stuff, making backups, etc.).
4. An image will adapt to the drive. If you have a 4GB SD and burn (dd) a 1GB image to it, your SD will suddenly present itself as a 1GB SD. If you format it with the right tool, your SD will be 4GB again. So don't panick, if it says 1GB after burning, it's jut "adapted to the image". You haven't lost any disk space.
5. 1GB would be enough, but you can go up to 4GB image with a 4GB.. It could sometimes be a problem to apply an image which is the exact same size as the drive. I would use th 1GB, which is plenty for what you are going to do.
6. That's up to you. Both should work.
7. Yes.
8. Just read threads exhaustively before attempting anything..
So what you need to do is read threads about this CWR Bootable img to learn how to burn it to your SD.
Then, find the appropriate .zip files to flash (apply) (1.1 recovery and 1.0.1 are available in dev section.
Copy them to root of SD.
Boot with the SD Card and apply zip files from SD.
If your NC should still have problems booting, you can also apply a boot repair zip file, that you will find on my Nook Color restore to stock tread in dev..
Sam
His Rootpack wont work on 1.1.0 You should have seen that in his instructions. It will only block 1.1.0 and fake it. You need to see this thread to fix your nook. It is 100% NOT bricked, just messed up atm. You can fix it tho. Read here:
http://forum.xda-developers.com/showthread.php?t=949699
Thanks for thr quick reponse Sam. I'm at work now, but will be able to use your suggestions later this afternoon\tonight. So, if I get a 1gb CWR image on my 4gb sd card, plus the 1.1.0 zip file and put it in the root of the sd card, the Nook should boot up even though I can't turn it on now? How long typacally will it take to boot up? What should I expect to see?
I will post results after I try the procedure. Thanks again!!
Thanks Thiboi69. I have printed out the instructions from the link you sent and will follow them to the T. I'll post results later.
It will work. I have never heard of a 100%bricked NookColor to date. And I have read 1,000's of posts here over the past 4 months. IT is just your boot partition that is messed up and B&N made it check the sdcard first for a Boot partition, then fall back to eMMC. Thank you B&N !!!
I downloaded all the files, wrote them to my sd card, and put it in the Nook. When I connected the Nook to my pc, I got a messaage the the battery was too low to turn on. So, I took the sd card out, and put the Nook on charge. After a while, it turned on, booted up and when I checked my OS, I found that I had
version 1.1.0. Apparently, my attempt to root with autonooter 3, never got installed, partially or completely. And, my battery probably got to low to turn the nook on. So, I didn't need to use CWR after all. I apologize to all who have tried to help me. But, all replies were good and contained useful info.
Now, my question is: Should I try to use Autonooter 3 again, or is there an easier
(more foolproof) way to root v1.1.0?
I just got a nook last night with the sole intention of hacking it - and did so in a matter of minutes. Autonooter couldnt be easier! When you get to the part of putting the SD card in the nook and connecting it to USB to make it boot, just plug it in and go get a cup of coffee. Don't unplug or touch anything until it boots up by itself. At 1st I thought it wasn't doing anything as I didn't see a clockwork mod screen come up or anything, but just be patient and it'll tell you when it's done. Just make sure it's pretty well charged when you do it - mine was about 80% or so.
Honestly after less than a day of the rooted stock 2.1 Eclair OS, I'm ready to drop a fully customized Froyo or Gingerbread image on this thing. Autonooter it 1st and run it for a few days 1st and see what you think. I'm still learning the ins and outs of tinkering with this thing, but so far it seems much easier than the Epic and Moment I've been beating on. Seems pretty well unbrickable too thanks to the boot to SD 1st option B&N baked into this puppy.
jostarr said:
I was reading this thread [RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD (1.1 Compatible!). But, since I am new to this forum I couldn't post there. I hope this is the right place to ask for help.
I upgraded my NC to 1.1.0 successfully. I put Autonooter 3.0.0 on a MicroSD card. With my NC off, I inserted the card and then plugged the NC into my PC. I got a black screen for over 5 minutes. It looked like nothing was happening, so, I disconnected the NC, removed the SD card and tired to turn the NC on. No joy, it won't turn on and won't boot at all. I think my Nook is bricked. Any ideas what went wrong?
I've read some other threads about similar problems. It seems there is a fix to get it back to stock (1.1.0). I hope the Recovery thread I mentioned above is where the answer lies. But, I'm a bit confused and don't want to make any more mistakes. I only have one 4GB SD card at my disposal right now.
My questions are as follows:
1. Is my NC bricked beyond hope of recovery?
2. If I follow the procedures in this post can I get it to boot from the sd card even though it won't turn on at all?
3. What is the difference between the Rootpack and the Clockwork Recovery Image?
4. This is the confusing part. Should I download the RootPack? Or, should I download a bootable Clockwork SD card (128mb, 1gb, 2gb, 4gb, 8gb)
5. Since I only have a 4GB card, what should I choose?
6. Should I opt for 1.0.1, or 1.1.0 where it was still working.
7. Can I get all of this on one 4GB card?
8. Is there anything else I should be weary of before starting this procedure?
If i have posted this in the wrong place, I am sorry. But, I hope someone can clear things up for me. Thanks.
Click to expand...
Click to collapse
Joe, I would recommend downloading the 1gb rootpack image and a restore to stock file. Make your bootable clockwork recovery image, place the resotre to stock file on the sdcard, turn your nook off, insert the sdcard, power on and flash the file. All this info and more can be found in my thread here:
http://forum.xda-developers.com/showthread.php?t=949699
Thanks for your suggestion Riley, please take a look at my post # 7 above. Seemd my NC
had a low battery. When I charged it, all was ok. It booted up and I was back in 1.1.0.
But, I just now tried autonooter 3.0.0 again. When I pluged thr NC inyo my PC, I got some sort or warning message. I hit cancel and waited a few minutes. The message came up again. It said the device was not recognized. I unplugged, removed the card, and my fully charged NV won't turn on. And, windows explorer can not read the sd card. This is basically what happened yesterday to cause my panic. The sd card had all the files befor I inserted it into the NC. Now, it's unreadable and I can't turn on or boot the NC again.
Is it autonooter 3.0.0, or the card, or the Nook, or me?????
One correction to post # 10. I can read the sd card in windows explorer. But my NC won't turn on.
With sd card out of the Nook, I get a "Welcome to the Found New Hardware Wizzard"
What does this tell anyone about the condition of my Nook?
I am having a problem and don't really know what to do. When I start my NC its stops at the N screen and goes no further. I've tried a lot of the different ways to get it back to stock with no luck. When I try to write CWM to my SD card with win32 it either doesn't have enough room to put the stock file on the zip with it or when I open the SD card it says the card needs to be formatted. The file is a tr.gz or something like that is there a step between that I am missing or just download the CWM and write to SD using win32? I also tried adb with no luck. I am very new to rooting so any super dumbed down instructions would be greatly appreciated.
Sent from my ADR6300 using XDA App
You can put the rom image to a separate SD card. Just swap it after you boot up from cwr. I did it before for flashing froyo to emmc.
Sent from my PC36100 using XDA App
72chevy2k2 said:
I am having a problem and don't really know what to do. When I start my NC its stops at the N screen and goes no further. I've tried a lot of the different ways to get it back to stock with no luck. When I try to write CWM to my SD card with win32 it either doesn't have enough room to put the stock file on the zip with it or when I open the SD card it says the card needs to be formatted. The file is a tr.gz or something like that is there a step between that I am missing or just download the CWM and write to SD using win32? I also tried adb with no luck. I am very new to rooting so any super dumbed down instructions would be greatly appreciated.
Click to expand...
Click to collapse
Have you followed the restore-to-stock procedure outlined in this thread?
http://forum.xda-developers.com/showthread.php?t=914690
Just a noobish advise!
After configure everything and become accustomed to some of the NC behaviors this should not matter, but I remember at my first attempts at rooting the NC, using a Win7 PC was much easier than using Win XP or iOS devices. Might fix your 'not recognized' problems, sd card recognition and formatting problems etc.
It has CWM on it. I can get it to recovery but it will not recognize the SD or not mount it and I go to mount it in the menu and it says something like can not mount SD card so I have been trying to do the CWM SD burn but I keep getting the above errors I am on a vista computer so I will try it on my windows 7 one and see how that goes. And the different SD card one I will try that as well after work thank you for the help.
Sent from my ADR6300 using XDA App
RickOSidhe said:
Have you followed the restore-to-stock procedure outlined in this thread?
http://forum.xda-developers.com/showthread.php?t=914690
Click to expand...
Click to collapse
Yes I did try that one I put the nookie froyo on the SD and put it I'm my turned off NC and plugged it in to my computer and it sat at the N screen forever and after a while I took it off and it was still in the same state could the CWM be the problem?
Sent from my ADR6300 using XDA App
I'm not sure what posts 13 thru 18 have to do with my problem???
Just didn't feel like starting a new thread for the couple of questions I had along the same line as yours.
Sent from my ADR6300 using XDA App
I was dicking around with the Rom Explorer (can't remember the exact name) app that comes with CM7 and I installed CMR onto my Nook. Problem is, it installed the 3.0.0.5 version over the previously installed 3.0.0.6, which I didn't know until I rebooted. When I did, it booted straight into Recovery version 3.0.0.5 and threw up the following errors:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Fine, no problem. I'll just flash 3.0.0.6 on and... ADB won't work.
Okay, new tactic. I'll just wipe /system, /data, /cache, and reinstall CM7, which might fix recovery. Only...
E:Can't mount /sdcard
Ah.
Well, no problem, B&N wisely made the NC basically unbrickible to stop returns from idiots like me. I'll just boot 3.0.0.6 from my sdcard and flash CM7 again. Yay, it works! Only... it doesn't quite. It refuses to show up in ADB, and the root that I have is buggy. Titanium backup offers to install a newer version of su, but I already have the latest. I double check by trying to rename a file in /system with Root Explorer. No dice.
Well wonderful. Time to start from scratch. So I try all the return-to-stock methods in this thread, but none of them work.
At this point, I'm not really sure what I messed up... obviously flashing the older recovery image is a big part of it, but I'm completely flabbergasted as to why I apparently can't overwrite it with ANYTHING.
Does anyone have any ideas how I can fix this?
Sigh. I know this is the wrong section, but I don't have enough posts to post in the development subforum... certainly someone must have an idea of what I can do? Or am I completely SOL?
Finally got back to stock using brian21's stock 1.1 image! Now to start all over again.
lelandjs said:
Finally got back to stock using brian21's stock 1.1 image! Now to start all over again.
Click to expand...
Click to collapse
Glad you got it working again.
Isn't the Nook a wonderful device. It makes your world shine when you first root it. And then comes CM7. And even a HC preview. And then of course it throws a wrench in everything when we aren't paying attention to details and our happiness is turned into frustration.. and from the frustration brings us some actual knowledge.
I find the best part about my Nook is all the great things that I have learned along the way. From never touching an android platform to actually starting to learn some linux along the way.
Just my 2 cents.
racks11479 said:
Glad you got it working again.
Isn't the Nook a wonderful device. It makes your world shine when you first root it. And then comes CM7. And even a HC preview. And then of course it throws a wrench in everything when we aren't paying attention to details and our happiness is turned into frustration.. and from the frustration brings us some actual knowledge.
I find the best part about my Nook is all the great things that I have learned along the way. From never touching an android platform to actually starting to learn some linux along the way.
Just my 2 cents.
Click to expand...
Click to collapse
Not gonna lie, I was... underwhelmed by the rooted default Nook firmware. It just ended up being too slow. But CM7?
The NC actually marks my return to Android; I was slinging roms on my G1 back in the day (hence my vague knowledge of rom flashing).
Can't wait for a Honeycomb build, though I'm happy enough with CM7 for the moment. This really is a great tablet; the perfect size for taking with you to work and reading some comics on the subway. I liked the iPad but it (and other 10" tablets) was just too large for practical use.
i have the same problem,
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
is this due to the CWR version, I have 3.0.0.5. I have CWR installed on the internal as well as booting it from sd.
were you able to format system and data under mount and settings because i get an error when doing so. Seems like this is a crucial step. This stops me from completing the steps necessary to flashing the file. If I try flashing the zip without formatting, my install aborts and gives me an error.
Sam is actually helping me sort out when he can but we still haven't been able to get it going. My emmc is corrupt is all i know and needs reformatting but abd won't even allow.
I am having the same problem as the post above me. I am a noob any help would be greatly appreciated.
lelandjs said:
Can't wait for a Honeycomb build, though I'm happy enough with CM7 for the moment.
Click to expand...
Click to collapse
Until now and you are still waiting for HC? Seriously?
wendellc said:
My emmc is corrupt is all i know and needs reformatting but abd won't even allow.
Click to expand...
Click to collapse
I had a very good double-boot configuration from NC stock 1.0.1-cm7 on a 32Gb SanDisk card. At that point, I could easily sideload media into the NC and the SDCard. I thought that I had successfully upgraded to the NC to 1.4 and then installed the triple-boot configuration stock/cm7/cm9 from the SDCard. The NookColor showed up in XP Pro Device Manager > Hardware. However, I began to run into problems at this point, I can't recall specifically (that was several weeks ago) what these problems were, other than that, after reading the forums here, I suspected that it might have had to do with upgrading the NC stock from 1.0.1 to 1.4. So, I managed to restore the NC 1.4 back to 1.2 (I read that NC stock 1.3 auto-updated if it were the boot). Then I burned the triple-boot back onto to the SDCard. I could access NC 1.2 stock/cm7/cm9 but I could no longer sideload media into the NC. When I take out the SDCard and plug the NC into XP, only two partitions appear as separate drives. The only partition that appears in XP Pro Windows explorer is the "boot" (115MB), with the list of files for the NookColor, it looks like.
I thought that, maybe, this was an acceptable price to pay, this loss of access to the internal 5Gb of the NC but access to the rest of the storage on the 32Gb SDCard. But, I need the NC ebook reader's access to its internal 5Gb storage and the 32Gb storage. When I recently booted into cm9, I got the message "Unfortunately, Trebuchet has stopped" so I tried to use adb to load an .apk into the appropriate place in order to attempt to repair/correct this. This is when I discovered that it seems like my NC emmc has, somehow, been corrupted because it doesn't appear in adb > adb devices. And when I've closed the 5037 connection in TCPView, adb still will not connect.
So, besides no longer being able to access the NC 5Gb storage from inside NC nor being able to sideload into NC, I can't repair the cm9 installation. If the NC emmc has been corrupted, would a simple upgrade to 1.3 repair this? If so, do I put the 1.3 update into the root NC by copying it to the "boot" 115MB drive and then inserting the SDCard into the NC and booting into NC?
Is there a way to repair or restore the NC so that I can sideload files into it?
I've plugged the NC into two other Windows XP machines with similar results, so it's a problem with the NC.
Thank You!
Sorry i didn't read all the details, but you really shouldn't be using such old CWM recoveries.
http://forum.xda-developers.com/showthread.php?t=1469732
boldred said:
I had a very good double-boot configuration from NC stock 1.0.1-cm7 on a 32Gb SanDisk card. At that point, I could easily sideload media into the NC and the SDCard. I thought that I had successfully upgraded to the NC to 1.4 and then installed the triple-boot configuration stock/cm7/cm9 from the SDCard. The NookColor showed up in XP Pro Device Manager > Hardware. However, I began to run into problems at this point, I can't recall specifically (that was several weeks ago) what these problems were, other than that, after reading the forums here, I suspected that it might have had to do with upgrading the NC stock from 1.0.1 to 1.4. So, I managed to restore the NC 1.4 back to 1.2 (I read that NC stock 1.3 auto-updated if it were the boot). Then I burned the triple-boot back onto to the SDCard. I could access NC 1.2 stock/cm7/cm9 but I could no longer sideload media into the NC. When I take out the SDCard and plug the NC into XP, only two partitions appear as separate drives. The only partition that appears in XP Pro Windows explorer is the "boot" (115MB), with the list of files for the NookColor, it looks like.
I thought that, maybe, this was an acceptable price to pay, this loss of access to the internal 5Gb of the NC but access to the rest of the storage on the 32Gb SDCard. But, I need the NC ebook reader's access to its internal 5Gb storage and the 32Gb storage. When I recently booted into cm9, I got the message "Unfortunately, Trebuchet has stopped" so I tried to use adb to load an .apk into the appropriate place in order to attempt to repair/correct this. This is when I discovered that it seems like my NC emmc has, somehow, been corrupted because it doesn't appear in adb > adb devices. And when I've closed the 5037 connection in TCPView, adb still will not connect.
So, besides no longer being able to access the NC 5Gb storage from inside NC nor being able to sideload into NC, I can't repair the cm9 installation. If the NC emmc has been corrupted, would a simple upgrade to 1.3 repair this? If so, do I put the 1.3 update into the root NC by copying it to the "boot" 115MB drive and then inserting the SDCard into the NC and booting into NC?
Is there a way to repair or restore the NC so that I can sideload files into it?
I've plugged the NC into two other Windows XP machines with similar results, so it's a problem with the NC.
Thank You!
Click to expand...
Click to collapse
First, your adb problem with CM9 is because CM9 uses different device ids for the windows usb adb driver than stock or CM7. If you want to know how to fix that, I can quote one of my posts for you.
I think you should take your SD and make a new single CM7 SD. You are getting too complex with triple booting while trying to debug. Then you can see if your emmc media partition is corrupt or not as I said in my other post about mounting drives in windows. Then once you are sure everything is ok with emmc, you can go back to triple booting.
The reason you are seeing 'boot' show up in windows when you plug the NC into windows running stock is the stock looks at partition 1 of an SD for 'sdcard'. On your triple boot SD partition 1 is the boot partition.
If it turns out that your emmc media partition is corrupt, I can help you fix that.
To learn more about fixing your stock if you need to again, read eyeballers thread (the epilogue of the first post).
http://forum.xda-developers.com/showthread.php?p=12797652
By doing the repartitioning he talks about in Dean Gibson's thread you can follow it but instead of going from 1GB media to 5GB media, back up, repartition to 5GB again and you will have a new reformated 5GB media. Then restore your data partition.
votinh said:
Until now and you are still waiting for HC? Seriously?
Click to expand...
Click to collapse
eyeballer said:
Sorry i didn't read all the details, but you really shouldn't be using such old CWM recoveries.
Click to expand...
Click to collapse
Folks, if you look at the dates of these earlier posts you will see they are from February of 2011 not 2012. That's why they were talking about Honeycomb and CWR 3.0.0.5.
leapinlar said:
Folks, if you look at the dates of these earlier posts you will see they are from February of 2011 not 2012. That's why they were talking about Honeycomb and CWR 3.0.0.5.
Click to expand...
Click to collapse
Ahh, my bad, getting old, I guess.
Apologize to OP, beer on me
Hello Everyone,
I don't know if someone posted a thread like this already but I really need some help here. To start off I rooted my NC with auto nooter 2.12 then I went and tried the dual boot and flashed HC v4 2nd edition onto my emmc. Then I foolishly went and installed cwm onto my emmc. HC was giving me some boot up issues so I decided to remove it, I did that successfully and I was back to only auto nooter. I used a bootable cwm sd card and removed the cwm recovery and flashed the 1.01 stock version. But when I went and reverted back to stock my onboard storage is no longer 5gb it's 3.7gb, it's the same amount of 3.7gb when I plug it in to my PC. Does anyone know how I can repartition my onboard storage, or /media so I can get back to 5gb again by either a adb command etc. I'm desperate I'll try anything. Please Help!
Seminoobie, please help. I successfully made a Nook CM7 uSD with the Size-Agnostic instructions using 7.0.2 (thanks dev). Transcend 8gb card. Worked great for three days, now it is stuck on the circle-skater screen. I let it run for a half-hour, no dice.
Running Autnootered 3.0 emmc in 1.1, that works fine. I don't have CWM installed on emmc (I want to avoid this for now to make factory restore/1.2 upgrade easier for autonooter 4), so I have no current access to Rom Manager, if that matters. I've seen some posts suggesting to clear caches with Rom Manager but I assume the uSD caches aren't in internal memory, are they? Other posts suggest partition corruption but the card worked fine before I turned it off and rebooted, and the boot partion shows up on the computer with a card reader just as you would expect.
The last thing I did before this happened was run Titanium Backup to pull the 200 existing apps on emmc onto the CM7 card. I did this by copying the entire full Backup file from a standard sd backup to the computer, then copied that file back to the /sd partition after putting cm7 into usb mode, then running Titanium in CM7. That worked fine, and I even was able to move some of the apps to the virtual SD and they worked.
I could take an hour and burn another card but wondered if I am just missing something to fix this, also if I do burn another card whether I did something wrong in applying Titanium that I should avoid again.
Also wondering if it is worth waiting for a future stable build that addresses the Nook deep sleep/battery drain issue, which seems to be in the works.
If I burn another card and get the same freeze happiness will elude me. Thanks in advance.
I assume you powered down and rebooted. I have had that happen to me and after a fresh reboot everything loaded.
Have had NC rooted w CM7 since April w no problems.
As of month ago, SD card has not stayed in. Seems spring that locks card in is junk. Tried other cards and same thing so has to be hardware.
Because of this, can't download any files, update CM7, CWM, etc. Total bummer.
Can I flash CWM and CM7 directly to emmc or is that impossible w/o SD card?
Have searched multiple forums for resolutions to this issue but no one else seems to have this problem.
Would hate to lose this functionality and have a crippled NC.
Thanks in advance
I never done that but according to my read, you have 2 options
1. Flash CwMR (aka ROM Manager) into eMMC and using it.
2. If you can get ADB working, you can push stuff over.
I had exactly that problem and it happened right in the middle of an update and would not reboot at all. Here is what I did:
Fished out my original, bootable SD card with Nightly 86 and the apps pack, put it in the slot and held it all the way in. Booted up and reinstalled CM7 to the eMMC. (I did not wipe anything but Davlik so I still had all my apps and settings. Then, rebooted into CM7 while holding my regular SD card in place, opened ROM Manager and reinstalled Nightly 201. (I had to hold the SD card in throughout this process to complete which was very strenuous.) Now I am back to where I was, except the SD card slot is basically useless. I called in under warranty and a new Nook is on the way. When I get it I will go through this tiresome process one more time to revert the current Nook to stock before i return it.
If you were only running CM7 off the SD card and still have a functioning stock Nook, forget everything i just said and call them up to request a replacement under warranty. If your warranty is over, you are either stuck with stock or you will have to root the way I just mentioned above.