• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Help a Nook Noob

*sigh*

I thought I was finally doing well. Flashed everything, and after I did the factory wipe/reset, CWR sort of froze up on me. I couldn't navigate at all. I went ahead and popped out my SD card and reformatted it in my PC. I then booted the Nook, and saw the Cyanogen logo, then, in landscape view, saw A N D R O I D in the lower-left. After a few seconds of that, I get what appears to be a cursor in the upper-left, and it just sits there.
 
flu13 said:
*sigh*

I thought I was finally doing well. Flashed everything, and after I did the factory wipe/reset, CWR sort of froze up on me. I couldn't navigate at all. I went ahead and popped out my SD card and reformatted it in my PC. I then booted the Nook, and saw the Cyanogen logo, then, in landscape view, saw A N D R O I D in the lower-left. After a few seconds of that, I get what appears to be a cursor in the upper-left, and it just sits there.
Click to expand...

How long did you let it sit before you decided it was frozen? Sometimes there's a period of screen inactivity. Try it again and see if it works by letting it sit a little longer.
 
A good 5 minutes or so.

I flashed back to a stock 1.2 that I found, tried flashing CM7 again, and no dice, still.

Flashed ManualNooter, and it seemed to work. I'd like to get CM7 working, but at least now I can play a little bit.
 
flu13 said:
A good 5 minutes or so.

I flashed back to a stock 1.2 that I found, tried flashing CM7 again, and no dice, still.

Flashed ManualNooter, and it seemed to work. I'd like to get CM7 working, but at least now I can play a little bit.
Click to expand...

You did get the stable build for the Nook from here?

You might try downloading it again.
 
You want the stable 7.03 build. I've seen complaints about the cursor like you describe, but I think it's due to flashing the wrong overclock kernel version (ext4 instead of ext3). Obviously I'd know more if it had happened to me. :D
 
Wait a sec....7.0.3 and ext4 don't play nice together?

The guide I was following on XDA had a link to ext4. Maybe that's the issue. Where could I get ext3? And if 7.0.3 is the latest and ext4 is the latest, why doesn't ext4 work with it?
 
This morning, I had some success with CM nightly build 87 and the 5-23-11 OC kernel. I got the device to come up, but didn't love the experience. I seemed to have lost my notification bar and the soft keys down there, and I kept getting FC messages from com.android.media or something like that.
 
flu13 said:
This morning, I had some success with CM nightly build 87 and the 5-23-11 OC kernel. I got the device to come up, but didn't love the experience. I seemed to have lost my notification bar and the soft keys down there, and I kept getting FC messages from com.android.media or something like that.
Click to expand...

Sounds like you have successfully got CM7 to boot. At this point I'll have to bow out as I have no experience with any of the Cyanogen mods. Good luck and have fun.
 
Thanks. For now, I've gone back to my manual nooter setup. I think I'll try PhireMod later today.
 
Ext4 is only for 7.03 and certain nightly builds after 7.03. I think they have since gone back to ext3.

The latest kernels only work with nightly CM7 builds after 7.03 that include the .32 kernel and cannot be interchanged. Maybe that's what your problem was.

I usually install what needs to be installed, which is just CM7 and Gapps. A kernel is not required initially and can be installed later, preferably after a recovery backup. :D

If you check the kernel in settings... about phone, you can see which kernel you need. :D
 
flu13 said:
This morning, I had some success with CM nightly build 87 and the 5-23-11 OC kernel. I got the device to come up, but didn't love the experience. I seemed to have lost my notification bar and the soft keys down there, and I kept getting FC messages from com.android.media or something like that.
Click to expand...
I decided to play with installing CM7 to the internal memory on my green dot NC today and am seeing the same issue with the most recent nightly...anybody know a solution? Should I try the stable CM7 instead? Or just go straight to Phiremod?

Also, Settings/Cyanogenmod Settings closes with a message that "process.com.android.settings has stopped unexpectedly".
 
Try fixing permissions in Rom Manager (or boot into recovery under advanced menu via Rom Manager)
 
colchiro said:
Try fixing permissions in Rom Manager (or boot into recovery under advanced menu via Rom Manager)
Click to expand...
Already did. It didn't help so I wiped and reflashed. Same thing happened and fixing permissions didn't help then either. I did fix the android.media message by clearing a cache (Market? can't remember) as described in another thread, but I can't seem to get rid of the one that pops up when I try to access Cyanogenmod settings.

The lack of the notification bar (I have nothing there - no clock, no battery reading, nothing) is especially annoying.
 
Problem solved. I hadn't done a data wipe because the instructions said "most people" didn't need to. Apparently I'm not most people. ;)
 
If coming from stock rom, then yes, you need to format data.

This is in the first section:

FORMATTING DATA: only format data if you want to delete all your apps. Google will still remember your purchased apps and will attempt to download the ones you've downloaded, assuming you have this turned on. See Settings... Privacy... "Back up my data" and "Automatic restore" should both be check for some time prior to installing if you want it to remember your apps and settings. Officially, formatting data is recommended for any rom install. Unofficially, I've had good results just updating my previous rom without formatting data. Your results may differ. :D The one exception? You need to format data if coming from the stock B&N rom or from a really old version.
Click to expand...
 
colchiro said:
If coming from stock rom, then yes, you need to format data.

This is in the first section:
Click to expand...
I didn't see that until later, since it was in the section on upgrading an existing ROM, which wasn't what I was doing (unless you call the stock B&N software a ROM, which wouldn't have been obvious to me at least, although I suppose it's technically correct). Would be good if there had been a reference to it in the part about installing CM7 from a bootable CWM card. All's well that ends well, though, and maybe my experience will help someone else. :) The guide was really helpful.

So far I like this setup better than running CM7 off a card - I think you're right about it working better. No mysterious crashes so far. Hopefully that will still be true after I install more apps.
 
You must log in or register to reply here.
Back
Top Bottom