Related
I had FroYo running on eMMc and all was running smoothly until I went to reboot it and now the screen will not turn on. I have held the power button for a long time and tried pretty much every button combination to get it to power on. I also tried plugging it in and still nothing. Is my nook bricked?
Have you tried booting Froyo on a SD card?
If you don't even see anything on the screen maybe it's a hardware failure..
Were you overclocked?
I put froyo on a 2gb card and i still cant get it to boot. Is there a specific key combination i need to use to get it to boot off of the sd card?
Are you sure that battery wasn't almost dead? Try booting it while plugged in for a bit.
I've had it plugged in for about 10 minutes and ill try to boot it in a second. Whats my next course of action if that doesnt work? and thanks for the suggestions so far.
Still a no go on the boot. Im going to let it charge overnight and give it another go in the morning.
when I power my nook on by holding down the power button eventually the screen will "light up" (even though it will stay black, you can tell the backlight has come on). is it doing that, or just never seems to respond?
I had an issue once running Nookie Froyo where I thought my Nook was dead and realized it was actually on after a while. Only way I found it was that I saw it on my network via my router when checking something else. No matter how long I held the power button down it never seemed to do anything. After a while of fiddling the screen finally lit up and I could get in.
If you plug it into the USB port on your computer, does the computer see it and load the driver for it?
digeratix90 said:
I've had it plugged in for about 10 minutes and ill try to boot it in a second. Whats my next course of action if that doesnt work? and thanks for the suggestions so far.
Click to expand...
Click to collapse
Unless you're using the B&N supplied cable, the NC takes a REALLY long time to charge. I inadvertently let my battery drain and tried charging it using my EVO's USB cable and still couldn't use it more than an hour later, with the "try again in 15 minutes" warning on the screen the whole time.
Hope you managed to fix your problem and that your NC is functional again.
I had the same problem and I could actually replicate it. I had froyo running emmc. What I did was clear out some cache and data from market, Google framework, and also the download manager since I had the market download unsuccessfully problem. Right after I cleared the cache and data then force close the Google framework application (and of course reboot), I couldn't turn on the nook color anymore. I know the device wasn't dead because I got feedbacks if I do.SSH. I flashed the rom again and it came right back on. Then I did the same steps for the cache and data, the device once again couldn't turn on.
Ok i let it charge overnight with the b&n cable (the light was green this morning) And I tried to turn it on again. The screen still does not turn on and the backlight does not turn on. I do not get any response from the computer when I plug it in. I think that I may have bricked the hard to brick nook color :/
I ran into this very same issue a moment ago, and I just followed these steps:
http://forum.xda-developers.com/showthread.php?t=931720
In your case, you want to install the CWM to the SD with the nook 1.0.1 software zip, insert the SD card into your nook, then press and hold down the power and the N button ... and it should boot into CWM then continue with the rest of the steps.
Thanks for the help everyone. I think I may have had a coincidental hardware failure. I took the nook color to b&n today and they tried everything to get it to work and they were going to try to send me a refurbished one, but I asked for cash instead so they gave me a new one on the spot. I am going to stay away from the froyo stuff until it is a little safer (hopefully I can hold out until CM7 comes out)
I can confirm this is definitely a problem with the current Froyo build (.6.7). After loading it to my EMMC and loading Google Apps, I had the blank screen, no reboot issue after I sent the adb reboot command. Thinking I had bricked it (charging, holding the power button, etc. wouldn't do a thing), I popped in an SD card with bootable froyo on it and now the thing powers on and boots to SD. If I take the card out, it goes back to it's dead state.
I'm downloading the stock FW and going to reflash it, but I just wanted to confirm that this is a problem and it probably wasn't a coincidental hardware failure.
backlund said:
I can confirm this is definitely a problem with the current Froyo build (.6.7). After loading it to my EMMC and loading Google Apps, I had the blank screen, no reboot issue after I sent the adb reboot command. Thinking I had bricked it (charging, holding the power button, etc. wouldn't do a thing), I popped in an SD card with bootable froyo on it and now the thing powers on and boots to SD. If I take the card out, it goes back to it's dead state.
I'm downloading the stock FW and going to reflash it, but I just wanted to confirm that this is a problem and it probably wasn't a coincidental hardware failure.
Click to expand...
Click to collapse
I'm having the same issue. Nookie Froyo .6.7 on emmc. Completely dead and not recognized by computer usb. Will try the SD bootable froyo.
Edit: Ok, I was able to boot off the sdcard, but can't get to recovery. If I remove sdcard it won't boot. I guess I'll have to put the recovery on the sdcard to reflash a rom.
I had the same issue when using Froyo 6.6 to EMMC.
I really thought I had bricked it and out of Desperation I made a CWR card put it in and tried every button combo I could think of and low and behold it booted back up. lol, now I'm back to stock 1.1 rooted. I think I will wait till CM7 is out for the nook before writing to EMMC again.
But man props to the makers of the nook color, 99.9% Un-brick-able
Yeah I had a couple issues with throwing an image on the first time I went to root it, just re-formatted and put a diff image on the SD and everything was fine....
Ugh, I'm glad I'm not the only one having this problem. Now I get to walk through the recovery.
Update:
So after walking through the recovery, I still couldn't get it to boot. It wasn't until I performed step 5 that it finally worked.
http://forum.xda-developers.com/showthread.php?t=914690&highlight=cwm
like namely, neither one will boot.
Grabed the Nookie Froyo boot image, wrote it onto a card (8Gig AData Class 6 card) with my linux box then watched as whole lot of nothing happened.
Saw a "Loading..." screen for a bit then "ANDROID.." and it stops there.
Somewhat similar problem with CM7. The installer version never could finish. Froze just past the mkfs the first time, second time got past the extract process, third time it said it made it and to restart. Never made it past that and actually booted.
Found a pre-done CM7 image, just sat at the logo screen for a long time before I shut it off. (like ~15 minutes)
The honeycomb preview image I found also didn't work...
I've tried both ones I have avaliable right now. (they're both identical from a different (failed) project involving a PSP and a Mem Stick Pro Duo adapter)
Technically I do have a 4Gig Class 4 in my MP3 player but i'd rather avoid using it. (it's near full right now and i'd have to copy everything off of it)
Right now i'm just wondering what's going on?
ok, just tried the Kingston 4gb class 4 card
Used the win32 disk imager program to write the nookie froyo image to the sd card.
Works fine, if a bit sluggish (class 4 card, ~15MB/sec read, ~5-6 writes, what do I expect here)
so i'll make an assumption that the Adata cards aren't suitable for use? Really sucks if this is true, was hoping to avoid spending any more money on this.
Now my only problem is that SoftKeys is misbehaving "Unable to execute as root"
Should I just tough it out on 2.1 until the "official" 2.2 or CM7 comes out? (heard something about how sleep is broken)
Sorta sucks a little as there's a 2.2 only app I rather wanted to run.
Fnord12 said:
ok, just tried the Kingston 4gb class 4 card
Used the win32 disk imager program to write the nookie froyo image to the sd card.
Works fine, if a bit sluggish (class 4 card, ~15MB/sec read, ~5-6 writes, what do I expect here)
so i'll make an assumption that the Adata cards aren't suitable for use? Really sucks if this is true, was hoping to avoid spending any more money on this.
Now my only problem is that SoftKeys is misbehaving "Unable to execute as root"
Should I just tough it out on 2.1 until the "official" 2.2 or CM7 comes out? (heard something about how sleep is broken)
Sorta sucks a little as there's a 2.2 only app I rather wanted to run.
Click to expand...
Click to collapse
Is softkeys the only app that cant get root privileges? I guess you could try to fix permisions in rom manager, it wont hurt anything
johnmagoo said:
Is softkeys the only app that cant get root privileges? I guess you could try to fix permisions in rom manager, it wont hurt anything
Click to expand...
Click to collapse
I didn't play around with it much given it's somewhat sluggishness. I did see the superuser prompt for softkeys but it apparently didn't work. Not sure what you mean by "rom manager" though?
Am getting ready to try out CM7 RC4 though. Wondering what that's like. Launcher Pro on 2.1 is nice-ish but it's clearly made for a phone given the wide spacing between buttons on the NC's screen.
Fnord12 said:
I didn't play around with it much given it's somewhat sluggishness. I did see the superuser prompt for softkeys but it apparently didn't work. Not sure what you mean by "rom manager" though?
Am getting ready to try out CM7 RC4 though. Wondering what that's like. Launcher Pro on 2.1 is nice-ish but it's clearly made for a phone given the wide spacing between buttons on the NC's screen.
Click to expand...
Click to collapse
Rom Manager is in settings, its part of CWM for flashing roms and stuff.
I am personally running Nookie Comb with no problems. For me it runs super smooth, wireless does not loop, and all my apps work just fine. I think I will probably switch to CM7 once the actual release is out, I am just having a really hard time switching to it now because Nookie Comb is working flawlessly for me.
johnmagoo said:
Rom Manager is in settings, its part of CWM for flashing roms and stuff.
I am personally running Nookie Comb with no problems. For me it runs super smooth, wireless does not loop, and all my apps work just fine. I think I will probably switch to CM7 once the actual release is out, I am just having a really hard time switching to it now because Nookie Comb is working flawlessly for me.
Click to expand...
Click to collapse
Well, so far CM7 is running better off the card than Nookie Froyo did.
app downloads are slow as hell though, no clue why.
once CM7 is out and if the odd wireless issue is solved then I may install it to the internal memory.
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.
I have been running CM7 off of my SD card for several weeks now, and it has been working very smoothly -- virtually no problems.
Today I installed the updated Barnes & Noble Nook app. It worked fine the first couple of times, but now every time I try to launch it I get the message:
"The application has stopped unexpectedly, please try again."
Then I am given the option to force close or report. The problem is that this is now happening with the majority of my apps. They are refusing to open. When I try to use any of my browsers, they open and shut in the blink of an eye.
The only two apps that appear to be working OK are Market and YouTube.
I tried rebooting, but that didn't fix anything.
Also, my Nook is showing a very low wifi signal, while at the same time my iPod Touch shows a strong signal.
Anybody have any ideas on how I can clear this all up? Is there any troubleshooting app I can run? Thanks.
Update: Market doesn't work now either. I can open it up, but it crashes when I try to download anything.
Dunno if it would cause this... but did you recently modify your build.prop file to install Netflix? If so, restore the original file, reboot, and see if it helps.
It could be oxidation on the microSD card connectors...
I have been messing around with Android on SD for some time, and I don't know what kind of microSD you are using but some of mine require periodic cleaning of the card edge connectors.
Just yesterday, one card I had started with the FCs and crashes and after cleaning the edge connectors it is working fine again.
I dunno, but that is what works for me...
RageAgain said:
It could be oxidation on the microSD card connectors...
I have been messing around with Android on SD for some time, and I don't know what kind of microSD you are using but some of mine require periodic cleaning of the card edge connectors.
Just yesterday, one card I had started with the FCs and crashes and after cleaning the edge connectors it is working fine again.
I dunno, but that is what works for me...
Click to expand...
Click to collapse
Thanks for your suggestion. I took the card out and cleaned the contacts, but everything is still acting flaky. I tried to uninstall the nook app, which is the last thing I installed before everything started going haywire, but it force closes and won't let me uninstall it.
I'm afraid I'm going to have to wipe my sd card clean and reinstall CM7 all over again if somebody can't come up with a solution.
I have the market Nook app installed here on the 2.6.32 Beta 3.1, no problems..
khaytsus said:
I have the market Nook app installed here on the 2.6.32 Beta 3.1, no problems..
Click to expand...
Click to collapse
Yeah, I really don't think it's the nook app that's causing all these problems, but what is? CM7 was working beautifully with no problems until today. Now, everything is force closing on me.
Probably somewhere down the line, corrupted SD card. Not all CM7/SD card installs play well, especially if you're using a Class 6/10 card as they have piss poor random small block writes. Read this thread:
http://forum.xda-developers.com/showthread.php?t=1005633
robot8 said:
Probably somewhere down the line, corrupted SD card. Not all CM7/SD card installs play well, especially if you're using a Class 6/10 card as they have piss poor random small block writes. Read this thread:
http://forum.xda-developers.com/showthread.php?t=1005633
Click to expand...
Click to collapse
Wow, that's pretty amazing. Thanks. I am using a Class 6 card, thinking that it would be better. Who knew?
Do you have Bluetooth turned on? My FCs stopped when I turned it off.
I was having a problem with a lot of force closes as well and it ended up being the SD card. Started off with a Transcend Class 6. Force closes all the time. Then tried a Sandisk Class 4. Runs smooth. The difference was night and day.
kwyrt said:
I was having a problem with a lot of force closes as well and it ended up being the SD card. Started off with a Transcend Class 6. Force closes all the time. Then tried a Sandisk Class 4. Runs smooth. The difference was night and day.
Click to expand...
Click to collapse
That's exactly what I'm using -- a Transcend Class 6. I will have to buy a Sandisk Class 4. Thanks for the tip!
scosgt said:
Do you have Bluetooth turned on? My FCs stopped when I turned it off.
Click to expand...
Click to collapse
I'll have to give that a try. Thanks.
How could this be?
I have two Transcend 8GB Class 6 SD cards. On one of them I have froyo, on the other is CM7.
Yesterday, the CM7 card started going wacky, locking up or force closing practically every application I tried. I rebooted, but that didn't help.
Well, I turned my Nook off, took out the CM7 card and popped in the froyo card. I then powered up. Now the froyo card is acting the same way as the CM7 card did.
How could this be? Is this just a coincidence, or is something internally in the Nook causing this? I mean, before yesterday, both cards were working fine, and then one day they both go bad? Hmmmmm?
cameraz said:
I have two Transcend 8GB Class 6 SD cards. On one of them I have froyo, on the other is CM7.
Yesterday, the CM7 card started going wacky, locking up or force closing practically every application I tried. I rebooted, but that didn't help.
Well, I turned my Nook off, took out the CM7 card and popped in the froyo card. I then powered up. Now the froyo card is acting the same way as the CM7 card did.
How could this be? Is this just a coincidence, or is something internally in the Nook causing this? I mean, before yesterday, both cards were working fine, and then one day they both go bad? Hmmmmm?
Click to expand...
Click to collapse
I at one point actually got something inside my microSD card slot, but I didn't know it until it got on my microSD card and came out...
Maybe the connectors inside your Nook need cleaning...
I am gonna scrape up some change and buy a 4GB CL4 card from the 'shack' and see how CM7 likes it...
On a side note, does anyone have a life expectancy for microSD cards that have Android run off of them?
Not to knock the SD, but not goto eMMC, then you wouldn't have to worry about bad SD card connections. There are plenty ways to go back to stock. I could see using SD for a beta test, of course that's just my opinion.
Ronin3178 said:
Not to knock the SD, but not goto eMMC, then you wouldn't have to worry about bad SD card connections. There are plenty ways to go back to stock. I could see using SD for a beta test, of course that's just my opinion.
Click to expand...
Click to collapse
Isn't it hard as hell to get things put on the eMMC now?
Sent from my Incredible with the XDA Premium App.
I Am Marino said:
Isn't it hard as hell to get things put on the eMMC now?
Sent from my Incredible with the XDA Premium App.
Click to expand...
Click to collapse
Well, I got my nook back in March, didn't have any problems then. And haven't played with a newer one, mine was simple.
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.