tl;dr: Manual to install Linux on the UG007 HDMI Android stick.

Just to clarify, I am not liable if you destroy your device with the information given here. No guarantee given. If you follow this guide, you do it on your own responsibility and risk.

Order process

I recently ordered a UG007 HDMI Android stick on geekbuying for around 50 €. The package took around 3 weeks to arrive in Germany and was unfortunately first blocked by German customs. After paying the import tax (19%) I could finally take it home.

WIFI problems

For 50 € (+ 10 € taxes) it is an amazing piece of hardware! It worked out of the box quite good, only the WIFI made sometimes problems as mentioned by other users. To fix this, it actually helped to change the power supply. If I use as the power supply my cell phone charger or my laptop USB port the wifi works permanently. Must be some issues with too less or too much voltage with the shipped power supply.

Rooting the device

I wanted to use the stick as a media and gaming platform. So the first thing I tried was to root it, to be able to install the sixaxis software to use my Playstation 3 bluetooth controller with it.

To root the device from a Linux (Arch Linux) machine I did the following:

  1. plug the USB cable to power the stick in the Laptop
  2. check the Settings -> USB -> Connect to PC box on the stick
  3. check the Settings -> Developer options -> USB debugging box on the stick
  4. check on the Laptop the hardware ID of the stick with lsusb (the 4 digits before the colon, mine was 2207 it did not show any vendor string though).
  5. add a udev rule /etc/udev/rules.d/51-android.rules with the content SUBSYSTEM=="usb", ATTR{idVendor}=="0x2207", MODE="0666" (of course change 2207 here to your hardware id).
  6. make it executable chmod +x /etc/udev/rules.d/51-android.rules
  7. restart udev
  8. after that the device should be visible with the command adb devices (adb comes with the android sdk)
  9. Get the root files with busybox from somewhere (I used TPSarky-VonDroid-Root)
  10. Execute the following (probably some commands are redundant here):

  11. adb shell mv /data/local/tmp /data/local/tmp.bak

  12. adb shell ln -s /data /data/local/tmp
  13. adb reboot
  14. adb shell rm /data/local.prop > nul
  15. adb reboot
  16. adb shell id
  17. adb remount
  18. adb push su /system/bin/su
  19. adb shell chown /system/bin/su
  20. adb shell chmod 6755 /system/bin/su
  21. adb push busybox /system/bin/busybox
  22. adb shell chown /system/bin/busybox
  23. adb shell chmod 0755 /system/bin/busybox
  24. adb shell chown root.root /system/app/SuperSU.apk
  25. adb shell chmod 0644 /system/app/SuperSU.apk
  26. adb push RootExplorer.apk /system/app/RootExplorer.apk
  27. adb shell chown root.root /system/app/RootExplorer.apk
  28. adb shell chmod 0644 /system/app/RootExplorer.apk
  29. adb shell rm /data/local.prop
  30. adb shell rm /data/local/tmp
  31. adb shell mv /data/local/tmp.bak /data/local/tmp
  32. adb reboot

And that's it. The stick is rooted now.

Sixaxis PS3 controller over bluetooth

After that I installed the sixaxis app on the stick. The trick here is to change the master adress of the controller to the one of the stick. When running the sixaxis app, the bluetooth adress of the stick should be shown at the bottom. On my Linux laptop I used the controller before with the qtsixa application which is available in the AUR. This package also ships an application called sixpair which takes as an argument a bluetooth hardware adress. So after connecting the controller to my Linux box with USB and changing the hardware adress with sixpair it was working on the Android stick.
Btw for Linux I can recommend also the application qjoypad which allows to remap all the keys of the controller to keyboard events. It is possible e.g. to map the motion sensors to mouse movements. Otherwise there is also the package xf86-input-joystick available in the extra repository which allows X11 controls with the controller.

Flashing Linux

This was already nice but I was not completely satisfied with the Android system, I am used to use bash or python scripts extensively to automate tasks which was not so easy on the Android system. Furthermore the behaviour of Android with a connected mouse and keyboard still feels not right. You always have to think in touch screen ways. So I wanted to flash Linux on the stick.

Luckily there is this guy AndrewDB on the slatedroid forums which created a Linux image for the Rockchip based Android sticks (thanks for that!):

The only problem is that all the tutorials are based on flashing the device from a Windows box. Flashing Linux on an Android stick from Windows, why not use also Linux in the first place?

The flashing works basically by setting the stick to a flashing mode and overwriting the recovery partition which is /dev/block/mtdblock3 on the stick. In the slatedroid forum thread a guy named Patola had success by just using cat to overwrite the recovery partition with the zero padded kernel image (the partition has 16 mb the kernel image is around 8 mb).

I tried several things:

  • Padding the kernel image with zeros:  dd if=/dev/zero bs=1 count=8536064 >> kernel-0.3_pad.img (8536064 is the difference in byte between 16 mb and the kernel image size)
  • Then overwriting the partition with dd: dd if=kernel.img of=/dev/block/mtdblock3 bs=8192 (I also tried different block sizes)
  • Overwriting it with cat: cat kernel.img > /dev/block/mtdblock3
  • First overwriting the partition with zeros: dd if=/dev/zero of=/dev/block/mtdblock3 bs=8192 and then doing the above
Unfortunately all of the above methods did not properly overwrite the partition, each time the compare command **cmp** yielded a different byte in the partition and the image used. A restart of the stick into recovery mode (**reboot recovery**) which should boot the recovery partition just brought up a blank screen. Maybe I would need to set the stick into flashing mode first somehow (**reboot bootloader**) but I thought of this only afterwards.
So in the end I had to try it with the Windows flashing tool RKAndroidTools. With wine it didn't recognise the stick, so I tried it with virtualbox. Here I had to first setup properly the USB device which needs the **virtualbox-ext-oracle** package available from AUR. With this package I was able to see the stick in the Windows XP virtual machine (after activating USB 2.0 support in the virtual machine settings). I was then able to flash the recovery image with the RKAndroidTools as described in the README. The flashing tool is available from the custom Finless Android image which is available on the freaktab forums. I basically followed the readme included but in the tool **only checked the recovery checkbox** to not overwrite my Android image too. Before flashing I exchanged the recovery.img of the tool with my linux kernel image. Btw if you do let the other checkboxes checked, it should install the Finless Android image which is already rooted, so the process of rooting described above is not necessary anymore (however I did not test this).

After creating a Ubuntu memory card as described in the forum thread by formatting it with gparted to ext4 and label it linuxroot I can now boot into Ubuntu by executing reboot recovery on the stick. :)

Btw the Ubuntu image from AndrewDB needs a 4 GB stick, I only had a 2 GB one around so I deleted the folders /var/cache /usr/share/help /usr/share/doc and all locales but the english ones from /usr/share/locale/. This brought the image down to less than 2 GB while keeping all the functionality I needed.


I don't got milk

Posted on Mo 21 Januar 2013

Hey I was thinking of getting the MK808 and had a few questions I was hoping you could assist me with:

  1. I don't want Android, at all. Is it safe to wipe the Android setup so it only boots to Linux?
  2. I prefer a pretty barebone setup and only install the packages I need. Is there an Ubuntu image that doesn't have XFCE or any collection of software on it? Do you know how I can make my own image?
  3. Are you able to recover the system if the OS becomes dysfunctional?




Posted on Do 21 November 2013

Kind of a late response, but better late than never:

  1. I did not remove the stock Android to have the fallback if I break sth in the Linux system.
  2. If you install the provided image you can just remove everything you don't need afterwards. Ubuntu normally has these meta-packages where you can uninstall the whole graphics system with one apt-get command.
  3. That is why I let the Anroid on the system :). In the end the best is probably to backup your system regularly so that you can reinstall your backup image.