As we know, the Nook Color's SD slot will always take first boot priority. I'm in a situation where even booting via SD through known methods are not working.
The purpose of this thread is to:
1) Share with others who are in this similar situation, on methods which may result in the recovery of their own devices
2) Keep this discussion healthy so one day, I will be able to restore my own bricked device which I'm still striving hard to.
Click to expand...
Click to collapse
IMPORTANT: If you have a bricked device I need to emphasize on searching and reading very carefully what others have shared here in both General and in Development. This is a fundamental requirement, as with the ability to follow instructions and not panic by creating unnecessary threads. This will only make things harder to find, so thank you in advance for not doing that.
There are many useful guides out there, some of which the most helpful are:
Nook Color Restore to stock by samuelhalff
Dummies Guide to Fixing 'My Nook Won't Boot' by RileyGrant
Stock 1.1.0 Clockwork Recovery Image by brianf21
Nook 1.01 stock dd images by shad0wf0x
[RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD by thecubed
Click to expand...
Click to collapse
Anyway, in severe bricking cases where hardware is not at fault, many of the solutions to restore the NC begins with either:
1) Booting to CWR-SD via uSD
2) Booting to a rom i.e. Nookie Froyo via uSD
3) Having ADB access, if available
Till date I am not sure why the SD-loaded programs do not work for me, and here are the symptoms:
1) Without SD inserted, the standard BN splash appears, 'Welcome to the Future of Reading', then gets stuck there till powered down. Needless to say, the 8-times reset method doesn't work.
2) With SD inserted, the 'LOADING' screen will splash, then screen blacks out with device still powered on . You will know that the device is still running as you need to hold power down for around 20 secs before you're able to power it back up again. I call this the 'Black Screen of Death'.
Click to expand...
Click to collapse
To get your device up and running, try the following:
0) Do not panic. As long there's no hardware failure there will always be a solution. Look at me, thing's still a damn brick and yet here I am, still hopeful
1) Perform a search, read the useful threads created by the above members first. This thread is related only to failed SD-booting.
Once you've done that, prepare your recovery options with these in mind. The elimination process is part and parcel of problem-solving. In no particular order:
2) Sometimes, try powering on your device by connecting the USB cable from your PC or A/C source, instead of using the Power button.
3) Use only the original USB cable that came with your device.
4) Use the back USB ports of your PC, instead of the fronts as they may provide more consistent power and connection to your device. Try to avoid using USB hubs as they may not distribute the required power equally/properly.
5) Try switching to different USB ports, some may be hardware-gimped due to wear-and-tear.
6) Try to attempt the recovery on another Win, Mac or Linux computer. At least eliminate further possibilities of environmental hardware error.
7) Try charging the battery full.
8) Or, try discharging the battery completely, by leaving the device in BSOD state overnight until you get a message saying your device can't boot due to insufficient power when switched on. Once you are in this state, keep booting the device up until the screen does not appear. Then, recharge it back to full to see if the OS returns to stock (I am sceptical of this, but this was what others advised).
9) Try different SD cards. The device could be picky. Variety should be by class-type, brand, SDHC or non-SDHC. It's been discussed that faster cards perform better, as with more reknowned brands. Also, 16GB cards reportedly do not run Froyo (do read more by searching).
10) When loading anything via SD (CWR, roms), try different button combinations i.e. power + n + up, power + n, etc.
11) And/or, hold power for various timed-presses i.e. >30 / 45 / 60 seconds. Some members report CWR booting up after these periods, or even longer.
Note: funnily I tried holding power + n + up for > 60 seconds and the 'LOADING' screen just stays frozen. Still doesn't work, and I didn't get any ADB access.
12) Try formatting the card completely with native Win/Linux tools, EASEUS Partition Master or SDFormatter before each burn.
13) Try using both Win32DiskImager and WinImage, or dd-ing in Linux (search for more instructions). If you have Linux, you can check to see if the SD's /boot partition is indeed bootable or not.
14) For ADB access, try to unregister your hardware (go to Start > Run > devmgmt.msc), then unplug-replug device to have your PC detect it again. If a device with VID of 2080 shows up, that's the NC. You should know what this means, by now. If not, read more here.
15) Try different SD card readers, especially when experiencing failure on multiple computers. As opposed to multi-adapters i.e. 6-in-1s, try dedicated microSD readers like this one. Do not use those microSD-to-normalSD converters (usually packed together in the same shipping plastic as your card) just because you only have a reader that reads regular SD cards, they tend to fail a lot.
16) At your own risk, try cleaning the contact points on your SD cards (if you must, use cleaning alcohol and a cottom swap/q-tip - do not use water), to free them of dirt and invisible grime. If you have multiple SDs, try cleaning the least expensive ones first. Don't forget to leave them to dry completely before insertion into the NC. Credit to bonobomidwest, read his experience here.
Click to expand...
Click to collapse
17) Use Nooter 0.2 (recommendation from thecubed):
Here's my recommendation: use the stock charger cable (the one with the light-up N in it) when you try Nooter 0.2.
If the light goes from orange to green (or something like that) that means Nooter is booted and working.
My new thought: some file in /rom is missing, which controls the backlight and lcd controller. I can't prove this, but it seems logical haha.
All you need to do is get Nooter 0.2 booted and ssh'd in and you'll be able to dd over a complete 1.0.1 backup.
rawfish: I use Ubuntu, so sorry if I'm not able to provide instructions for Windows
Type:
Code:
sudo ifconfig usb0 192.168.2.1
Then:
Code:
ssh [email protected]
And you should be able to follow the directions for restoring on the wiki... either that or check around on IRC, if you tell them that you've got ssh access and you just need to restore your device, they'll help you out if I'm not around..
rawfish: I typed 'dmesg' in shell to see if the NC connected as a usb-ethernet device, and it doesn't show. If it does for you, then you should have progress and should ask around in IRC.
Click to expand...
Click to collapse
All these did not work for me, but hope this is useful to some. I've read testimonies from everyone that this is an unbrickable device, and I certainly hope it's true, and for a kind soul to help suggest more solutions. As I'm overseas, do you think I should call BN up to see if I can arrange to send my device back for fixing/replacement? It's been a month since purchase, and 3 weeks of failed restore attempts.
Disclaimer: I am not responsible if any of these methods get you in deeper trouble. Attempt at your own risk. Credit goes to thecube aka IOMonster, and the #nookcolor channel on irc.freenode.net. Thank you to everyone who created the recovery guides too.
This space reserved.
You sure you just don't have crap or badly burned SD cards? Sounds pretty much what happens if you boot s really slow/junk SD or burn it badly.
khaytsus said:
You sure you just don't have crap or badly burned SD cards? Sounds pretty much what happens if you boot s really slow/junk SD or burn it badly.
Click to expand...
Click to collapse
I tried on 6 different SD cards:
1. Transcend 8GB Class 6
2. Transcend 4GB Class 2
3. Wintec 16GB Class 10
4. Sandisk 4GB Class 4
5. Sandisk 2GB non-SDHC
6. Sandisk 256MB
I've burned stuffs like Autonooter and Honeycomb on these before, and they worked fine.
rawfish said:
I tried on 6 different SD cards:
1. Transcend 8GB Class 6
2. Transcend 4GB Class 2
3. Wintec 16GB Class 10
4. Sandisk 4GB Class 4
5. Sandisk 2GB non-SDHC
6. Sandisk 256MB
I've burned stuffs like Autonooter and Honeycomb on these before, and they worked fine.
Click to expand...
Click to collapse
First of all - great job in pulling all the resources into one place (it's small consolation, but i think you've just helped a whole load of people )
Second, i apologise if I'm telling you stuff that's obvious, but in helping out on these forums often it's the LOGIC of troubleshooting rather than the particulars of the problem that are important... In other words, only vary one thing at a time, and ALWAYS swap out every piece of hardware involved at each stage... if you always rely on one piece of hardware this might be the weak link... so have you tried a different SD drive or adapter? and have you tried burning from a different computer?
Now, I'm not being insulting, because I had a virtually identical problem with my first froyo - it just wouldn't boot (as you describe) despite multiple burns, different cards, all of the standard formatting tricks etc. It wouldn't work in multiple computers - the common element being the SD/microSD adapter. It never occurred to me that such an electrically simple part could be at fault, but you bet it was - in fact i would say in my experience these things consistently fail! (I spent a day kickign myself, because we know ho unreliable they are from using them in other devices). They also all look alike so it's hard to keep track of which one you are dealing with They also fail unexpectedly, so if you used an adapter before there's no guarantee it's working now...
Sooo... Have you tried a dedicated microSD reader (rather than a simple adapter)? I now carry one with me everywhere (it doubles as the world's smallest thumb drive too)
http://www.amazon.com/gp/product/B002HGFKR8
Also bear in mind that froyo appears not to work on 16gb cards (i see you tried one)
Also, from my experience with other devices these cards are very sensitive to dirt and oil on the contacts. Certainly with enough frustrated handling you can get enough finger-grease on them to have them fail. Also they seem to be much less tolerant when writing than reading. I have NO idea how you would go about cleaning out the slot in the NC (and as someone who has ruined at least one DVD drive by blowing canned air where you shouldn't I'm not going to advocate for that). I have resurrected 'dead' SD cards before by cleaning the contacts with rubbing alcohol and a q-tip (on the card's contacts) - but again do so with great care (at your own risk!!!) and with your cheapest card, and make sure it si completely dry before you put it in the NC.
I have been generally a little scared that all this plugging and unplugging of the microSD might hurt the NC, so i have done everything i can to avoid that...
I am sure you can find someone local to you willing to help fix your boot issue but I assure you, its damn near impossible to brick a nook without physical damage.
@bonobomidwest:
No offence taken at all, in fact I am very appreciative of your contribution. I forgot to add the fact that I tried on 2 different card readers, plus indeed tried to clean the slot via an air duster VERY GENTLY as a last effort resort (I would not recommend this, it may cause permanent hardware damage). Once I'm free I'll go get a new SD reader (reads uSD only) and a new uSD which I haven't tried before. I'll try cleaning the contact points too.
*Thanks - I've added more checklists to the OP
@combustiblemonkey:
Thanks for the assurance.
I convinced my friend to buy a nook, rooted it for him, and was bricked within 2 days. Here is how I fixed it
EDIT: I tried to post a link, but was unable. If you go to theunlockr(dot)com and search for how to restore nook color to stock, there is a detailed article.
This took me almost 2 days of reboots, black screens, and freezing. I would get into CWR, and it would freeze. Had to reboot, got the black screen of death. Literally, a couple hundred reboots before it said that the OS has successfully installed, and of course, it froze again. Many more reboots, and it was finally at stock. I figure getting it back to stock was enough to return it.
Dr-Rockso said:
I convinced my friend to buy a nook, rooted it for him, and was bricked within 2 days. Here is how I fixed it
EDIT: I tried to post a link, but was unable. If you go to theunlockr(dot)com and search for how to restore nook color to stock, there is a detailed article.
This took me almost 2 days of reboots, black screens, and freezing. I would get into CWR, and it would freeze. Had to reboot, got the black screen of death. Literally, a couple hundred reboots before it said that the OS has successfully installed, and of course, it froze again. Many more reboots, and it was finally at stock. I figure getting it back to stock was enough to return it.
Click to expand...
Click to collapse
Thanks, this is the direct link:
http://theunlockr.com/2011/02/14/how-to-restore-the-nook-color-to-stock
All instructions were taken from XDA, plus no guarantee it's the most updated
Moving on, great to hear you've gotten it back to stock. Man, you've got GREAT patience, a couple hundred reboots?
1) Was the SD inserted in or not? Curious about the OS successfully installed message, which is the result of 8x unsuccessful reboots without SD inserted.
2) Could you also provide a more detailed account on what you did? Looking forward to hear - thanks.
Hi rawfish
I also have this issue and have been trying many things. My nook did boot nooter 0.2 (the light went green) but I couldn't get Win 7 or Ubuntu to connect to it. My screen never changes at all, no backlight even. Seems this may be a larger issue than most believe it to be, especially for people like us who don't live in the US.
chrysilis said:
Hi rawfish
I also have this issue and have been trying many things. My nook did boot nooter 0.2 (the light went green) but I couldn't get Win 7 or Ubuntu to connect to it. My screen never changes at all, no backlight even. Seems this may be a larger issue than most believe it to be, especially for people like us who don't live in the US.
Click to expand...
Click to collapse
If you can find a friend or person in your area having the same device, you can try to see if an SD you burned work on theirs. If it works on theirs, it's possible that your SD slot is defective - but then comes the question of it being in working condition before the bricking happened, right?
I still think mine's recoverable, as with yours. Could be a bad SD or reader, or bad contacts. I'm going to try out using another reader plus purchase an el-cheapo branded SD. I'm also going to try formatting it via another PC in a linux environment and messing around with the partitions.
I understand the trouble you may have taken to get the device - and this happens. All the best mate, and do cheer up, don't give up.
rawfish said:
Thanks, this is the direct link:
All instructions were taken from XDA, plus no guarantee it's the most updated
Moving on, great to hear you've gotten it back to stock. Man, you've got GREAT patience, a couple hundred reboots?
1) Was the SD inserted in or not? Curious about the OS successfully installed message, which is the result of 8x unsuccessful reboots without SD inserted.
2) Could you also provide a more detailed account on what you did? Looking forward to hear - thanks.
Click to expand...
Click to collapse
When I finally got it to work, the SD card was installed with the 1.0.1 stock OS on it, and CWR. The problem was that that (+) and (-) would only occasionally work. And if they did, it would usually freeze. I would be able to format system, but it would freeze if I tried to format data. Powered off, and I would get the black screen of death (BSoD). Once this happened, I would plug it into my computer so that I could hear the chime indicating a new device was plugged in. I found that ejecting the SD and then rebooting would sometimes help get rid of the BSoD. Then another power down, plug in the SD, and start again. Also, holding the N, +, and Power would sometimes help in launching CWR. I would usually have to hold for 60 seconds, but it would finally launch. It seemed like the nook was trying to run a process that slowing it down and causing it to freeze, but I couldn't figure out what it was. If I would wait an hour, it would boot CWR and allow me to format system and data, but then it would freeze when I would try to install the zip.
The successful install message was in CWR. It said Install From SD Card Complete, or something like that. After that, I still had to do the 8 reboots. It would load up the stock welcome screen and freeze. 8 reboots later, I got the video lady. Good enough to return it to the store.
It really was just persistence. It would usually take an hour of reboots before I was able to try to install the zip, and it probably failed on me 15+ times. The status bar would get half way, and freeze. Then I had to begin again. If it had been my nook instead of my friends, I probably would have given up. I wish I could be more specific, but unfortunately I am new to all of this. My nook rooted just fine, and fixing his is really my only experience with CWR. I just kept going until it worked.
Good luck! It is a pain in the ass, but it can happen.
rawfish said:
If you can find a friend or person in your area having the same device, you can try to see if an SD you burned work on theirs. If it works on theirs, it's possible that your SD slot is defective - but then comes the question of it being in working condition before the bricking happened, right?
I still think mine's recoverable, as with yours. Could be a bad SD or reader, or bad contacts. I'm going to try out using another reader plus purchase an el-cheapo branded SD. I'm also going to try formatting it via another PC in a linux environment and messing around with the partitions.
I understand the trouble you may have taken to get the device - and this happens. All the best mate, and do cheer up, don't give up.
Click to expand...
Click to collapse
My wife has one as well so am able to test using that and the SD works fine in hers. The whole screen not turning on thing is weird though, does your screen turn on?
We bought them when on honeymoon in America so didn't have to pay a shipper or anything
Deleting the partitions manually with Gparted and using dd to burn the SDs and making sure the correct partitions are bootable doesn't seem to work. Last night I retried a lot of the previously attempted options, with no results.
It's weird to think that a working SD slot and a slew of cards will suddenly malfunction, but for now that seems like the most plausible reason why my NC can't boot anything off SD.
To think back how it all started, the device suddenly rebooted from HC preview v0.4 to stock BN 1.01 (rooted + installed CWR on eMMC) while the SD is inserted, then upon another reboot it simply stays dead, this gives me reason to believe that the internal boot partition is corrupted, and SD slot nuked hardware-wise.
Hmmm, really hoping to find someone else who has the same device, in my area.
Right now I am at the Black Screen of Death as well...
I think Barnes should refund me, but I am willing to do some tests for the good of society.
Steelfan555 said:
Right now I am at the Black Screen of Death as well...
I think Barnes should refund me, but I am willing to do some tests for the good of society.
Click to expand...
Click to collapse
Sorry to hear that, and don't give up! Hope you took a look at the other threads, and this little pseudo checklist I made in the OP. Do share the outcome
Thank you Rawfish. The first option, the Dummies Guide to Fixing 'My Nook won't boot'
was what I needed to get started on the right track again. Though I'm not sure anyone wants to know how I ended up here, I'm grateful to those that put in the time and effort to find any of these solutions.
Thank you!
FroztIkon said:
Thank you Rawfish. The first option, the Dummies Guide to Fixing 'My Nook won't boot'
was what I needed to get started on the right track again. Though I'm not sure anyone wants to know how I ended up here, I'm grateful to those that put in the time and effort to find any of these solutions.
Thank you!
Click to expand...
Click to collapse
Update:
Ok, so after running through it, I ended up getting stuck on the boot screen that shows N. If I powered off, it would restart and get stuck at that screen. I tried the 8 shutdowns (it installed new software), but afterwards, it was still stuck. So, I tried another method I found on the forums. I powered off holding the N button and power, which caused it to boot back up and do a factory reset. I now have a factory fresh Nook.
Okay, it's been a while since I kept this thread updated - I contacted BN and had the device sent back, apparently the SD slot failed so they sent me a new one. I'm just wondering if it's sheer concidence that it happened, as I was tinkering with Nookie Honey preview v0.4, when the hardware suddenly failed.
Oh well, I guess the NC still remains as a 99.99% unbrickable device - with the 0.01% being related to the ambiguous root cause to my case.
I now have 2 NCs (one from the RMA process, another one from the $199 eBay deal.
My wife and I have Nook Colors and I recently decided to root mine using AutoNooter. I went through all the steps, crossed referenced the steps with other sites, and went through the steps again. Here's the problem I run into; upon inserting the microSD card into the NC(while off)and plugging it into the computer using the USB cable the darn thing won't boot up.
Everything I've tried:
-a different SD card(I have now tried a 4GB PNY microSDHC and a 2G Sandisk microSD.....and a generic microSD card from my cellphone)
-I've tried loading the image from different sites and using different browsers
-I've tried different imaging software
-I've tried using BOTH mine and my wifes NC.
-I've tried it from 2 different laptops(a Toshiba and a Gateway)
-I've tried downloading the image from both laptops integrated disk reader using an adapter and I've tried loading it using an external USB card reader that reads/writes a microSD directly without needing an adapter.
-I've tried de-registering the NC and re-registering.
-I've let the NC sit for an hour while plugged in.
NOTHING. The light on the USB cable goes from amber to green....which is where the whole process ends.
-I'm running firmware v1.1.0 therefore I'm using AutoNooter 3.0
-I tried it a while back when running 1.0.1 using AutoNooter 2.12.25 with the same results. I'm getting impatient waiting for B&N's rumored update so I decided to try again.
-I do know how to format the SD card so that is not the problem
It's gotta be something simple. PLEASE HELP! Thanks for taking the time to read this. So frustrated
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Sorry if you already know this but nothing happens when you boot the autonooter image. The screen stays black. All the magic just happens in the background. All the basic nooter does is enable side loading apps. Some of the others to more. Find your favorite apk and try
adb install myApp.apk
If it works then so did nooter. Find a launcher and go nuts.
vlucchetti said:
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Click to expand...
Click to collapse
Same here. I thought I botched the install but the android showed up eventually when it finally booted and I'm running market apps so i know it worked. Very weird though.
I don't think autonooter has any coding in it to prompt the screen to turn on to let you know its installing, but usually (at least in windows) when you plug in your Nook you can hear it mount to the computer...I usually wait for this, leave it on then unplug//remove the uSD card and boot up my Nook.
What are you using to "burn" the .img to the SD card? If you see the same file written to the card after burning, its not imaged properly. I had this problem the night I bought my nook and it drove me nuts. Use WinImage. From the top menu select Disk>> Restore virtual hard disk image to virtual drive>> select SD card>> select file. The burn should take about 10 secs and you should see a file system structure on the card when opened. If you get an error that the file is in use when you go to burn it, log out, log in and try again or reboot. Burning the image is key, the rest is cake.
Sent from my LogicPD Zoom2 using XDA App
chris peas said:
What are you using to "burn" the .img to the SD card? If you see the same file written to the card after burning, its not imaged properly. I had this problem the night I bought my nook and it drove me nuts. Use WinImage. From the top menu select Disk>> Restore virtual hard disk image to virtual drive>> select SD card>> select file. The burn should take about 10 secs and you should see a file system structure on the card when opened. If you get an error that the file is in use when you go to burn it, log out, log in and try again or reboot. Burning the image is key, the rest is cake.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I've used WinImage 8.5 and Win32DiskImager. I know it has to be an issue with the image but the files on the sd card after it's been written look identical to screen shots I've seen of the image on multiple "how to" websites. How long did you wait before the NC booted up?
Taeseong said:
I don't think autonooter has any coding in it to prompt the screen to turn on to let you know its installing, but usually (at least in windows) when you plug in your Nook you can hear it mount to the computer...I usually wait for this, leave it on then unplug//remove the uSD card and boot up my Nook.
Click to expand...
Click to collapse
According to NookDevs when using the latest autonooter for use with NC firmware v1.1.0 the NC will boot up automatically once it's connected to the usb cable after a few minutes. Not to be confused with the previous autonooter for use with firmware v1.0.1 where you connect, let sit for 10 minutes, then boot after removing from the usb cable and the sd card. Tried that one too with no luck.
donballz said:
Sorry if you already know this but nothing happens when you boot the autonooter image. The screen stays black. All the magic just happens in the background. All the basic nooter does is enable side loading apps. Some of the others to more. Find your favorite apk and try
adb install myApp.apk
If it works then so did nooter. Find a launcher and go nuts.
Click to expand...
Click to collapse
I never get to the point of seeing the new boot up process, skipping log-in, logging in to youtube, enabling softkeys, etc. It's funning that I quote the sequence without actually having done it. It's because I've read the steps so many times.. So frustrating!
You have to connect it to a PC to initiate the boot from SD. You should connect it to a pc where its NEVER been connected to before. A few things you can try. Connected to the PC, hold down the nook's power button for up to a minute. Did you hear a chime on the PC as if you connected a device to it? No? Next, open device manager on your PC with the nook connected. From the Action menu >> scan for new hardware. Did it find anything new? Do see anything with the name "gadget" or portable gadget in the device list? Right click, delete it. Again, scan for new hardware. Did windows find new hardware now? Did it boot from SD? Try plugging into a different PC. This is THE ctritical step.
I had this problem when i wiped my device and rerooted. Because the device drivers were already installed, my nook wouldn't boot n root. Chances are you connected it to your PC before attempting to root. You have to get windows to detect as a new device and the PC should fail to load the drivers. If you get that far with no luck, keep deleting the device from device manager and reconnecting it with the cable. Hope this helps...
vlucchetti said:
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Click to expand...
Click to collapse
Went this route and couldn't be happier with the result. Thanks so much for your input!
OP I have the same issues as you, very frustrating!
How did you solve the problem in the end?
edit: NM figured it out.
A couple of days ago my dad got my sister and me nook colors. I installed honeycomb which ran off the sd card on both and rooted both. I was tired of not having YouTube flash and many other apps so I tried out froyo and cm7. After about 50 unsuccessful installs I have decided I must have a hardware problem because they will run on my sisters nook.
The problem is that after the install, it boots off the sd card and loads android completely but when it asks to complete with setup wizard or
Default action it freezes up for a second and shuts off. After I boot again it just says "Powering Down."
I don't know if I should try a native install or go return this one. I already restored it completely to factory conditions so they won't be able to tell. I have searched everywhere and cannot find this anywhere else (problem or solution).
I just find it so strange how it works on the other nook color but not mine. Even setting it up on hers and moving it to mine produces the same issue. I probably will return it unless someone can help me but I'm more curious to what the problem is than how to fix it, since I can simply go get a new one.
Any help is appreciated!
****bump****
Thats certainly a new one. I only have one nook so ive never tried them side by side. Ive never been able too successfully boot off an sd card and have it stable. I eventually just decided to go to cm7 internal and never looked back. I wonder if theres something different in the nook in how it reads from the sd card.
are you overclocking the image? or running it stock?
you said you set it up on your sisters nook then move it to yours and you have problems. did you try taking her good, working build and moving that sd card to your nook and seeing if the problems go away. Ive read alot about sd cards and different quality's of cards. maybe theres something up with the sd card you have.
I have problems no matter what. If i put it on hers to setup, it still has the problem. If i set it up on mine, still has the problem. I just tried phiremod v6.1 and it also had the problem (i expected this because it is still cm7). I probably will return it but i wish they would just update these things to android 2.2/2.3 and maybe even full honeycomb when it comes out and save all of us from these issues.
The image is the normal one. I have tried installing directly to the sd, using the "SD CARD TEMPLATE" files that you install and then boot from to install cm7, etc.
They all work on the other nook but mine is being stubborn for some reason.
I am at the airport getting ready to fly home and i might try installing it internally tomorrow. I just don't want to have this problem again and have to spend a bunch of time reinstalling the stock rom to return it.
I completely understand your frustration, especially since you have 2 and are not seeing the same thing on both. Are you experiencing any other problems with the device. based on what your telling me i would have to assume there is something wrong with the sd card slot.
but if you forget about your sisters nook for a min, what you are describing is exactly what i experienced on my nook. that's why i went for internal. I started with the dual boot, but found that i stopped using the stock rom pretty quickly, and with the slow ports of cm7 to dual boot, i just scrapped dual booting all together, and now im full cm7 and its great.
john10101 said:
I completely understand your frustration, especially since you have 2 and are not seeing the same thing on both. Are you experiencing any other problems with the device. based on what your telling me i would have to assume there is something wrong with the sd card slot.
but if you forget about your sisters nook for a min, what you are describing is exactly what i experienced on my nook. that's why i went for internal. I started with the dual boot, but found that i stopped using the stock rom pretty quickly, and with the slow ports of cm7 to dual boot, i just scrapped dual booting all together, and now im full cm7 and its great.
Click to expand...
Click to collapse
I tried the internal install, but it is doing the same thing. I am recovering the stock image right now. Thanks for the help, but I am just going to take it back and get a new one and not root it or anything and just install it to the sd card.
I have the same problem too.
Hi there, I recently installed CM7 onto my SD card and was wondering if the time it takes to fully boot up is normal? My rough counting indicates that it takes approximately 20 seconds from when I press the power button to get to the CM7 splash screen, then another 30 seconds to get to my "desktop". I am using a Sanddisk 8gb class 4 card. The OS when running seems pretty quick and applications seem responsive. My Nook is a refurbished unit.
thx.
That's about right. It's not much different on eMMC.
Rodney
Sounds about the norm here too.
Sounds way fast to me actually. I'm pretty certain that mine takes quite a bit more time than that to boot, the CM7 splash screen is up forever.
i just switched from emmc to flash card and its about the same for both...whats funny is my wireless runs better off the flash card...
sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.
TainT said:
sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.
Click to expand...
Click to collapse
Since performance is almost the same, if you need warranty work you can just pop the card out and send it in to B&N, but if your device no longer boots or has some other major problem and you send it in and they see a custom ROM on it, they will not give you warranty coverage.
At least that's ONE reason...
TainT said:
sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.
Click to expand...
Click to collapse
Personally I liked the way the stock B&N software worked for reading books better than the Nook app. So I can see wanting the flexibility of being able to use the stock Nook when I was reading a book, then being able to pop in an SD card and use it like a tablet when I wanted to do other things.
Seems like kind of a pain though.
darien87 said:
Personally I liked the way the stock B&N software worked for reading books better than the Nook app. So I can see wanting the flexibility of being able to use the stock Nook when I was reading a book, then being able to pop in an SD card and use it like a tablet when I wanted to do other things.
Seems like kind of a pain though.
Click to expand...
Click to collapse
Agreed I actually wanted to use some of the BN features, books reading is better and reading of magazines in color rocks. It functions very as it was originally intended to be a "reader". But I like to be able to use it as a tablet when I want.
I have only run from SD card but I played with my son's that is flashed to eMMC and build for build, I can't tell any difference so I just stick with SD card.
Timed mine...
hokudog said:
Hi there, I recently installed CM7 onto my SD card and was wondering if the time it takes to fully boot up is normal? My rough counting indicates that it takes approximately 20 seconds from when I press the power button to get to the CM7 splash screen, then another 30 seconds to get to my "desktop". I am using a Sanddisk 8gb class 4 card. The OS when running seems pretty quick and applications seem responsive. My Nook is a refurbished unit.
thx.
Click to expand...
Click to collapse
From power button push to when the CM7 rotating circle is centered on screen was 39 seconds. Desktop appeared at 1:03. A few more seconds for everything to 'settle' (fancy widget gets its skin, superuser ok's nook tweaks, etc).
On a new Sandisk 16gb class 4.
So far I think CM7 on SD would be my choice for running Android. Reviews are positive about it, applicable solution for noob like me.
I've a chance to run both CM7 off uSD and eMMC.
Here's my take:
+ Boot off uSD
1. simpler procedure (good)
2. avoid "void warranty" (good)
3. want the original NOOKcolor = remove the uSD, want fancy CM7 = insert uSD, want fancy Honeycomb = insert uSD, want fancy bla bla bla = insert usD
4. seems slower than the eMMC version
5. if having Kingston or Transcend (even with class 6), there are too many FC's errors
+ Root and run from eMMC
1. have to do more procedure (such format /data / system /cache)
2. B&N doesn't like it if rooted. There are ways to restore stock ROM those, again, more steps
3. Want original NC? do a restore procedure. Want to try Honeycomb? repeat installing procedure, ....
4. Seems faster
5. Virtually eliminate all FC's errors unless it's a real software bug.
6. Still some issues, at least in my case such Gallery doesn't work if no external uSD (FAT32) plugged in. Why? Why requires an external card? Turn ON USB storage has to go through more steps, my case, I have to unmount the eMMC's /media storage first then plug the usb cable in, then mount the /media for it to work connecting PC.
Best of both worlds
Very much a noob here. I bought my nook as an early retirement present. I originally had a Velocity Cruz but wanted to do more with it than it was capable of. Started reading threads on this site and BN site and after a week or two decided to make a dual bootable sd card running CM7. Everything went smooth but instead of the 15 min to create this card like I read on posts here it took me 4 to 5 hrs. Ok so I had a few issues!!!!! Loved it for the next couple of weeks; then while checking things out one night after I officially retired I was in Rom manager. Big MISTAKE! Saw there was an update to the CM7 I was using. Thought ok I'll update and low and behold I ended up updating internally not to the SD card. It was really nice rooted internally but after a week I decided to put stock operating system back on. Created that bootable card and went back to stock. Bought a 16 gb card made a new dual boot card with the same OS that I had inadvertantly rooted internally too. For all of you techies out there it was a lot quicker this time. I'm one happy camper now. I have Aldiko reader on the card and Calibre on my computer with plugins for taking drm off my books so husband and I can both read them. If I can do all this anyone can. I feel I have the best of both worlds now.
votinh said:
+ Boot off uSD
3. want the original NOOKcolor = remove the uSD, want fancy CM7 = insert uSD,
Click to expand...
Click to collapse
Depending on the ROM, you shouldn't need to remove the uSD to load to stock. For example, with CM7, you should be able to just hold N while it's booting and it will go to a boot menu, from which you can choose stock/recovery/sd/etc. Or, if that doesn't work, you can usually use a different uboot file.
Creating the SD card to run CM7 was very easy with all the how-to's up here and around the net. The performance is close to the same as internal memory. The best part is I have my whole OS in a tiny little SD card, which I can remove for security reasons or a lost or damaged Nook. Just pop it into any Nook and away you go.
TainT said:
sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.
Click to expand...
Click to collapse
Warranty issues for one - but mostly there's no speed difference between SD and EMMC. It's actually *less* hassle - because you can fark around with an SD card all you want and *never* risk bricking your NC. The SD card sits in there and is no different in speed or boot up process - it just boots and runs.
I'm running racks' dual boot phiremod/hc and boot for phiremod seems slightly faster than hc. Maybe a few seconds faster than the 50 seconds it takes you, but seems like you're in the ball park.