[General Topics] sancho_sk:
Hello.

I just wish to share information on this device and my progress working with it.

The tablet is 10.1", resolution 1280x800, based on Rockchip RK3066 chipset, 1GB RAM, 8GB Flash, microSD slot, microHDMI slot, headphone output, USB OTG port.

So far I found these negatives:

charger vibrates during charging (maybe this is a problem of my device only)

USB OTG does not support USB hubs (stupid manufacturer disabled it within kernel module)

display is too bright - even the minimal brightness is too bright for night work

speakers are realy quiet

the cover for microUSB/microHDMI/microSD is lousy and sometimes it opens on the smallest touch

no kernel sources (wrote to the Polish support center twice and once to CZ support, no luck so far)

Other than that, the tablet is quite good and I am satisfied with my purchase.

I played with it for some time and I found a way to install CWM recovery for the tablet, so I decided to share the steps. I am using GNU/Linux, therefore this guide will focus on using it. I will assume you already have working ADB, therefore I'll skip its installation.

get RKflashTool for linux from here: RKFlashTool. This one is slightly modified to support Rockchip RK3066 correctly. Old versions could introduce problems during write operations, therefore DO NOT USE THEM!!!

get the CWM. I downloaded it from http://androtab.info/clockworkmod/rockchip/rk3066/, at the bottom of the page is a link for RK30GENERIC_CWM.zip.

make a work folder for the rkflashtool and extract the rkflashtool.c file onto the folder.

make sure you have a libusb dev files and gcc compiler - on Ubuntu run sudo apt-get install libusb-1.0-0-dev gcc

compile the sourcecode using gcc -o rkflashtool rkflashtool.c -lusb-1.0 -O2 -W -Wall -s

connect the tablet to PC using microUSB, go to Settings - Developer options and enable USB debugging.

run sudo adb devices and you should see the device connected

run command adb reboot bootloader (I assume you have adb utility within your PATH)

the device will restart with black screen, adb will no longer identify it. If you run lsusb command, you will see it changed from 2207:0010 to 2207:300a - this is what we need

now is a good time to get the device properties. Run sudo ./rkflashtool r 0x0 0x2000 > r105bk.param

if you now run something like less r105bk.param, you will see flash memory split for each system part - for example my device has a line like this: CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x00004000@0x00004000(kernel),0x00008000@0x00008000(boot),0x00008000@0x00010000(recovery),0x00100000@0x00018000(backup),0x0003a000@0x00118000(cache),0x00200000@0x00152000(userdata),0x00002000@0x00352000(kpanic),0x00100000@0x00354000(system),-@0x00454000(user)

from this we can see the size and start address of each flash part. I would recommend backup whatever you feel important (I personaly made a backup of whole flash just to have it later, should anything go wrong)

we will rewrite two flash parts - misc and recovery, therefore we will backup them first using sudo ./rkflashtool r 0x00010000 0x00008000 > r105bk.recovery.img and sudo ./rkflashtool r 0x00002000 0x00002000 > r105bk.misc.img

now extract the RK30GENERIC_CWM.zip using unzip -d RK30 RK30GENERIC_CWM.zip

we will flash the proposed recovery and misc from ClockworkMod using sudo ./rkflashtool w 0x00010000 0x00008000 < RK30/recovery.img and sudo ./rkflashtool w 0x00002000 0x00002000 < RK30/misc-boot-recovery.img

now the only thing to do is to reboot the device using sudo ./rkflashtool b

the device starts using recovery, to navigate use volume +/- buttons, to select a menu option use power button

navigate to reboot and simply reboot the device

That's about it.

So far I extracted also the system image using similar steps described above, mounted it locally, replaced the boot animation and flashed it back to the device. No problem, the CMX animation is far better than the GoClever original one ;)

I have to say that the inability to connect USB HUB to the OTG connector really makes me angry, so I will probably look for ways to enable it and I will share it once I find something.