Related
I haven't taken the plunge into the world of android (yet). I am just using my B&N NookColor "as is". My problem is that after I transfer a book from my XP desktop and disconnect the NC, my PC keyboard won't work until I reboot. (Yes, I first clicked on the safely remove or eject or whatever it is called thingy) I contacted Nook support and they said I needed to contact Dell (I haven't tried that yet). I am just wondering if anyone else is having a similar problem.
BTW, I think I will try rooting eventually but at the moment I am still a chicken. This is my first android device. I am reading up on it but I'm having some difficulty with all the abbreviations and "geek speak". At any rate I would like to thank all the people who have worked so hard this project.
Did you try to unplug the keyboard?
I had something funky happen with my Chinese knockoff Haipad G10 running on 2.1 Every time I connected it my keyboard and mouse would behave very erratically, stutters, stops, things of that sort. Both are wireless. Unplugging the G10 would bring them back to normal.
Not that this is the same thing, but Android is the common denominator here.
As I suggested, switching USB ports should fix it without the need for a restart.
I had something similar happen when i plugged in my nook for the first time, all my usb stuff went nuts and died until the nook had succesfully mounted as a drive, i think it might have to do with the charging voltage it pulls. couldnt get things working until i unplugged them and replugged them with the nook disconnected.
Thanks for trying to help, devis.
This is what I just did: connected NC to PC and moved a file. I properly ejected the Nook and then pulled out the Nook usb cord from the PC. At that point, my PC keyboard wouldn't respond. I removed the keyboard usb connection and put it into a different usb plug. No joy!
Perhaps I misunderstood or perhaps the problem is deeper.
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.
My rooted Nook Color reboots itself randomly sometimes, and also gets stuck in a reboot loop as well. I've been searching around and have seen several other cases of this but with no resolution.
After I first got my Nook Color, I started off by sideloading the latest B&N 1.1 update. Then I went ahead and used Auto-Nooter 3.0.0 (1.1 only). That's it really... aside from loading a few other apps from the Market like LauncherPro, BeautifulWidgets, Astro, JustPictures, & Screen ON Widget.
The first time around my Nook Color worked for about 3 weeks with no problems before the boot loop happened. I figured it was a fluke, so I restored to stock and then started back from scratch with updating and then Auto-Nooting again. This time around, it only took about 2-3 days to get back to this boot loop issue.
Anyone else come across this? You think I just have a bad Nook Color, maybe a hardware issue? Like I said, I did search around on Google and did come across a few threads where people were reporting the same thing. The only answer anyone would get was to restore and start from scratch. I just wish there was some type of debugging I can do to see what's happening....
I have the same issue with no resolution. Did you find anything? I think i'm moving to an iPad if I cant sort this today.
OK, here's the situation:
Nook Color running CM7 7.0.3 from SD card. Been running this since May without problems.
Last night I plugged in the Nook to charge and turned off the screen.
This morning I unplugged the charger from the Nook and it chirped. Never heard that before. I turned on the screen and it was at the out-of-the-box Nook lock screen. I swiped to unlock and found that overnight my Nook had somehow reset itself back to 1.2 of the Nook OS. I looked at the SD card contents and nothing was here.
I powered off completely, then back on, and all was well, back into CM7 from the SD card.
Any idea what caused this? I don't remember seeing any issues like this since I started following these forums in May.
Thanks in advance for any suggestions.
Steve
By "reset itself to back to 1.2," do you mean you had 1.3 installed and somewhat personalized previously, or just that it unexpectedly booted into stock instead of CM7?
I have no clue what happened either way--I'm just not sure what you're describing. If you were running CM7 from SD, stock was always still there, and some power irregularity caused your NC to shut down unexpectedly, and apparently fail to boot from SD, causing it to boot from stock on the internal storage instead.
Additionally, something may have triggered a factory-reset, but in that case it would have walked you through set-up again, and you said it took you straight to the lockscreen.
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.