Database Users

Now I'm REALLY confused

Ok, the more reading I do the more confused I get.
I have a nook 1.3 that I bought for my son. The reason I chose the nook was because I could put the market on it and give him the games he's always playing on my phone. I'd LIKE to keep the stock reader as well because he's only 7 and I like the read to me feature on it as well. My first attempt to root was an abject failure, and now with 1.4 coming out I'm totally lost.
From my poking around here is some of what I gather:
Some of that I gather is:
The market doesn't work when you use the current root files on 1.4. Or does it? There doesn't seem to be a consensus
Some nooks with 1.3 get the boot loop when using the two "current" nooter files (that's what I experienced), but you can use the older file and just have an older market
At this point, I'd really like to know what my options are. Right now I'm sitting at 1.3, and may (or may not...I think I might have goofed the first root process up) have one of those nooks that hangs. My #1 priority is the market, and #2 (or maybe 1A) is keeping the reader. What are my options for this? Or do I just create a bootable SD card and give him a plain Android tablet until this all washes out?

Girevik said:
Ok, the more reading I do the more confused I get.
I have a nook 1.3 that I bought for my son. The reason I chose the nook was because I could put the market on it and give him the games he's always playing on my phone. I'd LIKE to keep the stock reader as well because he's only 7 and I like the read to me feature on it as well. My first attempt to root was an abject failure, and now with 1.4 coming out I'm totally lost.
From my poking around here is some of what I gather:
Some of that I gather is:
The market doesn't work when you use the current root files on 1.4. Or does it? There doesn't seem to be a consensus
Some nooks with 1.3 get the boot loop when using the two "current" nooter files (that's what I experienced), but you can use the older file and just have an older market
At this point, I'd really like to know what my options are. Right now I'm sitting at 1.3, and may (or may not...I think I might have goofed the first root process up) have one of those nooks that hangs. My #1 priority is the market, and #2 (or maybe 1A) is keeping the reader. What are my options for this? Or do I just create a bootable SD card and give him a plain Android tablet until this all washes out?
Click to expand...
Click to collapse
May I suggest you start from the beginning. Samualhalff here has a great utility to take you to pristine stock. Apply the 1.3 update and use your bootable uSD, install Gapps (latest) and go a step at a time.
I've had success with the above ending up in CM7 7.0.0.3. You'll always have the "reader" using Aldiko, B&N or whatever you choice is.

skeeterpro said:
May I suggest you start from the beginning. Samualhalff here has a great utility to take you to pristine stock. Apply the 1.3 update and use your bootable uSD, install Gapps (latest) and go a step at a time.
I've had success with the above ending up in CM7 7.0.0.3. You'll always have the "reader" using Aldiko, B&N or whatever you choice is.
Click to expand...
Click to collapse
Ok, I guess it's time to display my ignorance.
First of all I think I AM at pristine stock, but what do I know? The nook came with 1.3 on it (just got it last week), and after my isues trying to root it the only way I was able to get it back working after beein stuck in the boot loop was with the "8 failed boots" method. My understanding that was akin to a factory reset so it was back to just like it was out of the box.
So that brings me to:
- I don't need to apply any updates to get it to 1.3, right?
- When you talk about my bootable uSD card, exactly what do you mean? The only thing I've created is the CockWorksRecoveryMod SD card to apply the ManualNooter files.
- I'm not sure what Gapps is (and I feel like I should)
- If I flash a rom, I understand I can download the B&N (or whatever) Android software, but I though the color stock reader (and only the out of the box reader) had the feature where it could actually read some books to you (a feature I think might be nice for a 7 year old)

Girevik said:
Ok, I guess it's time to display my ignorance.
First of all I think I AM at pristine stock, but what do I know? The nook came with 1.3 on it (just got it last week), and after my isues trying to root it the only way I was able to get it back working after beein stuck in the boot loop was with the "8 failed boots" method. My understanding that was akin to a factory reset so it was back to just like it was out of the box.
So that brings me to:
- I don't need to apply any updates to get it to 1.3, right?
- When you talk about my bootable uSD card, exactly what do you mean? The only thing I've created is the CockWorksRecoveryMod SD card to apply the ManualNooter files.
- I'm not sure what Gapps is (and I feel like I should)
- If I flash a rom, I understand I can download the B&N (or whatever) Android software, but I though the color stock reader (and only the out of the box reader) had the feature where it could actually read some books to you (a feature I think might be nice for a 7 year old)
Click to expand...
Click to collapse
OK. Guess maybe I mis-read your post! My fault!
Personally I have never gotten the "hang" of 8 Failed Boots. I have just wiped /data and /system then loaded stock.
If you are at stock 1.3 (and unrooted and no CWM) you can verify in Settings if you wish but it sounds as if you are.
Format your uSD using this. Then follow these directions. This will give you a good format on your card and help you create a working bootable uSD.
I post this as I have seen many uSD card not formatted correctly (never use windows format or your device to format..often corrupts)
You can also load whatever ROM you wish to instalkl on the card but flash it only after you have rooted and installed CWM.
Gapps is Google Apps. Installs Market.
HTH!

skeeterpro said:
OK. Guess maybe I mis-read your post! My fault!
Personally I have never gotten the "hang" of 8 Failed Boots. I have just wiped /data and /system then loaded stock.
If you are at stock 1.3 (and unrooted and no CWM) you can verify in Settings if you wish but it sounds as if you are.
Format your uSD using this. Then follow these directions. This will give you a good format on your card and help you create a working bootable uSD.
I post this as I have seen many uSD card not formatted correctly (never use windows format or your device to format..often corrupts)
You can also load whatever ROM you wish to instalkl on the card but flash it only after you have rooted and installed CWM.
Gapps is Google Apps. Installs Market.
HTH!
Click to expand...
Click to collapse
I tried to load stock back, but it seems that ANYTHING I tried to do (including the root) resulted in a boot loop on the "nook color" screen. It seemed that nothing I tried to do did anything but make it loop until I found the faild boot trick. I was even getting an error just trying to wipe the data, which had me worried.
When you talk about loading a ROM on the card and "flashing" it, is that to replace the nook OS with the ROM? I don't think I want to do that now since I'd like to keep the stock reader.
Ideally I'd like to just root and get the Market, but after my first failed attempt, learning that 1.4 is on the horizon, and that some 1.3 nooks seem to get the nook boot loop when using ManualNooter, I'm a little gun shy. At this point I'm thinking I may want to wait until someone has a stable root process for 1.4.
Does the nook have to be rooted if I want to boot an OS from the SD card? I'm thnking that may be my best compromise at this point.

Girevik said:
I tried to load stock back, but it seems that ANYTHING I tried to do (including the root) resulted in a boot loop on the "nook color" screen. It seemed that nothing I tried to do did anything but make it loop until I found the faild boot trick. I was even getting an error just trying to wipe the data, which had me worried.
When you talk about loading a ROM on the card and "flashing" it, is that to replace the nook OS with the ROM? I don't think I want to do that now since I'd like to keep the stock reader.
Ideally I'd like to just root and get the Market, but after my first failed attempt, learning that 1.4 is on the horizon, and that some 1.3 nooks seem to get the nook boot loop when using ManualNooter, I'm a little gun shy. At this point I'm thinking I may want to wait until someone has a stable root process for 1.4.
Does the nook have to be rooted if I want to boot an OS from the SD card? I'm thnking that may be my best compromise at this point.
Click to expand...
Click to collapse
Understand. Actually 1.4 is available right now for download from the Support section on BN site. If you wish, go ahead and get it, load it to the root of your NC, let it go to sleep and it will update automatically for you. (Directions on the BN site) If you wish to load CM7 for instance, you may wish to reload 1.3 for now as I don't see a 1.4 version yet.
Once that is done you will be at stock 1.4 (if you go that way). And yes, you can load your choice of ROM from the uSD. One of the really neat things about the NC is that it boots first to the uSD then to the internal. There are several choices in the Development section to choose from. Try out several and pick the one you like (I prefer CM myself) Keep in mind that booting from the uSD will not be as fast as if it was loaded to your internal but doing this will also keep your stock safe. And no, you need not be rooted to boot from uSD.
For example..... verygreen.
Let me know how it goes!

Ok, cool. So it sounds like my plan for now is to get 1.4 then boot off of an SD card. When and if we can root it successfully, I'll make that jump.
I asked this in another thread, but I'll do so hear as well. What happens to apps I download while booted from the card? Are they installed on the card or the nook internal memory? And if it's the nook memory, what happens when I boot to the nook?

Girevik said:
Ok, cool. So it sounds like my plan for now is to get 1.4 then boot off of an SD card. When and if we can root it successfully, I'll make that jump.
I asked this in another thread, but I'll do so hear as well. What happens to apps I download while booted from the card? Are they installed on the card or the nook internal memory? And if it's the nook memory, what happens when I boot to the nook?
Click to expand...
Click to collapse
Golly. It's been so doggeone long since I ran anything off the uSD....if I remember right.....Ya know....I believe everything runs from the uSD. I would sideload the apks. Lemme think about that one. That was like Months before last Christmas lol

For what you want, I would just do a MN Root of the stock Nook software. Then you wouldn't have to deal with switching back and forth between CM and stock.
---------------------------------
Sent from my LG Optimus V using Tapatalk

koopakid08 said:
For what you want, I would just do a MN Root of the stock Nook software. Then you wouldn't have to deal with switching back and forth between CM and stock.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
That's my long term goal. but is the root on 1.4 working yet? I tried to do the MN root (but may have missed a step) on 1.3 and got into a boot cycle. I was thinking I'd just let it upgrade then once all the 1.4 stuff was figured out do a root then

Girevik said:
That's my long term goal. but is the root on 1.4 working yet? I tried to do the MN root (but may have missed a step) on 1.3 and got into a boot cycle. I was thinking I'd just let it upgrade then once all the 1.4 stuff was figured out do a root then
Click to expand...
Click to collapse
From what I've read the 1.4 doesn't have reliable root yet. So you have two choices really. Leave as is and wait (I'm betting root will come to 1.4 eventually) or wipe (system/data) back to 1.3, load and MN/AN.

Girevik said:
That's my long term goal. but is the root on 1.4 working yet? I tried to do the MN root (but may have missed a step) on 1.3 and got into a boot cycle. I was thinking I'd just let it upgrade then once all the 1.4 stuff was figured out do a root then
Click to expand...
Click to collapse
I'm not sure about the progress of a 1.4 root but I do know that 1.2 is very easy to root as you only have to flash one file.
So unless you really want the small added features of 1.4 I would just revert to 1.2 and stay there until a 1.4 root is finalized.
---------------------------------
Sent from my LG Optimus V using Tapatalk

koopakid08 said:
I'm not sure about the progress of a 1.4 root but I do know that 1.2 is very easy to root as you only have to flash one file.
So unless you really want the small added features of 1.4 I would just revert to 1.2 and stay there until a 1.4 root is finalized.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
Can I revert to 1.2 if my nook came with 1.3 on it OOTB?

koopakid08 said:
I'm not sure about the progress of a 1.4 root but I do know that 1.2 is very easy to root as you only have to flash one file.
So unless you really want the small added features of 1.4 I would just revert to 1.2 and stay there until a 1.4 root is finalized.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
In doing this nooter on a 1.2 are you still able to have flash and the netflix app work? or do you have to have 1.3 or 1.4? I see 1.4 is bnn making netflix available, but im guessing if you root on a 1.3 you can gain access to the app? is it the same for 1.2? I have the netflix.apk file to sideload in either case. Just curious before I go wiping my nook and starting fresh (was gonna go with cm7 on a disk dual boot with 1.4) or go to 1.3 and manual nooter

miss_october said:
In doing this nooter on a 1.2 are you still able to have flash and the netflix app work? or do you have to have 1.3 or 1.4? I see 1.4 is bnn making netflix available, but im guessing if you root on a 1.3 you can gain access to the app? is it the same for 1.2? I have the netflix.apk file to sideload in either case. Just curious before I go wiping my nook and starting fresh (was gonna go with cm7 on a disk dual boot with 1.4) or go to 1.3 and manual nooter
Click to expand...
Click to collapse
Sure can. I ran Netflix on 1.3 (and I'm thinking 1.2 also) but I believe due to a small glitch one needed to modify the build.prop file. Very easy to do really And it works! The posts should still be in the forum. Search Netflix. That should get you what you need.

Girevik said:
That's my long term goal. but is the root on 1.4 working yet? I tried to do the MN root (but may have missed a step) on 1.3 and got into a boot cycle. I was thinking I'd just let it upgrade then once all the 1.4 stuff was figured out do a root then
Click to expand...
Click to collapse
Girevik, we exchanged messages on this topic in another thread. I wanted to let you know I've had some success with rooting 1.4.1 to the point that it might be suitable for what you want. See message 92 in this thread.
In short: You can sideload apps and run them in the B&N Walled Garden. You can't download or refresh apps, but you can work with sideloaded books and apps. It's not 100% stable yet, but I think with careful selection of sideloaded apps, it may be.

Girevik said:
Can I revert to 1.2 if my nook came with 1.3 on it OOTB?
Click to expand...
Click to collapse
Yes, you just need to flash the 1.2 zip
---------------------------------
Sent from my LG Optimus V using Tapatalk

miss_october said:
In doing this nooter on a 1.2 are you still able to have flash and the netflix app work? or do you have to have 1.3 or 1.4? I see 1.4 is bnn making netflix available, but im guessing if you root on a 1.3 you can gain access to the app? is it the same for 1.2? I have the netflix.apk file to sideload in either case. Just curious before I go wiping my nook and starting fresh (was gonna go with cm7 on a disk dual boot with 1.4) or go to 1.3 and manual nooter
Click to expand...
Click to collapse
Yes both will work on 1.2 and 1.3
---------------------------------
Sent from my LG Optimus V using Tapatalk

bobstro said:
Girevik, we exchanged messages on this topic in another thread. I wanted to let you know I've had some success with rooting 1.4.1 to the point that it might be suitable for what you want. See message 92 in this thread.
In short: You can sideload apps and run them in the B&N Walled Garden. You can't download or refresh apps, but you can work with sideloaded books and apps. It's not 100% stable yet, but I think with careful selection of sideloaded apps, it may be.
Click to expand...
Click to collapse
I think I saw that. I'll take a closer look, but to be honest right now I think my son will be be more likely to use the the straight Android boot to have access to the games he's always playing on my phone. I'm hoping that will change, but as this point I'm thinking I'm better off waiting until I can get the Market and Amazon Appstore on 1.4 and just getting the stuff he's used to playing with. I'd really like him to use the BN reader, but realistically I don't know how much he'd use that right now.
Frankly, it comes down to me not really wanting to go through the effort of sideloading the games he plays. I'd really just like to get it connected to the Market and Appstore and downaod the stuff he uses.

If I were you, I'd create a CWR bootable and flash CM7 or one of the other many available ROMs (possibly MIUI, I heard it's pretty top notch, somewhat akin to the layout of iOS). I find the NC's OS somewhat distasteful. I believe Dalingrin once said that he knew the NC better than its creators. Anyways, personal bias coming into account, I flashed CM7.1 and never looked back. It's completely up to you. If you do choose to take my advice, there are alot of good devs who can help you out with the process. Dalingrin and Fattire are 2 of my favorite devs.
I used to have a forum signature... then I took an arrow to the knee.

[Q] Cold weather returned my NC to stock !!

I purchased my NC used and with CM7 installed. I loved it the way it was except for the outdated flash player.
I forgot it in my car at work and it was all of 7* that night. Once I got home it took an hour to start up and now its just a regular NC, no Android. When I try to do the introduction registration, it connects to WiFi but tells me it cannot register at this time and gives a number to call.
I didnt mod the Nook what so ever but with the help of this site I did mod my HTC Incredible with excellent results. Id like to have Android on my NC like before but Id like to run a updated verison with Flash 11 if possible.
Please help a Nook Newbie !!! I know there is a TON of info on this device here but it gets pretty confusing pretty fast.

Was CM running on eMMC? I don't know why it wouldn't connect, but maybe something cold related caused the device to boot and continuously fail, doing the 8 failed boot restore?

You can't register it probably because the person you bought it from never de-registered it. Time to do a full reinstall of CM7. There are a ton of posts that describe how to do it in detail. Just use the search function.

LOL
You left your NC running CM7 (just to make fun, I assume it's installed in eMMC) in the car with temp. around 7 and after a nite, it automatically reverses back to bone stock, LOL
Man, if it's true, it gotta be an EASIEST way to restore stock ROM, crackinggg
Back to your case, for some reason, I do think your NC running CM7 off uSD and when it booted up, couldn't get into uSD so it booted directly to eMMC. Hope that's the case.

I bought it without an SD card so the mod was already installed on the NC internal memory. V
Ive read thru alot of info on here but still a bit confused. Im also wondering if having CM7 previously installed will cause me any problems trying to flash a different ROM.

pwrshft99 said:
Im also wondering if having CM7 previously installed will cause me any problems trying to flash a different ROM.
Click to expand...
Click to collapse
It won't if you wipe the caches for a full reload. Keep in mind that if you are the least bit hesitant you could just as easily make a bootable SD card and have no worries.

pwrshft99 said:
I bought it without an SD card so the mod was already installed on the NC internal memory.
Click to expand...
Click to collapse
For real???
How can that be possible?
I don't mean to not believing in you but it's too odd.

[Q] Conversion/flashing CM9 using Racks dualboot for SD

Here's my issue. I was using the latest racks prepared boot for CM9. The one dated 5/1 or so. I decided I wanted to try my hand at converting a nightly and flashing it on my own. I've been having nothing but trouble with the conversion process and I have no idea what I'm doing wrong.
And I've tried a few different ones of Eyeballers nightlies, but I'm always getting the same error. I just tried it using the Android script and the windows script and I'm getting different issues in each.. When I try to convert in dos, i'm getting really tiny files and most of the time it gives me a bunch of lines with items not found.
I'm really new at this but I've looked and was unable to find any answer to why this wouldnt be working or even what i could be doing wrong. I can get into the recovery, I install the converted nightly and when I try to boot into it I just get a black screen, I waited a few minutes to make sure it wasnt just something with the the device or just a first time thing but nothing happened.
on the android version I get the error attached. Im not sure how else to say whats going wrong but if someone has some suggestions I'd really appreciate it.

You might get a better response if you post this question in Racks conversion thread. Here:
http://forum.xda-developers.com/showthread.php?p=25648626
Sent from my Nook Color running ICS and Tapatalk

unfortunately I am not able to until I reach the 10 post threshold. but rather than spam to hit that. I figured I'd try this first. Thanks though. Hopefully he'll still see this.

kontam said:
unfortunately I am not able to until I reach the 10 post threshold. but rather than spam to hit that. I figured I'd try this first. Thanks though. Hopefully he'll still see this.
Click to expand...
Click to collapse
I will put a post there for you.

kontam said:
Here's my issue. I was using the latest racks prepared boot for CM9. The one dated 5/1 or so. I decided I wanted to try my hand at converting a nightly and flashing it on my own. I've been having nothing but trouble with the conversion process and I have no idea what I'm doing wrong.
And I've tried a few different ones of Eyeballers nightlies, but I'm always getting the same error. I just tried it using the Android script and the windows script and I'm getting different issues in each.. When I try to convert in dos, i'm getting really tiny files and most of the time it gives me a bunch of lines with items not found.
I'm really new at this but I've looked and was unable to find any answer to why this wouldn't be working or even what i could be doing wrong. I can get into the recovery, I install the converted nightly and when I try to boot into it I just get a black screen, I waited a few minutes to make sure it wasnt just something with the the device or just a first time thing but nothing happened.
on the android version I get the error attached. Im not sure how else to say whats going wrong but if someone has some suggestions I'd really appreciate it.
Click to expand...
Click to collapse
1.Are you using latest version of script 1.3?
2.Did you try the terminal emulator for running script?
3.Did you try to delete and extract again the folders of the c2dsd in case something went wrong during first extraction?

thanks for posting there for me.
RASTAVIPER said:
1.Are you using latest version of script 1.3?
2.Did you try the terminal emulator for running script?
3.Did you try to delete and extract again the folders of the c2dsd in case something went wrong during first extraction?
Click to expand...
Click to collapse
1. I updated both scripts and was still getting issues.
2. if you mean the one on android then yes, thats what I was using. I also tried it using the cmd on windows.
3. I've tried that at least two times with each including redownloading all aspects of it to make sure that wasn't the case.

kontam said:
thanks for posting there for me.
1. I updated both scripts and was still getting issues.
2. if you mean the one on android then yes, thats what I was using. I also tried it using the cmd on windows.
3. I've tried that at least two times with each including redownloading all aspects of it to make sure that wasn't the case.
Click to expand...
Click to collapse
Not sure about the windows issue. I'll have DizzyDen take a look at that. But with the Android version, i'll take a look at that in a little while. Looks like it's another mistake on my end. Mkimage is dependent on 'libmusl.so' which I did not include in the tools folder. I overlooked this tidbit because I had "BOTBREW" installed on my system so it never complained about linking to it.
Sorry for all the problems. I'll try and have a fix ASAP. Your feedback is much appreciated. Can't fix things if I don't know if their broken or not.
Thanks,
Racks
EDIT: Fixed I believe. Please try the v1.3a for the Android script.

I'm looking into the DOS version as we speak....

You guys are all really amazing for helping me out.
And as probably mentioned before by rasta Im not sure what the issue is but theres still something not quite gelling for the version. I took another screen to hopefully help you identify where its going weird. It is a little different but its still that crc cd issue. Im not going to try to flash it to see if it works, only because Im pretty certain that won't do it. But I really appreciate you looking into it.
and for clarity I also get a very similar if not exactly the same message when It trys to do the gapps as well. (using the 4/29 signed gapps)
And I decided now to try flashing the rom. it worked. Fantastically! though the boot animation is freezing. I dont even care about that since its actually working again. Awesome. But.. now im having those same issues as Rasta with the gapps. I flashed them and when I went to reboot it brought me to stock. When I converted them, i converted them with the rom. That rom worked. the gapps did not. if theres anything else I can help just ask and Ill try to do. Im just so happy to have a bootable CM9 again. Thank you so much

kontam said:
You guys are all really amazing for helping me out.
And as probably mentioned before by rasta Im not sure what the issue is but theres still something not quite gelling for the version. I took another screen to hopefully help you identify where its going weird. It is a little different but its still that crc cd issue. Im not going to try to flash it to see if it works, only because Im pretty certain that won't do it. But I really appreciate you looking into it.
and for clarity I also get a very similar if not exactly the same message when It trys to do the gapps as well. (using the 4/29 signed gapps)
And I decided now to try flashing the rom. it worked. Fantastically! though the boot animation is freezing. I dont even care about that since its actually working again. Awesome. But.. now im having those same issues as Rasta with the gapps. I flashed them and when I went to reboot it brought me to stock. When I converted them, i converted them with the rom. That rom worked. the gapps did not. if theres anything else I can help just ask and Ill try to do. Im just so happy to have a bootable CM9 again. Thank you so much
Click to expand...
Click to collapse
Thanks for the feedback... looking into gapps issue now... is this for primary or alternate?

Everything I'm referring to is for the alternate. Also not sure if this has anything to do with it but the calendar is broken with the gapps back from the novemeber or whenever dual boot apps. But flashing the fix doesnt fix it anymore, and then a reboot after that brings me to stock.
Also, im having issues doing a factory reset on stock when i take the SD card out.. is there something that clockwork did when it was trying to flash an incorrect rom?

If you want to return to stock situation, you probably should wipe everything and find stock image to flash.
Unleashed from my Revolutionized Desire HD

CM9 on Nook Color is frustrating me

I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!

BennyP86 said:
I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!
Click to expand...
Click to collapse
How did you install it? To SD or internal memory. And which version of CM9 are you using? Opengl or non-opengl?
If you installed to internal memory, did you factory reset via CWM first? You need to if coming from stock. You can still do it now.
If you installed to SD, what class SD card are you using? It should be a Sandisk class 4.

Your download isn't broken. CM9 on the NC is - it isn't really *done* yet on the Nook Color. Developers are working on it, but for now your best bet is CM7.2. I expect we might hear an announcement very soon, but for now, use CM7.2.

It's obvious that the installation of this person has problems.
CM9 DOESNT have this kind of problems. It might be a bit slower in hardware acceleration matters in comparison to CM7, but it sure works fine in all other matters.
It's quite mature by now.
Produced by NookColor at ICS AOKP 4.0.4

BennyP86 said:
I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!
Click to expand...
Click to collapse
What did you download?
Edit: Forget it. LeapinLar already asked all the pertinent questions.

I'm having similar issues as well. It's kind of sluggish and it has frozen a few times already. I downloaded the nightly by Eyeballer over at Techerrata: cm-9-encore-20120904-0700-unofficial.zip.
In the instructions over at Androidforums does say that it might be sluggish the first few days so I guess I will just have to wait it out. I did just install about roughly 12 hours ago.

I just installed today, over my CM7.2 install in internal memory. It seemed okay at first, though a bit sluggish. But then I re-booted it and now it is acting possessed. Apps are launching by themselves (Play Store, a notepad app I had installed, voice command window, etc.) Very odd. I've shut it down and re-booted, same thing. I am thinking of maybe doing a complete fresh install from a SD card, wiping out all my apps from 7.2 and see if that helps at all. Or, I made a backup of my 7.2 install from CWM before installing CM9, so can always go back to that.

Just to follow up on my previous post: My NC running CM9 (latest GL version) did stabilize quite a bit after a day or so. But it still is very sluggish at times, to respond to screen touches, opening apps, and even loading webpages. I ran the Quadrant benchmark tool and the results are slightly lower than I got with CM7.2, but not terribly so. I'm debating whether to go back to 7.2, or do a factory reset and try a fresh install of CM9 and see if that's any better? Is there any evidence that a fresh install will work better than updating over a installed 7.2?

It's total mistake to update CM9 over Cm7 or any other different system.
To be able to talk about how things should be, you need to do a clean install and then for sure things will be better.
Powered by my IceCold 8.6.1 DHD

RASTAVIPER said:
It's total mistake to update CM9 over Cm7 or any other different system.
To be able to talk about how things should be, you need to do a clean install and then for sure things will be better.
Powered by my IceCold 8.6.1 DHD
Click to expand...
Click to collapse
Wow, that made a world of difference! Thanks. I thought I'd read somewhere else that it was okay to update from CM7 to CM9.

Newbie Need Help..got my TF101 rooted..now what?

Hello, Im new to this and was able to root my TF101 build .27 with oneclickrecovery V0.4, which installed SUPERUSER v3.0.7
Wanted to install the EOS 4 JB because I read this is very Fast and Stable. This is what is important to me, hence the root.
Now how do I use this and install the ROM?
Is there a youtube or link that someone can direct me to?

Have a look here:
http://www.transformerforums.com/forum/showthread.php?t=33773
You will need to update to TWRP 2.3.2.3 (highly recommended) via GooManager

THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.

hipertec said:
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
Click to expand...
Click to collapse
I'll alleviate some of your confusion lol, Rouge XM etc are recoveries (that are accessed via holding vol down and power) Easyflasher is a program that runs off your pc and allows you to install a recovery (like Rouge, TWRP or CWM). Easyflasher also works as an unbrick tool (if you do something wrong and mess up your tf101 easyflasher will restore it back to stock)
When using a recovery you need to place the rom on your sd card (some recoveries will only allow flashing from internal or external sd card's not both, but in the case of rouge it access both) then wipe the device (this will get rid of data etc, so if your going to make a back up this is the time) and then wipe everything except for battery stats (it isnt necessary to wipe everything but im not using the same recovery so i cant remember what the options say on rouge so just wipe everything for now) then flash the rom with "install for .zip"(and anything that goes with it i.e gapps or another kernel----- depends on the rom your using) and then just to be safe wipe the devlik cache again and reboot.

hipertec said:
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
Click to expand...
Click to collapse
I would STRONGLY suggest switching to TWRP. Rogue will work for now, but if you flash updates to this ROM, the new file structure for 4.2 will cause your /sdcard/ to end up in the /sdcard/0/ directory, and after another flash it will be /sdcard/0/0/. You can move the files, but IMO TWRP is much better anyway (it can flash from internal and external storage).
You can install GooManager and choose to install open recoveryscript from the menu, or you can use the dd command and a terminal emulator to install TWRP:
First, download the twrp blob from here: http://techerrata.com/browse/twrp2/tf101
Rename the 2.3.2.3 blob to TWRP.blob
Method 1
Open a terminal emulator.
Code:
$ [B]su[/B]
# [B]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/B]
# [B]reboot[/B]
It is important to just do a reboot, if you reboot to recovery immediately it WILL NOT update the recovery. Upon reboot, you should see a progress indicator at the Eee Pad screen. Feel free to reboot to recovery after this (even before it boots).​

I strongly recommend reading the post by Fredurco in the link he provided. As a matter of fact, read the first three posts. These are the most detailed instructions for any ROM I've ever seen and believe me, I've seen more than a few. Take your time and just follow those directions to the letter and you will be fine.

frederuco said:
IMO TWRP is much better anyway (it can flash from internal and external storage).
Click to expand...
Click to collapse
I agree, rogue can also flash from internal and external, but twrp is the best, I need to update PERI to include it...

Thing O Doom said:
I agree, rogue can also flash from internal and external, but twrp is the best, I need to update PERI to include it...
Click to expand...
Click to collapse
Yeah, get crackin!

Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app

hipertec said:
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Nothing as fast, eos3 in my opinion is the stablest custom ROM I've used but I can't move away from eos4, plus when timduru release the cornerstone build my tablet is gonna get some major use.

hipertec said:
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
JoinTheRealms said:
Nothing as fast, eos3 in my opinion is the stablest custom ROM I've used but I can't move away from eos4, plus when timduru release the cornerstone build my tablet is gonna get some major use.
Click to expand...
Click to collapse
I agree! EOS 4 IMO is the most usable and stable 4.2 build. My biggest complaint with the CM10.1 build was the touchpad disable was not working. It is still a great ROM otherwise and pretty stable.
As far as 4.1 ROMs, EOS 3 is solid, and so is the CM10/PananoidAndroid hybrid.
I am definitely itching for some cornerstone love!

I use liquidsmooth currently, and it's my new favorite, since everything works. I haven't found or noticed any bugs, which is rare.
EOS4 is also good, but I just don't like the feel of it oddly. Very well built and worth a shot though.

Hi Fred! Dug my TF101 out of moth balls and put on EOS4.
Had some trouble with the drivers, So I ended up using 1 from column A, 2 from column B:silly:
end result, got my drivers, APX mode going, (cross between oneclickrecovery, easyflash, nvFlash, Universal Naked Drivers),
Finally got twrp on and flashed superuser
got twrp-goo manager to update it, Flashed EOS4- saw updated recovery did not stick, finished the flash, updated twrp again, reflashed eos4- saw twrp update did stick this time, and now get to play with the TF 101 all over again!
Everything old is new again!
Thanks Fred! Your post on the TF forum was great, and XDA supplemented what wasn't working for me!! Great teamwork:victory:

Thanks to Fred's excellent tuts, I was able to easily get TWRP installed and rooted (although it did kill my WiFi somehow, which I'm hoping will be solved with a different ROM), but have a dilemma:
Not to hijack (didn't see the point of starting a new thread about the same thing, but I will if you guys want me to) but which ROM will give the best video performance? I'm not trying to do 1080 stuff or anything naive like that, but I would at least like to be able to watch some of the lower quality 720p stuff (NPW's releases are very good) without stuttering or syncing issues.
Note: I'm not trying to do everything with this tablet and overall I'm VERY satisfied with the overall performance and wouldn't even be tinkering with it at all (I've had it for over a year on stock ICS) if I didn't travel a lot and use it to watch movies on the go. I only use this tablet for gaming, surfing, movies and lots of document viewing (PDF, MSOffice, etc). I don't care about GPS or the camera. I have a phone for that. However, I don't have the time or means to be constantly reflashing this thing because WiFi drops out every 30 minutes or something like that.
Basically, I'm looking for the ROM with the best combo of:
- Stability
- Respectable HD-ish video playback
I'm not a total Android noob. I spent many hours tinkering with my old Nook Color back in the day, so no worries there. I'm just looking for reliable video playback on the go. I've been looking at Android Revolution HD to preserve the ASUS File Manager and things like that, but really haven't seen anything definitive about video playback improvements. I'm open to moving up to JB, but its not a burning desire or anything.
Thanks!

LongbowFoSho said:
Thanks to Fred's excellent tuts, I was able to easily get TWRP installed and rooted (although it did kill my WiFi somehow, which I'm hoping will be solved with a different ROM), but have a dilemma:
Not to hijack (didn't see the point of starting a new thread about the same thing, but I will if you guys want me to) but which ROM will give the best video performance? I'm not trying to do 1080 stuff or anything naive like that, but I would at least like to be able to watch some of the lower quality 720p stuff (NPW's releases are very good) without stuttering or syncing issues.
Note: I'm not trying to do everything with this tablet and overall I'm VERY satisfied with the overall performance and wouldn't even be tinkering with it at all (I've had it for over a year on stock ICS) if I didn't travel a lot and use it to watch movies on the go. I only use this tablet for gaming, surfing, movies and lots of document viewing (PDF, MSOffice, etc). I don't care about GPS or the camera. I have a phone for that. However, I don't have the time or means to be constantly reflashing this thing because WiFi drops out every 30 minutes or something like that.
Basically, I'm looking for the ROM with the best combo of:
- Stability
- Respectable HD-ish video playback
I'm not a total Android noob. I spent many hours tinkering with my old Nook Color back in the day, so no worries there. I'm just looking for reliable video playback on the go. I've been looking at Android Revolution HD to preserve the ASUS File Manager and things like that, but really haven't seen anything definitive about video playback improvements. I'm open to moving up to JB, but its not a burning desire or anything.
Thanks!
Click to expand...
Click to collapse
I guess I am not sure what is causing your WiFi stability issues. I have no problems with the EOS 4 ROM and WiFi. It never drops out on me. It is perfectly stable, and I can play 720p H264 23.94 FPS mkv files with no issues using MX player.
Before I ran EOS 4, I was running the ParanoidAndroid/CM10 Hybrid ROM and it was just as stable and fast.
If you are having WiFi issues, did you do all the wipes (Cache, Davlik, System, Factory Reset) before flashing the ROM? If not, then that is probably where the WiFi issue is (settings from your previous ICS ROM still present on the data partition).

Disregard the bit about the WiFi. I disconnected and reconnected to my network and all is well.
It sounds like EOS4 is the only ROM that is still consistently updated. I'll give it a shot and see how it goes.
Thanks!

LongbowFoSho said:
Disregard the bit about the WiFi. I disconnected and reconnected to my network and all is well.
It sounds like EOS4 is the only ROM that is still consistently updated. I'll give it a shot and see how it goes.
Thanks!
Click to expand...
Click to collapse
EOS4 and the CM10.1 No-Name are the only ones getting regular updates.

Thanks for the quick responses. EOS 4 is installed and process of redownloading all my apps. Now I just need to test out some video. I'm testing it without the OC kernel first, just for fun.

If you wanna see more in-depth which rom is better, I recommend a little app called Antutu benchmark, it'll give your current setup a score depending on how fast it does things like 3d renderind, sd card reading and battery performance

I might be in the minority with this opinion, but after some tinkering I'm not all that convinced that EOS is any faster than the stock ROM from a general usability standpoint (even with the latest KAT kernel), but the video is definitely improved, so I'll keep it as my "daily driver".
Thanks for the help, guys!