Home > Android, Rockchip RK30xx, Rockchip RK31xx, Windows 8 > Simplified Method to Install Rockchip USB Drivers in Windows XP/7/8

Simplified Method to Install Rockchip USB Drivers in Windows XP/7/8

When you need to root or upgrade Rockchip RK3066 or RK3188 devices, you’ll usually have to connect your device to your computer via USB, and in Windows, installing specific drivers (ADB drivers) is usually needed. However, many people seem to have problems with installing the proper driver, and their device may not be recognized properly. To simplify the task for Windows users, Rockchip has written a tool called RK Driver Assistant to automatically install the correct drivers on different Windows versions.

Here’s how to install the drivers with this tools.There’s no need to connect your Rockchip device during this procedure.

  1. Download and extract RK_DriverAssitant.zip
  2. Double click on DriverInstall.exe in Release_DriverAssitant directory to start the utility
  3. If you’ve already tried to install USB drivers for Rockchip devices, make sure to click “Uninstall Driver” first
    RK_Driver_Assistant_Install_Uninstall
  4. Then click “Install Driver”, and depending on your version of Windows the Security below may show up twice during installation. Just click “Install”
    RK_Driver_Assistant_Windows_Security
  5. Done. The drivers should be installed, and you’re ready to root your device, or install or upgrade your firmware via USB.

Via MINIX and AndroidPC.es

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

  1. OS/2user
    November 9th, 2013 at 11:22 | #1

    And what about Linux/BSD users, who don’t have access to anything coming from the “hell of Redmond”?
    What are they supposed to do?

  2. November 9th, 2013 at 11:37 | #2

    @OS/2user
    See http://www.cnx-software.com/2013/09/27/how-to-root-rockchip-devices-in-linux/

    It shows how to configure adb access before rooting the device.
    Unfortunately, I don’t think it’s possible to upgrade the firmware in Linux yet (TBC), since you still need to use another windows-only RK tool to do so.

  3. January 24th, 2014 at 16:29 | #3
  4. February 23rd, 2014 at 02:27 | #4

    To fix Windows 8.1 Radxa Unknown USB Device(Device Descriptor Request Failed) try this , it work for me.

    http://forum.xda-developers.com/showthread.php?t=2598155

  5. btjz89
    March 18th, 2014 at 20:35 | #5

    I’ve tried this package on a Win7 64-bit system and my Minix X7 device still isn’t be recognized. I’ve installed two other android device (Lenovo Yoga 10, Samsung Galaxy Nexus) with *some* issues, but they’ve since been working fine when I installed the appropriate drivers. Is there anything I should take into account when installing these drivers?

    I’m at a loss on how to get this working

  6. sanzen
    March 28th, 2014 at 20:52 | #6

    In addition to installing the driver, you may also need to add USB vendor ID and product ID into C:\Users\[user name]\.andriod\adb_usb.ini in order for adb to recognize the driver. Here is what mine now looks like:

    # ANDROID 3RD PARTY USB VENDOR ID LIST — DO NOT EDIT.
    # USE ‘android update adb’ TO GENERATE.
    # 1 USB VENDOR ID PER LINE.
    0×2207; 0×0010

    0×2207 is the vendor ID of Rockchip, 0×0010 is the product ID.

    Once this is done, it worked great. Note that adb access is available even USB mass storage is turned on.

    For reference, my system is Lenovo Yoga running 64-bit Windows 8.1. I also tested on a Dell running 32-bit Windows 7.

  7. Bjorn Muller
    June 30th, 2014 at 15:21 | #7

    sanzen :
    In addition to installing the driver, you may also need to add USB vendor ID and product ID into C:\Users\[user name]\.andriod\adb_usb.ini in order for adb to recognize the driver. Here is what mine now looks like:
    # ANDROID 3RD PARTY USB VENDOR ID LIST — DO NOT EDIT.
    # USE ‘android update adb’ TO GENERATE.
    # 1 USB VENDOR ID PER LINE.
    0×2207; 0×0010
    0×2207 is the vendor ID of Rockchip, 0×0010 is the product ID.
    Once this is done, it worked great. Note that adb access is available even USB mass storage is turned on.
    For reference, my system is Lenovo Yoga running 64-bit Windows 8.1. I also tested on a Dell running 32-bit Windows 7.

    I have used this installer to at last install an adb driver and make my win 7 PC recognize my Pipo M9Pro tablet after a lot of previous failing efforts. Unfortunately, it could not recognize it properly, It appears as SAMSUNG Android Phone instead of Pipo M9Pro, which may be the reason why some other softwares still do not find it.
    I wonder if I need to create and add this file adb_usb.ini to make it work all the way. But then, where do I find the right product ID?

  8. June 30th, 2014 at 15:43 | #8

    @Bjorn Muller
    You should be able to find it in the “Hardware Manager”.

  9. Bjorn Muller
    June 30th, 2014 at 20:22 | #9

    cnxsoft :
    @Bjorn Muller
    You should be able to find it in the “Hardware Manager”.

    Do you mean the Device Manager? In that case, there is a lot of information there. Here are some of the lines I think may be relevant:

    Hardware-ID
    USB\VID_2207&PID_0010&REV_0222&MI_01
    USB\VID_2207&PID_0010&MI_01
    Matching Unit-ID
    USB\VID_2207&PID_0010&MI_01
    Unit description reported by bus:
    M9Pro
    Name on på physical device unit
    \Device000009a
    Displayed name
    SAMSUNG Android Phone

    There is nothing there that reminds of the product ID 0×0010 quoted by sanzen. The only thing indicating this is my M9Pro is the “Unit description by bus”.

    I should also mention that I live in Sweden, so the Windows names are the Swedish ones translated by me, not the official Microsoft English names

  10. June 30th, 2014 at 20:28 | #10

    @Bjorn Muller
    Yes, sorry “Device Manager”, Windows has not been my main OS for a while…
    You can see the vendor ID (VID) and Product ID (PID).
    VID = 0×2207
    PID = 0×0010

    Maybe your firmware is set to show your device as “SAMSUNG Android Phone”, some people hack the ROMS that way for better Google Play compatibility. I have no idea if this is the reason you have problem.

  11. Bjorn Muller
    July 2nd, 2014 at 15:52 | #11

    I have original (unhacked) Pipo ROM. Anyway, I made the adb_usb.ini file, but nothing changed. I then decided to uninstall the driver and start all over, still using your RK_DriverAssitant.zip. But unlike the first time I tried it, it now doesn´t work at all. When I come to the point when I press “Install driver”, the response is “No found driver inf!”. What may have happened?

    Seems I am moving farther away from success.

    I should also mention, that I am not installling the adb driver in order to root. I am trying to get the “Recordable” app to work. This is an app for screen recording. It doesn´t require rooting, but adb driver must be installed. Unfortunately, when I last had my Win7 PC to recognize the M9Pro (although with a different name SAMSUNG Android Phone), the app could still not find it.

  12. Brent Rogers
    July 23rd, 2014 at 11:38 | #12

    I tried this, but got an error saying that the install failed.
    Did the uninstall
    But now the install says “No Driver inf”
    –what happened?
    –How do I install now?

  13. JJP
    July 24th, 2014 at 00:53 | #13

    I have the ssame problem than BM and BR, HELP PLEASE!!

  1. November 8th, 2013 at 23:47 | #1
  2. November 19th, 2013 at 22:10 | #2
  3. December 4th, 2013 at 22:35 | #3