Hi,
After a lot of mucking about, interrupted by the Mar 2 update, I have my Vox rooted and the Marketplace (now Google Play) app installed. However apps I would like to install (like my bank's mobile app) will not install because Google says it doesn't recognize the K080 device.

Is this fixable? Can the Vox mask it's ID and look like some other device?

Or is this as good as it gets? It was a lot of work to get this far and then find out I still can't get the apps I want.

You can sideload the app from another android device. But clearly the app is claiming it has some hardware requirement that the vox does not support (gps? I don't know, you didn't say what the app is)

I did say it was my banks mobile app. After a ton of searching for the app (most links simply end up pointing back to the Android Marketplace) I did manage to find it at www.1mobile.com. It loads and runs just fine since all it needs is web access.

So why is Google Play so fussy? I've downloaded other apps from it, including paid apps, so why is it so totally hung up on this device ID being 'known' or not.

It effectively won't even tell me it exists, even though I KNOW it's there. It is rather a ludicrous position to take. If it somehow is not compatible with my device, it just won't install/work, why not let me try and suffer the consequences?

And maybe before downloading bank apps from shady places (basically everything else than your bank) think about what a person who knows how to decompile and recompile an apk could do with all your bank data.

There are Vox compatible Jellybean libs, the AMD Z430 is simply an Adreno 200, and ZTE have released Jellybean 4.2 for their N880E, which uses an Adreno 200 GPU.

If the current kernel is 2G VMSPLIT, it will be incompatible with AOSP or CyanogenMOD or MIUI or AOKP or Paranoid Android, as they all uses 3G VMSPLIT.
Has anyone grabbed the kernel config from /proc/config.gz yet?

The MfgTool is a manufacturing tool from Freescale that runs under Windows. It is designed to program firmware to i.MX boards for mass production. Boards are connected via USB and execute the USB/UART (Serial downloader) mode.

It is possible to format the /data and /cache partitions or update software based on a update script using recovery mode as follows:
Prepare for all android source code that assumed to be saved in ~/myandroid directory.
Prepare for ADB over USB. make sure that ADB over USB is ok. USB cable is connected. Refer to ADB over USB section for more information.
Connect the UART to the PC and open a terminal to check for printed messages
Enter the recovery by manual
Only works on MX53_SMD: Press "VOLUME -" and "Power" , you can enter Recovery mode.
Developer notes:
to support your board or MX51 platform, you can reference this patch in uboot-imx.git: