[Android Stick & Console RockChip based Computers] digitalhigh:
These are instructions for rooting Android devices that utilize the RK3066 chipset (Cortex A9 Dual Core, MALI Quad-Core GFX).

I have tested and verified that these instructions work for the UG007 Android-on-a-stick...they *should* work with any other devices that utilize the same USB chipset. I can almost guarantee this will work on the Imito MX1/2 as you can swap ROMS from this device.

(Basically, if you have the right ADB drivers, you should be good to go)

As per every other thread you read on this site - I TAKE NO RESPONSIBILITY FOR ANY DAMAGES YOU MAY CAUSE TO YOUR DEVICE.

This is a fairly risk-free mod, but you know...$hit happens.

Okay. Let's start.

THIS TUTORIAL ASSUMES YOU HAVE ADB AND KNOW HOW TO USE IT, and that you're in a Windows environment. There are numerous places on the web where you can find this info...and I ain't yo mamma. :D

1. Download all the files attached to this thread.

2. Attach your RK3066 device to your computer via it's microUSB port. You'll need to have it hooked to a display too.

3. Once booted, go to system settings. Under settings > developer options, enable USB Debugging. Under settings > USB, click "connect to computer" (This may vary depending on your ROM configuration. The point here is to have debugging enabled and your computer to recognize the stick in device manager as something other than USB storage)

4. Extract the right drivers for your system (x86/x64)

5. Go to device manager on your computer. Look for the new "unknown device". Right-click, pick "update driver software"., "browse my computer".

6. Browse to wherever you extracted the drivers in step 4. Click Next. Confirm that you want to install.

7. Open a command window in the directory where you have ADB. Type "adb devices". Still nothing, right?

8. Navigate to C:\users\MYUSERNAME\.android, where "MYUSERNAME" is your User Name. (Duh?)

9. Create a file called adb_usb.ini

10. Open it in a text editor. Add the following string and save (This tells ADB to look for our Vendor ID:

0x2207

11. You should now be able to type "adb devices" at CMD and see your device.

12. Now for the fun. Extract the stuff from "pushme" to the same directory as ADB.

13. Enter the following commands (note: The "$" and "#" symbols do not get keyed in):

adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter

14. Psneuter should run and close shell when done. Enter MOAR commands:

adb kill-server
adb devices
adb shell

15. Take a good look. Is there now a "#" sign? Good. You now have root access. You may continue. If not, then proceed to go yell at me in the comments. If yes, then proceed to enter the last batch of commands to make your newfound privileges permanent:

mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot

After a reboot, download a root app from Play Store to see if it worked! I find Root Checker is boffo for this sort of thing:

https://play.google.com/store/apps/...tcheck&feature=nav_result#?t=W251bGwsMSwyLDNd

THANKS/CREDITS:

Aaron Orquia @ Pocketables.com for the original "universal" root method.

AMJtech's tutorial where I found working ADB drivers and the adb_usb.ini bit to get it recognized.

The guy(s) who make Super1ClickRoot for putting all the necessary files in one easy-to-find spot. :D