[ROM 1.2] UPDATED - OS 1.2 su / root / adb / "Unknown Sources" APK Enabler - Nook Color Android Development

Coming soon: Full access to the 2.x market.
Progress is being made to bring the new market to the NC (less the FC permissions or APK signature issues.) Check posts towards the end of this thread for more info.
UPDATE - Version 1.1a - 4/27 - NOW WITH MORE ROOT!
I'm happy to announce that I now have a much improved version of apk-enabler all packaged up and ready to install. This version will work much better than the last one, and should provide much better application compatibility.
Version 1.1a:
Major update...
* Added Edify code to clean up old versions before installing or re-installing (either version)
* Updated su (version 2.3.6.1 - thanks dascud)
* Updated and relocated Superuser.apk (now lives in /data/app so updates will not complian about it being a "system application" anymore.)
* Added Zeam 2.9.2 to /data/app
* Added NookColorTools to /data/app
* Added SoftKeys 3.06 to /data/app (in case anyone needs this - some apps don't display the nook status bar properly.)
* Added latest busybox binary to /system/bin
* Added a crapload of symlinks to busybox functions in /system/xbin. Almost everything works now (grep, mount, etc) without having to run through busybox or toolbox. (thanks RileyGrant)
* I have attempted to perma-enable adb by setting the adb_enabled value in /data/data/com.android.providers.settings/databases/settings.db. Unfortunately it appears that this setting is ignored - at least when auto mounting is enabled. See notes below.
Notes:
Now that we have busybox and a current version of su, we now have what resembles a "normal" android shell environment. More apps should work with the updates, and we can now get a shell (then su) via adb. You can also run the Android Termainl app and su from there.
Also, since Zeam and SoftKeys now baked in, the first boot will now ask for your preference of default launchers (Home, SoftKeys, or Zeam.)
To get ADB working, you need to update your drivers, and play with settings in NookColorTools (development section) to enable USB debugging.
I have validated this install via a fresh install and over-top of existing installs. The only requirement is that the Nook has been turned on and registered. You can flash this over older versions, the script cleans up cruft from prior runs before installation.
Original Post:
So I went about fooling around with the stock 1.2 ROM, and like many I was frustrated by the lack of certain apps in the Nook app store. So here's a little work-around until we get a properly rooted solution in place:
What this hack does:
* Updates the SQLite Settings Database (data/data/com.android.providers.settings/databases/settings.db) with a hacked version, enabling the install_non_market_apps and adb_enabled settings.
* Installs a version of "su" in /bin and /xbin.
* Installs busybox to /system/bin and sets symlinks for most shell commands in /system/xbin
* Installs SuperUser.apk, SoftKeys_3.06.apk, NookColorTools_0.2.apk, and zeam-2.9.2.apk to /data/app (you may uninstall any of these if you wish.)
* With these in place, the stock browser (and other Market apps) are fully capable of downloading, launching, and installing .apk files of your choosing.
Is this safe? What if I brick my Nook?
The Nook Color bootloader will boot anything you throw at it. There are no signature checks anywhere, and even their own code is signed using test keys. If you get a bad flash or whatever, you can always boot your Clockwork SD card and restore from there. Remember - this is not a phone - there is no subsidy or baseband to protect. So, no there's no S-ON, locked boot loader, or any of that other silly crap the carriers do to screw their customers. You can flash forwards, backwards, sideways, whatever you want, as long as you can put it on an SD card.
Overall, this is no more dangerous than running a stock android device with the "Unknown Sources" setting enabled. Nothing is happening yet that is uncharacteristic of a "standard", vanilla android device.
That said, you should probably make a backup while you are running Clockwork, just to be on the extra-safe-side.
So, is this a full ROM that I can use to flash the 1.2 update?
No. This is a stand-alone update to 1.2 that overwrites one file and adds two others. You need to have 1.2 up and running in order to use this.
How to install...
First, you must have a microSD card already flashed with ClockworkMod. I'm not getting into that, you can find a good guide in this post:
http://forum.xda-developers.com/showthread.php?t=987735
(thanks fpga_guy)
NOTE - THIS WILL ERASE YOUR SD CARD - SO YOU MIGHT WANT TO PICK UP A CHEAP 2GB CARD FOR THIS.
* Once you have Clockwork set up, drop the attached zip in the root directory, and reboot your Nook Color. Once Clockwork is booted:
* Select "install zip from sdcard", then "choose zip from sdcard"
* Select "Yes - Install apk-enabler-1-1a-signed.zip". The install process will begin promptly.
* Once flashed, you will be prompted to Reboot,
* The Nook OS will almost certainly crash on the first reboot - I'm not sure why as of yet... If it does, hold the power button until the Nook powers off completely, then turn it back on. It should continue to boot normally after this point.
* Once you are back up, you can use the browser to download and run .APK files from anywhere. Some apps do not work, others do. Fortunately for us, Superuser.apk is one that does
As for launchers, you will not see your installed apps in the Extras area of the stock launcher - B&N is doing something shady here... Instead, you will need to install another Launcher. Zeam seems to work well, while ADW doesn't.
Once Zeam is installed, you can hit the "Home" button and select it as your Launcher (permanantly, if you like...) This is where you'll see all of your downloaded apps.
I have attached the flashable zip file, plus links to SuperUser.apk and Zeam. Use the built-in Nook browser to install both of these to your device. Once you download an APK file, tap the notificaiton in the lower left corner and select "Package Installer." The usual Android install screen will appear, and you know what to do from there...
What's not working?
Probably lots of things. I know ADW doesn't work, and the open source Terminal emulator doesn't either... Superuser.apk detects SU, which is a good thing. It isn't "full root access" until I hack /etc/fstab to mount /system r/w (probably tomorrow.) B&N hacked up the frameworks pretty bad for this, so there are probably lots of issues with non-market apps. However, this should open the door to someone willing to port Nookie Froyo (or something similar) over to the stock 1.2 ROM.
Credit where credit is due:
First, thanks to everyone on XDA, the official Nook forum, CyanogenMod, NookDevs, some kind folks on IRC who helped me sort out the partition layout, some helpful folks in this thread, and probably 20 others that I'm forgetting. This would not have been possible without your help.
Where do we go from here?
I suspect we will have something more like Autonooter in a day or so... However, this is a fully usable solution for the time being. You have su, busybox, Superuser, SoftKeys, and a Launcher.
Also, someone needs to look into getting side-loaded apps onto the home-screen and/or into the Extras screen. My fear is that B&N is checking signatures there - but hopefully I'm wrong on that one....
Version 1.1a: apk-enabler-1-1a-signed.zip (1.28mb)
md5sum: 65267cf3314d7fae829881970d70b444
http://www.mediafire.com/?bb7o66282bqfp6q

---

Apps known to work:
Superuser
Zeam
SoftKeys
Amazon App Store for Android (works beautifully)
Amazon Mobile
Collapse (today's free game on Amazon)
Kindle Reader
File Manager
ES file explorer
Pulse (with widgets)
Facebook
Evernote
Remember The Milk
Subsonic
WP Clock - Live Wallpapers are enabled by default - the Google Maps and WP Clock live wallpapers appear in the stock Nook Home settings
Free Dictionary
TV.com
TuneIn Radio
Winamp
LastPass
Xmarks
Dolphin
DocumentsToGo
cVolume
FancyWidget
Google Voice
ReadItLater
Button Savior
Dropbox
Adobe Reader
TerminalEmulator
Apps known not to work:
Any version of GApps. Especially those packaged for Gingerbread. This is a B&N issue.
ADWLauncher
aldiko (via kingsjack)
other Input Method (via kingsjack)
appmonster (via kingsjack)
gscript lite (via kingsjack)
GApps don't work because framework.jar needs to be ported from another release. B&N broke it.
Alternative keyboards and things like that will probably break (again, due to dependancies that have been broken by B&N.)
Fortunately, B&N left enough of the package installer intact to allow us to get this far.
(feel free to add to this list, I'll only test what I personally plan to use.)

---

Thanks for getting off market working
Sent from my SPH-M910 using XDA App

---

Zero to sixty in no time flat. Gracias Senor, now I can dual boot this and the incredibly speedy cm7 builds and have the best eReader on the market and a super great 7 inch tablet to boot.

---

can i use cm gapps-gb-20110307-signed in stock 1.2 after root?

---

kingsjack said:
can i use cm gapps-gb-20110307-signed in stock 1.2 after root?
Click to expand...
Click to collapse
No, that's the Gingerbread version. If you can find one for Froyo - who knows, it might just work

---

HamNCheese said:
No, that's the Gingerbread version. If you can find one for Froyo - who knows, it might just work
Click to expand...
Click to collapse
thank! now i cna install most apk in my nc.
but ... when i use root.explorer, i find superuser isn't work.. didn't root in my nc.
1. install apk.enabler.zip by ClockworkMod, is work. i can install apk by brower
2. install Superuser and zeam & rootexplorer, is work, and i can use rootexplorer to install other apk, but haven't root.

---

kingsjack said:
thank! now i cna install most apk in my nc.
but ... when i use root.explorer, i find superuser isn't work.. didn't root in my nc.
1. install apk.enabler.zip by ClockworkMod, is work. i can install apk by brower
2. install Superuser and zeam & rootexplorer, is work, and i can use rootexplorer to install other apk, but haven't root.
Click to expand...
Click to collapse
You're welcome. I'll look into Root Explorer - I'm not sure if it's a root issue or an issue with that software. Superuser thinks it has root, so I would think other apps would as well.
FYI /system is not mounted as read/write yet - perhaps that is what Root Explorer is complaining about?

---

HamNCheese said:
You're welcome. I'll look into Root Explorer - I'm not sure if it's a root issue or an issue with that software. Superuser thinks it has root, so I would think other apps would as well.
FYI /system is not mounted as read/write yet - perhaps that is what Root Explorer is complaining about?
Click to expand...
Click to collapse
without this Options

---

kingsjack said:
without this Options
Click to expand...
Click to collapse
Right. As I mentioned, I need to fix fstab to mount everything with read/write permissions (which I plan to do tomorrow.) This is really more of a work-around to get apps on the device. We will gain better control of it over time.

---

HamNCheese said:
Right. As I mentioned, I need to fix fstab to mount everything with read/write permissions (which I plan to do tomorrow.) This is really more of a work-around to get apps on the device. We will gain better control of it over time.
Click to expand...
Click to collapse
thank u work

---

I'm guessing, very much likely, that you didn't include a Superuser.apk into /system/app which allows Root Explorer to request use of su in xbin. I'm going to try and get an AN version going for 1.2 in a day or two.

---

GabrialDestruir said:
I'm guessing, very much likely, that you didn't include a Superuser.apk into /system/app which allows Root Explorer to request use of su in xbin. I'm going to try and get an AN version going for 1.2 in a day or two.
Click to expand...
Click to collapse
I didn't include it because it wasn't necessary. su is present, Superuser in apk form works. The only thing missing is to re-mount everything as rwxrwx---. That would satisfy the root explorer requirement without having to go the full autonooter route. For now, anwyay....
What you describe is simply a tweak to /etc/fsatb and possibly some changes here and there in some init scripts. It shouldn't be a difficult update, re-mounting file-systems isn't exactly the hardest thing to do in Linux.
The big headline here is "load apps from untrusted sources" - something that the Nook Color is physically incapable of doing out-of-the-box. In fact, their plan is exactly the opposite. Entangle the user with app purchases that they can't get anywhere else, and cannot transfer in or out of the Nook ecosystem. That problem is solved for now, and it should do what 90% of users want right out of the box.
We can discuss the next phase after evaluating the changes to frameworks and whatnot that will get Gapps and other crucial stuff up and running - that will prove to be a more difficult task than simply breaking in to the stock system. Judging by work that was done for previous iterations of Autonooter, there are enough framework changes that it's going to take some time to work out the details.
BTW, if anyone on that team would like to share information, please contact me and I'll see what I can do to help.

---

If there's no R/w toggle it means somethings wrong with Root Explorer, you should look into that problem as opposed to just fixing it by remounting system in init.rc this is not a good fix for something like this and shouldn't be acceptable. There's a reason the toggles built in and that's to help protect the /system folder.

---

GabrialDestruir said:
If there's no R/w toggle it means somethings wrong with Root Explorer, you should look into that problem as opposed to just fixing it by remounting system in init.rc this is not a good fix for something like this and shouldn't be acceptable. There's a reason the toggles built in and that's to help protect the /system folder.
Click to expand...
Click to collapse
Hmmmmm.....guess I'll have to spring for root explorer and dig through logcat to see what's going on. It could totally be some goofy B&N thing that's screwey on this one device. More after the break....

---

HamNCheese said:
Apps known to work:
Superuser
Zeam
Amazon App Store for Android (works beautifully)
Amazon Mobile
Collapse (today's free game on Amazon)
Kindle Reader
File Manager
Apps known not to work:
ADWLauncher
TerminalEmulator
(feel free to add to this list, I'll only test what I personally plan to use.)
Click to expand...
Click to collapse
Please explain how you got amazon appstore on there. I signed in on mazon had it send me the link on the nook to download it which i did. When i clicked on it brought up chice to run with app installer or package installer of which one gave me a parse error and the other did nothing.
Any ideas?

---

So, is this a full rom that I can flash my 1.1 nook into 1.2?

---

HamNCheese said:
BTW, if anyone on that team would like to share information, please contact me and I'll see what I can do to help.
Click to expand...
Click to collapse
Hint.. They already have in this thread.

---

HamNCheese said:
I didn't include it because it wasn't necessary. su is present, Superuser in apk form works. The only thing missing is to re-mount everything as rwxrwx---. That would satisfy the root explorer requirement without having to go the full autonooter route. For now, anwyay....[/B][/B][/I]
Click to expand...
Click to collapse
installing rom manager and running fix permissions should set all the right files to rwxrwx--- shouldnt it? i havent installed the update cuz im happy with cm7 so i cant test it..
Sent from my NookColor using Tapatalk

---

Good work Ham. The apps used to show after rebooting under the Extras section(Now called Apps), they are not now after the framework butchering they did. However, I installed Applanet and all I had to do was a search on the device and there it was. It launched fine and downloaded apps no issue.