[HOW-TO] Install Official CM7 Release (Gingerbread) to Internal Memory (eMMC)

I got the install done just right!

after rebooting i found the CM7 lock screen was a bit finicky, so I went into settings and enabled 'unlock on menu button' or whatever its called.
Now when I hit the nook 'n' menu button, the nook wakes up and I get the CM lock screen without any way to actually unlock!

I suppose I could reflash it again....

okay, I reflashed it...

Now, what do I use for a 'back' button??

CM7 should have a back button built into the notifications bar, top right. I also use button savior for occassiones where apps go full screen w/out notification bar. There will be no physical back button unless one is remapped.


Sent from my Gingerbreaded NookColor using Tapatalk...
 
My nook color will not turn on at all after installing the latest nightly. It seemed to install correctly and everything. But now nothing does nothing when I push the power button. I should have stayed with froyo I guess. Anything I can do?

Explain exactly what the nook does, like how far into the boot process does it get. Also, can you post a logcat, so we can see what the nook is actually doing?

Adb logcat > boot.txt

Use that command while connected to nook from computer just before you boot. Wait for about ten minutes, stop the log (ctrl c, I think), and it will be called boot.txt and will be in the directory your command prompt opened from. Post that.


Sent from my Gingerbreaded NookColor using Tapatalk...
 
CM7 should have a back button built into the notifications bar, top right. I also use button savior for occassiones where apps go full screen w/out notification bar. There will be no physical back button unless one is remapped.


Sent from my Gingerbreaded NookColor using Tapatalk...

Wow, I didn't even notice that button up there, thanks!
 
If you want the back up on an SD, why not get a CWR image flashed on a SD card, boot to the card and perform a backup. I am not sure if the devs that maintain the bootable images have created one for version 3.0.0.6 or newer, but that version or newer is what is recommended.


Sent from my Gingerbreaded NookColor using Tapatalk...

I could absolutely open to doing that, but the idea makes me nervous and would prefer not to. I'm not very technically savvy in the area of adb, kernals, etc., and I had a lot of trouble with ROM Manager & CWR (boot stuck in CWR) in the first week that resulted in 5 factory resets using the 1.0.1 recovery file through CWR. I've finally gotten to a point where I can boot both into AND out of CWR thanks to the newest version of CWR (3.0.1.0). I've now downloaded a bunch of apps and have a few screens setup wtih ADW EX launcher and feel satisfied enough that I don't want to have to go back to 1.0.1, re-update, and re-root if something goes amiss.

Maybe that's more my baggage than info you need, so in summary, I'd prefer not to do it for 2 reasons:

  1. I do not fully understand if/how an SD bootable CWR will affect my eMMC CWR
  2. The inability to create a backup with an Autonootered 1.1.0 NC is a flaw/bug in the current CWR and there is a way to fix it that I don't yet have my head around. I feel like the issue should be resolved lest it inhibit progress or create isssue in the future.

AN aside to Avi, Kazy, & Simon: I'm struggling a little bit with the NC... When you take time out of your day to help me out here's what happens: I appreciate it a lot (A LOT), you increase my knowledge and enjoyment with/about my NC, and because you increase my knowledge you increase the likelihood that I'll pass it on to someone else and continue to grow the community. Thank you and please keep it up!!
 
Explain exactly what the nook does, like how far into the boot process does it get. Also, can you post a logcat, so we can see what the nook is actually doing?

Adb logcat > boot.txt

Use that command while connected to nook from computer just before you boot. Wait for about ten minutes, stop the log (ctrl c, I think), and it will be called boot.txt and will be in the directory your command prompt opened from. Post that.


Sent from my Gingerbreaded NookColor using Tapatalk...

It wasn't booting period. Nothing, screen would not turn on at all. But I know what I did wrong. I formatted the uSD card while it was in the nook. I guess that is a no no, as wipes the boot partition not the uSD card, just with the CM nightly. So I have it booting into clockworkmod recovery, from the uSD card. And I have the return to stock zip, found at xda. Only problem is after it is done doing the update I don't know what to do in CWR? If I tell it to reboot it obviously reboots from the SD card if I just shut down it won't reboot at all nothing turns on, without the SD card in there. I really did a number but at least I know it can be fixed. Maybe I have the wrong file???

EDIT: Fixed it, by flashing two files the nook-complete something something, and repartition boot. And of course I flashed the boot one first. Now it is back to like it came out of the box! Woot. Thanks to all the people over at xda and here between the two...wow.

Here is the link to the original post that helped me return to a working stock nook. http://forum.xda-developers.com/showthread.php?t=914690
 
Last edited:
I'm having some trouble with getting the clockwork img. So I have the tar.gz, and it md5'd fine. How do I get the img? I can't remember how I got nookies img :(

The instructions say extract img for tar.gz. I downloaded the tar.gz. I don't see any img download. I also tried extracting the file inside the tar.gz, and renamed it to .img, but that didn't work either. I keep getting corrupted MicroSD cards.
 
Last edited:
My problem is here

Download the required EXT4 file suitable for your Micro SD card.
b. Extract the zip file with suitable zip manager.

I download a tar.gz for 8gb microSD cards. Win32 disk imager doesn't recognize it at all. I extract some file (doesn't even have an extension) from the tar.gz using 7zip. This is a 7.03Gb file. I add a .img extension, and burn to SD card. It still doesn't work. Not sure what to do at this point.
 
My problem is here



I download a tar.gz for 8gb microSD cards. Win32 disk imager doesn't recognize it at all. I extract some file (doesn't even have an extension) from the tar.gz using 7zip. This is a 7.03Gb file. I add a .img extension, and burn to SD card. It still doesn't work. Not sure what to do at this point.

Get Winzip, an utility (program) that will extract the file for you. The .tar.gz extension is a type of file compression. I didn't know what it was a few days ago, either. Definitely a learning process!
 
Actually I knew what tar.gz was, my problem was with the file inside it. Windows was having issues with it. Of course, all I had to do to fix the problem was boot into Linux. I swear, everytime I boot into windows, things blow up. :p

Sent from my phone. Forgive the typos.
 
I initially installed honeycomb and found it to be a bit flaky on many things, i'm sure it will be much better after a couple more releases.

In the meantime I installed the CM7 port, MUCH better, very stable.
Installed Button Saviour for a back button, AdFree, DropBox, Astro File Manager.

The only oddity i've noticed with the CM7 is with Wifi, when I turn it on it goes;
Turning on...
wait...
Turning off...
wait...
Turning on...
wait...
Turning off...
wait...
Turning on... Getting IP... On!

It works, just takes a minute or two to get connected.

and of course, Flash doesn't work at all....
 
Last edited:
If we update a Nightly build, does it wipe everything??? Or will all my apps and data remain intact???

I see nightly 13 is out, but I don't want to update if each time I"m going to have to reinstall all my apps.
 
If we update a Nightly build, does it wipe everything??? Or will all my apps and data remain intact???

I see nightly 13 is out, but I don't want to update if each time I"m going to have to reinstall all my apps.

You shouldn't need to factory wipe if you are coming from a recent build. Just wipe the cache, flash the zip, and reboot. You should still have all of your apps. If you are coming from a very early nightly (like pre v7) I would factory wipe just because there have been significant changes.

And on another note, I'm LOVING nightly 13! My apps finally works! Just a bit more work and I think we should see a release candidate.
 
You shouldn't need to factory wipe if you are coming from a recent build. Just wipe the cache, flash the zip, and reboot. You should still have all of your apps. If you are coming from a very early nightly (like pre v7) I would factory wipe just because there have been significant changes.

And on another note, I'm LOVING nightly 13! My apps finally works! Just a bit more work and I think we should see a release candidate.

do the nightly builds have release notes? I didn't see any..
 
So I heard n13 might be able to use the full 8GB of internal memory (instead of 1GB previousl?) - is that correct?
 
Great job on n13, glad to see the market working. One problem I'm having is that the wifi icon on my notification bar is not working, it looks like I have no signal but my signal is fine. Is anyone else experiencing this?
 
I am getting an issue where cell standby is killing my battery. I have set airplane mode and then turned on wifi but it still seems to be searching for a signal. And ideas how to get that to. Stop???
 
I am getting an issue where cell standby is killing my battery. I have set airplane mode and then turned on wifi but it still seems to be searching for a signal. And ideas how to get that to. Stop???

There was a way to replace a few of the files and disable this in Froyo...I suspect it will be disabled in future builds since Encore is incapable of phonecalls.
 
So I heard n13 might be able to use the full 8GB of internal memory (instead of 1GB previousl?) - is that correct?

Nope. I made the jump to 14 this morning, but it looks like there is still only the 1gb of internal storage available. /mnt/emmc shows 5gb available though.
 

Forum statistics

Threads
954,380
Messages
6,961,479
Members
3,163,017
Latest member
harmonywavegummiess