Archive

Posts Tagged ‘firmware’

How-to Upgrade Firmware on AllWinner A31 mini PCs

May 18th, 2013 1 comment

I’ve just received a mini PC powered by AllWinner A31, and I had to (re-)install the firmware, so I’ll explain the steps I followed in this post. The procedure is for CS868 mini PC, but it should be similar for all Android HDMI TV dongles, and media players based on AllWinner A20 or A31.The procedure below only works in Windows, and has been tested in Windows XP. I’ll mention a possible method in Linux at the end of the post.

  1. Download the latest CS868 firmware and tools, and extract “cs868 firmware and update tool 20130507.rar” file
  2. Download PhoenixUSBPro tool in English, and extract This is optional as the Chinese version is included in rar file above.
  3. Double-click on PhoenixUSBPro/PhoenixUSBPro.exe to start the programPhoenixUSBPro_English
  4. Click on Update to upgrade the tool to the latest version if need be.
  5. Click on Key to to load the key file (AW_LCTOOLS.key), on Image to load the firmware file (sun6i_android_fiber-onda809q9_20130507_V2.0_media_ck_288.img), and click on Start.
  6. Now connect the microUSB to USB cable to the OTG port of your device, use a paper clip or tweezers to press the recovery button, and connect the other end of the USB cable to your Windows PC. Release the recovery button once you hear Windows has detected a new device.
    CS868_Recovery
  7. Do not let Windows search for a driver online, but instead set the search path to PhoenixUSBPro/USBDriver, as shown below.
    PhoenixUSBPro_Driver
  8. Click on Next, let the driver installation complete, and the firmware update should start.
    PhoenixUSBPro_Firmware_Update_In_Progress
  9. Wait a few minutes until the firmware upgrade completes. It took 3 minutes 38 seconds to upgrade my device.

At the beginning I had issues in Windows, because, as I found out later, my Windows file system was encrypted, so I also gave it a try in Linux using Livesuit, but unsuccessfully. Livesuit Linux refuses to load the img file provided. The most likely reason is that Livesuit and PhoenixUSBPro file formats are different (and Livesuit did not need to key file), or  the current version of Livesuit may only work with AllWinner A10 or Cubieboard. I’m sure somebody will correct me on that.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

New Tronmart Prometheus Firmware Fixes XBMC Audio/Video Sync, Adds DLNA and Smartphone Control App

May 17th, 2013 No comments

A new firmware is now available for Tronsmart Prometheus with the following key changes:

  • New Android 4.2
  • XBMC audio/video sync bug fix
  • DLNA support
  • Smartphone control function
  • Internal storage for apps increased to 2GB

In order to use the smartphone control function, you need to download and install RC_Client.apk into your Android smartphone or tablet, and run this app to control your Prometheus. I haven’t tried myself, and they did not provide detail, so I don’t know whether functionalities are similar to DroidMote.

To update your device if It’s already running the previous Android 4.2 beta firmware:

  1. Download and extract Tronsmart Prometheus new stock firmware.zip.  It would be really nice if they could just provide version numbers for firmware releases.
  2. Open the download folder, copy the 5 files in the root folder of an SD card, and insert it into your device.
  3. Use a paper clip to press and hold the reset key at back  of the box, and power the device;
  4. Wait for blue LED to flash 3 times, release reset key, and wait for the system to automatically upgrade. Please note there’s no video output during the upgrade.
  5. Upon completion, the device will be reboot into the new firmware.
  6. I’m not sure why it’s not part of the firmware, but you also have to download, and install the updated version XBMC:  Tronsmart Prometheus-xbmcapp-20130507-debug.apk.

If you’ve bought a new device it will come with Android 4.1, and to successfully complete the firmware upgrade, you’ll have to repeat steps 1 to 5, before installing XBMC.

Future firmware releases will be available in Tronsmart’s Download page.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

How to Flash Firmware to Rockchip RK3188 HDMI TV Sticks

April 27th, 2013 1 comment

Yesterday, I’ve received MK908 mini PC featuring Rockchip RK3188, and a new firmware is available, so before further testing I’ll flash the firmware to the device basically using the instructions from Geekbuying. This method use standard Rockchip tools, so it should work for any RK3188 devices.

But first a little rant. Those instructions only work on Windows operating systems, so if you’re using Linux or Mac, you’re out of luck until you find a Windows PC, or launch Windows in a virtual machine. This method should just be used in case the device can’t boot, or you have serious issue with the device firmware, but it is also used for firmware upgrade for Rockchip mini PCs. This is just wrong. Typical users should not be asked to install software and drivers, press the recovery button, just to upgrade their firmware. The best very way would be OTA updates, but maybe this is asking too much. The alternative would be to just copy some files to a micro SD card, insert it in the mini PC, boot the device, and wait for the firmware to complete. This method could also avoid to complete wipe out your settings  and installed applications, although apps like Titanium Backup can help restore those after a full firmware update.

The steps to install firmware to RK3188 based mini PCs, in this case MK908, are as follows:

    1. Download RkBatchTool 1.6 (password: GEEKBUYING.COM), the Windows only tool to flash firmware to RK3xxx devices, as well as RockUSB drivers v3.5, the USB drivers for Windows 2000/XP/vista/7/8.
    2. Download the firmware file for your device. For MK908: update_mk908_100j1101_6210.rar
    3. Uncompress those 3 files in a directory in a Windows PC.
    4. Get the mini USB to USB cable, and connect it to your Windows PC. Now look at the back of MK908 with the HDMI connector pointing upwards, you should see 2 small holes at the top of the devices. The right hole is the power LED, and the left hole, the recovery button. Press the recovery button with a paper clip, and at the same time insert the other end of the USB cable into the OTG port of your device. Wait a few seconds before releasing the recovery button, and your windows PC should start installing the drivers automatically, but you don’t want that, so don’t let it install the drivers now, and move to the next step.

      MK908 Recovery Button (Left) and OTG Port (Right)

      MK908 Recovery Button (Left) and OTG Port (Right)

    5. There are different procedures depending on the version of Windows, but you should point the drivers installer to Rockusb_v3.5/Rockusb_v3.5/Rockusb/x86 (32-bit Windows) or Rockusb_v3.5/Rockusb_v3.5/Rockusb/x64 (64-bit Windows) and finally select the directory corresponding to your Windows version. Click OK or Next to complete the installation. In Windows XP, you should see “Class for rockusb devices->Rockusb Device” in the Device Manager.
    6. Now go to GEEKBUYING_Rockchip_Batch_Tool_v1.6/Rockchip_Batch_Tool_v1.6 and double click on RKBatchTool.exe to launch the tool.
    7. Click on “…” at the top right of the window, select the firmware file (e.g. update_mk908_100j1101_6210.img), and RKBatchTool should now indicate one device is connected by showing a green square in the “Connected Devices” section of the windows.
    8. Click on “Restore” (and not Update) to flash the firmware. It will take a few minutes (It took 1204 seconds, or about 20 minutes). Once it’s finished, the device will reboot, Windows will install the adb drivers, and you should see the windows below.RKBatchTool_MK908I’ve included the full log below for your reference:
      11:34:08 674 Rockchip Batch Tool v1.6.8.1 start run
      11:40:35 799 Rockchip Batch Tool v1.6.8.1 start run
      11:40:50 236 **********Restore Start Total**********
      11:40:50 267 Test Device Start
      11:40:50 283 Test Device Success
      11:40:50 299 Lowerformat Device Start
      11:40:59 346 Lowerformat Device Success
      11:40:59 377 Test Device Start
      11:40:59 408 Test Device Success
      11:40:59 424 Check Chip Start
      11:40:59 439 Check Chip Success
      11:40:59 455 Get FlashInfo Start
      11:40:59 471 INFO:FlashInfo: 0 0 0 1 0 10 10 28 2A 4 1
      11:40:59 502 Get FlashInfo Success
      11:40:59 517 Prepare IDB Start
      11:40:59 533 INFO:CS(1) (8192MB) (MICRON)
      11:40:59 580 Prepare IDB Success
      11:40:59 611 Download IDB Start
      11:41:00 299 Download IDB Success
      11:41:00 330 Reset Device Start
      11:41:01 346 Reset Device Success
      11:41:01 361 Wait For Loader Start
      11:41:02 846 Wait For Loader Success
      11:41:02 908 Test Device Start
      11:41:02 955 Test Device Success
      11:41:02 971 Download Firmware Start
      12:00:51 736 Download Firmware Success
      12:00:51 767 Reset Device Start
      12:00:52 783 Reset Device Success
      12:00:55 111 **********Restore Done Success Fail Time <1204828>ms**********
    9. Connect your device to the TV and enjoy!

I first tried the procedure in a Windows 7 virtual machine running in Ubuntu 12.04 64-bit, I could detect the device 2207:310b, and start the firmware, but I pressed the wrong button “Upgrade” and it failed. Subsequently Linux failed to detect the device, even after closing Virtual Box, so I switched to a Windows XP netbook to complete the procedure.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Preliminary Ubuntu 12.04 RootFS for GK802/HI802 mini PC

April 5th, 2013 No comments

After releasing a pretty good Ubuntu 11.10 image with both VPU and GPU acceleration for Freescale i.MX6 based HDMI dongles last month, Jasbir (aka jas-hacks) has released an Ubuntu 12.04 image with GPU support thanks to the help of Octavio (Yocto Project contributor), and Wi-Fi support. It’s possible to select Unity 2D or Xubuntu desktop, and Chromium and Neverball, a 3D ball game, are part of the image. There’s still more work however, as VPU (Video Processing Unit) support is work in progress, Bluetooth does not work yet, and OpenGL ES test programs such as glmark2-es2 or es2gears do not work properly with Xubuntu, even though they do work fine with Unity 2D.

Jasbir uploaded a video showing Neverball 3D game in GK802, and it works pretty good, although the framerate does not seem optimal for now.

If you want to give this image a try, install GK802 Ubuntu 11.10 image first, and follow the instructions below:

  • Download Ubuntu 12.04 rootfs for i.MX6 dongles:
    cd ~/Downloads
    wget http://dl.miniand.com/jas-hacks/gk802/linaro_12_04_gpu.tar.gz
  • Insert the micro SD card into a Linux PC, delete the existing rootfs from the Oneiric image, and extract the new rootfs:
    cd <sd card mount point>/ubuntu
    sudo rm -rf *
    sudo tar xzvf ~/Downloads/linaro_12_04_gpu.tar.gz
    sync
  • Remove micro SD card, insert it in the internal micro SD slot for your mini PC, and power the device up to start Ubuntu 12.04.

If you have questions about the image and/or want to participate in development, feel free to join imx6-dongle developers’ community, and contact developers on #imx6-dongle IRC channel or imx6-dongle mailing list.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Droid Stick A2 mini PC Recovery with AMLogic’s Hardware Flash Tool

March 28th, 2013 1 comment

In some circumstances, for example by installing the wrong firmware or doing something wrong by playing god (as a root user), it’s possible to brick your device. This happened to me with one of my Droid Stick A2 mini PCs based on AMLogic AML8726-MX. I changed some files in /system/etc/permissions directory, lost Wi-Fi access, and even  replacing my changes with the backup files would not solve the problem. It also changed some permissions in the system, and it was not possible to restore the firmware the usual way. At the end of last month, dbtablets left a comment with download links to “Amlogic USB Burning tool”, but  I only decided to give it a try today, and after some efforts I was successful. Just make sure you only use this method as last resort, i.e. a standard firmware upgrade does not work, and you’re about to throw your device in the trash bin, because you could brick your device if the “resources” file is not for your hardware. The same method should work with other AMLogic AML8726-XX devices but you would have to get the correct resources file from the manufacturer.

The tools are only available for Windows XP or 7. Here are the steps to follow (in theory):

  1. Download “Hardware flash.rar” which contains the burning tool, the USB drivers, and the “resources” file, a zip file with the SPL, the bootloader, uImage and update.zip, which is specific to Droid Stick A2. There’s also a word file with instructions.
  2. You’ll need to short two pins on the board, so open Droid Stick A2 casing to access the board.
  3. Extract Hardware flash.rar in a directory of your choice, enter Hardware Flash/Hardware flash of amlogic directory, and click on ImageBurnTool.exe to start the program.AmlogicBurningTool
  4. AMlogic_burning_tool_load_resourcesIn the top menu click on the first item on the left drop down menu to load the resources file. I had to do this in a netbook with 1024×600 resolution, and following the great “flash tools” tradition, the window cannot be resized, so I could not see the top menu. In that case, simply press “Alt” then “Down Arrow” and “Enter” to access the popup menu to load resources.zip
  5. Connect the mini USB to USB cable to your Windows PC but not to Droid Stick A2 yet, short TP14 as shown below, and only then connect the mini USB cable to start your device. N.B.: Some other devices have a recovery button so that you don’t need to open the case.
    Droid_Stick_A2_Recover_TP14
  6. Windows should then detect a new device (M6-CHIP), and ask you to install the drivers. To be honest, I’m not sure what you have to do at this point (as I did this many times), but I think you can just press cancel, as the burning tool will install the drivers automatically (in theory) and you should eventually see a “WorldCup device” in the hardware manager.
  7. wipe_out_chinesePort 1 line should show the device is connected in the burning tool. Check the option to erase the flash (as shown on the right), and click on the start button (开始) on the top right of the window to start erasing the flash. For me the process connected to both Port 1 and Port 3, it failed on Port1, but was eventually successfully on Port 3.
  8. Disconnect and reconnect the USB cable from your PC, it should start upgrading the firmware automatically, and having a while you should see “Success” in the window. Again, for me Port 1 failed, but Port 3 worked OK.

Once this is done, connect Droid Stick A2 to your HDMI TV, and it should start normally with a relatively recent firmware (30th of January 2013). Apparently the method above worked just fine for some people, but it did not work for me, as the system refused to install the drivers (Step 6). I tried in a virtual machine Windows 7, and a netbook running Windows XP SP3, and the drivers refused to install either automatically thru the burning tool, or manually with the drivers in Hardware Flash/Hardware flash of amlogic/AmlogicusbBurningdriver directory. So I decided to look for alternative drivers, and found another version of the burning tool in Slatedroid. So I download the file (AML_Flash_tool.rar), extracted it, and instead of starting ImageBurnTool.exe, I clicked on ImageBurnTool-sp3.exe as my netbook runs Windows XP SP3. AML_Flash_tool.rar only contains the burning tool, so I used resources.zip for Droid Stick A2 from the first rar file. The program managed to install the “M6-CHIP” drivers automatically, but then the procedure would fail during steps 7 or 8, as SPL would not load for some unknown reasons. After several retries however, the procedure went through successfully (don’t ask me why) and I could recover my device, although as mentioned previously it ended with an error on Port 1, but successfully on Port 3.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Ubuntu 11.10 Image for Hi802 / GK802 is Now Available for Download

March 25th, 2013 21 comments

About 2 weeks ago, Jasbir released an Ubuntu 11.10 image and installation instructions for GK802 and Hi802 mini PCs based on Freescale i.MX6. I could only find time to give it try yesterday and today. I’ll provide the steps I followed to install the image, and my quick first impressions of the stability and performance of this image.

Totem (1080p Video) + Firefox + es2gears + htop running in Ubuntu 11.10 on Hi802 (Click to Enlarge)

Totem (1080p Video) + Firefox + es2gears + htop running in Ubuntu 11.10 on Hi802 (Click to Enlarge)

Installation Instructions

I mainly followed the instructions provided by Jasbir, and run GParted to increased the partition size on my micro SD card. The image is for a 8 GB micro SD, but those instructions should work on 4GB SD card and greater, as the rootfs partition is only 3GB large.

  1. Download the Ubuntu 11.10 image, uboot, as well as the kernel image and modules in a Linux PC:
    wget http://dl.miniand.com/jas-hacks/gk802/ubuntu_gk802.img.gz
    wget http://dl.miniand.com/jas-hacks/gk802/u-boot.imx
    wget http://dl.miniand.com/jas-hacks/gk802/uImage_3.0.35-0269_cpu_freq
    wget http://dl.miniand.com/jas-hacks/gk802/modules_3.0.35-02695.tar
  2. Copy the image, uboot and the kernel to the micro SD card by typing the commands below:
    gzip -d ubuntu_gk802.img.gz
    sudo dd if=ubuntu_gk802.img of=/dev/<sd_device>
    sudo dd if=u-boot.imx bs=1k seek=1 of=/dev/<sd_device> && sync
    sudo dd if=uImage_3.0.35-0269_cpu_freq of=/dev/<sd_drive> bs=1048576 seek=1 && sudo sync

    Replace /dev/<sd_device> by your actual device. In my case: /dev/sdc. N.B. My 8 GB micro SD is slightly smaller than Jasbir’s image so dd failed with “No space left on device“, but it’s not an issue, as there’s no critical data at the end of the image.

  3. Remove the micro SD from your PC, and reinsert it to automatically mount the rootfs. If it does not automatically mount, you may need to mount it manually (e.g. sudo mount -t vfat /dev/sdc1 /media/ubuntu)
  4. Copy the kernel modules to the rootfs. Replace <sd_mount_pt> by your micro SD mount point (e.g. /media/ubuntu):
    tar xvf modules_3.0.35-02695.tar
    sudo cp -r modules/3.0.35-02695-ga09806b-dirty <sd_mount_pt>/lib/modules
  5. Unmount the microSD, and run
    gparted /dev/<sd_device> to resize the root filesystem, as shown below

    Ubuntu GK802 gparted

    GParted failed to run e2fsck properly for an unknown reason, possibly because my micro SD is smaller than the provided image, so I slightly reduced the size of the partition, and it worked OK.

  6. Exit GParted, remove the micro SD from your PC to insert it in the internal microSD slot of your  Hi802 / GK802 mini PC.

Running Ubuntu 11.10 in Hi802

Since this is a development release, and the boot may fail with your configuration, you’d better connect a USB to TTL board to your device to access the serial console. During my first boot, I got to the Ubuntu desktop on my HDMI display (720p), but my USB mouse or keyboard would not work. I’d get no messages (via dmesg) at all when I connected a USB hub, and upon connecting my mouse or keyboard directly in Hi802 USB port, I’d get the message below in the serial console:

usb 1-1: device descriptor read/64, error -71

rzk2 advised me to try another power supply on #imx6-dongle IRC. After my Droid Stick A2 5V/2A power supply, I tried a 5V/1.2A Nokia power supply, but the device would just keep rebooting, and finally I found another 5V/2A that make the device, my USB hub, mouse, keyboard and me happy :)

I could setup Wi-Fi very easily via Ubuntu user interface. As with other boards running Ubuntu + Unity from an SD card, the system is not super responsive but still (sort of) usable. To test the GPU and 2D/3D acceleration, I ran both es2gears and glmark2-es2.

es2gears renders at about 58 fps.

es2gears
EGL_VERSION = 1.4
vertex shader info:
fragment shader info:
info:
821 frames in 5.0 seconds = 164.069 FPS
818 frames in 5.1 seconds = 161.916 FPS
767 frames in 5.1 seconds = 149.893 FPS
511 frames in 5.0 seconds = 101.773 FPS
293 frames in 5.0 seconds = 58.495 FPS
292 frames in 5.0 seconds = 58.295 FPS
292 frames in 5.0 seconds = 58.272 FPS
292 frames in 5.0 seconds = 58.318 FPS
291 frames in 5.0 seconds = 58.107 FPS
293 frames in 5.0 seconds = 58.483 FPS
291 frames in 5.0 seconds = 58.142 FPS

and glmark2-es2 works, but gets a score between 12 and 14, which is quite lower than the score (54) I got on ODROID-X with Ubuntu 12.11 using the same resolution. A lower score was expected, but the difference is quite large, although I’m not sure whether it’s OK to compare glmark2-es2 results on Ubuntu 11.10 and 12.11.

glmark2-es2
=======================================================
glmark2 2012.03
=======================================================
OpenGL Information
GL_VENDOR: Vivante Corporation
GL_RENDERER: GC2000 core
GL_VERSION: OpenGL ES 2.0
=======================================================
[build] use-vbo=false: FPS: 31
[build] use-vbo=true: FPS: 30
[texture] texture-filter=nearest: FPS: 26
[texture] texture-filter=linear: FPS: 18
[texture] texture-filter=mipmap: FPS: 18
[shading] shading=gouraud: FPS: 19
[shading] shading=blinn-phong-inf: FPS: 12
[shading] shading=phong: FPS: 7
[bump] bump-render=high-poly: FPS: 6
[bump] bump-render=normals: FPS: 10
[bump] bump-render=height: FPS: 12
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 5
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 2
[pulsar] light=false:quads=5:texture=false: FPS: 12
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 14
[desktop] effect=shadow:windows=4: FPS: 0
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 10
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 7
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 7
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 14
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 6
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 7
[function] fragment-complexity=low:fragment-steps=5: FPS: 6
[function] fragment-complexity=medium:fragment-steps=5: FPS: 3
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 23
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 30
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 7
=======================================================
glmark2 Score: 12
=======================================================

In some cases, the HDMI display would just become black during 2D/3D testing for a short period of time (1 or 2 seconds).

I then tried video playback in Ubuntu, something I can’t do with any other boards or devices I own. I tried to play videos in Totem directly from a SAMBA share. Big Buck Bunny 480p plays just fine, but the 720p can’t play smoothly. So I copied Big Buck Bunny 1080p (~44 MB) to the micro SD. This took about 44 seconds (1MB/s), which means currently Wi-Fi performance is slower than in Android (1.42 MB/s). However, once I got the video in the micro SD, it could play just fine with low CPU usage.

I’ve performed a final quick test running Firefox, Totem (1080p video), es2gears, and htop at the same time (pictured above). Most of the time the system can manage this workload, but CPU usage is quite high (noticeably because of es2gears), and if you try to interact with Ubuntu while all those run, it’s just very sluggish. For example, if you take a screenshot with “Print Screen”, the pop-up window may take several seconds to appear, and video playback will be extremely choppy.  When I run all those programs at the same time, the system may also end up rebooting automatically.

Yet this is the first image that can boot properly on my HiAPAD Hi802, so this is good progress, and it shows good potential for this hardware. A faster micro SD, and/or replacing Unity with LXDE or XFCE desktop environment esshould greatly improve the responsiveness of the system.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

MK808 mini PC gets Android 4.2.2 Beta Firmware

March 19th, 2013 4 comments

Last week, Geekbuying announced the first release of Android 4.2.2 for MK808, with support for MK808B coming soon. They warn users that it’s still beta since this is the first time Android 4.2 is available on Rockchip RK3066 mini PC, however I could not find user’s complains in the comments section, but at least one users in ARMTvTech is disappointed by this release.

MK808

You’ll find three download links:

  • Android 4.2.2 for MK808 (dropbox) – Currently unavailable due to heavy traffic
  • Android 4.2.2 for MK808 rooted (Gdrive) – Same version as above but rooted by deadhp1
  • RKBatchTool  1.5 (dropbox)- Windows tool to perform the upgrade. Currently unavailable but there are alternate links.

Once you get the files, you can follow the instructions showing how to upgrade MK808 firmware, or watch the video showing the upgrade process. MK808 is another device I don’t own, so I haven’t been able to try it myself.

Beside a smoother experience, the most interesting of Android 4.2 new features for mini PCs is probably multiple user profiles so that each member of the family can keep their own settings and scores on one mini PC. There’s also Miracast support, but I doubt you can just convert you MK808 into a Miracast dongle easily, since Android is designed for Miracast “clients”. The rest of the new features (photo sphere, gesture typing, notifications…) are not really relevant to this type of device.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter