Steps to manually apply 1.1 on top of rooted 1.01 (and retain root) (not working yet) - Nook Color Android Development

1) Grab the 1gb clockwork recovery sd card image
2) boot into CW recovery; mount /system and /sdcard from CW
3) grab a DIFFERENT sd card. unzip the sideload_update.zip, zip up just the /system files
4) unzip system.zip (or whatever you called it) from adb shell onto the nook after moutning it's sdcard (mount sdcard from clockwork, unzip the zip file through adb)
Testing this myself now, but need to step away for about an hour..
EDIT - not having much luck trying new things.. but limited on time for this..
OK - so the above method didn't work. But i'm having partial success going the manual route. Right now, I have a nook 1.1 install with superuser working, and most of the google apps working. What's not working is market installs. market is also working.. (everything that I've tested so far is working )
Here's what I've done - it's complicated and I don't recommend it unless you're comfortable with adb / linux /etc. (wait for a real dev to package this up if you're not..)
http://legacyschool.us.to/nookdev/clockwork/clockwork_1gb-0.4.tar.gz
1) Burn the clockwork SD recovery card - boot from it. http://legacyschool.us.to/nookdev/clockwork/clockwork_1gb-0.4.tar.gz after it boots, adb from the desktop to your nook. (alternatively, bootup nookie froyo and adb to your nook using it. CW would be simpler though for mounting the /system and /data)
2) Restore your system and boot images to stock, using dd directions here - ( http://forum.xda-developers.com/showthread.php?t=919353
3) Upgrade the nook to 1.1 manually using B&N's directions - http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/?cds2Pid=35758
4) after an install, your apps will mostly be working, but you won't have the google apps or superuser. Bootup again using the SD card image (either clockwork or froyo) - mount /system and /data from there (using the menus in clockwork if that's what you used.
5) Follow the steps from nookdevs to re-root your device
http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
http://nookdevs.com/NookColor_Installing_Busybox
Nook color email if you need it - http://nookdevs.com/NookColor_Email
grab the google apps - http://www.mediafire.com/file/awqekwp5dpbk4e3/nc_gapps.zip - adb push it to your device (adb push nc_gapps.zip /data/local/
copy the /system/framework/framework.jar to a backup file (cp /system/framework/framework.jar /system/framework/framework.jar.bk)
unzip the nc_gapps.zip (cd /system; unzip /data/local/nc_gapps.zip)
copy the framework file back as it's most likely incompatible with the new 1.1 software (haven't tried using it yet) - ( cp /system/framework/framework.jar.bk /system/framework/framework.jar)
(Credit to MrMuffin for getting market working) using the clockwork sd card with /system and /data mounted, run the following commands from adb shell -
Code:
cp /system/build.prop /data/local/build.prop.bk
cp /data/system/packages.xml /data/local/system.xml.bk
sed 's/^.*ro.build.fingerprint.*$/ro\.build\.fingerprint=verizon\/voles\/sholes\/sholes:2\.1-update1\/ESE81\/29593:user\/release-keys/' /data/local/build.prop.bk > /system/build.prop
sed '1,/uid.system/!{ /<perms>/,/uid.system/!d; }' /data/local/packages.xml.bk > /data/system/packages.xml
Then unmount /system and /data in CW, remove the SD card, and reboot.
Reboot your nook.. now you're in 1.1 with su working..
Still working on it.. market installs are failing (because I haven't personally done the steps for enabling market y et.. ) but the rest of the apps are happy.. <-- working now
-m

---

I'm curious as to how this works out. Do we really need two SD cards, however? Or does that just save time?

---

Are you sure the ramdisk and kernel don't need upgrading as well?

---

Fast HTTP Mirror of the 1.1 Update for Nook Color:
http://www.techerrata.com/dl.php?path=14&file=Sideload_update_1-1.zip

---

Can you mount the necessary partitions via Nookie Froyo on SDcard?
Homer

---

Seriously hoping that this works. The changelog shows some great improvements, while not necessarily big. Please let us know how its going for you.

---

first attempt resulted in bootloops.. Most likely permission related as I had just used zip on windows.. after using CW to recovery my old image, I'm trying again with a zip file made under linux (to retain permissions..).
The kernel might be necessary.. not sure.. will report back..
-m

---

Giving up for now.. even after setting the permissisions based on the updater-script file, I can't get past this error in logcat -
Code:
E/ActivityThread( 1673): Failed to find provider info for settings
I/ActivityThread( 1673): Publishing provider android.server.checkin: com.google.
android.server.checkin.CheckinProvider
I/SystemServer( 1673): Battery Service
I/SystemServer( 1673): Hardware Service
E/ActivityThread( 1673): Failed to find provider info for settings
W/dalvikvm( 1673): threadid=37: thread exiting with uncaught exception (group=0x
4001b170)
E/AndroidRuntime( 1673): Uncaught handler: thread PowerManagerService exiting du
e to uncaught exception
E/AndroidRuntime( 1673): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 1673): java.lang.NullPointerException
E/AndroidRuntime( 1673): at android.content.ContentQueryMap.<init>(Conten
tQueryMap.java:65)
E/AndroidRuntime( 1673): at com.android.server.PowerManagerService.initIn
Thread(PowerManagerService.java:525)
E/AndroidRuntime( 1673): at com.android.server.PowerManagerService$1.onLo
operPrepared(PowerManagerService.java:457)
E/AndroidRuntime( 1673): at android.os.HandlerThread.run(HandlerThread.ja
va:59)
E/AndroidRuntime( 1673): Crash logging skipped, no checkin service
I/Process ( 1673): Sending signal. PID: 1673 SIG: 9
D/BootAnimation( 1684): SurfaceFlinger died, exiting...
I/ServiceManager( 773): service 'telephony.registry' died
I/ServiceManager( 773): service 'batteryinfo' died
I/ServiceManager( 773): service 'SurfaceFlinger' died
I/ServiceManager( 773): service 'power' died
I/ServiceManager( 773): service 'entropy' died
I/ServiceManager( 773): service 'activity' died
I/ServiceManager( 773): service 'usagestats' died
I/ServiceManager( 773): service 'account' died
I/ServiceManager( 773): service 'meminfo' died
I/ServiceManager( 773): service 'cpuinfo' died
I/ServiceManager( 773): service 'activity.broadcasts' died
I/ServiceManager( 773): service 'activity.services' died
I/ServiceManager( 773): service 'activity.senders' died
I/ServiceManager( 773): service 'activity.providers' died
I/ServiceManager( 773): service 'permission' died
I/ServiceManager( 773): service 'package' died
I/ServiceManager( 773): service 'content' died
I/ServiceManager( 773): service 'battery' died
I/ServiceManager( 773): service 'hardware' died
E/installd( 783): eof
Wondering if we need a hacked framework-res.apk file..

---

Oops, I 'd suggest editing your first post and making it clear NOT to try this just yet..

---

diomark said:
1) Grab the 1gb clockwork recovery sd card image
2) boot into CW recovery; mount /system and /sdcard from CW
3) grab a DIFFERENT sd card. unzip the sideload_update.zip, zip up just the /system files
4) unzip system.zip (or whatever you called it) from adb shell onto the nook after moutning it's sdcard (mount sdcard from clockwork, unzip the zip file through adb)
Testing this myself now, but need to step away for about an hour..
-m
Click to expand...
Click to collapse
I have a flashable, prerooted update.zip that gets you to 1.1. Will post up tonight. It worked fine for me when trying to update to 1.1.

---

Decad3nce said:
I have a flashable, prerooted update.zip that gets you to 1.1. Will post up tonight. It worked fine for me when trying to update to 1.1.
Click to expand...
Click to collapse
Not that I understand enough about it, but was thinking that framework had to be updated for google apps to work, is that going to be included with your update.zip? Or was the apps working without modification?

---

Decad3nce said:
I have a flashable, prerooted update.zip that gets you to 1.1. Will post up tonight. It worked fine for me when trying to update to 1.1.
Click to expand...
Click to collapse
What do u mean prerooted. What would this flashable zip do when installed overautonootered 1.0.1?

---

cflynt said:
Not that I understand enough about it, but was thinking that framework had to be updated for google apps to work, is that going to be included with your update.zip? Or was the apps working without modification?
Click to expand...
Click to collapse
It's essentially a ROM template created from the sideload update.zip from barnes and noble. It contains the gapps framework, gapps permissions, as well as busybox and the su binary along with the other goodies from the autonooter img.
I didn't want to risk brick on unrooting and updating via official so the created update.zip flashes via clockwork recovery but lacks the uboot stuffs for clockwork overwrite.

---

Decad3nce said:
It's essentially a ROM template created from the sideload update.zip from barnes and noble. It contains the gapps framework, gapps permissions, as well as busybox and the su binary along with the other goodies from the autonooter img.
I didn't want to risk brick on unrooting and updating via official so the created update.zip flashes via clockwork recovery but lacks the uboot stuffs for clockwork overwrite.
Click to expand...
Click to collapse
SO if we were to flash this we essentially goto a 1.1 nootered?
Will we be able to use the 1.1 ghz OC kernal?

---

Canadoc said:
SO if we were to flash this we essentially goto a 1.1 nootered?
Will we be able to use the 1.1 ghz OC kernal?
Click to expand...
Click to collapse
Yes. 10char

---

Well if it works as you say you are gonna make a lot of people happy!!!!!

---

Decad3nce said:
Yes. 10char
Click to expand...
Click to collapse
Have observed Decad3nce's work on the CDMA hero. This will be the real deal. Thank you sir. Glad you are on board.

---

Yea I've seen him on the Eris forums too. Thanks again Decad3nce. Much appreciated.

---

Sounds cool, but will it require CWM to install? Will it require it to run after?
I'm still seeing little weirdness reported with CWM so I'm avoiding it for now, but I could always install it and remove it again..

---

Decad3nce nice work!
All others, just sit tight, I am sure he's testing and will post a write up later. One thing I have learned from these boards is:
1. Never rush a developer
2. Never rush a developer
3. See #1 then #2.
Rushing leads to bugs leads to hate posts. So....Never rush a developer