Related
hello!
my nook likes to tap all by itself, sometimes in different places but generally in the center of the screen. i just bought it on onesaleaday.com a few days ago and had plans to upgrade to the latest cm7 nightly. my questions are:
1. is the tapping problem one that will go away when i boot my nook from an external microsd, running cm7?
2. since im under warranty for a year, is there are reason i should consider fixing the problem and/or returning my nook prior to putting cm7 on it?
3. if i do run cm7 from an external microsd card, will my nook always be stock and unmodified when i remove the card, thereby allowing me to make warranty claims on hardware if need be?
and on a related note, i bought a microsdhc card prior to hearing about how sandisk is the best. i bought this one: Transcend 32 GB Class 4 microSDHC . i may be able to return it for a sandisk.
4. does anyone have specific experience running this card or know as to its functioning on the nook?
5. if i have problems running cm7 on this card, is it easy to use the internal card on the nook for cm7, and then use the external one for my music collection? obviously this would void my warranty.
thank you!
sorry, i know some of these could be answerable by searching in depth, but i couldnt find anything particular to the tapping problem i have.
Do you have sweaty hands?
If the screen gets at all moist, it will get false touches. If that occurs, switch the screen off then on again, it should reset it.
If/when you root it, and the issue is still there, run nook recalibrator to recalibrate the display. Worked for me
Sent from my NookColor using Tapatalk
whatismouse said:
hello!
my nook likes to tap all by itself, sometimes in different places but generally in the center of the screen. i just bought it on onesaleaday.com a few days ago and had plans to upgrade to the latest cm7 nightly. my questions are:
1. is the tapping problem one that will go away when i boot my nook from an external microsd, running cm7?
2. since im under warranty for a year, is there are reason i should consider fixing the problem and/or returning my nook prior to putting cm7 on it?
3. if i do run cm7 from an external microsd card, will my nook always be stock and unmodified when i remove the card, thereby allowing me to make warranty claims on hardware if need be?
and on a related note, i bought a microsdhc card prior to hearing about how sandisk is the best. i bought this one: Transcend 32 GB Class 4 microSDHC . i may be able to return it for a sandisk.
4. does anyone have specific experience running this card or know as to its functioning on the nook?
5. if i have problems running cm7 on this card, is it easy to use the internal card on the nook for cm7, and then use the external one for my music collection? obviously this would void my warranty.
thank you!
sorry, i know some of these could be answerable by searching in depth, but i couldnt find anything particular to the tapping problem i have.
Click to expand...
Click to collapse
I've heard that the phantom taps have been related to when the NC is plugged in. I know I experienced a few when I first got mine, but I haven't in a long time.
Does this only happen when you have the NC plugged in. Also, have you given the screen a good clean to make sure all dirt, grim, oil, etc are off of it (I know at least once that was my problem).
There is no reason not to try CM7 on it before claiming any warranty. As far as where you want to run it from, that is entirely up to you and what you feel comfortable with. Running it off eMMC is not a big deal since the NC boots off SD card first you can always revert back to stock B&N OS on it.
There are a lot of tutorials on how the roms and such for the device, just dig around.
Phantom taps seem to only happen on my NC when it is plugged into the wall charger, but doesn't seem to happen at all while hooked up to the computer. Random zoom in and out and highlighting of words from a single touch. Sometimes my finger can be 2" away from the screen and it sets off the touch sensor.
Thanks everyone. I think it must have been a dirty screen because i havent had any problems today after cleaning. The browser on froyo is still terrible, it just wont respond to my scrolls or taps sometimes but if i turn off the screen and back on it always works again. All of the tapping problems i was having was with the nook unplugged.
I hate to have to write this asking for help but I wasn't able to use the other posts I found to help me. The directions for touchnooter seemed straight forward, but I am stuck anyway. Here is what I did and what is happening, and what I have tried to remedy situation. It is a bit long, but I wanted to be as complete as I can.
I have a new nook bought at end of March so assuming it has latest update. I followed directions and was able to get touchnooter onto microsd card. I stuck it in nook and turned on. I got an instruction screen saying to take card out when screen goes black and reboot. My screen did go dim but you could still see the writing behind. I wasn't sure if this what they meant by going black or if I was waiting for complete darkness. I think I panicked for a second (don't know why) and might have rebooted with the card still in (would this have created a problem that I will be describing).
So upon rebooting, it goes through the same reboot nook screen, gets to a screen with an n and the balls and that is the furthest I have gotten it. Messing with the power key seems to initiate a reboot, but it still never makes it past the n screen. Cannot turn off the nook. I was able to get it to give me the factory reset message by doing the failed reboot 8 times. I tried that a couple times but wasn't able to get any further past the screen with the n, so it seems it may not be doing any resetting. I tried repeating the rooting process (except for the shuting down the nook part since I can't actually get it to shut down) and it gave me the same rooting instruction page but no change the problem of not getting past n screen.
I have seen people asking similar questions about rooting with something else called CNW or something because the touchnooter didn't work for them but I didn't understand the instructions and wanted to get help first before trying something else. I had also read that there is something called a factory restore, which is supposed to be different from reset but I don't know how to do that. I downloaded barnes and nobles latest update thinking I would just reload it/ but I can't see my nook from my computer (do I need to download some drivers? Or is this because it can't get past the n screen?). I tried using a different microsd card in case the first was faulty, but didn't help.
Does it seem there is something wrong with the touchnooter content on the card, like maybe it doesn't work with the latest nook update? Also wanted to mention, I did not do a backup before trying to root. I originally planned to but after I was done researching what I needed to do and got to the touchnooter downloading directions, they didn't mention it, so I didn't do it (besides that, I don't know how to do it and don't know if it would help in this situation anyway). Could it be that the nook itself has a problem?
Anyway, I would still like to root but would be happy to at least get a basic nook back. If you have made it this far in reading my problem, what do you think I should try? I am thinking of taking it back since I don't think it actually rooted but if I can fix it, that would be better. Thanks in advance for anyone who takes the time to work on this with me. I wish I had someone right in front of me to ask questions to but this the next best thing.
Thanks!
Tara
I am really leaning towards just seeing if I can return it. The instructions for touchnooter seemed so straight forward and I thought I could handle it. Since it didn't work and I don't even know if it was a problem with something I did, the device, or the touchnooter (since other people with new nooks are having similar problems), then I don't even know if it is something that will work at all. Trying to use some of the other methods are just way beyond my ability without more detailed instructions. Sigh.
http://forum.xda-developers.com/showthread.php?t=1289233
Should help You to restore to factory state. After You can use any other ways to root(if You want )
PS: From what You say, You haven`t done anything irreversible yet. So calm down reread the forum and go on
Thanks for the reply! I did come across that at one point but didn't try it. But I will give it a go once I get the nook charged (it discharges by the end of everyday while having this prob so I have to charge it back up everyday). These directions look pretty straight forward though, so I am crossing my fingers.
"I did not do a backup before trying to root...besides that I don't know how to do it and don't know if it would help in this situation anyway."
After you get your Nook back to stock state don't shy away from making the backup. And do it before you make any other changes. Having a pristine image of your Nook's original state will make you nearly bulletproof. Give yourself time to understand the issues involved in making the backup. This new knowledge will generalize to other aspects of rooting.
The instructions for making the backup are here but you may find this isn't enough information. I found this post from Renate extremely helpful.
Finally, it will be helpful to know that, done correctly, your Nook v.1.1.2 backup will be exactly 1,958,739,968 bytes.
Efemmeral said:
Finally, it will be helpful to know that, done correctly, your Nook v.1.1.2 backup will be exactly 1,958,739,968 bytes.
Click to expand...
Click to collapse
Depend on nook memory chip used (manufacturing date) it should be either 1,958,739,968 or 1,962,934,272 bytes
ApokrifX said:
Depend on nook memory chip used (manufacturing date) it should be either 1,958,739,968 or 1,962,934,272 bytes
Click to expand...
Click to collapse
Yes? I have always gotten 1,957,616,640.
Hmm, mine is 2.000.683.008.
EDIT: I think that was 1.1.0 (or 1.1.1?)
Hello Folks!
I guess my question will make me sound dumber than a box of rocks, but here goes. A bit of history before I make myself an idiot. I've only been fooling with computers and these new tech. machines for about a year and a half now and for the most part been having an enjoyable time. I'm 70 years old and I'm not the sharpest crayon in the box anymore, time has dulled my tip a bit. I've been given a Nook Tablet as a Christmas gift by 2 of my grandsons, I intend to change the Android on it to the Ice Cream version but before I do I want to practice on something else first. So I bought a used Nook Color from a lady at church for $50 and I want to try and make a SD card to run the new Android from. The reason I want to use SD card is that there are over 200 books on the Nook and I would like to eventually read a lot of them. I guess I'm just greedy.
I've spent most of the weekend reading this forum information, but unfortunately the more I read the more confused I get. There is a tremendous amount of information to try and digest here and sometimes some of it seems to contradict itself. What are the different types of modified Androids that can be used? Can the Andriod that is installed on the SD card be modified so that more applications can be stored on it? How difficult is it to install the software that allows you to speed up the Nooks processor, that is, can a raw noob do it?
I'm sorry if I've yacked too much. I'm still learning how to correctly ask the questions.
Hey, knock off the old man stuff. I am 67 and my crayon tip is still sharp (although there are some here that would disagree with that, LOL). This nook color stuff is not that hard. I would recommend putting cm7 on sd first to get your feet wet. Then if you feel like experimenting move on to cm9. You can get the rom at cyanogenmod.com (for the encore - Nook Color). I recommend 7.2 RC3. It comes already rooted and overclocked so you can speed it up. And it has plenty of room for apps if you put it on a 4Gb card or larger. If you can afford it, I recommend 16GB (and Sandisk, class 4). Follow this guide to set it up:
http://forum.xda-developers.com/showthread.php?p=12240928
But look at my tips thread linked in my signature to get an updated image to use instead of the one in the thread above. Also read all of section B in my tips, as it all applies to the sd installation. If you need more help, just come back here.
GrampaBear said:
Hello Folks!
I guess my question will make me sound dumber than a box of rocks, but here goes. A bit of history before I make myself an idiot. I've only been fooling with computers and these new tech. machines for about a year and a half now and for the most part been having an enjoyable time. I'm 70 years old and I'm not the sharpest crayon in the box anymore, time has dulled my tip a bit. I've been given a Nook Tablet as a Christmas gift by 2 of my grandsons, I intend to change the Android on it to the Ice Cream version but before I do I want to practice on something else first. So I bought a used Nook Color from a lady at church for $50 and I want to try and make a SD card to run the new Android from. The reason I want to use SD card is that there are over 200 books on the Nook and I would like to eventually read a lot of them. I guess I'm just greedy.
I've spent most of the weekend reading this forum information, but unfortunately the more I read the more confused I get. There is a tremendous amount of information to try and digest here and sometimes some of it seems to contradict itself. What are the different types of modified Androids that can be used? Can the Andriod that is installed on the SD card be modified so that more applications can be stored on it? How difficult is it to install the software that allows you to speed up the Nooks processor, that is, can a raw noob do it?
I'm sorry if I've yacked too much. I'm still learning how to correctly ask the questions.
Click to expand...
Click to collapse
And in keeping with the older guy thread concept (66), you're talking about two different devices, the Nook Tablet (NT) and the Nook Color (NC). The newer NT is much more difficult to deal with than the older NC. It's not as straightforward to install anything on the NT as it is for the NC. Also try to differentiate between the device hardware and the operating system software. The software will get the most out of a particular devices' hardware. The NC's processor is single core; the NT is dual core. The Ice Cream Sandwich (ICS) Android operating system applications are pretty much the same between the two devices, but the operating system interface between the applications and the hardware (the kernel) is different, so overclocking, over/undervolting, etc. will be different, too.
Just keep reading; that's how to sharpen the tip. It's never permanently dull until everything else is.
shumash said:
And in keeping with the older guy thread concept (66), you're talking about two different devices, the Nook Tablet (NT) and the Nook Color (NC). The newer NT is much more difficult to deal with than the older NC. It's not as straightforward to install anything on the NT as it is for the NC. Also try to differentiate between the device hardware and the operating system software. The software will get the most out of a particular devices' hardware. The NC's processor is single core; the NT is dual core. The Ice Cream Sandwich (ICS) Android operating system applications are pretty much the same between the two devices, but the operating system interface between the applications and the hardware (the kernel) is different, so overclocking, over/undervolting, etc. will be different, too.
Just keep reading; that's how to sharpen the tip. It's never permanently dull until everything else is.
Click to expand...
Click to collapse
You're right of course. I was talking about how to update his NC. I also have an NT and it is much more difficult to deal with on modding.
Actually, after playing with the rooted 1.4.2 stock NT, I see no reason to move to CM yet on it (BT is the only thing missing on stock), even though I have CM7/CM9 on dual boot SD. After CM gets more stable on the NT, maybe.
Sent from my Nook Color running ICS and Tapatalk
Old age
Gentlemen,
Thanks for the replies. I don't feel old most of the time, just when I have some of the youngsters whizzing past me. Computers, smart cell phones, and Nooks are fairly new to me, never touched one until after my wife passed a year and a half ago. Now I need one to keep in touch with my family (4 kids, 12 grandkids(and 3 more on the way), and 4 greatgrand kids (and 2 more coming).
Due to a accident last fall the old brain sometimes has a bit of a hard time comprehending things now and then, so I get a bit frustrated and I may ask questions that seem to be a repeat. Hope you all can forgive that.
Thanks!
The tablet my grandsons gave me is a Lenovo A1 not a Nook tablet. It is running Android 2.3 and I want to upgrade to Ice Cream Sandwich when I'm confident enough in my abilities.
Well done, gentlemen.
These two will have you building your own Android OS before you're done, GrampaBear.
GrampaBear said:
The tablet my grandsons gave me is a Lenovo A1 not a Nook tablet. It is running Android 2.3 and I want to upgrade to Ice Cream Sandwich when I'm confident enough in my abilities.
Click to expand...
Click to collapse
You might want to check out these for information on the Lenovo Ideapad A1:
http://androidforums.com/lenovo-ideapad-a1/
http://forum.xda-developers.com/showthread.php?t=1355319
There's very little activity for this device on xdadevelopers, and what we know is primarily for the Nook Color.
Well, I started the process of making an SD card with Android on it. I am now thoroughly convinced I am near as dumb as a box of rocks. I download the agnostic sd card image and the win32imager. I didn't realise I needed to uncompress the files ( this was a first for me, never had to do it before ). I finally figured out I needed WinZip and I downloaded the trial version and ran the program. I took a old Kingston 4 GB class4 micro sd card (I have ordered a Sandisk from newegg but didn't want to wait to try) and formatted it to fat32 with a sd formatting program. I then ran Winimage (with my fingers crossed for I was not sure of what I was doing) and I think I have the image on the sd card, at least when I look at the card it windows it says boot on the sd icon. I went to the site where the C7 images are kept, but could not get one to download ( this was around 11 pm last night ). One problem I have is that I have no idea what I'm looking for when I pick a file. Could you tell me which one I should be using? It says I should write the image to the card, put the card in the nook and boot it. OK! I'll give that a shot, but how exactly do I get the Nook to boot off the sd card and how exactly does the Nook know what to do with the program? Will this mess up the Nook and the programs on it?
I knew that this would be a project, but after 12 hours of reading and trying I've become a bit frustrated. Maybe someone would take on a project and write a forum called The Big Dummy's Guide to Installing CM7 to a SD card and do a step by step instruction that tells us dummys what we should be seeing as we do this.
Funny you should ask about the dummies guide to SD installs. Taosaur just gave me a link to his here:
http://taosaur.blogspot.com/2011/09/running-cyanogenmod-7-from-sd-nook.html
He gives links for the CM7 files. Pick the CM 7.2 RC3.
Once you get the SD set up right and the CM zip on it, just put in your nook and boot. Everything is automatic and does not harm your stock install at all.
Sent from my Nook Color running ICS and Tapatalk
Thanks for answering my post. Looks like I'll be starting all over with the process again later this evening. You must have been doing this work for quite a while with the knowledge you have.
Well, for now I'm taking my 6 1/2 year old great-granddaughter, a couple of fishin poles, a can of worms, and we're walking down to the pond to catch us some bluegills for dinner. Need to have a little grandpa fun and let the ole brain relax for a bit.
GrampaBear said:
Well, I started the process of making an SD card with Android on it. I am now thoroughly convinced I am near as dumb as a box of rocks. I download the agnostic sd card image and the win32imager. I didn't realise I needed to uncompress the files ( this was a first for me, never had to do it before ). I finally figured out I needed WinZip and I downloaded the trial version and ran the program. I took a old Kingston 4 GB class4 micro sd card (I have ordered a Sandisk from newegg but didn't want to wait to try) and formatted it to fat32 with a sd formatting program. I then ran Winimage (with my fingers crossed for I was not sure of what I was doing) and I think I have the image on the sd card, at least when I look at the card it windows it says boot on the sd icon. I went to the site where the C7 images are kept, but could not get one to download ( this was around 11 pm last night ). One problem I have is that I have no idea what I'm looking for when I pick a file. Could you tell me which one I should be using? It says I should write the image to the card, put the card in the nook and boot it. OK! I'll give that a shot, but how exactly do I get the Nook to boot off the sd card and how exactly does the Nook know what to do with the program? Will this mess up the Nook and the programs on it?
I knew that this would be a project, but after 12 hours of reading and trying I've become a bit frustrated. Maybe someone would take on a project and write a forum called The Big Dummy's Guide to Installing CM7 to a SD card and do a step by step instruction that tells us dummys what we should be seeing as we do this.
Click to expand...
Click to collapse
Leapinlar's post will answer your questions, but here's a few things to watch for that may concern you:
1. It takes a while for the initial install, and you may see a black screen without any indication of activity. Don't panic! If it lasts more than 20 minutes or so, turn the Nook off, pull the sdcard out, and start again. Don't be afraid to redo everything.
2. The first time it successfully boots into Android, you will see the introductory splash screen for what seems an inordinately long time. It's setting up files and processes so just let it run. Once again, if it takes more that 20 minutes or so, there's most likely some problem.
2. The Kingston card may be sloooow, so my comment above is even more possible. Because the Kingston card is so slow, when you finally boot into Android on it, you may think that the system is too slow or error-prone to run on an sdcard. You may get popups during boot up, when you're running programs, or when its just sitting there, saying something to the effect that so and so program has a problem or had a fault or whatever, and asking you to wait or "force close" (FC). This is probably caused by the card. Your Sandisk card will generally not have those problems (I've been running for over a year on an 8gb Sandisk card with no problems and very snappy response).
Thank you
Shumash,
Thank you for the information. I tried my first try at making a card tonight, it appears to be a no go. Left the Nook alone for an hour and 15 minutes with nothing apparently happening. I will reformat the card and try again tomorrow. I want to thank all who have written to help me along. I know what a pain in the kester having to work with absolute beginners can be.
GrampaBear said:
Shumash,
Thank you for the information. I tried my first try at making a card tonight, it appears to be a no go. Left the Nook alone for an hour and 15 minutes with nothing apparently happening. I will reformat the card and try again tomorrow. I want to thank all who have written to help me along. I know what a pain in the kester having to work with absolute beginners can be.
Click to expand...
Click to collapse
I see you used winimage to burn. Do not use 'write disk' to burn it. Use 'Restore Virtual Disk Image to physical drive' in the same menu. That's why I recommended win32diskimager. It is simpler to use for noobs.
Sent from my Nook Color running ICS and Tapatalk
Shumash,
I did use win32diskimager but I apparently did something wrongin the process. I will try again tomorrow it's late and I'm a bit tired.One thing that I will be doing also is trying to learn as much about Android as I can, though it may need to be in a bit simplified format. If anyone can suggest available information this old geezer will appreciate any guides to it.
I finally did it!
It took me 6 trys and I'm not sure what I did right this time, but I finally had success. The first 5 trys all I would get on the screen were 3 lines going across the screen about 40% of the way up and nothing else. The last time it booted and took a bit of time probably 12 - 15 minutes working and then shut itself down. I was thinking it was another failure and held the power button down for a few seconds to restart and Bingo! up came the Android window. I messed around a bit and set up the wireless and pulled up the internet. I LIKE IT!!
It is a bit slow and I'm assuming the Sandisk card will fix that when it finally arrives. It didn't freeze up or anything just ran a bit slow. The Lenovo A1 that my grandsons gave me is always locking up.
The only other thing that I have a worry about is the micro sd card reader in the Nook. I did have a pretty hard time getting the card in and out of the reader slot. I've labored with my hands all of my life and I have developed rather thick and calloused fingers and a bit of arthritis doesn't help either. I can not physically fit the tip of my finger into the little open loop area for the SD card reader. I had to use a tweezer from my fly tying kit to insert and remove the card from the Nook. After I get this type of card down pat I'd like to see if there is a way to leave the card in all of the time and be able to boot from the card or the nook reader software.
THANKS AGAIN! I wouldn't have succeeded without all of you gentlemens help.
While I was finishing typing this message my 13 year old grandson has been fooling around with the Android on the Nook. He said to tell you, that you all are AWESOME!
GrampaBear said:
Shumash,
I did use win32diskimager but I apparently did something wrongin the process. I will try again tomorrow it's late and I'm a bit tired.One thing that I will be doing also is trying to learn as much about Android as I can, though it may need to be in a bit simplified format. If anyone can suggest available information this old geezer will appreciate any guides to it.
Click to expand...
Click to collapse
If you're using windiskimager, getting everything straight can be a bit confusing. Make sure that you're doing the following four steps on your PC, not the Nook!
1. To the right of the box that says "Image File", there is a blue folder picture. Click on it and select the image file. It should be something like "generic-sdcard.img". It's easiest if the image file is in the same directory/folder as the win32diskimager software.
2. To the right of the blue folder looking picture is the selection box for the location where this image will be written. It says "Device" right above it. If it is the wrong drive letter, click on the arrow at the right of the box. Select the letter of the sdcard. Use a file manager or windows explorer to find out which drive letter the sdcard is. Make absolutely sure you know which drive it is!
3. After you have properly selected the image file and the correct drive letter, click "write" and wait for it to complete.
4. After the image has been written, you will have to put the CM7 (Gingerbread) or CM9 (ICS) flashable zip on the sdcard in its root directory (called "/boot" in a file manager or windows explorer). Copy the one you want onto the sdcard.
Once the above is done, remove the sdcard from the PC and put it in your Nook. Boot the Nook up, and it will do everything else automatically.
GrampaBear said:
The only other thing that I have a worry about is the micro sd card reader in the Nook. I did have a pretty hard time getting the card in and out of the reader slot. I've labored with my hands all of my life and I have developed rather thick and calloused fingers and a bit of arthritis doesn't help either. I can not physically fit the tip of my finger into the little open loop area for the SD card reader. I had to use a tweezer from my fly tying kit to insert and remove the card from the Nook. After I get this type of card down pat I'd like to see if there is a way to leave the card in all of the time and be able to boot from the card or the nook reader software.
Click to expand...
Click to collapse
It's funny you should mention old hands and micro chips. I have always had a hard time with the chip and that darned slot. Yesterday I was changing the chip and it popped out. I was sitting in my big recliner, you know the kind all old folks have, LOL. Anyway, the chip went down the crack in the chair. I could not find it. I finally turned the chair on it's side and shook it. It came tumbling out. LOL.
So you will be glad to hear there is a way to set up your stock so that you can use the same SDcard. The only complication is your stock must be rooted first. But that is simple to do. But maybe you want wait on that till you are more confident. Once it is rooted you can look at my tips thread, item B3, and I tell you how to set up stock to use the same SD so you don't have to keep changing cards. There is another method of setting it up without rooting first, but it is more complex to do. If you want me to reference that thread, let me know.
Leapinlar,
I know what you mean about the old folks and recliner thing. I have a big old style chair with a foot stool that my wife bought me at a garage sale 38 years ago. It was well over 20 years old when she bought it. She re-upholstered it and made it into the most comfortable chair for a large man ever. I'm kinda like Archie Bunker with that chair, it's my chair and you don't sit in it unless I offer it to you.
I appreciate all the help you all have given me, this is all new to me and sometimes I get to feeling a bit flumoxed. I'm having a bit of a problem getting the Android gapps program to work at the moment. Think I may be copying it to the wrong spot, but Windows only seems to show me one spot to copy to. I'll get it figured out it'll just take time. It may be a bit before I feel brave enough to root the Nook.
Still waiting for the Sandisk card to arrive. The Kingston card seems to work but is really slow at times.
You're copying it right. As you turn the nook on with the card in the slot, hold down the n key and choose to boot into the SD recovery partition.
Sent from my NookColor using XDA
Hello all: posted this elsewhere, perhaps on wrong page. lots of views, alas no replies. Perhaps nobody loves me....
***********************************************************************************************************************
After a bit of research I've just bought a Nook ST Glow in the UK. I've read forums and watched YouTube videos of rooting these devices by various methods.
I then came across some forums about CM7.
Now if I understand this correctly, and apologies if I don't (I'm very new to Nook and Android), you can prepare a microSD card with a version of Android OS, pop it into the Nook and boot from that card to access the Android Market etc. The big advantage (for me at least) is to be able to remove the card and boot the Nook back into standard ebook reader functionality.
I have spent a couple of hours reading through XDA posts but haven't stumbled upon any posts about Nook ST Glow and CM7.
******************************************
So, my noobie question is simple: Can I configure a microSD card with an OS and files that will boot my Nook ST Glow into the unlocked Android world.
******************************************
Any advice or pointing in the right direction much appreciated.
Craig
You are probably reading about the bootable CM7/CM9 uSD cards for the NOOK Tablet and/or NOOK Color. Those, sadly, are not for the NOOK Simple Touch or the NSTG, which you have.
Rooting your NSTG will give you access to the Android Market. Keep in mind, the device only runs Android 2.1 Eclair, so a lot of software simply won't work. BE SURE to only follow procedures for the NSTG. The procedures for rooting the NSTG are not the same as for the NC, NT or even the NST.
Be sure to back up your device before you try anything. If you screw up badly, it can be very difficult to recover some of the device-specific info.
bobstro said:
You are probably reading about the bootable CM7/CM9 uSD cards for the NOOK Tablet and/or NOOK Color. Those, sadly, are not for the NOOK Simple Touch or the NSTG, which you have.
Rooting your NSTG will give you access to the Android Market. Keep in mind, the device only runs Android 2.1 Eclair, so a lot of software simply won't work. BE SURE to only follow procedures for the NSTG. The procedures for rooting the NSTG are not the same as for the NC, NT or even the NST.
Be sure to back up your device before you try anything. If you screw up badly, it can be very difficult to recover some of the device-specific info.
Click to expand...
Click to collapse
Thanks for the reply Bobstro. I've read a lot about rooting the GLow, and have downloaded what I think I need from a couple of excellent articles on it (using Glownooter).
To be honest, I'm only after Sudoku and perhaps a good chess program. nothing much else (I have an excellent Blackberry for all other comms etc) so the risks involved with rooting (it all seems to "cluncky") seem to outweigh the benefits.
Thats why the option of a bootable MicroSD card seemed so attractive. Ah well, thanks for the information.....
Rooting is not all that big a deal if you're cautious and follow instructions well. I've rooted my two NSTs several times each with few problems. I have only loaded a few additional apps myself. My rooting focus was more on power savings (running Tasker) and time sync (using ClockSync) when I travel.
(BLACK SCREEN OF DEATH)
OK, I have a dead Nook on my hands - non-responsive completely. A coworker of mine bought one of those CM7 cards off of Ebay and it worked fine, but had some connection issues, so I suggested he make a move to PA. Of course, I was the one that was going to do this, so I installed CWR to the EMMC, rebooted, hit N, and booted to EMMC recovery no problem.
Here's where things got stupid:
In recovery, I attempted to install PA without removing the sd card and used the internal SD Card to grab the image. Yeah, I know... Browbeating not necessary... It was taking too long and appeared stuck, and then suddenly the unit just appeared to power down. That was it. No more recovery, the card no longer worked, NOTHING!
Hooked it up to my PC and for a second or two when you hook it up, you can see in the device manager, the Motorola device pops up (I own a Motorola phone, so I assume the drivers are kicking in), and then it goes away. Long press power, do it again, same results. Still no screen, no nothing.
So I figure the 16GB CM7 card (Sandisk SDHC) still has to be useful for creating a recovery card, right? After all, whoever created it originally was able to stuff a bootloader on there, right?
So here's what I tried in terms of tools:
win32diskimager .1 r15
win32diskimager .7
WinImage 8.5
with these, I have tried the following images:
16gb_clockwork-3.0.2.8.img
generic-sdcard-v1.3.img
TWRP-2.1.8-bootable-SD.img
And I used MiniTool Partition Wizard to remove the partitions after each attempt and reformat back to its full 16GB.
The only time a burn was unsuccessful was on the 16GB clockwork with Win32DiskImager - it gave an error stating it couldn't find sectors at 99%. I tried an 8GB image too, but while it burned successfully, no dice.
Alright, so here we are, me at the end of my wits, you reading this tale of woe, and a coworker without a functioning device. The device has charged all night. I owned an NC for years and was mod-happy during that time, and although I had BSOD, I was able to fix it easily. This is a 1 year old BNRV200 (pretty sure they didn't switch up the models).
Help? Advice? WT%#$%^?
EDIT: ADB does not recognize the device when connected.
Go to my NC partition repair thread linked in my signature and follow the procedures there.
Use SDFormatter free on the web for formatting your card before burning one of my bootable CWM images. Don't use partitioning software. The NC is real finicky about how cards are burned. Look at my NC Tips thread and read item A9.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Go to my NC partition repair thread linked in my signature and follow the procedures there.
Use SDFormatter free on the web for formatting your card before burning one of my bootable CWM images. Don't use partitioning software. The NC is real finicky about how cards are burned. Look at my NC Tips thread and read item A9.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
OK, so I used SD Formatter v3.1, size adjustment ON, Full Format (Erase)
Then I used win32diskimager v.7 with CWM-6.0.1.2-bootable_SD - still no boot.
Went back to SD Formatter, rinse, repeat.
Then I used win32diskimager v.1 r15 with same image - still DOA.
Anything I'm missing? I'm going to try 5.5.0.4 in the meantime, but I have my doubts that it will make a difference.
majorpay said:
OK, so I used SD Formatter v3.1, size adjustment ON, Full Format (Erase)
Then I used win32diskimager v.7 with CWM-6.0.1.2-bootable_SD - still no boot.
Went back to SD Formatter, rinse, repeat.
Then I used win32diskimager v.1 r15 with same image - still DOA.
Anything I'm missing? I'm going to try 5.5.0.4 in the meantime, but I have my doubts that it will make a difference.
Click to expand...
Click to collapse
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
reply
majorpay said:
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
Click to expand...
Click to collapse
brother what to tell you my nook color is also dead similarly since last 3 weeks.i also tried everything under the roof like bootable sd card.i also opened a topic in help section but did not get a single reply.i wrote to lepinllair also but even he does not know what to do . i miss my nook everyday. i appeal to nook community to please help us get out of this mess. i also get similar trying to search divers issue when attached to a laptop.also mine is getting charged fully .so i guess both of us have a similar issue. brother please let me know if you find solution .thankyou
majorpay said:
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
Click to expand...
Click to collapse
dajmaa said:
brother what to tell you my nook color is also dead similarly since last 3 weeks.i also tried everything under the roof like bootable sd card.i also opened a topic in help section but did not get a single reply.i wrote to lepinllair also but even he does not know what to do . i miss my nook everyday. i appeal to nook community to please help us get out of this mess. i also get similar trying to search divers issue when attached to a laptop.also mine is getting charged fully .so i guess both of us have a similar issue. brother please let me know if you find solution .thankyou
Click to expand...
Click to collapse
Well looks like their is Three of Us. I have been trying to fix my daughters Nook Color for about 2 weeks now. I have tried 6 different sd cards, my internal card reader and 2 external ones. I have used every version of cw recovery and twrp i can find. I have tried alot of guides. At least the ones that the downloads are still there for.
Heres to pulling your hair out.
SHOOTEMUP2.0 said:
Well looks like their is Three of Us. I have been trying to fix my daughters Nook Color for about 2 weeks now. I have tried 6 different sd cards, my internal card reader and 2 external ones. I have used every version of cw recovery and twrp i can find. I have tried alot of guides. At least the ones that the downloads are still there for.
Heres to pulling your hair out.
Click to expand...
Click to collapse
Well, here's what I can say (which may be saying nothing):
Back in the day when I had a BSOD on my old device, I was able to fix it by using TheCube's methods. I don't think he hangs around these parts anymore, but I know it was a specific sized SD card you had to have, and a pretty old version of CWR you were flashing onto the card. I remember there was only ONE version of win32diskimager that would work and it was one of the V 0.1 variants (r?). Technology has changed, people have come and gone, and this may mean absolutely squat now. I just know I had this problem on my old one and I was able to fix it that way.
All the links to those items are gone, all the files have been long since lost, and the server I used to use to house those files has long since become a thing of the past.
Maybe B&N has set trip-wires for the modding community in their "newer" revisions? I cut the red wire, and the whole thing blew up.
majorpay said:
Well, here's what I can say (which may be saying nothing):
Back in the day when I had a BSOD on my old device, I was able to fix it by using TheCube's methods. I don't think he hangs around these parts anymore, but I know it was a specific sized SD card you had to have, and a pretty old version of CWR you were flashing onto the card. I remember there was only ONE version of win32diskimager that would work and it was one of the V 0.1 variants (r?). Technology has changed, people have come and gone, and this may mean absolutely squat now. I just know I had this problem on my old one and I was able to fix it that way.
All the links to those items are gone, all the files have been long since lost, and the server I used to use to house those files has long since become a thing of the past.
Maybe B&N has set trip-wires for the modding community in their "newer" revisions? I cut the red wire, and the whole thing blew up.
Click to expand...
Click to collapse
Story of my life. always a Dollar Short and a Day Late. Well in this case a couple years late.
leapinlar said:
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Leap... Have you tested these methods? If so, can you give me a lead as to which SD reader you used? I'm not above believing that the problem is the multiple readers I have (one is internal, the other is a Chinese plastic knock-off).
I was not able to get over to my parents house to test on their Nook yet.
majorpay said:
Leap... Have you tested these methods? If so, can you give me a lead as to which SD reader you used? I'm not above believing that the problem is the multiple readers I have (one is internal, the other is a Chinese plastic knock-off).
I was not able to get over to my parents house to test on their Nook yet.
Click to expand...
Click to collapse
I use an external USB card reader made for micro SDs so I need no micro to SD adapter. A little red or grey one. I got it on eBay for $2. In fact, I bought several since they sometimes quit working. Then I use win32diskimager with no other windows open. Someone said they even had to update to the latest version (0.7, I think) from sourceforge. Any number of things could make it not boot. NCs can sometimes be very temperamental. But I have never had one I could not eventually get to boot to SD.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
I use an external USB card reader made for micro SDs so I need no micro to SD adapter. A little red or grey one. I got it on eBay for $2. In fact, I bought several since they sometimes quit working. Then I use win32diskimager with no other windows open. Someone said they even had to update to the latest version (0.7, I think) from sourceforge. Any number of things could make it not boot. NCs can sometimes be very temperamental. But I have never had one I could not eventually get to boot to SD.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Alright... Well here's where we are at this point:
Bought a Dynex 7 in 1 with specific port for MicroSD - burned v6 cwr bootable to 16GB SanDisc C4 SD using Laptop - Didn't work
Switched to main PC and burned 5.5 to 512mb Nokia C4 SD - didn't work.
Both were attempted with latest Win32DiskImager (.7) from SourceForge.
At this point, I'd lean towards a hardware failure, BUT... it's too coincidental that this occurred during a standard CWR install of a ROM. My understanding is that the Nook is supposed to ALWAYS check the SD slot prior to booting internally. Now whether there is a partition block that tells it to do this or not, I've never dug that far, but I'd have to say that this sure makes it look that way.
If that's the case, then the "unbrickable Nook" (which I once believed to be true) is a fairy tale. The fact that several others around here have met with the same fate, I'm almost inclined to believe it. I'm going to go on a hunt for the original files that fixed my first nook. If only I could remember what the heck I did with them.
Scratch that...
I found the files, but now I have an entirely different issue.
My copy of Win32DiskImager back then was very size specific, and although I have a copy of the 16gb_clockwork file I used back then, I can't burn it because Win32DI says the card isn't the right size..
Ugh... I'll keep you all posted.
majorpay said:
Alright... Well here's where we are at this point:
Bought a Dynex 7 in 1 with specific port for MicroSD - burned v6 cwr bootable to 16GB SanDisc C4 SD using Laptop - Didn't work
Switched to main PC and burned 5.5 to 512mb Nokia C4 SD - didn't work.
Both were attempted with latest Win32DiskImager (.7) from SourceForge.
At this point, I'd lean towards a hardware failure, BUT... it's too coincidental that this occurred during a standard CWR install of a ROM. My understanding is that the Nook is supposed to ALWAYS check the SD slot prior to booting internally. Now whether there is a partition block that tells it to do this or not, I've never dug that far, but I'd have to say that this sure makes it look that way.
If that's the case, then the "unbrickable Nook" (which I once believed to be true) is a fairy tale. The fact that several others around here have met with the same fate, I'm almost inclined to believe it. I'm going to go on a hunt for the original files that fixed my first nook. If only I could remember what the heck I did with them.
Click to expand...
Click to collapse
It is possible that it is a hardware failure of the SD slot. Have you tried cleaning it? The booting to SD is built into the OMAP chip and is not effected by what you have in emmc. It automatically looks at the SD slot first to see if a bootable SD is there. But it looks for specific features of the SD found there to be sure it is bootable. If it is not bootable, it tries the emmc boot partition and if valid boot files are not there, it won't turn on.
Sent from my Nook HD+ running CM10.1 on emmc.
Alright, I ended up flashing the old image I used on my last Nook with the same version of win32diskimager I used back then, and still no signs of life.
Unlike the previous issues I had on my first Nook, this one shows no signs of life. No backlit deep black that you can see in the dark, nothing. So I plugged it into my tower PC and held the power for 10 seconds. The install for the OMAP 36xx processor drivers went through the process, but when done, you could not find it in the device manager. So I held the power again for 10 seconds, it showed up for a second, then went away. I repeated this process several times, and same thing each time.
Just to make sure I wasn't leaping to assumptions, I unplugged it and plugged it back into the PC, and no response. Not until I held the power down for 10 seconds again.
So what can we conclude from this? Well, either it is normal for the Nook to show up for a split second on Windows, or the Nook is powering on, then down almost instantaneously. I'm inclined to believe the latter as ordinarily holding the power down for a few seconds wouldn't *reboot* the device, but instead, it would power it down, or power it up (if it was off). Also, unplugging and replugging it in to the PC should have activated the device driver if it was staying on (assuming that isn't a momentary thing on initial startup).
What's the missing piece of the puzzle? I don't know if it's the same for all the other users that have commented, but I don't have the original cable for this device, so I cannot fast charge. A dead Nook will power on, even if drained, when the fast charge cable is used (I believe?). This is something else I will have to try when I get my hands on my dad's Nook. Is it possible that a trickle charge doesn't work below a certain point?
This was kind of my thoughts back when this first occurred - that perhaps the Nook simply lost juice during the install.
Grasping at straws? Perhaps, but straws are all I'm seeing at this point.
majorpay said:
Alright, I ended up flashing the old image I used on my last Nook with the same version of win32diskimager I used back then, and still no signs of life.
Unlike the previous issues I had on my first Nook, this one shows no signs of life. No backlit deep black that you can see in the dark, nothing. So I plugged it into my tower PC and held the power for 10 seconds. The install for the OMAP 36xx processor drivers went through the process, but when done, you could not find it in the device manager. So I held the power again for 10 seconds, it showed up for a second, then went away. I repeated this process several times, and same thing each time.
Just to make sure I wasn't leaping to assumptions, I unplugged it and plugged it back into the PC, and no response. Not until I held the power down for 10 seconds again.
So what can we conclude from this? Well, either it is normal for the Nook to show up for a split second on Windows, or the Nook is powering on, then down almost instantaneously. I'm inclined to believe the latter as ordinarily holding the power down for a few seconds wouldn't *reboot* the device, but instead, it would power it down, or power it up (if it was off). Also, unplugging and replugging it in to the PC should have activated the device driver if it was staying on (assuming that isn't a momentary thing on initial startup).
What's the missing piece of the puzzle? I don't know if it's the same for all the other users that have commented, but I don't have the original cable for this device, so I cannot fast charge. A dead Nook will power on, even if drained, when the fast charge cable is used (I believe?). This is something else I will have to try when I get my hands on my dad's Nook. Is it possible that a trickle charge doesn't work below a certain point?
This was kind of my thoughts back when this first occurred - that perhaps the Nook simply lost juice during the install.
Grasping at straws? Perhaps, but straws are all I'm seeing at this point.
Click to expand...
Click to collapse
I think what you are seeing is the device powering on with the screen off (like it normally does), looking for boot files in SD and emmc and when seeing none, immediately powering off. That is why the brief driver showing in windows. Ordinarily if it finds those boot files, it turns the screen on and continues the boot.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
I think what you are seeing is the device powering on with the screen off (like it normally does), looking for boot files in SD and emmc and when seeing none, immediately powering off. That is why the brief driver showing in windows. Ordinarily if it finds those boot files, it turns the screen on and continues the boot.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Bit the bullet and grabbed my dads. It's confirmed, the SD card I recently burned works - CWR booted right up. Now for the stock cable test.
Stock cable confirms that the Nook will not power up at all - cable is green indicating full charge. This Nook is toast - so just coincidence that it was during flashing PA? Hard to believe, but haven't I ruled every other possibility out?
EDIT - moved the cable and it turned orange. Coworker confirmed that his Nook charger he was using wouldn't even charge a phone I loaned him. May be on to something here. I'll wait until the cable turns green.
I'm done...
I'm beat. Cable turned green again, and no dice. This Nook is headed for the scrap pile (unless I get a wild hair and tear it apart to re-solder some joints).
majorpay said:
Stock cable confirms that the Nook will not power up at all - cable is green indicating full charge. This Nook is toast - so just coincidence that it was during flashing PA? Hard to believe, but haven't I ruled every other possibility out?
EDIT - moved the cable and it turned orange. Coworker confirmed that his Nook charger he was using wouldn't even charge a phone I loaned him. May be on to something here. I'll wait until the cable turns green.
Click to expand...
Click to collapse
I went back to your OP and re-read. It is very common for an installation to screw up and lock up, leaving the boot partition borked. But usually the user can boot to a bootable CWM and re-flash and it repairs it. Ordinarily I would say that the slot could have been messed up for a long time too, since a lot of users have CWM on emmc and would not know it until they needed a bootable card. But in your case the slot was working right up till after you put CWM on emmc. And your using internal memory to flash the zip from and leaving the SD in the slot is usually of no consequence. But it is remotely possible since you left the SD in and the software was running amouk, that it did something to the SD and the slot, like overcurrents or some such nonsense. I still think the not booting from SD is a slot hardware issue since your card boots on other devices and the booting code is in chip firmware.
Sent from my Nook HD+ running CM10.1 on emmc.