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?)
Related
I read on FixYa that getting stuck in a loop on the second (android) boot screen can be caused, possibly/maybe/guessing/testing by running something from the SD card. I had my (native) wallpaper there, had just done it, and I got stuck in the android screen loop. Factory ROM 1.1 Tmo US.
I'm sure I installed some apps today, but nothing crazy functional, and tweaked some things. Day 2 for me. Just scoping out wallpapers, and bam.
I don't particularly want to do this again, so I'm wondering if anyone can shed any light on the subject. I guess it's happened to at least a few people.
My FixYa post had something to say about leaving WM, possibly, in pursuit of something more reliable....
use ddms or do a logcat to see if there is a problem.
Sorry, day number 2
You might as well be speaking Swahili. I'll google around and find something, but in the future if you're offering help to a real pleeb, and one might find this post later, a link or something, or a translation of what you're talking about would be very helpful.
ddms
Uh, I'm still in the dark, too. ddms doesn't seem to find the device at all. I was operating the factory Tmo image, so I wasn't rooted or anything (funny thing, it wasn't the first thing I wanted to do with the phone). I haven't the foggiest idea how to get the unit properly connected to the PC, even. 2 days.
I do appreciate the tip. It will get me somewhere.
Not that it matters, but I already hard reset. I really didn't have anything on there I was going to keep (Locale settings, and I was sorry to lose the SMS's, but it wasn't that many). I was planning on flashing anyway.
Edit:
logcat Errors
05-23 02:50:31.243: ERROR/EventHub(48): could not get driver version for /dev/input/mouse1, Not a typewriter
05-23 02:50:31.343: ERROR/EventHub(48): could not get driver version for /dev/input/mouse0, Not a typewriter
05-23 02:50:31.373: ERROR/EventHub(48): could not get driver version for /dev/input/mice, Not a typewriter
05-23 02:56:22.423: ERROR/Uapi(148): Microphone Cannot Stop in Unknown State 3.
I'm putting my sim card back in my wizard for the night.... I"ll probably get the hard SPL and flash tomorrow.
Is there a way to identify hardware problems with this pile of tools?
ddms offers logcat viewing abilities. Your link was correct, you just have to run ddms from the tools folder of the SDK. If it doesn't find your device try installing the drivers (and make sure the phone is connected) if it still doesn't find it than there is nothing to do really.
To see a logcat without ddms try this in a command prompt
adb shell logcat -d V > adb.txt
Click to expand...
Click to collapse
then open it in notepad
ddms
In my relatively limited experience, particularly with xda-dev, there never truly is "nothing to do." By doing nothing, what am I doing? Giving up and throwing the phone in the garbage? Pursuing & reinstalling the usb driver (which is what I did)? Should I be hearing something kinda like (less comfortable to say?),"I've never run into that, so I don't know what to do in that instance." IMHO, it's better to define that you don't know something; it highlights what you *do* know and makes it easier to see. I'm having a hard time figuring out what you're trying to tell me, unless what you're telling me is very open-ended. If it is, just say so.
So, I do appreciate being able to see what's going on with ddms, but in this instance, what am I looking for?
errors, warnings. Basically anything not in black text LOL
can you not try a factory wipe/reset
Try booting the phone up while pressing the home key, then press Alt+L to turn on the text display then alt +W to wipe the phone that should recover it.
You may need to change the SPL on the phone and do some other minor tweaks Read the rooting thread on here as it explains what i am trying to explain but makes it alot clearer.
or if you wanted to go down the root road then remove your sd card and got the appropriate sticked thread and download a rom i chose JeasusFreake's 1.5 ADP1 build. put the update.zip on the SD card with no other files and boot the phone up with home pressed down
Alt+ L
Alt+W
Alt+ S
and if you are going to use JeasusFreake's rom then download the HTC cupcake radio from http://www.htc.com/www/support/android/adp.html
Hi all,
Firstly apologies for the long post, and thanks for all the info that is up here... however I have managed to get quite lost. I'll try to take you though the whole story as much as I understand it, but I woke up this morning and decided (after 8 months) to finally root my android.
That was 8am, it is now midnight, and I've had sandwiches while working at it, all day. It has been in various stages of bricked, and I think I might have just sent it back that way - should not be playing with it when tired.
Things I have
1 x UK Vodafone HTC Magic, doing return plus power = 32B, HBOOT-1.33.0009 (another story here).
1x 16GB SD-HC card
1x 1gb Card
1x cheap nokia I can use as a reader for the 1gig card, but it can't handle SD-HC
Anyway I started off with the 1 click root idea, which obviously doesn't work these days, so followed the next link, then the next, finding I need to do the 'goldcard' method.
theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/comment-page-3/
Anyway I'm not sure where all the time has gone (16 hours now), but I have learnt what an SPL was, flashed mine to an ‘imperfect’ one, managed to flash it to deteethed google, then cyanogen on top, but it would never boot, and just hangs saying HTC Magic, then managed to flash it using 'myhero' which gave me a Hero like phone.
However I now seem to have messed it up again as I'm determined to do the cyanogen mod - I really want to be able to tether, and lots of other bits and pieces.
The state at the moment therefore is I have it all working with fastboot, and can easily get the Amon_RA recovery image going, but the cm_recovery one makes it hang and do nothing. If I try and replace the recovery section using fastboot it tells me it has failed (I forget the exact message).
I can therefore upgrade things using the Amon_RA backup, but as I said things don't seem to entirely work, and at the moment my phone is hanging (I think as I'm tired I've overwritten my backup). I'm also not sure if this goldcard method is working – I asked a question in the thread and it seems that it might not be.
I guess I'm just looking for a few pointers, after 16 hours sat here I'm generally pretty frustrated and totally lost - there is a lot of information, but there are so many permutations of hardware, and a lot of the information is now out of date. Trying to take everything in as well as deal with a specific problem may actually be beyond me Which is something I hate- being the newbie needing help with a potentially simple problem (though I have had a good go at it).
I'm really not sure what stage the phone is at, have I rooted it? After all I can use the myhero rom, but on the other hand I can't do what I want to do, so therefore is there a problem? Exactly which step makes it ‘rooted?’ as every guide is obviously a chain of events to make it in to something else. I'm honestly not sure, but it isn't a fun feeling – I’m stressed and at the momentI have no phone just a brick that I can fastboot to recovery, and a bunch of backups as soon as I get it working again.
I really had no idea it would be this difficult, and am a big angry at Google/HTC for making it so - it is easier to get Hackintosh working than this! I’ve also managed to do hundreds of other similar things without any problem – Xbox Media Center (including soldering), and a few more spring to mind, all to use the hardware I already own! My hardware!
Anyway advice and pointers are appreciated, as although I've learnt a lot today, I'm still blundering about, and it is a matter of time until I cause serious damage in my attempts to make it better, al alternatively just throw in the towel, but then I don’t think I can go back as I have a horrible feeling that the restore I did didn’t work.
Again anything you can offer is appreciated, and if you need more detail, I’ll do what I can!
Anthony
Also just to add I've tried searching, which is partially how I've got myself in to this mess - solve one problem but make another!
Also I do have my APN settings, so when I get it installed, I can get my google account workign with it - I think i've had to do this about 6 times now! So if there is a way to get it in to 'myhero' which I think I can do again, and download an apk, then I should be able to do that.
Ant
There is a lot of information and everyone is recommended to do their research before rooting the phone.
That being said, it sounds like your phone is rooted if you can boot into recovery and load up a sense ROM. It'd been much easier to follow cyanogen's wiki instructions for non T-mobile 32B Magics. I also have a vodafone Magic and I rooted my phone successfully using the method.
Not having used the goldcard method, I don't exactly know where it went wrong. Have you done full wipes before applying a zip file? Stuff like that which might be easily overlooked?
Yeha I've been wiping it all before flashing, so that isn't the problem.
I also did as much reading as I could before starting (and watching the youtube guides before doing anything), but I guess a lot of the problems were unexpected (aren't they always?), for example I only found out half way through that I would need to flash the SPL, and it took me 40 minutes to figure out what SPL was, and what it did, then another 40 to work out how I was going to do it, then 40 to do so.
I have been following guides though - for the cyanogen one I get all the way down to flashing it with the detoothed google build, then cyanogen (obviously wiping before doing these). All the steps appear successful but then it doesn't boot.
The phone is also a rather strange one, a vodafone branded one that says 32B, but I'm sure it has more RAM.
Currently trying 'method 2' from here
android-dls.com/wiki/index.php?title=Magic_Rooting
to see if that works, but I'm not optimistic.
Yup 15 minutes laters same problem - it hangs on HTC magic screen, which is exactly what it does when I go for the Cyanogen one.
I'll goign to try and google for other roms, see if any of them work sucessfully (and might provide a bridghe to what I want to have.
Again however anybody knows good guides, sites or anythign else let me know.
As I said a big problem before is I'm reliant heavily on google, and a lot of the informaion out there is useless, as it is out of date in a big way. Also I don't know anyoen else who has doen this, so recommendations ofmethods/roms are dependent on my reading, not wword of mouth (which is generally better).
Ok I've tried the method 2, defiantely no sucess, went back to the myhero (which performs awfully, so much lag!), and have now tried flaskrec.apk on there.
It does not backup, but then bypassing that step, it gives me the error 'Flash failed'.
Really stuck now, and no idea what to try, any suggestions at all would be helpful. I'm almost at the stage of wishing I'd got an iphone :-(
Hello all,
I have recently upgraded from my g1 to an HD2. HD2 is a great phone but still miss android . Anyways, today I wanted to get my g1 to work without a sim or data plan and was about to start working on it when my g1 screen dimmed to just the blacklight with a black screen. I turned it off and tried turning it back on but it just comes up with the backlight on a black screen. It does not even get to the G1 screen. I cannot get to recovery mode or any other mode for that matter. I have searched around but not found any real solution to this problem (if there is one). I am thinking my phone is bricked but have heard possibilities using ADB. I have never used ADB before and if anyone knows if this is a possible fix to my problem that would be great. It would be nice to know if it actually could fix my problem before looking into it and learning it all while finding out it has no chance of fixing my problem. I have tried using my sim card and a different sd card so those are not causing the problems.
So the background of what I am running on my g1. Right before I got my HD2 I was using Cyanogen version 4.2.14.1 with and ext 3. I had no problems with it until now. I got my HD2 a week ago and my g1 has been on about twice in that time without a sim card just for comparing purposes to the HD2. Then just today (about 2-3 days since I last turned it on) the screen just went black and I had my problems. I cannot return my phone because it has been over a year and I dont have insurance on the phone so these are not possibilities for me unfortunately. I also don't really want to get parts from other g1's and take apart and put my g1 back together. I am just looking for something with ADB or any other possible solution to the problem (if one exists).
Any help would be greatly appreciated!
I had this happen to me before. Apparently, it was a hardware GPU problem that would cause a boot loop because it couldn't draw anything on the screen. This happened on SuperD, AOSP, Cyanogen, and stock Donut.
If your problem is the same, you should be able to get into recovery, regardless of your ability to see what you're doing. Easy way of telling is to hit Camera+End on boot. If it doesn't vibrate, you're able to flash still. You may be able to get the screen back temporarily by either pulling the battery or letting the battery die and recharging.
Anyways, I ended up flashing the DREAIMG.nbh, and trying to upgrade back to 1.6 to remove traces of hacking. (Be careful if you have DangerSPL, you want to restore the default before flashing DREAIMG.nbh) I eventually got the screen working on 1.6, but it died again, so I sent it in to T-Mobile and got a replacement. I'm now using AOSP with no problems.
One small note, however, I did start having my problems using Cyanogen's mod. May want to bring it up with him?
Sorry if this sounds scatterbrained, it's a bit late and I should be asleep right now.
e:Just realized you said the warranty was void. You may be able to get something out of what I did, though? Good luck, in any case.
Thanks very much for the help even though it was really late. I did understand pretty much everything you said and I tried the camera plus power button and it didn't vibrate so it should mean I probably can flash things still. I have drained the battery and am charging it back up to see if that helped.
I have a friend who knows ADB so I am going to have him look at it to see if we can't get it working through there. Also the G1 screen has been popping up but then fading right when its about to change to the boot animation. So we will see how things go and I'll try a couple different things and report back if anything seems to work or open up more possibilities.
Thanks again for your information.
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
coolookoo said:
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
sorry i have the same problem, but my g1 is not rooted nor has it been flashed before, my friend messed it up somehow? wen i turn it on all there is is a blank highlighted black screen. What do yall suggest i should do
r3s-rt said:
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
Click to expand...
Click to collapse
First of all we are not trying to unroot the phone just flash another rom
Secondly we already tried your "fantastic" method of using google before coming to the forums
Ok I think I just bricked my G1
I was following the steps on theunlockr.com and was following the steps to the T like I always do.
The problem incurred after flashing the spl. I flashed the correct radio then ir rebooted and went back into recovery mode. Then I flashed the spl all seemed well home+back and never rebooted. It stayed on a black screen for over 30 mins. So I took out the battery and waited a few mins and put battery back in and same thing. Just a black screen nothing I can do. I have tried holding home+power and camera+power and back+power nothing. I am stuck have looked it up and this is the best forum I have found to post in.
Any input would be great.
thanks
nate
hello folks,
I have seen some threads talking about some WM device freezing in bootup, and stick in the 1st screen when it says "stick together", I had the same problem, and I did contacted HTC for support, it seems they dont have a solution for that problem but to send the phone to them, whicj gonna take around 10 or 15 days to get back -if the warranty still in effect- and they probably gonna charge you something more than the shipping back fees, cause you flashed your device.
I was Planing to send my phone this monday, but i though lets try something and see what gonna happen, so what i did is :
1 - take you SIM card and your SD card, (don't connect your phone to your PC)
2 - While holding the VolUp press the Power button, you will see a screen with your device information
3 - Now connect your device to you PC, and use one of the Wm costume ROM, don't worry about the guide line, and about the winSync instruction, cause it do work without windows Sync
4 - follow the instruction on the costume ROM application, and just ignore the WmSync one.
your phone will reboot, and you probably gonna see your device radio and room information.
I just did the sameting to fix my device, I don't know if just got lucky
But I do have a problem now, I cant install android on my device, and when i try to lunch CLRCAD, it does not start, even when i lunch haret, the device reboot, if someone know a fix to that problem, so may help me.
dude, out of your three posts, two have been new threads that are strictly related to user-problems in a developmental sub-forum, which just isn't cool.
its like someone walking into your work meeting and asking about the lunch schedule (not the best analogy, but you get the point)
if you're really stuck in something, a hard reset always restores things nicely
bravo261 said:
dude, out of your three posts, two have been new threads that are strictly related to user-problems in a developmental sub-forum, which just isn't cool.
its like someone walking into your work meeting and asking about the lunch schedule (not the best analogy, but you get the point)
if you're really stuck in something, a hard reset always restores things nicely
Click to expand...
Click to collapse
i'm just trying to stay in the dark, waiting for the moment to say something useful, by the way hard reset does not work all the time
The only time a hard reset does not work is if there is something wrong with your phone or somehow you corrupted your ROM. In that case going into Bootloader and upping a new ROM does the trick. A Task29 will really fix things well.
As far as "launching" CLRCAD...it does nothing ANYWAY! You just tap it and that is it...it merely sets up the phone for Android to have sound, nothing more...no prompts, no hour glass nothing. (A SEARCH or reading the first post would have told you this.)
If you get resets in Haret then Android did not load correctly. Merely delete your data.img and start over. If that does not work then you likely corrupted your Android build....format your SD card and reload Android from scratch.
I personally have backed up my working daily build on a weekly basis so in case my Android gets hosed, I merely have to copy my entire backup (which is just a copy of my SD card on my computer) back to the SD card after a format (but have yet to really have a need for this except months ago).
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