[General Questions and Answers] jefftheworld:
Okay, so I just got my Vox today and I've had some success with rooting it, installing busybox and removing some of the junk that's preinstalled.

By using adbwireless I got around the fact that I couldn't get any adb drivers working. Once you're rooted simply install adbwireless.apk (a version I've tested as working with the vox is attached below) and give it root permission when it asks. Then open it and enable it and it'll tell you the exact command to use to connect via adb.

There are plenty of guides on installing adb (and getting your path variable set for it). A simple search on XDA should suffice for that, it's dead easy anyway. I won't cover that, I'll assume you have the SDK installed and that you have adb installed and working.

Now, let's start using adb, shall we?

So, adbwireless will spit out a command for you. Something to the effect of:

adb connect 192.168.1.2:5555

If you type the command it gives you, adb will connect to the device. You can then check to see if it's connected by typing:

adb devices

This should show your Vox as connected by echoing the IP address and to grab a shell from your device just type:

adb shell

Now, you can do some fun stuff. Want to get rid of some of those preinstalled apps that you can't remove?

To do this, you'll probably have to remount your /system partition as read-write. First, type su to gain root and then type mount to list all of your Vox's mount information. You'll see a series of lines in the following format:

/mount_point /directory filesystem flags other_stuff

The one you want probably looks like:

/dev/block/mmcblk0p1 /system ext4 ro,relatime,barrier=1,data=ordered 0 0

You can see by the "ro" flag that it's currently mounted as read-only, so you won't be able to delete or modify anything on it. Luckily it's easy to remount it as read-write:

mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system

Now if you check the mount info again you'll see it listed with the "rw" flag instead of the "ro" flag and TA-DA! You can now easily delete those annoying built-in apps. They're stored in the /system/app directory so just cd over there and use ls to see what all is in there. A rm command can delete apps and a mv command can disable them without deleting them by changing their filename or moving them somewhere else.

I've also been looking into getting two things working on the Vox:

A) The google framework, market, etc.

B) CyanogenMod

To speak to the first; it installs successfully and will run but gives an error stating it is unable to connect to google's servers. I reckon that's not the case, either another app is interfering or there's some other error going on, but I'm pretty sure nothing is actively blocking the connection and I know I have a connection. I'll certainly try to experiment with removing certain Kobo services to see if I can't get it work but I'm afraid it might be part of the ROM build itself.

As for CyanogenMod, there's already some buzz around their forums. I've been looking at seeing if I can manage a port myself and I'm optimistic but cautious. If anyone has any information on the topic of flashing a recovery image on the Vox it would be greatly appreciated.

EDIT: Dump of some stuff I've been looking at.

There are several files that are obviously added by Kobo, they are:

Kobo.apk - Kobo App

KoboOsProvider.apk - Kobo Os Storage

KoboTimeTracker.apk - KobobooksLauncher

KobobooksLauncher.apk -KoboTimeTrack

The first is the Kobo app itself, which is far smaller than the regular Kobo app - 1.41MB as opposed to 6.27MB - and it seems to be supported by several small services like Kobobooks Launcher and KoboTimeTrack.

I want to see which of those can be removed without catastrophe and whether or not that solves the problem of using the google apps.