[HOW-TO] [NEW VERSION] Install Nookie Froyo to Internal Memory

[backlund]

Wonder if anyone else has had this issue, or knows what I am doing wrong. Every time I flash the nookie-froyo-flashable-v0.6.7.zip the flash completes successfully, but then after I reboot it just goes back into ClockWorkMod recovery. I have taken out the SD card, but no matter what I do it just boots back to the clockwork recovery screen. I have redownloaded all the files, reflashed the CWR SD card, etc.

What's strange is that I can flash back to stock without any issues. As soon as I flash the froyo, it just boots into CWR. Any thoughts?

 

[DoughtCom]

I've read, re-read, and read AGAIN the simple instructions to do this. I'm a n00b at this but got auto-nooter completed after upgrading to 1.1 and everything is smooth up to that point.

It's the part where I start using clockworkmod Rom Manager. First issue is I have to "Flash ClockworkMod Recovery" to even get the recovery console on bootup, otherwise it just boots into the stock OS.

Once in there I choose "wipe data/factory reset" -> "wipe cache" -> then I install zip from sd (nookie-froyo-flashable-v0.6.7.zip).

That all works fine until reboot, like the person above me it's stuck booting only to the recovery console. I then (to the guy above me) use recovery console to install zip from sd and choose (CWR-removal.zip) to revert to stock.

It boots into android but I only get the top bar with a phone signal bar and time. Within 30 seconds it crashes or something, reboots and from that point on sits at the android black loading screen.

Am I using clockwork wrong? Am I missing a step? WTF is going?

 

[galdones]

Wonder if anyone else has had this issue, or knows what I am doing wrong. Every time I flash the nookie-froyo-flashable-v0.6.7.zip the flash completes successfully, but then after I reboot it just goes back into ClockWorkMod recovery. I have taken out the SD card, but no matter what I do it just boots back to the clockwork recovery screen. I have redownloaded all the files, reflashed the CWR SD card, etc.

What's strange is that I can flash back to stock without any issues. As soon as I flash the froyo, it just boots into CWR. Any thoughts?

Happened to me too. Go to the sticky: [HOW-TO] Restore Nook Color to rooted stock and follow everything until it's back to 1.1. Just run clockworkmod recovery from the SD card and flash the nookie-froyo-flashable-v0.6.7.zip. Hope that works out.

 

[hongkongdisney]

nyone have video problems with rockplayer and h264 mp4 files?
My videos are squished into 1/2 the screen with hardware acceleration on.
I have reflashed again, but the situation is same.
Any fix? THanks!

 

[Anoxymoron]

So what exactly is the difference between this and my simply rooted nook color?

I was hoping OP would mention some pluses and minuses to this over a simple root...

 

[amoricaorbust]

So what exactly is the difference between this and my simply rooted nook color?

I was hoping OP would mention some pluses and minuses to this over a simple root...

The biggest difference is speed. Even with the stock kernel there is more pep w/ Nookie Froyo than the simple Root Method.

Nookie Froyo

Pros:​

• Speed
• More like an Anroid Phone with Anroid Style Notification Bar
• Looks better with Higher LCD density (Larger Icons and Text)
• Better Gmail w/ Contact Sync
• Gallery App syncs photo album w/ Picasa
• More (but still not all) apps available in the Market

Cons:​

• Loses Nook Notification Bar at the bottom. This is a tradeoff. I got used to using the Nook notification bar inside most apps for back and Menu Bottons. I'm not a big fan of Soft Keys.
• Facebook Sync does not work - No Facebook photos in Contact. (this doesn't work in simple root either)
• Does not work w/ Nook Color E-reader software (No Magazine or Nook Kids if that is important to you)

These are some of the differences between the 2 off the top of my head. I'm sure there are others that I'm not thinking of and maybe a few that are important to other but not to me....

 

[elias832]

Im trying to install the GAPPS and i get "error: protocol fault (no status)" when i run "adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system"

adb recognizes the nook color because when i run adb devices it does list it.
Any help is appreciated.. thx.

 

[Anoxymoron]

Thanks for typing all that up amoricaorbust...

one more question. If I do decide to install nookie froyo to my internal memory and I end up not liking it---what would I have to do to get back to my plain rooted nook? Just stock restore it and re-root?

 

[bpopilek]

Does anyone have a link to the overclock kernel? The one posted in the first post links to XDA-Developers and it is dead. I have this all up and running minus the speed boost and would love to get that working as well. Thanks!

 

[amoricaorbust]

Thanks for typing all that up amoricaorbust...

one more question. If I do decide to install nookie froyo to my internal memory and I end up not liking it---what would I have to do to get back to my plain rooted nook? Just stock restore it and re-root?

Yup not much more to it than that. You can always try nookie on sd first.

 

[guts311]

3. Now, with your NOOKcolor connected to your computer's USB port, type the following (of course, hit enter after each line):

adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push [here, enter the path to your SDK tools folder]\system system/
adb reboot

Issue here...

Referring to the OP...I put the /system folder from the GApps zip files into my Android SDK/Tools folder. Then I run the first command above in CMD within the Tools folder and either CMD does nothing or it goes back the same prompt of C:\Android SDK\tools>

It won't seem to mount the system folder for RW. I know I have the usb drivers right, Device Manager shoes Android Composite ADB Interface, and like I said adb devices shows the ID.

What gives?
I checked with adb devices and it shows my NC hardware ID and everything...


ALSO, I've flashed ClockworkMod Recovery from ROM Manager, and it says success and everything. But clicking Reboot into Recovery does nothing but boot the NC normally into Froyo...???

 

[rats]

Hi there, I really need help. I guess I just kill my Nook color (V.1.1.0)

I installed Honeycomb in internal memory which worked great, but then I heard Froyo is more stable. So here i am, downloaded the clockwork/nookie zip as instructed at the initial post of this thread.

I installed the nookie zip file, took out the bootable SD card, and chose "reboot" on CW, but instead of rebooting, my Nook color become BLANK. nothing!

Could someone please help? (((

Thanks!
Stella

P.S. The devices Number shown on ADB (with bootable SD in NC , or else the Nook cannot be switched on at all ) has also changed from "2XXXXXX.." to "1XXXXXx" , does it matter? Thanks again!!

 

[bwat1009]

Help

I guess I should have known better than to do this as I am quite the novice. Froyo installed on my Nook but now I have no wifi access and the touch screen is responding quite poorly. Can you please help...

 

[guts311]

Issue here...

Referring to the OP...I put the /system folder from the GApps zip files into my Android SDK/Tools folder. Then I run the first command above in CMD within the Tools folder and either CMD does nothing or it goes back the same prompt of C:\Android SDK\tools>

It won't seem to mount the system folder for RW. I know I have the usb drivers right, Device Manager shoes Android Composite ADB Interface, and like I said adb devices shows the ID.

What gives?
I checked with adb devices and it shows my NC hardware ID and everything...


ALSO, I've flashed ClockworkMod Recovery from ROM Manager, and it says success and everything. But clicking Reboot into Recovery does nothing but boot the NC normally into Froyo...???

Anyone?? I can't get the market/Gapps installed per the OP's post and I can't get ClockwordMod Recovery to install/boot from device memory either. Help??

Trying to install the /system folder for the Gapps, all that ever happens when I try to mount or adb push is that CMD shows all the adb commands or it just blinks the cursor forever. WTF???

 

[guts311]

Anyone?? I can't get the market/Gapps installed per the OP's post and I can't get ClockwordMod Recovery to install/boot from device memory either. Help??

Trying to install the /system folder for the Gapps, all that ever happens when I try to mount or adb push is that CMD shows all the adb commands or it just blinks the cursor forever. WTF???

I got it to work but definitely not how you stated it. I had to do the following commands, involving adb shell'ing into the NC first to mount the system, THEN exiting back out to regular CMD, then pushing the folder. It was the only way:

adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb push .\system system/ (the files within /system pushed over now)
adb reboot

 

[yankees368]

Help! I got all google apps to install via adb, but I can't seem to log into any of my google accounts! What should I do?
After a minute or two, i get "cant establish a reliable data connection to the server" even though i have a wifi connection.

 

[dlcullen]

Help! I got all google apps to install via adb, but I can't seem to log into any of my google accounts! What should I do?
After a minute or two, i get "cant establish a reliable data connection to the server" even though i have a wifi connection.

I have gotten this msg a couple of times because I had the email or password entered incorrectly. I did eventually get it to go, you might just try a few times!

 

[yankees368]

I have gotten this msg a couple of times because I had the email or password entered incorrectly. I did eventually get it to go, you might just try a few times!

i've tried a whole bunch of times, and rebooted several times, and i know my password is correct, but I am still not able to log in.

 

[ddigby]

i've tried a whole bunch of times, and rebooted several times, and i know my password is correct, but I am still not able to log in.

About an hour ago I changed my build fingerprint and cleared the google services framework data, which requires re-entering account data. I was unable to get it to accept my info. I assumed I screwed something else up and just decided to try starting over, when I get to the point where I need to enter account data I have the same issue.

There is another person with the same problem in the Nookie Froyo off of SD thread.

I am guessing that there is a server issue of some sort.

 

[yankees368]

So what do we do from this point? This isn't really a very useful device if I can't even log into google. Will this resolve itself or do we need to take action?