[Nook Touch Android Development] roustabout:
I didn't have an exactly epic fail, and copying in su and the xbin directory (which is busybox and a boatload of symlinks for me) seems to be working well, but I do need finish setting the permissions on su - I'm already able so use my core apps. The big one being fbsync, since I'm just not that happy with the onboard reader.

Here's how I proceeded from rooted 1.0.1 to do the update. As a side note, I have done extensive customization of my device, resizing /media and /data and removing /data/media/B&N to put in symlinks to a new B&N tree in /media/B&N. I have about a gig of space for sideloads, and I can see my BN content from my computer. Very important for magazine curation (some mags, like the New Yorker, are only sold on the e-ink platform, but I want to read them elsewhere.)

- I have a backup made after my device was registered and before it was rooted;

- I have a fallback made from today before doing any screwing around, booted from noogie, cabled into a VMWare instance running linux, did a dd backup.

- I can mount individual partitions from my backup globs using the instructions here:

http://www.andremiller.net/content/mounting-hard-disk-image-including-partitions-using-linux

boot with noogie

mount partitions from a backup - 1 and 5 - to restore system to an upgradeable state.

p1 and

p5 via simply deleting all files already in, and copying over from a backup made after registering but before rooting.

boot.

copy across update file to the /media partition.

update installs as expected.

device restarts.

update is in; apps all still installed but

of course su is gone. Custom partitioning preserved.

Touchnooter resulted in a very unstable platform. Fast reboots prevented mount of Noogie or Touchnooter disk at start.

So, I found that if, during the reboot cycle of the four oscillating dots, I kept holding power in, I could get the device to shut all the way down.

Boot from Noogie, repeat the clear, restore, update steps.

- button savior still installed and running

- FB reader still installed and working

- FB sync crashing (no root)

- magazines and symlinks still viable.

Things that are missing include nook color tools - which might not have been best dropped in /system in the first place (this update script includes a format /system command before it starts going. It's well worth taking a glance at the script, at least, to see what all it's doing.)

I've rebooted and via noogie blown in SU and busybox. I think that with those installed I am good to go, and I can sideload other apps that I need. I've never had decent market visibility working reliably on this unit, so trying to hack in the market at the cost of a rebooting device isn't that interesting for me.

I am noticing the screen speed and the increased contrast just in the few hours I've been looking into this, which is why I am proceeding and not simply restoring from a backup.

Something I just caught - in my old touchnooter config, in build prop, I have these lines:

ro.sf.lcd_density.xdpi=167

ro.sf.lcd_density.ydpi=167

Doesn't having a nonstandard dpi value play hell with the Market? Could this be why so many folks struggle with market visibility, even after getting the market installed?