I'm having these weird issues trying to get CM7 uSD working on a newly bought Nook Color. It's odd as I've done this many times before. I have my own Nook Color that I have a uSD for and I've setup Nooks for 3 friends, but my roommate got a new Nook and I went and started setting him up with CM7 uSD but odd things start happening. Apps crash for no reason, touch screen glitches, random reboots, ect. However, when I pop the card in my Nook everything works fine. His Nook works completely fine with the Stock ROM. So I'm at a loss as to why this happens. I haven't tried the latest nighties on it yet as I like to put the more stable versions on Nooks I don't directly use as usually they don't want to bother with bugs.
Any ideas?
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
The nightlies actually are the most stable builds of CM7 for the Nook. I'd have to say your friend got a bad Nook, if the card works perfectly in your Nook than it should in his, maybe there is a problem with his SD card reader in his Nook.
Only other think I can think of that would make a difference is if you were overclocking, which would account for the differences in hardware...
It does sound like possibly a hardware fault, but one that would be hard to report credibly. You might try some side-by-sides with non-bootable SDs housing movies, music, or whatever else you can think of, and if you can see an appreciable difference there, your friend can call in with "My NC doesn't play videos from a card that works fine in my friend's NC and I think there's something wrong with the card reader."
All assuming your friend's NC was acquired through official channels and is under warranty.
Possibly the card is not staying seated properly in his Nook. I just had to replace mine because it popped out and would not stay back in.
Joe has good points
The card on my roommates Nook doesn't like to come out of his Nook easily so that could be a reason. I'll also have to try a more recent build of CM7. Would the CM7.1RC be a good place to start or should I go for one of the nightlies? If a nightly which one should I try first? I'd need one with as few bugs as possible so I don't have to factor that in when testing.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Just grab the most recent nightly.
You can see the changes in each nightly here:
http://cm-nightlies.appspot.com/?device=encore
Update...
Ok here's an update on my problem with this Nook. I tied again to install CM7 to uSD using verygreen's Size Agnostic Installer. This time I used 7.1 Stable. I payed attention to the Messages during Install and Noticed a Trend. I noticed many errors and they all pertained to some operation that involves writing to the Card. Essentially it encountered numerous write errors during install so Obviously CM7 wasn't installed properly which led to Boot Looping. Now I took the Same card and set it up the same way but used my Nook this time. I didn't notice any errors and CM7 installed Correctly. CM7 operated normally on my Nook but once I took the card and booted it with my Friend's Nook I got to the Home screen but during use I got multiple Force Closes and spotty behavior and eventually a freeze/Sudden-Reboot; probably caused by write errors as well.
All this evidence seems to firmly point to a defective Card Slot on my Friend's Nook. My Friend and I plan to take his Nook to a local B&N store and see if we can get it replaced. The Nook hasn't been Rooted but I'll perform a Factory Reset Just in case. The story my Friend and I will use is that my Friend has been trying to copy files to the SD card using his Nook but he keeps on getting errors, and the reason it isn't the card is because we've tried using it in my Nook and the Files copied fine.
If you have any suggestions on any extra steps I should take to Prep my Friend's Nook for Return (ie: make sure no evidence of running Android on it remain) I'm all ears. Thanks for the Help
Have you tried actually running operations side-by-side on the two NCs (moving files, playing videos) so you can actually demonstrate the problem? Your "story" will be more convincing if it's true
Related
I'm getting a used nook color tomorrow. What sort of things should I test/play with and look out for?
The seller had 1.1 on it with 0.6.8 nookie froyo on the emmc and will flash it to stock b&n when he sells it to me. it also comes with 2 matte screen protectors (one on it) and a case.
TIA
Scratches on the screen and physical damage to the unit are the only things I would be concerned about.
I would have it running a full ROM from the internal memory so it really doesn't matter what was flashed on it before. It sounds like the owner will be giving it back to you flashed stock so you won't have any issues even if you intend to keep it that way.
thnx for your quick reply
i guess if i want to put froyo on a sd card later on i should ask if he un-rooted it? or what he rooted it with?
he could have left it with 0.6.8 nookie froyo on but i wanted to learn this process by doing it myself. also a big part of why i chose this device anyways.
You won't need anything from him. Every file you need is in the development section here. The nook is incredibly hard to brick (maybe impossible?). I even corrupted the boot doing something stupid with an ext 4 build and was able to use adb to push the original Color Nook files and factory.zip back and it booted right back up like a champ.
I'm using the latest CM7 nightly with Phiremod's customizations, it is pretty stable and I look forward to future builds of HC (HC4 was a little unstable for me to use as a daily).
Turn it on and look to see if you find any dead or hot pixels...those would be a deal breaker for me...
danknee said:
Scratches on the screen and physical damage to the unit are the only things I would be concerned about.
I would have it running a full ROM from the internal memory so it really doesn't matter what was flashed on it before. It sounds like the owner will be giving it back to you flashed stock so you won't have any issues even if you intend to keep it that way.
Click to expand...
Click to collapse
Also check out http://nookdevs.com/Portal:NookColor They have alot of information on the Nook Color and various guides for Rooting, Making a Nookie Froyo SD, ect... You get the idea. They were the ones to hack the Nook Original and are now keeping an updated page for all things Nook Color.
____________________________________________________
Sent from Nookie Froyo using Tapatalk
Bring a Micro-SD card with you to make sure that the slot works. My first Nook wouldn't retail the card. It wouldn't stay "clicked" in the inserted position. The eject springs kept kicking it out.
Might as well check the headphone jack too.
Check rhe screen very carefully, both on dark and light background in order to check whether there are dead piscels.
Also, check hardware buttons, all other things should be perfectly fine since this device can't be older than 4 months...
personally i would check for physical damage(IE drops,scratches,ect), i would check to see if all buttons are working, dead/burnt pixels(unless its like one dead pixel in the very corner and it doesnt bother you) and i would check if head phone jack and sd card slot are working(he had nookie froyo installed on it so i am assuming the sd card slot is working but its always good to double check)
all of the above would be deal breakers for me personally but everyone is different so what bothers me might not bother you
I've been reading some issues with used NC that have been registered. The new owner couldn't register the used NC without the original owner removing the NC out of their BN.com account.
So, be sure you have contact info for the seller. Also look up the device info tabs and verify the seller/owner is who is registered.
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.
Hi
I have a brand new nook color that I bought because it appeared that it would be relatively easy to root and use a new kernel. I have tried froyo 2.2, honeycomb, and cm7 on sd cards and they all boot up fine but ... the touchscreen does not work at all with any of them. The nook works fine in native mode. I have tried 2 different sd cards, tried with nook plugged in and unplugged. I have downloaded images and built my own. No matter what I try, the touchscreen does not work at all--ever. Some have suggested turning the screen off and on. No help. Anyone have any ideas? Thanks
Post the forum thread with the method that you followed. There seem to be a lot of methods to do it. It might help the pros on here help you better.
I've got exactly the same issue after trying all the same fixes also on a brand new NC. Could it be the software version or something along those lines?
same exact issue. Booting CM7 or Honeycomb from SD card (multiple cards) the screen does not work after android boots. Nook came from factory with 1.3 firmware. I used an 8gig pny class 10 card and a 4 gig sandisk class 4. no joy. I made the cards using these instructions on a mac
forums.androidcentral.com/barnes-noble-nook-color/99131-how-download-install-cm7-run-off-sd-card.html
moviepastor said:
same exact issue. Booting CM7 or Honeycomb from SD card (multiple cards) the screen does not work after android boots. Nook came from factory with 1.3 firmware. I used an 8gig pny class 10 card and a 4 gig sandisk class 4. no joy. I made the cards using these instructions on a mac
forums.androidcentral.com/barnes-noble-nook-color/99131-how-download-install-cm7-run-off-sd-card.html
Click to expand...
Click to collapse
Ive got the same issue and tried it several times too!
wow still no responses, I have the same issues. Even flashed back to stock 1.3 and still the touch screen doesn't work!
ooo that sucks, your only luck now is, plopping that baby into the trash. or try a warranty exchange. yeah. good luck.
Are you guys trying to boot cm7 for nook COLOR on the brand new nook TABLET?
Sent from my Sensation using xda premium
cm7 stable just now booted up fine, touch screen works perfect. I didn't do anything different I hadn't already done, strange. On second thought, in CWR 3.2.0.1 I did change 2 options in the install from zip option, which was to enable signed
fixed my nook color with touch screen not working...
I had the same issue with a brand new nook color. rooted it, did the steps of sd card flashing. First I was stuck in the boot loop, but after trying three times I got to the main screen (but had no touch screen) . I tried to do a factory reset, and still no touch screen. I was freaking out as I have done this already to other earlier nook colors..... so I went back and just flash CM7, it booted up fine, and there are no longer issues.
I wont say that it is the absolute fix, but flashing CM7 was the only thing that worked for me.
How do I flash CM7?
rogerrabbit12345 said:
How do I flash CM7?
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/wiki/Barnes_&_Noble_Nook_Color:_Full_Update_Guide
Sent from my PG06100 using xda premium
OK so again I tried to install ICS sneakpeak1. I went into CWR 3.2.0.1 which was on my emmc. I did it as an update and again touchscreen is not working after booting up fine, my personal wallpaper was still up so everything seemed fine, but NO-GO. After this i went again in and updated to ICS sneakpeak2, and STILL no touchscreen.
Pretty freaking frustrating since everyone seems to have a grand ol time with here nook ICS.
So if i can't have ICS running i want Nook stock 1.4, but guess what THAT TOO has no touchscreen. I've tried 1.0 1.2 and 1.3 touch screen does NOT work except for CM7! ugh
I'm having the same issue with a fairly new NC. I've flashed many CM7 nightlies on an older NC and ICS sneakpeek 1 to an older NC with no issues. I've flashed a few CM7 nightlies on this NC as well, but ICS sneakpeek 1/2 have a non-working touchscreen on the new NC.
How new is your NC? I wonder if something changed with them.
(And yes I'm certain its an NC, not an NT)
Also, I have the same issue on a refurbished nook that I was just issued earlier this month. I remember something a few months back about a refreshed nookcolor with some different hardware component. Correct me if I am mistaken, please.
Well, we're at least two people with newish NCs and issues with the current ICS builds, maybe 3 - Zeno, how new is your NC?
Maybe it's a small change with the touchscreen controller or something. I went back to CM7, and went through the dmesg log after boot.
This seems to be the area (approx line 190) about the touchscreen:
Code:
<6>cyttsp_init:Cypress TrueTouch(R) Standard Product
<6>cyttsp_init:I2C Touchscreen Driver (Built Dec 6 2011 @ 13:47:20)
<4>cyttsp:Reseting TMA340
<4>cyttsp:Start Probe 1.2
<7>hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
<4>cyttsp:No TMA340 found; exiting probe.
<4>cyttsp:probe failed: -19
<6>ft5x06_init() - FT I2C Touchscreen Driver (Built Dec 6 2011 @ 13:47:20)
<6>ft5x06-i2c 2-0038: ft5x06_probe() - FT5x06 found on I2C bus.
<6>android_usb gadget: high speed config #1: android
<7>musb_hdrc periph: enabled ep1in for bulk IN, dma, maxpacket 512
<7>musb_hdrc periph: enabled ep1out for bulk OUT, dma, maxpacket 512
<4>max8903_charger_enable: dtct_status 0x04
<6>input: ft5x06-i2c as /devices/platform/i2c_omap.2/i2c-2/2-0038/input/input2
I wonder if someone running an older NC with CM7, or even with ICS, can share theirs and we can check for any differences
Just got mine about 3 weeks ago, so yes its a nook color and its brand new. It came with 1.3 already installed.
ZenoGia said:
Just got mine about 3 weeks ago, so yes its a nook color and its brand new. It came with 1.3 already installed.
Click to expand...
Click to collapse
Hi,
My Nook Color is also new, and touchscreen in ICS is also not working for me. I definetly think something has changed in hardware, as it's not a coincidence it isn't working for us. I have noticed however, when the screen dims, and I tap it, it comes back, which means it's probably just not detecting the touches properly.
EDIT: The dmesg log is very interesting. The Nook Color is supposed to come with a TMA340 touchscreen controller. But the log fails to find a TMA340 and loads an alternate driver for a different touchscreen controller. Which means your correct insz, it looks like there is a different touch controller in newer Nook Colors, and fattire's ICS is probably missing the driver. I think someone should contact him about that.
This post seems to confirm that suspicion.
bobstro said:
This post seems to confirm that suspicion.
Click to expand...
Click to collapse
a-ha! Thank you, that's what it was.
I am using an 8gb Sandisk class 4 card
I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1000957
I used cm_encore_full-253.zip as my firmware and I also put Gaps on my micro sd.
After making the bootable sd card I loaded it in my nook color and it loaded the android installer. Everything seemed to load fine and it finished and turned my nook color off. I turned it on and it loads the stock B&N firmware. What am I doing wrong? My nook color software version is 1.3.0 I have run into a ton of roadblocks with this and have been getting frustrated. I have modified a PS2, a couple PSP's, and about 10 Wii's. The Nook color has been the most difficult, but it should have been the easiest. Please help. Thanks
SD card madness
When this happens to me, and it does, I check the connectors on the SD card. Gold oxidizes, and my NC at least seems to have an issue with this. I have to periodically cleans the connectors, which also seems to attract particles of food and whatnot.
My card really seems to hate high humidity, and requires that I cleans it after exposure to same.
The more you handle them, the more likely these cards may be exposed to something that causes their function to conditionally deteriorate. I have found that when on the go, even a mild fingernail scraping across the contacts will restore functionality. Inserting and removing multiple times sometimes has the same effect.
Weird and weirder...
( p.s. I forgot to mention, sometimes these cards need their connectors cleaned BEFORE you use them - a malady of old game systems it seems that may have returned - although some people never have any such issues.... )
Since you didn't tell us how you got it done, I have to assume that you knew what and how to do.
Just a suggestion: do install ROM first then GApp.
votinh said:
Since you didn't tell us how you got it done, I have to assume that you knew what and how to do.
Just a suggestion: do install ROM first then GApp.
Click to expand...
Click to collapse
Yes that is what I did wrong, I tried to install both at once. Got it working now. thanks