Related
Ok, setting up the old debian chroot is pretty straight forward. I had it up and running within a couple of days. What I really want to try to do is boot into debian natively.
I've been poking around and looking into a few things. I'm thinking it shouldn't be too hard to modify the init.rc to bring up debian instead of the normal android services and whatnot. From looking around it looks to me like init.rc lives in the boot image. So I'm guessing I would need to put together a boot.img with my custom init.rc and any supporting files.
Thoughts?
Should be totally doable. Debugging the boot process is a PITA though. Some things that might help with that:
TTL level serial (2.8v, 3.3v tolerant, I think) is available on the D+/D- lines of the microusb connector when VBUS (usb +5vdc) is not present. You can test a cable with a running N1 -- a couple taps of enter should get the debug> FIQ debugger prompt. For your own build, you'll probably want to enable serial console on ttyMSM0 and disable the FIQ debugger.
Alternatively you could try to dust off the fbconsole support. We never build with it, so it is *possible* that it has some problems, but it might Just Work <tm>.
Until you get a GUI environment up that has touch support, your inputs for on-device for debugging are limited -- volume buttons, power button, trackball button, trackball. The "soft keys" are implemented in userspace, not the kernel -- the kernel just provides a touchpanel driver.
Somebody could probably do an in-kernel softkeyboard, like the guy who did the android-for-vogue stuff way back when did, or perhaps you could convert graffiti-style strokes to keys in-kernel or something suitably fun like that.
I don't currently have the equipment I would need to setup a serial cable for that. Perhaps in the near future though. Thanks for that tip.
Is fbconsole part of the android source, or is a kernel option? I've been digging around for it, and haven't been able to track it down yet.
I poked at this a little over the weekend. Played around with init.rc, but I couldn't get my sdcard to mount without logging in via adb and mounting it by hand. I also decided it would probably be easier to install debian on a partition on the SD card instead of mounting an image off of the card.
I have a lot to learn here, espesially figuring out how to get debian to boot so I expect this will take me some time to figure everything out.
fbconsole is doing some very weird stuff. Scrolling sideways, a very distorted looking image scrolls by. All in all pretty much unusable. I have a mini - micro adapter, and a spare mini usb cable I don't mind donating to science, so having a go at building a serial cable tonight.
You might want to have a look at this
Woot! BOOTS!
Hit default run-level tonight
Next. Configure it so it does more then start cron.
It's already been done, as of 11 days ago...
http://forum.xda-developers.com/showthread.php?t=622474
Could have saved yourself some time with a simple 3 second search...
I hate to break it to you but chrooting into a debian image is not booting into debian. Cute trick, but I had that done the day after I got my nexus.
I'm talking about booting debian from the boot-loader.
Anywho...
I got hung up with getting getty running. Once I installed udev, getty started playing nice.
Debian GNU/Linux 5.0 TheBriaDroid ttyMSM0
TheBriaDroid login:
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
(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.
I recently received a used Nook color from a family member. They had bought a new tablet, and didn't need the Nook any longer. The problem with the NC, however, is it would no longer turn on or even charge. After opening the back (and thus voiding the warranty), I discovered the wires connected to the power button had come loose. I reattached them, put the NC back together, plugged in the charger and turned it on. Everything seemed fine, until I tried to erase it.
I've tried several different attempts, from simply tapping 'erase and deregister' to holding the power and home buttons, and pretty much every other way B&N's tech support told me. Each time, I get the same error message telling me to try again or contact customer support.
Likewise, any changes I make to the Nook (wallpaper, deleting some of the previous owner's books, etc) revert back to the way they were before each failed attempt as well as after simply turning the Nook off and back on.
My computer will not recognize it as a mass usb storage device, nor will it install at all on the computer. Plug in the usb, and it shows up as 'unrecognized'
Finally, anytime I have an SD card plugged in, the NC blackscreens after about 5-10 mins. Requiring a quick reboot.
Now, B&N tells me the NC is pretty much trashed and that I need to upgrade to a new one. I refuse to believe this until I've tried every option I can find. So, if someone can give me any help on trying to get this thing fixed, I'd be greatly appreciated, or if I'd just be better off buying a new tablet. (probably won't be getting a new nook)
MsEdyn said:
I recently received a used Nook color from a family member. They had bought a new tablet, and didn't need the Nook any longer. The problem with the NC, however, is it would no longer turn on or even charge. After opening the back (and thus voiding the warranty), I discovered the wires connected to the power button had come loose. I reattached them, put the NC back together, plugged in the charger and turned it on. Everything seemed fine, until I tried to erase it.
I've tried several different attempts, from simply tapping 'erase and deregister' to holding the power and home buttons, and pretty much every other way B&N's tech support told me. Each time, I get the same error message telling me to try again or contact customer support.
Likewise, any changes I make to the Nook (wallpaper, deleting some of the previous owner's books, etc) revert back to the way they were before each failed attempt as well as after simply turning the Nook off and back on.
My computer will not recognize it as a mass usb storage device, nor will it install at all on the computer. Plug in the usb, and it shows up as 'unrecognized'
Finally, anytime I have an SD card plugged in, the NC blackscreens after about 5-10 mins. Requiring a quick reboot.
Now, B&N tells me the NC is pretty much trashed and that I need to upgrade to a new one. I refuse to believe this until I've tried every option I can find. So, if someone can give me any help on trying to get this thing fixed, I'd be greatly appreciated, or if I'd just be better off buying a new tablet. (probably won't be getting a new nook)
Click to expand...
Click to collapse
All hope is not lost.
Make sure your nook is model # BNVR200. Look on the back cover toward the lower half by the speaker grill. If it is BNT250A/B you have a nook tablet and are in the wrong forum.
If your computer is Windows OS download Google Android USB driver here.
If the nook still has the stock ROM, check by going into settings, about. Latest BN stock ROM is v1.43. If you are on stock BN ROM, try the 8 failed reboots to restore the BN ROM. Instructions are provided by LeapinLar. Read item A12.
The nook could be powering down to conserve battery when a SD card is inserted. It should wake when the n home button is pressed.
The previous owner is the one who should be deregistering the nook, not you. If he/she does not want to do it and you do not care to use his/her media content, you can install CM7-gingerbread, CM10-jellybean, or CM-11-kit kat. CM can be installed on bootable SD or internally in place of the stock BN ROM. Instructions are provided by LeapinLar here.
Whichever CM version you install, make sure to install the correct version of GApps. BN for Android is almost similar in functionality as the stock BN UI. Only you cannot read BN interactive books with the Android BN app. Screen shots of Android Nook app attached.
Of course BN will tell you to buy another Nook product to increase its profits, but we all know better.
hwong96 said:
All hope is not lost.
Make sure your nook is model # BNVR200. Look on the back cover toward the lower half by the speaker grill. If it is BNT250A/B you have a nook tablet and are in the wrong forum.
If your computer is Windows OS download Google Android USB driver here.
If the nook still has the stock ROM, check by going into settings, about. Latest BN stock ROM is v1.43. If you are on stock BN ROM, try the 8 failed reboots to restore the BN ROM. Instructions are provided by LeapinLar. Read item A12.
The nook could be powering down to conserve battery when a SD card is inserted. It should wake when the n home button is pressed.
The previous owner is the one who should be deregistering the nook, not you. If he/she does not want to do it and you do not care to use his/her media content, you can install CM7-gingerbread, CM10-jellybean, or CM-11-kit kat. CM can be installed on bootable SD or internally in place of the stock BN ROM. Instructions are provided by LeapinLar here.
Whichever CM version you install, make sure to install the correct version of GApps. BN for Android is almost similar in functionality as the stock BN UI. Only you cannot read BN interactive books with the Android BN app. Screen shots of Android Nook app attached.
Of course BN will tell you to buy another Nook product to increase its profits, but we all know better.
Click to expand...
Click to collapse
The model number is BNTV250 Which a quick google search tells me it's a tablet color. Either way, I have tried doing most of this stuff already before coming here. Failed reboots, booting from an SD card, pretty much everything I could find through a google search.
As for the issue with the sd card, it's not a simple issue of it powering down to conserve battery. No amount of pressing any of the buttons will work. The only way I'm able to get it to turn back on is by pressing the power key for about 20 secs, releasing, and pressing again for about 3 secs.
Finally, a bit of new information. I was finally able to manage to get the nook to install on my computer and give me access to the files. However, I can't delete anything. I tried going that route to delete the old books, however once I eject and disconnect the nook, all the books that were deleted remain, and the books I attempted to add weren't there.
MsEdyn said:
The model number is BNTV250 Which a quick google search tells me it's a tablet color. Either way, I have tried doing most of this stuff already before coming here. Failed reboots, booting from an SD card, pretty much everything I could find through a google search.
As for the issue with the sd card, it's not a simple issue of it powering down to conserve battery. No amount of pressing any of the buttons will work. The only way I'm able to get it to turn back on is by pressing the power key for about 20 secs, releasing, and pressing again for about 3 secs.
Finally, a bit of new information. I was finally able to manage to get the nook to install on my computer and give me access to the files. However, I can't delete anything. I tried going that route to delete the old books, however once I eject and disconnect the nook, all the books that were deleted remain, and the books I attempted to add weren't there.
Click to expand...
Click to collapse
You had better do more than a quick search. A BNTV250 is a Nook Tablet, not a Nook Color and nothing in this Nook Color forum will work on it. There is no such thing as a tablet color. Go to the Nook Tablet forum for your answers.
Sent from my BN NookHD+ using XDA Premium HD app
Hey guys,
I cracked my s5 screen and need to backup everything and restore it onto another s5.
Phone info: NO ROOT, Pattern-locked screen.
I tried a lot (I mean A LOT) of different methods, and if I would be able to successfully backup/restore with a few easy steps, I still would like to have the following questions/methods answered.
They are as follows:
1. USB debugging mode is enabled, so i can use adb commands, which I have already. I have done the pull /sdcard/ command. I was able to get pictures, videos, downloads, etc. But I dont think it backed up any apk's. Any idea as to which pull command can fully backup the phone including apps, and if possible also text messages??
2. I have purchased a usb OTG (On-the-go) which allows me to connect my mouse to my phone. I cannot see the screen so i tried to randomly swipe my lock pattern, but i wasn't able to. So, what I thought of was to connect my phone to my mac, and use android screencast (which shows my phones screen on my mac monitor) while also using my mouse to control my phone. However, the USB OTG only has 1 usb slot, so I can either connect my mouse, or take out the usb otg adapter and connect the micro usb directly to my phone that connects to my laptop.
So the question is. Can I connect two micro-usb's into my phone simultaneously? One would be the usb-otg adapter( to connect my mouse into) and the other would be the micro-usb that would connect to my mac(in order to see the screen.) This way I would be able to control my phone with a mouse, and see my screen on my laptop monitor. I use mac btw.
3. If I can't connect two micro-usb's into my s5, can I enable bluetooth to connect to a wireless mouse via abd commands or any other method?
3. Can I root my cracked-screen phone? And without losing any data?
4. Is there a way to disable the pattern-lock on my phone using adb commands? I have read solutions to this for older galaxy models, but they didn't work for my phone.
Yes, these are tough questions, and I hope some of you have the proper knowledge and patience to answer them.
Please be specific, and note the Question # you are providing an answer to.
Thanks
The Puma
Your post doesn't quite make sense, which I think is because you're leaving something critical out or making an assumption that you aren't telling us about. e.g. you cracked your screen.. okay. I'm sure that is frustrating but how does it cause you any significant difficulty in using your phone?
There is something that you're not telling us. We can't see your phone or tell what you are thinking.. did you forget to mention that you broke your digitizer? Or perhaps broke the LCD, so that your screen doesn't power up? Or something else?
Tell us what the actual problem is, because a cracked screen per se would not impair normal phone use. If we don't know what is going on, it's hard to offer good advice on how to proceed.
If you do a search, you can find posts describing how to bypass a pattern lock if USB debugging is enabled. If you can't view your screen directly for some reason, there are various ways to root or even easier, assuming an unlocked bootloader, simply install a custom recovery.. which is only a few clicks. Then boot to recovery mode, allowing you to run a root ADB session and use the dd command to backup your partitions.
.
..
fffft said:
Your post doesn't quite make sense, which I think is because you're leaving something critical out or making an assumption that you aren't telling us about. e.g. you cracked your screen.. okay. I'm sure that is frustrating but how does it cause you any significant difficulty in using your phone?
There is something that you're not telling us. We can't see your phone or tell what you are thinking.. did you forget to mention that you broke your digitizer? Or perhaps broke the LCD, so that your screen doesn't power up? Or something else?
Tell us what the actual problem is, because a cracked screen per se would not impair normal phone use. If we don't know what is going on, it's hard to offer good advice on how to proceed.
If you do a search, you can find posts describing how to bypass a pattern lock if USB debugging is enabled. If you can't view your screen directly for some reason, there are various ways to root or even easier, assuming an unlocked bootloader, simply install a custom recovery.. which is only a few clicks. Then boot to recovery mode, allowing you to run a root ADB session and use the dd command to backup your partitions.
.
Click to expand...
Click to collapse
Yes, the digitizer is cracked as well, and my screen is black. That is the reason I am using Screencast to view my screen on my laptop monitor.
puma224 said:
Yes, the digitizer is cracked as well, and my screen is black. That is the reason I am using Screencast to view my screen on my laptop monitor.
Click to expand...
Click to collapse
I am guessing you can see the screen on your PC. Well, you can open up Google Play on your PC browser, search for the app "Helium backup" and let it install on your phone. That app can backup all your app data and other stuff as well I think, but I know for sure that it can backup the app data, which I assume is what you desire. The data can even be backed up to a Cloud. From there it should be easy to restore on your new S5. Also, the messages etc. are backed up on your Samsung account, that shouldn't be a problem as well.